Re: Debian on /usr (Re: TC decision on ownership of top-level filesystem aliases - #1091995)

2025-03-10 Thread Matthias Urlichs
On 09.03.25 17:45, Marco d'Itri wrote: On Mar 09, Matthias Urlichs wrote: My "build me a Debian image" script has been doing that for two years now, simply by moving /var/lib/dpkg to /usr/state/dpkg and bind-mounting it back onto /var/lib/dpkg (symlinking won't work). How so? My /var/lib/dpkg

Re: Debian on /usr (Re: TC decision on ownership of top-level filesystem aliases - #1091995)

2025-03-09 Thread Marco d'Itri
On Mar 09, Matthias Urlichs wrote: > My "build me a Debian image" script has been doing that for two years now, > simply by moving /var/lib/dpkg to /usr/state/dpkg and bind-mounting it back > onto /var/lib/dpkg (symlinking won't work). How so? My /var/lib/dpkg has been a symlink for a very long t

Debian on /usr (Re: TC decision on ownership of top-level filesystem aliases - #1091995)

2025-03-09 Thread Matthias Urlichs
On 06.03.25 11:25, Helmut Grohne wrote: onger term, it shall become possible to install Debian in such a way that the entire installation lives below /usr (though it will not be possible to upgrade such an installation due to the lack of /var/lib/dpkg in the initial implementation). My "build

Re: TC decision on ownership of top-level filesystem aliases - #1091995

2025-03-08 Thread Sean Whitton
Hello, On Thu 06 Mar 2025 at 11:25am +01, Helmut Grohne wrote: > Can you clarify how you understand policy here? > > I read it as systemd is not performing an installation here and > therefore does not violate the present policy. If your reading is > different, we should likely clarify policy on

Re: TC decision on ownership of top-level filesystem aliases - #1091995

2025-03-07 Thread Helmut Grohne
On Fri, Mar 07, 2025 at 08:14:00AM -0500, Marvin Renich wrote: > Are you saying that systemd creates the symlinks at runtime when it > finds them missing, rather that when the systemd package is installed? > To me, this is a clear violation of the policy quoted above. "...must > not install..." sa

Re: TC decision on ownership of top-level filesystem aliases - #1091995

2025-03-07 Thread Marvin Renich
* Helmut Grohne [250307 07:05]: > Hi Sean, > > On Thu, Mar 06, 2025 at 05:39:06PM +0800, Sean Whitton wrote: > > Just to note that the most recent release of Policy sort-of defines > > ownership of this, though it is not as explicit as the TC decision: > > > > Packages must not install files

Re: TC decision on ownership of top-level filesystem aliases - #1091995

2025-03-07 Thread Helmut Grohne
Hi Sean, On Thu, Mar 06, 2025 at 05:39:06PM +0800, Sean Whitton wrote: > Just to note that the most recent release of Policy sort-of defines > ownership of this, though it is not as explicit as the TC decision: > > Packages must not install files to paths whose first component is a > name

Re: TC decision on ownership of top-level filesystem aliases - #1091995

2025-03-06 Thread Sean Whitton
Hello ctte, On Tue 04 Mar 2025 at 11:46am GMT, Matthew Vernon wrote: > In Bug #1091995, the Technical Committe was asked to rule on an issue > that could, under certain circumstances, result in failure of the > base-files package to install or upgrade correctly. Under these > circumstances, syste

TC decision on ownership of top-level filesystem aliases - #1091995

2025-03-04 Thread Matthew Vernon
Hello, In Bug #1091995, the Technical Committe was asked to rule on an issue that could, under certain circumstances, result in failure of the base-files package to install or upgrade correctly. Under these circumstances, systemd will create a symlink from /lib64 to /usr/lib, which does not match