Bug#1072768: debian-installer: menu item to select to install oldstable gone

2024-06-07 Thread Thorsten Glaser
Package: debian-installer
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de

https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.5.0-amd64-netinst.iso

I was booting in expert mode and expecting between the mirror select
and the installing of the base system there to be an option to select
which release to install (oldstable, stable, testing, unstable), as
I have been using occasionally for years.

This menu did not show up.


-- System Information:
Debian Release: 11.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 
'oldstable-proposed-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-29-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)



Re: Contacting Debian Boot team

2024-06-07 Thread Emanuele Rocca
Hi Andreas,

On 2024-06-06 04:38, Andreas Tille wrote:
> Any experiences with Lenovo Thinkpad X13S?  Finally Lenovo is present on
> DebConfs and we can talk to them.  Just from reading[1] it seems to be
> what I'm looking for in principle - provided they might unbundle Win11
> from it and I can just plugin the Debian installer USB to install
> Debian.

Trixie runs fine on it, though there are some rough edges. Full details
on https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s

For details of the work done on the kernel/installer/cd/live images:
https://wiki.debian.org/DebianEvents/gb/2023/MiniDebConfCambridge/Rocca

  ema



Bug#1065592: marked as done (partman-efi: add build support for loongarch64)

2024-06-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Jun 2024 21:08:38 +
with message-id 
and subject line Bug#1065592: fixed in partman-efi 104
has caused the Debian Bug report #1065592,
regarding partman-efi: add build support for loongarch64
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 ow...@bugs.debian.org
immediately.)


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

Source: partman-efi
Version: 103
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

The partman-efi source package lacks LoongArch architecture support.
We need to add build support for loongarch64 in d/control.

Please consider the patch I have attached.
The partman-efi source package was compiled successfully on my local 
loong64 rootfs environment.

If you have any questions, you can contact me at any time.

thanks,
Dandan Zhang

diff -Nru partman-efi-103/debian/control partman-efi-103/debian/control
--- partman-efi-103/debian/control  2024-01-06 21:33:46.0 +
+++ partman-efi-103/debian/control  2024-01-06 21:49:11.0 +
@@ -9,6 +9,6 @@
 
 Package: partman-efi
 Package-Type: udeb
-Architecture: i386 ia64 amd64 arm64 armhf riscv64
+Architecture: i386 ia64 amd64 arm64 armhf riscv64 loong64
 Depends: partman-base, efi-modules, dosfstools-udeb, ${misc:Depends}
 Description: Add to partman support for EFI System Partitions
--- End Message ---
--- Begin Message ---
Source: partman-efi
Source-Version: 104
Done: Holger Wansing 

