[EPEL-devel] Re: borgbackup: Rebuilt to change main python from 3.4 to 3.6
On Sat, Mar 9, 2019 at 8:19 PM Kevin Fenzi wrote: > > 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 > You have a good point Kevin. I'll be tagging everything into an update today. I'll just tag in the newer borgbackup. I've added this newer one to my list of packages for the big update. But in general, I think we need to have a statement on what to do after I've done the big update. 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: 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: 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
