Bug#935841: RM: python-googlecloudapis -- RoM; RC-buggy; uninstallable
Package: ftp.debian.org Severity: normal User: debian-python@lists.debian.org Usertag: py2removal Depends and build-depends on python3-protorpc-standalone which is not installable on Python 3.7, and on python-oauth2client which is dropped from Debian. Reverse deps checked with dak rm -Rn python-googlecloudapis -- WBR, wRAR signature.asc Description: PGP signature
Bug#935840: RM: python-protorpc-standalone -- RoQA; orphaned; RC-buggy; incompatible with Python 3.7
Package: ftp.debian.org Severity: normal User: debian-python@lists.debian.org Usertag: py2removal From the O bug (#906195): "If it is still RC buggy at the time of the freeze, I'll ask for its removal from Debian." The only reverse dep is python-googlecloudapis which has other problems and isn't installable because of python3-protorpc-standalone. RM for it will be filed shortly. Reverse deps checked with dak rm -Rn python-protorpc-standalone python-googlecloudapis -- WBR, wRAR signature.asc Description: PGP signature
Bug#935838: RM: python-visual -- RoQA; orphaned; RC-buggy; broken
Package: ftp.debian.org Severity: normal User: debian-python@lists.debian.org Usertag: py2removal Control: block -1 by 935073 Control: block -1 by 911171 According to #884616 (RC bug on python-visual) and #911171 (RC bug on epigrass) it's broken and should not be used. Its only reverse dep is epigrass which was requested to be removed (#935073), though that discussion hints it may be ported to Py3 before being removed, which should drop this dep anyway. -- WBR, wRAR signature.asc Description: PGP signature
Bug#935837: RM: pygdchart2 -- RoQA; orphaned; ancient; dead upstream; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-python@lists.debian.org Usertag: py2removal http://www.nullcube.com/software/pygdchart2.html (from the O bug) is dead. No new releases in Debian since initial packaging in 2005. The only reverse dep is rebuildd for which an RM bug was just filed. Reverse deps checked with dak rm -Rn rebuildd pygdchart2 -- WBR, wRAR signature.asc Description: PGP signature
Bug#935836: RM: rebuildd -- RoQA; orphaned; low popcon; dead upstream; Python 2-only
Package: ftp.debian.org Severity: normal User: debian-python@lists.debian.org Usertag: py2removal Native package by a retired DD. Homepage gives 404. Last release in 2012. Popcon 8. Depends on several py2 packages. Reverse deps checked with dak rm -Rnb rebuildd -- WBR, wRAR signature.asc Description: PGP signature
Bug#935835: RM: htmlgen -- RoQA; orphaned; RC-buggy; ancient; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-python@lists.debian.org Usertag: py2removal Source in Debian was first packaged in 1999. Depends on cruft python-imaging. Reverse deps checked with dak rm -Rnb python-htmlgen -- WBR, wRAR signature.asc Description: PGP signature
Re: Git, gbp blues
On Sun, 25 Aug 2019, Dmitry Shachnev wrote: > The correct procedure is running “gbp pq import” *before* importing a new > tarball. Then after importing you do “gbp pq rebase”. > > Sometimes I myself forget to run “gbp pq import”. In this case I do the > following: Instead you should use "gbp pq import --time-machine=X" where X is the number of commits that you accept to go backwards to try to find a point where the patch series can be applied. Then you are on your branch, ready for a rebase... Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/ signature.asc Description: PGP signature
Re: Git, gbp blues
On Mon, Aug 26, 2019 at 08:20:13AM +0200, Guðjón Guðjónsson wrote: > > The correct procedure is running “gbp pq import” *before* importing a new > > tarball. Then after importing you do “gbp pq rebase”. > In fact I did do that. Then you would get an error message when trying to do that second time. > > > But fixing the patches with quilt before importing them the second > > > time seems to fix all my problems. > > If it does not break the patches metadata then it also works. > But what other way is possible? gbp pq rebase. Seriously. > The patch queue must apply cleanly in gbp pq import And it will, of course. > in general you can assume it doesn't with new upstream and > old patch queue. This is not something you can or should do. > I still don't understand how to edit the patches the correct way > after a new upstream release. gbp pq rebase, as the wiki page tells you. -- WBR, wRAR signature.asc Description: PGP signature
Re: Git, gbp blues
Hi Dmitry and Anrdrey On Sun, Aug 25, 2019 at 10:19 PM Dmitry Shachnev wrote: > The correct procedure is running “gbp pq import” *before* importing a new > tarball. Then after importing you do “gbp pq rebase”. In fact I did do that. > > Sometimes I myself forget to run “gbp pq import”. In this case I do the > following: > > - Remember the current commit SHA1; > - git reset --hard origin/debian/master; # or to previous tag > - gbp pq import; # this is the needed step > - git checkout debian/master; # back to debian/master branch > - git merge COMMIT_ID; # that you remembered before Thanks, this is useful for me. > > > But fixing the patches with quilt before importing them the second > > time seems to fix all my problems. > If it does not break the patches metadata then it also works. But what other way is possible? The patch queue must apply cleanly in gbp pq import and in general you can assume it doesn't with new upstream and old patch queue. I still don't understand how to edit the patches the correct way after a new upstream release. Regards Gudjon Ps. The package qscintilla2 is pushed, still a few lintian warnings to fix.
