On Tue, 4 Dec 2018 23:24:56 +0100, Stephen Kitt wrote:
> On Tue, 4 Dec 2018 19:09:22 +0100, Moritz Mühlenhoff wrote:
> > On Tue, Jan 16, 2018 at 09:05:15PM +0100, Stephen Kitt wrote:
> > > I’ve been meaning to look into all this further, but help is
> > > welcome.
> >
> > This is unfixed
Hi Moritz,
On Tue, 4 Dec 2018 19:09:22 +0100, Moritz Mühlenhoff wrote:
> On Tue, Jan 16, 2018 at 09:05:15PM +0100, Stephen Kitt wrote:
> > I’ve been meaning to look into all this further, but help is welcome.
>
> This is unfixed for quite a while and the upstream homepage now
> mentions "This
On Tue, Jan 16, 2018 at 09:05:15PM +0100, Stephen Kitt wrote:
>
> I’ve been meaning to look into all this further, but help is welcome.
This is unfixed for quite a while and the upstream homepage now
mentions "This is now - and has been for a long while - abandonware".
Shall we remove
Hi Raphaël,
On Tue, 16 Jan 2018 17:15:08 +0100, Raphael Hertzog
wrote:
> On Sun, 26 Jun 2016, Stephen Kitt wrote:
> > On Sun, 26 Jun 2016 12:23:30 +0200, Kurt Roeckx wrote:
> > > If you have problems making things work, feel free to contact us.
> >
> >
[ Copy to upstream author to know his plans wrt openssl 1.1
and to invite him to review the current patches ]
Hello Stephen,
On Sun, 26 Jun 2016, Stephen Kitt wrote:
> On Sun, 26 Jun 2016 12:23:30 +0200, Kurt Roeckx wrote:
> > If you have problems making things work, feel free
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
On Mon, Jun 27, 2016 at 09:02:56PM +0200, Stephen Kitt wrote:
>
> Right, that's the impression I'm getting too -- in particular for
> osssigncode, the associated SET_OF and i2d/d2i functionality appears to have
> changed (or rather, been replaced by other approaches)...
If you need help I
On Mon, 27 Jun 2016 20:21:58 +0200, Kurt Roeckx wrote:
> On Sun, Jun 26, 2016 at 10:31:13PM +0200, Kurt Roeckx wrote:
> > On Sun, Jun 26, 2016 at 10:15:44PM +0200, Stephen Kitt wrote:
> > > On Sun, 26 Jun 2016 22:07:28 +0200, Stephen Kitt
> > > wrote:
> > >
On Sun, Jun 26, 2016 at 10:31:13PM +0200, Kurt Roeckx wrote:
> On Sun, Jun 26, 2016 at 10:15:44PM +0200, Stephen Kitt wrote:
> > On Sun, 26 Jun 2016 22:07:28 +0200, Stephen Kitt wrote:
> > > On Sun, 26 Jun 2016 12:23:30 +0200, Kurt Roeckx wrote:
> > > > If you
On Sun, Jun 26, 2016 at 10:15:44PM +0200, Stephen Kitt wrote:
> On Sun, 26 Jun 2016 22:07:28 +0200, Stephen Kitt wrote:
> > On Sun, 26 Jun 2016 12:23:30 +0200, Kurt Roeckx wrote:
> > > If you have problems making things work, feel free to contact us.
> >
> >
On Sun, 26 Jun 2016 22:07:28 +0200, Stephen Kitt wrote:
> On Sun, 26 Jun 2016 12:23:30 +0200, Kurt Roeckx wrote:
> > If you have problems making things work, feel free to contact us.
>
> I've managed to fix most of the build issues, the remaining issue I'm
Hi Kurt,
On Sun, 26 Jun 2016 12:23:30 +0200, Kurt Roeckx wrote:
> If you have problems making things work, feel free to contact us.
I've managed to fix most of the build issues, the remaining issue I'm faced
with is the apparent disappearance of the STACK API
Source: osslsigncode
Version: 1.7.1-1
Severity: important
Control: block 827061 by -1
Hi,
OpenSSL 1.1.0 is about to released. During a rebuild of all packages using
OpenSSL this package fail to build. A log of that build can be found at:
13 matches
Mail list logo