On Thu, Dec 29, 2016 at 9:36 PM, victory wrote:
> correction libraw ... fix memory objects are not intialized properly
> in*i*tialized
Fixed in CVS.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Santiago Vila:
> Dear Release Managers:
>
> If Release Policy wording is not going to be clarified in any way, that's ok.
>
> [...]
>
> Please advise.
>
> Thanks.
>
Hi Santiago,
Thanks for your interest in this subject and for wanting to increase the
stability of builds in Debian.
As Julien
Rob Browning:
>
> I suspect it might be too late, but 0.29 has just been uploaded to sid,
> and at least speaking from the upstream perspective (I'm one of the
> developers there), we'd certainly be happy to see it stretch.
>
> I think we're probably about 2 days past the 10-day migration window,
Processing commands for cont...@bugs.debian.org:
> # correct subject
> retitle 849725 jessie-pu: package cairo/1.14.0-2.1+deb8u2
Bug #849725 [release.debian.org] jessie-pu cairo/1.14.0-2.1+deb8u2
Changed Bug title to 'jessie-pu: package cairo/1.14.0-2.1+deb8u2' from
'jessie-pu cairo/1.14.0-2.1+de
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Hi
src:cairo in jessie is affected by CVE-2016-9082 which would not
warrant a DSA. A while back in october the issue was already fixed in
unstable, cf. #842289. I would like to prop
Quack,
I think the release team should have been involved much much earlier.
It seems having Lilypond working with recent Guile before the release is
not going to happen. Even if it built properly there would maybe have
runtime bugs to solve.
If people are willing to maintain Guile 1.8 into
Processing commands for cont...@bugs.debian.org:
> close 847500
Bug #847500 [release.debian.org] jessie-pu: package samba/2:4.2.14+dfsg-0+deb8u2
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
847500: http://bugs.debian.org/cgi-bin/bugreport.cgi
OK, we're now down to these outstanding issues:
- automake: can't yet sbuild; known sbuild issues (could try porterbox next)
- doxymacs: appears fine; need to test resulting deb behavior.
This package is orphaned, so we should be relatively free to fix it.
- gnuplot: builds fine; ne
I suspect it might be too late, but 0.29 has just been uploaded to sid,
and at least speaking from the upstream perspective (I'm one of the
developers there), we'd certainly be happy to see it stretch.
I think we're probably about 2 days past the 10-day migration window,
but I didn't know whether
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Hi
I'd like to fix CVE-2013-7459 (#849495) in jessie via the next point release.
The issue was marked as no-dsa.
The proposed debdiff is attached. The same patch was applied to the
Rob Browning writes:
> And at the moment, we have:
>
> First category:
> - two packages that are likely fine once the deps are broadened
> - five still to evaluate
>
Update regarding the second category:
- ten packages that appear fine (plus or minus a couple of trivial patches)
We've been hoping (#debian-emacs and I) for a while that we might be
able to remove emacs24 from stretch, and while there was some initial
trouble with emacs25's stability, we finally got that sorted, and we've
been trying to nudge maintainers to adjust their package deps to not
depend solely on e
Your message dated Thu, 29 Dec 2016 17:07:53 +0100
with message-id <8e24c0ec-1478-07db-0e1c-ad7a56ced...@debian.org>
and subject line Re: Bug#842744: transition: kodi
has caused the Debian Bug report #842744,
regarding transition: kodi
to be marked as done.
This means that you claim that the probl
On 29/12/16 16:34, Francesco Poli wrote:
> Hello!
> It seems to me that the BTS version tracking is no longer working
> correctly.
>
> Yesterday the RC bug count page [1] suddenly reported more than 2000 RC
> bugs closed or downgraded. The actual listed RC bugs were not really
> closed or downgrad
Processing control commands:
> tags -1 confirmed
Bug #849218 [release.debian.org] transition: imagemagick
Added tag(s) confirmed.
--
849218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 confirmed
On 23/12/16 18:54, Bastien ROUCARIÈS wrote:
> Package: release.debian.org
> Severity: normal
>
> Hi,
>
> Due to #846385 could be possible to get transition for imagemagick.
>
> Sorry for being late but upstream is really sloppy.
>
> The break was in 6.9.2-10 released
Your message dated Thu, 29 Dec 2016 16:32:27 +0100
with message-id
and subject line Re: Bug#849567: nmu: gdb-mingw-w64_10.4
has caused the Debian Bug report #849567,
regarding nmu: gdb-mingw-w64_10.4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Hello!
It seems to me that the BTS version tracking is no longer working
correctly.
Yesterday the RC bug count page [1] suddenly reported more than 2000 RC
bugs closed or downgraded. The actual listed RC bugs were not really
closed or downgraded, they just seemed to lack knowledge about which
pack
correction libraw ... fix memory objects are not intialized properly
in*i*tialized
--
victory
no need to CC me :-)
Hello,
sorry for the delay, i somehow thought this was already fixed.
I will upload my fixed version (following [0] today/tomorrow) - Scarlet
fever struck the whole family :-(.
Regards,
Simon
[0]
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security
Am 2016-12-26 u
20 matches
Mail list logo