Norbert Preining writes:
> I have prepared a new package and tried to build it in my
> wheezy chroot/cowbuilder, but that ended in segfaults.
> It seems that either my wheezy chroot is broken, or the binaries
> in wheezy (bash) cannot run anymore on my sid system.
It looks like it builds fine fr
Hi Markus,
> Would you like to take care of this yourself?
I have prepared a new package and tried to build it in my
wheezy chroot/cowbuilder, but that ended in segfaults.
It seems that either my wheezy chroot is broken, or the binaries
in wheezy (bash) cannot run anymore on my sid system.
Thus,
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of qbittorrent:
https://security-tracker.debian.org/tracker/source-package/qbittorrent
Would you like to take care of this yourself?
If yes, please follow the workfl
On Mon, Mar 06, 2017 at 06:56:33PM +0100, Arturo Borrero Gonzalez wrote:
> However, please note, the usefulness of that old version of suricata
> (5 years old) is very reduced. People should really move forward.
I don't understand: because they are suffering from old software already, you
think i
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of imagemagick:
https://security-tracker.debian.org/tracker/source-package/imagemagick
Would you like to take care of this yourself?
If yes, please follow the workfl
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of freetype:
https://security-tracker.debian.org/tracker/CVE-2016-10244
Would you like to take care of this yourself?
If yes, please follow the workflow we have defi
On 6 March 2017 at 17:14, Chris Lamb wrote:
> Arturo Borrero Gonzalez wrote:
>
>> > the Debian LTS team would like to fix the security issues which are
>> > currently open in the Wheezy version of suricata:
> […]
>> Yes, I can do that this month.
>
> We would prefer to provide an update a little s
Arturo Borrero Gonzalez wrote:
> > the Debian LTS team would like to fix the security issues which are
> > currently open in the Wheezy version of suricata:
[…]
> Yes, I can do that this month.
We would prefer to provide an update a little sooner; would you mind if I
jumped in and handled this if
On 6 March 2017 at 10:23, Markus Koschany wrote:
> Hello dear maintainer(s),
>
> the Debian LTS team would like to fix the security issues which are
> currently open in the Wheezy version of suricata:
> https://security-tracker.debian.org/tracker/source-package/suricata
>
> Would you like to take
On Mon, Mar 06, 2017 at 09:45:04AM +0100, Markus Koschany wrote:
> Hi James,
>
> there are currently two security issues open in the Wheezy version of
> vim? Would you like to take care of them again?
Sure, I'll work on addressing those.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of suricata:
https://security-tracker.debian.org/tracker/source-package/suricata
Would you like to take care of this yourself?
If yes, please follow the workflow we
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of texlive-base:
https://security-tracker.debian.org/tracker/CVE-2016-10243
Would you like to take care of this yourself?
If yes, please follow the workflow we have
Hi James,
there are currently two security issues open in the Wheezy version of
vim? Would you like to take care of them again?
https://security-tracker.debian.org/tracker/source-package/vim
Regards,
Markus
signature.asc
Description: OpenPGP digital signature
13 matches
Mail list logo
