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 options-18.bz2 options-19.bz2
> diff: extra operand '/tmp/bzdiff.6FPnOK9OHZ'
> diff: Try 'diff --help' for more information.
> 
> The problem has been introduced in buster and is still present in bullseye.
> 
> The solution is to remove the quotes around options in diff execution
> as show in the attached patch.
> 
> Regards
> 
>   Joey

Dear Joey,

Thanks for reporting this. Patch applied in git, and I'll upload to
unstable today or tomorrow.

Cheers,

 -- Santiago


signature.asc
Description: PGP signature

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 returned an error code
> 
> I guess the dpkg/APT hook should check if /sbin/paxrat exists, and
> exit nicely with return code 0 if it doesn't.
> 

Oups, I have missed that. Thanks for reporting.  I will upload a new
release soon that fixes this.

Cheers,

  -- Santiago

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 the first boot may be problematic (e.g.
> GDM won't start). This would be a non-issue if paxrat was during
> (early) boot.
> 
> Subgraph OS does that using a live-config hook, which is of course not
> applicable in the general case. So I suggest adding a systemd unit
> file, or whatever appropriate solution the maintainers prefer.

I am not expert on writing systemd units, and I am unable to play with
this soon. So it would be great if you could propose a patch :-)

Maybe paxrat should also take this into account for systems relying on
sysvinit.

Cheers,

  -- Santiago

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 out!

However, paxrat uses paxctl as second option, when it is not possible to
set the flags via xattr (and the grsec kernel should be configured to
support them). I think a Recommends: would be a more accurate
relationship. Is that OK for you?

Cheers,

  -- Santiago

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 record, I am filling a bug that
should be closed in the next upload.

Additionally, as the comment in template.pot says, the po/ directory
includes more messages that need translation. You have translated the
debconf templates, which is great, but now more general
debian-security-support messages also need to be translated into Telugu.
Could you please take a look to them (messages.po attached).

Maybe having two po/ and debian/po/ directories is confusing. I am not
expert on i18n support, especially for debian native packages, and I
wonder if these messages could be unified in a single dir.

Cheers,

Santiago

> 
> 
> On Thu, May 12, 2016 at 2:16 PM, Santiago R.R.  wrote:

...

