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

Bug#861686: marked as done (unblock: openssl/1.1.0e-2)



Your message dated Sat, 20 May 2017 05:54:00 +0000
with message-id <b254c1b9-8e9a-4c80-048d-189bf2e63db4@thykier.net>
and subject line Re: Bug#861686: unblock: openssl/1.1.0e-2
has caused the Debian Bug report #861686,
regarding unblock: openssl/1.1.0e-2
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.)


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

I prepared an update to the openssl about which I seek your guidance
whether it is approriate for Stretch or not.
After the rewrite/update of the debian/rules file we gained the dh_perl
command which adds a dependency on the perl package for the openssl
package. This was considered "okay" because `c_rehash' needs perl.
In #860254 two people complained that this change made the openssl
"quite hefty". The `c_rehash' script works also with perl-base instead
so I changed it (dh_perl -d). And since perl-base is essential the perl
dependency is all gone in the resulting openssl package.

In terms of full disclosure: We also have `tsget' (including a man page)
which is in a non-standard path (/usr/lib/ssl/misc/) and would need
`libwww-curl-perl' to work. This is something we never had and it is
misc because upstream puts it there. We don't want to add this
dependency to the packet (especially at this point in the cycle). For
post-Stretch we will decide how we handle it.

unblock openssl/1.1.0e-2

Sebastian
diff -Nru openssl-1.1.0e/debian/changelog openssl-1.1.0e/debian/changelog
--- openssl-1.1.0e/debian/changelog	2017-02-16 18:57:58.000000000 +0100
+++ openssl-1.1.0e/debian/changelog	2017-05-01 21:50:37.000000000 +0200
@@ -1,3 +1,9 @@
+openssl (1.1.0e-2) unstable; urgency=medium
+
+  * Make openssl depend on perl-base (Closes: #860254)
+
+ -- Sebastian Andrzej Siewior <sebastian@breakpoint.cc>  Mon, 01 May 2017 21:50:37 +0200
+
 openssl (1.1.0e-1) unstable; urgency=high
 
   * New upstream version
diff -Nru openssl-1.1.0e/debian/rules openssl-1.1.0e/debian/rules
--- openssl-1.1.0e/debian/rules	2017-02-16 18:57:19.000000000 +0100
+++ openssl-1.1.0e/debian/rules	2017-05-01 21:50:37.000000000 +0200
@@ -133,6 +133,9 @@
 	fi
 	dh_fixperms -a -X etc/ssl/private
 
+override_dh_perl:
+	dh_perl -d
+
 override_dh_makeshlibs:
 	#dpkg-gensymbols -Pdebian/libssl1.1/ -plibssl1.1 -c4
 	dh_makeshlibs -a --add-udeb="libcrypto1.1-udeb" -Xengines
@@ -140,7 +143,7 @@
 	# that breaks debootstrap in jessie (the current stable). This hack
 	# could be removed once stretch is stable and contains a fixed
 	# debootstrap, see #836525
-	sed -i 's@perl:Depends=perl:any@perl:Depends=perl@' debian/openssl.substvars
+	#sed -i 's@perl:Depends=perl:any@perl:Depends=perl@' debian/openssl.substvars
 
 override_dh_shlibdeps:
 	sed -i '/^udeb: libssl/s/libcrypto1.1-udeb/libssl1.1-udeb/' debian/libssl1.1/DEBIAN/shlibs

--- End Message ---
--- Begin Message ---
Cyril Brulebois:
> Sebastian Andrzej Siewior <sebastian@breakpoint.cc> (2017-05-18):
>> On 2017-05-07 16:39:00 [+0000], Niels Thykier wrote:
>>> Sebastian Andrzej Siewior:
>>>> uploaded and built on all releases architectures.
>>>
>>> Ack/RT unblock, CC'ing KiBi for a d-i ack.
>>
>> I don't want to rush or anything but in case it got forgotten, we are
>> still waiting for the d-i ack.
> 
> Thanks for prodding, I indeed missed the request initially…
> 
> No objections, and sorry for the lag.
> 
> 
> KiBi.
> 

Unblocked, thanks.

~Niels

--- End Message ---

Reply to: