Please dak copy-installer 20230427

2023-04-27 Thread Cyril Brulebois
Hi,

FTP team, please sync the installer from sid to testing, as it seems to
be Installed for all release architectures (9 total):

  dak copy-installer 20230427

(It seems the SSH trigger thing wasn't finished, as it's only in master,
not yet in deploy; and possibly the SSH config has yet to be adjusted?
https://lists.debian.org/debian-boot/2023/04/msg00090.html)


Release team: FYI, I've unblocked and urgented it.


Thanks for your time.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


debian-installer_20230427_source.changes ACCEPTED into unstable

2023-04-27 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 27 Apr 2023 16:51:19 +0200
Source: debian-installer
Architecture: source
Version: 20230427
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Changes:
 debian-installer (20230427) unstable; urgency=medium
 .
   * Update translation-status for the release.
Checksums-Sha1:
 4a2e18d710f08a963b44427297143ca0e4234b3b 3868 debian-installer_20230427.dsc
 6d0fb99fb70ff1a66a900f1a7e7a6aff74d50f34 1429698 
debian-installer_20230427.tar.gz
 0d1ae11559128741d4af853d79a14a3c1686cf81 12687 
debian-installer_20230427_source.buildinfo
Checksums-Sha256:
 2c74101334fbd13b5d6f8927785d2c41cfad7b1b99e42d320705dc54f6efd636 3868 
debian-installer_20230427.dsc
 4040be6451f61fedc6e9e5e2f6eba522e1e990f9ae3dd4d286d7bbf7d21ff075 1429698 
debian-installer_20230427.tar.gz
 718bac9749bf918be764adc0c99308738ce0c359e00c9ba50861f46dc803f8d3 12687 
debian-installer_20230427_source.buildinfo
Files:
 d278053f9e9159fc72d56b8645bdcb76 3868 devel optional 
debian-installer_20230427.dsc
 d927db72738bebb13a21c64315807d64 1429698 devel optional 
debian-installer_20230427.tar.gz
 96bcb078e92ee8375b2c6b9009970c44 12687 devel optional 
debian-installer_20230427_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmRKlY8QHGtpYmlAZGVi
aWFuLm9yZwAKCRD/kUrwwrNVIJC+D/9RvUwEW6t/UHusmJRWSD2YbLQZrJDLkMEX
D8V9mJVCLUckIJaVq/p3Kns/aLVXoWaCtyPv1WrADyknV/GaYTdvB9J9VnYCSOr+
D3DTUQlNHMqx7HgQ2Q5pPyzYBivxRvC4mAV+uhpm9RQwGrTtMVeNg3FDI09DszFd
kBoZm9HlWkXriRPU01PS5qj+/wLhlt58X+1J0XYOFFwg59fK47lDM1Hh4h0rTOsf
A1iuNpQ36SXARM4spt40HII+MQhs0RfvLsPC2DaH5gZQfou/ywyJ+ZuExBnskuZp
uXAa1S6EmxrRDu/FIp+nijDG6THXu6jEBCL79AR/vmWmULR5vPGIWR4CJqd1+iwR
hD/6FKfIIFf4O4vgFCr4I4rfu3hYzDtCqa+MJTm90C2vzMffEOqg6KMcaeFRhTF/
/KiNnzYd2pRNgLeOCcKmKRlvmenGJiL8qHaV62IOmDH6YusWsrcfE39d/5bimPM6
GzJTaieTNv3ZsSOcN+jG2WFAIviwYudftb/nISYIaC54ExsbC3lvGRiZj3jmVh9+
7mV0D8rLs97dn1I/tlDaKJGEDddnaLVnkHGeV8EPG9S5mCiRWRu4lx1WL/aMrRBv
6hqiVEGEWeiPmXpZjfNWg6xlVHbtnlNmYM9nm5gtK5CsltXDW1QG4wNKG7i0KCoV
2ZRdLQ9HdA==
=WKnV
-END PGP SIGNATURE-



Processing of debian-installer_20230427_source.changes

2023-04-27 Thread Debian FTP Masters
debian-installer_20230427_source.changes uploaded successfully to localhost
along with the files:
  debian-installer_20230427.dsc
  debian-installer_20230427.tar.gz
  debian-installer_20230427_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

2023-04-27 Thread kt programs
On Thu Apr 27, 2023 at 10:39 PM +08, Cyril Brulebois wrote:
> Control: tag -1 patch
>
> Hi Keith and X team,
>
> and thanks for your report.
>
> Keith Toh  (2023-04-27):
> > Image version: 
> > http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
> >  (2023-04-24 23:09)
>
> For the avoidance of doubt: same story with amd64.
>
> > Machine: UTM QEMU VM
> > 
> > When booting the installer in Graphical install mode, Xorg repeatedly
> > errors saying "no screens found". Based on the Xorg log, it is failing
> > to load the modesetting driver, as the file
> > /usr/lib/xorg/modules/drivers/modesetting_drv.so appears to have been
> > dropped from xerver-xorg-core-udeb between bullseye and bookworm.
> > 
> > >From kibi on #debian-boot (https://paste.debian.net/1278647/):
> > xserver-xorg-core-udeb_1.20.11-1+deb11u3_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.11-1+deb11u4_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.11-1+deb11u5_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.11-1+deb11u6_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.13-1_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.13-2_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.13-3_amd64.udeb YES
> > xserver-xorg-core-udeb_1.20.14-1_amd64.udeb YES
> > xserver-xorg-core-udeb_21.1.1-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.1-2_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.3-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.3-2+b1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.3-2_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.4-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.4-2_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.4-3_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.5-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.6-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.7-1_amd64.udeb NO
> > xserver-xorg-core-udeb_21.1.7-2_amd64.udeb NO
>
> Tracked down to 9c81b8f5b5 upstream:
>   https://cgit.freedesktop.org/xorg/xserver/commit/?id=9c81b8f5b5
>
> Flipping the switch and wrapping it up in a netboot mini.iso
> debian-installer build led to a successful test (with amd64) by Keith.
> We'll try and confirm the same happens with arm64.

Can confirm that an arm64 mini.iso with the same fixes works.

> If you're happy with that approach, feel free to reassign to the udeb,
> and check the udeb-modesetting branch in xorg-server:
>   
> https://salsa.debian.org/xorg-team/xserver/xorg-server/-/commits/udeb-modesetting
>
> I don't have access to VirtualBox right now, but we've had reports of
> failures there as well, maybe that's the same kind of things.
>
>
> Cheers,
> -- 
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant



Bug#1035018: btrfs-progs: /sbin/fsck.btrfs missing from udeb

2023-04-27 Thread Emanuele Rocca
Package: btrfs-progs
Version: 6.2-1
X-Debbugs-CC: debian-boot@lists.debian.org
Tags: patch

Hi,

the btrfs-progs udeb currently includes only /bin/btrfs and /bin/mkfs.btrfs.

Please add /sbin/fsck.btrfs as well so that it can be included in the initramfs
generated by the debian installer. Patch attached.

Thanks!
  ema
diff -Nru btrfs-progs-6.2/debian/btrfs-progs-udeb.install btrfs-progs-6.2/debian/btrfs-progs-udeb.install
--- btrfs-progs-6.2/debian/btrfs-progs-udeb.install	2023-03-01 00:16:51.0 +0100
+++ btrfs-progs-6.2/debian/btrfs-progs-udeb.install	2023-04-27 16:43:48.0 +0200
@@ -1,2 +1,3 @@
 btrfs		/bin
 mkfs.btrfs	/bin
+fsck.btrfs /sbin


Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

2023-04-27 Thread Cyril Brulebois
Control: tag -1 patch

Hi Keith and X team,

and thanks for your report.

Keith Toh  (2023-04-27):
> Image version: 
> http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
>  (2023-04-24 23:09)

For the avoidance of doubt: same story with amd64.

> Machine: UTM QEMU VM
> 
> When booting the installer in Graphical install mode, Xorg repeatedly
> errors saying "no screens found". Based on the Xorg log, it is failing
> to load the modesetting driver, as the file
> /usr/lib/xorg/modules/drivers/modesetting_drv.so appears to have been
> dropped from xerver-xorg-core-udeb between bullseye and bookworm.
> 
> >From kibi on #debian-boot (https://paste.debian.net/1278647/):
> xserver-xorg-core-udeb_1.20.11-1+deb11u3_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.11-1+deb11u4_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.11-1+deb11u5_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.11-1+deb11u6_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.13-1_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.13-2_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.13-3_amd64.udeb YES
> xserver-xorg-core-udeb_1.20.14-1_amd64.udeb YES
> xserver-xorg-core-udeb_21.1.1-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.1-2_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.3-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.3-2+b1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.3-2_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.4-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.4-2_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.4-3_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.5-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.6-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.7-1_amd64.udeb NO
> xserver-xorg-core-udeb_21.1.7-2_amd64.udeb NO

Tracked down to 9c81b8f5b5 upstream:
  https://cgit.freedesktop.org/xorg/xserver/commit/?id=9c81b8f5b5

Flipping the switch and wrapping it up in a netboot mini.iso
debian-installer build led to a successful test (with amd64) by Keith.
We'll try and confirm the same happens with arm64.

If you're happy with that approach, feel free to reassign to the udeb,
and check the udeb-modesetting branch in xorg-server:
  
https://salsa.debian.org/xorg-team/xserver/xorg-server/-/commits/udeb-modesetting

I don't have access to VirtualBox right now, but we've had reports of
failures there as well, maybe that's the same kind of things.


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


signature.asc
Description: PGP signature


Processed: Re: Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

2023-04-27 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 patch
Bug #1035014 [installation-reports] installation-reports: Graphical installer 
has Xorg "no screens found" error
Added tag(s) patch.

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



Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

2023-04-27 Thread Keith Toh
Package: installation-reports
Severity: important

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
 (2023-04-24 23:09)

Machine: UTM QEMU VM


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[ ]
Configure network:  [ ]
Detect media:   [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

When booting the installer in Graphical install mode, Xorg repeatedly
errors saying "no screens found". Based on the Xorg log, it is failing
to load the modesetting driver, as the file
/usr/lib/xorg/modules/drivers/modesetting_drv.so appears to have been
dropped from xerver-xorg-core-udeb between bullseye and bookworm.

>From kibi on #debian-boot (https://paste.debian.net/1278647/):
xserver-xorg-core-udeb_1.20.11-1+deb11u3_amd64.udeb YES
xserver-xorg-core-udeb_1.20.11-1+deb11u4_amd64.udeb YES
xserver-xorg-core-udeb_1.20.11-1+deb11u5_amd64.udeb YES
xserver-xorg-core-udeb_1.20.11-1+deb11u6_amd64.udeb YES
xserver-xorg-core-udeb_1.20.13-1_amd64.udeb YES
xserver-xorg-core-udeb_1.20.13-2_amd64.udeb YES
xserver-xorg-core-udeb_1.20.13-3_amd64.udeb YES
xserver-xorg-core-udeb_1.20.14-1_amd64.udeb YES
xserver-xorg-core-udeb_21.1.1-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.1-2_amd64.udeb NO
xserver-xorg-core-udeb_21.1.3-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.3-2+b1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.3-2_amd64.udeb NO
xserver-xorg-core-udeb_21.1.4-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.4-2_amd64.udeb NO
xserver-xorg-core-udeb_21.1.4-3_amd64.udeb NO
xserver-xorg-core-udeb_21.1.5-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.6-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.7-1_amd64.udeb NO
xserver-xorg-core-udeb_21.1.7-2_amd64.udeb NO


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230423-02:07:34"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 6.1.0-7-arm64 #1 SMP Debian 6.1.20-2 (2023-04-08) 
aarch64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Red Hat, Inc. QEMU PCIe Host bridge 
[1b36:0008]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:1100]
lspci -knn: 00:01.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network 
device [1af4:1000]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0001]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:02.0 Display controller [0380]: Red Hat, Inc. Virtio GPU 
[1af4:1050] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:1100]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller 
[8086:2668] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: 00:04.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 
Host Controller [1033:0194] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:05.0 USB controller [0c03]: Red Hat, Inc. QEMU XHCI Host 
Controller [1b36:000d] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:1100]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:06.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio block 
device [1af4:1001]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0002]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:07.0 Communication controller [0780]: Red Hat, Inc. Virtio 
console [1af4:1003]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0003]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:08.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG 
[1af4:1005]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0004]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
usb-list: 
usb-list: Bus 01 Device 01: xHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 6.1.0-7-arm64 xhci-hcd
usb-list:Interface 00: Class 09(hub  ) 

