Hi Roberto
Thanks for the quick response. This was my original thought but I was
unsure as the regression description on
https://wiki.debian.org/LTS/Development described the use a little
differently (did not consider the case when the text was wrong).
Maybe that information should be updated? I'm
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of libwmf:
https://security-tracker.debian.org/tracker/CVE-2016-9011
Would you like to take care of this yourself?
If yes, please follow the workflow we have defined
On Fri, Oct 28, 2016 at 10:52:31PM +0200, Ola Lundqvist wrote:
>Hi
>I wrote wrong version in the DLA for the recent bash update. I wrote
>the version in wheezy instead of the fixed version.
>Should I create a new DLA-680-2 or shall I re-send DLA-680-1 with
>updated revision info
Hi
I wrote wrong version in the DLA for the recent bash update. I wrote
the version in wheezy instead of the fixed version.
Should I create a new DLA-680-2 or shall I re-send DLA-680-1 with
updated revision information?
And the text for the DLA, shall I keep everything in it except for the
versi
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of kde-runtime:
https://security-tracker.debian.org/tracker/CVE-2016-7787
Would you like to take care of this yourself?
If yes, please follow the workflow we have de
On Tue, Oct 25, 2016 at 10:38:04AM +0200, Hugo Lefeuvre wrote:
> > > However, more than 15 CVEs are still affecting libav in Debian wheezy.
> > > Would it be feasible to work on a new point release fixing some of
> > > them ?
> >
> > Yes, I plan to and will after I'm back from a short trip to SF a
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of tar:
https://security-tracker.debian.org/tracker/CVE-2016-6321
Would you like to take care of this yourself?
If yes, please follow the workflow we have defined he
Hello,
I just finished preparing new version of tiff/tiff3 packages.
One of the patch has not been officially acked by upstream yet
(cf http://bugzilla.maptools.org/show_bug.cgi?id=2580 )
and thus I would like some user testing before I release
the DLA to make sure that my changes do not have unex
On Fri, Oct 28, 2016 at 09:41:42AM -0400, Antoine Beaupré wrote:
> On 2016-10-28 07:53:39, Roberto C. Sánchez wrote:
> > It appears to me that the upstream diff is ensuring that the allocated
> > memory area is not too small, hence the change of "number_planes_filled"
> > to "MagickMax(number_plane
On 2016-10-28 07:53:39, Roberto C. Sánchez wrote:
> It appears to me that the upstream diff is ensuring that the allocated
> memory area is not too small, hence the change of "number_planes_filled"
> to "MagickMax(number_planes_filled,4)" in two places. However, in the
> code currently in wheezy,
On Fri, Oct 28, 2016 at 09:28:37AM -0400, Antoine Beaupré wrote:
> On 2016-10-27 22:28:17, Roberto C. Sánchez wrote:
> > [ Unknown signature status ]
> > Hello,
> >
> > I decided (perhaps because I don't know any better) to take over
> > ImageMagick after Ben released his lock on it.
>
> For the r
On 2016-10-27 22:28:17, Roberto C. Sánchez wrote:
> [ Unknown signature status ]
> Hello,
>
> I decided (perhaps because I don't know any better) to take over
> ImageMagick after Ben released his lock on it.
For the record, I did the same yesterday, except I forgot to lock the
package... :/
I hav
On Fri, Oct 28, 2016 at 02:05:25PM +0200, Salvatore Bonaccorso wrote:
> Hi
>
> I now have uploaded the version (see previously sent debdiff) to
> security master and will release the regression update once all archs
> have build the packages.
>
Hi,
I have now also uploaded the wheezy packages us
Hi
I now have uploaded the version (see previously sent debdiff) to
security master and will release the regression update once all archs
have build the packages.
Regards,
Salvatore
On Thu, Oct 27, 2016 at 10:28:17PM -0400, Roberto C. Sánchez wrote:
>
> I have some questions about how to handle this issue:
>
> https://security-tracker.debian.org/tracker/TEMP-0836171-53B142
> https://bugs.debian.org/836171
>
So, I have another similar issue on which I would like some
confi
Hi Raphael,
Thanks for the feedback.
On Fri, Oct 28, 2016 at 10:32:06AM +0200, Raphael Hertzog wrote:
> Hi,
>
> On Thu, 27 Oct 2016, Roberto C. Sánchez wrote:
> > https://security-tracker.debian.org/tracker/TEMP-0836171-53B142
> > https://bugs.debian.org/836171
> >
> > The diff that addresses t
Hi Lars,
2016-10-27 18:07 GMT+02:00 Lars Tangvald :
>
> - bal...@balintreczey.hu wrote:
>
>> Hi Lars,
>>
>> I noticed you have prepared the MySQL update for wheezy in git:
>> https://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/?id=refs/heads/debian/wheezy
>>
>> Would you like the LTS T
Hi,
On Thu, 27 Oct 2016, Roberto C. Sánchez wrote:
> https://security-tracker.debian.org/tracker/TEMP-0836171-53B142
> https://bugs.debian.org/836171
>
> The diff that addresses this issue is here:
> https://github.com/ImageMagick/ImageMagick/commit/10b3823a7619ed22d42764733eb052c4159bc8c1
This
18 matches
Mail list logo
