Bug#1056697: 12.2 Installation Report, Complete Failure of Network

2023-11-24 Thread Holger Wansing 
Hi,

Am 24. November 2023 23:54:49 MEZ schrieb David Hillman 
:
>On 11/24/23 12:59, Holger Wansing wrote:
>Thanks Holger.  I could do that, but that would completely defeat the purpose. 
> I installed Debian 12 on this machine as a test, to confirm that everything 
>necessary works, before installing it on a dozen or so other similar machines.

Trying a debian 13 image was meant as some sort of debugging. 
It would involve a newer kernel for example, in case it's a kernel issue...


Holger



-- 
Sent from /e/ OS on Fairphone3

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

2023-11-24 Thread Cyril Brulebois 
Hi David,

David Hillman  (2023-11-24):
> Thanks Holger.  I could do that, but that would completely defeat the
> purpose.  I installed Debian 12 on this machine as a test, to confirm that
> everything necessary works, before installing it on a dozen or so other
> similar machines.
> 
> And clearly, the opposite is the case, and it isn't ready for use yet, at
> least, not on server hardware.  I have D12 running on a laptop, and a few
> virtual machines, and it doesn't suffer this problem, but I will apparently
> have to stay with Ubuntu for a while on the servers.

Extracting /var/log/syslog would be useful to understand what's going on
there. A very quick search suggests this card might be supported by the
tg3 module (drivers/net/ethernet/broadcom/tg3.c), which is definitely
shipped in the installer. So maybe it's something that needs tweaking or
fixing on the firmware side (e.g. “modprobe dance”), or a missing
auxiliary bus (e.g. mhi) to make the card visible. Hard to tell without
any logs.


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


signature.asc
Description: PGP signature

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

2023-11-24 Thread David Hillman 

On 11/24/23 12:59, Holger Wansing wrote:

Hi,

David Hillman  wrote (Fri, 24 Nov 2023 12:34:50 -0600):

Ubuntu 20 and 22 installers work just fine on the same hardware, so this
is a Debian-specific issue.  All four interfaces work just fine under
both Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.

Maybe you could try a preview Debian 13 image?
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/



Thanks Holger.  I could do that, but that would completely defeat the 
purpose.  I installed Debian 12 on this machine as a test, to confirm 
that everything necessary works, before installing it on a dozen or so 
other similar machines.


And clearly, the opposite is the case, and it isn't ready for use yet, 
at least, not on server hardware.  I have D12 running on a laptop, and a 
few virtual machines, and it doesn't suffer this problem, but I will 
apparently have to stay with Ubuntu for a while on the servers.



--
David Hillman

Bug#1056700: Package: installation-reports

2023-11-24 Thread Julian Barg 
Package: installation-reports

Boot method: DVD image via USB Stick
Image version: 
https://laotzu.ftp.acc.umu.se/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso
Date: 2023-11-24 5PM EST

Machine: Thinkpad P14s AMD Gen 4
Processor: AMD Ryzen™ 7 PRO 7840U
Memory: 64 GB LPDDR5X-6400MHz (Soldered)
Partitions: separate management and home partition

Output of lspci -knn (or lspci -nn): didn't try to extract, but looked
correct for Thinkpad model "21K5001JUS".

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:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems: Regular boot failed. Recovery mode dropped me into
shell but I could not launch gnome session. ```exec gnome``` failed,
yielding Warning: "Could not make bus activated clients aware of
XDG_CURRENT_DESKTOP=GNOME environment variable: Cannot autolaunch
D-Bus without X11 $DISPLAY"

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

2023-11-24 Thread Holger Wansing 
Hi,

David Hillman  wrote (Fri, 24 Nov 2023 12:34:50 -0600):
> Ubuntu 20 and 22 installers work just fine on the same hardware, so this 
> is a Debian-specific issue.  All four interfaces work just fine under 
> both Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.

Maybe you could try a preview Debian 13 image?
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/


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

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

2023-11-24 Thread David Hillman 


Package: installation-reports

Boot method: USB stick
Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.2.0-amd64-netinst.iso

Date: 2023-November-23 11PM GMT

Machine: Dell R720
Processor: 2 x Xeon E5-2650
Memory: 192GB

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

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

Comments/Problems:


