Re: Bug#1003484: bullseye-pu: package openssl/1.1.1m-0+deb11u1

[Kurt Roeckx]

On Fri, Mar 18, 2022 at 10:22:57PM +0100, Sebastian Andrzej Siewior wrote:
> On 2022-03-18 14:51:32 [+], Adam D. Barratt wrote:
> > Boo. Hope you're doing better.
> 
> Thanks, yes.
> 
> > > I would also do the upload for Buster, would that work? I remember
> > > that
> > > the packages, that broken, were already uploaded a few cycles ago.
> > 
> > Also as 1.1.1n?
> 
> Yes.
> 
> > I assume there haven't been any regressions reported with l/m/n in the
> > meantime.

I'm not aware of any regressions the past year.


Kurt

Re: Bug#1003484: bullseye-pu: package openssl/1.1.1m-0+deb11u1

[Sebastian Andrzej Siewior]

On 2022-03-18 14:51:32 [+], Adam D. Barratt wrote:
> Boo. Hope you're doing better.

Thanks, yes.

> > I would also do the upload for Buster, would that work? I remember
> > that
> > the packages, that broken, were already uploaded a few cycles ago.
> 
> Also as 1.1.1n?

Yes.

> I assume there haven't been any regressions reported with l/m/n in the
> meantime.

Not that I am aware of. I'm adding Kurt explicit in To: in case has some
secret knowledge.
Just uploaded the Bullseye version.

> Regards,
> 
> Adm

Sebastian

Re: Bug#1004452: bullseye-pu: package gnupg2/2.2.27-2+deb11u1

[Daniel Kahn Gillmor]

On Fri 2022-03-18 09:13:08 +, Adam D. Barratt wrote:
> Unfortunately it looks like the upload failed:
>
> gnupg2_2.2.27-2+deb11u1.dsc: Refers to non-existing file
> 'gnupg2_2.2.27.orig.tar.bz2.asc'

Sigh.  thanks for the note.  I've just tried again, this time including
the orig.tar.bz2.asc in the upload.

--dkg


signature.asc
Description: PGP signature

Processed: Re: Bug#1007707: Update Indonesian translation

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1007707 [win32-loader] Update Indonesian translation
Added tag(s) pending.

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

Processed: Re: Bug#1007701: tasksel: [INTL:id] [l10n] [patch] update Indonesian translation

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1007701 [tasksel] tasksel: [INTL:id] [l10n] [patch] update Indonesian 
translation
Added tag(s) pending.

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

Bug#1007929: netcfg: FTBFS on s390x

[Paul Gevers]

Source: netcfg
Version: 1.177
Severity: serious
Tags: ftbfs

Dear maintainer,

Your package failed to migrate for 60 days, hence I spotted it. It
fails to build from source on s390x. I hit the giveback button once
because looking at the failing test result I suspected it is "just" a
flaky test. However, that didn't work. The same issue happened on
powerpc, ppc64 and sparc64 but those are not release architectures.

Paul

https://buildd.debian.org/status/fetch.php?pkg=netcfg&arch=s390x&ver=1.177&stamp=1642282014&raw=0


Running suite(s): inet_mton
 inet_ptom
 netcfg_parse_cidr_address
 netcfg_network_address
 netcfg_gateway_reachable
 nc_v6_interface_configured
95%: Checks: 24, Failures: 1, Errors: 0
test/test_netcfg_gateway_reachable.c:94:F:netcfg_gateway_reachable:test_netcfg_gateway_reachable_v6_fe80:0:
 Gateway erroneously unreachable
make[1]: *** [test/tests.mk:19: test] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: error: make -j1 test returned exit code 2
make: *** [debian/rules:6: build-arch] Error 25

Bug#1007928: Please ignore the email disclaimer

[Steve Capper]

Hello,
A quick one to say apologies for the "IMPORTANT NOTICE" email disclaimer 
in my previous email. This can safely be ignored.


I'll be more careful with my email software in future.

Cheers,
--
Steve

Bug#1007928: grub-installer: support for arm64 EBBR systems

[Steve Capper]

Package: grub-installer
Version: 1.182

Hello,
On arm64 EBBR style systems with U-boot + EFI API the persistent
variable store can, unfortunately, be read-only when boot time services
have finished[1]. Meaning that Linux is unable to set EFI variables.

Would it be possible to please add logic for arm64 + EFI to re-attempt a
failed grub-install with the extra flags added:
--force-extra-removable --no-nvram

For reference, this was discussed briefly on debian-boot[2].

