Ole Marggraf <margg...@astro.uni-bonn.de> writes:
> Package: ia32-apt-get
> Version: 20
> Severity: important
>
>
> Hello Goswin,
>
> as it seems, ia32-apt-get deliberately ignores alternate list/cache
> directories defined in apt-conf...
>
> We are using an apt.conf with the following Dir section:
>
> Dir
> {
> Cache "/myaptetc_amd64/cache";
> Cache::archives "/myaptetc_amd64/archives/";
>
> Etc "/myaptetc_amd64";
>
> State "/aibn38_1/debian/apt/sid_amd64/state";
> State:lists "/myaptetc_amd64/lists";
> };
>
>
> (where /myaptetc_amd64 is located on an nfs volume, but that should not
> matter here).
>
> This being far from a standard configuration, I expected some additional
> adjustments on our side (such as manually creating the i386 and amd64
> dirs in place).
>
> However, it seems that ia32-apt-get ignores any directory modification
> in an "update" run, putting lists in the standard locations in /var/lib,
> and tries to respect at least some of the dir modifications in an
> "upgrade" run, but finding only some old lists of course and not doing
> any upgrade at all (ia32-lib* are equally not being found).
Indeed, ia32-apt-get assumes the default paths are in use. I never
heart of anyone changing them for the system wide config. I will have
to add code to support that.
Meanwhile is there any reason why you didn't use bind mounts?
mount --bind /myaptetc_amd64/cache /var/cache/apt
mount --bind /myaptetc_amd64/lists /var/lib/apt/lists
...
> Removing the Dir section from apt.conf and running with standard
> directories works without a problem, ia32-lib* and all.
>
> I do not find anything on changed Dir variables or anything in the apt
> manpages, so I suppose the apt.conf is still valid in this form.
>
> apt-config shows the correct settings:
>
> APT "";
> APT::Architecture "amd64";
> APT::Build-Essential "";
> APT::Build-Essential:: "build-essential";
> APT::Install-Recommends "0";
> APT::Install-Suggests "0";
> APT::Acquire "";
> APT::Acquire::Translation "environment";
> APT::Update "";
> APT::Update::Post-Invoke "";
> APT::Update::Post-Invoke:: "[ ! -x /usr/lib/ia32-libs-tools/mangle ] || cat
> /var/lib/apt/lists/*_Packages | /usr/lib/ia32-libs-tools/mangle --index
> >/dev/null";
> APT::NeverAutoRemove "";
> APT::NeverAutoRemove:: "^linux-image.*";
> APT::NeverAutoRemove:: "^linux-restricted-modules.*";
> APT::Periodic "";
> APT::Periodic::Update-Package-Lists "0";
> APT::Cache-Limit "50000000";
> Dir "/";
> Dir::State "/myaptetc_amd64/state";
> Dir::State::lists "lists/";
> Dir::State::cdroms "cdroms.list";
> Dir::State::userstatus "status.user";
> Dir::State::status "/var/lib/dpkg/status";
> Dir::Cache "/myaptetc_amd64/cache";
> Dir::Cache::archives "/myaptetc_amd64/archives/";
> Dir::Cache::srcpkgcache "srcpkgcache.bin";
> Dir::Cache::pkgcache "pkgcache.bin";
> Dir::Etc "/myaptetc_amd64";
> Dir::Etc::sourcelist "sources.list";
> Dir::Etc::sourceparts "sources.list.d";
> Dir::Etc::vendorlist "vendors.list";
> Dir::Etc::vendorparts "vendors.list.d";
> Dir::Etc::main "apt.conf";
> Dir::Etc::parts "apt.conf.d";
> Dir::Etc::preferences "preferences";
> Dir::Bin "";
> Dir::Bin::methods "/usr/lib/apt/methods";
> Dir::Bin::dpkg "/usr/bin/dpkg";
> Dir::Log "var/log/apt";
> Dir::Log::Terminal "term.log";
> Dir::State:lists "/myaptetc_amd64/lists";
> DPkg "";
> DPkg::Pre-Install-Pkgs "";
> DPkg::Pre-Install-Pkgs:: "/usr/bin/apt-listchanges --apt || test $? -ne 10";
> DPkg::Pre-Install-Pkgs:: "/usr/sbin/dpkg-preconfigure --apt || true";
> DPkg::Tools "";
> DPkg::Tools::Options "";
> DPkg::Tools::Options::/usr/bin/apt-listchanges "";
> DPkg::Tools::Options::/usr/bin/apt-listchanges::Version "2";
> DPkg::Options "";
> DPkg::Options:: "--force-confdef";
>
>
> Any idea?
I will use apt-config to parse the systems apt.conf and extract the
relevant paths from that instead of the hardcoded paths in use now.
> Best regards,
>
> Ole
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