Installer completely failed to identify the presence of all four 
integrated Broadcom BCM5720 ethernet ports, and even after manually 
adding and configuring the four interfaces, no network connectivity is 
to be had.  Interfaces are allegedly "UP", but cannot ping anything nor 
respond to any communication.  IDRAC card interface works fine -- on the 
same subnet.  A half-dozen other multi-interface machines on the same 
subnet are working fine, as well.


Ubuntu 20 and 22 installers work just fine on the same hardware, so this 
is a Debian-specific issue.  All four interfaces work just fine under 
both Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.


Journal entries for NetworkManager and avahi-daemon appear to show the 
correct IP addresses being registered for all four interfaces, and "ip" 
agress, all to no avail.  No related error messages exist in the journal.




--
David Hillman

Bug#1056628: marked as done (udhcpc: file loss during upgrade due to Multi-Arch: same interacting with /usr-merge)

2023-11-24 Thread Debian Bug Tracking System 
Your message dated Fri, 24 Nov 2023 07:30:49 +0100
with message-id <20231124063049.ga2392...@subdivi.de>
and subject line Re: udhcpc: file loss during upgrade due to Multi-Arch: same 
interacting with /usr-merge
has caused the Debian Bug report #1056628,
regarding udhcpc: file loss during upgrade due to Multi-Arch: same interacting 
with /usr-merge
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.)


-- 
1056628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udhcpc
Version: 1:1.36.1-6~exp.1
Severity: normal
User: helm...@debian.org
Usertags: dep17p7

Hi Chris,

thanks for sitting down with me and doing this /usr-move. We aimed to be
careful and upload to experimental. Now dumat doesn't like your upload.
I'm trying to figure out why and whether this is an analyzer bug or a
real problem, so please do not move busybox to unstable for the time
bing.

What follows is details that you may skip entirely, but figured I better
write them down for my future self. So dumat figured that udhcpc is
Multi-Arch: same in bookworm and /sbin/udhcpc is a shared file. Then the
experimental package contains /usr/sbin/udhcpc. In theory, this could
result in a loss scenario, because you can install udhcpc for two
architecture in bookworm, dpkg --unpack the experimental one for one
architecture and then dpkg --remove the other. While you can unpack
udhcpc for two architectures, configuring it does not work out, because
it depends on busybox, which happens to implied to be Multi-Arch: no and
apt would never consider a solution where you'd have to coinstall
udhcpc. Also udhcpc was changed to an Architecture: all package later
and that also makes the issue unreproducible. In theory, the detector
should have noticed that the experimental package is not coinstallable
with itself and therefore the alleged problem cannot be exercised.

I think the latter is an analyzer bug and should have prevented the
issue from being displayed. In the mean time, please avoid uploading
this to unstable. I'll either close this bug or upgrade it to rc once I
have a better understanding of what's going on.

Helmut
--- End Message ---
--- Begin Message ---
Hi Chris,

TL;DR: If you don't convert udhcpc back to M-A:same and you'll be fine.

On Fri, Nov 24, 2023 at 12:27:38AM +0100, Helmut Grohne wrote:
> What follows is details that you may skip entirely, but figured I better
> write them down for my future self. So dumat figured that udhcpc is
> Multi-Arch: same in bookworm and /sbin/udhcpc is a shared file. Then the
> experimental package contains /usr/sbin/udhcpc. In theory, this could
> result in a loss scenario, because you can install udhcpc for two
> architecture in bookworm, dpkg --unpack the experimental one for one
> architecture and then dpkg --remove the other. While you can unpack
> udhcpc for two architectures, configuring it does not work out, because
> it depends on busybox, which happens to implied to be Multi-Arch: no and
> apt would never consider a solution where you'd have to coinstall
> udhcpc. Also udhcpc was changed to an Architecture: all package later
> and that also makes the issue unreproducible. In theory, the detector
> should have noticed that the experimental package is not coinstallable
> with itself and therefore the alleged problem cannot be exercised.

You've triggered a quite unique situation. The analyzer is correct about
it and the situation is fine. It was merely me being confused. :)

So yes, bookworm's udhcpc is m-a:same and performing the /usr-move runs
a theoretical risk of triggering the DEP17 P7 problem. As explained in
my earlier mail, you cannot actually trigger this for two reasons:
 * For one thing, udhcpc depends on busybox, which is implicitly m-a:no
   and therefore you cannot actually install two udhcpc concurrently.
   For technical correctness, you can dpkg --unpack them (leaving
   dependencies unsatisfied) and this would bear a risk, but apt never
   does this.
 * The trixie/sid/experimental packages have changed udhcpc to
   Architecture:all plus implied Multi-Arch:no. As a consequence, dpkg
   will not allow you to unpack the new udhcpc before removing all but
   one instance of udhcpc. This restriction reliably prevents the
   problem.

