re: git-buildpackage to be autoremoved due to python2 transition
Quoting peter green (2020-02-27 22:54:19) > > Relevant packages and bugs: > > 943107 git-buildpackage: Python2 removal in sid/bullseye > This bug is not marked as rc. > > Nevertheless I believe that this bug report is in-fact a false positive. From > what I can tell git-buildpackage, even in buster, does not (build-)depend on > python 2 or any python 2 modules. correct, but it does build-depend on packages that require python2: rpm I was recently in a similar situation where I thought I had a false positive for one of my package so I filed this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952523 You can always check whether you got a false positive or not by investing the dependency relationship yourself. In this case: dose-ceve -T grml --deb-builds-from --deb-native-arch=amd64 debsrc://Sources deb://Packages > /tmp/graph.xml botch-graph-shortest-path /tmp/graph.xml /tmp/out.xml --source realpackage:src:git-buildpackage --target realpackage:src:python2.7 Thanks! cheers, josch signature.asc Description: signature
re: git-buildpackage to be autoremoved due to python2 transition
Relevant packages and bugs: 943107 git-buildpackage: Python2 removal in sid/bullseye This bug is not marked as rc. Nevertheless I believe that this bug report is in-fact a false positive. From what I can tell git-buildpackage, even in buster, does not (build-)depend on python 2 or any python 2 modules. It does build-depend on python-pydoctor, but according to a recently entry in the pydoctor changelog that package "is a Python application and not used as a module" It would make sense to change the build-dependency to pydoctor in the next upload, but it's probablly not worth making an upload just for that change. 937132 nevow: Python2 removal in sid/bullseye Depended on by pydoctor in testing, but not in unstable. Should stop being a problem for git-buildpackage when pydoctor migrates. 938622 tahoe-lafs: Python2 removal in sid/bullseye Listed as a "blocker" of the above bug but not currently in testing. Personally I advocate ignoring "blockers" that are not in testing, but I'm not sure if consensus has been reached on that. Bugs which you may notice which are now not so relevant any more because they have been fixed in sid (but not yet migrated): 950216 [git-buildpackage] missing xsltproc autopkg test dependency Fixed in sid; migration blocked by FTBFS due to pydoctor breakage (#949232). When pydoctor has migrated, reattempting build (eg by re-upload) should fix this. Builds happen in unstable, so there is no need to wait for pydoctor to migrate to testing before retrying the build. I just requested a retry and the package built succesfully. I'd expect it to migrate as soon as dak and britney process the binary. 949232/948831 [pydoctor] needs to depend on cachecontrol 952546 [pydoctor] d/copyright & DFSG issues 937421 [pydoctor] Python2 removal in sid/bullseye Should hopefully be fixed in a few days when pydoctor migrates to testing, i'm not seeing any obvious blockers for that right now.
Re: git-buildpackage to be autoremoved due to python2 transition
On Wed, Feb 26, 2020 at 12:14:08PM +, Ian Jackson wrote: > I looked again and I was looking at an old version. Sorry for the > noise. I still think we have problems with these > 937132 nevow: Python2 removal in sid/bullseye > 938622 tahoe-lafs: Python2 removal in sid/bullseye > which I think are brought in by pydoctor... As you can see with reverse-depends or dak, there is no packages depending on these two (after pydoctor was ported, I guess). -- WBR, wRAR signature.asc Description: PGP signature
Re: git-buildpackage to be autoremoved due to python2 transition
Andrey Rahmatullin writes ("Re: git-buildpackage to be autoremoved due to
python2 transition"):
> Yes, and as far as I can see after pydoctor migrates the only problem with
> gbp will be python-rpm in debian/tests/control, which is probably
> unneeded.
Oh.
> > the py2 rot seems wider including in gbp itself.
>
> Where exactly?
I looked again and I was looking at an old version. Sorry for the
noise. I still think we have problems with these
937132 nevow: Python2 removal in sid/bullseye
938622 tahoe-lafs: Python2 removal in sid/bullseye
which I think are brought in by pydoctor...
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Re: git-buildpackage to be autoremoved due to python2 transition
On Wed, Feb 26, 2020 at 11:28:03AM +, Ian Jackson wrote: > FYI. The widespread impact of this not so apparent because > git-buildpackage is typically used ad-hoc by maintainers, rather than > via (Build)-Depends. > > Relevant packages and bugs: > 943107 git-buildpackage: Python2 removal in sid/bullseye > 937132 nevow: Python2 removal in sid/bullseye > 938622 tahoe-lafs: Python2 removal in sid/bullseye > > Bugs which you may notice which are now not so relevant any more > because they have been fixed in sid (but not yet migrated): > 950216 [git-buildpackage] missing xsltproc autopkg test dependency > Fixed in sid; migration blocked by FTBFS due to pydoctor > breakage (#949232). When pydoctor has migrated, reattempting > build (eg by re-upload) should fix this. > 949232/948831 [pydoctor] needs to depend on cachecontrol > 952546 [pydoctor] d/copyright & DFSG issues > 937421 [pydoctor] Python2 removal in sid/bullseye Yes, and as far as I can see after pydoctor migrates the only problem with gbp will be python-rpm in debian/tests/control, which is probably unneeded. > the py2 rot seems wider including in gbp itself. Where exactly? -- WBR, wRAR signature.asc Description: PGP signature
