Re: mass RC-bug filing? deps on libart-2.0-2
-----BEGIN PGP SIGNED MESSAGE-----
Riku Voipio wrote:
> On Thursday 15 April 2004 20:56, Rene Engelhard wrote:
> > $ grep-available -FDepends libart-2.0 | grep Package > l
> > $ $ for p in `cat l | sed -e s/"Package: "//`; do if apt-cache show $p |
> > grep -q libart-2.0-2 && ! apt-cache show $p | grep -q "libart-2.0-2 (>=
> > 2.3.8)"; then echo $p; fi; done
> I understand this only locates packages on $ARCH you use? other arches
> may have other packages linked against the broken libart package.
> In any case, you would want to list the source packages, the current listing
> will give (if I read it correctly) binary packages.
Right. that is i386 here.
(and with an available file from some days ago, no idea whether some
stuff got added in the meantime..)
I probably should do a zgrep on the Packages.gz files...
> > Is (mass-)filing serious bugs against those pkgs ok?
> > (adding build-conflicts against that libart version and rebuilding with
> > the fixed one)
> Isn't broken build env a use case of binNMU ? However, as most packages
> depending on libart are huge, it might be worth bugging the maintainer, if
> there is a new upload coming soon anyway.
Bin-NMU those on all archs which are affected?
I don't think this is a very good way.
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' firstname.lastname@example.org | GnuPG-Key ID: 248AEB73
`- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
-----END PGP SIGNATURE-----