Hi,
sorry, I forgot to write down how to reproduce this bug and apparently lacked
enough clarity in my initial description. So here it goes:
To reproduce this bug add a aptpreferences line pointing to a valid pinning
file like to any multistrap config which does NOT include suite X. Then at the
same time in your *host* system (the system which runs multistrap) modify your
apt config so that the APT::Default-Release is suite X. Then try running that
multistrap config. Here step by step with X being "testing":
mkdir /tmp/multistraptest
cd /tmp/multistraptest
echo -ne "Package: *\nPin: release a=stable\nPin-Priority: 700\n" >
00pinning.pref
echo -ne
"[General]\ninclude=/usr/share/multistrap/squeeze.conf\naptpreferences=/tmp/multistraptest/00pinning.pref"
> multistrap.conf
echo 'APT::Default-Release "testing";' | sudo tee
/etc/apt/apt.conf.d/02default-release
sudo multistrap -f multistrap.conf -d debian-squeeze
The last line of multistrap output will read:
E: The value 'testing' is invalid for APT::Default-Release as such a
release is not available in the sources
We can work around this by disabling the apt config we just made:
sudo mv /etc/apt/apt.conf.d/02default-release
/etc/apt/apt.conf.d/02default-release.disabled
When running multistrap again everything will work fine. The reason for this
bug is the lines which read:
$config_str .= " -o Dir::Etc=${dir}${etcdir} -o APT::Default-Release=*"
if (not defined $preffile);
So only if no aptpreferences are specified will the APT::Default-Release be
set. This of course makes sense but it also means that on a system which sets
APT::Default-Release I can only use aptpreferences if the system I want to
create contains the suite with my APT::Default-Release.
I do not know what the solution to this problem is, but I don't think I should
have to disable my APT::Default-Release every time that I want to use
multistrap with aptpreferences.
I hope this is more clear now. Sorry for the time you lost because of my
initial confusing description.
cheers, josch
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
