Re: Bug#932258: console-setup-freebsd: missing dependency

[Guillem Jover]

On Wed, 2019-07-17 at 18:06:00 +0300, Anton Zinoviev wrote:
> On Wed, Jul 17, 2019 at 04:15:51PM +0200, Guillem Jover wrote:
> > 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.
> 
> Why is it a problem to have an arch:all package which is installable 
> only on some architectures (due to missing dependencies)?

Because that's generally confusing for users, as they might not know
off-hand whether the unsatisfiable problem is due to a bug or it being
intended that way (even though it could be made very clear in the
Description). It also triggers all kind of alarms on automatic
dependency satisfiability checkers, which then need to be ignored
(like apparently this being the cause for thus bug report :). And
I guess in the metadata sense it seems wrong, as even though the
contents do not change across different architectures (so it has one
of the facets of an arch:all package) it is still not an archecture
indepdenent package (one of the other facets of an arch:all package).

Thanks,
Guillem

Re: Bug#932258: console-setup-freebsd: missing dependency

[Héctor Orón Martínez]

Hello,

Missatge de Anton Zinoviev  del dia dc., 17 de jul.
2019 a les 17:06:

> On Wed, Jul 17, 2019 at 04:15:51PM +0200, Guillem Jover wrote:
> >
> > 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.
>
> Why is it a problem to have an arch:all package which is installable
> only on some architectures (due to missing dependencies)?

I noticed the issue while doing a repository consistency check with
main, contrib and non-free components for amd64 architecture on the
buster suite. Tools like wanna-build also do similar checks for
building packages, however this has not been an issue for the
wanna-build checks in the past.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Re: Bug#932258: console-setup-freebsd: missing dependency

[Anton Zinoviev]

On Wed, Jul 17, 2019 at 04:15:51PM +0200, Guillem Jover wrote:
> 
> 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.

Why is it a problem to have an arch:all package which is installable 
only on some architectures (due to missing dependencies)?

Anton Zinoviev

Re: Bug#932258: console-setup-freebsd: missing dependency

[Guillem Jover]

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  wrote:
> > Héctor Orón Martínez  (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

Re: Bug#932258: console-setup-freebsd: missing dependency

[Hector Oron]

Hello,

> Missatge de James Clarke  del dia dc., 17 de jul.
> 2019 a les 8:25:

> > 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.
>
> Oh! I did not check unreleased, only `amd64` architecture and I saw
> that dependency loop was not closed. Thanks very much for the nice
> explanation and background.

Along the lines,
https://packages.debian.org/unstable/console-setup-freebsd site should
probably check on the unreleased suite.

Best regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Re: Bug#932258: console-setup-freebsd: missing dependency

[Hector Oron]

Hello,

Missatge de James Clarke  del dia dc., 17 de jul.
2019 a les 8:25:

> 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.

Oh! I did not check unreleased, only `amd64` architecture and I saw
that dependency loop was not closed. Thanks very much for the nice
explanation and background.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Re: Bug#932258: console-setup-freebsd: missing dependency

[James Clarke]

On 17 Jul 2019, at 10:55, Holger Wansing  wrote:
> 
> Hi,
> 
> Cyril Brulebois  wrote:
>> Héctor Orón Martínez  (2019-07-17):
>>> Package: console-setup-freebsd
>>> Version: 1.191
>>> Severity: grave
>>> 
>>> 
>>> Dear Maintainer,
>>> 
>>>  console-setup-freebsd has a dependency on vidcontrol, which is not
>>> part of buster|bullseye|unstable, and causes the package to be
>>> uninstallable.
>> 
>> Adding debian-bsd@ to the loop for advise.
> 
> 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.

James

[1] https://www.ports.debian.org/archive

Re: Bug#932258: console-setup-freebsd: missing dependency

[Holger Wansing]

Hi,

Cyril Brulebois  wrote:
> Héctor Orón Martínez  (2019-07-17):
> > Package: console-setup-freebsd
> > Version: 1.191
> > Severity: grave
> > 
> > 
> > Dear Maintainer,
> > 
> >   console-setup-freebsd has a dependency on vidcontrol, which is not
> > part of buster|bullseye|unstable, and causes the package to be
> > uninstallable.
> 
> Adding debian-bsd@ to the loop for advise.

The same counts for kbdcontrol, also not existing in all suites.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Bug#932258: console-setup-freebsd: missing dependency

[Cyril Brulebois]

Hi Héctor,

Héctor Orón Martínez  (2019-07-17):
> Package: console-setup-freebsd
> Version: 1.191
> Severity: grave
> 
> 
> Dear Maintainer,
> 
>   console-setup-freebsd has a dependency on vidcontrol, which is not
> part of buster|bullseye|unstable, and causes the package to be
> uninstallable.

Adding debian-bsd@ to the loop for advise.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature