Bug#965309: bzdiff not working with two compressed files

2020-07-20 Thread santiagorr
Control: tags -1 + confirmed pending El 19/07/20 a las 10:13, Joey Schulze escribió: > Package: bzip2 > Version: 1.0.6-9.2~deb10u1 > Severity: important > Tags: patch > > Moin, > > bzdiff does not work when comparing two bzip2 compressed files: > > finlandia!joey(tty6):/data> bzdiff

Bug#852086: paxrat: Fails on removal with "sh: 1: /sbin/paxrat: not found"

2017-01-23 Thread santiagorr
Control: forwarded -1 https://github.com/subgraph/paxrat/pull/21

Bug#852086: paxrat: Fails on removal with "sh: 1: /sbin/paxrat: not found"

2017-01-23 Thread santiagorr
Control: tags -1 + pending upstream Hi! El 21/01/17 a las 16:11, intrig...@debian.org escribió: … > Purging configuration files for paxrat (1.0-2) ... > sh: 1: /sbin/paxrat: not found > E: Problem executing scripts DPkg::Post-Invoke '/sbin/paxrat -c > /etc/paxrat/paxrat.conf' > E: Sub-process

Bug#849863: paxrat: Lacks dependency on paxctl

2017-01-17 Thread santiagorr
Control: tags -1 +pending Control: severity -1 important El 16/01/17 a las 14:50, intrigeri escribió: > santiag...@riseup.net: > > I think a Recommends: would be a more accurate relationship. Is that > > OK for you? > > Sounds right! change pushed into the collab maint rep. -- Santiago

Bug#849864: paxrat: Please run paxrat during (early) boot

2017-01-16 Thread santiagorr
Hi! El 01/01/17 a las 18:48, intrig...@debian.org escribió: … > > It's great that there's APT integration to take care of the package > installation and upgrade issue, but how about the first time one > reboots into their PaX-enabled kernel? Likely they won't have run > paxrat manually yet, so

Bug#849863: paxrat: Lacks dependency on paxctl

2017-01-16 Thread santiagorr
El 01/01/17 a las 18:04, intrig...@debian.org escribió: … > If I got it right, paxrat requires paxctl, but I see no such > dependency encoded in the package. I didn't try it myself yet, hence > the non-RC severity, but if I guessed right, then this bug should > be RC. Thanks for pointing this

Bug#824638: debian-security-support: [INTL:te] Telugu debconf templates translation

2016-05-18 Thread santiagorr
Package: debian-security-support Severity: wishlist Tags: l10n patch El 18/05/16 a las 11:34, Praveen Illa escribió: > Hi Santiago, > > Please find the attached Telugu translation(te) for debian-security-support. > > Cheers, > Praveen Illa. Hi Praveen, Thanks for the translation. For having a

Bug#793142: marked as done (torbrowser-launcher: torbrowser cannot start+update due to apparmor issues)

2016-03-08 Thread santiagorr
Holger, El 06/03/16 a las 09:15, Debian Bug Tracking System escribió: ... > > I'm closing this bug as the BTS has version tracking, thus > https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=torbrowser-launcher;dist=stable > will still show this bug as open, while >

Bug#525213: grep: Misleading error message when presenting a badly formed character class

2016-02-29 Thread santiagorr
control: clone -1 -2 control: retitle -2 "regex: fix [ diagnostic" control: reassign -2 glibc control: tags -2 + patch control: block -1 -2 El 26/02/16 a las 08:49, Jim Meyering escribió: > On Fri, Feb 26, 2016 at 6:51 AM, wrote: > > Hi, > > > > I'd like to forward a bug

Bug#525213: forwarded to upstream

2016-02-26 Thread santiagorr
Control: forwarded -1 http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22820 thanks

Bug#186568: bug#22793: grep -E assertion failure with back references

2016-02-24 Thread santiagorr
Control: reassign -1 glibc Control: retitle -1 "ERE '0|()0|\1|0' causes regexec undefined behavior" Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=18986 Control: tags -1 + patch El 24/02/16 a las 11:46, Paul Eggert escribió: > With recent 'grep' you can work around the

Bug#814997: Reverting upstream commit 40ed879db fixes gnome-pkg-tools

2016-02-17 Thread santiagorr
Hello Andreas, El 17/02/16 a las 15:46, Andreas Henriksson escribió: > Hello! > > I've bisected the upstream git repo v2.22..v2.23 and found that > the issue is caused by commit 40ed879db22d57516a31fefd1c39416974b74ec4 > "grep: fix bug with with invalid unibyte sequence" > > I've verified that