Mikkel Krautz:
> On Sun, Mar 13, 2016 at 9:20 PM, Chris Knadle
> wrote:
>> Mikkel Krautz:
>>> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
I would also like to say again that if we can somehow see in the
meta data that they are using libssl, they would get rebuild at
the sa
Kurt Roeckx:
> On Mon, Mar 14, 2016 at 10:25:30PM +0100, Mikkel Krautz wrote:
>> Quoting Kurt Roeckx:
>>> I would also like to say again that if we can somehow see in the
>>> meta data that they are using libssl, they would get rebuild at
>>> the same time and you wouldn't get into this situation t
Mikkel Krautz:
> On Sun, Mar 13, 2016 at 9:20 PM, Chris Knadle
wrote:
>> Mikkel Krautz:
>>> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
I would also like to say again that if we can somehow see in the
meta data that they are using libssl, they would get rebuild at the
same
On Mon, Mar 14, 2016 at 10:25:30PM +0100, Mikkel Krautz wrote:
> Quoting Kurt Roeckx:
> > I would also like to say again that if we can somehow see in the
> > meta data that they are using libssl, they would get rebuild at
> > the same time and you wouldn't get into this situation that they
> > are
On Sun, Mar 13, 2016 at 6:20 PM, Chris Knadle wrote:
> Mikkel Krautz:
>> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
>>> I would also like to say again that if we can somehow see in the
>>> meta data that they are using libssl, they would get rebuild at
>>> the same time and you wouldn't
On Sun, Mar 13, 2016 at 9:20 PM, Chris Knadle wrote:
> Mikkel Krautz:
>> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
>>> I would also like to say again that if we can somehow see in the
>>> meta data that they are using libssl, they would get rebuild at
>>> the same time and you wouldn't
Mikkel Krautz:
> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
>> I would also like to say again that if we can somehow see in the
>> meta data that they are using libssl, they would get rebuild at
>> the same time and you wouldn't get into this situation that they
>> are using a different v
Chris Knadle:
> Mikkel Krautz:
>[...]
> When a new OpenSSL comes down containing a library rename, the Mumble #2124
> patch will disallow multiple libssl/libcrypto load and Mumble will break.
> Besides Mumble not being functional, the broken behavior deletes the user's
> SSL key used with Mumble an
Mikkel Krautz:
> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
>> I would also like to say again that if we can somehow see in the
>> meta data that they are using libssl, they would get rebuild at
>> the same time and you wouldn't get into this situation that they
>> are using a different v
On Sun, Mar 13, 2016 at 4:18 PM, Kurt Roeckx wrote:
> On Sun, Mar 13, 2016 at 03:55:54PM +0100, Mikkel Krautz wrote:
>> On Sun, Mar 13, 2016 at 3:36 PM, Kurt Roeckx wrote:
>> > On Sun, Mar 13, 2016 at 03:28:30PM +0100, Mikkel Krautz wrote:
>> >> A tiny bit of follow-up to my suggestion of using "
On Sun, Mar 13, 2016 at 03:55:54PM +0100, Mikkel Krautz wrote:
> On Sun, Mar 13, 2016 at 3:36 PM, Kurt Roeckx wrote:
> > On Sun, Mar 13, 2016 at 03:28:30PM +0100, Mikkel Krautz wrote:
> >> A tiny bit of follow-up to my suggestion of using "-openssl-linked" for Qt:
> >>
> >> In the earlier Debian b
On Sun, Mar 13, 2016 at 3:36 PM, Kurt Roeckx wrote:
> On Sun, Mar 13, 2016 at 03:28:30PM +0100, Mikkel Krautz wrote:
>> A tiny bit of follow-up to my suggestion of using "-openssl-linked" for Qt:
>>
>> In the earlier Debian bug that was linked by Chris, it was brought up
>> that an application may
On Sun, Mar 13, 2016 at 03:28:30PM +0100, Mikkel Krautz wrote:
> A tiny bit of follow-up to my suggestion of using "-openssl-linked" for Qt:
>
> In the earlier Debian bug that was linked by Chris, it was brought up
> that an application may use QtNetwork without using SSL, and therefore
> might no
On Sun, Mar 13, 2016 at 3:22 PM, Mikkel Krautz wrote:
> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
>> I would also like to say again that if we can somehow see in the
>> meta data that they are using libssl, they would get rebuild at
>> the same time and you wouldn't get into this situat
On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
> I would also like to say again that if we can somehow see in the
> meta data that they are using libssl, they would get rebuild at
> the same time and you wouldn't get into this situation that they
> are using a different version.
My vote is a
On Sun, Mar 13, 2016 at 01:57:23PM +0100, Mikkel Krautz wrote:
> On Sat, Mar 12, 2016 at 8:06 PM, Kurt Roeckx wrote:
> > On Sat, Mar 12, 2016 at 04:56:22PM +, Chris Knadle wrote:
> >> > Maybe Qt should have some way to indicate what version it's build
> >> > against so that we can binNMU it wi
On Sat, Mar 12, 2016 at 11:38 AM, Kurt Roeckx wrote:
> On Sat, Mar 12, 2016 at 01:04:12AM +, Chris Knadle wrote:
>> Discussions with mumble upstream about this problem have continued, and the
>> situation seems much more muddied than I previously knew. This is likely
>> not an OpenSSL issue p
On Sat, Mar 12, 2016 at 8:06 PM, Kurt Roeckx wrote:
> On Sat, Mar 12, 2016 at 04:56:22PM +, Chris Knadle wrote:
>> > Maybe Qt should have some way to indicate what version it's build
>> > against so that we can binNMU it with all the other packages? Or
>> > maybe Qt should just link against
On Sat, Mar 12, 2016 at 04:56:22PM +, Chris Knadle wrote:
> > Maybe Qt should have some way to indicate what version it's build
> > against so that we can binNMU it with all the other packages? Or
> > maybe Qt should just link against it, instead of doing dlopen()?
>
> Mumble upstream looked
Kurt Roeckx:
> On Sat, Mar 12, 2016 at 01:04:12AM +, Chris Knadle wrote:
>> Discussions with mumble upstream about this problem have continued, and the
>> situation seems much more muddied than I previously knew. This is likely
>> not an OpenSSL issue per se but rather seems to be an issue whe
On Sat, Mar 12, 2016 at 01:04:12AM +, Chris Knadle wrote:
> Discussions with mumble upstream about this problem have continued, and the
> situation seems much more muddied than I previously knew. This is likely
> not an OpenSSL issue per se but rather seems to be an issue whenever OpenSSL
> sh
Discussions with mumble upstream about this problem have continued, and the
situation seems much more muddied than I previously knew. This is likely
not an OpenSSL issue per se but rather seems to be an issue whenever OpenSSL
ships renamed libssl and libcrypto files for soname changes.
Mumble lin
Kurt Roeckx:
> On Mon, Nov 09, 2015 at 09:36:46PM +, Chris Knadle wrote:
>> Kurt Roeckx:
>>> On Mon, Nov 09, 2015 at 07:58:30PM +, Chris Knadle wrote:
Everybody dealing with the mumble bug agrees that SSL should be initialized
before making SSL calls -- the reason I opened #8
On Mon, Nov 09, 2015 at 09:36:46PM +, Chris Knadle wrote:
> Kurt Roeckx:
> > On Mon, Nov 09, 2015 at 07:58:30PM +, Chris Knadle wrote:
> >>
> >> Everybody dealing with the mumble bug agrees that SSL should be initialized
> >> before making SSL calls -- the reason I opened #804487 is to try
Kurt Roeckx:
> On Mon, Nov 09, 2015 at 07:58:30PM +, Chris Knadle wrote:
>>
>> Everybody dealing with the mumble bug agrees that SSL should be initialized
>> before making SSL calls -- the reason I opened #804487 is to try to figure
>> out /what/ caused mumble_1.2.10-2+b1 to break, when mumble_
On Mon, Nov 09, 2015 at 07:58:30PM +, Chris Knadle wrote:
>
> Everybody dealing with the mumble bug agrees that SSL should be initialized
> before making SSL calls -- the reason I opened #804487 is to try to figure
> out /what/ caused mumble_1.2.10-2+b1 to break, when mumble_1.2.10-2 works.
>
Kurt Roeckx:
> On Sun, Nov 08, 2015 at 10:26:42PM +, Chris Knadle wrote:
>> Package: openssl
>> Version: 1.0.2d-3
>> Severity: serious
>>
>> Greetings.
>>
>> I'm marking this bug as 'serious' because the upgrade to 1.0.2d-3 seems to
>> have broken mumble, though it's unclear why that would be.
On Sun, Nov 08, 2015 at 10:26:42PM +, Chris Knadle wrote:
> Package: openssl
> Version: 1.0.2d-3
> Severity: serious
>
> Greetings.
>
> I'm marking this bug as 'serious' because the upgrade to 1.0.2d-3 seems to
> have broken mumble, though it's unclear why that would be.
>
> After a binNMU w
Package: openssl
Version: 1.0.2d-3
Severity: serious
Greetings.
I'm marking this bug as 'serious' because the upgrade to 1.0.2d-3 seems to
have broken mumble, though it's unclear why that would be.
After a binNMU with openssl_1.0.2d-3 mumble and mumble-server are unable to
find the available lis
29 matches
Mail list logo