On 2018-02-28 23:38:44 [+0100], Manuel A. Fernandez Montecelo wrote:
> Hello,
Hi,
> We need support in this package for RISC-V, to bootstrap the riscv64
> architecture.
Please be aware that we plan to get rid of this.
> I am attaching a patch that allowed me to cross-compile the package. I am
On 2018-03-03 16:02:37 [+0100], To sub...@bugs.debian.org wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: pu
> Tags: stretch
> Severity: normal
>
> Clamav upstream released 0.99.4 on 2018-03-01 fixing five CVEs [0]. I
> mention only two of them
On 2018-02-23 11:30:34 [+0100], Laurent Bigonville wrote:
> Hi,
>
> It seems that clamav support both (old) pcre and (new) pcre2
>
> Any reasons why clamav is still depending on this old version? Shouldn't
> it be switched to the new one?
I wanted to reply earler but didn't make it…
So clamav
control: clone -1 -2
control: reassign -2 libio-socket-ssl-perl 2.056-1
control: severity -2 normal
control: tags -2 patch
On 2018-02-27 21:52:23 [+0800], 積丹尼 Dan Jacobson wrote:
> Here is all you need to reproduce it:
>
> $ mech-dump https://mbasic.facebook.com/
> POST
>
On 2018-02-27 09:12:06 [+0800], 積丹尼 Dan Jacobson wrote:
> WWW::Mechanize: 500 Can't connect to mbasic.facebook.com:443...
You opened a grave bug and provide way less then enough information to
get this solved. It might look from your perspective that you provide
enough information but over here
On 2018-02-27 02:37:38 [+0800], 積丹尼 Dan Jacobson wrote:
> Package: libssl1.1
> Version: 1.1.1~~pre1-1
> Severity: grave
>
> SSL connect attempt failed error:141A90B5:SSL
> routines:ssl_cipher_list_to_bytes:no ciphers available
Can you give more information how to reproduce this? My first guess
control: reopen -1
Sebastian
On 2018-01-11 14:32:59 [+0100], To Alessandro Ghedini wrote:
> On 2018-01-10 23:57:56 [+], Alessandro Ghedini wrote:
> > Thoughts?
>
> If I understand Julien correctly in [0] he suggests a new soname (maybe
> with ssl suffix without bumping the 4 to 5) and a new package name.
>
> [0]
>
Source: grokmirror
Version: 1.0.0-1
Severity: important
I installed a Debian Stretch system, installed grokmirror on it and
then:
|$ grok-manifest -m /srv/www/manifest.js.gz -t /srv/git/
|Traceback (most recent call last):
| File "/usr/bin/grok-manifest", line 5, in
|from pkg_resources
On 2018-01-28 18:20:36 [+], Adam D. Barratt wrote:
>
> Please go ahead.
uploaded.
> Regards,
>
> Adam
Sebastian
On 2018-01-28 18:21:35 [+], Adam D. Barratt wrote:
> Please go ahead.
uploaded
> Regards,
>
> Adam
Sebastian
On 2018-01-27 02:07:51 [+0100], To sub...@bugs.debian.org wrote:
>diff -Nru clamav-0.99.2+dfsg/debian/libclamav7.symbols
>clamav-0.99.2+dfsg/debian/libclamav7.symbols
>--- clamav-0.99.2+dfsg/debian/libclamav7.symbols 2016-05-19
>18:40:20.0 +0200
>+++
On 27 January 2018 15:30:45 CET, Salvatore Bonaccorso wrote:
>So "the remaining CVEs were not address yet" part.
>
I was referring to the Stretch release. The fd bug is fixed but not the CVEs.
In the meantime I opened pu bugs for stable and oldstable.
Sebastian
s: #888484):
+- fixes for the following CVE's: CVE-2017-6418, CVE-2017-6420,
+ CVE-2017-12374, CVE-2017-12375, CVE-2017-12376, CVE-2017-12377,
+ CVE-2017-12378, CVE-2017-12379, CVE-2017-12380.
+ * Bump symbol version of cl_retflevel because CL_FLEVEL changed.
+
+ -- Sebastian Andrz
12375, CVE-2017-12376, CVE-2017-12377,
+ CVE-2017-12378, CVE-2017-12379, CVE-2017-12380.
+ * Bump symbol version of cl_retflevel because CL_FLEVEL changed.
+ * Cherry-pick patch from bb11549 to fix a temp file cleanup issue
+(Closes: #824196).
+
+ -- Sebastian Andrzej Siewi
control: fixed -1 0.99.3~beta2+dfsg-1
On 2018-01-26 09:35:25 [+], Rob N wrote:
> Package: clamav
> Version: 0.99.2+dfsg-0+deb8u2
> Severity: important
>
> 0.99.3 has been released, see
> http://blog.clamav.net/2018/01/clamav-0993-has-been-released.html.
>
> This fixed a number of overflow
Control: forwarded -1 https://github.com/openssl/openssl/pull/5169
Sebastian
Cornet <acor...@debian.org> from Uploaders. Thank you for
+all your work (Closes: #876953).
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Mon, 22 Jan 2018 23:28:55 +0100
+
bip (0.8.9-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru bip-0.8.9/de
Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Fri, 19 Jan 2018 20:22:08 +0100
Subject: [PATCH] opensmtpd: openssl 1.1 bits
Try to add OpenSSL 1.1 bits while it still should compile against 1.0.2.
Compile tested.
Signed-off-by: Sebastian Andrzej Siewior <sebast...@breakpo
On 19 January 2018 16:05:25 CET, Andreas Henriksson wrote:
>Would be great to hear from
>the maintainer if complicating the config/templates part is worth
>it to avoid the Depends on e2fsprogs!
Nope, I don't think so. I planned to add a depends on e2fsrogs.
>Regards,
On 2018-01-12 21:44:19 [+0100], Magnus Fromreide wrote:
> On Thu, Jan 11, 2018 at 07:07:45PM -0800, Bart Van Assche wrote:
> > On 12/23/17 15:17, Sebastian Andrzej Siewior wrote:
> > > added those, added a const and removed the "HAVE_EVP_MD_CTX_CREATE"
> >
On 2018-01-11 23:07:32 [+0200], Adrian Bunk wrote:
> On Thu, Jan 11, 2018 at 09:39:51PM +0100, Sebastian Andrzej Siewior wrote:
> >...
> > since everything not
> > shipped Debian wise would be suddenly linked againt libssl-1.1 while it
> > might have been compiled
On 2018-01-04 11:11:42 [-0500], Ryan Kavanagh wrote:
> Control: tag -1 + help
>
> Hi Sebastian,
Hi,
> Sorry for dropping the ball on this.
>
> On Fri, Oct 13, 2017 at 10:07:54PM +0200, Sebastian Andrzej Siewior wrote:
> > Could you retry with the following patch?
>
On 2018-01-11 14:54:26 [+0100], Ondřej Surý wrote:
> I commented at salsa.d.o, but for consistency, I am resending my comment here:
…
> The conflict here means that all r-depends will have to migrate at once, and
> absolutely no backports would be possible. I wish there would be a way where
>
On 2018-01-10 23:57:56 [+], Alessandro Ghedini wrote:
> > This whole transition looks pretty straightforward to me,
> > please let me know if there is anything where I could help.
>
> Following Adrian's comment, I prepated a patch that:
>
> * Renames *all* lincurl3* packages to libcurl4*
On 2018-01-07 14:59:54 [+0100], intrigeri wrote:
> Hi,
Hi,
> Francois Gouget:
> /etc/apparmor.d/usr.sbin.clamd profile, then.
>
> > So here is my feedback on the current configuration: […]
>
> Thanks for thinking this through. I'm not knowledgeable with ClamAV so
> I'll stick to general
as dependency of libsnmp-dev
+- drop the guard which enforced libssl 1.0.2
+- add -lcrypto back to pkg-config
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Sat, 23 Dec 2017 23:48:23 +0100
+
net-snmp (5.7.3+dfsg-1.7) unstable; urgency=medium
[ Niels Thykier ]
diff -N
pped HAVE_EVP_MD_CTX_CREATE + DESTROY and added a check for OpenSSL
version instead (and currently 1.0.2 is the only one supported).
BTS: https://bugs.debian.org/828449
Signed-off-by: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
---
apps/snmpusm.c | 43 ++
On 2017-12-17 18:35:17 [+0100], Hilko Bengen wrote:
> Control: tag -1 patch -fixed-upstream
>
> I don't see where the direct struct access issues have been fixed
> upstream, the source code snapshot available from
> http://www.kermitproject.org/ckdaily.html still has lots of those.
>
> I have
On 2017-12-17 19:32:52 [+0100], Hilko Bengen wrote:
> Control: tag -1 patch
>
> Hi,
>
> here's a patch that fixes the OpenSSL-1.1-related FTBFS for sslsniff.
>
> I'd appreciate a review of the patch.
It is not back compatible with openssl 1.0.2
>Index: sslsniff/SessionCache.cpp
On 2017-12-16 12:55:35 [+], deb...@fau.xxx wrote:
> Upstream are aware of this issue, but quite stuck on it, by the look of
> it:
>
> * https://github.com/netty/netty-tcnative/issues/263
> * https://github.com/netty/netty/issues/6320
>
> This is going to be a problem, as netty-tcnative
On 2017-12-14 01:58:25 [+0100], Hilko Bengen wrote:
> Control: tag -1 patch
>
> I have prepared patches for ssldump to
>
> (1) recognize OpenSSL 1.1 at configure time
>Index: ssldump/configure.in
>===
>--- ssldump.orig/configure.in
Source: crash
Version: 7.1.7-1
Severity: serious
Tags: patch
The utility is probably working in its current shape for older kernel,
but not for newer:
|$ crash ../build-RT/vmlinux mem2
|
|crash 7.1.7
|Copyright (C) 2002-2016 Red Hat, Inc.
|Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
On 2017-12-13 08:33:02 [+0100], Andreas Tille wrote:
> Hi Sebastian,
Hi Andreas,
> it would be nice if you could answer the question below. Otherwise
> we would set the bug to wontfix for the moment.
somehow this email never reached me or I skipped it by accident.
> Thank you
>
>
Source: neomutt
Version: 20171208+dfsg.1-1
Severity: Important
I tried
neomutt -a $file
it then prompts for To:, Subject: and opens $EDITOR. After that I tell
it send. Neomutt saves the email in the `Sent' folder and crashes then:
|-- NeoMutt: Compose [Approx. msg size: 15K Atts:
On 2017-11-28 21:15:29 [+0100], To YunQiang Su wrote:
> control: forwarded -1 https://github.com/openssl/openssl/pull/4813
> On 2017-11-18 05:45:29 [+0800], YunQiang Su wrote:
> > If you can help to forward, it will be great.
>
> done.
Upstream as of 1.1.1 has R6 support the asm part and that
control: forwarded -1 https://github.com/openssl/openssl/pull/4813
On 2017-11-18 05:45:29 [+0800], YunQiang Su wrote:
> If you can help to forward, it will be great.
done.
Sebastian
Source: cl-plus-ssl
Version: 20170630-1
Severity: serious
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans
Control: block 871056 by -1
Please migrate to libssl-dev in the Buster cycle. I am very sorry for
this late report but this package was never on
Package: pyelliptic
Version: 1.5.7-1.1
Severity: serious
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans
Control: block 871056 by -1
Please migrate to libssl-dev in the Buster cycle. I am very sorry for
this late report but this package was never on my
Package: telepathy-qt
Version: 0.9.6.1-6.1
Severity: serious
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans
Control: block 871056 by -1
Please migrate to libssl-dev in the Buster cycle. I am very sorry for
this late report but this package was never
On 2017-11-23 17:09:09 [+0200], Adrian Bunk wrote:
> On Thu, Nov 23, 2017 at 01:57:58PM +, Ian Jackson wrote:
> > 2. For the reason just mentioned, it might be a good idea to put in a
> >Breaks against old versions of packages using
> >CURLOPT_SSL_CTX_FUNCTION. However, (a) I am not
Package: nim
Version: 0.17.2-1
Severity: serious
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans
Control: block 871056 by -1
Please migrate to libssl-dev in the Buster cycle. I am very sorry for
this late report but this package was never on my list.
On 2017-10-12 23:44:24 [+0200], To 858...@bugs.debian.org wrote:
Hi,
> this is a remainder about the openssl transition [0]. We really want to
> remove libssl1.0-dev from unstable for Buster. I will raise the severity
> of this bug to serious in a month. Please react before that happens.
is
On 2017-11-21 14:21:32 [+0100], Christoph Anton Mitterer wrote:
> Hi.
Hi,
> With the lastest version the package fails to upgrade:
sorry for that. Not sure why I didn't catch this during testing. Fix is
comming… This is mostly a note to myself that I need to ping the systemd
people and figure out
control: tags -1 pending
On 2017-08-27 15:53:03 [+0200], Sylvestre Ledru wrote:
> Hello,
Hi,
> Currently, we have 6 versions of the llvm toolchain in the archive.
> I would like to move to 3 versions (4.0, 5.0 and snapshot, aka 6.0)
>
> Could you please update your package to use 4.0 (or,
On 2017-11-17 22:45:26 [+0800], YunQiang Su wrote:
> +--- a/Configurations/10-main.conf
> b/Configurations/10-main.conf
> +@@ -736,6 +736,31 @@ sub vms_info {
> + shared_ldflag=> add("-mabi=64"),
> + multilib => "64",
> + },
> ++"linux-mips32r6" => {
> ++
On 2017-11-15 03:46:46 [+0200], Bob Bib wrote:
> Dear Maintainer,
Hi Bob,
>
> I've tried reconfiguring clamav-freshclam,
> to disable the daemon:
>
> # dpkg-reconfigure clamav-freshclam
> ...
> Virus database update method: manual
> ...
>
> The reconfiguration process ends up with database
control: tags -1 pending
On 2017-11-13 20:35:29 [+0200], Vincas Dargis wrote:
> I have edited Exim4 configuration as READE.Debian.gz suggested:
>
>
> ```
>Then add the following to your data time acl:
>
>deny message = This message contains a virus: ($malware_name) please scan
> your
control: tags -1 patch
control: forwarded -1
http://lists.xiph.org/pipermail/icecast-dev/2017-November/002641.html
Please find attached the patch.
Sebastian
>From 01fafc449f0de56743d08e7976933c49e2915bfa Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc
On 2017-10-21 16:37:14 [+0200], Denis Briand wrote:
> Hello Sebastian,
Hi Denis,
> Pgadmin3 is no longer supported by upstream team and I haven't enought skills
> in openssl lib to fix this bug.
> Feel free to raise the bug severity to prevent pgadmin3 to be in buster.
>
> In a marvelous world
: #859226).
+
+ -- Sebastian Andrzej Siewior <sebast...@breakpoint.cc> Mon, 13 Nov 2017 21:31:11 +0100
+
m2ext (0.1-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru m2ext-0.1/debian/control m2ext-0.1/debian/control
--- m2ext-0.1/debian/control 2017-02-05 14:54:51.0
g maybe more
> obvious and with more documentation.
okay. This time with the patch attached…
> > > M E Andersson, maintainer of netkit-ftp-ssl
Sebastian
>From 48939773820c9fb2c48ec444b156099d1bae Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
control: tags - patch
On 2017-11-10 14:45:52 [+0100], To Mats Erik Andersson wrote:
> On 2017-11-09 18:54:42 [+0100], Mats Erik Andersson wrote:
> > than a few kilobytes. Netkit-ftl-ssl achieves this by
> > use of the function SSL_copy_seesion_id(). This presumably
> > is a legacy function from
On 2017-11-09 18:54:42 [+0100], Mats Erik Andersson wrote:
> than a few kilobytes. Netkit-ftl-ssl achieves this by
> use of the function SSL_copy_seesion_id(). This presumably
> is a legacy function from the time of SSLeay.
I can't find this in SSL_copy_seesion_id() in the source in
On 2017-11-10 00:48:34 [+0100], Carsten Leonhardt wrote:
> Sebastian Andrzej Siewior <sebast...@breakpoint.cc> writes:
> Hi,
Hi,
> > oh boy. Yes, definitely. Something like that in the attached patch?
> > (this time not even compile tested).
>
> adding that pa
, definitely. Something like that in the attached patch?
(this time not even compile tested).
> __Martin
Sebastian
>From 7eb1f97ca3a154818ff42e3259899fbc94140fbc Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Thu, 9 Nov 2017 21:55:20 +0100
ep 17 00:00:00 2001
From: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Date: Wed, 8 Nov 2017 14:37:31 +0100
Subject: [PATCH 1/5] crypto: remove support for ancient openssl
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
OpenSSL 1.0.2 is still
control: forwarded -1 https://github.com/openssl/openssl/pull/4547
On 2017-10-13 14:15:13 [+0100], Toni Mueller wrote:
> Hi Sebastian,
Hi Toni,
> that's also one way to go about it, but while we are at it, can we
> change the "should" to a "must"?
The chapter just vanished. See the pull req.
On 2017-10-17 11:51:19 [+0100], Colin Watson wrote:
> > I didn't even figure out if they want to alter their code or not.
>
>
> https://lists.mindrot.org/pipermail/openssh-unix-dev/2017-October/036370.html
let me check.
> I don't see any benefit in conducting a discussion in which we assume
On 2017-10-16 17:29:09 [+0100], Colin Watson wrote:
> [I won't quote everything, but people replying to this should probably
> read the bug log in the BTS first.]
It was a lot to read and "they" stumbled over details.
> While there does exist a skeletal compatibility layer linked from the
>
On 2017-10-15 22:06:35 [+0100], Colin Watson wrote:
> What? You've entirely misunderstood me. OpenSSH upstream *already*
This got cleared up in the meantime.
> > I've been pointed out to another way to go I hope you like it: There is
> > PKIX-SSH [0].
>
> I dislike the idea of switching to a
On 2017-10-13 15:30:13 [+0100], Colin Watson wrote:
> That's basically the last I recall hearing, and that they were trying to
> put pressure on OpenSSL upstream.
I pinged upstream about the situation. I'm not sure if I made it worse
or not but I read something like "adding glue code to fetch and
On 2017-10-13 11:21:03 [-0400], Ryan Kavanagh wrote:
> Hi Sebastian,
Hi Ryan,
> To clarify: I wrote a patch that I believe ports opensmtpd to OpenSSL
> 1.1, but with no backwards compatibility for 1.0. It has not been
> applied (nor reviewed) by upstream, because upstream needs to cope with
>
On 2017-10-13 08:49:21 [+0100], Colin Tuckley wrote:
> > this is a remainder about the openssl transition [0]. We really want to
> > remove libssl1.0-dev from unstable for Buster. I will raise the severity
> > of this bug to serious in a month. Please react before that happens.
>
> I've talked to
On 2017-10-13 11:44:21 [+0300], Boris Pek wrote:
> Hi,
Hi,
> Just for note. OpenSSL >= 1.1 will be supported in a next stable release of
> EiskaltDC++ (2.4.0) which is going to be released soon. I will update the
> package once this happens. But updated package should go through NEW queue
> due
On 2017-10-13 08:56:06 [+0200], Carsten Leonhardt wrote:
> Hi Sebastian,
Hi Carsten,
> Upstream does not see a pressing need because OpenSSL version 1.0.2 is
> supported until 2019-12-31 - significantly longer than 1.0.2.
and then do the port on new years eve :)
> Are there any other
On 2017-10-13 09:06:36 [+0800], Boyuan Yang wrote:
> Pidgin-openfetion was hosted on code.google.com, which was obsoleted long ago
> without upstream activity. Pidgin-openfetion package in Debian is also
> orphaned.
>
> For QA purpose, I suggest we remove this package from Debian Archive. If
>
On 2017-10-13 01:21:35 [+0100], Colin Watson wrote:
> I'm sorry, but reminders or not, at this time I do not intend to move to
> 1.1 in advance of upstream; I consider that far too risky a change (it's
> a ~4000-line patch to security-critical code, IIRC). If you want to
> lobby for this, you
On 2017-10-12 18:33:40 [-0400], Ryan Kavanagh wrote:
> Hi Sebastian,
Hi Ryan,
> This is being tracked upstream. I made initial efforts to port it to
> OpenSSL 1.1 and sent them upstream (see second comment in the upstream
> bug), but things are complicated by opensmtpd needing to be able to cope
On 2017-10-12 14:49:31 [+0100], Toni Mueller wrote:
> Package: openssl
> Version: 1.1.0f-3
> Severity: normal
> Tags: security upstream
>
>
> Hi,
>
> the genrsa(1) manpage suggests that 1024 bits may be a typical key size
> for RSA keys. I have to object - the Debian project deprecated 1024 bit
On 2017-10-12 09:40:08 [-0400], Jeremy Bicha wrote:
> I was wrong in my last email.
>
> But…SSLv23_client_method() is deprecated according to the manpage. Use
> TLS_client_method() instead.
This is what I suggested with the ifdef around to be able to work with
older openssl if the change goes
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
Hi,
this is a remainder about the openssl transition [0]. We really want to
remove libssl1.0-dev from unstable for Buster. I will raise the severity
of this bug to serious in a month. Please react before that happens.
[0] https://bugs.debian.org/871056#55
Sebastian
701 - 800 of 1856 matches
Mail list logo