>
> #
> # Note to translators:
> # Some more messages that require translation are in the po/
> # directory. Additionally, there's also a manpage at
> # "man/check-support-status.txt", in the docbook format. If you
> # provide a translated version, use the file name
> # "man/check-support-status.txt.$LANG", and it will be added to the
> # package.
> #
> # Telugu translation for Debian-security-support.
> # Copyright (C) 2016 Telugu Contributors
> # This file is distributed under the same license as the 
> debian-security-support package.
> # Praveen Illa , 2016.
> #
> msgid ""
> msgstr ""
> "Project-Id-Version: debian-security-support\n"
> "Report-Msgid-Bugs-To: debian-security-supp...@packages.debian.org\n"
> "POT-Creation-Date: 2016-05-12 09:42+0200\n"
> "PO-Revision-Date: 2016-05-18 11:26+0530\n"
> "Last-Translator: Praveen Illa \n"
> "Language-Team: Telugu \n"
> "MIME-Version: 1.0\n"
> "Content-Type: text/plain; charset=UTF-8\n"
> "Content-Transfer-Encoding: 8bit\n"
> "X-Generator: Gtranslator 2.91.6\n"
> "Plural-Forms: nplurals=2; plural=(n != 1);\n"
> "Language: te\n"
> 
> #. Type: text
> #. Description
> #: ../debian-security-support.templates:2001
> msgid "Ended security support for one or more packages"
> msgstr "ఒకటి లేదా మరిన్ని ప్యాకేజీలకు భద్రతా తోడ్పాటు ముగిసింది"
> 
> #. Type: text
> #. Description
> #: ../debian-security-support.templates:2001
> msgid ""
> "Unfortunately, it has been necessary to end security support for some "
> "packages before the end of the regular security maintenance life cycle."
> msgstr ""
> "దురదృష్టవశాత్తు, సాధారణ భద్రతా నిర్వహణ కాలం కంటే ముందే కొన్ని ప్యాకేజీలకు 
> భద్రతా తోడ్పాటు ముగించడం "
> "ఆవశ్యకమైంది."
> 
> #. Type: text
> #. Description
> #. Type: text
> #. Description
> #. Type: text
> #. Description
> #: ../debian-security-support.templates:2001
> #: ../debian-security-support.templates:3001
> #: ../debian-security-support.templates:4001
> msgid "The following packages found on this system are affected by this:"
> msgstr "దీని వల్ల వ్యవస్థలో క్రింద పేర్కొన్న ప్యాకేజీలు ప్రభావితమవుతాయి:"
> 
> #. Type: text
> #. Description
> #: ../debian-security-support.templates:3001
> msgid "Limited security support for one or more packages"
> msgstr "ఒకటి లేదా మరిన్ని ప్యాకేజీలకు పరిమిత భద్రతా తోడ్పాటు"
> 
> #. Type: text
> #. Description
> #: ../debian-security-support.templates:3001
> msgid ""
> "Unfortunately, it has been necessary to limit security support for some "
> "packages."
> msgstr "దురదృష్టవశాత్తు, కొన్ని ప్యాకేజీలకు భద్రతా తోడ్పాటు పరిమితం చేయడం 
> ఆవశ్యకమైంది."
> 
> #. Type: text
> #. Description
> #: ../debian-security-support.templates:4001
> msgid "Future end of support for one or more packages"
> msgstr "ఒకటి లేదా మరిన్ని ప్యాకేజీలకు తోడ్పాడు భవిష్యత్తులో ముగింపు అయ్యేవి"
> 
> #. Type: text
> #. Description
> #: ../debian-security-support.templates:4001
> msgid ""
> "Unfortunately, it will be necessary to end security support for some "
> "packages before the end of the regular security maintenance life cycle."
> msgstr ""
> "దురదృష్టవశాత్తు, సాధారణ భద్రతా నిర్వహణ కాలం కంటే ముందే కొన్ని ప్యాకేజీలకు 
> భద్రతా తోడ్పాటు ముగించడం "
> "ఆవశ్యకమవుతుంది."

# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR , YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-05-12 09:43+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#: check-support-status.in:24
#, sh-format
msgid ""
"Unknown DEBIAN_VERSION $DEBIAN_VERSION. Valid values from $DEB_LOWEST_VER_ID "
"and $DEB_NEXT_VER_ID"
msgstr

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
> https://bugs.debian.org/torbrowser-launcher will correctly show this bug as
> fixed.
> 
> Also, strictly speaking 0.2.0-2 already fixed this bug (initially), but only
> 0.2.2-3 fixes the one (#808140) preventing the upgrade feature from torbrowser
> (itself) to work, thus the very first control line above.
> 
> That said, the fix for jessie and wheezy-backport is probably to just use the
> profiles from the sid version. This should be easily testable once
> 0.2.3-1~bpo8+1 will be available, which should be doable in 4 days, once the
> version in unstable migrated to testing.
>
> If someone wants to test sooner: just rebuild the sid source package on jessie
> and install and test it. Then please report back here :)

I've rebuilt the package on jessie, but I got this the first time I
tried to launch torbrowser-launcher:

audit: type=1400 audit(1457440407.716:146): apparmor="DENIED" 
operation="file_mmap" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 
name="/home/santiago/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/TorBrowser/Tor/libgmp.so.10"
 pid=3368 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=1000
audit: type=1400 audit(1457440408.036:147): apparmor="DENIED" operation="link" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 
name="/home/santiago/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/.cache/fontconfig/CACHEDIR.TAG.LCK"
 pid=3368 comm="firefox" requested_mask="l" denied_mask="l" fsuid=1000 
ouid=1000 
target="/home/santiago/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/.cache/fontconfig/CACHEDIR.TAG.TMP-dPlCHK"
audit: type=1400 audit(1457440408.036:148): apparmor="DENIED" operation="link" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 
name="/home/santiago/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/.cache/fontconfig/889ed3ff05f78fd24d4c5898ee6e3f83-le64.cache-4.LCK"
 pid=3368 comm="firefox" requested_mask="l" denied_mask="l" fsuid=1000 
