On Wed, 2018-10-17 at 18:57 +0200, Holger Wansing wrote:
> Hi,
>
> Ben Hutchings <ben@decadent.org.uk> wrote:
> > On Tue, 2018-10-16 at 19:43 +0200, Holger Wansing wrote:
> > > Package: console-setup
> > > Severity: wishlist
> > >
> > >
> > > Holger Wansing <linux@wansing-online.de> wrote:
> > > > Holger Wansing <hwansing@mailbox.org> wrote:
> > > > > I noticed that the latest upload of console-setup fails to
> > > > > migrate to testing.
> > > > > It claims being "uninstallable on amd64", while
> > > > > https://buildd.debian.org/status/fetch.php?pkg=console-setup&arch=all&ver=1.185&stamp=1534275854&raw=0
> > > > > says that the build was successful.
> > > > >
> > > > > How can I find out what is wrong here?
> > > >
> > > > Hmm, at the 15. day it migrated to testing now, while I cannot see that
> > > > something has changed.
> > >
> > > console-setup needs several attempts everytime, 'til it migrates.
> > >
> > > The point is, that autopkgtest claims about unmet dependencies for all
> > > archs (packages vidcontrol and kbdcontrol being unavailable).
> > > However, these packages are only existing for kfreebsd.
> > >
> > > Why does console-setup depend on it on all archs?
> > > Can the control file be changed for console-setup-freebsd as below?
> >
> > No. dpkg-gencontrol handles architecture qualification in Depends
> > (etc.) at build time, for architecture-dependent binary packages. You
> > must not use them in architecture-independent binary packages.
>
> Ok. Anything else that can be done about this?
> Maybe change
>
> - Architecture: all
> + Architecture: kfreebsd-amd64 kfreebsd-i386
>
> for console-setup-freebsd?
[...]
That seems reasonable as it's not a very big package.
Ben.
--
Ben Hutchings
Man invented language to satisfy his deep need to complain.
- Lily Tomlin
Attachment:
signature.asc
Description: This is a digitally signed message part