Hi Sylvain,
On Fri, Apr 01, 2022 at 12:06:40PM +0200, Sylvain Beucler wrote:
> Holger, can you clarify if you want the LTS team to handle
> debian-security-support backports to stretch, or if you intend to do it
> yourself?
thanks for asking, I'd be glad for more people maintaining
debian-securi
Hi,
On 01/04/2022 11:50, Emilio Pozuelo Monfort wrote:
On 03/12/2021 23:50, Markus Koschany wrote:
Am Freitag, dem 03.12.2021 um 14:28 +0100 schrieb Sylvain Beucler:
This year I worked on libspring-java twice for LTS&ELTS. In both case
upstream provided limited information for the CVEs, and fo
Hi,
On 03/12/2021 23:50, Markus Koschany wrote:
Hi Sylvain,
Am Freitag, dem 03.12.2021 um 14:28 +0100 schrieb Sylvain Beucler:
Hi,
This year I worked on libspring-java twice for LTS&ELTS. In both case
upstream provided limited information for the CVEs, and for 5 of them
we're unable to determ
Hi Sylvain,
Am Freitag, dem 03.12.2021 um 14:28 +0100 schrieb Sylvain Beucler:
> Hi,
>
> This year I worked on libspring-java twice for LTS&ELTS. In both case
> upstream provided limited information for the CVEs, and for 5 of them
> we're unable to determine the fixes.
> https://deb.freexian.co
On Tue, 26 Mar 2019 14:46:35 +0100 Mattia Rizzolo wrote:
> Dear maintainer (and tony, whose upload 4.3.22-2 caused this bug),
>
> your package libspring-java suddenly stopped building two binaries that
> were actively used by other packages, like activemq.
>
> What's very worse, the changelog d
On 27 Nov 2014 12:18, "Emmanuel Bourg" wrote:
>
>
> I'm indeed working on the libspring-java upgrade to the version 3.2.12.
> The propdeps plugin was easy to package and I hope the FTP masters will
> quickly validate it, but if I can't get it in Jessie with the Spring
> update I'll probably follow
Le 27/11/2014 13:00, Stephen Nelson a écrit :
> However as a pragmatic option I noticed that Redhat/Fedora took a clever
> approach and they are downloading the .pom files published by Gradle
> from Maven central and using those for the build.
Hi Stephen,
I'm indeed working on the libspring-java
On Wed, Aug 27, 2014 at 6:55 PM, tony mancill wrote:
> I just checked and it builds fine for me, but I suspect that it's
> because my cowbuilder bind mounts my build area so that its path looks
> the same to the bits of the build that run before entering the chroot to
> those after entering that
On 08/25/2014 03:02 AM, Stephen Nelson wrote:
> Hi,
>
> I've started work on backporting CVE-2014-0255 [1] to the version of
> Spring in wheezy to fix [2]. However I'm having a few problems building
> it in pbuilder/cowbuilder and wondered if anyone has any pointers to get
> it building?
>
> I'm
On Thu, Oct 10, 2013 at 11:22 AM, Emmanuel Bourg wrote:
> Le 10/10/2013 15:30, Stephen Nelson a écrit :
> > I'm looking at packaging a new upstream version of libspring-java.
> > However upstream has switched to using gradle to build the code. What
> > is the correct way to package for Debian in
Le 10/10/2013 15:30, Stephen Nelson a écrit :
> I'm looking at packaging a new upstream version of libspring-java.
> However upstream has switched to using gradle to build the code. What
> is the correct way to package for Debian in this instance?
Not sure, but I think you have to patch the build
11 matches
Mail list logo