Re: Debian installer can't install Debian testing in VirtualBox when EFI enabled

2023-04-27 Thread Cyril Brulebois
Steve McIntyre  (2023-04-27):
> *Please* reply to all and respond to the debian-boot list, I'm not the
> only person working on stuff here...

Yes please!

> On Thu, Apr 20, 2023 at 12:45:17PM +0800, Licheng Hsu wrote:
> >> Thanks, it does. It seems there's a problem with video setup and
> >> it's not starting X. What options do you have under Display?
> >
> >There're 4 options to choose from "Graphics Controller" in VirtualBox.
> >They're VBoxVGA, VMSVGA, VBoxSVGA, and None. VirtualBox suggests
> >VMSVGA, but they all don't work.

Does Debian 11 start correctly?


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


signature.asc
Description: PGP signature


Re: Debian installer can't install Debian testing in VirtualBox when EFI enabled

2023-04-27 Thread Steve McIntyre
*Please* reply to all and respond to the debian-boot list, I'm not the
only person working on stuff here...

On Thu, Apr 20, 2023 at 12:45:17PM +0800, Licheng Hsu wrote:
>Hi
>
>> Thanks, it does. It seems there's a problem with video setup and it's
>> not starting X. What options do you have under Display?
>
>There're 4 options to choose from "Graphics Controller" in VirtualBox.
>They're VBoxVGA, VMSVGA, VBoxSVGA, and None. VirtualBox suggests
>VMSVGA, but they all don't work.

