Bug#515072: faad2: 2.7 packages are ready for upload
Andres Mejia schrieb: libfaad2-0 Please kill this package for the new upload. It was absolutely never needed at all! -- Dipl.-Phys. Fabian Greffrath Ruhr-Universität Bochum Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT) Universitätsstr. 150, IB 3/134 D-44780 Bochum Telefon: +49 (0)234 / 32-26334 Fax: +49 (0)234 / 32-14227 E-Mail: greffr...@leat.ruhr-uni-bochum.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515072: faad2: 2.7 packages are ready for upload
I went ahead and packaged up faad2-2.7. The packaging can be found at git://git.debian.org/git/pkg-multimedia/faad2.git http://git.debian.org/?p=pkg-multimedia/faad2.git;a=summary The tarball used is the same tarball from upstream, unmodified except for renaming it to faad2_2.7.orig.tar.gz. -- Regards, Andres -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515072: faad2: 2.7 packages are ready for upload
Forgot to mention this in the last mail. I've also fixed every bug in the BTS for faad2. faad2 will have to pass through the NEW queue again. One thing that changed is the name of the libfaad shared lib package. It's now named as libfaad2, since the library installed is libfaad.so.2.0.0. A debug package is also made for all binary packages produced by faad2. Finally, there's now going to be a shared lib package and dev package for libmp4ff. The static library and headers for libmp4ff is already created and installed by default by upstream. The shared lib is created and installed by patching the source. I already sent the patch upstream. --- Sent message --- I went ahead and packaged up faad2-2.7. The packaging can be found at git://git.debian.org/git/pkg-multimedia/faad2.git http://git.debian.org/?p=pkg-multimedia/faad2.git;a=summary The tarball used is the same tarball from upstream, unmodified except for renaming it to faad2_2.7.orig.tar.gz. -- Regards, Andres -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515072: faad2: 2.7 packages are ready for upload
On Sunday 31 May 2009 22:40:16 Felipe Sateler wrote: El lunes 1 de junio, Andres Mejia escribió: Forgot to mention this in the last mail. I've also fixed every bug in the BTS for faad2. faad2 will have to pass through the NEW queue again. One thing that changed is the name of the libfaad shared lib package. It's now named as libfaad2, since the library installed is libfaad.so.2.0.0. You should coordinate with the release team, so that you don't get faad tangled with some other transition. This is something we still have to wait for the new faad2 package to be accepted and enter testing anyway. I suppose once the new faad2 is accepted, binNMUs should be requested for reverse dependencies. Here's my list of packages depending on libfaad0 and libfaad2-0. $ apt-cache rdepends libfaad0 libfaad0 Reverse Depends: libquicktime1 libavcodec51 mpd libqmmp-misc xmms2-plugin-faad vlc-nox mpd moc libxine1-ffmpeg libquicktime1 libfaad2-0 libfaad-dev libavcodec52 gstreamer0.10-plugins-bad faad cmus $ apt-cache rdepends libfaad2-0 libfaad2-0 Reverse Depends: libfaad2 libfaad2 libfaad0 libfaad0 -- Regards, Andres -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515072: faad2: 2.7 packages are ready for upload
On Sunday 31 May 2009 23:28:04 Felipe Sateler wrote: El lunes 1 de junio, Andres Mejia escribió: On Sunday 31 May 2009 22:40:16 Felipe Sateler wrote: El lunes 1 de junio, Andres Mejia escribió: Forgot to mention this in the last mail. I've also fixed every bug in the BTS for faad2. faad2 will have to pass through the NEW queue again. One thing that changed is the name of the libfaad shared lib package. It's now named as libfaad2, since the library installed is libfaad.so.2.0.0. You should coordinate with the release team, so that you don't get faad tangled with some other transition. This is something we still have to wait for the new faad2 package to be accepted and enter testing anyway. No. Imagine libA is transitioning. faad is uploaded to unstable. Package B is built against the new faad. Then libfaad has becomed tangled with the transition of libA: B cannot transition into testing until libfaad does too. The transitions are *into* testing. Could you CC 515...@bugs.debian.org? faad2 is not maintained by the multimedia team yet. Alright then, I'll contact the release team. However, will any DD from the multimedia team upload the new faad2? I suppose once the new faad2 is accepted, binNMUs should be requested for reverse dependencies. Here's my list of packages depending on libfaad0 and libfaad2-0. You have to look at the reverse build-dependencies on the -dev package. Is there some program that will show reverse build-dependencies? I can't figure out how to make apt-cache do this. -- Regards, Andres -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515072: faad2: 2.7 packages are ready for upload
El lunes 1 de junio, Andres Mejia escribió: On Sunday 31 May 2009 23:28:04 Felipe Sateler wrote: El lunes 1 de junio, Andres Mejia escribió: On Sunday 31 May 2009 22:40:16 Felipe Sateler wrote: El lunes 1 de junio, Andres Mejia escribió: Forgot to mention this in the last mail. I've also fixed every bug in the BTS for faad2. faad2 will have to pass through the NEW queue again. One thing that changed is the name of the libfaad shared lib package. It's now named as libfaad2, since the library installed is libfaad.so.2.0.0. You should coordinate with the release team, so that you don't get faad tangled with some other transition. This is something we still have to wait for the new faad2 package to be accepted and enter testing anyway. No. Imagine libA is transitioning. faad is uploaded to unstable. Package B is built against the new faad. Then libfaad has becomed tangled with the transition of libA: B cannot transition into testing until libfaad does too. The transitions are *into* testing. Could you CC 515...@bugs.debian.org? faad2 is not maintained by the multimedia team yet. Sorry, I didn't notice that. Alright then, I'll contact the release team. However, will any DD from the multimedia team upload the new faad2? I can't help you with that (not a DD myself). I suppose once the new faad2 is accepted, binNMUs should be requested for reverse dependencies. Here's my list of packages depending on libfaad0 and libfaad2-0. You have to look at the reverse build-dependencies on the -dev package. Is there some program that will show reverse build-dependencies? I can't figure out how to make apt-cache do this. Well, if you have some deb-src line in your apt sources.list, you can use grep-dctrl: grep-dctrl -FBuild-Depends -sPackage libfaad-dev /var/lib/apt/lists/mirrorSources Saludos, Felipe Sateler signature.asc Description: This is a digitally signed message part.
Bug#515072: faad2: 2.7 packages are ready for upload
On Monday 01 June 2009 00:46:21 Felipe Sateler wrote: El lunes 1 de junio, Andres Mejia escribió: On Sunday 31 May 2009 23:28:04 Felipe Sateler wrote: El lunes 1 de junio, Andres Mejia escribió: On Sunday 31 May 2009 22:40:16 Felipe Sateler wrote: El lunes 1 de junio, Andres Mejia escribió: Forgot to mention this in the last mail. I've also fixed every bug in the BTS for faad2. faad2 will have to pass through the NEW queue again. One thing that changed is the name of the libfaad shared lib package. It's now named as libfaad2, since the library installed is libfaad.so.2.0.0. You should coordinate with the release team, so that you don't get faad tangled with some other transition. This is something we still have to wait for the new faad2 package to be accepted and enter testing anyway. No. Imagine libA is transitioning. faad is uploaded to unstable. Package B is built against the new faad. Then libfaad has becomed tangled with the transition of libA: B cannot transition into testing until libfaad does too. The transitions are *into* testing. Could you CC 515...@bugs.debian.org? faad2 is not maintained by the multimedia team yet. Sorry, I didn't notice that. Alright then, I'll contact the release team. However, will any DD from the multimedia team upload the new faad2? I can't help you with that (not a DD myself). I suppose once the new faad2 is accepted, binNMUs should be requested for reverse dependencies. Here's my list of packages depending on libfaad0 and libfaad2-0. You have to look at the reverse build-dependencies on the -dev package. Is there some program that will show reverse build-dependencies? I can't figure out how to make apt-cache do this. Well, if you have some deb-src line in your apt sources.list, you can use grep-dctrl: grep-dctrl -FBuild-Depends -sPackage libfaad-dev /var/lib/apt/lists/mirrorSources Thanks. This is what I got. $ grep-dctrl -FBuild-Depends -sPackage libfaad-dev /var/lib/apt/lists/ftp.us.debian.org*Sources Package: mpd Package: qmmp Package: cmus Package: ffmpeg-debian Package: gst-plugins-bad0.10 Package: libquicktime Package: moc Package: mpd Package: vlc Package: xine-lib Package: xmms2 -- Regards, Andres -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