Also, unfortunately, the force-efi-extra-removable logic only employs
the following flag:
--force-extra-removable
So on arm64 EBBR systems the "expert mode" installation option doesn't
work either :-(. Could --no-nvram please be added to this option?

FWIW, for testing this I built a recent u-boot with qemu_64_defconfig
and passed the resultant u-boot.bin to qemu with "-bios u-boot.bin".
Also, I'm more than happy to quickly test grub-installer .udebs

Cheers!
--
Steve Capper

[1] https://arm-software.github.io/ebbr/#id21
[2] https://lists.debian.org/debian-boot/2021/11/msg00079.html
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

Re: Bug#1000355: bullseye-pu: package nano/5.4-2+deb11u1

[Adam D. Barratt]

Control: tags -1 + d-i

The changes are probably beneficial to the use of nano-udeb as well,
but in any case tagging and CCing for inforamation.

On Fri, 2022-03-18 at 18:15 +0100, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Mon, Nov 22, 2021 at 01:29:56AM +0100, Jordi Mallach wrote:
> > Package: release.debian.org
> > Severity: normal
> > Tags: bullseye
> > User: release.debian@packages.debian.org
> > Usertags: pu
> > 
> > [ Reason ]
> > 
> > As we did early during the freeze, nano's upstream Benno
> > Schulenberg has
> > been maintaining a series of patches against nano 5.4, which
> > backport
> > crashes fixes and other big impact fixes for Debian's version of
> > nano.
> > 
> > [ Impact ]
> > 
> > We will miss several crash (and general bugs) fixes in different
> > situations and scenarios.
> > 
> > [ Tests ]
> > 
> > Patches have been tested individually against 5.4, and have had a
> > wider
> > testing in the newer nano versions in which the fixes were
> > introduced.
> > 
> > [ Risks ]
> > 
> > There is a big amount of patches, but most of them are one or
> > two-liners. Of course, the risk of any of them introducing new bugs
> > is
> > real, but given Benno's knowledge of the codebase, it is unlikely.
> > 
> > [ Checklist ]
> >   [X] *all* changes are documented in the d/changelog
> >   - I've only mentioned the addition of a bundle of patches,
> > not
> > each one of them in detail. I can add a list of patches
> > like in
> > the changes section below, if that's preferred.
> >   [X] I reviewed all changes and I approve them
> >   [X] attach debdiff against the package in (old)stable
> >   [X] the issue is verified as fixed in unstable
> > 
> Go ahead, thanks.
> 
> Cheers,
> Julien
> 
> 

Bug#1005693: marked as done (Installation of sid failed because of network configuration failure)

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2022 15:04:23 +
with message-id <6668648351417fa5600c585d7bc69ddb87a1cb86.ca...@posteo.de>
and subject line Installation is now successfully
has caused the Debian Bug report #1005693,
regarding Installation of sid failed because of network configuration failure
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.)


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

Boot method: Network PXE Boot
Image version: PXE Boot with daily:

> https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/initrd.gz
> https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/linux

Date: 2022-02-13

Machine: Asus Zenbook Pro UX501J
Processor: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz
Memory: 16GB
Partitions: -

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
> Processor DRAM Controller [8086:0c04] (rev 06)
>   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
> DRAM Controller [1043:18dd]
>   Kernel modules: ie31200_edac
> 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
> Processor PCI Express x16 Controller [8086:0c01] (rev 06)
>   Kernel driver in use: pcieport
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
> Processor Integrated Graphics Controller [8086:0416] (rev 06)
>   Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
> Graphics Controller [1043:18dd]
>   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 [8086:0c0c] (rev 06)
>   Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD 
> Audio Controller [8086:2010]
>   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 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB xHCI [1043:18dd]
>   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: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> MEI Controller [1043:18dd]
>   Kernel driver in use: mei_me
>   Kernel modules: mei_me
> 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
> Family USB EHCI #2 [8086:8c2d] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB EHCI [1043:18dd]
>   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 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset High 
> Definition Audio Controller [1043:18dd]
>   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 [8086:8c10] (rev d5)
>   Kernel driver in use: pcieport
> 00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
> Family PCI Express Root Port #3 [8086:8c14] (rev d5)
>   Kernel driver in use: pcieport
> 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
> Family PCI Express Root Port #4 [8086:8c16] (rev d5)
>   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 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> USB EHCI [1043:18dd]
>   Kernel driver in use: ehci-pci
>   Kernel modules: ehci_pci
> 00:1f.0 ISA bridge [0601]: Intel Corporation HM87 Express LPC Controller 
> [8086:8c4b] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. HM87 Express LPC Controller [1043:18dd]
>   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:8c03] (rev 05)
>   Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family 
> 6-port SATA Controller 1 [AHCI mode] [1043:18dd]
>   Kerne

Re: Bug#1003484: bullseye-pu: package openssl/1.1.1m-0+deb11u1

[Adam D. Barratt]