Hmmm.

>> If you start with "Install" rather than "Graphical Install" then that
>> should work for now.
>
>I have tried "Install", even "Expert install" in "Advanced
>options...", but still doesn't work. They all end with blank gray
>screen just as the videos I attached show.

Argh. I've no idea what's going on here... :-(

>"Graphical rescue mode" or "Rescure mode" in "Advanced options..."
>doesn't work, neither.
>
>By the way, thanks for your hard work.

You're welcome!

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back



Bug#1034990: [INTL:be] updated Belarusian translation

2023-04-27 Thread Viktar Siarheichyk
Package: grub-installer
Version: 1.190

be.po
Description: application/po

Severity: wishlist
Tags: patch l10n
Please find attached the updated Belarusian translation.

Bug#1030938: os-prober: Does not detect OpenSuse Tumbleweed

2023-04-27 Thread Steve McIntyre
Hi Frank,

On Thu, Feb 09, 2023 at 11:58:58AM -0500, Frank McCormick wrote:
>Package: os-prober
>Version: 1.81
>Severity: wishlist
>X-Debbugs-Cc: bea...@videotron.ca
>
>
>Debian Sid updated Grub today and when os-prober ran via update-grub it did 
>not detect
>my OpenSuse Tumbleweed partition.
>The update had installed the new Grub so I could not boot into
>Tumbleweed.
>
>Now I have held all the grub packages so I won't be faced
>with this again. The Tumbleweed grub installation and it's version
>of os-prober does detect both Debian and Fedora on another partition.
>FYI Fedoras os-prober also doesn't detect Tumbleweed but that's a 
>problem I'll report to them.

This is most likely a grub issue - the defaults have changed to *not*
run os-prober by default.

If so, edit /etc/default/grub and set GRUB_DISABLE_OS_PROBER=false
then run update-grub this will fix your problem. Or run
dpkg-reconfigure on your grub package (either grub-pc or
grub-efi-amd64) and the latest grub packages will ask you about
os-prober.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Welcome my son, welcome to the machine.



Processed: Re: Bug#1034812: installation-reports: Unbootable after install: UEFI installed to wrong ESP

2023-04-27 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 patch
Bug #1034812 [installation-reports] installation-reports: Unbootable after 
install: UEFI installed to wrong ESP
Added tag(s) patch.

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



Bug#1034812: installation-reports: Unbootable after install: UEFI installed to wrong ESP

2023-04-27 Thread Pascal Hambourg

Control: tags -1 patch

On 25/04/2023 at 19:55, Pascal Hambourg wrote:

Suggested fix is two-fold:

1) Call clean_method() at the beginning of 
partman-auto-lvm/autopartition-lvm, as is done in 
partman-auto/autopartition and partman-auto-crypto/autopartition-crypto. 
This should solve the issue for swap partitions but is not enough for ESPs.