Now why did it show up in the dumat report? What I didn't read precisely
was that it did not predict a loss scenario, but a "pre-loss" scenario.
This is an advance warning about the P7 situation being close. In most
cases, where this is emitted, a dh_movetousr is the missing piece to

di-netboot-assistant_0.78~deb12u1_source.changes ACCEPTED into proposed-updates

2023-11-24 Thread Debian FTP Masters 
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Jun 2023 09:11:47 +0200
Source: di-netboot-assistant
Architecture: source
Version: 0.78~deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Andreas B. Mundt 
Changes:
 di-netboot-assistant (0.78~deb12u1) bookworm; urgency=medium
 .
   * Fixes for bookworm live iso image inclusion.
   * Update/add/fix preseed examples.  Thanks to Holger Wansing.
Checksums-Sha1:
 893d77d2eacb518146da688044668fc6871d0dc6 1966 
di-netboot-assistant_0.78~deb12u1.dsc
 63dc152b1376b65383eb272d056bc6efd6d388e3 47424 
di-netboot-assistant_0.78~deb12u1.tar.xz
 cb90dda546cd93076ed8b19429e6fbaa087bb82a 5932 
di-netboot-assistant_0.78~deb12u1_amd64.buildinfo
Checksums-Sha256:
 d6358111247490f005cb62c63360ca100483f26a718e5c30760c50be4c1d737e 1966 
di-netboot-assistant_0.78~deb12u1.dsc
 c89465132322ccc71988f0c305fe37288f9ae0d81e798e96c25207e5620398e0 47424 
di-netboot-assistant_0.78~deb12u1.tar.xz
 2feb65a710dfe96941e6d5d62455d2f270cfe938fc7fc055f097dc84a1afab0e 5932 
di-netboot-assistant_0.78~deb12u1_amd64.buildinfo
Files:
 12a68ede0c7ab07e5e0d88bd4a95164c 1966 utils optional 
di-netboot-assistant_0.78~deb12u1.dsc
 f0a883514d2e99668692dd153b1d93b9 47424 utils optional 
di-netboot-assistant_0.78~deb12u1.tar.xz
 5c9202164e58d281e1128b76c2f51fb0 5932 utils optional 
di-netboot-assistant_0.78~deb12u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEk4pc7h4pDeJV2ayYsB/qhGF7WG0FAmVYYjcACgkQsB/qhGF7
WG2edg//V1JN2GRRJ5QpdHDw/fsniUD/lzLFR0hZXizgcy5/iKP6EnbegOjN0oAE
ZSEjFmhKmELfmW/j340TKiV0CuTkCzf77WJDvIwjk4eVhkrPGHAgmpqTCa6g/wZe
k1X7tv6SeSCSAEa3ACYu0X9DjRaIGn6MC0382748qMpNFjWDNs6PMVFmxByqnIC4
QQCtz+bUWvwH08RUsxL8ydgjYPf12fD6wWsZFK64Pj3VF+Ijd6qrvMBnHYfIuge2
YFKNvvwrlotTkRVI/VPs49EhVTad2k8xMUkzOzJXyJ8uuBsnRYB/rup64FqCn0tm
yL4c4BU5/q2RyjB9qDjSr3cdIrQBRU0S4SEBK8NxKpHtBggYkl/lAxubb4bikC4z
cgKHCe2Dg7JBUvZioX+1K4HEPxyzv9aBPku917+6tEwnZY6YHgBFbB1FzkR0+ANK
hztgrKZKTvrwB8HOUPslofJBKwX1Wqb5SQMTdejOLVnQ/IEvmgH5LnbxWBK0j8nt
CleJqNyIMGvgwLQHKAbMo5sD990ghmwQMA8EyTY7cNV3N/0pvyeutqoRmgIVmJrT
uyUzPYcU3E7WG8spuyzTLnPbBW5DvbOt6q1mvIjDLo1pKFiPerDD7PUVUG0VG0nG
OmJ5EYoKu0ypVFq0DfjaUsxgRvgb4svFrLuc7oJACkXIV7YJnMA=
=i3Cb
-END PGP SIGNATURE-