* Helmut Grohne [Tue Dec 18, 2018 at 01:30:36PM +0100]:

> If you backport mmdebstrap to stretch (yes, that's relatively easy after
> downgrading debhelper compatibility and dependency), you can observe the
> following interaction:

> # grep VERSION_ID /etc/os-release 
> VERSION_ID="9"
> # mmdebstrap buster /target
[...]
> Reading package lists...
> W: Problem unlinking the file auxfiles - Clean (21: Is a directory)
> apt-get --option Dir::Etc::SourceList=/dev/null update failed at
> /usr/bin/mmdebstrap line 569.
> # echo $?
> 1
> #

> I guess this is due to some interaction between stretch's apt and
> buster's apt. The resulting chroot looks like it works otherwise. If you
> don't want to diagnose this, please just close it as wontfix. I can
> fully understand that.

A similar thing happens when mmdebstrap-ing a stretch system (I'm
running this from a buster-based environment, JFTR). The directory
/var/lib/apt/lists/auxfiles is left behind and executing 'apt-get
update' will display the following message:

  W: Problem unlinking the file auxfiles - Clean (21: Is a directory)

A simple `rmdir /var/lib/apt/lists/auxfiles` seems to fix this. When
mmdebstrap-ing buster the directory (/var/lib/apt/lists/auxfiles)
exists as well, but apt doesn't complain about it.

regards,
-mika-

Attachment: signature.asc
Description: Digital signature

Reply via email to