Package: gnat-4.6 Followup-For: Bug #743833 If I understand well, right after an upload of a NEW source version: - gnat-x.y-base NEW, being Arch:all, immediately replaces OLD in unstable - gnat-x.y NEW, being Arch: any, waits to be built. Meanwhile: - gnat-x.y OLD remains in unstable - gnat-x.y OLD Depends: gnat-x.y-base (= OLD) so is uninstallable - gnat-x.y source NEW Build-Depends: gnat-x.y so is BD-Uninstallable
According to the build logs, the build daemons seem to cleverly select an older version after a few days and eventually manage to bootstrap. However - gnat-x.y users cannot upgrade it for a few days - this does not solve the potential +b1 problem Relaxing the dependency of the 10 other binary packages generated by the same source to gnat-x.y-base (>= x.y-n) instead of gnat-x.y-base (= x.y-n) is not an option, because gnat-x.y-base provides changelog.Debian which must be up-to-date. Duplication of the files across architectures seems necessary, and we should revert gnat-x.y-base to "Arch: any". Why not drop the gnat-x.y-base package and put its contents into libgnat-x.y instead? All 10 packages seem to depend on the same binary version of both gnat-x.y-base and libgnat-x.y, so the only practical effect would be to simplify the internal dependencies. For the record, gnat-x.y-base contains: - a symbolic link: /usr/share/doc/gcc-x.y-base/Ada -> /u/s/d/gnat-x.y-base - documentation in in /u/s/d/gnat-x.y-base/: changelog.Debian.gz 130 Kb copyright 26 Kb README.Debian 1.5 Kb README.gnat 0.9 Kb README.maintainers.gz 2.7 Kb TODO.Debian 1.7 Kb changelog.gz 3.2 Kb test-summary.gz 5.3 Kb -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
