On Sat, Mar 13, 2021 at 04:21:02PM +0100, Dennis Filder wrote:
> Good, I just tried it with linphone 4.4.21-2, linphone-desktop 4.2.5-3
> and soci 4.0.1-5 and chat message history restoration works nicely.
That's great to hear! Glad you got it sorted out.
Hi Dennis,
I did respond to your email on the 7th. Maybe it wound up in your spam
folder?
At any rate, apologies for the delay - things have been a bit busy the
past several days.
I'm currently building/testing the data type patch, and hope to upload
it to unstable today. I'll file the
Hi,
> Have you reached out to the SOCI maintainer in private already? I don't
> see a bug report on this. If we can get a targeted fix uploaded for this
> within the next days (next step of the freeze is on March 10th, with a
> migration time of 10 days right now) I will attempt to push through a
Hi,
I've uploaded xalan 1.12 to unstable. If you would like me to NMU
xml-security-c with the necessary changes (attached to 977568), I would
be happy to do so.
Best regards,
Bill
--
GPG: 5CDD 0C9C F446 BC1B 2509 8791 1762 E022 7034 CF84
Hi,
Thanks for your report.
I hope to address these issues next week.
Best regards,
Bill
It appears that the needed changes are located in Salsa [1], and that the
release was prepared but not uploaded (since it's nowhere to be found).
This package is team maintained, and since it's not clear to me if the
rest of the team is aware of this issue, I'm CC'ing the team address in
this
Package: python3-django-casclient
Version: 1.2.0-2
Severity: grave
Tags: upstream patch
Due to middleware API changes in Django 1.10, django-cas-client 1.2 no
longer works (fails with an unhandled exception). This currently
effects stable, testing, and unstable (oldstable used django 1.7). So
The fix for stable has been uploaded to proposed-updates, and should be
included in the next point release. Oldstable was not affected by this
bug, so nothing was needed there.
My apologies for this - this is my fault.
I'm about to upload the fix to unstable, and will submit an update for
for stable and oldstable to hopefully be included in the next point
release.
Bill
While this is fixed for unstable/testing, the security team has informed
me that there will be no DSA for this issue for stable/oldstable.
As such, I'm reopening this until stable/oldstable can be updated via a
point release.
I've prepared a new package and uploaded it to mentors:
https://mentors.debian.net/debian/pool/main/x/xerces-c/xerces-c_3.1.4+debian-2.dsc
If someone wants to test and/or upload it, I would appreciate it.
Note: I didn't put an entry to close this bug because I intend to
retitle it, lower the
On Fri, Dec 16, 2016 at 08:25:02AM +, Gianfranco Costamagna wrote:
> Hi,
>
>
> >export DEB_BUILD_MAINT_OPTIONS=noopt
>
> >
> >to the top of d/rules and rebuilding should do it.
>
>
> it worked:
> DEB_BUILD_OPTIONS=noopt dpkg-buildpackage
>
> [...]
>
Interesting. Under the emulator
On a whim, I decided to install the Hercules s390 emulator and see if I
could reproduce the problem there. It's slow (4+ hours to do a build of
xerces) but it appears to work, and the issue shows up there as well.
I started trying to trace down the memory issue in real time, but the
variables I
On Wed, Dec 14, 2016 at 07:11:12AM +, Gianfranco Costamagna wrote:
>
> >So while I'm not sure it will help, there might be benefit to try to get a
> >stack trace from DOMCount. It's possible there's an exception being
> >thrown but it's getting caught/squashed. If someone wants to try to
On Tue, Dec 13, 2016 at 11:15:26PM +, Gianfranco Costamagna wrote:
>
> http://paste.debian.net/902086/
>
> ^^ this is the file you requested
>
> G.
That's great. As I had hoped, ignoring that exception allows SAXCount
to complete successfully, and with the expected output (despite the
On Tue, Dec 13, 2016 at 12:06:46PM +, Gianfranco Costamagna wrote:
> Hi
>
>
> >Based on the stack trace, the exception is thrown because a managed
>
> >buffer that is being freed isn't actually registered to the buffer manager.
> >his shouldn't happen, since the only way to get a buffer is
Based on the stack trace, the exception is thrown because a managed
buffer that is being freed isn't actually registered to the buffer manager.
This shouldn't happen, since the only way to get a buffer is to request
it from the manager in the first place. It's possible there's a memory
>
> It still fails the very same way.
> Attached the backtrace I get with the way you said above (without
> exporting anything). It seems to really be full, what Gianfranco posted
> looks more like the non-full/regular bt, dunno why.
Thanks. Disregard my other email.
GDB didn't find the debug
On Sun, Dec 11, 2016 at 07:43:08PM +0100, Mattia Rizzolo wrote:
> On Sun, Dec 11, 2016 at 01:34:18PM -0500, Bill Blough wrote:
> > I just found a reference in the Debian Maintainer's Guide that says the
> > default build locale is C. And it looks like the Ubuntu build is
> &g
On Sun, Dec 11, 2016 at 06:20:13PM +, Mattia Rizzolo wrote:
> anyhow, 1) build should not depend on the locale it runs
I'll admit, I don't know a lot about locales, etc., but some of the
tests use files in UTF-8. Wouldn't that generally require UTF-8 support
from the locale?
> 2) afaik it
On Sun, Dec 11, 2016 at 05:57:38PM +, Gianfranco Costamagna wrote:
> Hi,
>
> >Does anyone know (or can find out) the default locale on the s390
> >systems, and does that differ from the other architectures?
> >
> >env | egrep "(LC|LANG)"
> >
> >should give a list of relevant vars.
>
>
>
Does anyone know (or can find out) the default locale on the s390
systems, and does that differ from the other architectures?
env | egrep "(LC|LANG)"
should give a list of relevant vars.
Thanks,
Bill
On Sat, Dec 10, 2016 at 08:56:29AM +, Gianfranco Costamagna wrote:
>
> > libtool --mode=execute gdb --args samples/SAXCount
> > samples/data/personal.xml
> > catch throw
> >
> > bt full
> >continue
> > quit
> >This will hopefully help me to isolate this issue.
> >
>
>
> here we are!
>
On Sat, Dec 10, 2016 at 02:25:08AM +0100, Mattia Rizzolo wrote:
> On Fri, Dec 09, 2016 at 08:11:54PM -0500, Bill Blough wrote:
> > > >Or does anyone have other suggestions?
>
> I have one: please try to CC people (and/or MLs) sooner. I now noticed
> that you asked for
On Fri, Dec 09, 2016 at 11:07:54PM +, Gianfranco Costamagna wrote:
> >Can anyone comment on the use of -Bsymbolic_functions in Ubuntu? If I
> >understand it correctly, it shouldn't have any effect on this, but I
> >have no way to test it other than another upload.
>
>
> I still prefer the
I'd really like to get this resolved before the freeze.
Can anyone comment on the use of -Bsymbolic_functions in Ubuntu? If I
understand it correctly, it shouldn't have any effect on this, but I
have no way to test it other than another upload.
Assuming that's not it, would someone be willing
I diffed the Debian and Ubuntu build logs, and the only difference I see
in build flags is that Ubuntu adds the -Bsymbolic_functions link flag.
Though, if I correctly understand the description of the flag, then I
don't think that's related.
As for package version differences, the only
I looked at it briefly, but had to refocus on other issues before I
could really get anywhere. I'll get it sorted out and/or forwarded
shortly.
Thanks for the ping!
On Thu, Nov 03, 2016 at 04:10:27PM -0400, Sandro Tosi wrote:
> On Mon, 8 Aug 2016 13:24:48 + Mattia Rizzolo
On Fri, Oct 10, 2014 at 02:30:10PM +0200, Mathieu Malaterre wrote:
Any chance patch from upstream be applied ? We are very close to
entering freeze period.
The upstream patch has already been applied in the repository, so it is
technically pending.
Now that we're not blocked from Jessie by
29 matches
Mail list logo
