Processing of zvbi_0.2.35-3_kfreebsd-amd64.changes

2014-09-21 Thread Debian FTP Masters
zvbi_0.2.35-3_kfreebsd-amd64.changes uploaded successfully to localhost along with the files: libzvbi0_0.2.35-3_kfreebsd-amd64.deb libzvbi-dev_0.2.35-3_kfreebsd-amd64.deb libzvbi-common_0.2.35-3_all.deb libzvbi-doc_0.2.35-3_all.deb zvbi_0.2.35-3_kfreebsd-amd64.deb zvbi_0.2.35-3.dsc

zvbi_0.2.35-3_kfreebsd-amd64.changes ACCEPTED into unstable

2014-09-21 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 21 Sep 2014 17:56:38 + Source: zvbi Binary: libzvbi0 libzvbi-dev libzvbi-common libzvbi-doc zvbi Architecture: source kfreebsd-amd64 all Version: 0.2.35-3 Distribution: unstable Urgency: medium Maintainer:

Bug#731481: marked as done (zvbi: FTBFS on kfreebsd-*/hurd-i386 due to missing symbols)

2014-09-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Sep 2014 18:19:15 + with message-id e1xvlj9-0005ln...@franck.debian.org and subject line Bug#731481: fixed in zvbi 0.2.35-3 has caused the Debian Bug report #731481, regarding zvbi: FTBFS on kfreebsd-*/hurd-i386 due to missing symbols to be marked as done. This

Bug#754658: please display the package's description

2014-09-21 Thread Andrew Starr-Bochicchio
On Thu, Sep 18, 2014 at 6:50 AM, Raphael Hertzog hert...@debian.org wrote: On Tue, 16 Sep 2014, Paul Wise wrote: On Tue, Sep 16, 2014 at 7:40 PM, Ben Hutchings wrote: I think this fall back should not be used, except for packages that build a single binary. It results in nonsense like:

Bug#754658: please display the package's description

2014-09-21 Thread Stefano Zacchiroli
[ quoted text edit to add references ] On Tue, Sep 16, 2014 at 11:39:13PM +0800, Paul Wise wrote: 1) When only one binary package, use the description from it. 2) When more than one binary package but one has the same name as the source package, use the description from that. 3)

Bug#754658: please display the package's description

2014-09-21 Thread Paul Wise
On Mon, Sep 22, 2014 at 3:35 AM, Stefano Zacchiroli wrote: Uhm, interesting, I always thought the heuristic was slightly difference. It was always that way FYI. Is there an argument for not replacing point (3) above with: (3*) Otherwise, use the description of the first binary in