On Fri, 2022-03-18 at 14:12 +0100, Sebastian Andrzej Siewior wrote:
> On 2022-03-18 09:21:50 [+], Adam D. Barratt wrote:
> > Apologies if the status here got confused - based on the above, I
> > was
> > assuming that in the absence of a negative response you would
> > proceed
> > with the 1.1.1n-0+deb11u1 plan. For complete clarity, please feel
> > free
> > to do so, bearing in mind that the window for the 11.3 point
> > release
> > closes over this weekend.
> 
> No need to apologies. I did plan to do it on WED but got busy with
> other
> things, got sick on THU and couldn't anything so the plan is indeed
> today.
> 

Boo. Hope you're doing better.

> I would also do the upload for Buster, would that work? I remember
> that
> the packages, that broken, were already uploaded a few cycles ago.

Also as 1.1.1n?

I assume there haven't been any regressions reported with l/m/n in the
meantime.

Regards,

Adm

Re: Bug#1003484: bullseye-pu: package openssl/1.1.1m-0+deb11u1

[Sebastian Andrzej Siewior]

On 2022-03-18 09:21:50 [+], Adam D. Barratt wrote:
> Apologies if the status here got confused - based on the above, I was
> assuming that in the absence of a negative response you would proceed
> with the 1.1.1n-0+deb11u1 plan. For complete clarity, please feel free
> to do so, bearing in mind that the window for the 11.3 point release
> closes over this weekend.

No need to apologies. I did plan to do it on WED but got busy with other
things, got sick on THU and couldn't anything so the plan is indeed
today.

I would also do the upload for Buster, would that work? I remember that
the packages, that broken, were already uploaded a few cycles ago.

Thank you!

> Regards,
> 
> Adam

Sebastian

