Your message dated Tue, 29 Jul 2014 12:29:37 +0200
with message-id <20140729102937.ga22...@gaara.hadrons.org>
and subject line Re: Bug#640604: debsigs: installation fails: Verification on 
package /var/cache/apt/archives/debsigs_0.1.17_all.deb failed!
has caused the Debian Bug report #640604,
regarding debsigs: installation fails: Verification on package 
/var/cache/apt/archives/debsigs_0.1.17_all.deb failed!
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 ow...@bugs.debian.org
immediately.)


-- 
640604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debsigs
Version: 0.1.17
Severity: serious
User: debian...@lists.debian.org
Usertags: instest-20110825 instest

Hi,

While testing the installation of all packages in sid, I ran
into the following problem:

> Reading package lists...
> Building dependency tree...
> Reading state information...
> Starting
> Starting 2
> Done
> The following NEW packages will be installed:
> debsigs
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> 11 not fully installed or removed.
> Need to get 52.9 kB of archives.
> After this operation, 184 kB of additional disk space will be used.
> Get:1 http://localhost/debian/ sid/main debsigs all 0.1.17 [52.9 kB]
> Fetched 52.9 kB in 0s (969 kB/s)
> Authenticating /var/cache/apt/archives/debsigs_0.1.17_all.deb ...
> debsig: Origin Signature check failed. This deb might not be signed.
> 
> dpkg: error processing /var/cache/apt/archives/debsigs_0.1.17_all.deb 
> (--unpack):
> Verification on package /var/cache/apt/archives/debsigs_0.1.17_all.deb failed!
> configured to not write apport reports
> Errors were encountered while processing:
> /var/cache/apt/archives/debsigs_0.1.17_all.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)

The full build log is available from:
 http://people.debian.org/~lucas/logs/2011/08/25/debsigs.log

It is reproducible by installing your package in a clean chroot, using
the debconf Noninteractive frontend, and priority: critical.

This test was carried out using about 50 AMD64 nodes of the Grid'5000
platform.  Internet was not accessible from the nodes.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr             GPG: 1024D/023B3F4F |



--- End Message ---
--- Begin Message ---
Hi!

On Thu, 2014-06-12 at 01:41:56 +0200, Guillem Jover wrote:
> On Mon, 2011-09-05 at 21:53:59 +0200, Lucas Nussbaum wrote:
> > Package: debsigs
> > Version: 0.1.17
> > Severity: serious
> > User: debian...@lists.debian.org
> > Usertags: instest-20110825 instest
> 
> > > The following NEW packages will be installed:
> > > debsigs
> > > 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> > > 11 not fully installed or removed.
> > > Need to get 52.9 kB of archives.
> > > After this operation, 184 kB of additional disk space will be used.
> > > Get:1 http://localhost/debian/ sid/main debsigs all 0.1.17 [52.9 kB]
> > > Fetched 52.9 kB in 0s (969 kB/s)
> > > Authenticating /var/cache/apt/archives/debsigs_0.1.17_all.deb ...
> > > debsig: Origin Signature check failed. This deb might not be signed.
> > > 
> > > dpkg: error processing /var/cache/apt/archives/debsigs_0.1.17_all.deb 
> > > (--unpack):
> > > Verification on package /var/cache/apt/archives/debsigs_0.1.17_all.deb 
> > > failed!
> > > configured to not write apport reports
> > > Errors were encountered while processing:
> > > /var/cache/apt/archives/debsigs_0.1.17_all.deb
> > > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > 
> > The full build log is available from:
> >  http://people.debian.org/~lucas/logs/2011/08/25/debsigs.log
> 
> > It is reproducible by installing your package in a clean chroot, using
> > the debconf Noninteractive frontend, and priority: critical.
> 
> No, It's not, this bug report seems bogus to me. In the log from the
> URL the packages start to fail to install just after debsig-verify gets
> unpacked, so this cannot really be a bug in debsigs, it could be at
> most a bug in either debsig-verify or dpkg. But as mentioned in the
> subsequent replies dpkg has shipped with no-debsig in its default
> dpkg.cfg file for a while. So my assumption is that the chroot used
> had an empty or custom dpkg.cfg w/o that option enabled, i.e. a
> problem in the setup. And no, there's no need for any signing of the
> debsigs package at all, because those would get rejected at this point
> in time anyway.
> 
> As such this bug should be closed,  but I'll leave that to the
> maintainer. It's a pitty though that the package got removed from
> stable due to a bogus bug report. :(

Ok, closing now, so that the package can proceed to testing, and does
not miss the next release. Peter please let me know in case you disagree.

Thanks,
Guillem

--- End Message ---

Reply via email to