Hi,
Christophe Prud'homme wrote:
> suitesparse (3.2.0-1) unstable; urgency=low
^^^^^^^^
WTF?
> Accepted:
> libsuitesparse-3.2.0_3.2.0-1_i386.deb
> to pool/main/s/suitesparse/libsuitesparse-3.2.0_3.2.0-1_i386.deb
> libsuitesparse-dbg_3.2.0-1_i386.deb
> to pool/main/s/suitesparse/libsuitesparse-dbg_3.2.0-1_i386.deb
> libsuitesparse-dev_3.2.0-1_i386.deb
> to pool/main/s/suitesparse/libsuitesparse-dev_3.2.0-1_i386.deb
> libsuitesparse-doc_3.2.0-1_all.deb
> to pool/main/s/suitesparse/libsuitesparse-doc_3.2.0-1_all.deb
> suitesparse_3.2.0-1.diff.gz
> to pool/main/s/suitesparse/suitesparse_3.2.0-1.diff.gz
> suitesparse_3.2.0-1.dsc
> to pool/main/s/suitesparse/suitesparse_3.2.0-1.dsc
> suitesparse_3.2.0.orig.tar.gz
> to pool/main/s/suitesparse/suitesparse_3.2.0.orig.tar.gz
Nice. Uploading a NEW PACKAGE NAME version of suitesparse, breaking all
of the following reverse-deps:
[EMAIL PROTECTED]:~$ grep-available -FDepends libsuitesparse-3.1.0 -sPackage
Package: libsuitesparse-dev
Package: illuminator-demo
Package: libluminate7
Package: python-scipy
Package: libpetsc2.3.3
Package: openoffice.org-calc
Package: lp-solve
Package: octave3.0
Package: octave3.1
Package: python-sparse
Package: freemat
Package: libsuitesparse-dbg
(and openoffice.org-core in turn depends on lp-solve).
When those now get rebuilt in sid against the new suitesparse (and they need to
because they will become uninstallable when libsuitesparse-3.1.0
semi-automatically
get removed) they can't be fixed via sid anymore.
Did you EVER hear of the freeze?
Upload such stuff to experimental.
Anyway, we discussed that quickly on #debian-relese.
Reverted. Will NMU with epoch uploading 3.1.0 again.
Grüße/Regards,
René
--
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73
`- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
