Closed sam-gq closed 1 year ago
This is limitation of proot default link2symlink handling, you can switch that but it'll require wiping your current installation:
proot-distro reset debian
)mkdir /.l2s
proot-distro
again, after restarting it is okay to start using apt
Good point, I think it is gonna work, not sure. So I tried to create a new clean install instead, and I followed your instruction.
- After first login run following command in guest: mkdir /.l2s
- Exit from that session and start proot-distro again, after restarting it is okay to start using apt.
In just 1st or 2nd attempts of upgrading apt upgrade usrmerge, the usrmerge works in 2nd attempt (don't remember the 1st attempt how to do if I just restart proot when outputs an error of apt upgrade).
In my inspection, I tried to execute convert-usrmerge again and it works. And I look at the root directory, there has no /bin, /sbin, and /lib folder anymore. Just an invalid file but it has a symbolic link as well!
Anyway, I have a request. Do you have a time to make /.l2s directory of the debian rootfs, and then upload it to proot-distro? Seems to be great.
@michalbednarski is that ok? Or anyone..
I'd have to redirect that topic (creation of /.l2s in guest) back to proot-distro (@sylirre)
As far as I can remember there were some problems with that but cannot remember what
Yes, there were problems related to /.l2s directory. For example on Alpine Linux it was not possible to install gcc package. However it seems doesn't happen now or there different steps needed to trigger.
Problem description
I am using Debian Unstable for a long time on my devices which I used for leaning how to use debian package.
I have a new update about “init-system-helpers” package with version 1.65.2 from 1.64. Which it has a new dependency package called “usrmerge”.
init-system-helpers is the essential package in which package has essential tag cannot be removed.
Now I accept the update after backup the entire distro.
Here this is happened.
Please find out how to fix this error before Debian Bookworm came out in, which is being accepted by the maintainers.
As of now I held the init-system-helpers from updating to latest version, unless the dependency “usrmerge” will be removed.
Please look at the Debian Package Tracker. https://tracker.debian.org/
Or you can redirect that said package. https://tracker.debian.org/pkg/init-system-helpers https://tracker.debian.org/pkg/usrmerge
What steps will reproduce the bug?
I'm on Debian Unstable. Simply apt upgrade the init-system-helpers with usrmerge.
What is the expected behavior?
Expecting to be good after updating init-system-helpers with a new dependency “usrmerge” that is not in the use case but required by debian if I forgot to update the package.