On Thu, 6 Mar 2025 14:00:46 +0100, Lee Garrett
wrote:
>P.S.: This failure mode isn't even documented in the release notes.
But they do, don't they, recommend to have console access available
during an upgrade right?
Greetings
Marc
--
-
On Wed, 5 Mar 2025 14:36:20 -0500, "Helmut K. C. Tessarek"
wrote:
>On the other
>hand, it's not always possible to have a test bed for every single setup.
It is way easier to have a test bed or to arrange for console access
than even trying to cater for every situation that might happen. Rest
as
Lee Garrett writes:
>> On Tue, 4 Mar 2025 20:39:43 -0500, "Helmut K. C. Tessarek"
>> wrote:
>>>Network interface name changed: please update config files before reboot.
> P.S.: This failure mode isn't even documented in the release notes.
This does seem to be correct given that the OP was upg
On 2025-03-06 17:56, Helmut K. C. Tessarek wrote:
It was a Debian Buster on armv7l that I had forgotten, because it
was running perfectly until now, but apps complained that the OS is
no longer supported.
To clarify my previous statement:
The upgrade to bullseye changed the ifname.
Buster used
On 2025-03-05 07:38, Helmut Grohne wrote:
I am surprised to see this happen. Back in older times, interfaces used
to be named like eth0, but that should not be happening since quite a
number of stable releases. Those old systems that still use eth0 today
tend to do it due to a file /etc/udev/rule
On 2025-03-06 09:13, Wookey wrote:
Would it? Do we know why these things happened? K.C. does not say what
he was upgrading from/to (so it wasn't a very useful report in that
regard), but there has certainly been a long-term expectation that
headless upgrades will work (and in my experience of 25
Wookey writes:
> Which entry in which release notes will warn that this time
> (presumably - was this an upgrade to unstable K.C. or to bookworm, or
> something else?) the (pretty old now) eth0 -> 'annoying, unmemorable,
> but ordered and unique', renaming will/might actually break your
> config?
On Thu, Mar 06, 2025 at 02:13:49PM +, Wookey wrote:
Which entry in which release notes will warn that this time
(presumably - was this an upgrade to unstable K.C. or to bookworm, or
something else?) the (pretty old now) eth0 -> 'annoying, unmemorable,
but ordered and unique', renaming will/mi
On 3/6/25 4:00 PM, Lee Garrett wrote:
On Tue, 4 Mar 2025 20:39:43 -0500, "Helmut K. C. Tessarek"
wrote:
Both network "outages" could have been prevented by adding a note at
the end of the dist-upgrade output.
e.g. something like the following (monospace font required for the
"Attention" te
On 2025-03-06 08:43 +, Holger Levsen wrote:
> On Tue, Mar 04, 2025 at 08:39:43PM -0500, Helmut K. C. Tessarek wrote:
> > Both network "outages" could have been prevented by adding a note at the end
> > of the dist-upgrade output.
>
> they could also have been prevented by reading the release n
On Tue, 4 Mar 2025 20:39:43 -0500, "Helmut K. C. Tessarek"
wrote:
Both network "outages" could have been prevented by adding a note at the
end of the dist-upgrade output.
e.g. something like the following (monospace font required for the
"Attention" text):
_ _ _ _ _ _ ___
Il 06/03/2025 09:43, Holger Levsen ha scritto:
On Tue, Mar 04, 2025 at 08:39:43PM -0500, Helmut K. C. Tessarek wrote:
Both network "outages" could have been prevented by adding a note at the end
of the dist-upgrade output.
they could also have been prevented by reading the release notes and fol
On Tue, Mar 04, 2025 at 08:39:43PM -0500, Helmut K. C. Tessarek wrote:
> Both network "outages" could have been prevented by adding a note at the end
> of the dist-upgrade output.
they could also have been prevented by reading the release notes and following
their advice.
that would also have pre
On Wed, Mar 05, 2025 at 10:12:05PM +0100, Matthias Urlichs wrote:
On 05.03.25 21:35, Marc Haber wrote:
And which of the millions of changes would that be that would break
YOUR system?
The number of changes that can adversely impact your ability to boot
*or* your network connectivity (but whic
On Tue, Mar 04, 2025 at 08:39:43PM -0500, Helmut K. C. Tessarek wrote:
> This is my first mail in a Debian mailing list and I hope I've chosen the
> correct one. There are way too many lists thus please direct me to the
> correct one, in case I messed up.
As the matter is intersecting multiple pac
On 05.03.25 21:35, Marc Haber wrote:
And which of the millions of changes would that be that would break
YOUR system?
The number of changes that can adversely impact your ability to boot
*or* your network connectivity (but which won't fail the upgrade!) can
safely be assumed to be smaller th
On Wed, Mar 05, 2025 at 03:32:51PM -0500, Helmut K. C. Tessarek wrote:
I doubt there are more than one or at max two items that would break
network connectivity.
And which of the millions of changes would that be that would break YOUR
system?
--
-
Matthias Urlichs writes:
> On 05.03.25 17:16, Bjørn Mork wrote:
>> apt install apt-listchanges
>
> To be fair, apt-listchanges lists a whole lot of changes, esp. when
> you do a dist-upgrade.
>
> Noticing the one change among the umpteen more-or-less-major NEWS
> entries that actually affects the
On 2025-03-05 14:51, Bjørn Mork wrote:
We can (and do, AFAIK) discuss which items belong in NEWS. But there
are many more-or-less-major changes which might require attention when
you do a dist-upgrade. Filtering this list down to one or two items is
not realistic. And prefixing the list with ATT
On Wednesday, March 5, 2025 12:34:27 PM MST Marc Haber wrote:
> On Wed, Mar 05, 2025 at 06:29:26PM +0100, Matthias Urlichs wrote:
> >Noticing the one change among the umpteen more-or-less-major NEWS
> >entries that actually affects the ability of your system to safely
> >reboot with the same networ
On 2025-03-05 12:29, Matthias Urlichs wrote:
Noticing the one change among the umpteen more-or-less-major NEWS
entries that actually affects the ability of your system to safely
reboot with the same network configuration is not a trivial task, even
for reasonably experienced sysadmins.
I coul
Hello,
Thaank you for all the replies so far.
On 2025-03-05 10:15, Michael Banck wrote:
Presumably because it will be written directly to their terminal.
Yes, this is one of the reasons. During a dist-upgrade you receive the
changes, but it's many, many pages long and spotting the entry that
On Wed, Mar 05, 2025 at 06:29:26PM +0100, Matthias Urlichs wrote:
Noticing the one change among the umpteen more-or-less-major NEWS
entries that actually affects the ability of your system to safely
reboot with the same network configuration is not a trivial task, even
for reasonably experience
On 05.03.25 17:16, Bjørn Mork wrote:
apt install apt-listchanges
To be fair, apt-listchanges lists a whole lot of changes, esp. when you
do a dist-upgrade.
Noticing the one change among the umpteen more-or-less-major NEWS
entries that actually affects the ability of your system to safely
r
Michael Banck writes:
> On Wed, Mar 05, 2025 at 04:06:56PM +0100, Marc Haber wrote:
>> On Tue, 4 Mar 2025 20:39:43 -0500, "Helmut K. C. Tessarek"
>> wrote:
>> >Both network "outages" could have been prevented by adding a note at the
>> >end of the dist-upgrade output.
>> >
>> >e.g. something lik
Hi,
On Wed, Mar 05, 2025 at 04:06:56PM +0100, Marc Haber wrote:
> On Tue, 4 Mar 2025 20:39:43 -0500, "Helmut K. C. Tessarek"
> wrote:
> >Both network "outages" could have been prevented by adding a note at the
> >end of the dist-upgrade output.
> >
> >e.g. something like the following (monospace
On Tue, 4 Mar 2025 20:39:43 -0500, "Helmut K. C. Tessarek"
wrote:
>Both network "outages" could have been prevented by adding a note at the
>end of the dist-upgrade output.
>
>e.g. something like the following (monospace font required for the
>"Attention" text):
>
> _ _ _ _ _
Il 05/03/2025 02:39, Helmut K. C. Tessarek ha scritto:
This is my first mail in a Debian mailing list and I hope I've chosen
the correct one. There are way too many lists thus please direct me to
the correct one, in case I messed up.
I would like to make a suggestion for release upgrades. It s
28 matches
Mail list logo