s390-dasd_0.0.74_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 Mar 2022 13:12:26 +0100
Source: s390-dasd
Architecture: source
Version: 0.0.74
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 1004292
Changes:
 s390-dasd (0.0.74) unstable; urgency=medium
 .
   [ Dipak Zope ]
   * Stop passing deprecated -f option to dasdfmt, which was dropped in
 s390-tools 1.37.1-1 (Closes: #1004292).
Checksums-Sha1:
 561e3893abeb544b78f8f9d44e134017d3e0dbdf 1718 s390-dasd_0.0.74.dsc
 19b9e92565aa3901b1a1f38ddfb82d0a6d45e024 68220 s390-dasd_0.0.74.tar.xz
 4f3fcd6d6f28236430a0ca27dd4b1348cd5ceb35 6349 s390-dasd_0.0.74_source.buildinfo
Checksums-Sha256:
 8a7c31f32a381a2c16c7a0fcf29bde87c8f59231726eb165e50104afac76c7a6 1718 
s390-dasd_0.0.74.dsc
 21826472dcd89303c34a943e20793169000655da0cbf336bf93c804ba2bda789 68220 
s390-dasd_0.0.74.tar.xz
 adb576ac6172c53ee3304c0d8a8f83e13533722d967faadc8e3d6378a9c0c46d 6349 
s390-dasd_0.0.74_source.buildinfo
Files:
 c32d21b652c73a790ab98d2b3d8be9d7 1718 debian-installer standard 
s390-dasd_0.0.74.dsc
 8b6ce9e65897ab0ee4d9b38278446e66 68220 debian-installer standard 
s390-dasd_0.0.74.tar.xz
 7abca1c513ceb62f5eba47da38816ae9 6349 debian-installer standard 
s390-dasd_0.0.74_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmI0d+cQHGtpYmlAZGVi
aWFuLm9yZwAKCRD/kUrwwrNVIOFKD/9NC9n6Ugt1ssGWrc0PXyNIDbXM+YUPHSP4
5cM6HvqV97OmEKcr2lBDE5HpEZJkPkvHdrXVWk0dgHXL8DgmLeXIcvs1u2LpEC3I
90/Mxg0CpANWEVzcTn7uTXaHJauLwinBSra5YCyWoTLe6CEPPT1CCvT2x5Enui4G
N954OYixqlycKwsmHpde63aNKx10KcuKQrLptfR5oxE4b4GuwAp2zMFBX63aG62b
za8Q2c6etylqWDVd9xA5etiQpR55NOI7199jfWQomAUlT+ERrMUyjqssUXngml8G
8dYonaCCjOxQ87x4p8bDtHfCnewqGINUXQB8RocSmOQ7DDsX7gLqtrL51Tl/T80s
J1WNIO7xGqvk+YFAWA8fjn7zB3Iq+osh0OwtwmQm+HsVcEHt+MSLkHcYfIhIQahm
yUVHqyuRljB9B+eIOba04phxvuQGU0kQbum0+AkquivI27JAdaM28gA450UUDNyH
Hw+5yr0BLlS0+rauZmsiZeWJc1LZrMpwRiwqFoFcQAPJreX9doK84SRnoovjczUf
miRztEuL6tLPSGsrqZsr6UnrQeqO49SPc6iShYZqeLqLIuBjRjFP8YxcVGSrWBXs
D/Uw9Hs2hSNT1H+ioGnHlw3gvPswrPZqzt5fYMqX3tnYnKTa5TCeMJCDk94h0Y3w
0aJBEZ0VjQ==
=1lUB
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#1007776: authemtication of wireless network after password input fails

[Peter Müller]

I apologize; so far, unable to. (I found no option to switch to plain 
text from HTML in the Web interface, and my e-mail client so far failed 
to send from that domain for an unknown reason.)


The last message got through, though, from my e-mail client, so the 
sending failure is apparently random.  I could to try to re-send the 
report as plain to the list (debian-boot@lists.debian.org, right?), but, 
as there's go guarantee of success,  it'd be better if I could kindly 
ask you to do this on my behalf.

Bug#1007776: authemtication of wireless network after password input fails

[Peter Müller]

Dear Cyril,

thanks for the quick answer!

On 18.03.22 09:12, Cyril Brulebois wrote:

Hi Peter, and thanks for your report.

A couple of things: please avoid sending HTML messages in general. And
since you included a large picture (by mailing list configuration
standards), your report was not delivered to our list.


I apologize; so far, unable to. (I found no option to switch to plain 
text from HTML in the Web interface, and my e-mail client so far failed 
to send from that domain for an unknown reason.)



Peter Mueller  (2022-03-16):

I tried to install unofficial (due to various drivers, in particular
the Intel WiFi network driver) Debian bullseye. During the
installation, I was asked for the network card, and I chose a wireless
one: wlp179s0, which is in my case WLAN/Bluetooth Adapter PCIe (WL-PCI
ASUS PCE-AX3000 BT5.0) Dual-Band (2,4 GHz/5 GHz), Bluetooth-Version
5.0.


Over the course of the installation process, did you get any messages
regarding missing firmware? I'm not sure this would explain the issue
you're describing, but that's an easy item to check for…


No such messages in the user interface. As for the console, I'll try to 
check.





I was asked for the WLAN ID, which I provided (the SSID of my router).
Then I was asked for the type, which I provided as WPA/WPA2 PSK in my
case (WPA2 for my router). Then I was asked for the WPA-Passphrase,
which I typed in (WPA2 password for my router). Then a progress bar
depicting an authentication attempt with the access point appeared.
For a few minutes the bar continuously made progress  (the messages on
the fourth console are attached) and finally reached 100%.  Then I saw
a failure message asking me to verify the WPA-parameters which I
input.
I repeated the process several times, with the same result: no network
during installation. The wireless card itself and the SSID-password
combination are o.k. because I got connection using Debian live from
the same installation drive. (Moreover, on a similar machine with the
same network card the nerwork happily starts with NetworkManager,
though with ifupdown there is a delay of several minutes at boot; cf.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993826).  Any
bugfix? Any help?


The live test is quite useful, thanks for mentioning it. I'm wondering
whether this could be due to missing crypto modules inside our image,
which I've seen to be the reason for failure to associate from the
installer, while the installed system was fine. Any chance you could
start the live image again, save the output of `lsmod`, and attach it
here, using reply-all?


Will do, though not immediately.  In several days I'm likely to get 
again to the machine on which the installation fails.  As for the very 
similar machine with the same network card (and for which I recall the 
installer had similar problems), there is an lsmod log in the 
aforementioned bug report. If netcfg uses the same logic as ifupdown on 
an installed system, that bug report is probably connected.


Cheers,
Peter

Processing of s390-dasd_0.0.74_source.changes

[Debian FTP Masters]

s390-dasd_0.0.74_source.changes uploaded successfully to localhost
along with the files:
  s390-dasd_0.0.74.dsc
  s390-dasd_0.0.74.tar.xz
  s390-dasd_0.0.74_source.buildinfo

Greetings,

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

Bug#1004292: marked as done (debian-installer:s390x: installer fails to format dasd disc on s390x systems)

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2022 12:36:44 +
with message-id 
and subject line Bug#1004292: fixed in s390-dasd 0.0.74
has caused the Debian Bug report #1004292,
regarding debian-installer:s390x: installer fails to format dasd disc on s390x 
systems
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.)


-- 
1004292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-installer
Version: 20210731+deb11u2
Severity: important
Tags: d-i s390-dasd upstream
X-Debbugs-Cc: dipak.zo...@ibm.com



On s390x machines with dasd disc, the installer fails to format the dasd 
disc. 