We believe that the bug you reported is fixed in the latest version of
partman-efi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated partman-efi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Jun 2024 22:21:01 +0200
Source: partman-efi
Architecture: source
Version: 104
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 1065592
Changes:
 partman-efi (104) unstable; urgency=medium
 .
   * Team upload.
 .
   [ John Paul Adrian Glaubitz ]
   * Build for loong64 (Closes: #1065592)
Checksums-Sha1:
 297840d50c2fbcb0d84f1b5f7f31a6e77eee7394 1757 partman-efi_104.dsc
 9af379361448eddd91491fc5d48594aed6ba3fdf 62100 partman-efi_104.tar.xz
 613a45e2b65eabbc2cd5d9ae24e4ddf5aec851ca 5998 partman-efi_104_amd64.buildinfo
Checksums-Sha256:
 653f1082f326d1378a82a5319577090fefdcad8030c07a341fe3210081115a12 1757 
partman-efi_104.dsc
 cc91f553d3201ff33ea260af31f177bdd0e6ade1fa92e0519adb58ec6d5a1922 62100 
partman-efi_104.tar.xz
 1f25c9aefcb5e2d929a23b505e9459ec7b51dc7c78f5c1031fdc7bdefe25b1d4 5998 
partman-efi_104_amd64.buildinfo
Files:
 1ea54c537a74893ada83248577c641c5 1757 debian-installer standard 
partman-efi_104.dsc
 b2d118c7d95f114b80d2fc8dad157dfd 62100 debian-installer standard 
partman-efi_104.tar.xz
 ede16cda6b4fb86f40a6658d472d6610 5998 debian-installer standard 
partman-efi_104_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZiHywVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2EVkP/A4vFas29SyihO9VzLZditIrbopb
I7BJxn9KZdl1o7gfEYAPoOaL3xzRrd/WIijmMkMiDiTyysQKxVrGcCl97LX7BPjM
0fncAEFc5WIasBQfNejpJR2ESZEokrffvyg5/mQECXe+q8UMTi9LeJ8MWOFT9Rrx
CCoNLyH/tSPnMvTwjgrnlV1we7C8cF3i7h3aL80WRvNcy2EItHrUdmYomeskTkXv
lbGcAopBVkFyfaAn1Cji+bR7b2PfY2mp+n5AsYVPXZDJv+qsnQhh4Qt1v2yOnasp
8Ot/AwWdeG7kPFIACC6YqH+1fSOwsxJa7kcaXKPtBlvbBYn2syRGSQhTGyvZTgvK
hLd2ItOhN8mhl7AXUKw0aKei8aEXiRLZ3atBE6GUuW7Zb4GBdwIPaY3qNz+nd3QE
CniNNzFG/AqGkY5SeFhv/kjBrQSeY3FO3Q1/cNg0wATcoV2eLXsf0hetC0l019ML
onWQmFJ+DOjeqxLVElNYKHp3bjme+Lnn0M8SMtB+YCpPuhxciawMh+6lRIoTrH2I
vJs0klvYI1FHu+VgD4nNkzccT+Yr/+5lLpDswMVYhl+x7u3rtO/w8zMwIpMdk7M8
+oVCcm7mdXyQUnOj5OiHqHFvfKAvQbbMGtEMfkrEccHQJiEXHpbKE3CN+uH2DQeN
4kUIHVwjZ85oqO5F
=lqQl
-END PGP SIGNATURE-



pgpyuRbS5m1cW.pgp
Description: PGP signature
--- End Message ---


Processing of partman-efi_104_source.changes

2024-06-06 Thread Debian FTP Masters
partman-efi_104_source.changes uploaded successfully to localhost
along with the files:
  partman-efi_104.dsc
  partman-efi_104.tar.xz
  partman-efi_104_amd64.buildinfo

Greetings,

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



partman-efi_104_source.changes ACCEPTED into unstable

2024-06-06 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Jun 2024 22:21:01 +0200
Source: partman-efi
Architecture: source
Version: 104
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 1065592
Changes:
 partman-efi (104) unstable; urgency=medium
 .
   * Team upload.
 .
   [ John Paul Adrian Glaubitz ]
   * Build for loong64 (Closes: #1065592)
Checksums-Sha1:
 297840d50c2fbcb0d84f1b5f7f31a6e77eee7394 1757 partman-efi_104.dsc
 9af379361448eddd91491fc5d48594aed6ba3fdf 62100 partman-efi_104.tar.xz
 613a45e2b65eabbc2cd5d9ae24e4ddf5aec851ca 5998 partman-efi_104_amd64.buildinfo
Checksums-Sha256:
 653f1082f326d1378a82a5319577090fefdcad8030c07a341fe3210081115a12 1757 
partman-efi_104.dsc
 cc91f553d3201ff33ea260af31f177bdd0e6ade1fa92e0519adb58ec6d5a1922 62100 
partman-efi_104.tar.xz
 1f25c9aefcb5e2d929a23b505e9459ec7b51dc7c78f5c1031fdc7bdefe25b1d4 5998 
partman-efi_104_amd64.buildinfo
Files:
 1ea54c537a74893ada83248577c641c5 1757 debian-installer standard 
partman-efi_104.dsc
 b2d118c7d95f114b80d2fc8dad157dfd 62100 debian-installer standard 
partman-efi_104.tar.xz
 ede16cda6b4fb86f40a6658d472d6610 5998 debian-installer standard 
partman-efi_104_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZiHywVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2EVkP/A4vFas29SyihO9VzLZditIrbopb
I7BJxn9KZdl1o7gfEYAPoOaL3xzRrd/WIijmMkMiDiTyysQKxVrGcCl97LX7BPjM
0fncAEFc5WIasBQfNejpJR2ESZEokrffvyg5/mQECXe+q8UMTi9LeJ8MWOFT9Rrx
CCoNLyH/tSPnMvTwjgrnlV1we7C8cF3i7h3aL80WRvNcy2EItHrUdmYomeskTkXv
lbGcAopBVkFyfaAn1Cji+bR7b2PfY2mp+n5AsYVPXZDJv+qsnQhh4Qt1v2yOnasp
8Ot/AwWdeG7kPFIACC6YqH+1fSOwsxJa7kcaXKPtBlvbBYn2syRGSQhTGyvZTgvK
hLd2ItOhN8mhl7AXUKw0aKei8aEXiRLZ3atBE6GUuW7Zb4GBdwIPaY3qNz+nd3QE
CniNNzFG/AqGkY5SeFhv/kjBrQSeY3FO3Q1/cNg0wATcoV2eLXsf0hetC0l019ML
onWQmFJ+DOjeqxLVElNYKHp3bjme+Lnn0M8SMtB+YCpPuhxciawMh+6lRIoTrH2I
vJs0klvYI1FHu+VgD4nNkzccT+Yr/+5lLpDswMVYhl+x7u3rtO/w8zMwIpMdk7M8
+oVCcm7mdXyQUnOj5OiHqHFvfKAvQbbMGtEMfkrEccHQJiEXHpbKE3CN+uH2DQeN
4kUIHVwjZ85oqO5F
=lqQl
-END PGP SIGNATURE-



pgpAmKYQ59YOf.pgp
Description: PGP signature


Bug#787279: marked as done (Cannot disable screen blanking with Jessie preseed installation)

2024-06-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Jun 2024 20:50:52 +
with message-id 
and subject line Bug#787279: fixed in rootskel-gtk 12.0.3
has caused the Debian Bug report #787279,
regarding Cannot disable screen blanking with Jessie preseed installation
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 ow...@bugs.debian.org
immediately.)


-- 
787279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer (i386)
Version: 20150422
Severity: normal
Tags: d-i

With preseed installation (bare metal) of Jessie screen goes black in 10
minutes though there is parameter "dpms=false":
APPEND vga=788 auto=true priority=critical interface=eth0 url=
http://192.168.0.100/preseed_jessie.cfg
initrd=netboot_debian_jessie_32bit/debian-installer/i386/initrd.gz
netcfg/dhcp_timeout=120 hw-detect/load_firmware=false dpms=false
desktop=xfce suite=jessie

Same situation with installation (bare metal) without GUI, even the
consoleblank=0 does not prevent screen to go blank:
APPEND vga=788 auto=true priority=critical interface=eth0 url=
http://192.168.0.100/preseed_jessie.cfg
initrd=netboot_debian_jessie_32bit/debian-installer/i386/initrd.gz
netcfg/dhcp_timeout=120 hw-detect/load_firmware=false dpms=false
consoleblank=0 tasks=standard suite=jessie

Is that timeout hardcoded to d-i, consoleblank=0 has no effect, and no X on
CLI install?
After installation adding consoleblank=0 to /etc/default/grup &&
update-grub works normally.

netboot.tar.gz from:
http://ftp.fi.debian.org/debian/dists/jessie/main/installer-i386/current/images/netboot/gtk/

Related bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695270

Not a critical thing, but its annoying to keep hitting the key to power up
display to see how the installation is going.
IMHO whole screensaver feature could be disabled, it was usefull with old
CRTs, but dont think it's needed nowadays... more of a nuisance.
--- End Message ---
--- Begin Message ---
Source: rootskel-gtk
Source-Version: 12.0.3
Done: Holger Wansing 

We believe that the bug you reported is fixed in the latest version of
rootskel-gtk, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 787...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated rootskel-gtk package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Jun 2024 21:09:50 +0200
Source: rootskel-gtk
Architecture: source
Version: 12.0.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 787279 1036886
Changes:
 rootskel-gtk (12.0.3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Philip Hands ]
   * prevent screen blanking under X (closes: #787279)
 .
   [ Samuel Thibault ]
   * Dark theme: Set background as dark, so that text input fields actually
 show up (Closes: #1036886)
Checksums-Sha1:
 03b2a7010d6c484dd47fbfd8b9c52f392f05dc9f 1721 rootskel-gtk_12.0.3.dsc
 19807d6db26b68ed1c65b9490d52f46b39b733a7 30368 rootskel-gtk_12.0.3.tar.xz
 b64705cd5fa8b2bbffb62bf10214f859a937fdcd 7372 
rootskel-gtk_12.0.3_amd64.buildinfo
Checksums-Sha256:
 efe35d14b78646d8fcb5daba969e50ee90f37811a74ef8158436219b03d359bc 1721 
rootskel-gtk_12.0.3.dsc
 845ae93b2b9f4e2338b94c50f7f8906f1c4cc3d9160c03efed3c7c735992bed3 30368 
rootskel-gtk_12.0.3.tar.xz
 1febe93772062ebb134eddadb137e125a866e83089396b442ca3aa62174de1f3 7372 
rootskel-gtk_12.0.3_amd64.buildinfo
Files:
 46e34cea606699638e9810e2fce0e774 1721 debian-installer optional 
rootskel-gtk_12.0.3.dsc
 cbb6ee5d7195d66cd9f65e3be6cd33b1 30368 debian-installer optional 
rootskel-gtk_12.0.3.tar.xz
 a6594c54560e5b3e16b08ab5aa6e3269 7372 debian-installer optional 
rootskel-gtk_12.0.3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZiEvgVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2xDEP/AgF/4dwRARTMOEsGA/R4pb1h4Cu
4OcX6+gtU2LK/bwyltgQx8V60QkgzfAEhm+razPQktTpiVGPAYCt4K9UdxfQ2Xcc
yVS4DzfcJ/tvKaY4efkX93rZf47YZHOEGOp3BTDw/gs+ptW0karEFvGldYf7TBsE
DwYFQYWgTf+hDJoZKeQN0Nec9BVKq5Y8rud9zPVZ36TqR66d0DhGDAlkRDFuw7xR

Bug#1036886: marked as done (Text input fields very hard to identify in high contrast / dark mode)

2024-06-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Jun 2024 20:50:52 +
with message-id 
and subject line Bug#1036886: fixed in rootskel-gtk 12.0.3
has caused the Debian Bug report #1036886,
regarding Text input fields very hard to identify in high contrast / dark mode
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 ow...@bugs.debian.org
immediately.)


-- 
1036886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rootskel-gtk
Severity: normal
Tags: a11y

Dear Mantainer,

running the installer in graphical dark / high contrast mode, it’s very
hard to identify text input fields in the installer pages, making it
very difficult to see where things need to be input.

The default theme does a must better job at it whereas the high contrast
theme uses (almost ?) the same color for the global page background and
the text input fields background, and the input fields have no visible
border.

If we don’t want to reduce the contrast of either the static text or the
input fields an option could be for text input fields to have a border
with the same color as the text that would make them clearly
identifiable.



-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'testing-security'), (500, 'testing'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: rootskel-gtk
Source-Version: 12.0.3
Done: Holger Wansing 

We believe that the bug you reported is fixed in the latest version of
rootskel-gtk, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1036...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated rootskel-gtk package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Jun 2024 21:09:50 +0200
Source: rootskel-gtk
Architecture: source
Version: 12.0.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 787279 1036886
Changes:
 rootskel-gtk (12.0.3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Philip Hands ]
   * prevent screen blanking under X (closes: #787279)
 .
   [ Samuel Thibault ]
   * Dark theme: Set background as dark, so that text input fields actually
 show up (Closes: #1036886)
Checksums-Sha1:
 03b2a7010d6c484dd47fbfd8b9c52f392f05dc9f 1721 rootskel-gtk_12.0.3.dsc
 19807d6db26b68ed1c65b9490d52f46b39b733a7 30368 rootskel-gtk_12.0.3.tar.xz
 b64705cd5fa8b2bbffb62bf10214f859a937fdcd 7372 
rootskel-gtk_12.0.3_amd64.buildinfo
Checksums-Sha256:
 efe35d14b78646d8fcb5daba969e50ee90f37811a74ef8158436219b03d359bc 1721 
rootskel-gtk_12.0.3.dsc
 845ae93b2b9f4e2338b94c50f7f8906f1c4cc3d9160c03efed3c7c735992bed3 30368 
rootskel-gtk_12.0.3.tar.xz
 1febe93772062ebb134eddadb137e125a866e83089396b442ca3aa62174de1f3 7372 
rootskel-gtk_12.0.3_amd64.buildinfo
Files:
 46e34cea606699638e9810e2fce0e774 1721 debian-installer optional 
rootskel-gtk_12.0.3.dsc
 cbb6ee5d7195d66cd9f65e3be6cd33b1 30368 debian-installer optional 
rootskel-gtk_12.0.3.tar.xz
 a6594c54560e5b3e16b08ab5aa6e3269 7372 debian-installer optional 
rootskel-gtk_12.0.3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZiEvgVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2xDEP/AgF/4dwRARTMOEsGA/R4pb1h4Cu
4OcX6+gtU2LK/bwyltgQx8V60QkgzfAEhm+razPQktTpiVGPAYCt4K9UdxfQ2Xcc
yVS4DzfcJ/tvKaY4efkX93rZf47YZHOEGOp3BTDw/gs+ptW0karEFvGldYf7TBsE
DwYFQYWgTf+hDJoZKeQN0Nec9BVKq5Y8rud9zPVZ36TqR66d0DhGDAlkRDFuw7xR
bpjKPJxWpqZ/nc0f/e5Aw+TzJ8Fy1Uml9GzgwPFe4iO5vOv0AKYNNUkcFMTtVZ76
qVR1FpTjPcjpDU0USM7WE4t3M++vW6dRHaUTmZ7aekunsBaAZN78W8li5jWiw0Q0
hQHeAquVbtkfBCW3IkDWX355p3PFZk+OqF2vrWWXuTn9uKvUyH6JkR41oaxsScow
q8g9xn+jj5cKshsqgkRFqeiWGiJpYDHOWUZ58sqpQrewa7aIbIFQpJZsZIczIdHf
Y+A1s+89/4tldW6I4NEjKeUXrnxExCvA7dAX1FRAqvx9tBr2L2Se5rq5kfQyr+od

rootskel-gtk_12.0.3_source.changes ACCEPTED into unstable

2024-06-06 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Jun 2024 21:09:50 +0200
Source: rootskel-gtk
Architecture: source
Version: 12.0.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 787279 1036886
Changes:
 rootskel-gtk (12.0.3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Philip Hands ]
   * prevent screen blanking under X (closes: #787279)
 .
   [ Samuel Thibault ]
   * Dark theme: Set background as dark, so that text input fields actually
 show up (Closes: #1036886)
Checksums-Sha1:
 03b2a7010d6c484dd47fbfd8b9c52f392f05dc9f 1721 rootskel-gtk_12.0.3.dsc
 19807d6db26b68ed1c65b9490d52f46b39b733a7 30368 rootskel-gtk_12.0.3.tar.xz
 b64705cd5fa8b2bbffb62bf10214f859a937fdcd 7372 
rootskel-gtk_12.0.3_amd64.buildinfo
Checksums-Sha256:
 efe35d14b78646d8fcb5daba969e50ee90f37811a74ef8158436219b03d359bc 1721 
rootskel-gtk_12.0.3.dsc
 845ae93b2b9f4e2338b94c50f7f8906f1c4cc3d9160c03efed3c7c735992bed3 30368 
rootskel-gtk_12.0.3.tar.xz
 1febe93772062ebb134eddadb137e125a866e83089396b442ca3aa62174de1f3 7372 
rootskel-gtk_12.0.3_amd64.buildinfo
Files:
 46e34cea606699638e9810e2fce0e774 1721 debian-installer optional 
rootskel-gtk_12.0.3.dsc
 cbb6ee5d7195d66cd9f65e3be6cd33b1 30368 debian-installer optional 
rootskel-gtk_12.0.3.tar.xz
 a6594c54560e5b3e16b08ab5aa6e3269 7372 debian-installer optional 
rootskel-gtk_12.0.3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZiEvgVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2xDEP/AgF/4dwRARTMOEsGA/R4pb1h4Cu
4OcX6+gtU2LK/bwyltgQx8V60QkgzfAEhm+razPQktTpiVGPAYCt4K9UdxfQ2Xcc
yVS4DzfcJ/tvKaY4efkX93rZf47YZHOEGOp3BTDw/gs+ptW0karEFvGldYf7TBsE
DwYFQYWgTf+hDJoZKeQN0Nec9BVKq5Y8rud9zPVZ36TqR66d0DhGDAlkRDFuw7xR
bpjKPJxWpqZ/nc0f/e5Aw+TzJ8Fy1Uml9GzgwPFe4iO5vOv0AKYNNUkcFMTtVZ76
qVR1FpTjPcjpDU0USM7WE4t3M++vW6dRHaUTmZ7aekunsBaAZN78W8li5jWiw0Q0
hQHeAquVbtkfBCW3IkDWX355p3PFZk+OqF2vrWWXuTn9uKvUyH6JkR41oaxsScow
q8g9xn+jj5cKshsqgkRFqeiWGiJpYDHOWUZ58sqpQrewa7aIbIFQpJZsZIczIdHf
Y+A1s+89/4tldW6I4NEjKeUXrnxExCvA7dAX1FRAqvx9tBr2L2Se5rq5kfQyr+od
J75xpIZCzyaDJrneHuaCKrlHrBxOjr5/a3AyoENZefwT3TxWL6yRhAFx/TSlSdhE
2k+dxE2tPVc+D1Plthg+7hdZIeGbr9O5btOkKn8Cy3+HcDFoBkUojA1hmOJsjS4D
EUorCx7WarAK9cb1
=NAav
-END PGP SIGNATURE-



pgpoqJRkcFhXr.pgp
Description: PGP signature


Processing of os-prober_1.82_source.changes

2024-06-06 Thread Debian FTP Masters
os-prober_1.82_source.changes uploaded successfully to localhost
along with the files:
  os-prober_1.82.dsc
  os-prober_1.82.tar.xz
  os-prober_1.82_amd64.buildinfo

Greetings,

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



os-prober_1.82_source.changes ACCEPTED into unstable

2024-06-06 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Jun 2024 22:08:08 +0200
Source: os-prober
Architecture: source
Version: 1.82
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 os-prober (1.82) unstable; urgency=medium
 .
   * Team upload
 .
   [ Philip Hands ]
   * Switch to using default branch2repo for salsa-CI.
   * Refactor windows version detection (+ adding ver 12).
 .
   [ Samuel Thibault ]
   * Make gbp tag produce the right tag format.
Checksums-Sha1:
 b878d5908c31a0360c0496cc8844c836601e36f7 1734 os-prober_1.82.dsc
 3d3fe0601115c687f35c2f47726bbccc6221d176 27596 os-prober_1.82.tar.xz
 9d8710b6d2dd9f7b7adf98ee0e1d0e0fffc3530b 6506 os-prober_1.82_amd64.buildinfo
Checksums-Sha256:
 528eec2bc8079567e6f6a85fe5572d9ae0a0b8e96e45f32caad68ac38e7bc3dd 1734 
os-prober_1.82.dsc
 3244125405c44f038b5299312f52dcf826a0d531e1ab97ec749a656d2886cf6e 27596 
os-prober_1.82.tar.xz
 1ee9e8f7cf3ed209e89b265648b3c17cef0bb45e01fb1a2ec8862500511eb40a 6506 
os-prober_1.82_amd64.buildinfo
Files:
 38c77b47b676c19c692c38f60a0ef0cb 1734 debian-installer optional 
os-prober_1.82.dsc
 f970156e641123bfe6065f17e945b087 27596 debian-installer optional 
os-prober_1.82.tar.xz
 d79d7743fe244341acabbb1a3803f4cb 6506 debian-installer optional 
os-prober_1.82_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZiGbQVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2FF8QAJBPS8tSidpwvw1lFR1/TqsnwQ90
Bfel/IMPzUm7pnne532ENcEM7WKZcIT/I/SMs3QyPJn1TwRNbLRBVhaj8uDAXkKq
ermUB2CWp8qP2PP1xghIOoKZPw1jDOY3Q9MP7lI/7UV/z2rX00NQxpKxXh7X0U9j
4m6KQCOE47ndjBRoghIf/dKcgkIGxatUo2MphgQjGRt07bGhhYNrjbfREUNEtW/E
swYOiWxFwQ5mS8zHtvH/YqDfRsgli63zJl/j5uNmxrgPymL9SklXk+MDYffsq+CR
Tjr5m8kebhCja4NtQi33vVMAUnJtYl+2roj1LkX8wfVw09iyrFezknAjotHDjqVZ
BKLqFEvI8Jao8sFHkME7ZaSoFEIoHz9tijp4PEl6P3W64Tf1gD8r5EdWrOh0i+kk
/xSBs/TwDf9tpnJAGIMA8+KQCY4dBBvb9SPSeQiKYpKSfTvBBWKt1SeX02/Tluhb
Rvtf1hWe4LG4DXwuESOok0VS0dvSdKA4K1FjfmuSh4g4QIybwwBXobD1aXYyV4Ga
Hc+TUAJ5WqITxwzvwaT5LTlrNMr45Rr1wZRCksxjBg5Zp48NHr+h5HrCpCMBrBgm
HzkFCz7CHusikpt0MkAR/U0RpQFq144uAc2/W1L7VXFYil9IYPoj0B1j9F3pl3pu
inhnxayjqrX2KGuI
=45ku
-END PGP SIGNATURE-



pgpPbERUgBPrh.pgp
Description: PGP signature


mountmedia_0.27_source.changes ACCEPTED into unstable

2024-06-06 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Jun 2024 22:01:08 +0200
Source: mountmedia
Architecture: source
Version: 0.27
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 mountmedia (0.27) unstable; urgency=medium
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster (oldstable):
 + Build-Depends-Indep: Drop versioned constraint on dpkg-dev and 
po-debconf.
 + mountmedia: Drop versioned constraint on di-utils in Depends.
   * Bump debhelper from deprecated 9 to 13.
   * Set debhelper-compat version in Build-Depends.
Checksums-Sha1:
 e94f69111d06c4d54a0bd92c63c5ed140f806d62 1605 mountmedia_0.27.dsc
 755ef8eccd73a60831625c3ab1a3ca331d1804f5 5812 mountmedia_0.27.tar.xz
 fc026f140baf325bc3375b2fd0b7bb9168eb282d 5970 mountmedia_0.27_amd64.buildinfo
Checksums-Sha256:
 b0067bb56ebafbc2c494cec9b79e0c64fe83b59620cb2cc31a4e22173bf2ccef 1605 
mountmedia_0.27.dsc
 2831977ad9986bfb2a659637658f6dc1e98f50b0bacf2093c8f9b5db7583a40e 5812 
mountmedia_0.27.tar.xz
 14255e82b0fb58aab2da4ae750632151f9b1be9f5aa9e73666fe79fec81839b4 5970 
mountmedia_0.27_amd64.buildinfo
Files:
 f031c2c0a91b402b145688f598e0668f 1605 debian-installer optional 
mountmedia_0.27.dsc
 d37ff1de7b4ebf3ea8770870b3e2cd90 5812 debian-installer optional 
mountmedia_0.27.tar.xz
 563427505a54b21986664e3c783c4b12 5970 debian-installer optional 
mountmedia_0.27_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZiFnYVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2EWIP/ReeE4HRswKjxC4w+4sJYW340L7v
uWcTpriI+4Ae9fQzZZEuqzBAAdPF2GwKtNAFJ6/8Je67tXIeNl6J1NY7HEFYVlKx
3rpIMQ/jCw17PWneMgyc+3FfHgI5wTUwhj/WMEzc2QKrUPNHlQRLLUhvwcCfskFK
Stn8zRDlBfX5l9ZngCzD/UhzrK+Epy3cDLUTwhwtojDWJ41gtkC7Yp4dF5dgMQrC
q/AjSHlLbWm1YUXGNrXYYdcvfV2sLFNq2GZkyACYdAJM9mlrLZIy7Xv/ub4/IWV2
dWLCPKW1sb5JPTNQlnhCh4SSUKxyyQFZfYGV2Ou+zSb+z0s/MKDP3DHzuUJz7A9w
k7LEH5qT6PkDQObGr0QXIkpnWGqVeHTAD9NMCBeAs+q3LDK9e2FXhmG/odWv+Exa
t8f3zHZuwMzdNFMDn8oSgCIm/WIBJ1NorwK8e/NK6AxV1on35ar0Lus0jq1OtP9h
M4CIlNJNJMN8GDcixpsrxIn2iyNi588fjNRozNuYeKiJRIefYLkXe7IlmPNxaElU
2gazdRMC5HIn6ncj8QlgXtb9Y4lF93zLXK0zQiUezS6hmlWDK2xP3wtkMsRszex5
9g0ZQ82+rg0Llh/X+GtfmA7Chk89Jyw0GWn4L4kHeIkr4eZCeLdfKBw4IYqyAET8
rY1UiLHtJlXK59+s
=tLnC
-END PGP SIGNATURE-



pgpmAU9_yfCmT.pgp
Description: PGP signature


Processing of mountmedia_0.27_source.changes

2024-06-06 Thread Debian FTP Masters
mountmedia_0.27_source.changes uploaded successfully to localhost
along with the files:
  mountmedia_0.27.dsc
  mountmedia_0.27.tar.xz
  mountmedia_0.27_amd64.buildinfo

Greetings,

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



Processing of rootskel-gtk_12.0.3_source.changes

2024-06-06 Thread Debian FTP Masters
rootskel-gtk_12.0.3_source.changes uploaded successfully to localhost
along with the files:
  rootskel-gtk_12.0.3.dsc
  rootskel-gtk_12.0.3.tar.xz
  rootskel-gtk_12.0.3_amd64.buildinfo

Greetings,

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



Re: Contacting Debian Boot team

2024-06-06 Thread Andreas Tille
Hi Holger,

Am Thu, May 30, 2024 at 04:48:17PM +0200 schrieb Holger Wansing:
> Andreas Tille  wrote (Sun, 26 May 2024 11:31:24 +0200):
> >   - Do you feel good when doing your work in Debian Boot team?
> 
> While I have to admit that I'm mostly doing just the simple things :-)

I consider this a weak excuse.  While I'm known for lots of uploads and
bug fixes I'm so happy that people do not go and check how many low
hanging fruits of bugs with patches and semi-automated upgrades are
amongst those.  Doing the simple things (but doing them right) is very
much part of the job and I'm happy we have people doing these.

As I previously said in the "Blends in D-I" suggestion I'm extremely
thankful for your work and its far from simple since that issue is
nearly 20 years old and nobody else (including me) found some acceptable
solution for it.  Thanks again for this!

> I consider myself being only a small candle on the cake.
> Being not a programmer, I don't do difficult or critical changings most of
> the time, so relaxed gaming here ;-)

Good that you are considering your volunteer time relaxed.
 
> >   - Do you consider the workload of your team equally shared amongst its
> > members and who actually is considered a team member?  (I added some
> > persons in CC who have recently answered to questions on the mailing
> > list.)
> 
> My impression is, that kibi might be kind of overloaded (at least some time),
> since he's the mainly active part, when it comes to the "difficult or
> critical things", which I leave around ...
> (and his answer to this survey confirms this)
> But I cannot see what I can do against this :-( (see below)
> 
> (ok, that's not strictly correct generally, there are some people taking care
> of specific packages, taking workload from kibi's shoulders, but that's not
> for the majority of packages)

I think I've spotted some instance of the reason which finally motivated
me to do this team contacts:  For a long time I have the impression that
Debian is driven by several "one-person-teams" (to varying extend of the
one person influence and tendency to burn out).  I see my task as DPL in
trying to find means to help on this front.  I'm just making some note in
my Bits from DPL draft that Debian Boot team might need some help - other
ideas how to attract new contributors are welcome.

> >   - Do you have some strategy to gather new contributors for your team?
> 
> Since I lack the skills to lead new contributors into doing the difficult
> or critical things from above (where we would mostly need more manpower,
> if at all), I'm a bit lost here ...

Attracting people to the things you are doing might help anyway.

> >   - Can you give some individual estimation how many hours per week you
> > are working on your tasks in youre team?  Does this fit the amount of
> > time you can really afford for this task?
> 
> This ranges from zero to 5-10 hours per week, depending on variables like
> the state of development cycle of release (when the next release comes
> nearer, I try to get missing translation updates, which leads to more
> commits and uploads, as an example).
> And: I'm fine with this time effort.

Sounds good and healthy.

> >   - I recently had some discussion on Chemnitzer Linuxtage what might
> > be the reason for derivatives to write their own installers.  While
> > I'm personally perfectly happy with the way I can install Debian I'm
> > somehow wondering why others are spending time into a problem we
> > are considering "solved" and whether we can learn something from this,
> 
> That was often mentioned, and the arguments for the Debian Installer was the 
> broader range of architectures, and as well as the support for older hardware.
> You can easily create a nicer installer, if you develop from scratch for only
> a small variety of up-to-date devices.
> 
> OTOH since Buster we have the Calamares installer on the live images as well,
> to serve such approaches.
> The idea behind the Calamares installer is exactly that: develop a framework,
> which can be used to install a variety of distributions, to solve those
> distributions from developing their own installer.

Ahhh, I was not aware that Calamares is actually what I get when I select
live installer.  Thank you for the clarification.

> So I think we are on a not that bad position here ... (?)

I never said we are bad.  I was simply wondering why derivatives do extra
work.
 
> >   - I once had a amr64 based laptop (Pinebook) and had to learn that I
> > can't use the Debian installer which was frustrating.  I was told
> > that this is the case for hardware that is not featuring some BIOS-like
> > boot system.  Do you see any chance to let the installer work for
> > non-Intel architectures (or should I rather ask this question on
> > Debian CD (sorry for my ignorance if I miss responsibility here.)
> >   - Can I do anything for you?
> 
> I guess most teams are undermanned in 

Re: Contacting Debian Boot team

2024-06-06 Thread Andreas Tille
Hi Phil,

Am Mon, May 27, 2024 at 12:15:47AM +0200 schrieb Philip Hands:
> This is mostly because I found that I wasn't able to devote the time
> required to test things to my satisfaction when my first daughter came
> along,

So we will see you back in the team once your youngest child is around
10 or so. ;-P

> as I'd be distracted before I completed my tests, so I decided to
> do something about automating testing, and I've been down that rabbit
> hole ever since.  When I'm working on that, I'm pretty happy.

Good!  Keep on working with that. ;-)
 
> I'd say that that work is now bearing some fruit, finally.  I had
> originally hoped that I'd then be able to put more effort into D-I
> itself, but I suspect that maintaining openQA and the Salsa pipeline
> stuff may continue to eat a fair amount of my time.

Sounds like a pretty interesting project.  Thanks for keeping me
informed about this.
 
> >   - Do you consider the workload of your team equally shared amongst its
> > members and who actually is considered a team member?  (I added some
> > persons in CC who have recently answered to questions on the mailing
> > list.)
> 
> My contributions are pretty-much background noise recently, so I guess
> that means that the load is very unequal if you were including me in the
> stats.
> 
> Cyril has been responsible for keeping D-I viable in recent times, and
> Holger also does _loads_ of (mostly translation related) work too.

I highly appreciate all responses from Debian Boot team which are the
most extensive so far.
 
> >   - Do you have some strategy to gather new contributors for your team?
> 
> One of my intentions with the salsa/openQA work is that I'm trying to
> make it possible for people to make simple changes to bits of D-I and
> have them receive feedback about whether the result is an improvement.
> 
> Hopefully that will lower the bar to new people contributing.

Very nice contribution!
 
> >   - Can you give some individual estimation how many hours per week you
> > are working on your tasks in youre team?  Does this fit the amount of
> > time you can really afford for this task?
> 
> My work on D-I is pretty sporadic, because I generally pick some small
> thing in D-I to use as a test of the current salsa/openqa setup, and
> then spend significantly more time sorting out some new wrinkle that's
> revealed in the salsa and/or openqa setup by this new example.
> 
> Often this means that by the time I've finished, someone else has
> already dealt with the original bug/patch in D-I. I'm not sure to what
> extent that counts as D-I work, but I'm happy with the time I spend on
> it.

OK
 
> >   - I recently had some discussion on Chemnitzer Linuxtage what might
> > be the reason for derivatives to write their own installers.  While
> > I'm personally perfectly happy with the way I can install Debian I'm
> > somehow wondering why others are spending time into a problem we
> > are considering "solved" and whether we can learn something from this,
> 
> I quite like it as it is, but I'm sure many would not find the installer
> particularly pretty, and it is quite hard to work on (being in busybox
> shell, and lacking popular things like python), and I personally have no
> idea how easy/possible it is to e.g. change its branding (if a
> downstream wanted to do that).
> 
> If one doesn't care about installing on our minority architectures, then
> it's possible to do something that's much easier to work on by booting a
> live image. One can then have something that'll ask all the questions
> up-front (especially if one is opinionated about what should be on the
> resulting system), and then apply that to the system without further
> interaction.

Would you agree to the statement I'm drawing from past discussion:
Debian has to care for working installer on all architectures.  Debian
derivatives do not have this requirement and prefer other pretty / fancy
/ brandable ways over the Debian one?

> Some arm64 things certainly can be installed with D-I, because I have
> openQA workers running on altra.debian.net testing D-I installs, but I
> don't know that much about the details.

OK
 
> >   - Can I do anything for you?
> 
> I'm currently looking into the options that might be worth exploring for
> getting more openqa-workers running.  I suppose at some point that might
> involve asking for funds to be spent, but I'm not at that stage yet.

If you have some ideas whom to ask and reasons to motivate them for X
amount to spent I'd happily support you in this.

> It probably wouldn't harm to offer some funding to osuosl, because they
> let us use their systems for various things and making sure that they
> are sustainable would be wise. (that's who host most of what I'm running
> openqa on at present, and they also host jenkins and reproducible things
> AFAIK)

If you want to go into more detail (if you consider in private might be
better that's fine) I can talk with 

Re: Contacting Debian Boot team

2024-06-06 Thread Andreas Tille
Hi,

Am Fri, May 31, 2024 at 04:54:13PM +0200 schrieb Cyril Brulebois:
> > However, my question was rather whether you know some valid reasons
> > why derivatives are exchanging the install method - maybe that
> > question should be better asked on Debian-Boot (if so feel free to
> > ignore this question).  I was rather wondering about the motivation
> > for the usage of Ubiquity or Calamares (or others?).  I might be naive
> > but from my perspective installing is something that just needs to
> > work and having a lot of ways to make this working is somehow burning
> > developer time.  So what according to your insight is motivating
> > derivatives to solve a problem in a different way that is IMHO solved
> > by Debian.
> 
> You seem to be asking the wrong person. I don't know about downstream's
> motivation, the various alternatives/competitors, etc., and I wouldn't
> have time to investigate if I wanted to (and I'm not saying that's the
> case).

Fair enough.
 
> > Sure there is an arm64 image and I started with copying this to some
> > USB stick.  But that hardware did not booted from an USB device but
> > only from eprom that had to be flashed via SD card.  Its not your
> > fault definitely but was frustrating for me not beeing able to simply
> > run the Debian installer.
> 
> I understand the frustration (“welcome to the ARM world…”) but (1) the
> initial statements were a very wrong conclusion from your findings and
> (2) even with hardware that's supposed to be supported by free software
> we might need time to spot, fix, or workaround bugs (hardware, software,
> firmware, doc, etc.) or integrate new features to support new boards.
> 
> That's not specific to d-i, that's just how IT works.

ACK.
 
> > It was not really a claim but a question based on my experience with a
> > single piece of hardware.  I was hoping for some ideas how we could
> > motivate hardware vendors to deliver hardware that can be easily
> > booted by simply plugging in some USB device featuring the installer
> > images we provide on our web page.
> 
> UEFI/arm64 is a thing. Whether HW vendors actually implement/enable UEFI
> is another matter entirely (see early EEPROM versions on e.g. Pi 4).

Any experiences with Lenovo Thinkpad X13S?  Finally Lenovo is present on
DebConfs and we can talk to them.  Just from reading[1] it seems to be
what I'm looking for in principle - provided they might unbundle Win11
from it and I can just plugin the Debian installer USB to install
Debian.
 
Kind regards
   Andreas.

[1] https://www.theregister.com/2023/09/08/linux_on_the_thinkpad_x13s/

-- 
https://fam-tille.de



Re: Grub error on an installed system

2024-06-06 Thread Pascal Hambourg

On 06/06/2024 at 12:35, darkpenguin wrote:


Harmless messages are fine, but what could be taking about 4 seconds of
waiting at "Welcome to GRUB!" before the menu? Is there any way to find out?


You can try adding 'set debug=all' and 'echo ' commands in 
/boot/efi/EFI/debian/grub.cfg and /boot/grub/grub.cfg.




Re: Grub error on an installed system

2024-06-06 Thread darkpenguin
Thanks for the info! So it won't be in Bookworm then, but should be
there right after.

Harmless messages are fine, but what could be taking about 4 seconds of
waiting at "Welcome to GRUB!" before the menu? Is there any way to find out?


On 06/06/24 14:30, Pascal Hambourg wrote:
> On 06/06/2024 at 11:51, darkpenguin wrote:
>>
>> On a new Bookworm installation I see a new issue: before grub-efi shows
>> the menu, it pauses for a whole few seconds on "Welcome to GRUB!", and
>> then flashes an error for a split second:
>>
>> error: no such device: /.disk/info
>> error: no such device: /.disk/mini-info
> 
> These (harmless) messages are caused by the early grub.cfg embedded in 
> the monolithic EFI GRUB image memdisk, which was originally designed for 
> installation media. It has been removed since version 2.06-14 when the 
> FAT memdisk image was replaced with a SquashFS one.
> 
> 
> 



Re: Grub error on an installed system

2024-06-06 Thread Pascal Hambourg

On 06/06/2024 at 11:51, darkpenguin wrote:


On a new Bookworm installation I see a new issue: before grub-efi shows
the menu, it pauses for a whole few seconds on "Welcome to GRUB!", and
then flashes an error for a split second:

error: no such device: /.disk/info
error: no such device: /.disk/mini-info


These (harmless) messages are caused by the early grub.cfg embedded in 
the monolithic EFI GRUB image memdisk, which was originally designed for 
installation media. It has been removed since version 2.06-14 when the 
FAT memdisk image was replaced with a SquashFS one.






Grub error on an installed system

2024-06-06 Thread darkpenguin
Hello!

(I'm not sure where should I go with this, but seems like it's about
"Debian boot" and likely has something to do with the installer.)

On a new Bookworm installation I see a new issue: before grub-efi shows
the menu, it pauses for a whole few seconds on "Welcome to GRUB!", and
then flashes an error for a split second:

error: no such device: /.disk/info
error: no such device: /.disk/mini-info

Trying to find any information about this, the only thing I've found is:

https://unix.stackexchange.com/questions/753732/what-does-grub-error-no-such-device-disk-info-mean-and-how-to-fix-it

So this is likely not for the upstream grub, but for the Debian
adaptation of grub.


I've tried to fix it for a while, and now I'm not sure if the error is
still there, because it flashes so quickly. But a significant
multiple-second delay on "Welcome to GRUB!" on a very modern PC is
definitely there. Is there a way to see the logs from this stage of grub
loading?


(Please CC me - I'm not on the list)

-- 
darkpenguin



Processed: reassign Bug#1071927 (discover: Discover displaying packages wrong) to plasma-discover

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1071927 plasma-discover 5.27.5-2
Bug #1071927 [discover] discover: Discover displaying packages wrong.
Bug reassigned from package 'discover' to 'plasma-discover'.
No longer marked as found in versions discover/2.1.2-10.
Ignoring request to alter fixed versions of bug #1071927 to the same values 
previously set
Bug #1071927 [plasma-discover] discover: Discover displaying packages wrong.
Marked as found in versions plasma-discover/5.27.5-2.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1071927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: reassign 1072574 to src:linux, downgrade severity

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1072574 src:linux
Bug #1072574 [kernel-wedge] kernel-wedge: Enable Renesas RZ/G3S and RZ/V2H 
boards
Bug reassigned from package 'kernel-wedge' to 'src:linux'.
Ignoring request to alter found versions of bug #1072574 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1072574 to the same values 
previously set
> severity 1072574 wishlist
Bug #1072574 [src:linux] kernel-wedge: Enable Renesas RZ/G3S and RZ/V2H boards
Severity set to 'wishlist' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1072574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1036315: rootskel-gtk: Alpha/missing pixels on the borders of the PNG banner

2024-06-05 Thread Roland Clobus

Control: tags +patch

Hello maintainers of rootskel-gtk,

On Fri, 19 May 2023 10:58:35 +0200 Cyril Brulebois  wrote:

When building the package on bullseye, I'm getting transparency on both
left and right borders. When building it on sid, I'm get that at the
bottom. It would be great if we had some better or at least reproducible
export.


In the file `build/config/x86.cfg`, rsvg-convert is called without 
additional options.
If the option `--background-color black` is used, all transparency will 
be pre-rendered and the image will have no transparency left.


The colour black would be suitable, since that would match the 
'nothingness' at the border of the screen.


The slight stretching of the svg image in [1] could then be reverted.

Old:
rsvg-convert $(SPLASH_SVG) > $(SPLASH_PNG);
New:
rsvg-convert --background-color black $(SPLASH_SVG) > $(SPLASH_PNG);


With kind regards,
Roland Clobus

[1] 
https://salsa.debian.org/installer-team/debian-installer/-/commit/698311cb81e26512a86a7b94682367cd047f491c


OpenPGP_signature.asc
Description: OpenPGP digital signature


Processed: Fixed in git, needs a release

2024-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 787279 +pending
Bug #787279 [rootskel-gtk] Cannot disable screen blanking with Jessie preseed 
installation
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
787279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Re: Planning for 12.6/11.10

2024-06-04 Thread Adam D. Barratt
press@ - please could you comment on the dates proposed below

Thanks,

Adam

On Mon, 2024-05-27 at 13:07 +0100, Jonathan Wiltshire wrote:
> Hi,
> 
> The final bullseye point release 11.10 (and therefore also 12.6 for
> versioning) should be soon after 10th June, when security team
> support
> will end.
> 
> Please indicate availability for:
> 
>   Saturday 15th June
>   Saturday 22nd June
>   Saturday 29th June
> 
> Thanks,
> 



Bug#1072574: kernel-wedge: Enable Renesas RZ/G3S and RZ/V2H boards

2024-06-04 Thread John
Package: kernel-wedge
Severity: important
Tags: d-i
X-Debbugs-Cc: john.vincent...@bp.renesas.com

Dear Maintainer,

Please enable Renesas RZ/G3S and RZ/V2H device support in Debian by updating 
the following configurations:

CONFIG_ARCH_R9A09G057=y #RZ/V2H
CONFIG_ARCH_R9A08G045=y #RZ/G3S

Best Regards
John

-- System Information:
Debian Release: 11.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 
'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-30-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kernel-wedge depends on:
pn  debhelper  
ii  make   4.3-4.1

kernel-wedge recommends no packages.

kernel-wedge suggests no packages.



Bug#1072562: console-setup-linux: /etc/init.d/keyboard-setup.sh needs mountkernfs, not in dependencies

2024-06-04 Thread Erwan David
Package: console-setup-linux
Version: 1.227
Severity: normal


When upgrading, I get following error message:
Setting up: console-setup-linux (1.227)
insserv: FATAL: service mountkernfs has to be enabled to use service 
keyboard-setup.sh

I see that /etc/init.d/keyboard-setup.sh has
# Required-Start:mountkernfs

mountkernfs is in initscripts package, but console-setup.sh does not depends on
it.
So either this Required-Start should be removed, either the dependency should be
added.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'stable-security'), (600, 'unstable'), 
(500, 'stable-updates'), (500, 'proposed-updates'), (400, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.66
ii  kbd 2.6.4-2
ii  keyboard-configuration  1.227

console-setup-linux recommends no packages.

Versions of packages console-setup-linux suggests:
ii  console-setup  1.227

Versions of packages keyboard-configuration depends on:
ii  debconf [debconf-2.0]   1.5.86
ii  liblocale-gettext-perl  1.07-7
ii  xkb-data2.41-2

Versions of packages console-setup depends on:
ii  debconf [debconf-2.0]   1.5.86
ii  keyboard-configuration  1.227
ii  xkb-data2.41-2

Versions of packages console-setup suggests:
ii  locales2.38-11
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.09-1

Versions of packages console-setup-linux is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.6.4-2
ii  systemd   256~rc3-7

-- debconf information:
* keyboard-configuration/model: Generic 105-key PC
  debian-installer/console-setup-udeb/title:
* console-setup/fontsize-text47: 8x16
* keyboard-configuration/layout:
* keyboard-configuration/variant: French - French (legacy, alt.)
  keyboard-configuration/unsupported_layout: true
* keyboard-configuration/other:
* console-setup/fontsize-fb47: 8x16
* keyboard-configuration/toggle: No toggling
* console-setup/charmap47: UTF-8
* keyboard-configuration/ctrl_alt_bksp: false
* keyboard-configuration/altgr: The default for the keyboard layout
* keyboard-configuration/layoutcode: fr
* keyboard-configuration/variantcode: latin9
* keyboard-configuration/modelcode: pc105
  keyboard-configuration/unsupported_config_layout: true
  console-setup/use_system_font:
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
* console-setup/store_defaults_in_debconf_db: true
* keyboard-configuration/xkb-keymap: fr(latin9)
  console-setup/framebuffer_only:
* keyboard-configuration/optionscode:
* console-setup/fontsize: 8x16
  console-setup/guess_font:
* console-setup/codesetcode: Lat15
* keyboard-configuration/compose: No compose key
* keyboard-configuration/store_defaults_in_debconf_db: true
* keyboard-configuration/switch: No temporary switch
  keyboard-configuration/unsupported_config_options: true
* console-setup/fontface47: Fixed
  keyboard-configuration/unsupported_options: true



Re: Adding systemd-boot support in debian-installer

2024-06-03 Thread John Paul Adrian Glaubitz
On Mon, 2024-06-03 at 20:18 +0100, Luca Boccassi wrote:
> > Hmm? Did we get rid of supporting the installation of systems without
> > a bootloader? I found this very handy when installing on systems that
> > don't support standard bootloaders or when installing inside QEMU and
> > then booting kernel and initrd from the command line.
> > 
> > Is there anything broken in nobootloader?
> 
> No, they were referring to some copypasta in the new package - I
> started by copying the nobootloader sources because I'm lazy AF, but
> forgot to sed s/nobootloader/systemd-boot-installer/ one PO file.

OK, thanks for the clarification.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: Adding systemd-boot support in debian-installer

2024-06-03 Thread Luca Boccassi
On Mon, 3 Jun 2024 at 20:07, John Paul Adrian Glaubitz
 wrote:
>
> Hello,
>
> On Mon, 2024-06-03 at 03:46 +0200, Cyril Brulebois wrote:
> > ACK on the .mrconfig part, but I think this misses an addition to
> > packages/po/packages_list (to be confirmed with Holger Wansing). Might
> > be best to get rid of the fuzzy parts still mentioning nobootloader
> > beforehand though. Just something that needs taken care of at some
> > point.
>
> Hmm? Did we get rid of supporting the installation of systems without
> a bootloader? I found this very handy when installing on systems that
> don't support standard bootloaders or when installing inside QEMU and
> then booting kernel and initrd from the command line.
>
> Is there anything broken in nobootloader?

No, they were referring to some copypasta in the new package - I
started by copying the nobootloader sources because I'm lazy AF, but
forgot to sed s/nobootloader/systemd-boot-installer/ one PO file.



Re: Adding systemd-boot support in debian-installer

2024-06-03 Thread John Paul Adrian Glaubitz
Hello,

On Mon, 2024-06-03 at 03:46 +0200, Cyril Brulebois wrote:
> ACK on the .mrconfig part, but I think this misses an addition to
> packages/po/packages_list (to be confirmed with Holger Wansing). Might
> be best to get rid of the fuzzy parts still mentioning nobootloader
> beforehand though. Just something that needs taken care of at some
> point.

Hmm? Did we get rid of supporting the installation of systems without
a bootloader? I found this very handy when installing on systems that
don't support standard bootloaders or when installing inside QEMU and
then booting kernel and initrd from the command line.

Is there anything broken in nobootloader?

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#1072526: netcfg removes DHCP ipv6 addresses after configuration finishes

2024-06-03 Thread Steffen Kieß

Package: netcfg
Version: 1.187

When netcfg is finished configuring the interface, it will call 
kill_dhcp_client() (from netcfg_activate_dhcp()), which will send 
SIGTERM and then SIGKILL to dhcp6c. When dhcp6c gets a SIGTERM, it will 
send a DHCP6 Release message and remove the IP from the interface, which 
means that the installer will have no (public) IP anymore, and 
installation from network will fail.


This happens both in an IPv6-only and in a dual-stack configuration 
(though in a dual-stack configuration there still will be an IPv4 
address, which means the installation will probably succeed).


A possible workaround is to switch to another console with Alt+F3 after 
the DHCP6 configuration was done but before netcfg finishes and kill the 
dhcp6c process with -9 (to prevent it from releasing the IP).




Bug#1072525: s390x install Debootstrap warning

2024-06-03 Thread Berli Gayathri
Package: installation-reports

When I tried installing  different debian images(buster, bookworm and sid) I 
run into this Problem (from log console ):

in the /var/log/syslog I have seen installation is failing because of packages 
breaking which are not installed yet
May 27 10:02:59 debootstrap: dpkg: error processing package s390-tools 
(--configure):
May 27 10:02:59 debootstrap:  dependency problems - leaving unconfigured
May 27 10:02:59 debootstrap: Errors were encountered while processing:
May 27 10:02:59 debootstrap:  s390-tools
May 27 10:03:00 debootstrap: dpkg: dependency problems prevent configuration of 
s390-tools:
May 27 10:03:00 debootstrap:  s390-tools depends on libcurl4 (>= 7.16.2); 
however:
May 27 10:03:00 debootstrap:   Package l
May 27 10:03:00 debootstrap: ibcurl4 is not installed.
May 27 10:03:00 debootstrap:  s390-tools depends on libfuse2 (>= 2.8); however:
May 27 10:03:00 debootstrap:   Package libfuse2 is not installed.
May 27 10:03:00 debootstrap:
May 27 10:03:00 debootstrap: dpkg: error processing package s390-tools 
(--configure):
May 27 10:03:00 debootstrap:  dependency problems - leaving unconfigured
May 27 10:03:00 debootstrap: Errors were encountered while processing:
May 27 10:03:00 debootstrap:  s390-tools
May 27 10:03:01 debootstrap: dpkg: dependency problems prevent configuration of 
s390-tools:
May 27 10:03:01 debootstrap:  s390-tools depends on libcurl4 (>= 7.16.2); 
however:
May 27 10:03:01 debootstrap:   Package l
May 27 10:03:01 debootstrap: ibcurl4 is not installed.
May 27 10:03:01 debootstrap:  s390-tools depends on libfuse2 (>= 2.8); however:
May 27 10:03:01 debootstrap:   Package libfuse2 is not installed.
May 27 10:03:01 debootstrap:
May 27 10:03:01 debootstrap: dpkg: error processing package s390-tools 
(--configure):
May 27 10:03:01 debootstrap:  dependency problems - leaving unconfigured
May 27 10:03:01 debootstrap: Errors were encountered while processing:
May 27 10:03:01 debootstrap:  s390-tools
May 27 10:45:27 base-installer: error: exiting on error 
base-installer/debootstrap-failed
May 27 10:45:33 main-menu[382]: WARNING **: Configuring 'bootstrap-base' failed 
with error code 1
May 27 10:45:33 main-menu[382]: WARNING **: Menu item 'bootstrap-base' failed.
May 27 10:45:40 main-menu[382]: INFO: Modifying debconf priority limit from 
'high' to 'medium'
May 27 10:45:40 debconf: Setting debconf/priority to medium
May 27 10:45:40 depthcharge-tools-installer: Not installing to non-ChromeOS 
board.
May 27 10:46:59 main-menu[382]: INFO: Menu item 'di-utils-shell' selected



Installation failed in step install base system, not only with the debian 
buster but also with the debian bookworm and the latest sid images as well. The 
link below points to the place from where I picked the images.

https://snapshot.debian.org/archive/debian/20220731T213859Z/dists/bookworm/main/installer-s390x/20210731/images/generic/
https://d-i.debian.org/daily-images/s390x/daily/generic/


The final error message, while installing the Debian from GUI based installer 
is as below.
Warning: Failure while configuring base pacakges. This will be re-attempted up 
to five times.


The same issue I have seen while trying to setup the qemu host on the x86 
architecture for s390x target
$qemu-system-s390x -blockdev 
driver=file,node-name=dasd1,filename=/root/gayathri/LPAR/debian-buster-DI-rc1-s390x-netinst.iso
 -device virtio-scsi -device scsi-cd,drive=dasd1,bootindex=1 -nographic
LOADPARM=[]
Using virtio-scsi.
SCSI CD-ROM detected.
! Cannot IPL this ISO image !

Thanks,
Berli Gayathri.


Re: Adding systemd-boot support in debian-installer

2024-06-03 Thread Luca Boccassi
On Mon, 3 Jun 2024 at 16:11, Holger Wansing  wrote:
>
> Hi,
>
> Am 3. Juni 2024 11:23:57 MESZ schrieb Luca Boccassi :
> >On Mon, 3 Jun 2024 at 02:47, Cyril Brulebois  wrote:
> >> Luca Boccassi  (2024-06-03):
> >>
> >> > https://salsa.debian.org/installer-team/d-i/-/merge_requests/17
> >>
> >> TIL: builscript.
> >>
> >> ACK on the .mrconfig part, but I think this misses an addition to
> >> packages/po/packages_list (to be confirmed with Holger Wansing). Might
> >> be best to get rid of the fuzzy parts still mentioning nobootloader
> >> beforehand though. Just something that needs taken care of at some
> >> point.
> >
> >Ah missed that packages_list - fixed in the latest push
>
> As kibi mentioned, the left-overs from nobootloader should be cleaned up in
> the templates file, so
> s/nobootloader/systemd-boot-installer/

Whoops, forgot to fixup that file, thanks

> and according to
> 
> I would prefer the new message to be sublevel 3, so
> s/# :sl1:/# :sl3:/
>
> before pushing this one.
>
> Otherwise fine I think

Sounds good, will push to main shortly and upload as soon as the
package has cleared NEW. Thanks for the reviews.



Re: Adding systemd-boot support in debian-installer

2024-06-03 Thread Holger Wansing
Hi,

Am 3. Juni 2024 11:23:57 MESZ schrieb Luca Boccassi :
>On Mon, 3 Jun 2024 at 02:47, Cyril Brulebois  wrote:
>> Luca Boccassi  (2024-06-03):
>>
>> > https://salsa.debian.org/installer-team/d-i/-/merge_requests/17
>>
>> TIL: builscript.
>>
>> ACK on the .mrconfig part, but I think this misses an addition to
>> packages/po/packages_list (to be confirmed with Holger Wansing). Might
>> be best to get rid of the fuzzy parts still mentioning nobootloader
>> beforehand though. Just something that needs taken care of at some
>> point.
>
>Ah missed that packages_list - fixed in the latest push

As kibi mentioned, the left-overs from nobootloader should be cleaned up in
the templates file, so
s/nobootloader/systemd-boot-installer/

and according to

I would prefer the new message to be sublevel 3, so
s/# :sl1:/# :sl3:/

before pushing this one.

Otherwise fine I think


Holger


-- 
Sent from /e/ OS on Fairphone3



Re: Planning for 12.6/11.10

2024-06-03 Thread Mark Hymers
On Mon, 27, May, 2024 at 01:07:17PM +0100, Jonathan Wiltshire spoke thus..
> The final bullseye point release 11.10 (and therefore also 12.6 for
> versioning) should be soon after 10th June, when security team support
> will end.
> 
> Please indicate availability for:
> 
>   Saturday 15th June
>   Saturday 22nd June
>   Saturday 29th June

Hi,

I think I can do any of those as long as we lock it in soon so that I
know.

Thanks,

Mark

-- 
Mark Hymers 


signature.asc
Description: PGP signature


Re: Adding systemd-boot support in debian-installer

2024-06-03 Thread Luca Boccassi
On Mon, 3 Jun 2024 at 02:47, Cyril Brulebois  wrote:
>
> Hi,
>
> Luca Boccassi  (2024-06-03):
> > I've created a udeb that adds an expert menu item to allow choosing
> > systemd-boot (in the NEW queue):
> >
> > https://salsa.debian.org/installer-team/systemd-boot-installer
>
> The `Architecture: all` in control vs the 64-bit EFI logic in the script
> seems odd at first glance. Looking at other *-installer, they tend to
> have a restricted arch list in most cases.
>
> I have no strong feelings either way, just something that caught my eye
> when I first looked into the repository.

Given it's only shipping a script I thought it was supposed to be
'all', and also it would avoid the need to conditionalize
dependencies. I can change it if needed, just let me know.

> > A couple of PRs for minimal support:
> >
> > https://salsa.debian.org/installer-team/debian-installer-utils/-/merge_requests/12
>
> OK, spotted the todo in the script when I spotted the upload; a
> versioned dependency will do the trick once the d-i-utils part is
> reviewed/merged/uploaded.
>
> > https://salsa.debian.org/installer-team/d-i/-/merge_requests/17
>
> TIL: builscript.
>
> ACK on the .mrconfig part, but I think this misses an addition to
> packages/po/packages_list (to be confirmed with Holger Wansing). Might
> be best to get rid of the fuzzy parts still mentioning nobootloader
> beforehand though. Just something that needs taken care of at some
> point.

Ah missed that packages_list - fixed in the latest push

> > https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/46
> >
> > It does not show up in non-expert mode, which is fine for now,
> > especially as secure boot signing is not yet available.
> >
> > After it's been in the testing image like this for a while, and after
> > we have secure boot integration finished up, would it be ok to show a
> > question in the non-expert install too? GRUB would still be the
> > default of course, the question would select it by default, and allow
> > to switch to sd-boot if chosen. Where would be the best place to add
> > this?
>
> I have close to no knowledge about the details around menu items at the
> moment. Looking at the good old GRUB vs. LILO duo, I see they had
> different numbers (7400 for GRUB, 7500 for LILO), not sure whether we
> should have the same numbers for grub-installer and for
> systemd-boot-installer.

Yeah I just copied it without giving it much thought, if it needs to
be changed let me know what is the right number and I'll fix it.

> I'm also not sure whether we should offer a choice between those two
> different booting methods in the course of a normal (non-expert)
> install.
>
>
> Finally, I'm Cc-ing GRUB people to let them know.

Sure we can leave it as-is until there's at least some request to have
it, expert mode is fine for now.



Re: Bug#1072501: ITP: systemd-boot-installer -- Install systemd-boot on a hard disk

2024-06-03 Thread Luca Boccassi
On Mon, 3 Jun 2024 at 02:22, Cyril Brulebois  wrote:
>
> Hi,
>
> Luca Boccassi  (2024-06-03):
> > Package: wnpp
> > Severity: wishlist
> > Owner: Luca Boccassi 
> > X-Debbugs-Cc: debian-de...@lists.debian.org
> >
> > * Package name: systemd-boot-installer
> >   Version : 0.1
> >   Upstream Author : Luca Boccassi 
> > * URL : 
> > https://salsa.debian.org/installer-team/systemd-boot-installer
> > * License : GPL-2.0-or-later
> >   Programming Lang: shell
> >   Description : debian-installer component to install systemd-boot
> > as the bootloader
>
> Could we have some kind of heads-up via X-D-Cc to debian-boot@ for such
> things, please? Discovering we have a new package under our namespace
> via a “Processing” mail from ftpmaster is awkward.

Sorry, since it needs to go through NEW I uploaded at the same time as
I sent this:

https://lists.debian.org/debian-boot/2024/06/msg00013.html

so I thought it would be enough heads-up.



Processing of debian-installer-utils_1.149_source.changes

2024-06-03 Thread Debian FTP Masters
debian-installer-utils_1.149_source.changes uploaded successfully to localhost
along with the files:
  debian-installer-utils_1.149.dsc
  debian-installer-utils_1.149.tar.xz

Greetings,

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



debian-installer-utils_1.149_source.changes ACCEPTED into unstable

2024-06-03 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Jun 2024 09:26:41 +0100
Source: debian-installer-utils
Architecture: source
Version: 1.149
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Colin Watson 
Changes:
 debian-installer-utils (1.149) unstable; urgency=medium
 .
   [ Colin Watson ]
   * user-params: Exclude initrd, since it's sometimes hard to avoid syslinux
 appending it after "---".
 .
   [ Luca Boccassi ]
   * chroot_setup.sh: Mount efivarfs in /target if available.
Checksums-Sha1:
 af8d1d1e672c957235f5b09d7c0a1a3844f7ad9a 2285 debian-installer-utils_1.149.dsc
 ed4cb66247734feecc82693deea1c2113732d3fa 102916 
debian-installer-utils_1.149.tar.xz
Checksums-Sha256:
 ac1577c1f5188025e6afa31c7a32e6b1909f484695cc342b15367ad9cf01c159 2285 
debian-installer-utils_1.149.dsc
 400e37da530743340954f14b03bcb928ae44c4da19a4b34c8502ffd85a70e7ab 102916 
debian-installer-utils_1.149.tar.xz
Files:
 9c1c17af1072882ae50b6706aeaf61ee 2285 debian-installer standard 
debian-installer-utils_1.149.dsc
 5b8d9fcbff4c9819740cc3b52f78e3fd 102916 debian-installer standard 
debian-installer-utils_1.149.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmZdf7oACgkQOTWH2X2G
UAvi6hAAppE+D0OEb3AvO/i0qiPBGdo6uTw+7phw/yMnbGsexfRBN4/deGEkbVrX
6wYA6Bwp08p8/V6sSq+SiL8Nm+dUsj203TSMH1zxK6ZvtklgmyiMg0MUXf+24klE
clX58oILC1TtLzTfDWMD7TdZOeiYhp/bv4JuQT2N7ENc+fZFJRM/xNWvO6hf/1q8
CF+NkFy8LJljJLV6bGxlki+ASj0YQ8h3dWBOlLl5cfH2mS9bzROwgLD3gCXHVGEm
IZkSBfB/WFGEQasUuMUbaT63E/9G3eBMBP65NbjfIVOUkckDn+Tw3ZtHRBqJ8GTk
TcdekbmOD3Wq3oPibRnVSJ5blMvo/3Cpu6wNvo9IIxkpVH8IIqytbJj+zrN0ryg4
VXijxiQALGaWGdTP838N5nVSzuF4wKvN6SL1Eu0TmsbnIrXZY2+wnwjJxmDh2URV
ttaB0bUyd2cYHyyrFm/Hds+zr/pkXnsSymJ0597D8OVTLjH9VrKbtPN7/zv7t/Y7
AY+G/az28MsFgp7UeGXTM7R9DThUil7Ell1IFLFw/PE3mjKEXGGZL377kwhjKz6M
BuryfMYTAi6zGPU/ig53AklGuKGv+4F280RNdzphTFNbNiesfzlysGFy8KteOuXv
OeFTjVqoW71mo5itNegHGGp6kqbwwc6uNt3ukk80fc+V+CZiKLo=
=/CGG
-END PGP SIGNATURE-



pgpIGFhYdyj3A.pgp
Description: PGP signature


Re: Adding systemd-boot support in debian-installer

2024-06-02 Thread Cyril Brulebois
Hi,

Luca Boccassi  (2024-06-03):
> I've created a udeb that adds an expert menu item to allow choosing
> systemd-boot (in the NEW queue):
> 
> https://salsa.debian.org/installer-team/systemd-boot-installer

The `Architecture: all` in control vs the 64-bit EFI logic in the script
seems odd at first glance. Looking at other *-installer, they tend to
have a restricted arch list in most cases.

I have no strong feelings either way, just something that caught my eye
when I first looked into the repository.

> A couple of PRs for minimal support:
> 
> https://salsa.debian.org/installer-team/debian-installer-utils/-/merge_requests/12

OK, spotted the todo in the script when I spotted the upload; a
versioned dependency will do the trick once the d-i-utils part is
reviewed/merged/uploaded.

> https://salsa.debian.org/installer-team/d-i/-/merge_requests/17

TIL: builscript.

ACK on the .mrconfig part, but I think this misses an addition to
packages/po/packages_list (to be confirmed with Holger Wansing). Might
be best to get rid of the fuzzy parts still mentioning nobootloader
beforehand though. Just something that needs taken care of at some
point.

> https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/46
> 
> It does not show up in non-expert mode, which is fine for now,
> especially as secure boot signing is not yet available.
> 
> After it's been in the testing image like this for a while, and after
> we have secure boot integration finished up, would it be ok to show a
> question in the non-expert install too? GRUB would still be the
> default of course, the question would select it by default, and allow
> to switch to sd-boot if chosen. Where would be the best place to add
> this?

I have close to no knowledge about the details around menu items at the
moment. Looking at the good old GRUB vs. LILO duo, I see they had
different numbers (7400 for GRUB, 7500 for LILO), not sure whether we
should have the same numbers for grub-installer and for
systemd-boot-installer.

I'm also not sure whether we should offer a choice between those two
different booting methods in the course of a normal (non-expert)
install.


Finally, I'm Cc-ing GRUB people to let them know.


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


signature.asc
Description: PGP signature


Re: Bug#1072501: ITP: systemd-boot-installer -- Install systemd-boot on a hard disk

2024-06-02 Thread Cyril Brulebois
Hi,

Luca Boccassi  (2024-06-03):
> Package: wnpp
> Severity: wishlist
> Owner: Luca Boccassi 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name: systemd-boot-installer 
>   Version : 0.1
>   Upstream Author : Luca Boccassi 
> * URL : 
> https://salsa.debian.org/installer-team/systemd-boot-installer
> * License : GPL-2.0-or-later
>   Programming Lang: shell
>   Description : debian-installer component to install systemd-boot
> as the bootloader

Could we have some kind of heads-up via X-D-Cc to debian-boot@ for such
things, please? Discovering we have a new package under our namespace
via a “Processing” mail from ftpmaster is awkward.


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


signature.asc
Description: PGP signature


Adding systemd-boot support in debian-installer

2024-06-02 Thread Luca Boccassi
Hi,

I've created a udeb that adds an expert menu item to allow choosing
systemd-boot (in the NEW queue):

https://salsa.debian.org/installer-team/systemd-boot-installer

A couple of PRs for minimal support:

https://salsa.debian.org/installer-team/debian-installer-utils/-/merge_requests/12
https://salsa.debian.org/installer-team/d-i/-/merge_requests/17
https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/46

It does not show up in non-expert mode, which is fine for now,
especially as secure boot signing is not yet available.

After it's been in the testing image like this for a while, and after
we have secure boot integration finished up, would it be ok to show a
question in the non-expert install too? GRUB would still be the default
of course, the question would select it by default, and allow to switch
to sd-boot if chosen. Where would be the best place to add this?

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part


systemd-boot-installer_0.1_amd64.changes is NEW

2024-06-02 Thread Debian FTP Masters
binary:systemd-boot-installer is NEW.
binary:systemd-boot-installer is NEW.
source:systemd-boot-installer is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports


pgpkiuZBshWAS.pgp
Description: PGP signature


Processing of systemd-boot-installer_0.1_amd64.changes

2024-06-02 Thread Debian FTP Masters
systemd-boot-installer_0.1_amd64.changes uploaded successfully to localhost
along with the files:
  systemd-boot-installer_0.1.dsc
  systemd-boot-installer_0.1.tar.xz
  systemd-boot-installer_0.1_all.udeb
  systemd-boot-installer_0.1_amd64.buildinfo

Greetings,

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



Bug#1072204: setupcon: race condition with systemd-tmpfiles

2024-06-02 Thread Samuel Thibault
Control: Tags -1 + pending

Marc Leeman, le mer. 29 mai 2024 11:46:46 +0200, a ecrit:
> On occasion I have a situation where console-setup.service fails to
> start up due to a race condition. After investigating this, it was
> already reported in Ubuntu back in 2019 and I have verified that the
> patch they have implemented resolves the issue for me:

Ok, applied, thanks!

Samuel



Processed: Re: Bug#1072204: setupcon: race condition with systemd-tmpfiles

2024-06-02 Thread Debian Bug Tracking System
Processing control commands:

> Tags -1 + pending
Bug #1072204 [console-setup] setupcon: race condition with systemd-tmpfiles
Added tag(s) pending.

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



Bug#1017542: systemd-cryptsetup@vda5_crypt.service: Control process exited, code=exited, status=1/FAILURE

2024-06-02 Thread Luca Boccassi
On Sun, 2 Jun 2024 at 20:04, Cyril Brulebois  wrote:
>
> Luca Boccassi  (2024-05-27):
> > I'll upload a D-I fix that adds x-initrd.attach to crypttab by default
> > shortly. Yes you can ignore the "unknown option" message, as the
> > Debian-specific initramfs-tools scripts do not know about it, but
> > that's fine, it's for the shutdown path anyway. And the finalize
> > messages can also be ignored.
>
> Having a cryptsetup warning about an unknown option on the very first
> line seen by users after the bootloader step doesn't feel appropriate
> at all to me. Telling users to just ignore it neither.
>
> For the record, on a fresh install, that means:
>
> cryptsetup: WARNING: sda5_crypt: ignoring unknown option 'x-initrd.attach'
> Please unlock disk sda5_crypt: _
>
> Looping in the cryptsetup team.

See #1072058



Processed: Bug#1072204 marked as pending in console-setup

2024-06-02 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1072204 [console-setup] setupcon: race condition with systemd-tmpfiles
Ignoring request to alter tags of bug #1072204 to the same tags previously set

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



Bug#1017542: systemd-cryptsetup@vda5_crypt.service: Control process exited, code=exited, status=1/FAILURE

2024-06-02 Thread Cyril Brulebois
Luca Boccassi  (2024-05-27):
> I'll upload a D-I fix that adds x-initrd.attach to crypttab by default
> shortly. Yes you can ignore the "unknown option" message, as the
> Debian-specific initramfs-tools scripts do not know about it, but
> that's fine, it's for the shutdown path anyway. And the finalize
> messages can also be ignored.

Having a cryptsetup warning about an unknown option on the very first
line seen by users after the bootloader step doesn't feel appropriate
at all to me. Telling users to just ignore it neither.

For the record, on a fresh install, that means:

cryptsetup: WARNING: sda5_crypt: ignoring unknown option 'x-initrd.attach'
Please unlock disk sda5_crypt: _

Looping in the cryptsetup team.


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


signature.asc
Description: PGP signature


Processing of partman-auto_166_source.changes

2024-06-02 Thread Debian FTP Masters
partman-auto_166_source.changes uploaded successfully to localhost
along with the files:
  partman-auto_166.dsc
  partman-auto_166.tar.xz
  partman-auto_166_source.buildinfo

Greetings,

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



partman-auto_166_source.changes ACCEPTED into unstable

2024-06-02 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 02 Jun 2024 13:53:57 +0200
Source: partman-auto
Architecture: source
Version: 166
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Aurelien Jarno 
Changes:
 partman-auto (166) unstable; urgency=medium
 .
   * Team upload
 .
   [ Aurelien Jarno ]
   * Drop kfreebsd support
Checksums-Sha1:
 a579fff3f6e807d36f49a7eda800eebff61cdb93 1684 partman-auto_166.dsc
 b0e45ad545c96cc5a7a7052ad5a201ee32e97d5f 112236 partman-auto_166.tar.xz
 b305ebcef60d87b2a71f6438d9dd214d31ca2821 5600 partman-auto_166_source.buildinfo
Checksums-Sha256:
 18b3b12ad2fe8ef405c48590ab4b28ad25bd9b53a25ff4c51305ac74610afe8a 1684 
partman-auto_166.dsc
 c71d76ab4b11d965fa78db36942e9212afab2e4c2aa5e3abda5dfe6fa2d2 112236 
partman-auto_166.tar.xz
 40819fdec03cfbbcd29b963dad4455d91ccc17ac8bfd6a787c70f864cf77979f 5600 
partman-auto_166_source.buildinfo
Files:
 ea6c16ba0c8ba1f306e05bc6bc5ec0ba 1684 debian-installer standard 
partman-auto_166.dsc
 79c7352e700b03a5e36cf098bd11917d 112236 debian-installer standard 
partman-auto_166.tar.xz
 6d59fc38e5d3ef6d02c322782a84920d 5600 debian-installer standard 
partman-auto_166_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmZcXjIACgkQE4jA+Jno
M2u4mA/8CKQH8pHodRaM3EwFQUA68c6kHLgSkcC1lQ3L7FpBxzau9cXASfBpMTr8
ezObwNYRqsaDeOPqqSPKl4RZ1LN5re2to7mSnKNKFoU6sS3K9oDGCW8rtDwpDf2m
bzzR0y+cKNUV6qszlAFRHakDQVC8VNofwDVPZdgmjGN/wOpjXJZnGgltoGOvIMQP
vTaD0ZT357htVNLdM3UQ77K2oQBL+9mHkqePQrO9dFpiZNDqBUkHxaM/ThlxXeyl
Ir/ogET9CRdQQEJll9lR9iOzjh/m4qGwi5BN47sMW08WTfuz8F74B2ILLiBXjGSj
QzfRZyLD5IovI1tqz2O/WoyfVgKwDmSI8xo0pCFepUulqDUET7DfTC0bx+IvpfXX
FkZn2QngtoA+HqpTIqlGvvBWxKPy8dMo2p6bM3GMv/y/7+JAo7SmEWBf0kXnVQeR
DCGiDCasuHrpDWmTmhwWMPoG48ou8d2ncd3ZQh+qkqquJh7a+brGcHpF4hTJHkVX
T4NaufMWKWllIlHUfOgyRjMiAIqczzqiTy112rShXasMt4L/M//iT2+MkUnw8YTL
uOf0JdKhaWtrab3WfXLnpuwoncLaRej+O0QQ3uCdF5SDYejwo4MRxxQsE1DLk3TW
vGZO317+0sBELDhYtWSnw0cryerM9jFFg9cV9TMAzGmaGeQn2/0=
=PHnc
-END PGP SIGNATURE-



pgpMqId9EIhhq.pgp
Description: PGP signature


Bug#1072215: USB wireless Netgear WNA1100 fails to load

2024-06-01 Thread Pascal Hambourg

On 01/06/2024 at 10:08, Tom Overlund wrote:


Running the patched installer, the output was a bit different, and it
DID unload the module ("ath9k_htc: Driver unloaded"),


Thank you for testing. It is still not clear which method identified the 
actual module. I should make it more verbose. I suspect it is the search 
in loaded module "firmware" fields because IIRC (I wrote these patches 
quite some time ago) other methods require 
/sys/bus/usb/devices/3-3/3-3:1.0 to be present.



but it still output errors trying to unload the usb module


This is normal, the installer still tries to unload the primary module 
in case it guessed the module wrong.



and it did NOT try to configure the wireless network:


I also expected this because /sys/bus/usb/devices/3-3/3-3:1.0 is missing 
so the driver is unable to bind with the device.


Now we must find why /sys/bus/usb/devices/3-3/3-3:1.0 is missing and how 
to make it reappear. "udevadm monitor" may help.


PS: I am following a somehow similar issue in another bug report 
. But I still 
lack knowledge in the USB field.




Bug#1072215: USB wireless Netgear WNA1100 fails to load

2024-06-01 Thread Tom Overlund
On Sat, Jun 01, 2024 at 09:13:01AM +0200, Pascal Hambourg wrote:
> 
> I don't know much about packaging, but comparing with other packages you may
> need to add the patch names to a file debian/patches/series. Or I guess you
> could just apply the patches manually with patch -p1 < patch" before
> building the package.

Just running patch did the trick, even without the -p1 flag.

Running the patched installer, the output was a bit different, and it
DID unload the module ("ath9k_htc: Driver unloaded"), but it still
output errors trying to unload the usb module, and it did NOT try to
configure the wireless network:

Jun  1 07:21:49 check-missing-firmware: looking at dmesg for the first time
Jun  1 07:21:49 check-missing-firmware: saving timestamp for a later use: [   
10.585522]
Jun  1 07:21:49 check-missing-firmware: failed to perform usb 3-3 lookup (got: 
0 entries, expected: 1)
Jun  1 07:21:49 check-missing-firmware: => sticking with the usb module
Jun  1 07:21:49 check-missing-firmware: using module usb instead of usb 3-3
Jun  1 07:21:49 check-missing-firmware: looking for firmware file 
ath9k_htc/htc_9271-1.4.0.fw requested by ath9k_htc
Jun  1 07:21:49 check-missing-firmware: failed to perform usb 3-3 lookup (got: 
0 entries, expected: 1)
Jun  1 07:21:49 check-missing-firmware: => sticking with the usb module
Jun  1 07:21:49 check-missing-firmware: using module usb instead of usb 3-3
Jun  1 07:21:49 check-missing-firmware: looking for firmware file 
ath9k_htc/htc_9271-1.4.0.fw requested by ath9k_htc
Jun  1 07:21:49 check-missing-firmware: failed to perform usb 3-3 lookup (got: 
0 entries, expected: 1)
Jun  1 07:21:49 check-missing-firmware: => sticking with the usb module
Jun  1 07:21:49 check-missing-firmware: using module usb instead of usb 3-3
Jun  1 07:21:50 check-missing-firmware: no module matching firmware htc_9271.fw 
found
Jun  1 07:21:50 check-missing-firmware: looking for firmware file htc_9271.fw 
requested by usb
Jun  1 07:21:50 check-missing-firmware: failed to perform usb 3-3 lookup (got: 
0 entries, expected: 1)
Jun  1 07:21:50 check-missing-firmware: => sticking with the usb module
Jun  1 07:21:50 check-missing-firmware: using module usb instead of usb 3-3
Jun  1 07:21:50 check-missing-firmware: no module matching firmware htc_9271.fw 
found
Jun  1 07:21:50 check-missing-firmware: looking for firmware file htc_9271.fw 
requested by usb
Jun  1 07:21:50 check-missing-firmware: missing firmware files 
(ath9k_htc/htc_9271-1.4.0.fw htc_9271.fw) for ath9k_htc usb
Jun  1 07:21:50 check-missing-firmware: mainloop iteration #1
Jun  1 07:21:50 check-missing-firmware: lookup with /firmware/Contents-firmware
Jun  1 07:21:50 check-missing-firmware: installing firmware package 
/firmware/firmware-ath9k-htc_1.4.0-108-gd856466+dfsg1-1.3+deb12u1_all.deb (main)
Jun  1 07:21:50 check-missing-firmware: installing firmware package 
/firmware/firmware-atheros_20230210-5_all.deb (non-free-firmware)
Jun  1 07:21:51 check-missing-firmware: removing and loading kernel module 
ath9k_htc
Jun  1 07:21:51 kernel: [   13.528483] usbcore: deregistering interface driver 
ath9k_htc
Jun  1 07:21:51 kernel: [   13.528507] ath9k_htc: Driver unloaded
Jun  1 07:21:52 kernel: [   13.745690] usbcore: registered new interface driver 
ath9k_htc
Jun  1 07:21:52 check-missing-firmware: removing and loading kernel module usb
Jun  1 07:21:52 check-missing-firmware: modprobe: FATAL: Module usb not found.
Jun  1 07:21:52 check-missing-firmware: modprobe: FATAL: Module usb not found 
in directory /lib/modules/6.1.0-18-amd64
Jun  1 07:21:52 check-missing-firmware: removing and loading kernel module 
usbcore as well (actual module for usb)
Jun  1 07:21:52 check-missing-firmware: modprobe: FATAL: Module usbcore is in 
use.
Jun  1 07:21:53 check-missing-firmware: looking at dmesg again, restarting from 
timestamp: [   10.585522]
Jun  1 07:21:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
Jun  1 07:21:53 check-missing-firmware: saving timestamp for a later use: [   
13.745690]
Jun  1 07:21:53 check-missing-firmware: no missing firmware in loaded kernel 
modules



Bug#1072215: USB wireless Netgear WNA1100 fails to load

2024-06-01 Thread Pascal Hambourg

On 31/05/2024 at 14:59, Tom Overlund wrote:


Can you tell me the best way to apply these patches? I tried:

$ apt-get source hw-detect
# apt-get build-dep hw-detect
$ cd hw-detect-1.159/
$ mkdir debian/patches

and copying the three .patch files there, followed by:

$ debuild -b -uc -us

I was hoping that would patch it automatically, but no such luck.


I don't know much about packaging, but comparing with other packages you 
may need to add the patch names to a file debian/patches/series. Or I 
guess you could just apply the patches manually with patch -p1 < patch" 
before building the package.




Bug#1071903: hw-detect: USB wireless adapter r8712u needs physical disconnect and reconnect for firmware to work

2024-06-01 Thread Pascal Hambourg

On 31/05/2024 at 13:51, Pascal Hambourg wrote:


Maybe running "udevadm trigger" during specific 
moments and recording its output may provide useful information:


Sorry, I meant "udevadm monitor".



Re: Contacting Debian Boot team

2024-05-31 Thread Cyril Brulebois
Hi,

No problems regarding the extensive reply, glad you liked it. I'm
trimming all parts that didn't look like they needed a follow-up to
keep this brief…

Andreas Tille  (2024-05-31):
> sorry for my late reply - I was basically offline the last couple
> of days.

No need to be sorry.

> However, my question was rather whether you know some valid reasons
> why derivatives are exchanging the install method - maybe that
> question should be better asked on Debian-Boot (if so feel free to
> ignore this question).  I was rather wondering about the motivation
> for the usage of Ubiquity or Calamares (or others?).  I might be naive
> but from my perspective installing is something that just needs to
> work and having a lot of ways to make this working is somehow burning
> developer time.  So what according to your insight is motivating
> derivatives to solve a problem in a different way that is IMHO solved
> by Debian.

You seem to be asking the wrong person. I don't know about downstream's
motivation, the various alternatives/competitors, etc., and I wouldn't
have time to investigate if I wanted to (and I'm not saying that's the
case).

> Sure there is an arm64 image and I started with copying this to some
> USB stick.  But that hardware did not booted from an USB device but
> only from eprom that had to be flashed via SD card.  Its not your
> fault definitely but was frustrating for me not beeing able to simply
> run the Debian installer.

I understand the frustration (“welcome to the ARM world…”) but (1) the
initial statements were a very wrong conclusion from your findings and
(2) even with hardware that's supposed to be supported by free software
we might need time to spot, fix, or workaround bugs (hardware, software,
firmware, doc, etc.) or integrate new features to support new boards.

That's not specific to d-i, that's just how IT works.

> It was not really a claim but a question based on my experience with a
> single piece of hardware.  I was hoping for some ideas how we could
> motivate hardware vendors to deliver hardware that can be easily
> booted by simply plugging in some USB device featuring the installer
> images we provide on our web page.

UEFI/arm64 is a thing. Whether HW vendors actually implement/enable UEFI
is another matter entirely (see early EEPROM versions on e.g. Pi 4).

> Just keep in mind my offer to contact me in private if needed. 

That's appreciated, thanks.


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


signature.asc
Description: PGP signature


Bug#1072215: USB wireless Netgear WNA1100 fails to load

2024-05-31 Thread Tom Overlund
On Fri, May 31, 2024 at 12:04:23AM +0200, Pascal Hambourg wrote:
>
> It seems that check-missing-firmware failed to identify the correct kernel
> module. At this point, can you post the output of
> 
> ls -d /sys/bus/usb/drivers/ath9k_htc/3-3*
> ls -d /sys/bus/usb/devices/3-3/3-3*

During the installer: No such file or directory. Note end of mail for
listing of these two directories.

On the installed system with the preloaded /lib/firmware/ath9k_htc/, it is:
/sys/bus/usb/drivers/ath9k_htc/3-3:1.0 and
/sys/bus/usb/devices/3-3/3-3:1.0

> assuming the wireless adapter is identified as 3-3 ?

Yes, I checked the syslog, it is always showing up as 3-3 in the installer.

> Then can you try the patches for hw-detect attached to
>  ?

Can you tell me the best way to apply these patches? I tried:

$ apt-get source hw-detect
# apt-get build-dep hw-detect
$ cd hw-detect-1.159/
$ mkdir debian/patches

and copying the three .patch files there, followed by:

$ debuild -b -uc -us

I was hoping that would patch it automatically, but no such luck.

Finally, per above, ls listings:

$ ls -l /sys/bus/usb/drivers/ath9k_htc/
--w---1 root root  4096 May 31 12:25 bind
lrwxrwxrwx1 root root 0 May 31 12:25 module -> 
../../../../module/ath9k_htc
-rw-r--r--1 root root  4096 May 31 12:25 new_id
-rw-r--r--1 root root  4096 May 31 12:25 remove_id
--w---1 root root  4096 May 31 12:25 uevent
--w---1 root root  4096 May 31 12:25 unbind

$ ls -l /sys/bus/usb/devices/3-3/
-rw-r--r--1 root root  4096 May 31 12:25 authorized
-rw-r--r--1 root root  4096 May 31 12:25 avoid_reset_quirk
-rw-r--r--1 root root  4096 May 31 12:25 bConfigurationValue
-r--r--r--1 root root  4096 May 31 12:25 bDeviceClass
-r--r--r--1 root root  4096 May 31 12:25 bDeviceProtocol
-r--r--r--1 root root  4096 May 31 12:25 bDeviceSubClass
-r--r--r--1 root root  4096 May 31 12:25 bMaxPacketSize0
-r--r--r--1 root root  4096 May 31 12:25 bMaxPower
-r--r--r--1 root root  4096 May 31 12:25 bNumConfigurations
-r--r--r--1 root root  4096 May 31 12:25 bNumInterfaces
-r--r--r--1 root root  4096 May 31 12:25 bcdDevice
-r--r--r--1 root root  4096 May 31 12:25 bmAttributes
-r--r--r--1 root root  4096 May 31 12:25 busnum
-r--r--r--1 root root  4096 May 31 12:25 configuration
-r--r--r--1 root root 65553 May 31 12:25 descriptors
-r--r--r--1 root root  4096 May 31 12:25 dev
-r--r--r--1 root root  4096 May 31 12:25 devnum
-r--r--r--1 root root  4096 May 31 12:25 devpath
drwxr-xr-x3 root root 0 May 31 12:25 ep_00
lrwxrwxrwx1 root root 0 May 31 12:25 firmware_node -> 
../../../../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:10/device:15/device:16/device:19
-r--r--r--1 root root  4096 May 31 12:25 idProduct
-r--r--r--1 root root  4096 May 31 12:25 idVendor
-r--r--r--1 root root  4096 May 31 12:25 ltm_capable
-r--r--r--1 root root  4096 May 31 12:25 manufacturer
-r--r--r--1 root root  4096 May 31 12:25 maxchild
drwxr-xr-x2 root root 0 May 31 12:25 physical_location
lrwxrwxrwx1 root root 0 May 31 12:25 port -> 
../3-0:1.0/usb3-port3
drwxr-xr-x2 root root 0 May 31 12:25 power
-r--r--r--1 root root  4096 May 31 12:25 product
-r--r--r--1 root root  4096 May 31 12:25 quirks
-r--r--r--1 root root  4096 May 31 12:25 removable
--w---1 root root  4096 May 31 12:25 remove
-r--r--r--1 root root  4096 May 31 12:25 rx_lanes
-r--r--r--1 root root  4096 May 31 12:25 serial
-r--r--r--1 root root  4096 May 31 12:25 speed
lrwxrwxrwx1 root root 0 May 31 12:25 subsystem -> 
../../../../../../bus/usb
-r--r--r--1 root root  4096 May 31 12:25 tx_lanes
-rw-r--r--1 root root  4096 May 31 12:25 uevent
-r--r--r--1 root root  4096 May 31 12:25 urbnum
-r--r--r--1 root root  4096 May 31 12:25 version



Bug#1071903: hw-detect: USB wireless adapter r8712u needs physical disconnect and reconnect for firmware to work

2024-05-31 Thread Pascal Hambourg

On 31/05/2024 at 10:26, Roland Clobus wrote:


* Moment 1: the first d-i screen is shown. The USB device is seen by the 
kernel, but the module is not yet loaded

ls -d /sys/bus/usb/drivers/r8712u/1-3*
No such file or directory


As expected, the module is not loaded so /sys/bus/usb/drivers/r8712u 
does not exist.



ls -d /sys/bus/usb/drivers/usb/1-3*
/sys/bus/usb/drivers/usb/1-3
ls -d /sys/bus/usb/devices/1-3/1-3*
/sys/bus/usb/devices/1-3/1-3:1:0


The device is present.


* Moment 2: the d-i screen 'No Ethernet card was detected' is shown
(The firmware has been placed where it can be found, module r8712u has 
been removed and added)

ls -d /sys/bus/usb/drivers/r8712u/1-3*
No such file or directory
The module is loaded so /sys/bus/usb/drivers/r8712u should exist but is 
not associated with the device.



ls -d /sys/bus/usb/drivers/usb/1-3*
No such file or directory
ls -d /sys/bus/usb/devices/1-3/1-3*
No such file or directory


It looks like the device is not present any more. But there was no 
disconnect message in the kernel log. All I can see it the reset 
message, but AFAICS a reset should not remove the device. Maybe it was 
disabled or powered down.


I do not know enough about the kernel and USB subsystem to have any clue 
about what is wrong. Maybe running "udevadm trigger" during specific 
moments and recording its output may provide useful information:

- when the adapter is connected
- when the module is loaded without the firmware
- when the adapter is disconnected
- when the module is reloaded with the firmware

You do not have to run check-missing-firmware for this, you can run 
modprobe commands in a shell.


* Moment 3: I disconnect and reconnect the USB device in virt-manager 
and select 'Detect network hardware' from the d-i menu. d-i shows a list 
of SSIDs

ls -d /sys/bus/usb/drivers/r8712u/1-3*
/sys/bus/usb/drivers/r8712u/1-3:1.0


As expected, the device is associated with the driver.



Bug#1071903: hw-detect: USB wireless adapter r8712u needs physical disconnect and reconnect for firmware to work

2024-05-31 Thread Roland Clobus

On 30/05/2024 00:55, Pascal Hambourg wrote:

On 26/05/2024 at 22:29, Roland Clobus wrote:


Your patch series works fine, the firmware is correctly identified and 
loaded. Unfortunately for me, it still needs a reconnect cycle.

See the attached syslog for their effect. (I've used sid)


Thank you for testing my patches but I did not expect them to solve the 
reattachment issue, only to identify the right module.


After the r8712u module is first loaded without the firmware then 
unloaded and reloaded, what is the output of


ls -d /sys/bus/usb/drivers/r8712u/1-3*
ls -d /sys/bus/usb/devices/1-3/1-3*

assuming the wireless adapter is identified as 1-3 ?


I've used the following to reproduce:
* A live-build-based image with the Debian installer, generated for sid
  with in config/packages the hw-detect.udeb with the patches from #1033679
* Virtual-Manager boots the ISO image (UEFI secure boot)
* When the GRUB menu is shown, I attach the USB network adapter from the 
host

* I select the Debian installer

* Moment 1: the first d-i screen is shown. The USB device is seen by the 
kernel, but the module is not yet loaded

ls -d /sys/bus/usb/drivers/r8712u/1-3*
No such file or directory
ls -d /sys/bus/usb/drivers/usb/1-3*
/sys/bus/usb/drivers/usb/1-3
ls -d /sys/bus/usb/devices/1-3/1-3*
/sys/bus/usb/devices/1-3/1-3:1:0
lsmod | grep r8712u


* Moment 2: the d-i screen 'No Ethernet card was detected' is shown
(The firmware has been placed where it can be found, module r8712u has 
been removed and added)

ls -d /sys/bus/usb/drivers/r8712u/1-3*
No such file or directory
ls -d /sys/bus/usb/drivers/usb/1-3*
No such file or directory
ls -d /sys/bus/usb/devices/1-3/1-3*
No such file or directory
lsmod | grep r8712u
r8712u 262144   0
cfg80211  1355776  1 r8712u
usbcore409600  5 xhci_hcd,usbhib,r8712u,usb_storage,xhci_pci

* Moment 3: I disconnect and reconnect the USB device in virt-manager 
and select 'Detect network hardware' from the d-i menu. d-i shows a list 
of SSIDs

ls -d /sys/bus/usb/drivers/r8712u/1-3*
/sys/bus/usb/drivers/r8712u/1-3:1.0
ls -d /sys/bus/usb/drivers/usb/1-3*
/sys/bus/usb/drivers/usb/1-3
ls -d /sys/bus/usb/devices/1-3/1-3*
/sys/bus/usb/devices/1-3/1-3:1:0
lsmod | grep r8712u
r8712u 262144   0
cfg80211  1355776  1 r8712u
usbcore409600  5 xhci_hcd,usbhib,r8712u,usb_storage,xhci_pci

With kind regards,
Roland Clobus


OpenPGP_signature.asc
Description: OpenPGP digital signature


Re: Contacting Debian Boot team

2024-05-31 Thread Andreas Tille
Hi Cyril,

sorry for my late reply - I was basically offline the last couple
of days.

Am Sun, May 26, 2024 at 08:55:37PM +0200 schrieb Cyril Brulebois:
> What follows is only my point of view, and anyone active within the
> installer team is welcome to share their own.

Thanks a lot for your extensive answer.  Your personal view is really
important to me.  I did not (yet) received so many extensive responses
to my contact mails.
 
> ACK. TL;DR: no strong organization, mainly some coordination around
> releases, but otherwise debian-boot gets to consume whatever ends up in
> testing/unstable, and has to adapt accordingly. Of course we have some
> packages on our own in addition to all the dependencies that we don't
> maintain.
> 
> You might have notice some heavy pushes in the past to get firmware
> support improved (enough to avoid black or unreadable screens post
> installation, in earlier releases), or to get non-free-firmware included
> (in Debian 12).

I need to admit I rarely use your great work - just when buying a new
machine or setting up some machine of a friend which finally boils down
to once a year in average.  But I confirm things became better each
time.  So thanks for all your work.
 
> I don't have any important or urgent needs at the moment, but I won't
> hesitate if I spot something that could benefit from your input.

Fine.
 
> > I'm sure not everybody will be able to travel this distance but it
> > would be great if you would at least consider joining that BoF
> > remotely.  I'll care for a somehow TimeZone aware scheduling - if
> > needed we'll organise two BoFs to match all time zones.  I'm also
> > aware that we have pretty different teams and it might make sense to
> > do some infrastructure related BoF with your team and other teams that
> > are caring for Debian infrastructure.
> 
> Anticipating and planning a full week (or more) off that much in the
> future is something I can't do at this point, but I'm usually fairly
> flexible when it comes to timezones, so joining remotely should work, at
> least in principle.

Thanks for confirming.  The BoF will definitely happen in the first half
of DebConf since I need to leave before DebConf ends.
 
> > I have some specific questions to the Debian Boot team.
> > 
> >   - Do you feel good when doing your work in Debian Boot team?
> 
> That's been the case from the moment I joined (around 2012, even if
> first contact happened in 2010-2011 with the DirectFB → X.Org
> transition, see https://mraw.org/blog/2010/01/31/Saving_private_GI/).

Good so far.
 
> And until last year, right after the Bookworm release, for reasons I
> cannot and wouldn't want to express publicly at this time (relevant team
> Bcc'd). What should have been a thumbs-up-all-around celebration turned
> into the most severe burnout I've ever felt, personally, professionally,
> and “debian-ly”, right after having sacrificed a lot (on all 3
> accounts).
> 
> I can endure hard work. Feelings like betrayal or distrust is something
> else entirely.

This sounds like the things I wanted to learn.  Feel free to contact
me in private if you think I can be of any help.

> I've come back to doing a few things here and there (including dealing
> with 64-bit time_t fallouts on the d-i side, reviewing Netplan's initial
> integration, or blends stuff as you know), but I'm nowhere near to
> feeling good again about doing d-i things.

Thanks a lot for expressing this.
 
> Which is absolutely heartbreaking because I've been doing that for a
> while, still enjoy doing it, and really don't want to leave it. And even
> if I'm not one to boast, I thought I had been doing a pretty fucking
> good job. Until last year that is.

My personal perception was always that you are actually debian-boot team
in person since >10 years (which might be unfair for other team members)
and my personal thanks (independently from my DPL position) goes to you.

> We have a very diverse team with people dealing mostly (but not only!)
> with i18n/l10n coordination (Holger), with QA (Phil), with some specific
> components (flash-kernel), with specific set(s) of images, etc. It's
> more a bits & pieces depending on one's area(s) of interest.

Thank you for the explanation fixing my perception I mentioned above.
 
> In the end, I'm the one making sure things look “good enough” when
> preparing a release makes sense, usually in coordination with various
> teams (see frequent mails to -boot, -release, -kernel, -cd, and -live
> during the bookworm release cycle, and also in previous ones). I don't
> think I need to prepare any statistical analysis, but if memory serves,
> those mails have usually been met with silence, tacit or explicit
> approval, and I don't remember any crazy ideas from mine needing to be
> shot down or rehashed differently -- even I wouldn't mind if it
> happened: I know freezing testing can impact any maintainer, but the
> -boot/-cd release process has been quite improved over the years (also
> 

Bug#1072215: USB wireless Netgear WNA1100 fails to load

2024-05-30 Thread Pascal Hambourg

Hello Tom,

On 30/05/2024 at 13:33, Tom Overlund wrote:


/var/log/syslog indicates it tried to load firmware for the USB WiFi
device, failed, but loaded the kernel module anyways. Then the
installer detected this, installed the package with the firmware, and
then got some errors about realoding USB modules.
It seems that check-missing-firmware failed to identify the correct 
kernel module. At this point, can you post the output of


ls -d /sys/bus/usb/drivers/ath9k_htc/3-3*
ls -d /sys/bus/usb/devices/3-3/3-3*

assuming the wireless adapter is identified as 3-3 ?

Then can you try the patches for hw-detect attached to 
 ?




Re: Contacting Debian Boot team

2024-05-30 Thread Holger Wansing
Hi all,

Andreas Tille  wrote (Sun, 26 May 2024 11:31:24 +0200):
>   - Do you feel good when doing your work in Debian Boot team?

Yes!
While I have to admit that I'm mostly doing just the simple things :-)
I consider myself being only a small candle on the cake.
Being not a programmer, I don't do difficult or critical changings most of
the time, so relaxed gaming here ;-)

>   - Do you consider the workload of your team equally shared amongst its
> members and who actually is considered a team member?  (I added some
> persons in CC who have recently answered to questions on the mailing
> list.)

My impression is, that kibi might be kind of overloaded (at least some time),
since he's the mainly active part, when it comes to the "difficult or
critical things", which I leave around ...
(and his answer to this survey confirms this)
But I cannot see what I can do against this :-( (see below)

(ok, that's not strictly correct generally, there are some people taking care
of specific packages, taking workload from kibi's shoulders, but that's not
for the majority of packages)

>   - Do you have some strategy to gather new contributors for your team?

Since I lack the skills to lead new contributors into doing the difficult
or critical things from above (where we would mostly need more manpower,
if at all), I'm a bit lost here ...

>   - Can you give some individual estimation how many hours per week you
> are working on your tasks in youre team?  Does this fit the amount of
> time you can really afford for this task?

This ranges from zero to 5-10 hours per week, depending on variables like
the state of development cycle of release (when the next release comes
nearer, I try to get missing translation updates, which leads to more
commits and uploads, as an example).
And: I'm fine with this time effort.

>   - I recently had some discussion on Chemnitzer Linuxtage what might
> be the reason for derivatives to write their own installers.  While
> I'm personally perfectly happy with the way I can install Debian I'm
> somehow wondering why others are spending time into a problem we
> are considering "solved" and whether we can learn something from this,

That was often mentioned, and the arguments for the Debian Installer was the 
broader range of architectures, and as well as the support for older hardware.
You can easily create a nicer installer, if you develop from scratch for only
a small variety of up-to-date devices.

OTOH since Buster we have the Calamares installer on the live images as well,
to serve such approaches.
The idea behind the Calamares installer is exactly that: develop a framework,
which can be used to install a variety of distributions, to solve those
distributions from developing their own installer.
So I think we are on a not that bad position here ... (?)

>   - I once had a amr64 based laptop (Pinebook) and had to learn that I
> can't use the Debian installer which was frustrating.  I was told
> that this is the case for hardware that is not featuring some BIOS-like
> boot system.  Do you see any chance to let the installer work for
> non-Intel architectures (or should I rather ask this question on
> Debian CD (sorry for my ignorance if I miss responsibility here.)
>   - Can I do anything for you?

I guess most teams are undermanned in the free software world, and there's 
nothing one can do against easily, but I consider this being the main "issue", 
if any...


So long
Holger

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



Re: migrating grub from BIOS to UEFI loses /etc/default/grub

2024-05-30 Thread Pascal Hambourg

On 30/05/2024 at 12:07, Felix Zielcke wrote:


d-boot is actually the wrong mailing list to discuss grub.


Right, so I posted a digest of this thread to the GRUB maintainer list 
for further discussion.





Bug#1072215: USB wireless Netgear WNA1100 fails to load

2024-05-30 Thread Tom Overlund
Package: installation-reports

Boot method: Netboot over TFTP
Image version: Debian version: 12 (bookworm); Installer build: 
20230607+deb12u5; URLs: 
https://deb.debian.org/debian/dists/bookworm/main/installer-amd64/current/images/netboot/netboot.tar.gz
 + https://cdimage.debian.org/cdimage/firmware/bookworm/current/firmware.cpio.gz
Date: May 29 ~9:30am

Machine: Generic desktop PC
Processor: AMD Athlon 200GE
Memory: 16GB
Partitions: Not applicable

Output of lspci -knn (or lspci -nn):

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Root Complex [1022:15d0]
Subsystem: ASRock Incorporation Raven/Raven2 Root Complex [1849:15d0]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 
[1022:15d1]
Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 
[1022:15d1]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe 
GPP Bridge [6:0] [1022:15d3]
Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP 
Bridge [6:0] [1022:1453]
Kernel driver in use: pcieport
00:01.6 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe 
GPP Bridge [6:0] [1022:15d3]
Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP 
Bridge [6:0] [1022:1453]
Kernel driver in use: pcieport
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Internal PCIe GPP Bridge 0 to Bus A [1022:15db]
Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal 
PCIe GPP Bridge 0 to Bus A [1022:]
Kernel driver in use: pcieport
00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Internal PCIe GPP Bridge 0 to Bus B [1022:15dc]
Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal 
PCIe GPP Bridge 0 to Bus B [1022:]
Kernel driver in use: pcieport
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 61)
Subsystem: ASRock Incorporation FCH SMBus Controller [1849:790b]
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge 
[1022:790e] (rev 51)
Subsystem: ASRock Incorporation FCH LPC Bridge [1849:790e]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 0 [1022:15e8]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 1 [1022:15e9]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 2 [1022:15ea]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 3 [1022:15eb]
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 4 [1022:15ec]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 5 [1022:15ed]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 6 [1022:15ee]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 7 [1022:15ef]
15:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset USB 3.1 xHCI Compliant Host Controller [1022:43d5] (rev 01)
Subsystem: ASRock Incorporation 400 Series Chipset USB 3.1 xHCI 
Compliant Host Controller [1849:43d0]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
15:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset SATA Controller [1022:43c8] (rev 01)
Subsystem: ASRock Incorporation 400 Series Chipset SATA Controller 
[1849:43c8]
Kernel driver in use: ahci
Kernel modules: ahci
15:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset PCIe Bridge [1022:43c6] (rev 01)
Subsystem: ASRock Incorporation 400 Series Chipset PCIe Bridge 
[1849:43c6]
Kernel driver in use: pcieport
1d:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset PCIe Port [1022:43c7] (rev 01)
Subsystem: ASRock Incorporation 400 Series Chipset PCIe Port [1849:43c7]
Kernel driver in use: pcieport
1d:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset PCIe Port [1022:43c7] (rev 01)
Subsystem: ASRock Incorporation 400 Series Chipset PCIe Port [1849:43c7]
Kernel driver in use: pcieport
1d:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset PCIe Port [1022:43c7] (rev 01)
Subsystem: ASRock 

Processing of apt-setup_0.186_source.changes

2024-05-30 Thread Debian FTP Masters
apt-setup_0.186_source.changes uploaded successfully to localhost
along with the files:
  apt-setup_0.186.dsc
  apt-setup_0.186.tar.xz
  apt-setup_0.186_amd64.buildinfo

Greetings,

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



apt-setup_0.186_source.changes ACCEPTED into unstable

2024-05-30 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 30 May 2024 12:32:48 +0200
Source: apt-setup
Architecture: source
Version: 1:0.186
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 apt-setup (1:0.186) unstable; urgency=medium
 .
   * Team upload
 .
   [ Russell Hernandez Ruiz ]
   * Reword non-free-firmware description template, for better information
 to users.
 .
   [ Updated translations ]
   * Catalan (ca.po) by victor dargallo
   * German (de.po) by Holger Wansing
   * Spanish (es.po) by gallegonovato
   * Hindi (hi.po) by Scrambled777
   * Hungarian (hu.po) by SZERVÁC Attila
   * Georgian (ka.po) by Temuri Doghonadze
   * Malayalam (ml.po) by Manoj Karingamadathil
   * Marathi (mr.po) by omwani
   * Dutch (nl.po) by Frans Spiesschaert
   * Punjabi (Gurmukhi) (pa.po) by Aman Alam
   * Portuguese (pt.po) by Miguel Figueiredo
   * Ukrainian (uk.po) by Hotripak
   * Traditional Chinese (zh_TW.po) by reimu105
Checksums-Sha1:
 9feb06620a6d1a9d26fcc4c26506058b114de806 1798 apt-setup_0.186.dsc
 6d0393b8de60af035d431488f284ee1ce1c8fecc 268752 apt-setup_0.186.tar.xz
 16668319056bcba6467f2f1d87a9afb158af87d6 6526 apt-setup_0.186_amd64.buildinfo
Checksums-Sha256:
 b6ff8bf8856c5fd46160a4237b16346865c744b6ec0c1f1478067a6c40c4d38e 1798 
apt-setup_0.186.dsc
 7a7435ea199388a5182ca0c49f03bbffec82e1009fd52ba22a084e88d9586058 268752 
apt-setup_0.186.tar.xz
 553112836b03fe26148438cbc3a78cd2fd15eb5248d39f75dba416eafbfb917c 6526 
apt-setup_0.186_amd64.buildinfo
Files:
 54e5bc91c6d7cde947274ba71e752c3f 1798 debian-installer optional 
apt-setup_0.186.dsc
 e078de1f643be7cfd407807504be465a 268752 debian-installer optional 
apt-setup_0.186.tar.xz
 902c422a59cb2995c311bbed509c5186 6526 debian-installer optional 
apt-setup_0.186_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZYXVgVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB261EQALz1i3L3FZ5HY8pq0EoueP9K1pl5
pLpmGWm04AvpROjoCiq5CfLDeUh3+Sdfa0geHYmnJ3nKFjwX52j4G5aRh1pvpF8/
Ljc3XKfvZk0ux10F8jUcx3USKXtctPncOyt07hJ0bmK3h5gYp1pmixwjrG4LTNK1
J9WNM+lvolBVQZTD98BkNpEqgmfulysHWQXRHQhAkFw0wbPeyXihJuTUGUI07BxM
zORzpp+djXrq59GJ5YnMNXZa57KCryYG3DDZNbwg7lrVsGt2W6GtYyPRqPMoQkQ1
8dqY+2Mgm0hACVYHJBCbw5tgnHRwctUoIp1B0O8uWMn1r1n6mzQHC7I2ftmuEozs
ZxqABVl556hBVqcJHHhwUfK7znRY/2GGTXKnSp1L2MhsLtg2pS+cr0P+5eHhhmMB
nipeCJGk76sdNSI5EX8C4x+2j67niHdH/CFYkRRGdo9e3lUNfbBupti7nlZCv+Yh
RWOl3jKfOWmWsDc3Wx01ENDm701OZJRkTzPcac/yYSbEo5iXQbhnVqko+gx4FeKK
2I06BXB5qOd/YmiYmn8TiYTprTkr5KGRfPfS9qWFn139HpmUG0h4LDx21ddaKuku
tt7BTekzmgsaiG5LIR0b7/sMkRkA/+x9PpA2NOWqEkDm7GZfyC+lHyfaYGC93QPk
HDLUuRGj4OYw07kG
=QENs
-END PGP SIGNATURE-



pgpo94oU__SH7.pgp
Description: PGP signature


Processing of console-setup_1.227_source.changes

2024-05-30 Thread Debian FTP Masters
console-setup_1.227_source.changes uploaded successfully to localhost
along with the files:
  console-setup_1.227.dsc
  console-setup_1.227.tar.xz
  console-setup_1.227_amd64.buildinfo

Greetings,

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



Bug#1069791: marked as done (console-setup: Build larger console fonts for HiDPI/accessibility with future 6.9 kernels)

2024-05-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 May 2024 10:19:42 +
with message-id 
and subject line Bug#816111: fixed in console-setup 1.227
has caused the Debian Bug report #816111,
regarding console-setup: Build larger console fonts for HiDPI/accessibility 
with future 6.9 kernels
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 ow...@bugs.debian.org
immediately.)


-- 
816111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: console-setup
Version: 1.226
Severity: wishlist

Dear Maintainer,

Linux kernel 6.9+ will support larger font sizes for HiDPI screens. This
is probably aimed at "more than 4k" monitors, but for accessibility
reasons it would be really useful to have larger sizes available sooner
for those of us already have 4k sorts of screens.

Perhaps this might best be done by putting those huge-sized fonts in an
appropriately named -huge fonts package? I'll leave the implementation
details to you, this is just a request for the fonts to be created.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages console-setup depends on:
ii  console-setup-linux 1.226
ii  debconf [debconf-2.0]   1.5.86
ii  keyboard-configuration  1.226
ii  xkb-data2.41-2

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales2.37-18
ii  sysvinit-utils [lsb-base]  3.09-1

Versions of packages keyboard-configuration depends on:
ii  debconf [debconf-2.0]   1.5.86
ii  liblocale-gettext-perl  1.07-7
ii  xkb-data2.41-2

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.66
ii  kbd 2.6.4-2
ii  keyboard-configuration  1.226

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.6.4-2
ii  systemd   255.4-1+b1

-- debconf information:
  keyboard-configuration/unsupported_config_options: true
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_options: true
  console-setup/guess_font:
  keyboard-configuration/unsupported_layout: true
  console-setup/fontsize: 16x32
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  keyboard-configuration/optionscode:
  console-setup/framebuffer_only:
  keyboard-configuration/layout:
  console-setup/fontsize-text47: 16x32 (framebuffer only)
* console-setup/charmap47: UTF-8
  keyboard-configuration/other:
  keyboard-configuration/model: Generic 105-key PC
  keyboard-configuration/switch: No temporary switch
* console-setup/fontsize-fb47: 16x32 (framebuffer only)
  keyboard-configuration/store_defaults_in_debconf_db: true
  keyboard-configuration/toggle: No toggling
  console-setup/store_defaults_in_debconf_db: true
  debian-installer/console-setup-udeb/title:
  keyboard-configuration/variantcode:
* keyboard-configuration/variant: English (US)
  console-setup/use_system_font:
  keyboard-configuration/layoutcode: us
  keyboard-configuration/unsupported_config_layout: true
  keyboard-configuration/compose: No compose key
  console-setup/codesetcode: Lat15
* console-setup/fontface47: TerminusBold
  keyboard-configuration/altgr: The default for the keyboard layout
  keyboard-configuration/xkb-keymap: us
  keyboard-configuration/modelcode: pc105
--- End Message ---
--- Begin Message ---
Source: console-setup
Source-Version: 1.227
Done: Holger Wansing 

We believe that the bug you reported is fixed in the latest version of
console-setup, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated console-setup 
package)

(This message was generated automatically at their request; if you
believe 

Bug#816111: marked as done (Larger font variants for HiDPI displays)

2024-05-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 May 2024 10:19:42 +
with message-id 
and subject line Bug#816111: fixed in console-setup 1.227
has caused the Debian Bug report #816111,
regarding Larger font variants for HiDPI displays
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 ow...@bugs.debian.org
immediately.)


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

Package: console-setup
Version: 1.137
Severity: wishlist

With a display close to 300dpi and the proper KMS driver, the framebuffer
effectively becomes HiDPI as well.

The largest font currently available in console-setup is 16x32 pixels, which
might not be big enough to be read confortably anymore.

Having some extra intermediate sizes up to 32x64 might be helpful, without
having to resort to lowering the resolution and incurring in switching between
X11 and the console.

It's a bit sad terminus doesn't include higher sizes, but rasterizing any
monospace TT font with good hinting such a DejaVu Sans Mono at this resolution
should give pretty good results.
--- End Message ---
--- Begin Message ---
Source: console-setup
Source-Version: 1.227
Done: Holger Wansing 

We believe that the bug you reported is fixed in the latest version of
console-setup, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated console-setup 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 30 May 2024 10:54:36 +0200
Source: console-setup
Architecture: source
Version: 1.227
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 816111 1065561 1071823
Changes:
 console-setup (1.227) unstable; urgency=medium
 .
   * Team upload
 .
   [ Jakub Wilk ]
   * typos in documentation (closes: 1065561)
 .
   [ Samuel Thibault ]
   * Fix key types, notably altgr not working with shift.
   * Add dejavu fonts rasterized from the DejaVu vector font. This notably
 provides fonts larger than 32 pixels, usable with linux ≥ 6.9.
 (closes: 816111)
   * rules,control: Add unifont and fonts-dejavu-mono to console-setup-linux
 and console-setup-freebsd's Static-built-Using.
   * console-setup.config, font-switch: Avoid warning on systems that don't
 have lsmod (closes: 1071823)
Checksums-Sha1:
 1a2980dd67a7e582520a1b5115b5f86a0d810d72 3259 console-setup_1.227.dsc
 2d1cffbbb613bc77b395ca19227f67bc73ed8ea9 3886728 console-setup_1.227.tar.xz
 413b978258a209d73c6b783e73e3d9d5df9176b7 19446 
console-setup_1.227_amd64.buildinfo
Checksums-Sha256:
 eddff99ebb438029702dd81e75ffbf3917a84764cbd182b15b5951ff33cd5cf9 3259 
console-setup_1.227.dsc
 a3b3c4f432f0eb0b4753a7967c564ac9eeb7ea7cdb6304318dac7177d3fd94e6 3886728 
console-setup_1.227.tar.xz
 6e9c9fc989f10c9cb3c81b26f37f3ceaa560d0db9ac4b42ac2976f02792b8207 19446 
console-setup_1.227_amd64.buildinfo
Files:
 0dc5fee037939781e96b849b068ad3e7 3259 utils optional console-setup_1.227.dsc
 1802215ed403b52f2f459e1be1358b56 3886728 utils optional 
console-setup_1.227.tar.xz
 b6931907b9477782457b7fa8c6fb7575 19446 utils optional 
console-setup_1.227_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZYTz8VHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2Xw0QALHjwsIk4/eGatQsCpPcAN3VkLWa
yPGTvEelLmZJ1Vmk1cTuS/2oCOQkiovLgGWNr+290W5zCKvPZ/4WIF4UwqUL+bWh
6EfwXP8sygRRCe6VVNKULYR7q60reVpxEN2ru5/DDAKXNpi+kw4fBB0/fpZ+LF1e
8K1CHSGH2bJ2jDk/QWVpPbIWF5xMIa4SurFFNe/9RMHYouDIglXmcsVoD+2FMWMi
SELpmzDRiX3sGaKhx8RiSKzEXBBYssObsSrxbKLayASQsZHC/ybLOtzoxq6NfM+c
yv57ZRqA8kA3yOrjNO+qGjRJ6VUCVKL5xY2TEI0Uih9t3y1Tak2s2TcxCZCsiHvs
AQUWooDN5Hx+UMe80PISQ44uj0P4xOq8xIdCCUqk1+4oj35BIYplDRf2trY6d6Xs
TSbw1BwDbjhzem1klZpRrCfyypZiXpfJTlyzBZS+AYpq1Nq0Ef2vJ8YBAQE38kSt
TmSKfGE1xsYepG/cH/iwyAie5yGQMke2US3kA/uU3lwvsNUeKJF7V8a5oO89adZR
r/+hdDE7AgUsu5yJMki/6Fsl5wJ02RCiBX5B21ze/B1ZgBYEQ1yUQ2ZvDz714BZx
P2O/X25aWJMhoFC99YYn3h1TKhgJ3egaS5yojhVY1ufX2QD5cTuhX3HDai9TsPd0
hE9rXNhT1GvIoYNh
=lWNN
-END PGP SIGNATURE-



pgpLCg_4B8QBW.pgp
Description: PGP signature
--- End Message 

Bug#1071823: marked as done (console-setup: [Hurd i386] debconf: lsmod: not found)

2024-05-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 May 2024 10:19:42 +
with message-id 
and subject line Bug#1071823: fixed in console-setup 1.227
has caused the Debian Bug report #1071823,
regarding console-setup: [Hurd i386] debconf: lsmod: not found
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 ow...@bugs.debian.org
immediately.)


-- 
1071823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: console-setup
Version: 1.223
Severity: important

While upgrading from 1.223 to 1.226 on Hurd i386:

Fetched 32.4 MB in 23s (1429 kB/s)  

   
Extracting templates from packages: 100%
Preconfiguring packages ...
/var/cache/debconf/tmp.ci/console-setup.config.otOVsK: 1196: lsmod: not found

-- System Information:
Debian Release: trixie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.8+git20231217-486/Hurd-0.9
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages console-setup depends on:
ii  debconf [debconf-2.0]   1.5.85
ii  hurd1:0.9.git20231217-1
ii  keyboard-configuration  1.223
ii  xkb-data2.38-2

console-setup recommends no packages.

Versions of packages console-setup suggests:
iu  locales2.38-11
ii  sysvinit-utils [lsb-base]  3.08-6

Versions of packages keyboard-configuration depends on:
ii  debconf [debconf-2.0]   1.5.85
ii  liblocale-gettext-perl  1.07-6+b1
ii  xkb-data2.38-2

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
pn  kbd   
pn  systemd   

-- debconf information:
* keyboard-configuration/variant: Finnish
* keyboard-configuration/optionscode:
* keyboard-configuration/modelcode: pc105
* console-setup/codesetcode: guess
* console-setup/charmap47: UTF-8
* keyboard-configuration/compose: No compose key
* keyboard-configuration/model: Generic 105-key PC
* console-setup/store_defaults_in_debconf_db: false
* keyboard-configuration/store_defaults_in_debconf_db: false
* keyboard-configuration/toggle: No toggling
  console-setup/guess_font:
* console-setup/fontface47: Fixed
  debian-installer/console-setup-udeb/title:
* keyboard-configuration/other:
  console-setup/framebuffer_only:
* keyboard-configuration/altgr: The default for the keyboard layout
* console-setup/fontsize-text47: 8x16
* keyboard-configuration/layout:
  keyboard-configuration/unsupported_options: true
* console-setup/fontsize: 8x16
  keyboard-configuration/unsupported_config_layout: true
* keyboard-configuration/ctrl_alt_bksp: false
* console-setup/codeset47: Guess optimal character set
  console-setup/use_system_font:
  keyboard-configuration/unsupported_layout: true
* keyboard-configuration/switch: No temporary switch
* keyboard-configuration/layoutcode: fi
* keyboard-configuration/xkb-keymap: fi
  keyboard-configuration/unsupported_config_options: true
* keyboard-configuration/variantcode:
* console-setup/fontsize-fb47: 8x16
--- End Message ---
--- Begin Message ---
Source: console-setup
Source-Version: 1.227
Done: Holger Wansing 

We believe that the bug you reported is fixed in the latest version of
console-setup, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1071...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated console-setup 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 30 May 2024 10:54:36 +0200
Source: console-setup
Architecture: source
Version: 1.227
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 816111 1065561 1071823
Changes:
 console-setup (1.227) unstable; urgency=medium
 .
   * Team upload
 .
   [ Jakub Wilk ]
   * typos in 

Bug#1065561: marked as done (console-setup: typos in documentation)

2024-05-30 Thread Debian Bug Tracking System
Your message dated Thu, 30 May 2024 10:19:42 +
with message-id 
and subject line Bug#1065561: fixed in console-setup 1.227
has caused the Debian Bug report #1065561,
regarding console-setup: typos in documentation
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 ow...@bugs.debian.org
immediately.)


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

Source: console-setup
Version: 1.226
Severity: minor
Tags: patch

--
Jakub Wilk
diff --git a/README.legacyfonts b/README.legacyfonts
index a707fcc..2078725 100644
--- a/README.legacyfonts
+++ b/README.legacyfonts
@@ -4,3 +4,3 @@ LEGACY FONTS: CONVERSION FROM PSF TO BDF
 
-The traditional font collection for Linux consolle was a big mess.
+The traditional font collection for Linux console was a big mess.
 There were many different fonts and nobody in the world knew the exact
@@ -18,4 +18,4 @@ generated for a group of fonts that share common typeface.  Console
 fonts that didn't have embedded Unicode table were simply ignored.
-The fonts LatArCyrHeb* were also ignored - partialy due to technical
-reasons and partialy because the other BDF fonts are better source for
+The fonts LatArCyrHeb* were also ignored - partially due to technical
+reasons and partially because the other BDF fonts are better source for
 making Unicode console fonts.
@@ -43,3 +43,3 @@ For example Greek-vga14.psf is the legacy font for Greek code set and
 size 14.  The list of BDF fonts that is used to produce
-Greek-vga14.psf was determined as folows.
+Greek-vga14.psf was determined as follows.
 
diff --git a/doc/console-setup.html/ch3.html b/doc/console-setup.html/ch3.html
index c2d3a1f..bc74c33 100644
--- a/doc/console-setup.html/ch3.html
+++ b/doc/console-setup.html/ch3.html
@@ -64,4 +64,4 @@ for a group of fonts that share common typeface.  Console fonts that didn't
 have embedded Unicode table were simply ignored.  The fonts
-LatArCyrHeb* were also ignored - partialy due to technical reasons
-and partialy because the other BDF fonts are better source for making Unicode
+LatArCyrHeb* were also ignored - partially due to technical reasons
+and partially because the other BDF fonts are better source for making Unicode
 console fonts.
@@ -148,3 +148,3 @@ fonts.  This font is named after the scheme
 size 14.  The list of BDF fonts that is used to produce Greek-vga14.psf was
-determined as folows.
+determined as follows.
 
diff --git a/doc/console-setup.sgml b/doc/console-setup.sgml
index 46e16a6..54f7fdf 100644
--- a/doc/console-setup.sgml
+++ b/doc/console-setup.sgml
@@ -388,3 +388,3 @@ Console fonts that didn't have embedded Unicode table were simply
 ignored.  The fonts LatArCyrHeb* were also ignored -
-partialy due to technical reasons and partialy because the other BDF
+partially due to technical reasons and partially because the other BDF
 fonts are better source for making Unicode console fonts.
@@ -465,3 +465,3 @@ from the legacy fonts.  This font is named after the scheme
 set and size 14.  The list of BDF fonts that is used to produce
-Greek-vga14.psf was determined as folows.
+Greek-vga14.psf was determined as follows.
 
--- End Message ---
--- Begin Message ---
Source: console-setup
Source-Version: 1.227
Done: Holger Wansing 

We believe that the bug you reported is fixed in the latest version of
console-setup, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated console-setup 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 30 May 2024 10:54:36 +0200
Source: console-setup
Architecture: source
Version: 1.227
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 816111 1065561 1071823
Changes:
 console-setup (1.227) unstable; urgency=medium
 .
   * Team upload
 .
   [ Jakub Wilk ]
   * typos in documentation (closes: 1065561)
 .
   [ Samuel Thibault ]
   * Fix key types, notably altgr not working with shift.
   * Add dejavu fonts rasterized from the DejaVu vector font. This notably
 

console-setup_1.227_source.changes ACCEPTED into unstable

2024-05-30 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 30 May 2024 10:54:36 +0200
Source: console-setup
Architecture: source
Version: 1.227
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 816111 1065561 1071823
Changes:
 console-setup (1.227) unstable; urgency=medium
 .
   * Team upload
 .
   [ Jakub Wilk ]
   * typos in documentation (closes: 1065561)
 .
   [ Samuel Thibault ]
   * Fix key types, notably altgr not working with shift.
   * Add dejavu fonts rasterized from the DejaVu vector font. This notably
 provides fonts larger than 32 pixels, usable with linux ≥ 6.9.
 (closes: 816111)
   * rules,control: Add unifont and fonts-dejavu-mono to console-setup-linux
 and console-setup-freebsd's Static-built-Using.
   * console-setup.config, font-switch: Avoid warning on systems that don't
 have lsmod (closes: 1071823)
Checksums-Sha1:
 1a2980dd67a7e582520a1b5115b5f86a0d810d72 3259 console-setup_1.227.dsc
 2d1cffbbb613bc77b395ca19227f67bc73ed8ea9 3886728 console-setup_1.227.tar.xz
 413b978258a209d73c6b783e73e3d9d5df9176b7 19446 
console-setup_1.227_amd64.buildinfo
Checksums-Sha256:
 eddff99ebb438029702dd81e75ffbf3917a84764cbd182b15b5951ff33cd5cf9 3259 
console-setup_1.227.dsc
 a3b3c4f432f0eb0b4753a7967c564ac9eeb7ea7cdb6304318dac7177d3fd94e6 3886728 
console-setup_1.227.tar.xz
 6e9c9fc989f10c9cb3c81b26f37f3ceaa560d0db9ac4b42ac2976f02792b8207 19446 
console-setup_1.227_amd64.buildinfo
Files:
 0dc5fee037939781e96b849b068ad3e7 3259 utils optional console-setup_1.227.dsc
 1802215ed403b52f2f459e1be1358b56 3886728 utils optional 
console-setup_1.227.tar.xz
 b6931907b9477782457b7fa8c6fb7575 19446 utils optional 
console-setup_1.227_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZYTz8VHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2Xw0QALHjwsIk4/eGatQsCpPcAN3VkLWa
yPGTvEelLmZJ1Vmk1cTuS/2oCOQkiovLgGWNr+290W5zCKvPZ/4WIF4UwqUL+bWh
6EfwXP8sygRRCe6VVNKULYR7q60reVpxEN2ru5/DDAKXNpi+kw4fBB0/fpZ+LF1e
8K1CHSGH2bJ2jDk/QWVpPbIWF5xMIa4SurFFNe/9RMHYouDIglXmcsVoD+2FMWMi
SELpmzDRiX3sGaKhx8RiSKzEXBBYssObsSrxbKLayASQsZHC/ybLOtzoxq6NfM+c
yv57ZRqA8kA3yOrjNO+qGjRJ6VUCVKL5xY2TEI0Uih9t3y1Tak2s2TcxCZCsiHvs
AQUWooDN5Hx+UMe80PISQ44uj0P4xOq8xIdCCUqk1+4oj35BIYplDRf2trY6d6Xs
TSbw1BwDbjhzem1klZpRrCfyypZiXpfJTlyzBZS+AYpq1Nq0Ef2vJ8YBAQE38kSt
TmSKfGE1xsYepG/cH/iwyAie5yGQMke2US3kA/uU3lwvsNUeKJF7V8a5oO89adZR
r/+hdDE7AgUsu5yJMki/6Fsl5wJ02RCiBX5B21ze/B1ZgBYEQ1yUQ2ZvDz714BZx
P2O/X25aWJMhoFC99YYn3h1TKhgJ3egaS5yojhVY1ufX2QD5cTuhX3HDai9TsPd0
hE9rXNhT1GvIoYNh
=lWNN
-END PGP SIGNATURE-



pgpNPqgcuKICF.pgp
Description: PGP signature


Re: migrating grub from BIOS to UEFI loses /etc/default/grub

2024-05-30 Thread Felix Zielcke
Am Dienstag, dem 28.05.2024 um 00:16 +0200 schrieb Pascal Hambourg:
> - Remove /etc/default/grub only if it is associated with the package 
> being purged in ucf.
> 
> - Do not remove /etc/default/grub when purging package-
> because 
> it is used by grub-install and update-grub which belong to grub2-
> common; 
> only remove it from ucf registry if it is associated with the package
> being purged.
> 

I did now a MR for this:

https://salsa.debian.org/grub-team/grub/-/merge_requests/62

> Also, it appears that grub-pc.postrm purge optionally removes files
> in 
> /boot/grub which may have been installed for other grub targets 
> (grub.cfg, fonts, locales, device.map, grubenv, background image
> cache).
> My opinion is that postrm should not touch /boot/grub at all. After
> all, 
> it does not remove GRUB boot image and core image nor EFI partition 
> contents.
> 
> Grub-team people, any comments ?
> 

d-boot is actually the wrong mailing list to discuss grub.
Despite its name it's mostly for debian-installer.
I don't know if the others are even subscribed to d-boot.

/boot/grub for grub-pc is only purged if debconf has 
grub-pc/postrm_purge_boot_grub == true

But I don't know the reason why unicode.pf2 is purged for grub-efi-
{amd64,i386}



Bug#1072204: setupcon: race condition with systemd-tmpfiles

2024-05-30 Thread Marc Leeman
Package: console-setup
Version: 1.226
Severity: normal
Tags: patch

Dear Maintainer,

On occasion I have a situation where console-setup.service fails to
start up due to a race condition. After investigating this, it was
already reported in Ubuntu back in 2019 and I have verified that the
patch they have implemented resolves the issue for me:

admin@boxpc001-a8f7693fbff14940ade0e3247b1cea8e:~$ for s in $(systemctl 
list-units --type service --full --failed --plain --no-legend | cut -f 1 -d ' 
'); do journalctl --boot --no-pager --unit "${s}"; done
May 28 13:15:05 boxpc001 systemd[1]: Starting console-setup.service - Set 
console font and keymap...
May 28 13:15:05 boxpc001 console-setup.sh[588]: /usr/bin/setupcon: 999: cannot 
open /tmp/tmpkbd.hoHrPK: No such file
May 28 13:15:05 boxpc001 systemd[1]: console-setup.service: Main process 
exited, code=exited, status=1/FAILURE
May 28 13:15:05 boxpc001 systemd[1]: console-setup.service: Failed with result 
'exit-code'.
May 28 13:15:05 boxpc001 systemd[1]: Failed to start console-setup.service - 
Set console font and keymap.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (400, 
'bookworm'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages console-setup depends on:
ii  console-setup-linux 1.226
ii  debconf [debconf-2.0]   1.5.86
ii  keyboard-configuration  1.226
ii  xkb-data2.41-2

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales2.38-11
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.09-1

Versions of packages keyboard-configuration depends on:
ii  debconf [debconf-2.0]   1.5.86
ii  liblocale-gettext-perl  1.07-7
ii  xkb-data2.41-2

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.66
ii  kbd 2.6.4-2
ii  keyboard-configuration  1.226

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
ii  gnome-control-center  1:46.0.1-1
ii  kbd   2.6.4-2
ii  systemd   255.5-1

-- debconf information:
* keyboard-configuration/optionscode:
  console-setup/use_system_font:
  console-setup/store_defaults_in_debconf_db: true
  debian-installer/console-setup-udeb/title:
  keyboard-configuration/unsupported_config_layout: true
* keyboard-configuration/model: Generic 105-key PC
* keyboard-configuration/store_defaults_in_debconf_db: true
* keyboard-configuration/switch: No temporary switch
* keyboard-configuration/layout:
  keyboard-configuration/unsupported_layout: true
  console-setup/fontsize: 8x16
  console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  console-setup/guess_font:
* keyboard-configuration/layoutcode: us
* keyboard-configuration/altgr: The default for the keyboard layout
  console-setup/fontsize-fb47: 8x16
* keyboard-configuration/xkb-keymap: us
* keyboard-configuration/variantcode:
* keyboard-configuration/toggle: No toggling
* keyboard-configuration/modelcode: pc105
* keyboard-configuration/compose: No compose key
  console-setup/fontface47: Fixed
  console-setup/framebuffer_only:
* keyboard-configuration/other:
  console-setup/fontsize-text47: 8x16
  console-setup/codesetcode: Lat15
* keyboard-configuration/variant: English (US)
  keyboard-configuration/unsupported_options: true
  console-setup/charmap47: UTF-8
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_config_options: true
diff -Nru console-setup-1.108ubuntu15.4/debian/changelog 
console-setup-1.108ubuntu15.5/debian/changelog
--- console-setup-1.108ubuntu15.4/debian/changelog  2017-10-05 
19:36:07.0 +
+++ console-setup-1.108ubuntu15.5/debian/changelog  2019-04-10 
20:16:29.0 +
@@ -1,3 +1,13 @@
+console-setup (1.108ubuntu15.5) xenial; urgency=medium
+
+  * setupcon: use /run for tempfiles (and dump the various unnecessary
+fallback paths), since /run is always mountable rw at least as early as
+/tmp is and is guaranteed to be safe from tmpcleaners at boot.  Only keep
+/tmp as a fallback in case we have access to write to /tmp and to a
+console, but not to /run.  LP: #1824227.
+
+ -- Steve Langasek   Wed, 10 Apr 2019 13:16:29 -0700
+
 console-setup (1.108ubuntu15.4) xenial; urgency=medium
 
* Drop dependency from console-setup to initramfs-tools |
diff -Nru console-setup-1.108ubuntu15.4/setupcon 
console-setup-1.108ubuntu15.5/setupcon
--- 

Processed: raise remaining usrmerge normal bugs to important

2024-05-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1055514 important
Bug #1055514 [opensysusers] opensysusers: ineffective diversion of 
/bin/systemd-sysusers due to /usr-merge and DEP17
Severity set to 'important' from 'normal'
> severity 1063878 important
Bug #1063878 [di-utils] di-utils: chroot-setup.sh creates ineffective 
diversions (DEP17)
Ignoring request to change severity of Bug 1063878 to the same value.
> severity 1064408 important
Bug #1064408 [live-build] [PATCH] duplicate aliased diversions for DEP17
Ignoring request to change severity of Bug 1064408 to the same value.
> severity 1063572 important
Bug #1063572 [jfsutils] jfsutils: move files to /usr (DEP17)
Ignoring request to change severity of Bug 1063572 to the same value.
> severity 1064449 important
Bug #1064449 [open-infrastructure-system-build] 
open-infrastructure-system-build: ineffective diversions due to /usr-move 
(DEP17)
Ignoring request to change severity of Bug 1064449 to the same value.
> severity 1061855 important
Bug #1061855 [src:libpam-ssh] libpam-ssh: install PAM module into /usr
Severity set to 'important' from 'normal'
> severity 1064315 important
Bug #1064315 [src:alsa-topology-conf] alsa-topology-conf: install firmware 
files into /usr
Severity set to 'important' from 'normal'
> severity 1063552 important
Bug #1063552 [libfreebsd-glue-0] libfreebsd-glue-0: move files to /usr (DEP17)
Severity set to 'important' from 'normal'
> severity 1061332 important
Bug #1061332 [src:cifs-utils] cifs-utils: install files into /usr
Severity set to 'important' from 'normal'
> severity 1064299 important
Bug #1064299 [src:console-setup] console-setup: move files to /usr (DEP17)
Severity set to 'important' from 'normal'
> severity 1063696 important
Bug #1063696 [src:freebsd-libs] freebsd-libs: move libraries to /usr (DEP17)
Severity set to 'important' from 'normal'
> severity 1064125 important
Bug #1064125 [src:libnss-pgsql] libnss-pgsql: install NSS module into /usr
Severity set to 'important' from 'normal'
> severity 1064396 important
Bug #1064396 [src:libinput] libinput: install udev files into /usr
Severity set to 'important' from 'normal'
> severity 1064888 important
Bug #1064888 [src:bash] bash: move files to /usr (DEP17)
Severity set to 'important' from 'normal'
> severity 1063620 important
Bug #1063620 [src:ukui-biometric-auth] ukui-biometric-auth: install PAM module 
into /usr
Severity set to 'important' from 'normal'
> severity 1054090 important
Bug #1054090 [src:zram-tools] zram-tools: let dh_installsystemd choose the 
location of the unit
Ignoring request to change severity of Bug 1054090 to the same value.
> severity 1061865 important
Bug #1061865 [src:oddjob] oddjob: install PAM module into /usr
Severity set to 'important' from 'normal'
> severity 1063693 important
Bug #1063693 [src:xdm] xdm: move systemd unit to /usr (DEP17)
Ignoring request to change severity of Bug 1063693 to the same value.
> severity 1064046 important
Bug #1064046 [src:pam-python] pam-python: install PAM module into /usr
Severity set to 'important' from 'normal'
> severity 1064400 important
Bug #1064400 [src:discover-data] discover-data: install files into /usr
Severity set to 'important' from 'normal'
> severity 1054084 important
Bug #1054084 [src:crowdsec] let dh_installsystemd choose the location of 
systemd units
Ignoring request to change severity of Bug 1054084 to the same value.
> severity 1064126 important
Bug #1064126 [src:libvirt] libvirt: install NSS modules and systemd units into 
/usr
Severity set to 'important' from 'normal'
> severity 1054191 important
Bug #1054191 [src:memlockd] memlockd: installs an empty /lib/systemd/system 
once dh_installsystemd installs to /usr
Ignoring request to change severity of Bug 1054191 to the same value.
> severity 1061527 important
Bug #1061527 [src:elogind] elogind: install files into /usr
Severity set to 'important' from 'normal'
> severity 1061851 important
Bug #1061851 [src:libpam-script] libpam-script: install PAM module into /usr
Severity set to 'important' from 'normal'
> severity 1061337 important
Bug #1061337 [src:google-compute-engine-oslogin] google-compute-engine-oslogin: 
install files into /usr
Severity set to 'important' from 'normal'
> severity 1061353 important
Bug #1061353 [src:pam-krb5-migrate] pam-krb5-migrate: install PAM modules into 
/usr
Severity set to 'important' from 'normal'
> severity 1064316 important
Bug #1064316 [src:rtkit] rtkit: install systemd units into /usr
Severity set to 'important' from 'normal'
> severity 1063622 important
Bug #1063622 [src:otpw] otpw: install PAM module into /usr
Severity set to 'important' from 'normal'
> severity 1063571 important
Bug #1063571 [libpcre3] libpcre3: move libraries to /usr (DEP17)
Severity set to 'important' from 'normal'
> severity 1064045 important
Bug #1064045 [src:pam-pgsql] pam-pgsql: install PAM module into /usr
Severity set to 'important' from 'normal'
> severity 1063699 important
Bug #1063699 [tarantool-common] 

Processed: more usrmerge bugs to important

2024-05-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1063693 important
Bug #1063693 [src:xdm] xdm: move systemd unit to /usr (DEP17)
Severity set to 'important' from 'normal'
> severity 1063572 important
Bug #1063572 [jfsutils] jfsutils: move files to /usr (DEP17)
Severity set to 'important' from 'normal'
> severity 1051460 important
Bug #1051460 [src:crowdsec-custom-bouncer] crowdsec-custom-bouncer: move 
systemd units to /usr
Severity set to 'important' from 'wishlist'
> severity 1054013 important
Bug #1054013 [src:dnssec-trigger] dnssec-trigger: defer location of systemd 
units to systemd.pc
Severity set to 'important' from 'normal'
> severity 1054084 important
Bug #1054084 [src:crowdsec] let dh_installsystemd choose the location of 
systemd units
Severity set to 'important' from 'normal'
> severity 1054086 important
Bug #1054086 [src:lsm] lsm: let dh_installsystemd choose the location of units
Severity set to 'important' from 'normal'
> severity 1054088 important
Bug #1054088 [src:sanoid] sanoid: let dh_installsystemd choose the location of 
units
Severity set to 'important' from 'normal'
> severity 1054089 important
Bug #1054089 [src:php-defaults] php-common: let dh_installsystemd choose the 
location of units
Severity set to 'important' from 'normal'
> severity 1054090 important
Bug #1054090 [src:zram-tools] zram-tools: let dh_installsystemd choose the 
location of the unit
Severity set to 'important' from 'normal'
> severity 1054093 important
Bug #1054093 [src:monit] monit: let dh_installsystemd choose the location of 
units
Severity set to 'important' from 'normal'
> severity 1054191 important
Bug #1054191 [src:memlockd] memlockd: installs an empty /lib/systemd/system 
once dh_installsystemd installs to /usr
Severity set to 'important' from 'normal'
> severity 1064449 important
Bug #1064449 [open-infrastructure-system-build] 
open-infrastructure-system-build: ineffective diversions due to /usr-move 
(DEP17)
Severity set to 'important' from 'normal'
> severity 1063455 important
Bug #1063455 [open-infrastructure-compute-tools] 
open-infrastructure-compute-tools: move files to /usr for DEP17
Severity set to 'important' from 'normal'
> severity 1063458 important
Bug #1063458 [open-infrastructure-storage-tools] 
open-infrastructure-storage-tools: move files to /usr for DEP17
Severity set to 'important' from 'normal'
> severity 1067817 important
Bug #1067817 [libfuse2t64] libfuse2: move library to /usr (DEP17 P1)
Ignoring request to change severity of Bug 1067817 to the same value.
> severity 1063878 important
Bug #1063878 [di-utils] di-utils: chroot-setup.sh creates ineffective 
diversions (DEP17)
Severity set to 'important' from 'normal'
> severity 1064408 important
Bug #1064408 [live-build] [PATCH] duplicate aliased diversions for DEP17
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1051460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051460
1054013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054013
1054084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054084
1054086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054086
1054088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054088
1054089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054089
1054090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054090
1054093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054093
1054191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054191
1063455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063455
1063458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063458
1063572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063572
1063693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063693
1063878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063878
1064408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064408
1064449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064449
1067817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1072188: Package error

2024-05-29 Thread Peter Carter

Package: installation-reports

Boot method: 
Image version: 
Date: 

Machine: Dell 7020
Processor:Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
Memory: 16G
Partitions:
filesystem Type 1K-blocks Used Available Use% Mounted on 
udev   devtmpfs   8108416    0   8108416   0% /dev tmpfs 
 tmpfs  1628976 1552   1627424   1% /run /dev/sda3 
 btrfs    468253696 32781716 430568940   8% / tmpfs  tmpfs 
 8144876    0   8144876   0% /dev/shm tmpfs  tmpfs 
5120   16  5104   1% /run/lock efivarfs   efivarfs 
  128   96    28  78% /sys/firmware/efi/efivars /dev/sdb1 
 btrfs    976761560 5920 974597824   1% /data /dev/sda1 
 vfat    497684 4480    493204   1% /boot/efi overlay 
   overlay  468253696 32781716 430568940   8% 
/var/lib/docker/overlay2/afa24d7e3210883370c5732 
914467d97f210df47b7a7635495e899928a72/merged tmpfs  tmpfs 
 1628972  232   1628740   1% /run/user/1000


Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor 
DRAM Controller [8086:0c00] (rev 06)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: hsw_uncore 00:02.0 VGA 
compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller [8086:0412] (rev 06) 
   DeviceName:  Onboard IGD    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: i915    Kernel modules: 
i915 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor HD Audio Controller [808 6:0c0c] (rev 06) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
snd_hda_intel    Kernel modules: snd_hda_intel 00:14.0 USB 
controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI [8086:8c31] (rev 04)    Subsystem: Dell Device [1028:05a5] 
   Kernel driver in use: xhci_hcd    Kernel modules: xhci_pci 
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 
Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
mei_me    Kernel modules: mei_me 00:19.0 Ethernet controller [0200]: 
Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 04) 
   DeviceName:  Onboard LAN    Subsystem: Dell Device 
[1028:05a4]    Kernel driver in use: e1000e    Kernel modules: 
e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 
Series Chipset Family USB EHCI #2 [8086:8c2d] ( rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
ehci-pci    Kernel modules: ehci_pci 00:1b.0 Audio device [0403]: 
Intel Corporation 8 Series/C220 Series Chipset High Definition Audio 
Controller [ 8086:8c20] (rev 04)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: snd_hda_intel    Kernel 
modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 8 
Series/C220 Series Chipset Family PCI Express Root Port #1 [808 6:8c10] 
(rev d4)    Subsystem: Dell Device [1028:05a5]    Kernel driver 
in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 8 
Series/C220 Series Chipset Family PCI Express Root Port #5 [808 6:8c18] 
(rev d4)    Subsystem: Dell Device [1028:05a5]    Kernel driver 
in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 8 
Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] ( rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
ehci-pci    Kernel modules: ehci_pci 00:1f.0 ISA bridge [0601]: 
Intel Corporation Q87 Express LPC Controller [8086:8c4e] (rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
lpc_ich    Kernel modules: lpc_ich 00:1f.2 SATA controller [0106]: 
Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA 
Controller 1 [AHCI mode] [8086:8c02] (rev 04)    DeviceName: 
 Onboard SATA controller #1    Subsystem: Dell Device [1028:05a5] 
   Kernel driver in use: ahci    Kernel modules: ahci 00:1f.3 
SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family 
SMBus Controller [8086:8c22] (rev 04)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: i801_smbus    Kernel 
modules: i2c_i801 02:00.0 Network controller [0280]: Intel Corporation 
Wireless 7265 [8086:095a] (rev 59)    Subsystem: Intel Corporation 
Dual Band Wireless-AC 7265 [Stone Peak 2 AC] [8086:5010]    Kernel 
driver in use: iwlwifi    Kernel modules: iwlwifi


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

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

Bug#1071903: hw-detect: USB wireless adapter r8712u needs physical disconnect and reconnect for firmware to work

2024-05-29 Thread Pascal Hambourg

On 26/05/2024 at 22:29, Roland Clobus wrote:


Your patch series works fine, the firmware is correctly identified and 
loaded. Unfortunately for me, it still needs a reconnect cycle.

See the attached syslog for their effect. (I've used sid)


Thank you for testing my patches but I did not expect them to solve the 
reattachment issue, only to identify the right module.


After the r8712u module is first loaded without the firmware then 
unloaded and reloaded, what is the output of


ls -d /sys/bus/usb/drivers/r8712u/1-3*
ls -d /sys/bus/usb/devices/1-3/1-3*

assuming the wireless adapter is identified as 1-3 ?



Processed: Re: Bug#1072092: piuparts: switch default tmpdir to /var/tmp/

2024-05-29 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 - piuparts debos vmdb2
Bug #1072092 [debootstrap] piuparts: switch default tmpdir to /var/tmp/
Removed indication that 1072092 affects piuparts, debos, and vmdb2
> reassign -1 piuparts
Bug #1072092 [debootstrap] piuparts: switch default tmpdir to /var/tmp/
Bug reassigned from package 'debootstrap' to 'piuparts'.
Ignoring request to alter found versions of bug #1072092 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1072092 to the same values 
previously set

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



Bug#1072092: piuparts: switch default tmpdir to /var/tmp/

2024-05-29 Thread Luca Boccassi
Control: affects -1 - piuparts debos vmdb2
Control: reassign -1 piuparts

On Tue, 28 May 2024 13:14:00 +0200 Helmut Grohne 
wrote:
> Control: reassign -1 debootstrap
> Control: affects -1 + piuparts debos vmdb2
> 
> On Tue, May 28, 2024 at 12:08:37PM +0100, Luca Boccassi wrote:
> > When piuparts runs debootstrap, it is pointed to the default --
tmpdir,
> > which absent any configuration or env var is /tmp/, which is now
(since
> > systemd 256~rc3-3) a tmpfs, which as it is expected it is mounted
with
> > noudev for security reasons, but debootstrap doesn't like that as
it
> > wants to create fresh node files.
> 
> This is a problem in debootstrap. debootstrap should refrain from
> creating device nodes when doing so is not possible. Most consumers
of
> debootstrap bind mount /dev already. Reassigning.

Feel free to work on that if you like, but it is unrelated

> > Please make piuparts --tmpdir default to /var/tmp if nothing is
set, to
> > avoid this issue.
> 
> Please don't as that would make reduce piuparts performance to crap.

Currently /tmp is on the same filesystem as /var/tmp, so there are zero
performance differences. It's just a default, you can change it as you
see fit if you have some special local setup.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part


Bug#1064005: marked as done (netcfg: "get_netmask string 255.255.255.255" not working)

2024-05-28 Thread Debian Bug Tracking System
Your message dated Tue, 28 May 2024 21:17:09 +
with message-id 
and subject line Bug#1064005: fixed in netcfg 1.187+deb12u1
has caused the Debian Bug report #1064005,
regarding netcfg: "get_netmask string 255.255.255.255" not working
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 ow...@bugs.debian.org
immediately.)


-- 
1064005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netcfg
Version: 1.187
Severity: normal

Dear Maintainer,

Setting a netmask of 255.255.255.255 (in my case using preseed, but I guess the 
same happens if using the UI)
fails the installer with Unreachable gateway (even if the gateway is set).
I agree it can be seen as an odd setup, but it's valid and works when 
configured manually in busybox and Linux.
My usecase is creating routed Debian VMs, where the host have a static route to 
the guest's IP (or v6 /128).
With a smaller subnet (like /23), we would have to use proxy ARP which is 
usually not recommended.

You can see more information in:
https://phabricator.wikimedia.org/phame/post/view/312/ganeti_on_modern_network_design/

My current workaround is to use a smaller netmask then run the following in 
early_command:
IFACE=$(ip -4 route list 0/0 | sed -r 's/.*dev ([^ ]*) .*/\1/' | head -1)
IP="$(ip address show dev $IFACE | egrep '^[[:space:]]+inet ' | cut -d ' ' -f 6 
| cut -d '/' -f 1)"
ip addr del $IP dev $IFACE
ip addr add $IP/32 dev $IFACE
ip route add 10.192.24.1 dev $IFACE scope link
ip route add default via 10.192.24.1

Right after "netcfg"
It would of course be cleaner if netcfg were to handle a /32 "out of the box".

Similarly, DHCP can allocate such IPs, see for example :
https://blog.fhrnet.eu/2020/03/07/dhcp-server-on-a-32-subnet/
I haven't tested DHCP in Debian Installer with such setup though.

Please let me know if I can be of any help.

Thanks

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: netcfg
Source-Version: 1.187+deb12u1
Done: Colin Watson 

We believe that the bug you reported is fixed in the latest version of
netcfg, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated netcfg package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 21 May 2024 17:32:45 +0100
Source: netcfg
Architecture: source
Version: 1.187+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Colin Watson 
Closes: 1064005
Changes:
 netcfg (1.187+deb12u1) bookworm; urgency=medium
 .
   * Handle routing for single-address netmasks (closes: #1064005).
Checksums-Sha1:
 7e3dbc53ae323a06de302abfe913e6250999ca55 1929 netcfg_1.187+deb12u1.dsc
 b4d9351abcc72e6623d08f7ce1a5ad6cc4e6e2d1 403188 netcfg_1.187+deb12u1.tar.xz
Checksums-Sha256:
 b15307ed1ec700e3c41c6f2a41a468a7e6aad4ba86f36716b9b24f5b3e166c4d 1929 
netcfg_1.187+deb12u1.dsc
 a3bdde6687b8489b97e7d0ebb08edee3466f3a3b048a90c9d7125863502039ef 403188 
netcfg_1.187+deb12u1.tar.xz
Files:
 bcd770b14c476c7c87fd73d6d04d 1929 debian-installer optional 
netcfg_1.187+deb12u1.dsc
 bd15007249be40c9041d1d0178ecb755 403188 debian-installer optional 
netcfg_1.187+deb12u1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmZMzRoACgkQOTWH2X2G
UAscLRAAo/M1CE6pPU6mUJwspR5FS1IRVIpQN9Qg2yWS/sYINx8VI0+AxEWVgQ30
9qTsNIl4ZVaSKLMDghkTTF8jN9SOMtnlvNpZn5P7x/oRLeBYhDe5guParHv4ozQz
vs0HeCuYKdVa8v6riBnhvA1JAvwCk6AXomunys+ZoIxNeqLsW3A0GauoAQRRwsWg
JrdupiBucfdQw0hY11ZdX7flHhwGDulZEnagtnlzJhpbix3rfnncbRUKCMi78C8N
6vLQRbMaUKIjnKcwfjwb7x+ffxHWzqr3nIqi4U7ZKLUFJ0uVAQnKX0PTraypHNrj
sMQ+oFsdyjZhEVkgfwgFWC4qsNy0mzPzX+1LjQDgwatxwLcQPoVvTaMweQJpQ5M4

netcfg_1.187+deb12u1_source.changes ACCEPTED into proposed-updates

2024-05-28 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 21 May 2024 17:32:45 +0100
Source: netcfg
Architecture: source
Version: 1.187+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Colin Watson 
Closes: 1064005
Changes:
 netcfg (1.187+deb12u1) bookworm; urgency=medium
 .
   * Handle routing for single-address netmasks (closes: #1064005).
Checksums-Sha1:
 7e3dbc53ae323a06de302abfe913e6250999ca55 1929 netcfg_1.187+deb12u1.dsc
 b4d9351abcc72e6623d08f7ce1a5ad6cc4e6e2d1 403188 netcfg_1.187+deb12u1.tar.xz
Checksums-Sha256:
 b15307ed1ec700e3c41c6f2a41a468a7e6aad4ba86f36716b9b24f5b3e166c4d 1929 
netcfg_1.187+deb12u1.dsc
 a3bdde6687b8489b97e7d0ebb08edee3466f3a3b048a90c9d7125863502039ef 403188 
netcfg_1.187+deb12u1.tar.xz
Files:
 bcd770b14c476c7c87fd73d6d04d 1929 debian-installer optional 
netcfg_1.187+deb12u1.dsc
 bd15007249be40c9041d1d0178ecb755 403188 debian-installer optional 
netcfg_1.187+deb12u1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmZMzRoACgkQOTWH2X2G
UAscLRAAo/M1CE6pPU6mUJwspR5FS1IRVIpQN9Qg2yWS/sYINx8VI0+AxEWVgQ30
9qTsNIl4ZVaSKLMDghkTTF8jN9SOMtnlvNpZn5P7x/oRLeBYhDe5guParHv4ozQz
vs0HeCuYKdVa8v6riBnhvA1JAvwCk6AXomunys+ZoIxNeqLsW3A0GauoAQRRwsWg
JrdupiBucfdQw0hY11ZdX7flHhwGDulZEnagtnlzJhpbix3rfnncbRUKCMi78C8N
6vLQRbMaUKIjnKcwfjwb7x+ffxHWzqr3nIqi4U7ZKLUFJ0uVAQnKX0PTraypHNrj
sMQ+oFsdyjZhEVkgfwgFWC4qsNy0mzPzX+1LjQDgwatxwLcQPoVvTaMweQJpQ5M4
aSquoIY0FGBtxS0WkQ+fJlTuRVlyNy4Bxvik6DyAwTpO0vpX7xSfPfcSE9WSH6Ko
vl2/mAuVOM+bttzYIgX9jICnOcgB9IzmnD943m0nOrGnoWj8J0RQ0qotrF7nY01l
uaTUFMWwqElsfaZIMzuS1xyUKmZkW8fMj4/0pcEQhiikF5q0TALNcYpJ16uSV0MY
ISAwMy6AEQF2so5FTRhHsGE6drBj17OwdZF+/wuXuH85Z0HeKCGWS2r7phZPzWNq
8rCdcHEiv34upT8Yn6hoMBdShMrcdFVoanAPR6bD9n8zck/RY9Y=
=EKTY
-END PGP SIGNATURE-



pgpQ8fpvKTUO0.pgp
Description: PGP signature


Processing of user-setup_1.98_source.changes

2024-05-28 Thread Debian FTP Masters
user-setup_1.98_source.changes uploaded successfully to localhost
along with the files:
  user-setup_1.98.dsc
  user-setup_1.98.tar.xz
  user-setup_1.98_amd64.buildinfo

Greetings,

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



Processing of partman-target_129_source.changes

2024-05-28 Thread Debian FTP Masters
partman-target_129_source.changes uploaded successfully to localhost
along with the files:
  partman-target_129.dsc
  partman-target_129.tar.xz
  partman-target_129_amd64.buildinfo

Greetings,

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



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

2024-05-28 Thread Jmkr
Pascal Hambourg wrote:
>
> You can run grub-install with --no-nvram to install GRUB without writing
> EFI boot variables. The Debian installer also has an option for this in 
> expert mode. Then you can create a custom boot entry with efibootmgr.

Thanks, this is very nice => I am definitely going to test adding the following 
to my pressed:
d-i grub2/update_nvram boolean false

It could help me simplify my "preseed/late_command" script that currently 
deletes the default EFI entry and then creates my custom one. I guess my NVRAM 
will also be very grateful to you:).

Jmkr



Processing of rescue_1.95_source.changes

2024-05-28 Thread Debian FTP Masters
rescue_1.95_source.changes uploaded successfully to localhost
along with the files:
  rescue_1.95.dsc
  rescue_1.95.tar.xz
  rescue_1.95_amd64.buildinfo

Greetings,

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



user-setup_1.98_source.changes ACCEPTED into unstable

2024-05-28 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 May 2024 20:41:58 +0200
Source: user-setup
Architecture: source
Version: 1.98
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 user-setup (1.98) unstable; urgency=medium
 .
   * Team upload
 .
   * Change entry for 1.97: add forgotten bug closure.
 .
   [ Updated translations ]
   * Hebrew (he.po) by Yaron Shahrabani
   * Japanese (ja.po) by Norimitsu SUGIMOTO
   * Punjabi (Gurmukhi) (pa.po) by Aman Alam
   * Ukrainian (uk.po) by Hotripak
   * Traditional Chinese (zh_TW.po) by yubike
Checksums-Sha1:
 1866e8bc66c5308aaf1f70fa55bba778d04c8178 1759 user-setup_1.98.dsc
 811c1d142fe86245f8e8bc0d622a9705dc6051e1 121428 user-setup_1.98.tar.xz
 5f935c4baa6fd498a8f320d5e08eb7ab5ed92be0 6218 user-setup_1.98_amd64.buildinfo
Checksums-Sha256:
 78a5ab74941d4f53ae8977b4427fc666fb6026b64944ad70f70e49f0aaf75a1c 1759 
user-setup_1.98.dsc
 8a1d07ace6ad4ccb0d6969af88e4ffb754560955579bcf06a61078309654905b 121428 
user-setup_1.98.tar.xz
 71febb63e8edf2360009e2cc3b811fa51fb45a7c587408f078cf070ddb32c379 6218 
user-setup_1.98_amd64.buildinfo
Files:
 808485b0fad4df258af6d26285322acb 1759 debian-installer optional 
user-setup_1.98.dsc
 7790cf24811821f143fa3bd5c91467c1 121428 debian-installer optional 
user-setup_1.98.tar.xz
 550fdf741c8ae5df7c4b60a925aec0f9 6218 debian-installer optional 
user-setup_1.98_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZWJnsVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2TyUP/ikw3kWmT459QLBQu3d+l/NpSrwJ
QYJmEOwWvV4xdxYMEBMDwCDulx6W1J14rzCdKtogY/MHU5jmxGQzL1oxAqN+KcLQ
3P4yX83zYqkmejFK2NIX0K1clwzqLYzGNP8P3hFRSrMEFGGh0mfcjhNUtsD1HR0d
mt/TS7ggOxmv/BNIjCYcGAJcIv84+aFWbBsQrnCiTM6OECT6mYv4SsZPsnzZKUHH
BeBEJyOmVjw70JuqG180tnhwJXgmdKSI7dSfHe19Z29NVT6pWGRa3OHofnB3XHXR
qPK63V9RhSyk7fCFOhAJljoDZ9J2MKLketqhuMZMnuZN9LKMZAM1lfTasvRcsWCn
feAChyvbOCegDTcvg+QfJfcJlmnF4DRLVu+JFRanprn+H/CatVTzpFF4vZnpR9ja
WPZ6KdPdK60JAiM5CMazH0qp97ZUwi3XXVLKQNrzw19hpxDKnEex6prCpB8NRJoQ
awRq5ecYMM3fxK0K3CdlguhJdw4YcdAEjobzL/fqqMLUSZE+WCvFBmt21W7tlEYU
q7Bby2W6dfXUsOl5je9agXUnv4T7+4HLF/CoMl6PsgURCS54YudYNksr0VwGajjo
7PMLE5p1cfWeEY6r6+d3dvnRNUcKMyykiQ4/UhROHAG68QOvN3M3v524+AzUHXfn
BEBm82x6Ur+U7pjK
=5FpT
-END PGP SIGNATURE-



pgpngSg6cLTb6.pgp
Description: PGP signature


rescue_1.95_source.changes ACCEPTED into unstable

2024-05-28 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 May 2024 20:36:52 +0200
Source: rescue
Architecture: source
Version: 1.95
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 rescue (1.95) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Updated translations ]
   * Occitan (oc.po) by Quentin PAGÈS
Checksums-Sha1:
 1454d530cb85f88e1bb87931ba857a8129c7af84 1678 rescue_1.95.dsc
 826b6be515d5c4c331e5303b0884a3a7cc3caa40 145188 rescue_1.95.tar.xz
 43c2a8d0a599c02d9fcd6283b8f06590bdcd5ed8 6204 rescue_1.95_amd64.buildinfo
Checksums-Sha256:
 8f37ddfb6e9dbb7ea2fd90ce388b4af6b5ff964920cd6a32142e0bf353fb1d56 1678 
rescue_1.95.dsc
 beb7ed1c7b4edf7be8f216cd994e6ebeaa2233e62b9c8b0fde3307f238036d74 145188 
rescue_1.95.tar.xz
 0b7cf2a95d4bae9069fc43b27056aeb0ace5dd6218895a5c6274c04795c62b7e 6204 
rescue_1.95_amd64.buildinfo
Files:
 f45b6fb5f75b9813acc0df2815cc2896 1678 debian-installer optional rescue_1.95.dsc
 9345005b8239c525beb50cd3b82a5677 145188 debian-installer optional 
rescue_1.95.tar.xz
 46a84dbce16eda2cff7cf8ce94345704 6204 debian-installer optional 
rescue_1.95_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZWJb0VHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB20+sP/3Of4/YH4jE3hExplLS0ZNMCZrye
wTSrGOvnZ8J9KUQKpDM1j/D19eBHbZMXsK4rdCJHA9uF6yJVU4MaXQatq7woFUCD
m5gLTlKRHKmoTog5YKh8V/Sy8sjzVATmcy8GXi4wl895pboRCVRVnTaIjMgM85bj
bYK8ISsA0Tj1qq1uhIX+cDVM0tzNRT4VmfqReD4I+pLP9dhcOBoLR+HnxnDNqSOQ
SeL9JxV1uEf8UynKuC5+RtuhsAMnKO83lG+ZcqjfONAaxa5YcfsNd5qqnihNhiJd
8v2yj2Qlf6l6wofP6j13FOfpmuQUoxISOVBNLJ5yEBese5m31tcjGaRR8Q13zwRb
ZEYAC1x0H4wjAJMDrjKp3H6ntFmbq2wCAx36GswYNufQ2V0jdOHmGCnMrsi9lWgv
7k71t3ptv/Zx1umzGWdkCexQmrsqdC3o6/mCnN/Ls5nmj4cOsR/LvyMDeiJXa09+
YoDiwWVuvTO5CvvBTB++UgkU+bK3s0Kq/5f2tzu60Qrj1XLIY2Rf8E45ViA9//kG
TbySrIngDiqygUMCgQ+CA9fYUiO66EqLBc+fX4FOW1QVKVu1C6sX6YggAyfgX9DV
87MGWA8RYN8qKSKBcbJJ/YLoiENgCeGS6G94VdngcLCvVgoxjTPB9SyJ9HW0cr4g
3iC8aNy+xFy+4Eeo
=D3LK
-END PGP SIGNATURE-



pgpN5J9g9UCYx.pgp
Description: PGP signature


partman-target_129_source.changes ACCEPTED into unstable

2024-05-28 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 May 2024 20:33:55 +0200
Source: partman-target
Architecture: source
Version: 129
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 partman-target (129) unstable; urgency=medium
 .
   * Team upload
 .
   [ Updated translations ]
   * Marathi (mr.po) by omwani
   * Punjabi (Gurmukhi) (pa.po) by Aman Alam
Checksums-Sha1:
 c8f88190431e4dafb74887db50b9f99028f455e9 1739 partman-target_129.dsc
 0126c868867762a056c677b48421c73794336e76 130896 partman-target_129.tar.xz
 84f2956450eedf913a5049a6da2892b98b28e2fb 6002 
partman-target_129_amd64.buildinfo
Checksums-Sha256:
 d93526ae87c4ba73de64d2b93de87b5af58922f1e108c8811bf002c91aa7bf18 1739 
partman-target_129.dsc
 cc9a5960ae5276a9306b9fd80db83c0d899d2ebb6c0eddeeb835115710e3f2b2 130896 
partman-target_129.tar.xz
 70b70ab645e5e80b830e1953e34fd4b7df6eb092479d32ba63aef1a2c4e2b4f9 6002 
partman-target_129_amd64.buildinfo
Files:
 64979da444d69d716f58cfc3a74fb57d 1739 debian-installer standard 
partman-target_129.dsc
 0a3a58f52587928945a33f45f165e87c 130896 debian-installer standard 
partman-target_129.tar.xz
 c7f5c7baa541cefb70d47262d1ffbad5 6002 debian-installer standard 
partman-target_129_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZWJQoVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2Oa8QAIWrW8ySq2obmqN9m9V+ZnMUl8to
MtBxDOVjUJAeXP/DBZUEA4upNVBBCCXFlyKGfkQbZ03jBw9HGWBieTRisRyt76VI
NcSkhDjNjLElzTXXzQ5SlISeIP9P9OLH777utJb5wSlhMOW51IdCwjprM6cZL4E7
LpbS2TthXDj1I8kfqsGZuBQKqOP6jedjl+HtMNpB2iomNa0C2ivPwFmomwoUm6hs
L0Idx7ryovu7AZeKUiQU7VDghRIrVp224Xyo/fDZHGZV0fLiGddVV5AWe62JgRJk
cBDdS2AUdz1mhthf3poA2dfRgeYq8CYtpgKQEbm9lqfgYH/zT7IRxvyTjyrDZCCN
5xcgj6jQCtAtF06javTzGyQVu/6WeRS9K3AkRV+gMZLf47V5uUN/U1QQVk3u4UJB
OMgOR3BH966VuPjdp+R4xd2ODOrlQmbEwRkYIeT48ndCcNE8MdIuKeN4KOzgTnXU
4v5RfRQgffjrMI0MFUrkfslM8cJ/GPbCzpbcfBUyay9Iljnso+w1gWx5dW520wBe
bdA5MXLUbShoOkp90JnfYT/+DEmbYqOkdzZnHZBbjdfTnRWuXUpcZqcpuRGMUGok
dihWzs40wkATKFAd1kqLJNZQpR+EcWZic2G2nx1Xu4jJuLlvqD7lqkaxZRcWk6aF
ryPP/l9KqFOATItc
=SISf
-END PGP SIGNATURE-



pgplUP7_TvmUF.pgp
Description: PGP signature


Processing of partman-partitioning_152_source.changes

2024-05-28 Thread Debian FTP Masters
partman-partitioning_152_source.changes uploaded successfully to localhost
along with the files:
  partman-partitioning_152.dsc
  partman-partitioning_152.tar.xz
  partman-partitioning_152_amd64.buildinfo

Greetings,

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



Processing of partman-nbd_0.74_source.changes

2024-05-28 Thread Debian FTP Masters
partman-nbd_0.74_source.changes uploaded successfully to localhost
along with the files:
  partman-nbd_0.74.dsc
  partman-nbd_0.74.tar.xz
  partman-nbd_0.74_amd64.buildinfo

Greetings,

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



Processing of partman-md_108_source.changes

2024-05-28 Thread Debian FTP Masters
partman-md_108_source.changes uploaded successfully to localhost
along with the files:
  partman-md_108.dsc
  partman-md_108.tar.xz
  partman-md_108_amd64.buildinfo

Greetings,

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



Processing of partman-lvm_150_source.changes

2024-05-28 Thread Debian FTP Masters
partman-lvm_150_source.changes uploaded successfully to localhost
along with the files:
  partman-lvm_150.dsc
  partman-lvm_150.tar.xz
  partman-lvm_150_amd64.buildinfo

Greetings,

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



Processing of partman-iscsi_78_source.changes

2024-05-28 Thread Debian FTP Masters
partman-iscsi_78_source.changes uploaded successfully to localhost
along with the files:
  partman-iscsi_78.dsc
  partman-iscsi_78.tar.xz
  partman-iscsi_78_amd64.buildinfo

Greetings,

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



partman-partitioning_152_source.changes ACCEPTED into unstable

2024-05-28 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 May 2024 20:29:46 +0200
Source: partman-partitioning
Architecture: source
Version: 152
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 partman-partitioning (152) unstable; urgency=medium
 .
   * Team upload
 .
   [ Updated translations ]
   * Arabic (ar.po) by Der Marschall
   * Estonian (et.po) by Kristjan Räts
   * Hindi (hi.po) by Scrambled777
   * Indonesian (id.po) by Andika Triwidada
   * Dutch (nl.po) by Frans Spiesschaert
   * Norwegian Nynorsk (nn.po) by Ola Haugen Havrevoll
   * Turkish (tr.po) by Fatih Altun
   * Ukrainian (uk.po) by Сергій
   * Traditional Chinese (zh_TW.po) by yubike
Checksums-Sha1:
 7a31915c79602309dc65af06333a846d99c1879b 1719 partman-partitioning_152.dsc
 24ab53e6061d53023b7edb6bd1cc9c712117e372 184892 partman-partitioning_152.tar.xz
 8a7f5dd27c9c83e788855e7b9e41fde10aebed9d 6073 
partman-partitioning_152_amd64.buildinfo
Checksums-Sha256:
 f9d6da1d600223dd64b34e4ad31010b468ad5e094801f5c89887384b2a20d11c 1719 
partman-partitioning_152.dsc
 a71bb1556fb89079a7b1b7fae6478d1935b9a14d3afbe1296b64295e29e6fd86 184892 
partman-partitioning_152.tar.xz
 0efcd4f899a711435a330fc82ca246a54e488e39dcb1ec899d67a6d8a043f296 6073 
partman-partitioning_152_amd64.buildinfo
Files:
 7be55c396da8a21aaa64c5d322bc1861 1719 debian-installer optional 
partman-partitioning_152.dsc
 bac6a2530260fe0df7939bda9e1141d3 184892 debian-installer optional 
partman-partitioning_152.tar.xz
 212b8b95379d59c5cc2ef22315c6cf3c 6073 debian-installer optional 
partman-partitioning_152_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZWI2QVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2TRUQAMdLfXM8FvB2pInPqXyRrKGN6jJN
lb/tgCQVFblEmX5fKEM5p3kKplUdO93cnHZrAcCfHUkUJ+z32L3RnleJyX4cs0by
WTkXeWxYH9tPHtHrTOUVo41oHC6AvhLfsy/Jf12ZY1WepqPLZyWZkNL0Q0QjX4yU
7vvrNYTmoD9N3YqAT3iOvX38ksGhTHK2bJj2hqix4u9WkBcvPZB05MdW5b59cOFo
COaJL0qfUtevGwwdoDJVgOAVhVVhn0RDEtzIZXHR0SJi6e8dMUxM22Ac5WqChX/n
YTG6ZbAY8cIJaZxX1/dras+Q5nE7yvOIx0GFunPYMZvoiYWuGPOxBBWmWkFrhVCG
Y6Bv7SgZGidb1d6/eOr2z1UWh+g4j4YiLh0GsketyaOF7rg5gAxh5yC2Tk8tkszS
9K3dBoKDPWlS08LNySMazppXMulXlRvYXx57HIebQ2wHSkB3akdy4YyTARRgCxN3
DWwxa9Xi1BJFJrxnyNm2davvVLH5bAw8x4AFH0/5+g8IlR6gLZI9fBM7ga8zfkqe
6ZTBuUWXtX1kqpK189QsRR3HwhCyNtPYNzgEp9mFV0WFdztRG/VFzuLs5sUQ84ib
e99rhsxxkaiRFKVuxFV/hdS/GD7iLggb+Lyfx2gEHoO8I8YI52cFDFi6jvZH7mQD
3SYxgViIHqIvGE9s
=7+oy
-END PGP SIGNATURE-



pgpPAXeQ9NjcU.pgp
Description: PGP signature


partman-nbd_0.74_source.changes ACCEPTED into unstable

2024-05-28 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 May 2024 20:27:17 +0200
Source: partman-nbd
Architecture: source
Version: 0.74
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 partman-nbd (0.74) unstable; urgency=medium
 .
   * Team upload
 .
   [ Updated translations ]
   * Welsh (cy.po) by Rhodri
   * Hindi (hi.po) by Scrambled777
   * Georgian (ka.po) by Temuri Doghonadze
   * Macedonian (mk.po) by Kristijan Fremen Velkovski
   * Punjabi (Gurmukhi) (pa.po) by Aman Alam
Checksums-Sha1:
 28dd4b4d94aa30d63876d95edce3b89da3dc88ca 1650 partman-nbd_0.74.dsc
 f055e0dbbc439842a1cdaf54572cd59e996a8ece 73012 partman-nbd_0.74.tar.xz
 8811aa45a715770bcf77df728168214d786288be 5980 partman-nbd_0.74_amd64.buildinfo
Checksums-Sha256:
 a32417ae5e660bcec53753ccfe9087209f5033a10e26ca6f60886b06d1b4281d 1650 
partman-nbd_0.74.dsc
 75442fe35f99fad0c9cd7e47fea41b0e10fc86c13ccd3f9364c65f3b2db4c58a 73012 
partman-nbd_0.74.tar.xz
 9edf6224e5d58c0a05fa00a14e8d7ab59b90fdf8b169267ce045b1309186db42 5980 
partman-nbd_0.74_amd64.buildinfo
Files:
 f148e02e4e7c3eab97257d8dc8e44dbd 1650 debian-installer optional 
partman-nbd_0.74.dsc
 72647304623528e742e4d230bdf89a4a 73012 debian-installer optional 
partman-nbd_0.74.tar.xz
 8a82454005f3912f57bac3a34f5c793b 5980 debian-installer optional 
partman-nbd_0.74_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZWIsIVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2UzoP/27ST8LtM6wRvuqN8tOJprh+vkQj
gs/Htvbzn/QbIkoHP3eDg5ndGeh6BhYGjHkI6SAU/kN23iPvds7/byjNY9Dn+e3L
PM2BIBPQfQYM/UL/A+eE36ZTPgiel6Tn7P6sDfrtNR0IvqEVy5dyrIGIXM0Xt5L1
5+gOmJa30Ez62wIYQt33X4dlUaYS2PZ0e4inK8aqW3uEU5rjHpZNW+36jnhHWhNy
k/LR+CMQQAweYuXX3qb7K7ZdHwWShWOnMEVD/7J6uDNxKQEZHT4bX/DwNEaagEdU
mpV6r0Z9chwyeL8PLc1fKQV4maBEv6/JACImtx/QnFsSajQwzRln7wC3HC6So40W
/P7qqiCsW4UE7oVtPqjkx/UKWJJXcQ93MlnXMLCsVCIKyX9+GBjMVE5/9MP6ki74
pwmXsqsfs1Pm8HlsYU2XuavwntXCV43bkB1LNZ9y3hvn7B429/OAyWU1plUXIvKk
4FLJmb16FB26OogkhG1jPTfCC9ZVBK4nxB3tw5ldwge7DoGHcHzdL96qFGPJ5B9a
60k9M6d+cNrJMeJXTrBmKfAGLteKYXC7YcXSlpC0/BMgCCflel6RFM6EFpHpQF8T
76SKh34tWdkRz+YDRD8Z3B3nmGgkj2Ohcj/q1flm+2bxkcNfgPu4TPF+kjEFh+2C
WztKD8lNwDXMKhC2
=Ypau
-END PGP SIGNATURE-



pgpaHbjilF9L6.pgp
Description: PGP signature


partman-md_108_source.changes ACCEPTED into unstable

2024-05-28 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 May 2024 20:24:13 +0200
Source: partman-md
Architecture: source
Version: 108
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 partman-md (108) unstable; urgency=medium
 .
   * Team upload
 .
   [ Updated translations ]
   * Hungarian (hu.po) by SZERVÁC Attila
   * Georgian (ka.po) by Temuri Doghonadze
   * Marathi (mr.po) by omwani
   * Occitan (oc.po) by Quentin PAGÈS
   * Punjabi (Gurmukhi) (pa.po) by Aman Alam
Checksums-Sha1:
 2201c81e654a9b0dd4bb466d637835ad0a12bab1 1669 partman-md_108.dsc
 9e8e11ddd276f15c205b6407b84c9beda21bf365 189144 partman-md_108.tar.xz
 ecdc43e2aed3140329dd3e030ad2bf817c3b16d8 5965 partman-md_108_amd64.buildinfo
Checksums-Sha256:
 ce20fceffef023d0f6e408f7d8ee8d1471264bf32911a14c2e3e8c1edc0a1d4f 1669 
partman-md_108.dsc
 af785e00058d43ef9265cd8d451fc486a296586b354b077f4296bd779bf0b9a8 189144 
partman-md_108.tar.xz
 f3cc3c980da3f628bec255671ff687300b74d54544d3b2b3e871a63577d820e0 5965 
partman-md_108_amd64.buildinfo
Files:
 4a07b594df03b342713fc1976b441589 1669 debian-installer standard 
partman-md_108.dsc
 f44cc95ee84f28e03e37068484f9aad2 189144 debian-installer standard 
partman-md_108.tar.xz
 4667709b2b55385122a799c273f3cbcd 5965 debian-installer standard 
partman-md_108_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZWIcUVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2KZUQAI5tSujBUP9RwJZsVtilZ0aRqU9g
ra5M+yX/JKdF30RVPIKQ96WNN7v4V8EBBGzXs+Eq8u2yzh1z/u5RFy7s7T/mgGMq
IED0fXejSkfHwepXIdf7XRiublcIDqRNrBhfkLAyIdSP995vUmHhrYEGK5YGsN+2
o0+fTy8aSLN1F6vAPL/T4pabS9y7gZiv69ACknc8nIPjwkNbkqMDRZ7cqvl/xNc7
X9x+ubcMUmNisAaQ0LyDtFbvQxIJ8XTwUjMYuie1+lwPpApIO6vbgOSDLMeXquE+
5+5P1sW42OAO0Dsl1KBycE0Y0z06yUhC9JHJqYfiBgY9QCEp5e68ITE1mgL0480I
IOGA1XjYxmM4WWE7ZSD7qjaCt9vp13LI9iIX5H6m9SPyGacUfLqgS1CUuQDLUtPt
9ls5YU0XMJ8EhQ9FzLe5hIgTbweGY9VO985dUvrPbu9MpqQHv+ahEZp+fVnc+43T
+8gdGHV60Qc+iQmy+WMQGpxyPmdPQm4YbZ8zjdNtH+APC2B5cmi789qOQu3K8hFA
EpFeNifNIuzRzWmSPaj1aFsCIzflPmKjp1EhGAew8P4mCWfxbS8hJyNFF3tws/Z1
OWEnJNFjx785itStlrxnIfsDMz8zQsk8TwJ2gG1OPJ8ye7cmgTSpFZCI8PXs5NBI
cF7e5YBAM4s6/o0l
=C9sZ
-END PGP SIGNATURE-



pgpgYZJbogXYQ.pgp
Description: PGP signature


partman-lvm_150_source.changes ACCEPTED into unstable

2024-05-28 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 May 2024 20:20:43 +0200
Source: partman-lvm
Architecture: source
Version: 150
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 partman-lvm (150) unstable; urgency=medium
 .
   * Team upload
 .
   [ Updated translations ]
   * Arabic (ar.po) by Der Marschall
   * Hindi (hi.po) by Scrambled777
   * Hungarian (hu.po) by SZERVÁC Attila
   * Norwegian Nynorsk (nn.po) by Ola Haugen Havrevoll
   * Occitan (oc.po) by Quentin PAGÈS
   * Traditional Chinese (zh_TW.po) by yubike
Checksums-Sha1:
 d19be7d81e7fc8a8aa17ecdad2da34576aaaea52 1688 partman-lvm_150.dsc
 62b177a011ab72f9f31ecde7b0c7f3cd6027c98e 260324 partman-lvm_150.tar.xz
 fa2ca7c13f0dd42fa8b7efed584b3453da93c42b 5975 partman-lvm_150_amd64.buildinfo
Checksums-Sha256:
 535e0bf0938d9aa2e5cf389d4191fff55f352bd5f95fdd5dcdcd5a58be325261 1688 
partman-lvm_150.dsc
 15ea830a5ee02867c9c116019f096760fb12c23abf737e528727ddab064b7202 260324 
partman-lvm_150.tar.xz
 d4cf64be714f107c3ce002a310f1561bc26d59bffe8e68ce0d4305a21a39f17f 5975 
partman-lvm_150_amd64.buildinfo
Files:
 0ec4394d54cd70d6d5e4479cbcfbf821 1688 debian-installer optional 
partman-lvm_150.dsc
 54174cc7f14535934fdfbff78b223b2b 260324 debian-installer optional 
partman-lvm_150.tar.xz
 f3f7ee6fb7a5e3105ec44b05e2e46991 5975 debian-installer optional 
partman-lvm_150_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZWISgVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2Wg4P/2uhw3ClB+SNsTPMoaHnMYvgefYB
OuTHUjuy7spvhpKoLpmNj07LRl1f4UizE95NC+6joET7DynR2xhJnrf+pSviF3iA
g+XVgD1zgRejL10mKhbOGqndzlYtypPRUVc4gCl/y+0RrCOEt+ylX0Z3ZrSdpVWz
8ShOJsl+D+swf6YQqcaGRRk/SixUjSlWhPoROzpQJmWrtaFXAn/c2ucj10CdVBnV
bV0i7Iy5LkBqUADlf3Mob/RtCy6gPXUrqbh2Njd02oUQIQBpHiSgNu7ExJxl76P4
lwRcsW/8W5ya5+p/OWXA82IfKarOeHdtw/NOhD55Bwo6jlAksjXVtHzLNW/8qJix
01tBBFTvnqlMAsw4XB1a36mraS8Zp6AO7m1qJpoNQXpCG3//e+xDb6zlgJGMTK+0
xO4koUgRKgU6FM132xE8i2srfwA5qAgnTQlT78oX1p8o6tO7IBC8OuXvw5YxS6l8
rUlZfxahQ1j5r/kwDHS4vyjcPUkf+ZZThWKIu+SZBcWwvZihLeIKrRi2+mRjP61c
Z/MnNf4g9sBXbfoEbhSG/PCbrQ9PooMNmBo5zJFgVJLBhJeKbPJ71kfFRhLherCH
HVw0acQ53J+lz0mGDEHb8opleFM/Yy5smpoK+sEp+SC1QcTBmzOcoj6DVIfSFReA
TfSAKwYra9pUmQ16
=rkg8
-END PGP SIGNATURE-



pgp9XbXjBkyA4.pgp
Description: PGP signature


partman-iscsi_78_source.changes ACCEPTED into unstable

2024-05-28 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 May 2024 20:18:26 +0200
Source: partman-iscsi
Architecture: source
Version: 78
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Changes:
 partman-iscsi (78) unstable; urgency=medium
 .
   * Team upload
 .
   [ Updated translations ]
   * Hebrew (he.po) by Yaron Shahrabani
Checksums-Sha1:
 b1e0c49b38649812246a096e580f6ee55b489d04 1657 partman-iscsi_78.dsc
 355cf22bfef1be0b4b97dd40800c2c3371199dcc 79552 partman-iscsi_78.tar.xz
 684ec1768980b9739bd65ebbe5050d5c907081cd 5984 partman-iscsi_78_amd64.buildinfo
Checksums-Sha256:
 f31dcbecaedf9fc200ffd2e4056f15e934b7c382a960c889831598a454b7a61d 1657 
partman-iscsi_78.dsc
 e15632df32e828a3d1aaa62ca5547f3eff4487f3bbede12af86569bafa1c0c7d 79552 
partman-iscsi_78.tar.xz
 4ddb2bf29de2051e90578617e3a635d0b7d260c1e19d7d280dea32ca13720e5b 5984 
partman-iscsi_78_amd64.buildinfo
Files:
 ab9efe7b6f47158def82a6f870d6796b 1657 debian-installer standard 
partman-iscsi_78.dsc
 888f82e052cb798357457dabc02caf5c 79552 debian-installer standard 
partman-iscsi_78.tar.xz
 fd398e58f470a358f8a4da05cf34fe5e 5984 debian-installer standard 
partman-iscsi_78_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAmZWIKMVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2P5wP/2GMJSqdpH3+ii0ESSA/mGL/IG5a
pYOBzc7R8zASel//2tskfeP9AWRaOAWBAN2cqOAkKKy+zYQFJXPFDZgyTdXuAlUU
fv/7nsd7efEFnmt4RSMewlM486f8Sy+yDjMo9WshSQZ6MLuYEXU90fLu59cVjjAv
OhJOYY8/3blg5PimwoqVVmZ/scjPXrCBCzA7hjhb1t91+Grwil3gp0K5TDJpQT8p
jTzTdG+xq9mtovFtfE0cig++656DX6v9EQnW6MATsqCdVVPPB0kvl3m1JxUAhQc9
N9uygizVJauyLlAgiCWEe/hMdc1D9UQRgYEtaNnBVTQhUxWKUpgm/j6zfekGGeRx
QvbGz6aCr+4qhEAWD55s+zdWZ+qSmR3wuNM+nn3QjTgO8yg/cZQ5qKCteBLBC8zI
CHx0CFBulmy7k6FlnVQEwRJ0p+f/XYEPF5apzVGinUPl37V5JP8DXuOcYZfwYA/x
uFwx8sAdOlTZpVApmFKc/lgVZB3M6fr+I20r6hp/LdQSF3g8kuPXiph5cxg42otS
f5evfebSyKEOIqdjFsd+jo6VsolZbkWewOtkodWXPZRaYDKfhROS1lz+zxmPIcpz
aBNkCxVMHYSD9ONnWGOtdgju9IoZAQUf0G25RBSuJ8Ezkps1qIcUIjgn22CGHKkN
Dr4Ca35e1eMGmE4/
=I4Uo
-END PGP SIGNATURE-



pgpfOIUJGXcZA.pgp
Description: PGP signature


Processing of partman-hfs_12_source.changes

2024-05-28 Thread Debian FTP Masters
partman-hfs_12_source.changes uploaded successfully to localhost
along with the files:
  partman-hfs_12.dsc
  partman-hfs_12.tar.xz
  partman-hfs_12_amd64.buildinfo

Greetings,

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



  1   2   3   4   5   6   7   8   9   10   >