On Fri, Aug 14, 2020 at 1:15 PM Fabio Valentini <decathorpe@xxxxxxxxx> wrote: > Sérgio, I have no idea what you're talking about here. Do you mean the > new policy to wait with a rawhide compose until the first "branched" > compose is successful and synced out? If I understand correctly, that > "policy" is enforced by bodhi not allowing any builds into "branched" > by default, and releng not launching any rawhide composes until a > "branched" compose finishes. > > I have no superpowers that allow me to circumvent those restrictions :) > If I had, I would untag glibc 2.22.9000 to check if it is indeed > broken, or if my development PC is haunted instead. I added "exit 1" to the end of %install in one of the affected OCaml packages, so that I could inspect the contents of /builddir/build/BUILDROOT in the mock chroot. The files all have the correct permissions. Yet when the binary RPM is generated, executable files are missing write permission for user; i.e., they have 555 permissions instead of 755. I am also seeing "Error in <unknown> scriptlet in rpm package x", where x is some random package, when running mock with --enablerepo=local, just as Fabio reported. The combination of the two makes me suspect that RPM has gone bonkers in Rawhide, whether due to the new version of glibc or something else, I couldn't say. -- Jerry James http://www.jamezone.org/ _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