Logs: 
Jan 24 12:25:13 main-menu[341]: INFO: Menu item 's390-dasd' selected
Jan 24 12:25:19 s390-dasd[3224]: dasdfmt:
Jan 24 12:25:19 main-menu[341]: WARNING **: Configuring 's390-dasd' failed with 
error code 1
Jan 24 12:25:19 main-menu[341]: WARNING **: Menu item 's390-dasd' failed.


Root cause: 
The s390-dasd package calls dasdfmt with '-f' option which is obselete
 long ago. 

Proposed Fix: 
s390-dasd / dasd-config.c: line 393:
Existing line: snprintf (buf, sizeof (buf), "dasdfmt -l LX%04x -b 4096 -m 1 -f 
%s -y", channel_device (channel_current->name), dev);
Proposed line: snprintf (buf, sizeof (buf), "dasdfmt -l LX%04x -b 4096 -m 1 %s 
-y", channel_device (channel_current->name), dev);


This fix is verified. Logs for reference after changes (with additional
debug statement): 

Jan 23 05:21:16 main-menu[347]: INFO: Menu item 'clock-setup' selected
Jan 23 05:21:16 main-menu[347]: INFO: Menu item 's390-dasd' selected
Jan 23 05:21:16 main-menu[347]: INFO: Falling back to the package description 
for dasd-modules-5.10.0-10-s390x-di
Jan 23 05:21:16 main-menu[347]: INFO: Falling back to the package description 
for dasd-modules-5.10.0-10-s390x-di
Jan 23 05:21:21 kernel: [  302.451325] dasd-eckd 0.0.2c7c: A channel path to 
the device has become operational
Jan 23 05:21:21 kernel: [  302.461801] dasd-eckd 0.0.2c7c: New DASD 3390/0C (CU 
3990/01) with 30051 cylinders, 15 heads, 224 sectors
Jan 23 05:21:21 kernel: [  302.485675] dasd-eckd 0.0.2c7c: DASD with 4 
KB/block, 21636720 KB total size, 48 KB/track, compatible disk layout
Jan 23 05:21:21 kernel: [  302.486712]  dasda:VOL1/  LX2C7C:
Jan 23 05:21:24 s390-dasd[3591]: INFO: DZDEBUG:01 executing: dasdfmt -l LX2c7c 
-b 4096 -m 1 /dev/disk/by-path/ccw-0.0.2c7c -y
Jan 23 05:21:24 s390-dasd[3591]: Printing hashmark every 10 cylinders.
Jan 23 05:23:45 kernel: [  446.669429] dasd-eckd 0.0.2c7c: DASD with 4 
KB/block, 21636720 KB total size, 48 KB/track, compatible disk layout
Jan 23 05:23:45 kernel: [  446.669445] dasda: detected capacity change from 0 
to 22156001280
Jan 23 05:23:45 kernel: [  446.669876]  dasda:
Jan 23 05:23:45 kernel: [  446.673221]  dasda:VOL1/  LX2C7C:
Jan 23 05:23:45 s390-dasd[3591]:
Jan 23 05:23:45 s390-dasd[3591]: Finished formatting the device.
Jan 23 05:23:45 s390-dasd[3591]: Rereading the partition table... ok
Jan 23 05:23:45 kernel: [  446.675799]  dasda:VOL1/  LX2C7C:
Jan 23 05:24:21 main-menu[347]: INFO: Menu item 's390-zfcp' selected



-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: s390x
--- End Message ---
--- Begin Message ---
Source: s390-dasd
Source-Version: 0.0.74
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
s390-dasd, 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 1004...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated s390-dasd 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: Fri, 18 Mar 2022 13:12:26 +0100
Source: s390-dasd
Architecture: source
Version: 0.0.74
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 1004292
Changes:
 s390-dasd (0.0.74) unstable; urgency=medium
 .
   [ Dipak Zope ]
   * Stop passing deprecated -f option to dasdfmt, which was dropped in
 s390-tools 1.37.1-1 (Closes: #1004292).
Checksums-Sha1:
 561e3893abeb544b78f8f9d44e134017d3e0dbd

Processed: Bug#1004292 marked as pending in s390-dasd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1004292 [src:debian-installer] debian-installer:s390x: installer fails to 
format dasd disc on s390x systems
Added tag(s) pending.

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

Re: Processed: Re: Bug#1007838: d-i.debian.org: Installer iSCSI does not work in Debian 11

[Cyril Brulebois]

Thanks Eugene,

Eugene Losowski-Gallagher  
(2022-03-18):
> This looks like a duplicate of:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003366
> Same issue (but with more diagnostics).

Since one isn't supposed to be using iscsid within the installer, I'd
suggest dropping it from the udeb entirely, so that people don't waste
time trying to start a daemon that's not supposed to be started there?

Alternatively, if that daemon can still be useful within the installer,
I can look into implementing a double build for open-iscsi, building
with systemd support for the main binary, and without it for the udeb
binary.


In any cases, that's a bit of a side quest, and the real issue is why
the regular installer tools aren't able to set up iSCSI storage. :)
(And that part I'm not familiar enough at this stage to be able to
debug.)


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


signature.asc
Description: PGP signature

Re: Processed: Re: Bug#1007838: d-i.debian.org: Installer iSCSI does not work in Debian 11

[Eugene Losowski-Gallagher]

Hi All,

This looks like a duplicate of:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003366
Same issue (but with more diagnostics).

Thanks

Eugene

On Fri, 18 Mar 2022 at 08:48, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Processing control commands:
>
> > reassign -1 open-iscsi 2.1.3-5
> Bug #1007838 [d-i.debian.org] d-i.debian.org: Installer iSCSI does not
> work in Debian 11
> Bug reassigned from package 'd-i.debian.org' to 'open-iscsi'.
> Ignoring request to alter found versions of bug #1007838 to the same
> values previously set
> Ignoring request to alter fixed versions of bug #1007838 to the same
> values previously set
> Bug #1007838 [open-iscsi] d-i.debian.org: Installer iSCSI does not work
> in Debian 11
> Marked as found in versions open-iscsi/2.1.3-5.
> > affects -1 debian-installer
> Bug #1007838 [open-iscsi] d-i.debian.org: Installer iSCSI does not work
> in Debian 11
> Added indication that 1007838 affects debian-installer
> > tag -1 d-i
> Bug #1007838 [open-iscsi] d-i.debian.org: Installer iSCSI does not work
> in Debian 11
> Added tag(s) d-i.
>
> --
> 1007838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007838
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>

-- 

*Eugene Losowski-Gallagher*
*Mob: *07825160923

Re: Bug#1003484: bullseye-pu: package openssl/1.1.1m-0+deb11u1

[Adam D. Barratt]

On Wed, 2022-03-09 at 08:45 +0100, Sebastian Andrzej Siewior wrote:
> On 2022-02-19 17:57:25 [+], Adam D. Barratt wrote:
> > Feel free to upload; we'll wait for the d-i ack before accepting
> > the
> > package into p-u.
> 
> There will be the release of 1.1.1n on Tuesday 15th March 2022
> including
> a security fix. Therefore I will:
> - prepare a security release against 1.1.1k-1+deb11u1 which will be
>   released via d-security.
> - respond to this bug with a debdiff against 1.1.1m-0+deb11u1
> - upload 1.1.1n-0+deb11u1.
> 

Apologies if the status here got confused - based on the above, I was
assuming that in the absence of a negative response you would proceed
with the 1.1.1n-0+deb11u1 plan. For complete clarity, please feel free
to do so, bearing in mind that the window for the 11.3 point release
closes over this weekend.

Regards,

Adam

Bug#1004292: debian-installer:s390x: installer fails to format dasd disc on s390x systems

[Cyril Brulebois]

Hi Dipak,

Dipak Zope1  (2022-03-12):
> I have completed the installer testing for dasd and zfcp and this is
> the only outstanding item for s390x installer. I would recommend it
> for backporting.

This is great news.

> The merge request: 
> https://salsa.debian.org/installer-team/s390-dasd/-/merge_requests/1

Thanks, so basically, -f needs to go away.

It was apparently dropped between 1.36.1-1 and 1.37.1-1, even if that
wasn't documented:

 Release History:
 
+1.37.1
+Changes of existing tools:
+- dbginfo.sh: Add Docker debug data
+
+Bug Fixes:
+- lsdasd: Replace continue with return
+- lscss: Allow to specify devices from subchannel set 3
+- mon_fsstatd: Only use physical filesystems
+- mon_fsstatd: Fix double free in error path
+- mon_procd: Fix segmentation fault
+
+1.37.0
+Added new tools:
+- dump2tar: Add sysfs collection helper for dbginfo.sh
+
+Changes of existing tools:
+- build process: Add 'make help'
+- build process: Add 'make D=1' for debugging
+- build process: Add automatic dependency generation
+- build process: Do echo also when overriding commands
+- Added internal libraries:
+  * util_rec: Print records in different output formats
+  * util_libc: Handle standard errors for libc functions
+  * util_file: Read and write files
+  * util_scandir: Scan a directory for matching entries
+  * util_path: Work with paths
+  * util_opt: Parse the command line options
+  * util_prg: Print standard program messages
+  * util_panic: Collect FFDC data for unexpected errors
+- qethconf: Remove check for OSN-device
+- znetconf: Remove OSN-support
+- lsdasd/tunedasd: Add channel path aware erp
+- zcrypt: Add multi domain support for zcrypt device driver
+- scm: Reimplement lsscm in C
+- chp: Reimplement chchp and lschp in C
+- dbginfo.sh: Make use of sysinfo collection helper
+
+Bug Fixes:
+- zfcpdbf: Only cap SAN short payload if pl_len exists
+- chzdev: Fix bug when configuring QETH devices
+- libu2s: Prevent buffer overflow
+- ziomon: No blktrace kill which can corrupt kernel blktrace state

The diff regarding the manpage drops -f from the example, and also
removes the -f paragraph entirely, which documented it as deprecated, so
it looks pretty intentional anyway.


Looking at the s390-tools package (which provides s390-tools-udeb), and
its dasdfmt/dasdfmt.c, it seems that:
 - 1.36.1-1 (stretch) supported -f;
 - 2.3.0-2~deb10u1 (buster) doesn't;
 - 2.15.1-2 (bullseye) doesn't.

So it might make sense to backport the fix to both bullseye and buster?


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


signature.asc
Description: PGP signature

Re: Bug#1004452: bullseye-pu: package gnupg2/2.2.27-2+deb11u1

[Cyril Brulebois]

Adam D. Barratt  (2022-02-19):
> That looks fine to me, but will need a d-i ack as the package builds a
> udeb; tagging and CCing accordingly.

No objections, thanks.


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


signature.asc
Description: PGP signature

Re: Bug#1004452: bullseye-pu: package gnupg2/2.2.27-2+deb11u1

[Adam D. Barratt]

On Thu, 2022-03-17 at 19:29 -0400, Daniel Kahn Gillmor wrote:
> On Thu 2022-03-17 17:49:04 +, Adam D. Barratt wrote:
> > On Sat, 2022-02-19 at 22:24 -0500, Daniel Kahn Gillmor wrote:
> > > On Sat 2022-02-19 17:09:21 +, Adam D. Barratt wrote:
> > > > Control: tags -1 + confirmed d-i
> > > > 
> > [...]
> > > > That looks fine to me, but will need a d-i ack as the package
> > > > builds a
> > > > udeb; tagging and CCing accordingly.
> > > 
> > > Understood -- i'll wait for a d-i ack before uploading.
> > 
> > As we're getting very close to the window for 11.3 closing, please
> > feel
> > free to upload.
> 
> I've just uploaded gnupg2/2.2.27-2+deb11u1 to bullseye now.  Please
> let
> me know if there are any problems.

Unfortunately it looks like the upload failed:

gnupg2_2.2.27-2+deb11u1.dsc: Refers to non-existing file
'gnupg2_2.2.27.orig.tar.bz2.asc'

Regards,

Adam

Bug#1007776: authemtication of wireless network after password input fails

[Cyril Brulebois]

Hi Peter, and thanks for your report.

A couple of things: please avoid sending HTML messages in general. And
since you included a large picture (by mailing list configuration
standards), your report was not delivered to our list.

Peter Mueller  (2022-03-16):
> I tried to install unofficial (due to various drivers, in particular
> the Intel WiFi network driver) Debian bullseye. During the
> installation, I was asked for the network card, and I chose a wireless
> one: wlp179s0, which is in my case WLAN/Bluetooth Adapter PCIe (WL-PCI
> ASUS PCE-AX3000 BT5.0) Dual-Band (2,4 GHz/5 GHz), Bluetooth-Version
> 5.0.

Over the course of the installation process, did you get any messages
regarding missing firmware? I'm not sure this would explain the issue
you're describing, but that's an easy item to check for…

> I was asked for the WLAN ID, which I provided (the SSID of my router).
> Then I was asked for the type, which I provided as WPA/WPA2 PSK in my
> case (WPA2 for my router). Then I was asked for the WPA-Passphrase,
> which I typed in (WPA2 password for my router). Then a progress bar
> depicting an authentication attempt with the access point appeared.
> For a few minutes the bar continuously made progress  (the messages on
> the fourth console are attached) and finally reached 100%.  Then I saw
> a failure message asking me to verify the WPA-parameters which I
> input.
> I repeated the process several times, with the same result: no network
> during installation. The wireless card itself and the SSID-password
> combination are o.k. because I got connection using Debian live from
> the same installation drive. (Moreover, on a similar machine with the
> same network card the nerwork happily starts with NetworkManager,
> though with ifupdown there is a delay of several minutes at boot; cf.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993826).  Any
> bugfix? Any help?

The live test is quite useful, thanks for mentioning it. I'm wondering
whether this could be due to missing crypto modules inside our image,
which I've seen to be the reason for failure to associate from the
installer, while the installed system was fine. Any chance you could
start the live image again, save the output of `lsmod`, and attach it
here, using reply-all?


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


signature.asc
Description: PGP signature

Processed: Re: Bug#1007838: d-i.debian.org: Installer iSCSI does not work in Debian 11

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 open-iscsi 2.1.3-5
Bug #1007838 [d-i.debian.org] d-i.debian.org: Installer iSCSI does not work in 
Debian 11
Bug reassigned from package 'd-i.debian.org' to 'open-iscsi'.
Ignoring request to alter found versions of bug #1007838 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1007838 to the same values 
previously set
Bug #1007838 [open-iscsi] d-i.debian.org: Installer iSCSI does not work in 
Debian 11
Marked as found in versions open-iscsi/2.1.3-5.
> affects -1 debian-installer
Bug #1007838 [open-iscsi] d-i.debian.org: Installer iSCSI does not work in 
Debian 11
Added indication that 1007838 affects debian-installer
> tag -1 d-i
Bug #1007838 [open-iscsi] d-i.debian.org: Installer iSCSI does not work in 
Debian 11
Added tag(s) d-i.

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

Re: Bug#1007838: d-i.debian.org: Installer iSCSI does not work in Debian 11

[Cyril Brulebois]

Control: reassign -1 open-iscsi 2.1.3-5
Control: affects -1 debian-installer
Control: tag -1 d-i

Hi,

Reports against d-i.debian.org are usually about our infrastructure and
tooling, you could have filed the report against debian-installer
instead, which makes for a better default package. :)

2lv63...@duck.com <2lv63...@duck.com> (2022-03-17):
> When using the Debian 11 netinst.iso or mini.iso installer, iSCSI does not
> work.
> 
> Boot the installer and go through the dialogs (continue with no disk
> assuming a diskless client) until the "Partition disks" task.
> 
> Select "Configure iSCSI volumes" -> "Log into iSCSI targets" -> Enter portal
> information
> 
> Error pops up "No iSCSI targets discovered" regardless of settings used. The
> network is working correctly and the iSCSI targets are available. This works
> without issue in the Debian 10 installer.
> 
> Dropping to the command line reveals iscsiadm can not start iscsid. Manually
> running iscsid results in:
> iscsid: error while loading shared libraries: libsystemd.so.0: cannot open
> shared object file: No such file or directory
> 
> I'm not sure if this belongs in the cdrom bug list or if it affects all d-i.

That's not an issue about installation images (which would be for
debian-cd), but about a component that's linked against a library that's
not available in the installer's context.

Hence the reassigning above. I might look into it shortly, but I need to
get (old)stable point release preps squared away first.

Would you be happy to test a tweaked mini.iso that I'd build for you to
test?


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


signature.asc
Description: PGP signature

Re: Bug#1006192: bullseye-pu: package espeak-ng/1.50+dfsg-7+deb11u1

[Cyril Brulebois]

Samuel Thibault  (2022-03-14):
> d-i doesn't usually spit out large amounts of text so the problem was
> not really showing up there, the effect won't really be noticed.

No objections, thanks.


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


signature.asc
Description: PGP signature

Re: Bug#1006187: bullseye-pu: package espeakup/0.80-20+deb11u1

[Cyril Brulebois]

Samuel Thibault  (2022-03-14):
> No because in d-i espeakup is started by hand, the systemd service file
> is not installed in the .udeb.
> 
> d-i doesn't usually start large amounts of process in parallel so it's
> not a problem there.

No objections anyway, thanks.


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


signature.asc
Description: PGP signature

Re: Bug#1007746: buster-pu: package glibc/2.28-10+deb10u1

[Cyril Brulebois]

Adam D. Barratt  (2022-03-17):
> Please go ahead, thanks.
> 
> As glibc produces a udeb, I'm tagging the bug and CCing accordingly.

No objections, thanks.


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


signature.asc
Description: PGP signature

Re: Bug#1005949: bullseye-pu: package glibc/2.31-13+deb11u3

[Cyril Brulebois]

Adam D. Barratt  (2022-03-15):
> This looks OK to me, thanks.

Looks fine to me as well, thanks.
 

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


signature.asc
Description: PGP signature

Re: Bug#1006165: bullseye-pu: package tasksel/3.68+deb11u1

[Cyril Brulebois]

Hi,

Adam D. Barratt  (2022-03-14):
> That seems reasonable enough, but for completeness I'd appreciate a
> KiBi-ack ("don't be silly, Holger knows what they're doing" counts ;-)
> )

Looks good to me, thanks.

Holger, sorry I haven't been able to answer your questions when you
first started preparing that proposed update…


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


signature.asc
Description: PGP signature

Re: Bug#1007714: bullseye-pu: package openssh/1:8.4p1-5+deb11u1

[Cyril Brulebois]

Adam D. Barratt  (2022-03-17):
> As openssh builds a udeb, I'm CCing KiBi and tagging the bug
> accordingly.

Making sure upgrades have a chance to work properly seems more important
than any possible regressions at install time, for those deploying over
SSH, so no objections at all.


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


signature.asc
Description: PGP signature