mohanboddu reported a new issue against the project: `releng` that you are following: `` The fedora 31 schedule[1] has a mass rebuild scheduled for Jul 24 2019, We need to plan and coordinate all tasks in preparation for it.
[1] https://fedoraproject.org/wiki/Releases/31/Schedule
``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
mohanboddu added a new comment to an issue you are following: `` Here's the list for mass rebuild:
https://pagure.io/releng/issue/8501 https://pagure.io/releng/issue/8482 https://pagure.io/releng/issue/8462 https://pagure.io/releng/issue/8395 https://pagure.io/releng/issue/8340 https://pagure.io/releng/issue/7575 ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
jcajka added a new comment to an issue you are following: `` https://pagure.io/releng/issue/8481 is missing on the list. I'm work atm on getting the prerelease version in. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
jcajka added a new comment to an issue you are following: `` There might be expected FTBFS on golang side of things due to the on going work on new macros stack. Following packages might fail to build(with broken deps): ``` arduino-builder buildah caddy consul containernetworking-plugins cri-tools deepin-api deepin-daemon delve dep direnv dnscrypt-proxy docker-distribution git-octopus glusterd2 go-bindata godep gomtree gotun grafana heketi hugo ignition jid kata-ksm-throttler kata-osbuilder kata-proxy kata-shim kompose kubernetes manifest-tool mantle micro moby-engine obfs4 oci-kvm-hook oci-register-machine ocitools openvswitch-ovn-kubernetes origin oshinko-cli podman popub reg restic rkt runc singularity skopeo snapd startdde source-to-image swig xe-guest-utilities ``` If they fail due to the broken deps they will be rebuild by the owners of https://fedoraproject.org/wiki/Changes/Adopt_new_Go_Packaging_Guidelines in collaboration with the respective maintainers. I have just spoke about it with @eclipseo ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
jcajka added a new comment to an issue you are following: ``
https://pagure.io/releng/issue/8481 is missing on the list. I'm work atm on getting the prerelease version in.
Ready in koji https://koji.fedoraproject.org/koji/buildinfo?buildID=1319666 ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
jcajka added a new comment to an issue you are following: ``
https://pagure.io/releng/issue/8481 is missing on the list. I'm work atm on getting the prerelease version in.
Ready in koji https://koji.fedoraproject.org/koji/buildinfo?buildID=1319666
Actually I have omitted one patch this is correct build https://koji.fedoraproject.org/koji/taskinfo?taskID=36450997 ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
mohanboddu added a new comment to an issue you are following: `` @jcajka Thanks for the update. We will use `golang-1.13-0.beta1.2.fc31` for mass rebuild. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
mohanboddu added a new comment to an issue you are following: `` We are not including [.plt.got isolation](https://pagure.io/releng/issue/7575) in this mass rebuild as it was not accepted upstream. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
churchyard added a new comment to an issue you are following: `` Are the s390x builders OK?
``` DEBUG util.py:587: CuraEngine-lulzbot-1:3.6.12-3.fc31 ######################################## DEBUG util.py:585: BUILDSTDERR: error: unpacking of archive failed on file /builddir/build/SOURCES/CuraEngine-lulzbot-3.6.12.tar.gz;5d387e80: cpio: read failed - Inappropriate ioctl for device DEBUG util.py:585: BUILDSTDERR: error: /builddir/build/originals/CuraEngine-lulzbot-3.6.12-3.fc31.src.rpm cannot be installed ```
https://koji.fedoraproject.org/koji/taskinfo?taskID=36462135 ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
churchyard added a new comment to an issue you are following: `` (Seem like an isolated incident.) ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
kevin added a new comment to an issue you are following: `` We have seen this very sporadically on those builders when they are under high load. ;( ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
ppisar added a new comment to an issue you are following: `` I've also noticed the ioctl error on dontpanic package and reported it https://pagure.io/fedora-infrastructure/issue/8029 as I could not find it in the issues.
More importantly, are relengs going to retry these failures? Or should do that packagers instead. If packagers, can they resubmit the built into the side tag right now? F30 rebuild suffered from dist-git failures (repository not found) and I had to resubmit tens of these builds. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
churchyard added a new comment to an issue you are following: `` If you do a regular rawhide build and it succeeds, the package goes away from https://kojipkgs.fedoraproject.org/mass-rebuild/f31-failures.html ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
ppisar added a new comment to an issue you are following: `` That solves the symptoms (the package is not enumerated as failed) but it produces a package built in a different build root with a possibly different compiler, RPM macros etc.
Is somewhere documented whether this side tag enables some of these changes? Or is this time pretty safe to rebuild packages in whatever build root? ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
sharkcz added a new comment to an issue you are following: ``
I've also noticed the ioctl error on dontpanic package and reported it https://pagure.io/fedora-infrastructure/issue/8029 as I could not find it in the issues. More importantly, are relengs going to retry these failures? Or should do that packagers instead. If packagers, can they resubmit the built into the side tag right now? F30 rebuild suffered from dist-git failures (repository not found) and I had to resubmit tens of these builds.
The rel-eng meeting yesterday touched the idea of a re-rebuild to workaround the infra glitches. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
mizdebsk added a new comment to an issue you are following: ``
That solves the symptoms (the package is not enumerated as failed) but it produces a package built in a different build root with a possibly different compiler, RPM macros etc.
Mass rebuild uses the standard rawhide buildroot - `f31-build`. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
kevin added a new comment to an issue you are following: `` Yeah, I think we should wait until the mass rebuild is over, then just resubmit all the failed builds again. That won't get all of them, but should help, and perhaps we can target more from that final pool of failures.
``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
churchyard added a new comment to an issue you are following: `` Note that a duplicated F31FTBFS bugzilla was created: https://bugzilla.redhat.com/show_bug.cgi?id=1732841
I've marked it as duplicate. Will check if it is hardcoded anywhere in this repo and update the number. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
churchyard added a new comment to an issue you are following: `` https://pagure.io/releng/pull-request/8574 ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
The status of the issue: `Fedora 31 Mass Rebuild` of project: `releng` has been updated to: Closed as Fixed by kevin.
kevin added a new comment to an issue you are following: `` This is done.
:christmas_tree: ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555
rel-eng@lists.fedoraproject.org
-
Dan Horák -
Jakub Čajka
-
Kevin Fenzi
-
Mikolaj Izdebski
-
Miro Hrončok
-
Mohan Boddu
-
Petr Pisar