Re: mass RC-bug filing? deps on libart-2.0-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
> 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[1] ? 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.
[1]
http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-porter-guidelines
- --
hi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAftaXibPvMsrqrwMRAoLAAJ9qDN1m4kAkFCJyhj6TgpgUdqG1wwCfSMxh
TZe88KWagleFrGY0n5wH+IA=
=OaE7
-----END PGP SIGNATURE-----
Reply to: