Your message dated Sun, 6 Jun 2021 15:47:48 -0600
with message-id <20210606214748.e75dcqzi6rkcfqvt@debian>
and subject line closing RoQA bug
has caused the Debian Bug report #987537,
regarding RM: scrollz -- RoQA unmaintained, dead upstream, has security issues
to be marked as done.
This means tha
Your message dated Sun, 06 Jun 2021 21:20:51 +
with message-id
and subject line Bug#988310: fixed in ssl-cert 1.1.0+nmu1
has caused the Debian Bug report #988310,
regarding ssl-cert: make-ssl-cert uses same filename for template and output
to be marked as done.
This means that you claim that
Processing control commands:
> tags 988310 + patch
Bug #988310 [ssl-cert] ssl-cert: make-ssl-cert uses same filename for template
and output
Ignoring request to alter tags of bug #988310 to the same tags previously set
> tags 988310 + pending
Bug #988310 [ssl-cert] ssl-cert: make-ssl-cert uses sa
Control: tags 988310 + patch
Control: tags 988310 + pending
I've prepared an NMU for ssl-cert (versioned as 1.1.0+nmu1) and
uploaded it to NEW.
Cheers
Timo
--
⢀⣴⠾⠻⢶⣦⠀ ╭╮
⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │
⢿⡄⠘⠷⠚⠋
On Sun, 6 Jun 2021 21:55:14 +0200 Stefan Fritsch wrote:
I won't be able to deal with this for at least 1-2 weeks. It would be
nice if someone could look at it and downgrade or NMU+unblock.
Consider it done :)
The suggested patch shifts the arguments, like it is done on other parts of the
scri
I won't be able to deal with this for at least 1-2 weeks. It would be
nice if someone could look at it and downgrade or NMU+unblock.
Am 06.06.21 um 13:14 schrieb Stefan Bühler:
Hi,
On Mon, 10 May 2021 11:09:58 +0200 Parodper wrote:
Package: ssl-cert
Version: 1.1.0
Severity: grave
Tags: patch
Your message dated Sun, 06 Jun 2021 19:33:28 +
with message-id
and subject line Bug#987149: fixed in xscreensaver 5.45+dfsg1-2
has caused the Debian Bug report #987149,
regarding xscreensaver: CVE-2021-31523: allows starting external programs with
cap_net_raw
to be marked as done.
This means
Control: severity 989406 normal
Control: retitle 989406 wireguard-dkms is unneeded for stock kernels > 5.6
I'm downgrading the severity to keep wireguard-dkms in bullseye -- we
can increase it again once bullseye is released to keep wireguard-dkms
out of bookworm.
Adrian or others, if you would p
Processing control commands:
> severity 989406 normal
Bug #989406 [wireguard-dkms] wireguard-dkms makes little sense with the
bullseye kernel
Severity set to 'normal' from 'serious'
> retitle 989406 wireguard-dkms is unneeded for stock kernels > 5.6
Bug #989406 [wireguard-dkms] wireguard-dkms mak
Your message dated Sun, 06 Jun 2021 14:33:07 +
with message-id
and subject line Bug#988893: fixed in squid 4.6-1+deb10u6
has caused the Debian Bug report #988893,
regarding squid: CVE-2021-28651
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
O 06/06/21 ás 13:14, Stefan Bühler escribiu:
Hi,
On Mon, 10 May 2021 11:09:58 +0200 Parodper
wrote:
Package: ssl-cert Version: 1.1.0 Severity: grave Tags: patch
Justification: renders package unusable
Given ssl-cert is installed on many systems probably just for the
snakeoil self-signed ce
Hi,
On Sun, Jun 06, 2021 at 12:46:40PM +0200, Andrej Shadura wrote:
> Hi,
>
> On Sun, 6 Jun 2021, at 12:44, Tormod Volden wrote:
> > Hi Salvatore and Andrew,
> >
> > I have prepared a xscreensaver 5.45+dfsg1-2 (which removes the setcap)
> > in git. Andrew is my regular sponsor. Andrew, can you p
Hi,
On Mon, 10 May 2021 11:09:58 +0200 Parodper wrote:
> Package: ssl-cert
> Version: 1.1.0
> Severity: grave
> Tags: patch
> Justification: renders package unusable
Given ssl-cert is installed on many systems probably just for the
snakeoil self-signed certificate I think the severity isn't just
On Sun, Jun 6, 2021 at 11:57 AM Salvatore Bonaccorso wrote:
>
> I've prepared an NMU for xscreensaver (versioned as 5.45+dfsg1-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
I saw this now. I would of course prefer to have my 5.45+dfsg1-2
uploaded
Hi,
On Sun, 6 Jun 2021, at 12:44, Tormod Volden wrote:
> Hi Salvatore and Andrew,
>
> I have prepared a xscreensaver 5.45+dfsg1-2 (which removes the setcap)
> in git. Andrew is my regular sponsor. Andrew, can you please upload
> this version? Or if you have no time, can Salvatore do it?
>
> Best
On 06 juin 2021 12:31, Andreas Beckmann wrote:
> On 05/06/2021 09.14, Christian Marillat wrote:
>> Display driver is working
>
> Which versions? 450.119.03? 450.119.04? 460.84?
As requested in your previous e-mail (tesla-450) 450.119.04
Christian
Hi Salvatore and Andrew,
I have prepared a xscreensaver 5.45+dfsg1-2 (which removes the setcap)
in git. Andrew is my regular sponsor. Andrew, can you please upload
this version? Or if you have no time, can Salvatore do it?
Best regards,
Tormod
On Sat, Jun 5, 2021 at 3:08 PM Salvatore Bonaccorso
On 05/06/2021 09.14, Christian Marillat wrote:
Display driver is working
Which versions? 450.119.03? 450.119.04? 460.84?
Andreas
Control: tags 987149 + patch
Control: tags 987149 + pending
Dear maintainer,
I've prepared an NMU for xscreensaver (versioned as 5.45+dfsg1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru xscreensaver-5.45+dfsg1/debian/cha
Processing control commands:
> tags 987149 + patch
Bug #987149 [src:xscreensaver] xscreensaver: CVE-2021-31523: allows starting
external programs with cap_net_raw
Added tag(s) patch.
> tags 987149 + pending
Bug #987149 [src:xscreensaver] xscreensaver: CVE-2021-31523: allows starting
external pro
Could you close this bug or downgrade its severity, or do whatever it
takes so that this *isn't* removed from bullseye? Removing this
package from the bullseye release would cause large problems.
Hello Samuel,
On Sat, 29 May 2021 14:06:18 +0100 Samuel Henrique wrote:
>
> That's a great catch!
> I'm bumping the severity as this "makes the package in question
> unusable or mostly so".
thanks for getting back to me regarding this bug.
Since there is just an offset in the values used for ke
Processing control commands:
> severity -1 important
Bug #989193 [apparmor-profiles-extra] breaks apt-cacher-ng by blocking link
operation
Severity set to 'important' from 'serious'
--
989193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989193
Debian Bug Tracking System
Contact ow...@bugs
Control: severity -1 important
intrigeri (2021-06-02):
> I see you've made this bug RC. I'd like to better understand the
> severity, so I can figure out what I should do for Bullseye.
> I'm wondering because I'm using this AppArmor policy on sid with
> apt-cacher-ng myself, and I can't find trace
24 matches
Mail list logo
