You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using the rpms-openqa repo to build packages for debian bullseye using debbuild like described in this blog post. This was working up to version 4.6.2. Starting 4.7.0 I started getting build failures due to an md2man issue, which was fixed with commit 1d3d97a. However with that issue resolved, I'm still having build issues. Starting at 4.8.0 (when that md2man issue was fixed), I get a build failure that makes very little sense. I can go into the debbuild build environment, and run the same build command (that debbuild is running) by hand, and get the same failure:
That's it. I get no more explanation of the failure than that. The cp succeeded fine as I can see the file in the destination path. There's something else that's failing that is not shown.
Any ideas what might be failing? Or is there a more appropriate place to ask?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been using the rpms-openqa repo to build packages for debian bullseye using debbuild like described in this blog post. This was working up to version 4.6.2. Starting 4.7.0 I started getting build failures due to an
md2man
issue, which was fixed with commit 1d3d97a. However with that issue resolved, I'm still having build issues. Starting at 4.8.0 (when thatmd2man
issue was fixed), I get a build failure that makes very little sense. I can go into thedebbuild
build environment, and run the same build command (thatdebbuild
is running) by hand, and get the same failure:^ version 4.9.0
That's it. I get no more explanation of the failure than that. The
cp
succeeded fine as I can see the file in the destination path. There's something else that's failing that is not shown.Any ideas what might be failing? Or is there a more appropriate place to ask?
Beta Was this translation helpful? Give feedback.
All reactions