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


Groups > linux.debian.bugs.dist > #1204710

Bug#1076539: plymouth: Updating plymouth fails with "No space left on device"

From Diederik de Haas <didi.debian@cknow.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1076539: plymouth: Updating plymouth fails with "No space left on device"
Date 2024-07-18 11:50 +0200
Message-ID <J1vVT-2WDp-1@gated-at.bofh.it> (permalink)
References <J1vjb-2WqG-3@gated-at.bofh.it> <J1vsR-2Wu7-1@gated-at.bofh.it> <J1u3L-2VvH-3@gated-at.bofh.it> <J1vsR-2Wu7-1@gated-at.bofh.it>
Organization Connecting Knowledge

Cross-posted to 2 groups.

Show all headers | View raw


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

On Thursday, 18 July 2024 11:11:23 CEST Laurent Bigonville wrote:
> Well you change expectation from users that have firmware-misc-nonfree
> installed by pulling that huge package

I fail to see how. If those files weren't split into their own packages, the 
updated/new firmware-misc-nonfree would've contained the firmware of
the 'old' misc-nonfree + nvidia-graphics + intel-graphics + mediatek/ralink + 
new files that would otherwise have been added for misc-nonfree.

See also https://bugs.debian.org/1057786

> IMVHO, a lot of people with firmware-misc-nonfree installed will
> experience an issue when updating.

You should've seen a NEWS entry informing you of the changes.
If that didn't happen, that's a problem/bug.

On donderdag 18 juli 2024 11:14:35 CEST you wrote:
> On 18.07.24 11:11, Laurent Bigonville wrote:
> > The /boot partition size I've here is the default one from the
> > debian-installer
> 
> This seems to be the core of the problem. In my case it is 500MB, and
> was the default from the install. So many users will be affected by default.

I do agree with that. And the kernel size growing bigger contributed to that 
becoming a (bigger) problem. (There are bug reports about that)

When I set up my system, I made /boot 2G because I foresaw this problem
(and I intended to do a bit more with kernels then the average user).

I think a very valid argument can be made to change the default in d-i,
but to be blunt: you *accepted* the *defaults*.

But most people are probably not as experienced with Debian as the two of you 
which in turn would make me point out the same problem, but be more subtle/
gentle about it.

Still, "No space left on device" is not a packaging problem.

Cheers,
  Diederik

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Bastian Venthur <venthur@debian.org> - 2024-07-18 09:50 +0200
  Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Laurent Bigonville <bigon@debian.org> - 2024-07-18 10:30 +0200
  Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Laurent Bigonville <bigon@debian.org> - 2024-07-18 11:20 +0200
    Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Diederik de Haas <didi.debian@cknow.org> - 2024-07-18 11:50 +0200
  Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Diederik de Haas <didi.debian@cknow.org> - 2024-07-19 17:40 +0200
    Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Diederik de Haas <didi.debian@cknow.org> - 2024-07-19 20:10 +0200
      Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Diederik de Haas <didi.debian@cknow.org> - 2024-07-23 16:20 +0200
  Bug#1076539: plymouth: Updating plymouth fails with "No space left on device" Max Görner <max+reportbug@familie-goerner.eu> - 2024-07-23 15:50 +0200

csiph-web