apt dir hierarchy retained in the chroot with essential variant #47

New issue

Closed

opened 2024-11-07 17:02:52 +00:00 by mexsus · 2 comments

mexsus commented

2024-11-07 17:02:52 +00:00

Hi. Is it expected that if bootstrapping a system using variant: essential (I use bdebstrap), /etc/apt/ and it's sub-dir hierarchy is present in the chroot upon completion of mmdebstrap execution?
The man page states:

   essential
           "Essential:yes" packages.

   apt     The essential set plus apt.

I was expecting that if using essential mmdebstrap would remove /etc/apt/ from the chroot.
I don't have any aptopt present.

Obviously this isn't a big deal as I can just rm -rf $1/etc/apt in a customize hook :)

Hi. Is it expected that if bootstrapping a system using ```variant: essential``` (I use bdebstrap), ```/etc/apt/``` and it's sub-dir hierarchy is present in the chroot upon completion of mmdebstrap execution? The man page states: > essential > "Essential:yes" packages. > > apt The essential set plus apt. I was expecting that if using ```essential``` mmdebstrap would remove ```/etc/apt/``` from the chroot. I don't have any ```aptopt``` present. Obviously this isn't a big deal as I can just ```rm -rf $1/etc/apt``` in a customize hook :)

mexsus commented

2024-11-07 17:43:21 +00:00

Author

I can just rm -rf $1/etc/apt in a customize hook

Unfortunately, that results in:

...
I: cleaning package lists and apt cache...
done
done
E: failed to unlink /etc/apt/apt.conf.d/00mmdebstrap: No such file or directory

The same occurs even if it's done in a cleanup hook. Maybe it can't be removed? What do you think?

> I can just rm -rf $1/etc/apt in a customize hook Unfortunately, that results in: ``` ... I: cleaning package lists and apt cache... done done E: failed to unlink /etc/apt/apt.conf.d/00mmdebstrap: No such file or directory ``` The same occurs even if it's done in a cleanup hook. Maybe it can't be removed? What do you think?