Bug#936806: koji: Python2 removal in sid/bullseye
On Sun, Feb 23, 2020 at 04:06:23PM +0100, Marek Marczykowski-Górecki wrote: > > so for the record: while I can easily workaround the above problem by using > > a > > Fedora based VM to download updates for my Qubes dom0, I'd be glad to help > > people to get yum, dnf and rpm back into Debian, eg by sponsoring such > > uploads. > Mihai have prepared packages for all of them and sent mail about it to > debian-devel here: > https://lists.debian.org/debian-devel/2019/09/msg00218.html ah, cool! & thanks for the reminder, Marek! > But he never get any response there... > I guess the next step would be someone to help him upload the packages to > Debian. added to my list, though i suspect it will take two weeks until i get to it... -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C we'll all die. make a difference while you can. disobey. smile. signature.asc Description: PGP signature
Bug#936806: koji: Python2 removal in sid/bullseye
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, Feb 22, 2020 at 12:11:04AM +, Holger Levsen wrote: > Hi, > > On Fri, Feb 14, 2020 at 03:12:20AM +0100, Marek Marczykowski-Górecki wrote: > > > I mean, rpm is definitly still useful to have on Debian, but yum and > > > friends??? > > They are also useful in some cases. For example if you want to use > > Debian-based VM to download updates for your Qubes dom0... > > hah, touche! > > so for the record: while I can easily workaround the above problem by using a > Fedora based VM to download updates for my Qubes dom0, I'd be glad to help > people to get yum, dnf and rpm back into Debian, eg by sponsoring such > uploads. Mihai have prepared packages for all of them and sent mail about it to debian-devel here: https://lists.debian.org/debian-devel/2019/09/msg00218.html But he never get any response there... I guess the next step would be someone to help him upload the packages to Debian. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAl5SlO8ACgkQ24/THMrX 1ywG4Af/d2hQWrq0NKpe9uNAwfE6byB0GbN96xJhkeGc+S+s/qU9/j7m+TrNqO0h SqRxinm/eYmehIxpViJ4F+dd0ATU9WhehwopFRV0zT/w2D5hIQNjoxx0uYIFAqFi qmxzWbzAv/LkJgRr4mJ9E9ztmb3vllbu2iCBdtnQTL2PzVKgaFjizfynX+gC2TZi Mkzay56ANtmUHqTlKkDKujZpwKX9oGJiyb7iJd2H4W1iUixHKsi3pfFNPTBoe6Ys RxoJ7InQmCM7I/kvDW7QlK/HduYS2FLnvH4ShQr52wa+5UQbnsPFmO8/9mhg8T0f 5BkiQAt7xh4cB7/MOjfHP/IS0uDsqA== =fI8y -END PGP SIGNATURE-
Bug#936806: koji: Python2 removal in sid/bullseye
Hi, On Fri, Feb 14, 2020 at 03:12:20AM +0100, Marek Marczykowski-Górecki wrote: > > I mean, rpm is definitly still useful to have on Debian, but yum and > > friends??? > They are also useful in some cases. For example if you want to use > Debian-based VM to download updates for your Qubes dom0... hah, touche! so for the record: while I can easily workaround the above problem by using a Fedora based VM to download updates for my Qubes dom0, I'd be glad to help people to get yum, dnf and rpm back into Debian, eg by sponsoring such uploads. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#936806: koji: Python2 removal in sid/bullseye
On 2/14/20 2:30 AM, Holger Levsen wrote: > On Thu, Feb 13, 2020 at 08:14:11PM -0500, Sandro Tosi wrote: >> thanks! I'm gonna go ahead and file an RM bug for the following pkgs >> too: yum createrepo python-lzma yum-metadata-parser mock yum-utils >> dtc-xen deltarpm >> >> they are a closed set > > thank you for cleaning up after all of us, now that we reached containers. > (which used to be called virtualisation mainframes before... ;) > > I mean, rpm is definitly still useful to have on Debian, but yum and > friends??? I am the one that maintained yum for about a decade in Debian. Yum is (was?) useful because it does the same thing as debootstrap. Ie: with it, you can bootstrap a CentOS chroot from a Debian host, which may be useful for example if using Xen (or other virtualization systems). That was in fact my use case. Anyway, yum is kind of dead, as distros have been moving to dnf. I see therefore no reason to keep it. Cheers, Thomas Goirand (zigo)
Bug#936806: koji: Python2 removal in sid/bullseye
On Fri, Feb 14, 2020 at 01:30:29AM +, Holger Levsen wrote: > On Thu, Feb 13, 2020 at 08:14:11PM -0500, Sandro Tosi wrote: > > thanks! I'm gonna go ahead and file an RM bug for the following pkgs > > too: yum createrepo python-lzma yum-metadata-parser mock yum-utils > > dtc-xen deltarpm > > > > they are a closed set > > thank you for cleaning up after all of us, now that we reached containers. > (which used to be called virtualisation mainframes before... ;) > > I mean, rpm is definitly still useful to have on Debian, but yum and > friends??? They are also useful in some cases. For example if you want to use Debian-based VM to download updates for your Qubes dom0... -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? signature.asc Description: PGP signature
Bug#936806: koji: Python2 removal in sid/bullseye
On Thu, Feb 13, 2020 at 08:14:11PM -0500, Sandro Tosi wrote: > thanks! I'm gonna go ahead and file an RM bug for the following pkgs > too: yum createrepo python-lzma yum-metadata-parser mock yum-utils > dtc-xen deltarpm > > they are a closed set thank you for cleaning up after all of us, now that we reached containers. (which used to be called virtualisation mainframes before... ;) I mean, rpm is definitly still useful to have on Debian, but yum and friends??? -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C There are no jobs on a dead planet. signature.asc Description: PGP signature
Bug#936806: koji: Python2 removal in sid/bullseye
On Sat, Feb 8, 2020 at 1:51 PM Moritz Mühlenhoff wrote: > > On Thu, Jan 30, 2020 at 01:36:33AM -0500, Sandro Tosi wrote: > > > > koji is keeping createrepo in the archive, which keeps python-lzma in > > > > the archive. > > > > > > there's also mock, yum, rpm, deltarpm and yum-metadata-parser affected by > > > this. > > > > yep i came across all of them starting from python-lzma -- do you know > > what's the status of the "RedHat infrastructure" in debian? many (if > > not all) of those tools are relatively old, not maintained (or just in > > life support mode) and most of all, python2 with no port to python3 > > available > > > > > > upgrading koji will help getting rid of some old python2 packages. > > > > > > dropping it, at least for now, seems to be the best way foreward here :/ > > > > Allright then, i'll just wait a week for allowing people to comment > > and then i'll file for koji removal. > > Since there were no further objections I've just filed a removal bug. thanks! I'm gonna go ahead and file an RM bug for the following pkgs too: yum createrepo python-lzma yum-metadata-parser mock yum-utils dtc-xen deltarpm they are a closed set (no external dependencies outside that set, tested via `dak rm -Rn list_of_pkgs`) of obsolete "redhat-related", python2, packages. Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#936806: koji: Python2 removal in sid/bullseye
On Thu, Jan 30, 2020 at 01:36:33AM -0500, Sandro Tosi wrote: > > > koji is keeping createrepo in the archive, which keeps python-lzma in > > > the archive. > > > > there's also mock, yum, rpm, deltarpm and yum-metadata-parser affected by > > this. > > yep i came across all of them starting from python-lzma -- do you know > what's the status of the "RedHat infrastructure" in debian? many (if > not all) of those tools are relatively old, not maintained (or just in > life support mode) and most of all, python2 with no port to python3 > available > > > > upgrading koji will help getting rid of some old python2 packages. > > > > dropping it, at least for now, seems to be the best way foreward here :/ > > Allright then, i'll just wait a week for allowing people to comment > and then i'll file for koji removal. Since there were no further objections I've just filed a removal bug. Cheers, Moritz
Bug#936806: koji: Python2 removal in sid/bullseye
* On 1/31/20 8:57 PM, Neal Gompa wrote: > As for yum and yum-utils, their replacements are dnf and > dnf-plugins-core (which have subpackages yum and yum-utils > respectively to act as legacy interfaces). > > My understanding is that Mihai Moldovan was working on this for Debian > for the past few months. Mihai worked with me upstream in the DNF > project to get things adapted nicely for Debian packaging in a > reasonable way. I've added Mihai to the thread to allow him to > participate. > > Mihai, would you care to chime in on your progress? Sure, thanks. I've made a list post introducing the packages at https://lists.debian.org/debian-devel/2019/09/msg00218.html , but sadly never received a response. This is hardly surprising, because the whole RPM stack in Debian is in a sorry state; essentially abandoned and unmaintained. :( The crucial "rpm" package has been up for adoption (c.f., https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923352 ) for almost a year and pretty much all others as well. I haven't made a formal ITP for my dnf packages because I'm a.) not a Debian Developer but merely a user and b.) do not *want* to maintain these packages within Debian. I wouldn't be a good maintainer in the first place since I often slack on user requests and I just flat out lack the temporal resources to do this properly. The dnf packages (and dependencies) I've packaged (and successfully use for building RPM packages via mock for newer Fedora versions!) are all Python-3-compatible. I'm not sure if I ever formally removed the Python-2-variants, but it's likely that I did, since no new packages providing Python 2 applications were allowed for quite some time. At least for dnf and mock I don't see any problem with going Python-3-only. yum sadly is Python-2-only, which could be problematic. Yum is still required to fetch packages on older distros like CentOS 6 and 7. Then again, dnf provides a yum-compat-mode, so Debian should just drop the abandoned yum package completely. Mihai signature.asc Description: OpenPGP digital signature
Bug#936806: koji: Python2 removal in sid/bullseye
I would honestly say it is probably fine to remove them. You could just use a Fedora container to get what you need if you are working on reproducible builds and need to provide some support. Though as Neal said it shouldn't be too hard to update everything, Fedora is well on the way to removing python2 and all of the tools have python3 support in the current releases. Dennis On Fri, Jan 31, 2020, 20:27 Sandro Tosi wrote: > On Fri, Jan 31, 2020 at 1:06 PM Marek Marczykowski-Górecki > wrote: > > > > On Thu, Jan 30, 2020 at 05:40:55PM -0800, Mike Miller wrote: > > > On Thu, Jan 30, 2020 at 01:36:33 -0500, Sandro Tosi wrote: > > > > yep i came across all of them starting from python-lzma -- do you > know > > > > what's the status of the "RedHat infrastructure" in debian? many (if > > > > not all) of those tools are relatively old, not maintained (or just > in > > > > life support mode) and most of all, python2 with no port to python3 > > > > available > > > > > > Yeah. I was responsible for some of these, but put them up for adoption > > > about a year ago. You've about captured the status, all rpm-related > > > packages in Debian are old, unmaintained, Python 2 only. Updating to > > > Python 3 ports of mock and koji need dnf, yum is abandonware. > > > > > > I've seen a couple threads about packaging dnf (likely not archived), > > > but so far no one has committed enough to file an ITP. > > > > > > There _is_ an ITP for createrepo-c (#912338), a C-only > reimplementation, > > > also a koji dependency, but looks like it may have stalled. > > > > Adding a bunch of people from Fedora, involved in reproducible builds > > before. And also adding Simon, who can help with some of this. > > > > A little context: Currently Fedora build tools packages in Debian are > > mostly unmaintained. This makes it difficult to have cross-distribution > > cooperation, for example Debian developers with a lot of experience in > > reproducible builds helping with reproducibility of Fedora packages. > > If I understand correctly, it is also one of the things needed to revive > > Fedora reproducibility testing on https://tests.reproducible-builds.org. > > > > This is about dnf, mock, koji and createrepo-c - and their dependencies > > (if any missing in Debian). > > > > Simon can do some packaging, but will need help with finding > > maintainers for them, and possibly also packaging some of the > > dependencies - if there are many of them missing. > > I sympathize with the willingness to have cross-distributions > collaboration for the reproducibility goal, but looking from a Debian > perspective (and in particular for the python2 removal effort), i cant > help but wonder what is the value of keeping this set of packages > (yum, koji, createrepo, mock, yum-utils; to name only the top-level > ones) in debian _at all_. > > should we just remove them (as in RM to ftp.d.o) and let them be > reintroduced, gradually and if interest arises again, at a later time? > This would be my preferred option, given it removes outdated tools > from Debian and allows progress for the py2removal, but i also want to > hear what y'all think > > Cheers, > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > Twitter: https://twitter.com/sandrotosi >
Bug#936806: koji: Python2 removal in sid/bullseye
On Fri, Jan 31, 2020 at 2:27 PM Sandro Tosi wrote: > > On Fri, Jan 31, 2020 at 1:06 PM Marek Marczykowski-Górecki > wrote: > > > > On Thu, Jan 30, 2020 at 05:40:55PM -0800, Mike Miller wrote: > > > On Thu, Jan 30, 2020 at 01:36:33 -0500, Sandro Tosi wrote: > > > > yep i came across all of them starting from python-lzma -- do you know > > > > what's the status of the "RedHat infrastructure" in debian? many (if > > > > not all) of those tools are relatively old, not maintained (or just in > > > > life support mode) and most of all, python2 with no port to python3 > > > > available > > > > > > Yeah. I was responsible for some of these, but put them up for adoption > > > about a year ago. You've about captured the status, all rpm-related > > > packages in Debian are old, unmaintained, Python 2 only. Updating to > > > Python 3 ports of mock and koji need dnf, yum is abandonware. > > > > > > I've seen a couple threads about packaging dnf (likely not archived), > > > but so far no one has committed enough to file an ITP. > > > > > > There _is_ an ITP for createrepo-c (#912338), a C-only reimplementation, > > > also a koji dependency, but looks like it may have stalled. > > > > Adding a bunch of people from Fedora, involved in reproducible builds > > before. And also adding Simon, who can help with some of this. > > > > A little context: Currently Fedora build tools packages in Debian are > > mostly unmaintained. This makes it difficult to have cross-distribution > > cooperation, for example Debian developers with a lot of experience in > > reproducible builds helping with reproducibility of Fedora packages. > > If I understand correctly, it is also one of the things needed to revive > > Fedora reproducibility testing on https://tests.reproducible-builds.org. > > > > This is about dnf, mock, koji and createrepo-c - and their dependencies > > (if any missing in Debian). > > > > Simon can do some packaging, but will need help with finding > > maintainers for them, and possibly also packaging some of the > > dependencies - if there are many of them missing. > > I sympathize with the willingness to have cross-distributions > collaboration for the reproducibility goal, but looking from a Debian > perspective (and in particular for the python2 removal effort), i cant > help but wonder what is the value of keeping this set of packages > (yum, koji, createrepo, mock, yum-utils; to name only the top-level > ones) in debian _at all_. > > should we just remove them (as in RM to ftp.d.o) and let them be > reintroduced, gradually and if interest arises again, at a later time? > This would be my preferred option, given it removes outdated tools > from Debian and allows progress for the py2removal, but i also want to > hear what y'all think > Hello, It should generally be quite easy to switch everything over to Python 3 equivalents. Koji and Mock have supported Python 3 for a few years now. And of course, createrepo_c does not require Python, though does provide Python 3 bindings. In Fedora, Mageia, and openSUSE, createrepo_c has fully replaced createrepo (Obsoletes + Provides, or Replaces + Provides in Debian parlance). As for yum and yum-utils, their replacements are dnf and dnf-plugins-core (which have subpackages yum and yum-utils respectively to act as legacy interfaces). My understanding is that Mihai Moldovan was working on this for Debian for the past few months. Mihai worked with me upstream in the DNF project to get things adapted nicely for Debian packaging in a reasonable way. I've added Mihai to the thread to allow him to participate. Mihai, would you care to chime in on your progress? -- Neal Gompa (FAS: ngompa)
Bug#936806: koji: Python2 removal in sid/bullseye
On Fri, Jan 31, 2020 at 1:06 PM Marek Marczykowski-Górecki wrote: > > On Thu, Jan 30, 2020 at 05:40:55PM -0800, Mike Miller wrote: > > On Thu, Jan 30, 2020 at 01:36:33 -0500, Sandro Tosi wrote: > > > yep i came across all of them starting from python-lzma -- do you know > > > what's the status of the "RedHat infrastructure" in debian? many (if > > > not all) of those tools are relatively old, not maintained (or just in > > > life support mode) and most of all, python2 with no port to python3 > > > available > > > > Yeah. I was responsible for some of these, but put them up for adoption > > about a year ago. You've about captured the status, all rpm-related > > packages in Debian are old, unmaintained, Python 2 only. Updating to > > Python 3 ports of mock and koji need dnf, yum is abandonware. > > > > I've seen a couple threads about packaging dnf (likely not archived), > > but so far no one has committed enough to file an ITP. > > > > There _is_ an ITP for createrepo-c (#912338), a C-only reimplementation, > > also a koji dependency, but looks like it may have stalled. > > Adding a bunch of people from Fedora, involved in reproducible builds > before. And also adding Simon, who can help with some of this. > > A little context: Currently Fedora build tools packages in Debian are > mostly unmaintained. This makes it difficult to have cross-distribution > cooperation, for example Debian developers with a lot of experience in > reproducible builds helping with reproducibility of Fedora packages. > If I understand correctly, it is also one of the things needed to revive > Fedora reproducibility testing on https://tests.reproducible-builds.org. > > This is about dnf, mock, koji and createrepo-c - and their dependencies > (if any missing in Debian). > > Simon can do some packaging, but will need help with finding > maintainers for them, and possibly also packaging some of the > dependencies - if there are many of them missing. I sympathize with the willingness to have cross-distributions collaboration for the reproducibility goal, but looking from a Debian perspective (and in particular for the python2 removal effort), i cant help but wonder what is the value of keeping this set of packages (yum, koji, createrepo, mock, yum-utils; to name only the top-level ones) in debian _at all_. should we just remove them (as in RM to ftp.d.o) and let them be reintroduced, gradually and if interest arises again, at a later time? This would be my preferred option, given it removes outdated tools from Debian and allows progress for the py2removal, but i also want to hear what y'all think Cheers, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#936806: koji: Python2 removal in sid/bullseye
On Thu, Jan 30, 2020 at 05:40:55PM -0800, Mike Miller wrote: > On Thu, Jan 30, 2020 at 01:36:33 -0500, Sandro Tosi wrote: > > yep i came across all of them starting from python-lzma -- do you know > > what's the status of the "RedHat infrastructure" in debian? many (if > > not all) of those tools are relatively old, not maintained (or just in > > life support mode) and most of all, python2 with no port to python3 > > available > > Yeah. I was responsible for some of these, but put them up for adoption > about a year ago. You've about captured the status, all rpm-related > packages in Debian are old, unmaintained, Python 2 only. Updating to > Python 3 ports of mock and koji need dnf, yum is abandonware. > > I've seen a couple threads about packaging dnf (likely not archived), > but so far no one has committed enough to file an ITP. > > There _is_ an ITP for createrepo-c (#912338), a C-only reimplementation, > also a koji dependency, but looks like it may have stalled. Adding a bunch of people from Fedora, involved in reproducible builds before. And also adding Simon, who can help with some of this. A little context: Currently Fedora build tools packages in Debian are mostly unmaintained. This makes it difficult to have cross-distribution cooperation, for example Debian developers with a lot of experience in reproducible builds helping with reproducibility of Fedora packages. If I understand correctly, it is also one of the things needed to revive Fedora reproducibility testing on https://tests.reproducible-builds.org. This is about dnf, mock, koji and createrepo-c - and their dependencies (if any missing in Debian). Simon can do some packaging, but will need help with finding maintainers for them, and possibly also packaging some of the dependencies - if there are many of them missing. -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? signature.asc Description: PGP signature
Bug#936806: koji: Python2 removal in sid/bullseye
On Thu, Jan 30, 2020 at 01:36:33 -0500, Sandro Tosi wrote: > yep i came across all of them starting from python-lzma -- do you know > what's the status of the "RedHat infrastructure" in debian? many (if > not all) of those tools are relatively old, not maintained (or just in > life support mode) and most of all, python2 with no port to python3 > available Yeah. I was responsible for some of these, but put them up for adoption about a year ago. You've about captured the status, all rpm-related packages in Debian are old, unmaintained, Python 2 only. Updating to Python 3 ports of mock and koji need dnf, yum is abandonware. I've seen a couple threads about packaging dnf (likely not archived), but so far no one has committed enough to file an ITP. There _is_ an ITP for createrepo-c (#912338), a C-only reimplementation, also a koji dependency, but looks like it may have stalled. -- mike signature.asc Description: PGP signature
Bug#936806: koji: Python2 removal in sid/bullseye
On Thu, Jan 30, 2020 at 09:55:58AM -0500, Sandro Tosi wrote: > i was mostly querying the status of it, i cant even find an ITP for dnf. exactly. > i was talking about removing koji entirely from debian, an RM to > ftp.d.o; is that not what you mean? right, this is also in order. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#936806: koji: Python2 removal in sid/bullseye
On Thu, Jan 30, 2020 at 4:12 AM Holger Levsen wrote: > > On Thu, Jan 30, 2020 at 01:36:33AM -0500, Sandro Tosi wrote: > > yep i came across all of them starting from python-lzma -- do you know > > what's the status of the "RedHat infrastructure" in debian? many (if > > not all) of those tools are relatively old, not maintained (or just in > > life support mode) and most of all, python2 with no port to python3 > > available > > as said: dnf needs to be packaged first and foremost. (dnf is the yum > replacement.) i was mostly querying the status of it, i cant even find an ITP for dnf. > > Allright then, i'll just wait a week for allowing people to comment > > and then i'll file for koji removal. > > RM bugs to remove koji from stable and oldstable have already been > filed, and it's not in bullseye. i was talking about removing koji entirely from debian, an RM to ftp.d.o; is that not what you mean? -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#936806: koji: Python2 removal in sid/bullseye
On Thu, Jan 30, 2020 at 01:36:33AM -0500, Sandro Tosi wrote: > yep i came across all of them starting from python-lzma -- do you know > what's the status of the "RedHat infrastructure" in debian? many (if > not all) of those tools are relatively old, not maintained (or just in > life support mode) and most of all, python2 with no port to python3 > available as said: dnf needs to be packaged first and foremost. (dnf is the yum replacement.) > Allright then, i'll just wait a week for allowing people to comment > and then i'll file for koji removal. RM bugs to remove koji from stable and oldstable have already been filed, and it's not in bullseye. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#936806: koji: Python2 removal in sid/bullseye
> > koji is keeping createrepo in the archive, which keeps python-lzma in > > the archive. > > there's also mock, yum, rpm, deltarpm and yum-metadata-parser affected by > this. yep i came across all of them starting from python-lzma -- do you know what's the status of the "RedHat infrastructure" in debian? many (if not all) of those tools are relatively old, not maintained (or just in life support mode) and most of all, python2 with no port to python3 available > > upgrading koji will help getting rid of some old python2 packages. > > dropping it, at least for now, seems to be the best way foreward here :/ Allright then, i'll just wait a week for allowing people to comment and then i'll file for koji removal. cheers, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#936806: koji: Python2 removal in sid/bullseye
On Tue, Jan 28, 2020 at 11:21:46PM -0500, Sandro Tosi wrote: > ok, whos of the maintainers is working on packaging 1.18? i see > there's even 1.20 released. noone, I believe. Also because it needs dnf, which is not packaged for Debian at all. I was just going to remove myself from uploaders in git and pushed my work-in-progress branch wip-python3. and then i also pushed it into the master branch. sigh > koji is keeping createrepo in the archive, which keeps python-lzma in > the archive. there's also mock, yum, rpm, deltarpm and yum-metadata-parser affected by this. > upgrading koji will help getting rid of some old python2 packages. dropping it, at least for now, seems to be the best way foreward here :/ -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#936806: koji: Python2 removal in sid/bullseye
Control: tags -1 +fixed-upstream On Fri, 30 Aug 2019 09:57:23 + Holger Levsen wrote: > On Fri, Aug 30, 2019 at 07:22:19AM +, Matthias Klose wrote: > > Package: src:koji > > Version: 1.16.2-1 > [...] > > Your package either build-depends, depends on Python2, or uses Python2 > > in the autopkg tests. Please stop using Python2, and fix this issue > > by one of the following actions. > > koji 1.18 has been ported to python 3 and needs to be packaged to solve > this. ok, whos of the maintainers is working on packaging 1.18? i see there's even 1.20 released. koji is keeping createrepo in the archive, which keeps python-lzma in the archive. upgrading koji will help getting rid of some old python2 packages. Thanks, Sandro
Bug#936806: koji: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:22:19AM +, Matthias Klose wrote: > Package: src:koji > Version: 1.16.2-1 [...] > Your package either build-depends, depends on Python2, or uses Python2 > in the autopkg tests. Please stop using Python2, and fix this issue > by one of the following actions. koji 1.18 has been ported to python 3 and needs to be packaged to solve this. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
