Bug#1016759: easy-rsa: regression?: Conflicting 'vars' files found

Control: tags -1 fixed-upstream Teco Boot wrote on Mon, 15 Aug 2022 14:59 +00:00: > It is fixed upstream in Merge branch 'TinCanTech-fix-make-cadir' > > See >

Bug#1016759: easy-rsa: regression?: Conflicting 'vars' files found

Package: easy-rsa Version: 3.1.0-0.1 Severity: normal Dear Maintainer, Consider the following sequence of commands: % make-cadir foo % cd foo % ./easyrsa init-pki % ./easyrsa build-ca In a fresh bullseye chroot (3.0.8-1), that sequence succeeds: CA creation complete and

Bug#1014383: [Pkg-zsh-devel] Bug#1014383: zsh: "IOT instruction" on SIGABRT

Control: tags -1 upstream Jakub Wilk wrote on Tue, 05 Jul 2022 08:40 +00:00: > The message zsh prints when a process aborts is confusing: > >% perl -MPOSIX -e'abort()' >zsh: IOT instruction perl -MPOSIX -e'abort()' > > I happen to know that SIGIOT == SIGABRT on Linux, but I guess most >

Bug#909124: quilt: Please fail gracefully on 'quilt series' when less(1) is not installed

Control: clone 909124 -2 Control: severity -2 normal Control: retitle -2 quilt: don't set QUILT_PAGER=less when $LESS is set Control: tags -2 upstream Control: found -2 0.66-2.1 Control: tags 909124 upstream patch Control: found 909124 0.66-2.1 Control: severity 909124 minor Trent W. Buck wrote

Bug#1007188: [Pkg-zsh-devel] Bug#1007188: zsh: completion for "info -f" does not work

Control: forwarded -1 https://www.zsh.org/workers/49849 Vincent Lefevre wrote on Tue, Mar 15, 2022 at 18:33:27 +0100: > Control: forwarded -1 https://www.zsh.org/mla/workers/2022/msg00179.html > > This also occurs with zsh from upstream's Git repository. Thanks, Vincent. Daniel (The link is to

Bug#1007188: [Pkg-zsh-devel] Bug#1007188: zsh: completion for "info -f" does not work

Control: reassign -1 zsh-common 5.8.1-1 Control: tags -1 upstream Could you please forward this upstream (and tag forwarded)?

Bug#1006345: postfix: fix configuration parameter name in README.Debian

