Debian Bug report logs - #448565
apt-transport-debtorrent: not installable in unstable (amd64)

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Chris Lawrence <lawrencc@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: apt-transport-debtorrent: not installable in unstable (amd64)

Date: Mon, 29 Oct 2007 21:37:07 -0500

Package: apt-transport-debtorrent
Version: 0.1.1
Severity: important

The current apt supplies libapt-pkg-libc6.6-6-4.6, rather than -4.4 or
-4.5; I believe a simple rebuild of apt-transport-debtorrent will fix
the problem.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23.1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apt-transport-debtorrent depends on:
pn  libapt-pkg-libc6.6-6-4.4      <none>     (no description available)
ii  libc6                         2.6.1-6    GNU C Library: Shared libraries
ii  libgcc1                       1:4.2.2-3  GCC support library
ii  libstdc++6                    4.2.2-3    The GNU Standard C++ Library v3

Versions of packages apt-transport-debtorrent recommends:
ii  debtorrent                    0.1.4.4    bittorrent proxy for downloading D

Message #10 received at 448565@bugs.debian.org (full text, mbox, reply):

From: "Cameron Dale" <camrdale@gmail.com>

To: "Chris Lawrence" <lawrencc@debian.org>, 448565@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Re: Bug#448565: apt-transport-debtorrent: not installable in unstable (amd64)

Date: Mon, 29 Oct 2007 20:42:32 -0700

tags 448565 +pending
thanks

On 10/29/07, Chris Lawrence <lawrencc@debian.org> wrote:
> Package: apt-transport-debtorrent
> Version: 0.1.1
> Severity: important
>
> The current apt supplies libapt-pkg-libc6.6-6-4.6, rather than -4.4 or
> -4.5; I believe a simple rebuild of apt-transport-debtorrent will fix
> the problem.

Hmmm, I'm not quite sure what to do here, as this is my first package
that has needed rebuilding for a library transition. I could rebuild
and upload it myself, but this seems like the kind of thing that
should be automated, especially since it's already been rebuilt for
ia64. I tried to schedule a binNMU on the debian-release list, which
you can see here:

http://lists.debian.org/debian-release/2007/10/msg00245.html

So I'm marking this as pending and hoping for the best. I can't seem
to find anything in the documentation about what specifically to do in
this situation, so if I'm mistaken or I've done something stupid
please let me know.

Thanks,
Cameron

Message #17 received at 448565-done@bugs.debian.org (full text, mbox, reply):

From: "Chris Lawrence" <lawrencc@debian.org>

To: "Cameron Dale" <camrdale@gmail.com>

Cc: 448565-done@bugs.debian.org

Subject: Re: Bug#448565: apt-transport-debtorrent: not installable in unstable (amd64)

Date: Tue, 30 Oct 2007 22:11:29 -0500

Version: 0.1.1+b1

On 10/29/07, Cameron Dale <camrdale@gmail.com> wrote:
> tags 448565 +pending
> thanks
>
> On 10/29/07, Chris Lawrence <lawrencc@debian.org> wrote:
> > Package: apt-transport-debtorrent
> > Version: 0.1.1
> > Severity: important
> >
> > The current apt supplies libapt-pkg-libc6.6-6-4.6, rather than -4.4 or
> > -4.5; I believe a simple rebuild of apt-transport-debtorrent will fix
> > the problem.
>
> Hmmm, I'm not quite sure what to do here, as this is my first package
> that has needed rebuilding for a library transition. I could rebuild
> and upload it myself, but this seems like the kind of thing that
> should be automated, especially since it's already been rebuilt for
> ia64. I tried to schedule a binNMU on the debian-release list, which
> you can see here:
>
> http://lists.debian.org/debian-release/2007/10/msg00245.html
>
> So I'm marking this as pending and hoping for the best. I can't seem
> to find anything in the documentation about what specifically to do in
> this situation, so if I'm mistaken or I've done something stupid
> please let me know.

Looks like it's taken care of; thanks!  I'm closing the report.


Chris

Send a report that this bug log contains spam.