| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Patch generated with `debchange --release'.
|
| |
|
| |
|
|
|
|
|
| |
The update was created with `gbp import-orig --pristine-tar --uscan',
this patch just updates the version information in debian/changelog.
|
|
|
|
| |
Patch generated with `debchange --increment'.
|
|
|
|
| |
Patch generated with `debchange --release --force-save-on-release'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Checked against the upgrade checklist:
4.9
The recommended way to implement the build process of a Debian
package, in the absence of a good reason to use a different
approach, is the dh tool. This recommendation includes the contents
of the debian/rules building script.
Some examples of good reasons to use a different approach are given.
The recommendation to use dh does not always apply, and use of dh is
not required.
OK, already using dh.
5.6.26
Permit -b in Vcs-Hg as well as Vcs-Git.
OK, vcs field is of git type and doesn't use -b anyway.
7.5
Document versioned Provides.
OK, not using Provides.
virtual
New logind and default-logind virtual packages for a package
providing logind API (via D-Bus and sd-login(3)), and for Debian’s
preferred implementation, respectively.
OK, not providing logind API.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Checked against the upgrade checklist:
2.3 & 4.5
In cases where a package’s distribution license explicitly permits
its copyright information to be excluded from distributions of
binaries built from the source, a verbatim copy of the package’s
copyright information should normally still be included in the
copyright file, but it need not be if creating and maintaining a
copy of that information involves significant time and effort.
OK - All files under GPL-2+, which is distributed by Debian.
4.9
Required targets must not write outside of the unpacked source
package tree, except for TMPDIR, /tmp and /var/tmp.
OK - Build is contained within the build dir.
4.17
Packages should not contain a non-default series file. That is,
dpkg’s vendor-specific patch series feature should not be used for
packages in the Debian archive.
OK - Only debian/patches/series is present.
10.1
Binaries should be stripped using strip --strip-unneeded
--remove-section=.comment --remove-section=.note (as dh_strip
already does).
OK - No binaries distributed [arch=all].
10.1
It is no longer suggested nor recommended to use install -s to strip
binaries, because it gets several things wrong.
OK - No binaries distributed [arch=all].
10.2
When stripping shared libraries with strip(1), you should
additionally pass --remove-section=.comment --remove-section=.note
(as dh_strip already does).
OK - No binaries distributed [arch=all].
virtual
New dbus-session-bus and default-dbus-session-bus virtual packages
for a package providing the D-Bus session bus, and for Debian’s
preferred D-Bus implementation, respectively.
OK - Not related to bash-completion.
|
|
|
|
| |
Patch generated with `debchange --increment'.
|
|
|
|
| |
Patch generated with `debchange --release --force-save-on-release'.
|
|
|
|
|
|
|
|
|
| |
Both "apt install bash-completion" and "apt purge bash-completion"
generate the following warning:
find: '/etc/bash_completion.d/': No such file or directory
The cause is that postinst and postrm assume that
/etc/bash_completion.d exists.
|
|
|
|
| |
This is a backport from upstream
|
|
|
|
| |
Patch generated with `debchange --increment'.
|
|
|
|
| |
Patch generated with `debchange --release --force-save-on-release'.
|
|
|
|
|
|
|
|
|
|
|
| |
Debian patch 03-disable_avahi_browse.patch disables completion with
avahi-browse for everyone, even though it can be disabled with
environment variables (as a matter of fact, it is disabled by default
and can be enabled by setting COMP_KNOWN_HOSTS_WITH_AVAHI).
This commit removes the patch from Debian.
Thanks to Ville Skyttä for suggesting this.
|
|
|
|
|
|
| |
The previous four commits added new entries to debian/maintscript, which
collectively fix bug #645439. This patch adds this information to the
changelog.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The commit:
commit 75a48b26676a4912c6984c7822fecdfcf460bffe
Author: David Paleino <dapal@debian.org>
Date: Thu Nov 3 12:42:39 2011 +0100
Drop trigger-based completion loading
deleted the conffile /etc/cron.monthly/bash-completion, without updating
the maintainer scripts to purge the files.
This patch adds the files to debian/maintscript, setting the version to
the next release of bash-completion, as required by
dpkg-maintscript-helper:
rm_conffile conffile [prior-version [package]]
prior-version
Defines the latest version of the package whose upgrade should
trigger the operation. It is important to calculate prior-version
correctly so that the operations are correctly performed even if the
user rebuilt the package with a local version. If prior-version is
empty or omitted, then the operation is tried on every upgrade
(note: it's safer to give the version and have the operation tried
only once).
If the conffile has not been shipped for several versions, and you
are now modifying the maintainer scripts to clean up the obsolete
file, prior-version should be based on the version of the package
that you are now preparing, not the first version of the package
that lacked the conffile. This applies to all other actions in the
same way.
For example, for a conffile removed in version 2.0-1 of a package,
prior-version should be set to 2.0-1~. This will cause the conffile
to be removed even if the user rebuilt the previous version 1.0-1 as
1.0-1local1. Or a package switching a path from a symlink (shipped
in version 1.0-1) to a directory (shipped in version 2.0-1), but
only performing the actual switch in the maintainer scripts in
version 3.0-1, should set prior-version to 3.0-1~.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The commits:
commit 4bfa85b495bff991ee9d142f7584b2a1b198c344
Author: David Paleino <dapal@debian.org>
Date: Mon Apr 11 11:50:14 2011 +0200
Re-implement triggers
and
commit a98c7d29191dbd44a29b58623fa4fa8b4f7c6fcb
Author: David Paleino <dapal@debian.org>
Date: Sun Apr 10 15:53:39 2011 +0200
Fix cronscript name
deleted the conffiles /etc/apt/apt.conf.d/99-bash-completion and
/etc/cron.monthly/bash-completion.cron, respectively, without updating
the maintainer scripts to purge the files.
This patch adds the files to debian/maintscript, setting the version to
the next release of bash-completion, as required by
dpkg-maintscript-helper:
rm_conffile conffile [prior-version [package]]
prior-version
Defines the latest version of the package whose upgrade should
trigger the operation. It is important to calculate prior-version
correctly so that the operations are correctly performed even if the
user rebuilt the package with a local version. If prior-version is
empty or omitted, then the operation is tried on every upgrade
(note: it's safer to give the version and have the operation tried
only once).
If the conffile has not been shipped for several versions, and you
are now modifying the maintainer scripts to clean up the obsolete
file, prior-version should be based on the version of the package
that you are now preparing, not the first version of the package
that lacked the conffile. This applies to all other actions in the
same way.
For example, for a conffile removed in version 2.0-1 of a package,
prior-version should be set to 2.0-1~. This will cause the conffile
to be removed even if the user rebuilt the previous version 1.0-1 as
1.0-1local1. Or a package switching a path from a symlink (shipped
in version 1.0-1) to a directory (shipped in version 2.0-1), but
only performing the actual switch in the maintainer scripts in
version 3.0-1, should set prior-version to 3.0-1~.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The upgrade to upstream version 1.2
commit f9748115fb4b2950fb4df7535fb723c4affde078 (tag: upstream/1.2)
Author: David Paleino <dapal@debian.org>
Date: Wed Jun 16 18:20:29 2010 +0200
Imported Upstream version 1.2
deleted some completion files from /etc/bash_completion.d/, without
updating the maintainer scripts to purge the files.
This patch adds the files to debian/maintscript, setting the version to
the next release of bash-completion, as required by
dpkg-maintscript-helper:
rm_conffile conffile [prior-version [package]]
prior-version
Defines the latest version of the package whose upgrade should
trigger the operation. It is important to calculate prior-version
correctly so that the operations are correctly performed even if the
user rebuilt the package with a local version. If prior-version is
empty or omitted, then the operation is tried on every upgrade
(note: it's safer to give the version and have the operation tried
only once).
If the conffile has not been shipped for several versions, and you
are now modifying the maintainer scripts to clean up the obsolete
file, prior-version should be based on the version of the package
that you are now preparing, not the first version of the package
that lacked the conffile. This applies to all other actions in the
same way.
For example, for a conffile removed in version 2.0-1 of a package,
prior-version should be set to 2.0-1~. This will cause the conffile
to be removed even if the user rebuilt the previous version 1.0-1 as
1.0-1local1. Or a package switching a path from a symlink (shipped
in version 1.0-1) to a directory (shipped in version 2.0-1), but
only performing the actual switch in the maintainer scripts in
version 3.0-1, should set prior-version to 3.0-1~.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The upgrade to upstream version 1.1
commit e5a9b6220e93ca656fd9774c6aefa78241edca6f (tag: upstream/1.1)
Author: David Paleino <d.paleino@gmail.com>
Date: Sat Oct 10 17:15:58 2009 +0200
Imported Upstream version 1.1
deleted some completion files from /etc/bash_completion.d/, without
updating the maintainer scripts to purge the files.
This patch adds the files to debian/maintscript, setting the version to
the next release of bash-completion, as required by
dpkg-maintscript-helper:
rm_conffile conffile [prior-version [package]]
prior-version
Defines the latest version of the package whose upgrade should
trigger the operation. It is important to calculate prior-version
correctly so that the operations are correctly performed even if the
user rebuilt the package with a local version. If prior-version is
empty or omitted, then the operation is tried on every upgrade
(note: it's safer to give the version and have the operation tried
only once).
If the conffile has not been shipped for several versions, and you
are now modifying the maintainer scripts to clean up the obsolete
file, prior-version should be based on the version of the package
that you are now preparing, not the first version of the package
that lacked the conffile. This applies to all other actions in the
same way.
For example, for a conffile removed in version 2.0-1 of a package,
prior-version should be set to 2.0-1~. This will cause the conffile
to be removed even if the user rebuilt the previous version 1.0-1 as
1.0-1local1. Or a package switching a path from a symlink (shipped
in version 1.0-1) to a directory (shipped in version 2.0-1), but
only performing the actual switch in the maintainer scripts in
version 3.0-1, should set prior-version to 3.0-1~.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Debian commit:
commit 5506a39b0f16cee692f44c209a0d1a3b98fa969f
Author: Gabriel F. T. Gomes <gabriel@inconstante.eti.br>
Date: Sat Nov 24 15:25:42 2018 -0200
Fix perl completion with space between option and argument (bug #614775)
incorporated a fix for perl completions, however the fix was not fully
correct. This commit updates the patch.
Also fix an error with debian/changelog syntax for the relevant entry.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The original problem reported on bug #550676 affected version 1:1.1-1
and was fixed in version 1:1.3-1.
Afterwards, commented #45 added a similar, yet different complaint [1].
Upstream developers suggested the use of COMP_FILEDIR_FALLBACK, however
that doesn't work without an additional upstream fix [2]. This commit
incorporates the fix into Debian.
[1] https://bugs.debian.org/550676#45
[2] https://github.com/scop/bash-completion/pull/260
|
|
|
|
|
|
|
|
|
|
|
|
| |
As reported in Debian bug #614775 [1], perl commands are being completed
with erroneous syntax for the '-d', '-V', and '-M' options, where a
space between the option and the option argument is not allowed. This
is also true for the '-I' option. This commit fixes this problem with a
Debian patch, which has been forwarded upstream.
Thanks to Jeff King for reporting and providing a patch.
[1] https://bugs.debian.org/614775
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The commit:
commit 920bbb8582bcd3039ff4e4388e795e3144eb30b6
Author: Ville Skyttä <ville.skytta@iki.fi>
Date: Tue Nov 26 19:45:02 2013 +0200
wtf: Look for acronym db from /usr/share/games/bsdgames/acronyms too.
was incorporated into Debian's bash-completion version 2.7-1, which
fixed bug #731567, but this information was missing from the changelog.
|
|
|
|
| |
Signed-off-by: Niels Thykier <niels@thykier.net>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The NOOP promise enables dh(1) to skip the call to dh_bash-completion
when dh can conclude (from the promise and the situation) that
dh_bash-completion will be a NOOP.
In the particular case, we know that dh_bash-completion will do
nothing when there is no "bash-completion" pkgfile regardless of the
command-line options.
Signed-off-by: Niels Thykier <niels@thykier.net>
|
|
|
|
|
|
|
| |
The install_{dir,file} variants avoids a fork+exec sequence, which
makes them slightly more efficient.
Signed-off-by: Niels Thykier <niels@thykier.net>
|
|
|
|
| |
Signed-off-by: Niels Thykier <niels@thykier.net>
|
|
|
|
| |
Use `debchange --increment'.
|
|
|
|
| |
Use `debchange --release --force-save-on-release'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upstream noticed a missing piece in the patch added by the commit:
commit 77ed63519ff5631475a496af1c536d8484a613f6
Author: Gabriel F. T. Gomes <gabriel@inconstante.eti.br>
Date: Sat Nov 17 12:43:47 2018 -0200
Add support for tar zstd completion (bug #913949)
This commit updates the patch.
Thanks to Ville Skyttä for the review [1].
[1] https://github.com/scop/bash-completion/pull/255#pullrequestreview-176067588
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for completing tar commands with zstd
compression extensions (`.zst' and `.tzst'). Support for the
compression itself is available since tar-1.30+dfsg-3 [1].
Thanks to Adam Borowski for reporting.
[1] https://tracker.debian.org/news/1003756/accepted-tar-130dfsg-3-source-amd64-into-unstable/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds a new completion file to Debian's bash-completion. It
is based on the completion file for update-rc.d and was submitted by
Mathieu Roy [1] and adapted by myself.
The new completion file was forwarded upstream [2].
Thanks to Mathieu Roy for reporting and providing a patch.
[1] https://bugs.debian.org/865548#5
[2] https://github.com/scop/bash-completion/pull/254
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upstream commit:
commit 71ac42b98c0eba39819fb8478d6443032c6ef6f1
Author: Ville Skyttä <ville.skytta@iki.fi>
Date: Mon Mar 19 18:58:09 2018 +0200
_known_hosts_real: Reimplement known hosts file parsing in pure bash
reimplements completion of hostnames from ssh/known_hosts files. As a
side-effect, it also fixes Debian bug #848125.
Thanks to Vincent Danjean for reporting and to Ville Skyttä for
suggesting the backport.
|
|
|
|
| |
Use `debchange --increment'.
|
|
|
|
| |
Use `debchange --release --force-save-on-release'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upstream commit:
commit 6ffde95c7ea257ff60cb51a263a8d33f4bb0898b
Author: dmerge <25472575+dmerge@users.noreply.github.com>
Date: Fri Apr 20 22:14:08 2018 -0700
_filedir: Refactor to remove heredoc-dependent loop
refactors the function _filedir, and, perhaps accidentally, fixes
completion when wildcards are used.
The backport doesn't completely solve the problem of wildcard (`*')
completion, because wildcards never get expanded, even when a single
match is available, nor do options get listed when TAB is pressed twice.
To get that behaviour, the following patch would be needed:
$ diff -U4 /usr/share/bash-completion/bash_completion.BACKUP /usr/share/bash-completion/bash_completion
--- /usr/share/bash-completion/bash_completion.BACKUP 2018-11-10 17:34:08.432870898 -0200
+++ /usr/share/bash-completion/bash_completion 2018-11-10 17:34:12.304421632 -0200
@@ -587,8 +587,10 @@
if [[ ${#toks[@]} -ne 0 ]]; then
# 2>/dev/null for direct invocation, e.g. in the _filedir unit test
compopt -o filenames 2>/dev/null
COMPREPLY+=( "${toks[@]}" )
+ else
+ compopt -o bashdefault 2>/dev/null
fi
} # _filedir()
Since this extra fix could cause unpredicted, undesired side-effects,
further discussion is required.
|
|
|
|
|
|
|
|
|
| |
This reverts commit c4ea37493f4c7c287ea0b0048bb58635f855b7bf.
The discussion upstream [1] exposed some potential, undesired
side-effects that this fix could cause, hence the reversion.
[1] https://github.com/scop/bash-completion/pull/252#issuecomment-435928977
|
|
|
|
|
|
|
|
|
|
| |
Part of the fix in debian/patches/00-fix_quote_readline_by_ref.patch
causes completions after `$(' to fail. This commit removes the hunk
that causes the problem.
Thanks to Malte Skoruppa for providing details for the fix [1].
[1] https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1312243/comments/8
|
|
|
|
| |
Ran `debchange --increment'.
|
|
|
|
| |
Use `debchange --release --force-save-on-release'.
|
|
|
|
|
|
| |
Checked against the upgrade checklist (no changes required):
10.4: No perl scripts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Checked against the upgrade checklist (no changes required):
4.9: All commands in debian/rules are dh_* scripts that don't have
a --verbose option.
4.9: No network access..
4.9.1: Informational comment.
5.2:
5.4: Standards-Version is present.
12.7: No NEWS file upstream, only a very verbose changelog.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Checked against the upgrade checklist (no changes required):
4.9.2: Not using Rules-Requires-Root.
5.6.12: No new changes to Epoch.
5.6.12.1: No new changes to Epoch.
5.6.31: Not using Rules-Requires-Root.
9.1.1: All files under /etc, /usr/bin, and /usr/share.
The changes do not affect these directories.
9.3.2: Not a service.
10.4: Bash-completion is supposed to be run by bash not sh.
|
|
|
|
|
|
|
|
|
|
| |
Checked against the upgrade checklist (no changes required):
3.2.2: Bash-completion is not reusing version numbers.
4.9: Bash-completion does not use get-orig-source.
9.1.2: Bash-completion doesn't install files under /usr/local.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Paul Wise reported additional information [1] about the fix for man
completion. According to him, the upstream commit
commit e6a471511dfdc230ff3eed65ccba09b6d7d30262
Author: Pawel <pawel.veselov@gmail.com>
Date: Wed Sep 27 06:34:59 2017 +0200
man: Don't use $MANPATH directly (#161)
fixes the behavior of man completion when MANPATH is set, however, it
misses the following:
* falling back on `man --path` when the man implementation does not
have support for `manpath` and `man -w`
* falling back on $MANPATH when the man implementation does not have
support for printing the manual pages paths
Thanks to Paul Wise for reporting and providing a fix.
[1] https://bugs.debian.org/892307#27
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upstream release 2.8 contains the commit
commit 5ed2fc4a9a604c780da48e87964d4ac21fc7a85d
Author: Ville Skyttä <ville.skytta@iki.fi>
Date: Sun Jul 9 16:52:06 2017 +0300
aptitude: Add keep to commands list (Debian: #867587)
which fixes bug 867587 [1]. This commits updates the changelog
accordingly, however Debian's bash-completion version 2.8-1 has already
been release and uploaded into the archives, thus, the bug report has
not been automatically closed.
Thanks to Dan Jacobson for reporting.
[1] https://bugs.debian.org/892307
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tim Connors reported the bug in Debian [1] and the fix has been
implemented upstream [2]. However, a new version of bash-completion has
not yet been released, so Debian carries the fix.
Thanks to Tim Connors for reporting.
[1] https://bugs.debian.org/892080
[2] https://github.com/scop/bash-completion/commits/b0851c06d050
|
|
|
|
|
|
|
|
|
|
|
| |
Emmanouil Kampitakis prepared an NMU (versioned as 1:2.8-1.1) [1] and
uploaded it to Debian [2]. This patch incorporates the changes provided
by the NMU.
Thanks to Emmanouil Kampitakis.
[1] https://bugs.debian.org/910128#26
[2] https://bugs.debian.org/910128#36
|