Dear Jean-Christophe, jean-christophe manciot wrote: > > 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.
I'm not. > The whole point of this bug report is that *building* > python-apt from the sources downloaded from https://packages.debian. > org/source/sid/python-apt is that the binary python3-apt is incompatible > with python3 >= 3.6. This depends a lot on which Debian release you build the package and what version /usr/bin/python3 has on that system as those versioned dependencies are calculated at build time. So if you build that package on Debian Stretch where python3 is 3.5.3, the above is true, expected and wanted: the package has a dependency on python3 << 3.6. And if you build it on Debian Unstable now (where python3 is currently 3.6.4), it's expected and wanted that the package has a dependency on python3 << 3.7. Short said: It's built to work with the currently installed version of python3 and _no_ other (earlier or later) version. That's why Debian rebuilds such packages when a new python3 minor version enters Debian Unstable by doing binNMUs. So there is no bug at all and everything works as expected and wanted. > If you try to built the packages from those sources, you'll discover I don't need to discover that. I can tell it by mind and it's expected. > that the version is *1.4.0~beta3*, as indicated in debian/changelog. Of course! Because it's no binNMU if you just build it from source without the appropriate commandline options for a binNMU. Please first read * https://wiki.debian.org/binNMU * https://www.debian.org/doc/manuals/developers-reference/pkgs.html#binary-only-nmu, * the dpkg-buildpackage(1) and dpkg-genchanges(1) man pages on the options -B, -C, -e (both) -V and -D (dpkg-genchanges only) * the deb-substvars(5) man page section on the topic "binary:Version" * and the dh_python3(1) man page before writing any further replies to this thread. Thanks. > > No. Nowhere in Debian you will find a binary package without an > > according source package. Period. > > It depends on what you call "sources". I talked about "source packages" (not "sources") which is a very precise term in Debian context: A Debian source package means a .dsc file including all files referenced in there (usually a .orig.tar.gz and a .debian.tar.xz file). > If you put the *debian* folder aside from your definition, then we > agree. The we disagree, because a debian folder of course is part of every Debian source package. 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