Package: postfix Version: 3.6.4-1 Severity: minor Tags: patch Control: found -1 3.4.14-0+deb10u1 Control: found -1 3.5.13-1 Dear Maintainer, The name of a configuration parameter is misspelled: [[[ diff --git a/debian/README.Debian b/debian/README.Debian index a4a42884..7baf0c43 100644 ---

Bug#1006331: www.debian.org: please set charset=utf-8 for vote tally *.txt files

Package: www.debian.org Severity: minor Dear Maintainer, contains UTF-8 in various DDs' names. The file is served with "Content-Type: text/plain" and has no BOM, so browsers have to guess the encoding. Please consider serving the file as

Bug#1006235: stgit: please re-enable the interactive tests

Source: stgit Version: 0.19-1 Severity: normal Tags: patch Dear Maintainer, One of the Debian changes (debian/patches/*) disables part of the test suite. Please consider the following patch so the entire test suite runs. It deletes debian/patches/disable_interactive_test and extends

Bug#1004341: mercurial-common: please add contrib/zsh_completion to d/copyright

Package: mercurial-common Version: 6.0.1-3 Severity: wishlist Tags: newcomer Dear Maintainer, Please add contrib/zsh_completion's license (lines 19:34) to debian/copyright. Thanks, Daniel P.S. I wasn't sure whether this is a wishlist bug (since the license seems to be compatible with license

Bug#934926: [Pkg-zsh-devel] Bug#934926: update (overridding of default fpath causes uncessary complexity and pain for software providing zsh completions)

Axel Beckert wrote on Sun, Jan 09, 2022 at 08:52:04 +0100: > Daniel Shahaf wrote: > > […], or /etc/zsh/zshrc.d/ could be added (there's a separate ticket > > for that but my quick grep didn't find it), > > You probably had https://bugs.debian.org/776663 in mind which has bee

Bug#934926: update

Joey Hess wrote on Sat, Jan 08, 2022 at 16:27:53 -0400: > The simple fact is that as an upstream author who used the debian > locations because they were the ones that worked on my system, I get bug > reports from users of other systems that it's not right for wider uses > of zsh. And Debian seems

Bug#941214: [Pkg-zsh-devel] Bug#941214: mutt zsh completion broken, -a does not take email address

martin f krafft wrote on Fri, Dec 31, 2021 at 15:26:24 +1300: > Regarding the following, written by "Daniel Shahaf" on 2021-12-31 at 02:16 > Uhr +: > > The two consecutive colons on the -a line mean the -a option takes an > > optional argument.

Bug#941214: [Pkg-zsh-devel] Bug#941214: mutt zsh completion broken, -a does not take email address

David Bremner wrote on Sun, Dec 26, 2021 at 07:54:35 -0400: > David Bremner writes: > > > martin f krafft writes: > > > >> Package: notmuch > >> Version: 0.29.1-2 > >> Severity: normal > >> File: /usr/share/zsh/vendor-completions/_email-notmuch > >> > >> mutt has a command-line switch '-a' for

Bug#802872: graphicsmagick: SVG to PNG conversion omits circles

Control: forwarded -1 https://sourceforge.net/p/graphicsmagick/bugs/322/ Control: tags -1 fixed-upstream Bob Friesenhahn wrote on Sat, Oct 24, 2015 at 12:11:42 -0500: > GraphicsMagick bug 322 has been opened at SourceForge to track this issue. And has been fixed in the meantime: [quoting

Bug#1002469: graphicsmagick: convert: SVG->PNG conversion shifts image left mostly off canvas; possibly because of a 'rotate' transform?

Package: graphicsmagick Version: 1.4+really1.3.37-1 Severity: normal Tags: upstream Dear Maintainer, * What exactly did you do (or not do) that was effective (or ineffective)? % wget

Bug#999918: zsh: depends on obsolete pcre3 library

Control: tags -1 upstream Good morning Matthew, Matthew Vernon wrote on Thu, Nov 18, 2021 at 11:49:09 +: > The newer PCRE2 library was first released in 2015, and has been in > Debian since stretch. Upstream's documentation for PCRE2 is available > here: https://pcre.org/current/doc/html/

Bug#138691: zsh: completion for man should find filenames as well as man pages

Vincent Lefevre wrote on Sun, Aug 01, 2021 at 22:27:38 +0200: > As this very old bug is still open... > > On 2002-03-18 11:45:08 -0500, Matt Zimmerman wrote: > > On Mon, Mar 18, 2002 at 11:06:15AM -0500, Clint Adams wrote: > > > > > > When the -l option is given, man will open and display a man

Bug#986103: in package dpkg marked as pending

Guillem Jover wrote on Sun, May 16, 2021 at 02:33:43 +0200: > scripts: Add zsh completions for dpkg-parsechangelog > > [guil...@debian.org: Hook into build system. ] Thanks, Guillem! > Closes: #986103 > Signed-off-by: Guillem Jover

Bug#986580: zsh-doc: Please install Misc/vcs_info-examples

Package: zsh-common Version: 5.8-6 Severity: wishlist Tags: upstream Dear Maintainer, As the subject says, please install Misc/vcs_info-examples as documentation examples (presumably to /usr/share/doc/zsh/examples?). Tagging this upstream in case this is better fixed in upstream's «make

Bug#986103: dpkg-parsechangelog: please add zsh completion

Package: dpkg-dev Version: 1.20.8 Severity: wishlist Tags: patch upstream Dear Maintainer, * What led up to the situation? «dpkg-parsechangelog -S » and «dpkg-parsechangelog -F » don't currently have zsh completion. * What exactly did you do (or not do) that was effective (or

Bug#964971: lintian: please consider new check: expired keys in debian/upstream/signing-key.asc

Good morning Felix, Felix Lechner wrote on Tue, Mar 23, 2021 at 14:16:26 -0700: > Hi Daniel, > > On Mon, Jul 13, 2020 at 8:27 AM Daniel Shahaf wrote: > > > > a debian/upstream/signing-key.asc file > > which contains an expired snapshot of upstream's signing key

Bug#970848: [Pkg-zsh-devel] Bug#970848: Problem with path to completion scripts

Frank Terbeck wrote on Fri, 25 Sep 2020 00:02 +0200: > Georgy Komarov wrote: > > I encountered with a problem, when trying to use custom zsh completions. > > As debian/README.Debian states: > > Load-path for functions from other packages > --- > > In

Bug#969305: [Pkg-zsh-devel] Bug#969305: Bug#969305: zsh: safe-rm needs to be added to the default path of interactive shells to work

Francois Marier wrote on Mon, 31 Aug 2020 12:04 -0700: > On 2020-08-31 at 04:41:56, Daniel Shahaf wrote: > > I guess it should be in the zprofile file, guarded by a [[ -o interactive > > ]] check. > > From the comment in /etc/zsh/zshrc: > > # This file is sourced

Bug#969305: [Pkg-zsh-devel] Bug#969305: zsh: safe-rm needs to be added to the default path of interactive shells to work

Control: affects -1 safe-rm Francois Marier wrote on Sun, Aug 30, 2020 at 19:50:10 -0700: > This isn't really a bug in zsh, but rather I'd like to figure out how to > best enable the safe-rm package for zsh users. Thanks! > As far as I can tell, the equivalent to protect zsh users who choose to

Bug#963253: Processed: forcibly merging 963253 954772

Debian Bug Tracking System wrote on Sun, Aug 16, 2020 at 08:57:10 +: > Processing commands for cont...@bugs.debian.org: > > > forcemerge 963253 954772 > Bug #963253 [mercurial-common] mercurial-common: please install zsh > completion where zsh finds it > Bug #963253 [mercurial-common]

Bug#964971: lintian: please consider new check: expired keys in debian/upstream/signing-key.asc

Package: lintian Version: 2.83.0 Severity: wishlist Tags: upstream Dear Maintainer, I noticed yesterday that the current source package of zsh-syntax-highlighting contains a debian/upstream/signing-key.asc file which contains an expired snapshot of upstream's signing key: the snapshot gives the

Bug#960298: [Pkg-zsh-devel] Bug#960298: zsh-common: Please consider backporting new debsnap completion from upstream

Control: tags -1 pending Daniel Shahaf wrote on Mon, 11 May 2020 15:58 +: > It was posted in 45724, revised and committed in 45731, and has had an > unposted followup afterwards. I looked again and I can't find an unposted followup, so at Axel's suggestion I pushed a backport of

Bug#963253: mercurial-common: please install zsh completion where zsh finds it

Package: mercurial-common Version: 5.4-2 Severity: wishlist Control: affects -1 zsh-common Dear Maintainer, mercurial-common installs zsh completion to /usr/share/doc/mercurial-common/examples/zsh_completion.gz. Please install that file to /usr/share/zsh/vendor-completions/ instead, named

Bug#658198: Autocompletion: 'ls --n' first returns 'ls --n-g'.

A. Costa wrote on Tue, Jan 31, 2012 at 18:08:57 -0500: > Package: zsh > Version: 4.3.15-1 > Severity: minor > > Dear Maintainer, > > If I do: > > ls --n > > ...the first autocompletion from 'zsh' is: > > ls --n-g > > Of course 'ls' has no '--n-g' option. > No, but it does have

Bug#960298: [Pkg-zsh-devel] Bug#960298: Bug#960298: zsh-common: Please consider backporting new debsnap completion from upstream

Daniel Shahaf wrote on Mon, 11 May 2020 16:07 +: > Daniel Shahaf wrote on Mon, 11 May 2020 15:58 +: > > On the heels of #953389, which added _dscverify, shall we backport the > > newly-added _debsnap completion as well? > > > > It was posted in 45724, rev

Bug#962133: [Pkg-zsh-devel] Bug#962135: Bug#962135: patch for bugs 962133 and 962135

Vincent Lefevre wrote on Thu, 04 Jun 2020 10:03 +0200: > On 2020-06-04 03:32:49 +0000, Daniel Shahaf wrote: > > Furthermore, I'd rather not remove code just because it's currently > > unused in zsh.git. The completion system — especially the Type/* > > functions — is an API,

Bug#962133: [Pkg-zsh-devel] Bug#962133: Bug#962133: zsh-common: missing package in "dpkg -s" completion

Vincent Lefevre wrote on Wed, 03 Jun 2020 18:02 +0200: > On 2020-06-03 17:45:11 +0200, Axel Beckert wrote: > > Vincent Lefevre wrote: > > > Actually there's another one: > > > > > > zira:~> dpkg -l | grep '^rc' > > > rc openntpd 1:6.0p1-1

Bug#962133: [Pkg-zsh-devel] Bug#962135: Bug#962135: patch for bugs 962133 and 962135

Vincent Lefevre wrote on Wed, 03 Jun 2020 21:14 +0200: > On 2020-06-03 20:28:11 +0200, Axel Beckert wrote: > > Daniel: Would you review it for upstream inclusion? Sure. > Note that this is not documented, so I thought that this was just > internal, and 3rd party code should have its own

Bug#961757: zsh-doc: Please install the FAQ

Package: zsh-doc Version: 5.8-4 Severity: wishlist Dear Maintainer, Please consider building and installing the upstream FAQ as well. Currently, the following get installed: usr/share/doc/zsh-common/html/The-Zsh-FAQ.html usr/share/doc/zsh-common/META-FAQ But neither of these is the FAQ. The

Bug#954113: bug 954113 is forwarded to https://github.com/vim-perl/vim-perl/pull/286 ...

James McCoy wrote on Mon, May 11, 2020 at 22:39:14 -0400: > forwarded 954113 https://github.com/vim-perl/vim-perl/pull/286 > forwarded 954016 https://github.com/vim-perl/vim-perl/pull/285 Thanks for extending #954113 into a proper ftplugin! And for upstreaming these two, of course ☺ > thanks >

Bug#960298: [Pkg-zsh-devel] Bug#960298: zsh-common: Please consider backporting new debsnap completion from upstream

Daniel Shahaf wrote on Mon, 11 May 2020 15:58 +: > On the heels of #953389, which added _dscverify, shall we backport the > newly-added _debsnap completion as well? > > It was posted in 45724, revised and committed in 45731, and has had an > unposted followup afterwards.

Bug#960298: zsh-common: Please consider backporting new debsnap completion from upstream

Package: zsh-common Version: 5.8-4 Severity: wishlist Tags: patch Dear Maintainer, On the heels of #953389, which added _dscverify, shall we backport the newly-added _debsnap completion as well? It was posted in 45724, revised and committed in 45731, and has had an unposted followup afterwards.

Bug#960282: [Pkg-zsh-devel] Bug#960282: Bug#960282: Bug#960282: zsh: completion error with non exsiting files since deca7c928520fba5a73383f1cac0b3ace8e0e45d

Axel Beckert wrote on Mon, 11 May 2020 17:01 +0200: > Daniel Shahaf wrote: > > Daniel Shahaf wrote on Mon, 11 May 2020 14:29 +: > > > using _arguments from git HEAD with zsh 5.8-4 [...] is not a > > > supported use case. > > Is this something that might

Bug#960282: [Pkg-zsh-devel] Bug#960282: zsh: completion error with non exsiting files since deca7c928520fba5a73383f1cac0b3ace8e0e45d

Daniel Shahaf wrote on Mon, 11 May 2020 14:29 +: > using _arguments from git HEAD with zsh 5.8-4 [...] is not a > supported use case. Citation: workers/37986. Cheers, Daniel

Bug#960282: [Pkg-zsh-devel] Bug#960282: zsh: completion error with non exsiting files since deca7c928520fba5a73383f1cac0b3ace8e0e45d

> Version: 5.8-4 ⋮ > _arguments:comparguments:393: too many arguments In version 5.8-4, line 393 of _arguments doesn't call comparguments. > after deleting $opt_args_use_NUL_separators from _arguments: You seem to be using _arguments from git HEAD with zsh 5.8-4. That is not a supported use

Bug#956921: subversion: Debian patch last-changed-date-charset has an error leak

Source: subversion Version: 1.13.0-3 Severity: normal Tags: patch Good morning James, One of the Debian patches has a error leak: [[[ --- debian/patches/last-changed-date-charset +++ debian/patches/last-changed-date-charset @@ -24,7 +24,7 @@ index c8c3018..b69f90a 100644 + { +

Bug#956497: ristretto: 25 seconds delay when org.Xfce.FileManager isn't available

Control: retitle -1 ristretto: 25 seconds delay when org.Xfce.FileManager isn't available Daniel Shahaf wrote on Sun, Apr 12, 2020 at 03:59:07 +: > I captured a backtrace (from a different ristretto run, because lldb > failed to attached to the strace'd run): > > * thr

Bug#956497: ristretto: 25 seconds delay when starting under openbox

Package: ristretto Version: 0.8.3-1 Severity: important Dear Maintainer, When I run «ristretto» under Openbox, there is a 25s delay before the window opens. That doesn't happen under XFCE. - I tried to run ristretto with and without command-line arguments. That did not affect the outcome.

Bug#955186: pbuilder: please have --login run the default login shell, when not bash

Daniel Shahaf wrote on Sat, Mar 28, 2020 at 01:50:38 +: > Please execute the passwd(5)-specified login shell by default. > > The following works for me, but please review. > Need to set $SHELL too. Revised patch: [[[ diff --git a/pbuilder b/pbuilder index ccd7cc0..30

Bug#955186: pbuilder: please have --login run the default login shell, when not bash

Package: pbuilder Version: 0.230.4 Severity: wishlist Tags: upstream patch Dear Maintainer, «pbuilder --login» is implemented as follows: 58 --login|login|l) ⋮ 76 executehooks "F" 77 (${CHROOTEXEC} bash -c 'exec -a -bash bash') 78 RET=$? This

Bug#954772: mercurial-common: Please install zsh completion where zsh will find it

Package: mercurial-common Version: 5.3.1-1 Severity: normal Control: affects -1 zsh-common Dear Maintainer, mercurial-common installs contrib/zsh_completion to /usr/share/doc/mercurial-common/examples/zsh_completion.gz. Please install it to /usr/share/zsh/vendor-completions, uncompressed. This

Bug#954016: vim-runtime: tap.vim: Make "TODO" and "SKIP" case-insensitive

Daniel Shahaf wrote on Sun, Mar 15, 2020 at 18:59:29 +: > P.S. I think there are at least two other bugs in tap.vim: (1) As > mentioned above, TAP syntax is not highlighted unless there is an empty > line above the plan line; (2) syntax/tap.vim sets various fold.* options > glob

Bug#954113: vim-runtime: tap.vim: Don't clobber global settings of fold.* options

Package: vim Version: 2:8.2.0368-1 Severity: normal Tags: patch upstream Dear Maintainer, syntax/tap.vim uses «:set foo» to set window-local options. That changes the default setting of those options for new buffers. Here is a patch to fix that: [[[ diff --git a/runtime/syntax/tap.vim

Bug#954016: vim-runtime: tap.vim: Make "TODO" and "SKIP" case-insensitive

Package: vim Version: 2:8.2.0368-1 Severity: normal Tags: patch upstream Dear Maintainer, * What led up to the situation? According to the TAP specification, the keywords "TODO" and "SKIP" are case-insensitive: https://testanything.org/tap-specification.html#directives Directives

Bug#953911: debian-policy: clarify documentation of "Closes: #NNNNNN" changelog syntax

Guillem Jover wrote on Sat, 14 Mar 2020 22:51 +00:00: > Hi! > > On Sat, 2020-03-14 at 21:49:12 +0000, Daniel Shahaf wrote: > > Sean Whitton wrote on Sat, 14 Mar 2020 20:39 +00:00: > > > On Sat 14 Mar 2020 at 08:09PM +00, Daniel Shahaf wrote: > > > > Daniel Sh

Bug#953911: debian-policy: clarify documentation of "Closes: #NNNNNN" changelog syntax

Sean Whitton wrote on Sat, 14 Mar 2020 20:39 +00:00: > Hello, > > On Sat 14 Mar 2020 at 08:09PM +00, Daniel Shahaf wrote: > > > Daniel Shahaf wrote on Sat, 14 Mar 2020 18:14 +00:00: > >> - :: > >> - > >> - /closes:\s*(?:bug)?\#?\s?\d+(?:

Bug#951911: debian-policy: clarify documentation of "Closes: #NNNNNN" changelog syntax

Daniel Shahaf wrote on Sat, 14 Mar 2020 19:57 +00:00: > ... Sorry for the noise! I typo'd the bug number in the To: header ☹

Bug#953911: debian-policy: clarify documentation of "Closes: #NNNNNN" changelog syntax

Daniel Shahaf wrote on Sat, 14 Mar 2020 18:14 +00:00: > - :: > - > - /closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i > - > + All of the bug numbers listed must be given on the same physical line > + as the word ``closes:``. Is this newly-added sentence

Bug#951911: debian-policy: clarify documentation of "Closes: #NNNNNN" changelog syntax

Daniel Shahaf wrote on Sat, 14 Mar 2020 18:14 +00:00: > - :: > - > - /closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i > - > + All of the bug numbers listed must be given on the same physical line > + as the word ``closes:``. Is this newly-added sentence

Bug#953911: debian-policy: clarify documentation of "Closes: #NNNNNN" changelog syntax

Sean Whitton wrote on Sat, 14 Mar 2020 19:06 +00:00: > Hello Daniel, > > On Sat 14 Mar 2020 at 06:14PM +00, Daniel Shahaf wrote: > > > The documentation of the "Closes: #NN" changelog syntax describes > > the syntax in terms of a Perl regular expression.

Bug#953911: debian-policy: clarify documentation of "Closes: #NNNNNN" changelog syntax

Package: debian-policy Version: 4.5.0.0 Severity: wishlist Tags: patch upstream Dear Maintainer, The documentation of the "Closes: #NN" changelog syntax describes the syntax in terms of a Perl regular expression. However, not all readers know Perl. I suggest to describe the semantics in

Bug#953805: zsh-syntax-highlighting: Please make another source-only upload to allow testing migration

Boyuan Yang wrote on Fri, 13 Mar 2020 13:55 -0400: > Source: zsh-syntax-highlighting > Version: 0.7.1-1 > Severity: important > X-Debbugs-CC: danie...@apache.org > > Dear zsh-syntax-highlighting maintainers, > > The latest upload of your package was not a source-only upload. As a result, > it

Bug#953732: debian-security-support: revert unintentional output change in #951874 4/4

: 0a0a .. % dash -c 'echo ""' | xxd : 0a . % The following patch fixes the regression: 8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<-- >From 251a86c3

Bug#953389: [Pkg-zsh-devel] Processed: Fwd: [zsh:code] New commit [0d7f88] by Romain Porte

Debian Bug Tracking System wrote on Tue, 10 Mar 2020 15:48 +00:00: > Processing commands for cont...@bugs.debian.org: > > tag 953389 fixed-upstream > Bug #953389 [zsh-common] zsh-common: completion for dscverify is missing > Added tag(s) fixed-upstream. The upstream commit hash was recorded in

Bug#953389: [Pkg-zsh-devel] Bug#953389: Bug#953389: zsh-common: completion for dscverify is missing

Control: forwarded -1 workers/45524 Romain Porte wrote on Mon, 09 Mar 2020 14:45 +00:00: > 09/03/2020 15:04, Daniel Shahaf : > >> +'*:dsc file:_files -g "*.{changes,dsc}(-.)"' > > In this line — > > > > 1. You may need to change «{foo,bar}» to «

Bug#953389: [Pkg-zsh-devel] Bug#953389: Bug#953389: zsh-common: completion for dscverify is missing

Romain Porte wrote on Mon, Mar 09, 2020 at 10:33:29 +0100: > Hello, > > 09/03/2020 02:51, Daniel Shahaf : > > Thanks. Upstreaming would consist of emailing the patch to > > zsh-work...@zsh.org and updating the metadata on this bug. However, > > have you consider

Bug#953389: [Pkg-zsh-devel] Bug#953389: zsh-common: completion for dscverify is missing

Control: tags -1 confirmed Control: affects -1 devscripts Romain Porte wrote on Sun, 08 Mar 2020 21:50 +0100: > I would be happy to help in the upstreaming process if you find it > welcome. I prefer to create this bug first to avoid duplicate work > and because this completion is Debian-specific,

Bug#952283: Bug#951874: debian-security-support: Miscellaneous sh fixes

Pirate Praveen wrote on Mon, 24 Feb 2020 10:18 +0530: > On Sun, 23 Feb 2020 18:03:30 +0000 Daniel Shahaf wrote: > > Holger Levsen wrote on Sun, 23 Feb 2020 16:21 +: > > > On Sun, Feb 23, 2020 at 03:51:58PM +0000, Daniel Shahaf wrote: > > > > Alternatively,

Bug#951874: debian-security-support: Miscellaneous sh fixes

Daniel Shahaf wrote on Sun, 23 Feb 2020 18:03 +: > Holger Levsen wrote on Sun, 23 Feb 2020 16:21 +: > > On Sun, Feb 23, 2020 at 03:51:58PM +0000, Daniel Shahaf wrote: > > > Alternatively, how about deleting the «exit 0» line entirely? That > > > would effe

Bug#951874: debian-security-support: Miscellaneous sh fixes

Holger Levsen wrote on Sun, 23 Feb 2020 16:21 +: > On Sun, Feb 23, 2020 at 03:51:58PM +0000, Daniel Shahaf wrote: > > Alternatively, how about deleting the «exit 0» line entirely? That > > would effectively downgrade the error message to a warning. > > sounds bette

Bug#951874: debian-security-support: Miscellaneous sh fixes

020 at 03:38:15PM +0000, Daniel Shahaf wrote: > > Following up on #951772, here are a few more bugfixes: > > Subject: [PATCH 1/4] Clarify an error message > > Subject: [PATCH 2/4] Fix --version output: used an undefined variable. > > Subject: [PATCH 3/4] Print errors and wa

Bug#951874: debian-security-support: Miscellaneous sh fixes

Package: debian-security-support Version: 2020.02.21 Tags: upstream patch Good morning Holger, Following up on #951772, here are a few more bugfixes: [[[ >From d96f69e8ed2eef988c4b2fab24dc43cc1fc672d3 Mon Sep 17 00:00:00 2001 From: Daniel Shahaf Date: Sat, 22 Feb 2020 15:29:06 + Subj

Bug#951772: debian-security-support: Please sign error messages

Control: tags -1 patch Holger Levsen wrote on Fri, Feb 21, 2020 at 15:38:38 +: > Hi Daniel, > > On Fri, Feb 21, 2020 at 03:25:34PM +0000, Daniel Shahaf wrote: > > Please prefix "check-support-status: " to the error message. > > Can I have a patch, please? Th

Bug#951442: marked as pending in debian-security-support

Perhaps add a comment as well? — --- a/check-support-status.in +++ b/check-support-status.in @@ -252,6 +252,7 @@ cat "$INTERSECTION_LIST" | while read SRC_NAME ; do [% AWK %] '($3=="'"$SRC_NAME"'"){print $1" "$2}' "$INSTALLED_LIST" | \ while read BIN_NAME BIN_VERSION ; do +#

Bug#951442: debian-security-support: Please allow to exclude specific packages from the check

Holger Levsen wrote on Fri, 21 Feb 2020 13:40 +00:00: > On Fri, Feb 21, 2020 at 11:04:48AM +0000, Daniel Shahaf wrote: > > Here you go: > [...] > > thanks, looks good to me now! Great, thanks for the quick turnaround! I'm building this now for buster and will update my lo

Bug#951772: debian-security-support: Please sign error messages

Package: debian-security-support Version: 2019.12.12~deb10u1 Severity: minor Tags: upstream confirmed # Confirmed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951442#40 Dear Maintainer, In the following case: % check-support-status --type foo E: Unknown --type 'foo' %

Bug#951442: debian-security-support: Please allow to exclude specific packages from the check

> > > > I'm not sure if the handling of the ":amd64" architecture suffixes is > > > > ideal. Thoughts? > > Okay, so what would you prefer? To have --except=foo match both > > foo and foo:bar for any value of bar? (and 'foo' documented as > > a bare package name without a ":arch" suffix) > >

Bug#951442: debian-security-support: Please allow to exclude specific packages from the check

Holger Levsen wrote on Fri, 21 Feb 2020 00:26 +00:00: > On Sun, Feb 16, 2020 at 07:35:39PM +0000, Daniel Shahaf wrote: > > > & patches welcome. > > Here you go, against current git: > > wheeehoo, very nice. > Thanks for the review! > just two comments: >

Bug#951442: debian-security-support: Please allow to exclude specific packages from the check

Controls: tags -1 confirmed patch Holger Levsen wrote on Sun, 16 Feb 2020 18:29 +: > On Sun, Feb 16, 2020 at 04:12:46PM +0000, Daniel Shahaf wrote: > > [...] Thus, in effect, it would let the admin "whitelist" > > known issues, so only new ones would be printed. >

Bug#951442: debian-security-support: Please allow to exclude specific packages from the check

Package: debian-security-support Version: 2019.12.12~deb10u1 Severity: wishlist Tags: upstream Dear Maintainer, * What led up to the situation? Two things: 1. I have installed binutils, which is Build-Essential and has limited security support (#948634). 2. I use «chronic -e sh -c

Bug#948986: aptitude search: please allow searching by component (main/contrib/non-free)

Package: aptitude Version: 0.8.12-1 Severity: wishlist Tags: upstream Dear Maintainer, Please add a search pattern ?component(…) that can be used as ?component(main), ?component(non-free), ?component(contrib). Thanks, Daniel

Bug#948634: debian-security-support: please elaborate on binutils' status

blocked 948634 with -1 > > On Sat, Jan 11, 2020 at 02:28:14AM +, Daniel Shahaf wrote: > > +++ b/security-support-limited > > @@ -7,7 +7,7 @@ > > -binutilsNot covered by security support > > +binutilsOnly suitable for trusted content; see > &g

Bug#948634: debian-security-support: please elaborate on binutils' status

Package: debian-security-support Version: 2019.06.13 Severity: important Tags: patch Control: affects -1 binutils Dear Maintainer, Now that binutils has limited security support, please elaborate on its status. Suggested patch (against current git): --- a/security-support-limited +++

Bug#948629: rpcbind: please say that the -r flag is a Debian extension

Package: rpcbind Version: 1.2.5-8 Severity: normal Tags: patch Dear Maintainer, Since the -r flag is added as a Debian patch, please document that it's a Debian extension. Here's the patch against current git: diff --git a/debian/patches/00-rmt-calls.patch b/debian/patches/00-rmt-calls.patch

Bug#733573: ssh: Doesn't use the key from -i when using an agent.

Kurt Roeckx wrote on Mon, Dec 30, 2013 at 01:53:39 +0100: > Package: openssh-client > Version: 1:6.4p1-1 > > Hi, > > When I use ssh with the -i option to use a different key, it seems > to be offering my default key anyway. It seems this is only the > case when an ssh-agent is running. The key

Bug#948445: release-notes: aptitude search for not-from-Debian package has false negatives

Justin B Rye wrote on Thu, Jan 09, 2020 at 12:02:19 +: > Andrei POPESCU wrote: > > The long form is quite self-explanatory, the short form is easier to > > type. > > > > Maybe both should be mentioned? > > Remember it's currently > > Below there are two methods for finding installed

Bug#948445: release-notes: aptitude search for not-from-Debian package has false negatives

Package: release-notes Severity: normal Tags: patch Dear Maintainer, §4.2 of the release notes¹ recommends to run «aptitude search '~i(!~ODebian)'». I suggest to change the search pattern to «'?narrow(~i, (!~ODebian))'». That will also catch packages that were backported directly from sid, or

Bug#948291: dpkg-buildpackage: please support --hook-foo=bar=baz

Package: dpkg-dev Version: 1.19.7 Severity: normal Tags: patch Dear Maintainer, [tl;dr: dpkg-buildpackage --hook-init=foo=bar errors out; patch attached.] * What led up to the situation? I was trying to build a package in a chroot and inject some additional flags into CFLAGS. * What

Bug#947120: vim-nox: :syn contains=TOP inside a :syn-include'd file refers to the outer file

Daniel Shahaf wrote on Sat, Dec 21, 2019 at 11:09:39 +: >* What was the outcome of this action? > > When the file iota is viewed with «set filetype=foo», the words "lorem > ipsum" on line 1 are not highlighted. > >* What outcome did you expect instead? >

Bug#947120: vim-nox: :syn contains=TOP inside a :syn-include'd file refers to the outer file

Package: vim-nox Version: 2:8.1.2269-1 Severity: normal Tags: upstream Dear Maintainer, * What led up to the situation? I wanted to write a custom syntax file that includes another syntax file. (Specifically, I wanted to write a syntax filefor zsh's test suite, and have it include the zsh

Bug#939194: [Pkg-zsh-devel] Bug#939194: zsh: git completion: does not know "git switch"

Control: tags -1 upstream Vincent Lefevre wrote on Mon, 02 Sep 2019 07:43 +00:00: > If I do "git sw[Tab]", zsh does not find any completion. > It should complete to "git switch". Please report this upstream if you haven't already.

Bug#934926: [Pkg-zsh-devel] Bug#934926: overridding of default fpath causes uncessary complexity and pain for software providing zsh completions

Joey Hess wrote on Fri, 16 Aug 2019 18:35 +00:00: > By default zsh loads completions from /usr/share/zsh/site-functions > and while the name of that is perhaps not great, as it's not > site-specific[1], it's a standard location. Debian has overridden this, > so zsh does not look there, but instead

Bug#863045: at: interactively please print parsed time at start

Jose M Calhariz wrote on Wed, 17 Jul 2019 19:09 +00:00: > as promised is here the patch. This is a draft so you can look into > the new message and say if you aprove it. The code is not optimized, > so I may change it a bit. > > +++ b/at.c > @@ -479,6 +479,11 @@ writefile(time_t runtimer, char

Bug#863045: at: interactively please print parsed time at start

Jose M Calhariz wrote on Wed, 17 Jul 2019 02:03 +00:00: > I am working in a new release of at and I have a draft of this > feature. If you are interested in beta testing it, I can prepare a > package for most releases of Debian on i386 ou amd64. Thanks for looking into this and for offering to

Bug#846278: Fix or workaround for Debian #846278

Robert Micsutka wrote on Sun, 16 Jun 2019 11:00 +00:00: > On Sat, 08 Jun 2019 10:21:31 +0000 "Daniel Shahaf" > wrote: > > You might be able to get around this by using the 'equivs' package: > > But after this you can not lock your screen anymore. > The qucik worka

Bug#846278: Fix or workaround for Debian #846278

Brian Doherty wrote on Fri, 07 Jun 2019 19:45 +00:00: > I don't have l3lock. If I try to purge light-locker, Lubuntu tries to > uninstall XFCE and install Gnome in its place :( You might be able to get around this by using the 'equivs' package: 1. cd "$(mktemp -d)" 2. apt install equivs 3.

Bug#924736: [Pkg-zsh-devel] Bug#924736: Bug#924736: zsh 5.7.1 segfaults when three setopt options are in play

wesl...@euronet.nl wrote on Sat, 23 Mar 2019 11:03 +00:00: > upstream seem to have fixed this bug with commit > 73b29f079b50412700727e0f77991506c03d19fe Thanks for the heads-up, Wesley. Axel already had annotated this bug with this information: > # Commit

Bug#921236: [Pkg-zsh-devel] Bug#921236: Bug#921236: zsh: provide equivalent of dh_bash-completion

Dmitry Bogatov wrote on Tue, 05 Feb 2019 16:15 +: > > [2019-02-03 13:39] Daniel Shahaf > > However, do note that some upstreams ship completion files that are > > inferior to those that ship with zsh itself. In such cases it would be > > desirable *not* to install t

Bug#921236: [Pkg-zsh-devel] Bug#921236: zsh: provide equivalent of dh_bash-completion

Dmitry Bogatov wrote on Sun, 03 Feb 2019 12:58 +: > Source: zsh > Severity: wishlist > > Dear Maintainer, > > please proived debhelper to install zsh completion scripts. Some of my > upstreams provide zsh scripts, but I, as non-user of zsh, have no idea, > how to install them properly. >

Bug#883453: xserver-xorg-input-libinput: xorg crash when waking-up from suspend to ram

Vincent Danjean wrote on Mon, Dec 04, 2017 at 09:40:55 +0100: > Package: xserver-xorg-input-libinput > Version: 0.26.0-1 > Severity: important > > Hi, > > When waking up from suspend to ram after several minutes, I get the unlock > screen from xscreensaver (I'm under XFCE with xcreensaver).

Bug#916021: [rb-general] Bug#916021: lintian: Please check for references to build directory

[fixing bug's address in Cc] Dmitry Bogatov wrote on Mon, 10 Dec 2018 19:49 +: > I believe, most of us keep repositories of git packages somewhere under > ~/. For example, for me, ucspi-tcp package is located at > /home/iu/devel/salsa/ucspi-tcp. > > So my workflow is following: > > $ cd

Bug#913862: vim-addon-manager: Add zsh completion

Package: vim-addon-manager Version: 0.5.6 Severity: wishlist Tags: patch upstream Control: affects -1 zsh-common Dear Maintainer, Please add zsh completion to vim-addon-manager by having the package install the following files: To /usr/share/zsh/vendor-completions/_vam: [[[ #compdef vam # Last

Bug#913860: editorconfig-core: man page does not describe semantics

Package: editorconfig-core Version: 0.12.1-1.1 Severity: minor Tags: upstream Dear Maintainer, The editorconfig(1) man page describes the syntax of the command, but not its semantics. The man page does say that the positional argument are filenames and that there must be at least one of them,

Bug#912756: diffoscope: Test failures with upcoming upstream file(1) version 5.35

Control: tags -1 patch Christoph Biedl wrote on Sat, Nov 03, 2018 at 16:13:58 +0100: > -diffoscope-104/tests/data/test2.pcap: tcpdump capture file (little-endian) - > version 2.4 (Ethernet, capture length 262144) > +diffoscope-104/tests/data/test2.pcap: pcap capture file, microsecond ts >

  1   2   3   4   >