@Axel Beckert It appears that some debian files have been modified in the meantime in the sources available at https://packages.debian.org/source/sid/python-apt and now we can build python-apt to generate the correct dependencies for python3-apt binary: python3 (<< 3.7), python3 (>= 3.6~),
On Mon, Jan 29, 2018 at 8:45 PM, jean-christophe manciot < actionmysti...@gmail.com> wrote: > @Axel Beckert > > >> That's wrong. The corresponding sources _are_ shown on >> https://packages.debian.org/source/sid/python-apt. It's the files >> called python-apt_1.4.0~beta3.dsc and python-apt_1.4.0~beta3.tar.xz >> >> > No, you're confused. The whole point of this bug report is that *building* > python-apt from the sources downloaded from https://packages.debian.o > rg/source/sid/python-apt is that the binary python3-apt is incompatible > with python3 >= 3.6. > If you try to built the packages from those sources, you'll discover that > the version is *1.4.0~beta3*, as indicated in debian/changelog. > > No. Nowhere in Debian you will find a binary package without an >> according source package. Period. >> > > It depends on what you call "sources". If you put the *debian* folder > aside from your definition, then we agree. > > That might be an issue of your downloader. > > > You're right here. I downloaded the python-apt binaries with Google > chrome 64.0.3282.119 (Official Build) (64-bit) on Linux. > I have just reported that issue to Google. > > -- > Jean-Christophe Manciot > -- Jean-Christophe
