Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #94012 > unrolled thread

Bug#1146782: Ensure split dracut packages are upgraded together

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1146782: Ensure split dracut packages are upgraded together Chris Hofstädtler <zeha@debian.org> - 2026-09-05 18:20 +0200
    Bug#1146782: Ensure split dracut packages are upgraded together Benjamin Drung <bdrung@debian.org> - 2026-09-06 13:40 +0200
    Bug#1146782: marked as done (Ensure split dracut packages are  upgraded together) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-09-06 14:30 +0200

#94012 — Bug#1146782: Ensure split dracut packages are upgraded together

Source: dracut
Version: 112-2
Severity: normal

Hi,

I've noticed that the individual dracut binary packages can be 
installed in mixed versions. I assume this is not a particularly 
well-tested situation.

Many other source packages configure their binary packages with a 
strict version dependency.

As an example, dracut-network currently has:

  Depends: dracut-core

This allows a simultaneous installation of dracut-network 112-2 and 
dracut 106-6.

If dracut-network were to switch to

  Depends: dracut-core (= ${binary:Version})

Then apt would install the packages in lockstep, and no probably 
badly-supported situations would arise.

Similar dependencies should probably be set in dracut, dracut-test,
and maybe from dracut-core to dracut-install.

Best,
Chris

[toc] | [next] | [standalone]

#94016

On Sat, 2026-09-05 at 18:16 +0200, Chris Hofstädtler wrote:
> Source: dracut
> Version: 112-2
> Severity: normal
> 
> Hi,
> 
> I've noticed that the individual dracut binary packages can be 
> installed in mixed versions. I assume this is not a particularly 
> well-tested situation.
> 
> Many other source packages configure their binary packages with a 
> strict version dependency.
> 
> As an example, dracut-network currently has:
> 
>   Depends: dracut-core
> 
> This allows a simultaneous installation of dracut-network 112-2 and 
> dracut 106-6.
> 
> If dracut-network were to switch to
> 
>   Depends: dracut-core (= ${binary:Version})
> 
> Then apt would install the packages in lockstep, and no probably 
> badly-supported situations would arise.
> 
> Similar dependencies should probably be set in dracut, dracut-test,
> and maybe from dracut-core to dracut-install.

Thanks. I'll tighten the dependencies.

dracut already has:

Depends: dracut-core (<< ${binary:Version}+b+~),
         dracut-core (>= ${binary:Version}),

This is needed because we have a mixture of architecture dependent and
architecture independent.

-- 
Benjamin Drung
Debian & Ubuntu Developer

[toc] | [prev] | [next] | [standalone]

#94018 — Bug#1146782: marked as done (Ensure split dracut packages are upgraded together)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sun, 06 Sep 2026 12:18:57 +0000
with message-id <E1x3Bpp-0000000DII6-1Y2m@fasolo.debian.org>
and subject line Bug#1146782: fixed in dracut 112-4
has caused the Debian Bug report #1146782,
regarding Ensure split dracut packages are upgraded together
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1146782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1146782
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web