Hello,
my laptop runs with a default partition layout created by Debian
Installer 4 years or so ago:
Device StartEnd Sectors Size Type
/dev/nvme0n1p120481050623 1048576 512M EFI System
/dev/nvme0n1p2 10506241550335499712 244M Linux filesystem
/dev/nvme0
On Thu, 06 Oct 2022 11:48:42 +0200, Enrico Zini wrote:
> ## /etc/initramfs-tools/initramfs.conf
>
> # makes somewhat smaller initrd files and buys some time
> COMPRESS=zstd
>
> # makes definitely smaller initrd files, but breaks boot if
> # dependencies are not computed correctly
On Thu, 2022-10-06 at 11:48 +0200, Enrico Zini wrote:
> Device Start End Sectors Size Type
> /dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
> /dev/nvme0n1p2 1050624 1550335 499712 244M Linux filesystem
> /dev/nvme0n1p3 1550336 1000214527 998664192 476.2G
On Thu, 2022-10-06 at 11:48 +0200, Enrico Zini wrote:
> Hello,
>
> my laptop runs with a default partition layout created by Debian
> Installer 4 years or so ago:
>
> Device StartEnd Sectors Size Type
> /dev/nvme0n1p120481050623 1048576 512M EFI System
> /dev/nvm
The vmlinuz is usually small. The initrd can be quite big.
Regards
On Thursday, 6 October 2022 15:41:52 CEST Ben Hutchings wrote:
> > my laptop runs with a default partition layout created by Debian
> > Installer 4 years or so ago:
> >
> > Device StartEnd Sectors Size Type
> > /dev/nvme0n1p120481050623 1048576 512M EFI System
> >
Hello,
El jue., 6 oct. 2022 12:03, gregor herrmann escribió:
> On Thu, 06 Oct 2022 11:48:42 +0200, Enrico Zini wrote:
>
> > ## /etc/initramfs-tools/initramfs.conf
> >
> > # makes somewhat smaller initrd files and buys some time
> > COMPRESS=zstd
> >
> > # makes definitely smaller ini
On Wed, Oct 05, 2022 at 10:11:27PM +0200, Julien Cristau wrote:
>On Sun, Oct 02, 2022 at 08:21:31PM +0100, Steve McIntyre wrote:
>> On Sun, Oct 02, 2022 at 11:08:47AM -0400, Michael Stone wrote:
>> >On Sun, Oct 02, 2022 at 03:53:00PM +0100, Steve McIntyre wrote:
>> >> On Sun, Oct 02, 2022 at 04:43:
On Thursday, 6 October 2022 16:23:27 CEST Diederik de Haas wrote:
> That doesn't change my perspective that the fundamental aspect of /boot
> being too small should be addressed (directly) and not try to workaround
> it.
With workarounds I was thinking of using a better compression scheme (already
On Thu, Oct 6, 2022 at 15:45:25 +0100, Steve McIntyre wrote:
> On Wed, Oct 05, 2022 at 10:11:27PM +0200, Julien Cristau wrote:
> >On Sun, Oct 02, 2022 at 08:21:31PM +0100, Steve McIntyre wrote:
> >> On Sun, Oct 02, 2022 at 11:08:47AM -0400, Michael Stone wrote:
> >> >On Sun, Oct 02, 2022 at 03:53
Am 06.10.22 um 16:23 schrieb Diederik de Haas:
That doesn't change my perspective that the fundamental aspect of /boot being
too small should be addressed (directly) and not try to workaround it.
Agreed. But automatically resizing existing partitions on a running
system will probably not be p
On Thu, Oct 06, 2022 at 05:03:20PM +0200, Julien Cristau wrote:
> On Thu, Oct 6, 2022 at 15:45:25 +0100, Steve McIntyre wrote:
>
> > On Wed, Oct 05, 2022 at 10:11:27PM +0200, Julien Cristau wrote:
> > >On Sun, Oct 02, 2022 at 08:21:31PM +0100, Steve McIntyre wrote:
> > >> On Sun, Oct 02, 2022 at
Hi,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021336
This kind of bug in "required" package breaks build infrastructure
that uses sid. However, we can prevent it by using piuparts before
it would get into repository, IMHO.
How we can implement it, any ideas?
--
Hideki Yamane
Am 06.10.22 um 17:34 schrieb Hideki Yamane:
Hi,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021336
This kind of bug in "required" package breaks build infrastructure
that uses sid. However, we can prevent it by using piuparts before
it would get into repository, IMHO.
Ho
Am 06.10.22 um 17:45 schrieb Michael Biebl:
Am 06.10.22 um 17:34 schrieb Hideki Yamane:
Hi,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021336
This kind of bug in "required" package breaks build infrastructure
that uses sid. However, we can prevent it by using piuparts before
it
Am 06.10.22 um 11:48 schrieb Enrico Zini:
(somehow a bit more space is needed during install than is used at the
end)
Can you clarify? Is the new intramfs generated in /boot or generated
outside of /boot but copied to /boot under a different name so it can be
replaced atomically?
I assume thi
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: lomiri-notifications
Version : 1.3.0
Upstream Author : UBports Foundation
* URL :
https://gitlab.com/ubports/development/core/lomiri-notifications/
* Lice
On Thu, 6 Oct 2022 17:14:56 +0200 Michael Biebl wrote:
> Am 06.10.22 um 16:23 schrieb Diederik de Haas:
> > That doesn't change my perspective that the fundamental aspect of /boot
> > being too small should be addressed (directly) and not try to workaround
> > it.
>
> Agreed. But automatically re
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 1261 (new: 0)
Total number of packages offered up for adoption: 173 (new: 1)
Total number of packages reques
Hi Michael,
On Thu, 6 Oct 2022 17:45:06 +0200
Michael Biebl wrote:
> If you are using salsa, you can utilize all the features gitlab
> provides. E.g. in src:systemd, we use
> https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/gitlab-ci.yml
Yes, I'm using salsa-ci pipelin
On Thu, Oct 06, 2022 at 06:16:56PM +0200, Michael Biebl wrote:
> Can you clarify? Is the new intramfs generated in /boot or generated outside
> of /boot but copied to /boot under a different name so it can be replaced
> atomically?
> I assume this is done for robustness reasons. Maybe, if space is
21 matches
Mail list logo
