[EPEL-devel] Re: borgbackup: Rebuilt to change main python from 3.4 to 3.6
On 3/9/19 7:16 PM, Troy Dawson wrote: > On Sat, Mar 9, 2019 at 9:47 AM Benjamin Pereto > wrote: >> >> Hi, >> >> I saw that you rebuilt borgbackup ( >> https://apps.fedoraproject.org/packages/borgbackup) for python3.6. >> >> thanks for that! >> >> Now I wanted to build a new package with the new upstream release and ran in >> some issues to deploy. >> The package depends on python3-llfuse and python3-msgpack. Thanks to the >> buildroot the package is built successfully, but submit it to testing would >> lead >> to install failures because of the missing new version of msgpack and llfuse. >> >> How should I approach that? Is it needed that the maintainers of llfuse and >> msgpack push the new version first to stable? >> >> Best regards, >> Benjamin > Hi Benjamin, > This is a very good question. > I'm sending it to epel-devel, because I'm sure you aren't the only > person that is going to ask it, and I want to make sure I/we give a > consistent answer to everyone. > Also, I'm sorta just the proven packager that volunteered to do the > rebuild. I'd rather the python-sig and/or developers give the final > answer. > > Epel Python Sig (or whoever was in charge of the python34 to python36 > change), what should Benjamin do with his package? You (or whoever makes the big python36 update) should add in that new build to that big update so it goes out with everything else. ;) kevin signature.asc Description: OpenPGP digital signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Epel7 Questions: Python34 - 36 transition
On 3/9/19 7:15 PM, Troy Dawson wrote: > Hello, > There are a few questions I have, and since I'm not positive who all > of the correct people ask are, I'm sending to the epel-devel list. > > Before I start the questions, thank you to everyone who helped out in > getting the build failures working. Thank you. thank you. thank you. > > We have all the python packages rebuilt. All of the packages needed > for the rebuilds are tagged into override, and thus in the buildroot. > None of these rebuilt packages have been put into updates, and thus > are not in -testing. > > Where do we go from here? > A) Do I do one big update for all of the rebuilt packages? Yes. > B) Do I do individual updates for each package? > C) Some combination of above? Bad idea, as then some dependent packages could go out stable without all the packages they need. > D) Do a side tag, and take out all the overrides? Nope... side tag won't push them out, unless we just merge them into the main tag, but then they are bypassing testing. > I personally think C. Do the main components (rpm macros, python34 > and python36) in one update. All the rest get their individual > update. All the other ones are going to need at least python36, so no, they should all be in one big update. Otherwise some of them could go stable and not have the python36 yet. > How long do we expect to be in this testing stage? I'd say at least 2 weeks? > If packagers want to update their python package for whatever reason, > what should they do? Build as usual, but ask someone to edit the update and remove the previous one and add in the new one. Thanks for building and coordinating everything! kevin signature.asc Description: OpenPGP digital signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: borgbackup: Rebuilt to change main python from 3.4 to 3.6
On Sat, Mar 9, 2019 at 9:47 AM Benjamin Pereto wrote: > > Hi, > > I saw that you rebuilt borgbackup ( > https://apps.fedoraproject.org/packages/borgbackup) for python3.6. > > thanks for that! > > Now I wanted to build a new package with the new upstream release and ran in > some issues to deploy. > The package depends on python3-llfuse and python3-msgpack. Thanks to the > buildroot the package is built successfully, but submit it to testing would > lead > to install failures because of the missing new version of msgpack and llfuse. > > How should I approach that? Is it needed that the maintainers of llfuse and > msgpack push the new version first to stable? > > Best regards, > Benjamin Hi Benjamin, This is a very good question. I'm sending it to epel-devel, because I'm sure you aren't the only person that is going to ask it, and I want to make sure I/we give a consistent answer to everyone. Also, I'm sorta just the proven packager that volunteered to do the rebuild. I'd rather the python-sig and/or developers give the final answer. Epel Python Sig (or whoever was in charge of the python34 to python36 change), what should Benjamin do with his package? Troy ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Epel7 Questions: Python34 - 36 transition
Hello, There are a few questions I have, and since I'm not positive who all of the correct people ask are, I'm sending to the epel-devel list. Before I start the questions, thank you to everyone who helped out in getting the build failures working. Thank you. thank you. thank you. We have all the python packages rebuilt. All of the packages needed for the rebuilds are tagged into override, and thus in the buildroot. None of these rebuilt packages have been put into updates, and thus are not in -testing. Where do we go from here? A) Do I do one big update for all of the rebuilt packages? B) Do I do individual updates for each package? C) Some combination of above? D) Do a side tag, and take out all the overrides? I personally think C. Do the main components (rpm macros, python34 and python36) in one update. All the rest get their individual update. How long do we expect to be in this testing stage? If packagers want to update their python package for whatever reason, what should they do? Troy ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Koji Build Failure Due To Dependency EPEL Dependency Issue
Thanks a lot Kevin! I can confirm it built perfectly! (ref https://koji.fedoraproject.org/koji/taskinfo?taskID=33328352) I truly appreciate your help! Chris On Sat, Mar 9, 2019 at 1:16 AM Kevin Fenzi wrote: > On 3/8/19 6:01 PM, Chris wrote: > > Hi guys, > > > > I apologize if this is a bit premature to revisit this subject. The > thing > > is, the releng ticket Stephen created ( > https://pagure.io/releng/issue/8185) > > based on my Bugzilla ticket ( > > https://bugzilla.redhat.com/show_bug.cgi?id=1684830) got closed and > marked > > resolved, but the build process still continues to fail. > > > > Recent Koji Build Fail Source: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=33310604 > > > > I sat on this for a week thinking maybe it just took time for this change > > to propagate, but now that this was week #2 and it was still failing... i > > should bother you all again :). > > > > Is this a RedHat issue? Perhaps just waiting for the Bugzilla issue to > > close will actually rectify my issue? i realize this can take months; > but > > it's a perfectly acceptable answer. I guess i'm just looking for closure > > at this point. I'd love to share my app with the rest of the fedora > > community. > > > > Thanks in advance! > > Sorry this has been a pain. ;( > > Anyhow, it did get blocked but there was still a version of the package > tagged into epel7 so that was messing things up. I untagged that one and > (I hope you don't mind) resubmitted your scratch build... and now it > completes. :) > > So, you should be all good now I hope. > > kevin > > > ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
