On Sat, Mar 9, 2019 at 9:47 AM Benjamin Pereto <benjamin@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
