Bug#932258: console-setup-freebsd: missing dependency
Hi!
[ I'm not sure this bug closure is entirely correct? See below. ]
On Wed, 2019-07-17 at 13:25:50 +0100, James Clarke wrote:
> On 17 Jul 2019, at 10:55, Holger Wansing <hwansing@mailbox.org> wrote:
> > Héctor Orón Martínez <zumbi@debian.org> (2019-07-17):
> > > Package: console-setup-freebsd
> > > Version: 1.191
> > > Severity: grave
> > > console-setup-freebsd has a dependency on vidcontrol, which is not
> > > part of buster|bullseye|unstable, and causes the package to be
> > > uninstallable.
> > The same counts for kbdcontrol, also not existing in all suites.
> vidcontrol, and the rest of src:freebsd-utils, is available in unreleased,
> since the source package only builds for kfreebsd-amd64 and kfreebsd-i386.
> Avoiding this would require either getting the source package to build on Linux
> architectures, or building at least one arch:all package, neither of which seem
> to have much point to them. As an architecture on Debian Ports, it is expected
> that you also have the "unreleased" suite enabled, as is clearly documented on
> the main site[1]. This is especially important on kFreeBSD, since
> bin:freebsd-utils is Essential, containing many of the core utilities required
> for a functioning system. All ports buildds should have unreleased available,
> and debian-installer learnt over 2 years ago to include unreleased when
> downloading udebs. Thus, I consider this not a bug; as much as we would like it
> to not be, as far as Debian Ports goes, unreleased is a necessary addition to
> unstable, with cases like these stemming from the fact that ftp-master does not
> allow sources to exist that don't build packages for any of its architectures.
I'm not sure the report was noticed on a kFreeBSD system (and due to
the unreleased confusion), but otherwise this seems like a problem with
console-setup-freebsd being arch:all and depending on kFreeBSD-specific
packages which will not be available elsewhere, in the same way
console-setup-linux is an arch:all depending on Linux-specific packages.
The solution to the latter problem is to make these packages
Architecture kfreebsd-any and linux-any respectively, because even if
they are written in scripting languages they are not arch-independent.
Thanks,
Guillem
Reply to: