As there's nothing we can do about that without breaking other use
cases, we have to declare that working as intended.
Please clear your configuration before setting RootDir like options and
then re-init the config.
Sorry
** Changed in: python-apt (Ubuntu)
Status: Confirmed => Opinion
--
** Changed in: python-apt (Debian)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238616
Title:
creating apt cache with rootdir= still considers global apt config
To
** Changed in: python-apt (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238616
Title:
creating apt cache with rootdir= still considers global apt config
To m
We had that fixed for some time, but had to revert this now, because
code broke.
Anyway, you can get that behavior by clearing the config yourself,
before creating the cache object; something like:
for key in apt_pkg.config:
del apt_pkg.config[key]
apt_pkg.config["dir"] = rootdir
apt_pkg.init
Hello Julian,
Julian Andres Klode [2013-10-11 15:47 -]:
> We are limited here, because APT uses a global configuration instance,
> so in order to use the configuration of the other root directory, we'd
> have to drop the other configuration because they cannot co-exist.
Does that mean it's no
Michal and I debugged this over IRC, and tracked it down. He had an
/etc/apt/apt.conf with explicitly setting Architecture:, and creating an
apt.Cache(rootdir="...") object still takes that global configuration
into account.
The attached test script works on a default installation, downloads the
a
Michael Vogt, do you have an idea about this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238616
Title:
creating apt cache with rootdir= still considers global apt config
To manage notifications
Michal and I debugged this over IRC, and tracked it down. He had an
/etc/apt/apt.conf with explicitly setting Architecture:, and creating an
apt.Cache(rootdir="...") object still takes that global configuration
into account.
The attached test as
** Summary changed:
- Retracing armhf doesn't work
We are limited here, because APT uses a global configuration instance,
so in order to use the configuration of the other root directory, we'd
have to drop the other configuration because they cannot co-exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It needs to use the global configuration, we do not reload configuration
files. You can manually clear the config, set rootdir, and then call
apt_pkg.init() or the other two init functions after each other.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
10 matches
Mail list logo