Patch attached for the partman-auto-lvm part.From 1d6b590b418184d1f5b92126542f33c90dfda945 Mon Sep 17 00:00:00 2001
From: Pascal Hambourg 
Date: Thu, 27 Apr 2023 08:53:05 +0200
Subject: [PATCH] Call clean_method again

The call to clean_method was lost with commit cfc6797f.
As a result, if existing swap and EFI partitions on other disks were marked
used (which is the default), swap partitions will be used (and get new UUIDs,
which is bad if they belong to another system) and any EFI partition on another
disk may be used instead of the newly created one (#1034812).

This patch fixes the issue for swap partitions but fixing the issue for EFI
partitions also requires a change in partman-efi (same as #1034208).
---
 autopartition-lvm | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/autopartition-lvm b/autopartition-lvm
index e081beb..40026c3 100755
--- a/autopartition-lvm
+++ b/autopartition-lvm
@@ -5,6 +5,9 @@
 devs="$*"
 method="lvm"
 
+# Ensure we have no pre-existing partitions marked as swap and efi
+clean_method
+
 auto_lvm_prepare "$devs" $method || exit $?
 
 auto_lvm_perform || exit 1
-- 
2.30.2



Processed: Re: Bug#1034208: Partman may use the wrong ESP partition

2023-04-27 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 Partman may use the wrong ESP partition
Bug #1034208 [partman-efi] Partman may reset user's choice for ESP partitions 
use
Changed Bug title to 'Partman may use the wrong ESP partition' from 'Partman 
may reset user's choice for ESP partitions use'.

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



Bug#1034208: Partman may use the wrong ESP partition

2023-04-27 Thread Pascal Hambourg

Control: retitle -1 Partman may use the wrong ESP partition

On 15/04/2023 at 16:34, Pascal Hambourg wrote:


Here are patches implementing the two versions of the above fix.


It seems that this patch is also needed to fix #1034812 (guided 
partitioning with LVM uses the wrong ESP), in combination with another 
(trivial) patch for partman-auto-lvm.


Updating the title accordingly.