Hi Roland,
Thanks for taking the time to look into this.
> E: Unable to locate package E:
>E: Unable to locate package program
>E: Unable to locate package grep-aptavail
>E: Unable to locate package not
>E: Unable to locate package found!
That's definitely not from my repository, there are only 2 files in there:
```
$ cat config/package-lists/*
! Packages Priority important
! Packages Priority required
$ tree config/package-lists/
config/package-lists/
├── 00-important.list.chroot
└── 00-required.list.chroot
```
I'm not getting this error at build time either,
```
...
[2025-10-24 00:20:54] lb chroot_install-packages install
P: Begin installing packages (install pass)...
Reading package lists...
Building dependency tree...
Reading state information...
adduser is already the newest version (3.152).
apt-utils is already the newest version (3.0.3).
cpio is already the newest version (2.15+dfsg-2).
cron is already the newest version (3.0pl1-197).
...
```
Make sure that your copy is clean and that you are on the same
live-build version as me? (the one from trixie)
I am only using packages from stable repositories. I also thought it
could be a preoblem in debootstrap, since this is the only direct
dependency of live-build:
```
srvadmin@builder-trixie:/var/debian-live-config$ apt policy debootstrap
debootstrap:
Installed: 1.0.141
Candidate: 1.0.141
Version table:
*** 1.0.141 500
500 https://deb.debian.org/debian trixie/main amd64 Packages
500 https://deb.debian.org/debian trixie/main i386 Packages
100 /var/lib/dpkg/status
```
```
srvadmin@builder-trixie:/var/debian-live-config$ git status --ignored
On branch minimal-reproduce-readonly-root-filesystem
Your branch is up to date with
'origin/minimal-reproduce-readonly-root-filesystem'.
nothing to commit, working tree clean
srvadmin@builder-trixie:/var/debian-live-config$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.1
ID=debian
HOME_URL="https://www.debian.org/";
SUPPORT_URL="https://www.debian.org/support";
BUG_REPORT_URL="https://bugs.debian.org/";
srvadmin@builder-trixie:/var/debian-live-config$ apt policy live-build
live-build:
Installed: 1:20250505+deb13u1
Candidate: 1:20250505+deb13u1
Version table:
*** 1:20250505+deb13u1 500
500 https://deb.debian.org/debian trixie/main amd64 Packages
500 https://deb.debian.org/debian trixie/main i386 Packages
100 /var/lib/dpkg/status
srvadmin@builder-trixie:/var/debian-live-config$ sudo lb config && sudo lb build
...
```
The build succeeds, the ISO boots, the installer runs without apparent
errors, but the resuting filesystem cannot be traversed by any user
except root.
Can you at least reproduce a successful build using the same version
as me? The error you're getting is definitely strange and not related
to anything in the repository.
Le sam. 18 oct. 2025 à 09:53, Roland Clobus <[email protected]> a écrit :
>
> Control: severity 1118163 normal
>
> Hello nodiscc,
>
> On 15/10/2025 18:45, nodiscc wrote:
> > git clone -b minimal-reproduce-readonly-root-filesystem
> > https://github.com/nodiscc/debian-live-config/
> > cd debian-live-config
> > sudo lb config && sudo lb clean && sudo lb build
>
> I did `lb config; sudo lb build` after a fresh git clone.
>
> This reproducer case does not build, I see:
> ```
> [2025-10-18 09:58:57] lb chroot_install-packages install
> P: Begin installing packages (install pass)...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> E: Unable to locate package E:
> E: Unable to locate package program
> E: Unable to locate package grep-aptavail
> E: Unable to locate package not
> E: Unable to locate package found!
> E: Couldn't find any package by glob 'found!'
> E: Unable to locate package E:
> E: Unable to locate package program
> E: Unable to locate package grep-aptavail
> E: Unable to locate package not
> E: Unable to locate package found!
> E: Couldn't find any package by glob 'found!'
> E: An unexpected failure occurred, exiting...
> ```
>
> So I'm currently not able to proceed to booting the ISO to reproduce
> this bug report.
>
> With kind regards,
> Roland Clobus
