Bug#930134: Please package new upstream version
Hey Thomas, Jonas Meurer: > Thomas Goirand: Also, the current OpenStack version needs 1.4.1, so uploading 2.0.0 to Experimental would break it. >>> >>> Mh, but the version in Debian is 1.0.0, so that doesn't work for current >>> OpenStack version either, right? Mailman3 would be fine with any version >>> newer than 1.0.0, so 1.4.1 would be sufficient. >> >> Falcon 1.4.1 requires python3-mimeparse (>= 1.5.2), which isn't packaged >> in Debian. Can you fill a bug against it so that it gets upgraded in >> Experimental as well? Otherwise, I wont be able to do the work. > > Sure, I did this now: https://bugs.debian.org/930499 > > The package seems rather unmaintained, though. So I assume that one of > us needs to take care of it. But let's wait a bit, maybe I'm mistaken ;) as you might have seen, python-mimeparse 1.6.1 just got uploaded to experimental, closing #930499. Cheers jonas signature.asc Description: OpenPGP digital signature
Bug#930134: Please package new upstream version
Thomas Goirand: >>> Also, the current OpenStack version >>> needs 1.4.1, so uploading 2.0.0 to Experimental would break it. >> >> Mh, but the version in Debian is 1.0.0, so that doesn't work for current >> OpenStack version either, right? Mailman3 would be fine with any version >> newer than 1.0.0, so 1.4.1 would be sufficient. > > Falcon 1.4.1 requires python3-mimeparse (>= 1.5.2), which isn't packaged > in Debian. Can you fill a bug against it so that it gets upgraded in > Experimental as well? Otherwise, I wont be able to do the work. Sure, I did this now: https://bugs.debian.org/930499 The package seems rather unmaintained, though. So I assume that one of us needs to take care of it. But let's wait a bit, maybe I'm mistaken ;) Cheers jonas signature.asc Description: OpenPGP digital signature
Bug#930134: Please package new upstream version
On 6/10/19 9:59 PM, Jonas Meurer wrote: > Hi Thomas, > > Thomas Goirand: >>> do you have plans to update the python-falcon packages to a newer >>> upstream version (2.0.0 being the most recent one at the moment) >>> anytime soon? >>> >>> python3-falcon is a dependency for mailman3 and starting with mailman3 >>> version 3.2.2, falcon > 1.0.0 is required. So I'll have to wait for the >>> python-falcon update before being able to update mailman3 to latest >>> upstream release. >> >> OpenStack Train (ie: the next version, due for early September) also >> needs version 2.0.0, so I will package that. However, I don't see any >> urgency during the Buster freeze. > > Sounds reasonable to me. I agree that we're not in a rush and can easily > wait until after the Buster release. > >> Also, the current OpenStack version >> needs 1.4.1, so uploading 2.0.0 to Experimental would break it. > > Mh, but the version in Debian is 1.0.0, so that doesn't work for current > OpenStack version either, right? Mailman3 would be fine with any version > newer than 1.0.0, so 1.4.1 would be sufficient. > > Cheers > jonas > > Falcon 1.4.1 requires python3-mimeparse (>= 1.5.2), which isn't packaged in Debian. Can you fill a bug against it so that it gets upgraded in Experimental as well? Otherwise, I wont be able to do the work. Cheers, Thomas Goirand (zigo)
Bug#930134: [PKG-Openstack-devel] Bug#930134: Please package new upstream version
On 6/10/19 9:59 PM, Jonas Meurer wrote: > Mh, but the version in Debian is 1.0.0, so that doesn't work for current > OpenStack version either, right? Mailman3 would be fine with any version > newer than 1.0.0, so 1.4.1 would be sufficient. > > Cheers > jonas As much as I know, 1.0.0 to 1.4.1 is fine for OpenStack Stein (currently in Experimental). Let's see if I can upgrade to 1.4.1 then. Cheers, Thomas Goirand (zigo)
Bug#930134: Please package new upstream version
Hi Thomas, Thomas Goirand: >> do you have plans to update the python-falcon packages to a newer >> upstream version (2.0.0 being the most recent one at the moment) >> anytime soon? >> >> python3-falcon is a dependency for mailman3 and starting with mailman3 >> version 3.2.2, falcon > 1.0.0 is required. So I'll have to wait for the >> python-falcon update before being able to update mailman3 to latest >> upstream release. > > OpenStack Train (ie: the next version, due for early September) also > needs version 2.0.0, so I will package that. However, I don't see any > urgency during the Buster freeze. Sounds reasonable to me. I agree that we're not in a rush and can easily wait until after the Buster release. > Also, the current OpenStack version > needs 1.4.1, so uploading 2.0.0 to Experimental would break it. Mh, but the version in Debian is 1.0.0, so that doesn't work for current OpenStack version either, right? Mailman3 would be fine with any version newer than 1.0.0, so 1.4.1 would be sufficient. Cheers jonas signature.asc Description: OpenPGP digital signature
Bug#930134: Please package new upstream version
On 6/7/19 7:25 PM, Jonas Meurer wrote: > Package: src:python-falcon > Version: 1.0.0-2 > Severity: normal > > Hello, > > do you have plans to update the python-falcon packages to a newer > upstream version (2.0.0 being the most recent one at the moment) > anytime soon? > > python3-falcon is a dependency for mailman3 and starting with mailman3 > version 3.2.2, falcon > 1.0.0 is required. So I'll have to wait for the > python-falcon update before being able to update mailman3 to latest > upstream release. > > Cheers > jonas Hi, OpenStack Train (ie: the next version, due for early September) also needs version 2.0.0, so I will package that. However, I don't see any urgency during the Buster freeze. Also, the current OpenStack version needs 1.4.1, so uploading 2.0.0 to Experimental would break it. Cheers, Thomas Goirand (zigo)
Bug#930134: Please package new upstream version
Package: src:python-falcon Version: 1.0.0-2 Severity: normal Hello, do you have plans to update the python-falcon packages to a newer upstream version (2.0.0 being the most recent one at the moment) anytime soon? python3-falcon is a dependency for mailman3 and starting with mailman3 version 3.2.2, falcon > 1.0.0 is required. So I'll have to wait for the python-falcon update before being able to update mailman3 to latest upstream release. Cheers jonas
