Bug#1064617: update password selection advice

[Diederik de Haas]

On Tuesday, 19 March 2024 12:08:53 CET Holger Wansing wrote:
> Apparently we have reached something like a consensus on this topic,
> should we merge this then?
> 
> 
> 
> Any objections?

LGTM :-)

possibly `s/rms/debra/` with username examples?

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

Bug#1064617: update password selection advice

[Philip Hands]

Holger Wansing  writes:

> Apparently we have reached something like a consensus on this topic, 
> should we merge this then?
>
> 
>
> Any objections?

None from me.

The only reason I've not done it already was that I wanted to check that
the wording still works if we were to merge MR !6 [1] or something like it.

However the current t64 transition bugs stopped me from building a
mini-ISO, and I've been busy since noticing that, so didn't have time to
work out how to work round those bugs.

That's not a reason to delay this MR though.

Cheers, Phil.

[1] https://salsa.debian.org/installer-team/user-setup/-/merge_requests/6



>
>
> Holger
>
>
> -- 
> Sent from /e/ OS on Fairphone3
>

-- 
Philip Hands -- https://hands.com/~phil


signature.asc
Description: PGP signature

Bug#923091: marked as done (base-installer: Allow installing w/o the broken merged-usr-via-symlinks)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 12:31:36 +0100
with message-id <20240319113136.w3x36ynyk4jjv...@shell.thinkmo.de>
and subject line Re: Bug#923091: base-installer: Allow installing w/o the 
broken merged-usr-via-symlinks
has caused the Debian Bug report #923091,
regarding base-installer: Allow installing w/o the broken 
merged-usr-via-symlinks
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.)


-- 
923091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base-installer
Version: 1.187
Severity: wishlist

Hi!

The current base-installer uses the default debootstrap settings
which end up unconditionally installing systems with the
merged-usr-via-symlinks deployment method which is broken by design,
please see:

  

I'm aware the original request to change the debootstrap default got
unfortunately moved to the tech-ctte. :(

But regardless of that outcome I'd like to request to have a way to
install using debootstrap's --no-merged-usr option, to not have to
install from stretch and then upgrade to buster, or having to drop into
a shell and do manual stuff from within the installer.

In addition it would be also nice if that option was passed whenever
/usr is not on its own partition, because then the properties from
the merged-/usr concept are not relevant anymore, but we get all the
downsides of the broken deployment method.

If this was to be applied for buster, I'd be happy to provide patches.

Otherwise I guess I might need to end up looking to generate
alternative netinst somewhere else or something. :(

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
On Sun, Feb 24, 2019 at 03:10:17AM +0100, Guillem Jover wrote:
> I'm aware the original request to change the debootstrap default got
> unfortunately moved to the tech-ctte. :(

And ctte made an decision.  So there is no bug here.  Closing.

Bastian

-- 
Violence in reality is quite different from theory.
-- Spock, "The Cloud Minders", stardate 5818.4--- End Message ---

Bug#1064617: update password selection advice

[Holger Wansing]

Apparently we have reached something like a consensus on this topic, 
should we merge this then?



Any objections?


Holger


-- 
Sent from /e/ OS on Fairphone3

Bug#923091: this is a mighty weird open bug

[Peter Gervai]

That's a weird bug to have open, especially considering the last entry from 
2019.

I landed here because dpkg have thrown a message on me 

Unpacking dpkg (1.21.22) over (1.21.21) ... 
  
Setting up dpkg (1.21.22) ...   
  
dpkg: warning: This system uses merged-usr-via-aliased-dirs, going behind 
dpkg's  
dpkg: warning: back, breaking its core assumptions. This can cause silent file  
  
dpkg: warning: overwrites and disappearances, and its general tools 
misbehavior.  
dpkg: warning: See .
  

referring me to
https://wiki.debian.org/Teams/Dpkg/FAQ#broken-usrmerge
which lead to
https://wiki.debian.org/Teams/Dpkg/MergedUsr
which pointed to a seemingly unfinished thread on ML and this bugreport.

It was surprising because I thought that's been over for a long time now.
(https://lists.debian.org/debian-devel-announce/2022/09/msg1.html and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978636 (closed))

Could anyone insert pointers here about
- what's the official layout now
- what are the supported layouts 
- what's with dpkg vs layouts
- what's with this open bug now, around 2024?

(Disclaimer: arrived from Devuan since, as you might have guessed, I try to
keep my system uninfected, but otherwise it should not matter too much where
I'm arriving from.)

(Except maybe if it's about patches like this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061718 
but then it would be neat to keep Debian wiki in sync with reality and
close/keep bugs with relevant summary to help the people finding for clues.)

Thanks,
Peter