[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#683334: marked as done (unblock: libcrypt-ssleay-perl/0.58-2 (pre-approval request))

Your message dated Sat, 4 Aug 2012 23:08:27 +0200
with message-id <20120804210827.GA29819@elende>
and subject line Re: Bug#683334: unblock: libcrypt-ssleay-perl/0.58-2 (pre-approval request)
has caused the Debian Bug report #683334,
regarding unblock: libcrypt-ssleay-perl/0.58-2 (pre-approval request)
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.)


-- 
683334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683334
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: freeze-exception

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear Release Team

libcrypt-ssleay-perl has a missing dependency on
liblwp-protocol-https-perl, which is tracked in bugreport #622917[1].
There is also an upstream bugreport[2].

 [1]: http://bugs.debian.org/622917
 [2]: https://rt.cpan.org/Public/Bug/Display.html?id=73754

The problem was first detected in checkgmail which failed with "Error:
500 Can't connect to www.google.com:443 (Crypt-SSLeay can't verify
hostnames)".

One could probably solve this by adding only libio-socket-ssl-perl,
but upstream fixed that in [2] by adding liblwp-protocol-https-perl
requirements.

Note, I just first would like to get a pre-approval, if the change is
okay to be passed to wheezy.

Attached is the debdiff against 0.58-1 currently in wheezy and
unstable.

I furthermore checked that the package should be installable in wheezy
(only amd64 checked), so that we can upload to unstable and let it
migrate to testing.

Does this fit the rules for wheezy freeze-exception requests, as
libcrypt-ssleay-perl has Priority: optional?

I don't see any drawbacks (at the moment at least), by adding the
dependency.

unblock libcrypt-ssleay-perl/0.58-2

Many thanks for your release work!

Regards,
Salvatore

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCgAGBQJQFvLwAAoJEHidbwV/2GP+8IIQAM7QryKid/pnVcf3rtIc2d23
yBUT8bBYbknKFpJHGFOKI4Q1loHRvVLokJnOPrD+/ebYd8vcDyMUDD2JaCo4PB2c
hMEzaJ9jFABUngw0EqDeHrVQEx0xY0fyXHdpT3wxrbjQ2msnqd++nGAIrgHjWyIO
SwCmpVADYZt+XT6K67lXrdglGT6ZE+KIWyTgQmKv5Cynqm285uVqQGUR3P8Cu7dr
LvplTFFrOkKGnOPhdoObRGFgPPi364FZY8wepmVA9WLGWy1XMUPQ3+pcwLaMHlwP
BQ5yHQUHCSBAhfYbSOVQfRbKiBOAOpvLb5EaHfjunmQMx+UqtR1kbTIGndABLwjZ
yJSaCyGGxe1S6SGyUCSy+w8cgC0Nt6RcOijGkKPhE35WvDXNYLdNQf8B4F2dgIHq
Z3ELp8Qnsb27U2RLGL0y7sb2Td5L2pTDrt5p8lETbOaYNnm92M49bzs6lIj+CY0V
CDte7WIqmXQIH163sGkYW0mb+jjau3SAqkcOfl/Prw1Kh8b6m5PWZVDWeW0e/eZC
4j3owbj9inzCMcYPM46K5bfNFcWrR9jTy51VewaVUaA+jJTZ4nPlGrNVH8gSdzMW
+bC3NK+RDJATwmDmy0B3OOPQ0X4ubWL6BYL4EStMx35zhTAg4wuc2kYIWQgndtDC
dxlYzU/LwrdIXQWpX8qD
=HEhT
-----END PGP SIGNATURE-----

diff -Nru libcrypt-ssleay-perl-0.58/debian/changelog libcrypt-ssleay-perl-0.58/debian/changelog
--- libcrypt-ssleay-perl-0.58/debian/changelog	2012-01-03 00:36:38.000000000 +0100
+++ libcrypt-ssleay-perl-0.58/debian/changelog	2012-07-30 22:14:49.000000000 +0200
@@ -1,3 +1,12 @@
+libcrypt-ssleay-perl (0.58-2) unstable; urgency=low
+
+  * Team upload.
+  * Add (build-)dependency for LWP::Protocol::https.
+    Add missing (Build-)Depends(-Indep) on liblwp-protocol-https-perl.
+    See https://rt.cpan.org/Public/Bug/Display.html?id=73754 (Closes: #622917)
+
+ -- Salvatore Bonaccorso <carnil@debian.org>  Mon, 30 Jul 2012 22:14:44 +0200
+
 libcrypt-ssleay-perl (0.58-1) unstable; urgency=low
 
   * Takeover for the Debian Perl Group with maintainer's permisson
diff -Nru libcrypt-ssleay-perl-0.58/debian/control libcrypt-ssleay-perl-0.58/debian/control
--- libcrypt-ssleay-perl-0.58/debian/control	2012-01-03 00:36:38.000000000 +0100
+++ libcrypt-ssleay-perl-0.58/debian/control	2012-07-30 22:14:49.000000000 +0200
@@ -7,6 +7,7 @@
 Vcs-Git: git://git.debian.org/pkg-perl/packages/crypt-ssleay.git
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/crypt-ssleay.git
 Build-Depends: debhelper (>= 8), perl,
+ liblwp-protocol-https-perl,
  libssl-dev,
  libtest-pod-coverage-perl,
  libtest-pod-perl,
@@ -15,7 +16,8 @@
 
 Package: libcrypt-ssleay-perl
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, ${perl:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, ${perl:Depends},
+ liblwp-protocol-https-perl
 Description: OpenSSL support for LWP
  This perl module provides support for the HTTPS protocol under LWP, so
  that an LWP::UserAgent can make HTTPS GET & HEAD & POST requests. Please

--- End Message ---
--- Begin Message --- 
Hi Philipp

On Tue, Jul 31, 2012 at 05:15:10PM +0200, Philipp Kern wrote:
> On Mon, Jul 30, 2012 at 10:47:49PM +0200, Salvatore Bonaccorso wrote:
> > Note, I just first would like to get a pre-approval, if the change is
> > okay to be passed to wheezy.
> > 
> > Attached is the debdiff against 0.58-1 currently in wheezy and
> > unstable.
> 
> ACK.

After the arguing with Jakub Wilk who helped a lot on this issue to
clarify I would say let's close this request.

I'm sorry for the additional work I caused to review this.

Regards,
Salvatore

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: