Bug#603396: RM: libdc0/0.3.13-1

2011-02-28 Thread Julien Cristau
reassign 603396 ftp.debian.org tag 603396 - squeeze kthxbye On Sat, Nov 13, 2010 at 17:30:12 +, Daniel Silverstone wrote: > The version of libdc0 in unstable (0.3.23-1) fails to build from source on > armel. This is preventing the transition of the newer version to testing. > However, the fa

Bug#603396: RM: libdc0/0.3.13-1

2010-11-28 Thread Philipp Kern
On Sat, Nov 13, 2010 at 05:30:12PM +, Daniel Silverstone wrote: > The version of libdc0 in unstable (0.3.23-1) fails to build from source on > armel. This is preventing the transition of the newer version to testing. > However, the failure appears to be in code which is present in the version

Bug#603396: RM: libdc0/0.3.13-1

2010-11-13 Thread Daniel Silverstone
On Sat, Nov 13, 2010 at 07:21:02PM +0100, Julien Cristau wrote: > > I therefore suggest we remove it from testing before we end up having to > > support it in a stable release. > This would break valknut in testing. Given that popcon indicates that valknut is barely used, removing it also wouldn't

Bug#603396: RM: libdc0/0.3.13-1

2010-11-13 Thread Julien Cristau
On Sat, Nov 13, 2010 at 17:30:12 +, Daniel Silverstone wrote: > The version of libdc0 in unstable (0.3.23-1) fails to build from source on > armel. This is preventing the transition of the newer version to testing. > However, the failure appears to be in code which is present in the version i

Bug#603396: RM: libdc0/0.3.13-1

2010-11-13 Thread Julien Cristau
On Sat, Nov 13, 2010 at 17:30:12 +, Daniel Silverstone wrote: > I therefore suggest we remove it from testing before we end up having to > support it in a stable release. The exact same version is already in lenny, fwiw. Cheers, Julien signature.asc Description: Digital signature

Bug#603396: RM: libdc0/0.3.13-1

2010-11-13 Thread Daniel Silverstone
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm The version of libdc0 in unstable (0.3.23-1) fails to build from source on armel. This is preventing the transition of the newer version to testing. However, the failure appears to be in code w