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-g
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
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
epig
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 file
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
Desc
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
On Mon, Aug 26, 2019 at 11:18:33AM +0200, Raphael Hertzog wrote:
> 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
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 i
8 matches
Mail list logo