David Kalnischkies <da...@kalnischkies.de> wrote: > That said, it might make sense to be able to set an empty value from the > cmdline, yes, but apt doesn't have a way for it either
It seems, that tools from apt package now (ver. 2.2.3) _do_ allow to unset an
apt.conf(5) option by using `-o`:
$ apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 https://deb.debian.org/debian rc-buggy/main amd64 Packages
release
o=Debian,a=experimental,n=experimental,l=Debian,c=main,b=amd64
origin deb.debian.org
990 https://deb.debian.org/debian sid/main amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64
origin deb.debian.org
Pinned packages:
$ apt-cache -o APT::Default-Release='' policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 https://deb.debian.org/debian rc-buggy/main amd64 Packages
release
o=Debian,a=experimental,n=experimental,l=Debian,c=main,b=amd64
origin deb.debian.org
500 https://deb.debian.org/debian sid/main amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64
origin deb.debian.org
Pinned packages:
While aptitude(8) still complains about syntax:
$ aptitude -o APT::Default-Release='' show
-o requires an argument of the form key=value, got APT::Default-Release=
Should not it be brought into the line?
signature.asc
Description: PGP signature
