Your message dated Tue, 18 Nov 2014 19:48:19 +0000 with message-id <20141118194819.GO6216@lupin.home.powdarrmonkey.net> and subject line Re: Bug#769122: unblock: qpid-proton/0.7-8 has caused the Debian Bug report #769122, regarding unblock: qpid-proton/0.7-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 769122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769122 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: qpid-proton/0.7-8
- From: "Darryl L. Pierce" <mcpierce@gmail.com>
- Date: Tue, 11 Nov 2014 09:33:25 -0500
- Message-id: <[🔎] 20141111143325.4637.50065.reportbug@mcp-debian.usersys.redhat.com>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock Please unblock package qpid-proton The reason it failed to build from source was due to it having a dependency on libsslcommon2-dev. However, this dependency can instead by met by libssl-dev which does exist in Jessie. unblock qpid-proton/0.7-8 -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: "Darryl L. Pierce" <mcpierce@gmail.com>, 769122-done@bugs.debian.org
- Subject: Re: Bug#769122: unblock: qpid-proton/0.7-8
- From: Jonathan Wiltshire <jmw@debian.org>
- Date: Tue, 18 Nov 2014 19:48:19 +0000
- Message-id: <20141118194819.GO6216@lupin.home.powdarrmonkey.net>
- In-reply-to: <[🔎] 20141116133707.GI6216@lupin.home.powdarrmonkey.net>
- References: <[🔎] 20141111143325.4637.50065.reportbug@mcp-debian.usersys.redhat.com> <[🔎] 20141111203013.GB21455@lupin.home.powdarrmonkey.net> <[🔎] 20141111223617.GA4436@mcpierce-laptop.redhat.com> <[🔎] 20141112124711.GL13253@mraw.org> <[🔎] 20141112154557.GA3989@mcpierce-laptop.rdu.redhat.com> <[🔎] 20141112202404.GJ21455@lupin.home.powdarrmonkey.net> <[🔎] 20141112215337.GB3989@mcpierce-laptop.rdu.redhat.com> <[🔎] 20141115105500.GC6216@lupin.home.powdarrmonkey.net> <[🔎] 20141115123357.GH4236@mcpierce-laptop.redhat.com> <[🔎] 20141116133707.GI6216@lupin.home.powdarrmonkey.net>
On Sun, Nov 16, 2014 at 01:37:07PM +0000, Jonathan Wiltshire wrote: > Control: tag -1 - moreinfo + confirmed > > On Sat, Nov 15, 2014 at 07:33:57AM -0500, Darryl L. Pierce wrote: > > On Sat, Nov 15, 2014 at 10:55:00AM +0000, Jonathan Wiltshire wrote: > > > The debdiff doesn't show your adding the python helper? > > > > I had sent the wrong one, before I had added the python helper. I sent a > > second email but not sure why it's not attached to the bug. Here is the > > correct one: > > Ok, that looks fine apart from getting rid of the now-empty lintian > override file. It was sponsored; unblocked. -- Jonathan Wiltshire jmw@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51Attachment: signature.asc
Description: Digital signature
--- End Message ---