[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#94061: bug #94061



der.hans (der.hans@LuftHans.com) wrote:

> Greg,
> 
> I've got a workaround solution for you and thought you might be interested.
> 
> I've been using this for a year or so without any problems for testing and
> unstable. I've now added security to the list as well :).
> 
> http://home.pages.de/~lufthans/unix/
> 
> See the link about the "security, testing and unstable updater for debian".
> 
> This is just a tarball that is meant to be untarred from slash. Being that
> it is such, please minimally review a tar tfz to verify I'm not doing
> anything evil :).
> 
> apt-sec update
> apt-sec -u dist-upgrade
> 
> The above would update a secondary package cache, not muddying up your main
> package cache, then perform a dist-upgrade against it, thereby only getting
> new packages as listed in the security updates.
> 
> Replace sec with test or uns for testing or unstable. There's also
> apt-cache-sec and friends for searching the caches and anthing else you do
> with apt-cache.
> 
> All three pick up the stable security updates, which should also be in the
> normal sources.list.
> 
> ciao,
> 
> der.hans
> -- 
> # der.hans@LuftHans.com home.pages.de/~lufthans/ www.DevelopOnline.com
> #  A t-shirt a day keeps the noose (tie) away. - der.hans
> 

(Note that I'm Cc'ing the bug report; that's why I quoted your whole
message.)

Hmm, interesting.  It's actually a small collection of shell scripts
that look like this:

.........................................................................
#!/bin/sh

THISAPT=apt-sec
CACHEDIR=/var/cache/$THISAPT
STATEDIR=/var/lib/$THISAPT

/usr/bin/apt-cache -o Dir::Etc::sourcelist=/etc/apt/security.list -o APT::Cache::archives=$CACHEDIR/archives/ -o APT::Cache::pkgcache=$CACHEDIR/pkgcache.bin -o APT::Cache::srcpkgcache=$CACHEDIR/srcpkgcache.bin -o Dir::State::lists=$STATEDIR/lists/ $*
.........................................................................

First, I'd replace $* with "$@" so that arguments with white space in
them are handled properly.  (I can't think of any apt-* arguments with
white space in them off the top of my head, but that's not the point.)

Second, while this is certainly a useful workaround, I doubt it's what
the apt maintainers will want to do. :-)

But I'm glad to see that I'm not the only person in the world who wants
this type of flexibility.

-- 
Greg Wooledge                  |   "Truth belongs to everybody."
greg@wooledge.org              |    - The Red Hot Chili Peppers
http://wooledge.org/~greg/     |

Attachment: pgpvyS9TFRopt.pgp
Description: PGP signature


Reply to: