Bug#679671: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8

2012-07-06 Thread Goswin von Brederlow
On Thu, Jul 05, 2012 at 08:55:37PM -0400, Larry wrote: The dependency problem was with package ia32-libs-i386. You submitted new ia32-libs but not the package in question ia32-libs-i386 It still depends on the removed package libdb4.8, thus ia32-libs is still broken because it depends on

Bug#679671: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8

2012-07-01 Thread Goswin von Brederlow
Sven Joachim svenj...@gmx.de writes: Package: ia32-libs-i386 Version: 20120616 Severity: serious Your package depends on libdb4.8 which is no longer available in unstable. It is still in wheezy. I assume it is going to be removed there as well? Dear Release Team, as per

Bug#679671: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8

2012-07-01 Thread Adam D. Barratt
On Sun, 2012-07-01 at 11:13 +0200, Goswin von Brederlow wrote: Sven Joachim svenj...@gmx.de writes: Your package depends on libdb4.8 which is no longer available in unstable. It is still in wheezy. No, it isn't (and wasn't when you mailed). I assume it is going to be removed there as

Bug#679671: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8

2012-07-01 Thread Adam D. Barratt
[Dropped pkg-db-devel from Cc because it apparently doesn't accept posts from non-subscribers] On Sun, 2012-07-01 at 11:56 +0100, Adam D. Barratt wrote: Looking at the package currently in unstable, I do have to ask what happened to: ia32-libs-20120616/debian/copyright|13164 --

Bug#679671: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8

2012-07-01 Thread Goswin von Brederlow
Adam D. Barratt a...@adam-barratt.org.uk writes: [Dropped pkg-db-devel from Cc because it apparently doesn't accept posts from non-subscribers] On Sun, 2012-07-01 at 11:56 +0100, Adam D. Barratt wrote: Looking at the package currently in unstable, I do have to ask what happened to: