Package: src:fpc Severity: normal fpc provides a lot of packages, both in versioned and unversioned variants. All versioned packages Break the unversioned fpc package like fpc-$foo-3.0.4 Breaks fpc (<= 3.0.4).
This means that while the packages are versioned, they are not co-installable, rendering the versioning useless. This is causing significant trouble for the apt resolver, as it tries to decide what to do with the upgrade. Upgrading fpc means removing a lot of packages and installing a lot of new ones, and it's not happy about it. We just noticed an upgrade failure in Ubuntu, because the solver was incapable of upgrading fpc. It kept jumping back and forth between upgrading fpc and keeping it and eventually gave up. I have not tested it, but I'd expect a switch to unversioned packages to solve the issues. I'll try to setup a test case, and report back with the results. -- System Information: Debian Release: buster/sid APT prefers cosmic APT policy: (500, 'cosmic'), (100, 'cosmic-proposed') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-6-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fpc depends on: pn fp-docs-3.0.4 <none> pn fp-utils-3.0.4 <none> pn fpc-3.0.4 <none> fpc recommends no packages. fpc suggests no packages. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
