Hi
In LTS the hook is available in debian/rules but commented. The number
of failed test cases seems to be the same as I remember from when I
had to disable it.
// Ola
On 1 December 2016 at 05:59, Guido Günther wrote:
> Hi Antoine,
> On Wed, Nov 30, 2016 at 11:03:39PM -0500, Antoine Beaupré wro
Hi Antoine,
On Wed, Nov 30, 2016 at 11:03:39PM -0500, Antoine Beaupré wrote:
> On 2016-11-30 16:46:17, Ola Lundqvist wrote:
> > Hi
> >
> > There were no test suite before the update so I could not tell if it was a
> > regression or not.
>
> I just figured out how to hook up the test suite, and it
On 2016-11-30 16:46:17, Ola Lundqvist wrote:
> Hi
>
> There were no test suite before the update so I could not tell if it was a
> regression or not.
I just figured out how to hook up the test suite, and it fails:
Tests summary:
--
Passed: 8282
Failed: 17
Faile
On Tue, 2016-11-29 at 12:14 +0100, Raphael Hertzog wrote:
> Hi,
>
> On Mon, 28 Nov 2016, Roberto C. Sánchez wrote:
> > Quite right:
> > http://people.debian.org/~roberto/imagemagick_6.7.7.10-5+deb7u7_6.7.7.10-5+deb7u8.diff
>
> Somme comments:
> - since we have no git history, it's nice to indicat
On 2016-11-30 16:46:17, Ola Lundqvist wrote:
> Hi
>
> There were no test suite before the update so I could not tell if it was a
> regression or not.
Ah, I see! Thanks for the updates, I'll see if i can fix the test
suite for a while otherwise I'll just stick with this...
A.
--
Drowning people
Hi
There were no test suite before the update so I could not tell if it was a
regression or not.
/ Ola
Sent from a phone
Den 30 nov 2016 22:27 skrev "Antoine Beaupré" :
> On 2016-11-30 16:17:50, Ola Lundqvist wrote:
> > Hi Antoine
> >
> > I do not find it strange (as I was one of the two that
On 2016-11-30 16:17:50, Ola Lundqvist wrote:
> Hi Antoine
>
> I do not find it strange (as I was one of the two that did it). You
> are supposed to keep the changelog as far as I know. I mirrored the
> changes in stable/jessie. I never checked the unstable version (I do
> not think I did at least).
Hi Antoine
I do not find it strange (as I was one of the two that did it). You
are supposed to keep the changelog as far as I know. I mirrored the
changes in stable/jessie. I never checked the unstable version (I do
not think I did at least).
However the resulting package was the same (as jessie
I have looked at updating the nss package in wheezy to cover for a new
security issue that came up. The package is ready for testing in:
https://people.debian.org/~anarcat/debian/wheezy-lts/
The diff between the upstream 2.26.2 release and the 2.26 release in
wheezy is fairly small, so I felt it
On 2016-11-30 14:11:31, Jonas Meurer wrote:
> Hi LTS list,
>
> I spent the last six hours backporting the CVE-2016-7067 patch[1] to
> monit 5.4 from Debian Wheezy. A lot of manual backporting work was needed.
>
> I already tested the resulting package on a productive Wheezy system
> running monit a
Hi everybody,
I uploaded version 1.900.1-13+deb7u5 of jasper to:
https://people.debian.org/~alteholz/packages/wheezy-lts/jasper/amd64/
Please give it a try and tell me about any problems you met.
As upstream is basically doing only bugfixes now, I would suggest to not
proceed with patching th
Hi LTS list,
I spent the last six hours backporting the CVE-2016-7067 patch[1] to
monit 5.4 from Debian Wheezy. A lot of manual backporting work was needed.
I already tested the resulting package on a productive Wheezy system
running monit and verified that it
*) installs and upgrades cleanly
*)
12 matches
Mail list logo
