ignatenkobrain reported a new issue against the project: `releng` that you are following: `` https://fedoraproject.org/wiki/Changes/Packaging_Rust_applications_and_libra...
Release Engineering are one of key persons in implementing this change because tools should be ported to DNF, `with` rich operator should be supported from tools (speaking as DNF team member, it should *just* work).
As a creator of change proposal and member of DNF team, I will help rel-eng as much as I can. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
ignatenkobrain added a new comment to an issue you are following: `` @mohanboddu I tihnk this is missing f27 label... ;) ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
mohanboddu added a new comment to an issue you are following: `` We ack this requires releng work and currently we are working on porting our tools to dnf. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
mohanboddu added a new comment to an issue you are following: `` Its a huge change and it needs more coordination with the fedora tooling and also more with internal teams on how things are built, delivered and tested and everything else that gets effected. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
ignatenkobrain added a new comment to an issue you are following: `` @mohanboddu sure, I wrote this in the beginning ;) do you want me to take any actions now or just wait until someone from rel-eng will contact me? Ideally, we need this earlier than final freeze so we have time to submit package reviews, approve them, import them and such. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
ngompa added a new comment to an issue you are following: `` @ausil @mohanboddu:
What the heck? Why was this untagged? All the tooling should be in place *now*, with pungi supporting DNF as a depsolving algorithm. It should have been started to be used with Rawhide after the porting was done during Fedora 26 development cycle. @ignatenkobrain has even offered up his services to help speed up any remaining issues through the Fedora 27 development cycle.
:angry:
``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
ausil added a new comment to an issue you are following: `` we need to ensure that all the systems dealing with packages are able to cope with the change. This touches on every piece of the delivery pipeline, it needs input from QA, and infrastructure at the least to make sure we have plans to cope properly. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
ignatenkobrain added a new comment to an issue you are following: `` @ausil 1. Who and when will provide this information? 2. Who and when will provide information what needs to be done in order to accomplish this change?
P.S. F27 release cycle is quite short, so I need to know precisely who and what will be doing so I can offer my help and to slip this change to F28 just because someone didn't pay attention to this. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
ausil added a new comment to an issue you are following: `` @adamwill @tflink what state are the QA systems for ensuring that they can all read rpms with rich dependencies.
@kevin same for infra, likely every system in the build and delivery pipeline that runs rhel will need to be upgraded. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
kevin added a new comment to an issue you are following: `` Well, lets see:
* koji builders are fedora - fine * koji hubs are rhel7 - would need switching to fedora * rawhide/branched composers are fedora - fine * bodhi-backend01 is fedora - fine
so it sounds to me like the hubs would be the main thing. Of course all the tools on those things... koji, pungi, bodhi would need support. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
ignatenkobrain added a new comment to an issue you are following: `` @kevin note that we need to support here new rich dependency which is coming within F27 itself. Probably we will need RPM 4.14 somewhere on builders (mosr probably). I'm volunteering to maintain special RPM 4.13 (current in all fedoras) which support that kind of dependency if required. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
kevin added a new comment to an issue you are following: `` I'd really like to avoid doing that if we can. We have done that in the past and it was a big pain. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
puiterwijk added a new comment to an issue you are following: ``
Well, lets see:
koji builders are fedora - fine koji hubs are rhel7 - would need switching to fedora rawhide/branched composers are fedora - fine bodhi-backend01 is fedora - fine
Signing bridges are RHEL7 - would need switching
so it sounds to me like the hubs would be the main thing. Of course all the tools on those things... koji, pungi, bodhi would need support.
``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
jkurik added a new comment to an issue you are following: `` This Change has been deferred to F28. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
ignatenkobrain added a new comment to an issue you are following: `` @puiterwijk signing might just work... but we need to try-and-see..
@kevin, when would be good time to see what breaks? ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
ngompa added a new comment to an issue you are following: `` Signing bridges shouldn't care, since RPM shouldn't be processing the dependency header information... It's handled rich deps packages so far, I imagine it can handle this too. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
kevin added a new comment to an issue you are following: ``
@puiterwijk signing might just work... but we need to try-and-see.. @kevin, when would be good time to see what breaks?
Well, ideally we would wait for a less busy day where rawhide compose finished fine. Then you push a package, we make sure it's signed and then fire a new rawhide compose. If things blow up we untag it and fix them and try again later.
Possibly after flock? ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
ignatenkobrain added a new comment to an issue you are following: ``
Possibly after flock?
Would work for me, just let me know once you are ready! :wine_glass: ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6889
rel-eng@lists.fedoraproject.org
-
Dennis Gilmore -
Igor Gnatenko
-
Jan Kurik
-
Kevin Fenzi
-
Mohan Boddu
-
Neal Gompa
-
Patrick "マルタインアンドレアス" Uiterwijk