ouid=1000 
target="/home/santiago/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/.cache/fontconfig/889ed3ff05f78fd24d4c5898ee6e3f83-le64.cache-4.TMP-gDvyzg"
audit: type=1400 audit(1457440409.052:149): apparmor="DENIED" 
operation="file_mmap" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 
name="/home/santiago/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/TorBrowser/Tor/libgmp.so.10"
 pid=3368 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=1000
audit: type=1400 audit(1457440409.364:150): apparmor="DENIED" operation="link" 
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox"
 
name="/home/santiago/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/.cache/fontconfig/889ed3ff05f78fd24d4c5898ee6e3f83-le64.cache-4.LCK"
 pid=3368 comm="firefox" requested_mask="l" denied_mask="l" fsuid=1000 
ouid=1000 
target="/home/santiago/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/.cache/fontconfig/889ed3ff05f78fd24d4c5898ee6e3f83-le64.cache-4.TMP-M4Ed4Q"

I still need to aa-disable /etc/apparmor.d/torbrowser.*

Cheers,

Santiago

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 filled by Gunnar Wolf in Debian some time
> > ago:
> >
> > "It seems that whenever egrep finds something it cannot digest inside a
> > character class, it spews out the same error string: «Unmatched [ or [^».
> > This can be misleading and opens the way for long debugging time,
> > specially when trying to understand complex regexes. To illustrate the
> > point:
> >
> > $ echo | egrep -v '[[:digit]]+'
> > egrep: Unmatched [ or [^
> >
> > The brackets _are_ balanced, however the character class is not (it
> > lacks a finishing colon)."
> 
> Thank you for forwarding that.
> The diagnostic was fixed in gnulib via a commit last month:
> git.savannah.gnu.org/cgit/gnulib.git/commit/?id=7c6e85cf4eccbd5129
> Thus, as long as grep is configured --with-included-regex,
> you will now see this:
> 
>   $ grep -E '[[:digit]]+'
>   grep: Unmatched [, [^, [:, [., or [=
> 
> If grep is configure with --without-included-regex, you will
> still see the inferior diagnostic, but that string will then be
> coming from your system's C library.
> 
> Since fixing glibc's copy of regcomp.c is outside the scope
> of grep's issue tracker, I'm marking this as "done".

Thanks for you answer, Jim. I'm then filling a bug against Debian's
glibc.

Cheers,

Santiago

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 problem by configuring
> --with-included-regex. That has some other undesirable properties, though.
> 
> This is really a glibc bug
>  and the glibc patch
> could be applied to the Debian copy of glibc. Here's the patch:
> 
> http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=5513b40999149090987a0341c018d05d3eea1272
> 
> In other words, Debian bug #186568 is really a glibc bug, not a grep bug.
> Can you please fix the Debian bug report accordingly? I'll CC: this message
> there.

Paul, thanks for the info. I am answering to the mail, including the
control commands to reassign the bug to glibc.

Cheers,

Santiago


signature.asc
Description: Digital signature

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 using v2.23 with only the above commit reverted
> avoids the problem (see attached patch for my exact conflict resolution).
> 
> I also tested building the debian grep package with the patch attached.
> As expected that also avoids the issue. Attached debdiff.
> 
> I hope this can be used as an interim fix to avoid pkg-gnome packages
> loosing Uploaders information until someone with deeper knowledge can
> dive into whats causing the problem in the upstream change.
> 
> Regards,
> Andreas Henriksson

Thanks for working on this. However, I am not sure that reverting that
commit is the right way to solve the issue. grep is less and less
tolerant against invalid unicode characters. Maybe are there invalid
characters in the debian/* files where uploaders.mk get the info to fill
the Uploaders field? What package were you trying to build?

I would like to collect more info to forward the bug to upstream.

Cheers,

Santiago


signature.asc
Description: Digital signature