Dear Jean-Christophe, jean-christophe manciot wrote: > python3-apt depends on python3 (<< 3.6) when sid python3 version > is... 3.6.4-1. > There is another release - 1.4.0~beta3+b1 - which depends on python3 (<< > 3.7) and can be downloaded but the corresponding sources are nowhere to be > found on https://packages.debian.org/source/sid/python-apt.
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 jean-christophe manciot wrote: > > that's a binNMU. closing. binNMU means Binary Non-Maintainer Upload. A binNMU is nothing else than a rebuild of the very same source package just under newer build-dependencies (here namely a newer minor python3 version). But since the resulting binary package(s) are different from previously build ones, they need to have a different version number than the initially built ones. The "+b<n>" suffix is the convention for such rebuilt packages and Debian tools usually know that this means that the according source apackage has a version with the e.g. +b1 removed. But even if they don't know that, they can (as you can, too) just ask apt-cache: → apt-cache show python3-apt Package: python3-apt Source: python-apt (1.4.0~beta3) Version: 1.4.0~beta3+b1 […] Please note the line starting with "Source:" which includes the exact version number of the source package the binary package was built from. > OK, so no sources for the release 1.4.0~beta3+b1. No. Nowhere in Debian you will find a binary package without an according source package. Period. > I assume that only debian/control & debian/changelog files have been > modified accordingly. No. Not even that. Have you ever looked into the directory /usr/share/doc/python3-apt/? There is just one (generated) file added compared to the 1.4.0~beta3 binary package: changelog.amd64.gz — and it says: python-apt (1.4.0~beta3+b1) sid; urgency=low, binary-only=yes * Binary-only non-maintainer upload for amd64; no source changes. * Rebuild with python3.6 as a supported python3. -- amd64 Build Daemon (binet) <buildd-bi...@buildd.debian.org> Fri, 30 Jun 2017 06:15:05 +0000 > Another issue is that the downloaded package name is > incorrect: python3-apt_1.4.0_beta3+b1_amd64.deb should be > called python3-apt_1.4.0~beta3+b1_amd64.deb. That might be an issue of your downloader. E.g. wget saves it with a correct file name: → wget 'http://ftp.ch.debian.org/debian/pool/main/p/python-apt/python3-apt_1.4.0~beta3+b1_amd64.deb' --2018-01-27 17:35:51-- http://ftp.ch.debian.org/debian/pool/main/p/python-apt/python3-apt_1.4.0~beta3+b1_amd64.deb Resolving ftp.ch.debian.org (ftp.ch.debian.org)... 129.132.53.171, 2001:67c:10ec:3dd1::42 Connecting to ftp.ch.debian.org (ftp.ch.debian.org)|129.132.53.171|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 171302 (167K) [application/x-debian-package] Saving to: 'python3-apt_1.4.0~beta3+b1_amd64.deb' python3-apt_1.4.0~beta3+b1 100%[=====================================>] 167.29K --.-KB/s in 0.004s 2018-01-27 17:35:51 (41.9 MB/s) - 'python3-apt_1.4.0~beta3+b1_amd64.deb' saved [171302/171302] Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
