Hi, Ivan and Alban,
Thank you very much for your reports. They certainly help me debug this large
update.
I see two different issues:
1. Missing _comp_deprecate* functions
Bash-completion 2.12 adds a new file to /etc/bash_completion.d
(/etc/bash_completion.d/000_bash_completion_compat.bash),
Upstream does not want this change
(https://github.com/scop/bash-completion/issues/442).
* Philipp Marek wrote:
> This sequence runs chromium and blocks the shell until the browser is closed
> again:
>
> $ chromium --
That doesn't happen on my system, either with or without chromium installed.
The completion file runs 'chromium --help' and that exits quickly. What happens
Hi again,
One of the project maintainers said [1] that the plan for a release is
still up. I'll try to help them with whatever spare time I can find.
Not sure if you are interested in doing that as well, but I wanted to
make a point that bash-completion is a very friendly community and
welcomes
Hi, Richy,
Erring on the side of caution, I just posted a comment [1] to the upstream
project, asking if the plan to release 2.12 is still alive. If they say yes,
then we might give them a hand with the remaining tasks to speed it up.
Otherwise, I'll plan some debian-only update in the lines
Control: reassign -1 libreoffice
Hi, I believe the libreoffice package produces its own completion files
(which is awesome), thus reassigning.
A patch for this would probably look like:
--- bin/generate-bash-completion.py 2023-06-19 18:32:31.988021669 -0700
+++
On Wed, 19 Apr 2023 22:45:21 +0300
Askar Safin wrote:
>
> (But I still think we should just make /etc/skel/.bashrc to be default
> /root/.bashrc . This will fix other possible "user vs root" bugs.
> Currently /root/.bashrc doesn't have any non-comment lines, i. e. it
> doesn't contain anything
On Wed, 19 Apr 2023 17:10:06 +0300
Askar Safin wrote:
> If I copy /etc/skel/.bashrc to /root/.bashrc , the bug disappears.
That's because /etc/skel/.bashrc directly source /etc/bash_completion.
With login shells, /etc/bash_completion gets sourced by something else.
I think we need to dig
Control: tags -1 confirmed
Steps to reproduce
$ su -# become root
# echo $0
-bash # this is a login shell
# apt-get inst
(completes)
# su root
# echo $0
bash # this is a non-login shell
# apt-get inst
(nothing happens)
I don't currently know what sources
Thanks, Sergio.
You're the best archaeologist! S2
On Mon, 10 Apr 2023 13:55:27 -0400
Sergio Durigan Junior wrote:
> On Monday, April 10 2023, Gabriel F. T. Gomes wrote:
>
> > When I took the maintainer role for bash-completion, I did a lot of bug
> > archaeology, but
On Mon, 10 Apr 2023 14:04:06 +0200
"Richard B. Kreckel" wrote:
>
> Regarding my hangs: It is because something's broken in my NIS
> (yellow-pages) setup (haven't fully analyzed yet). It turns out that,
> when doing tab completion, your patch 00-fix_quote_readline_by_ref.patch
> tries to match
Thanks, Matthias,
I submitted a patch upstream to get the feedback from the upstream [1]
developers. I hope they accept it; if they do, it's easier for me to
backport. Cheers, Gabriel.
[1] https://github.com/scop/bash-completion/pull/922
On Wed, 29 Mar 2023 11:40:09 +0200
Matthias Geerdsen
Hi Richard,
thanks for your report.
With respect to the package being outdated, I realize that the sources
have not been sync'd with upstream for a long while, but that's because
upstream has not released any versions (no tags) since 2.11; and I
always wait for upstream releases before syncing.
:
On Tue, 4 Feb 2020 23:10:06 -0300 "Gabriel F. T. Gomes" wrote:
I maintain pragha, which depends on this package, so I'll adopt it.
It is now 1.5 years since you filed the ITA. There is a new upstream version
that is unpackaged. Do you still want to take over maintainership?
Could you plea
Hi, Rocky,
On Tue, 2 Nov 2021 13:11:07 -0400
Rocky Bernstein wrote:
>
> Hmm - as best as I can tell this patches things a little differently than
> what was done in the git codebase.
That was not my intention.
Actually, I don't understand why you say that.
The patch that I backported to
Hi, Rocky, Lucas,
Thanks for doing all the hard work of reporting and fixing the bug.
I have just uploaded a new version o libcdio with the fix.
Cheers,
Gabriel
On Mon, 04 Oct 2021 04:28:27 +0800
積丹尼 Dan Jacobson wrote:
>
> perltidy debian
> perltidy upstream
> bash-completion debian
> bash-completion upstream
Yeah, I know it's sometimes hard to tell where to submit bug reports
to. On the other hand, it looks like you are doing a good job of it.
On Mon, 04 Oct 2021 09:01:55 +0200
Philipp Marek wrote:
>
> Perhaps I can find out what went wrong...
> do you have any ideas? readline settings,
> some shell function interfering (wrong completion load order?), ...??
I don't. There are too many variables. :/
> Next time that happens, I'll dump
Control: tags -1 + unreproducible
Hi,
I could not reproduce this bug, even though I tried every version all
the way down to 1:2.10-2. Here's what I get:
$ apt-get u
$ apt-get up
update upgrade
$ apt-get a
$ apt-get auto
autoclean autoremove
If you have more information,
Hi,
thanks for reporting...
A fix is on its way to the Debian Archive and already in VCS [1].
Cheers,
Gabriel
[1]
https://salsa.debian.org/debian/bash-completion/-/commit/65534d18c5b0c5bf496af7a921ada56aa2a4375c
Control: forwarded -1 https://github.com/scop/bash-completion/issues/518
Control: tags -1 confirmed upstream fixed-upstream
Hello,
Hey, you could have mentioned that you submitted the bug upstream! :)
For future reference, here is is:
https://github.com/scop/bash-completion/issues/518
Control: tags -1 + fixed-upstream
Koichi Murase kindly pointed out that this has already been fixed upstream:
https://github.com/scop/bash-completion/issues/590#issuecomment-906045204
This patch has not been integrated into a release, yet:
$ git describe --tags 79a504a
2.11-81-g79a504a4
Control: tags -1 + confirmed upstream
The change in behavior is caused by the following upstream commit:
https://github.com/scop/bash-completion/commit/d1756f06ef9bffb1b4621c4e63e47e181ddf1086
which got released in upstream version 2.10.
Bug reported submitted upstream as
Thanks for the update.
I'll close the bug report now. Feel free to reopen it if anything else pops-up.
On Mon, 23 Aug 2021 19:36:34 -0300
"Gabriel F. T. Gomes" wrote:
>
> I will create a chroot with old-stable (buster) to check if older
> versions of bash-completion have this problem.
Indeed, now I was able to reproduce it.
And yes, using _have instead of have does fix the
Hello Jürgen,
thanks for following up on this bug.
On Mon, 23 Aug 2021 13:11:28 +0200
Jürgen Kuri wrote:
>
> If have() is used AND bash-completion script is stored into directory
>
> /usr/share/bash-completion/completions
I'm still trying to reproduce the problem, so...
I copied the
Hello again, Pelle,
I just tested it under sway and the column selection pop up showed up
normally. Perhaps I'm using Sway the wrong way?
I simply installed it with apt install sway; logged in from lightdm,
learned how to open a terminal, and launched pragha from it. Then, when
I right click on
Hi, Pelle,
On Tue, 13 Apr 2021 11:00:15 +0200
Pelle wrote:
>
> When I right-click on a column header, no list appears, when running
> Pragha in Sway (a Wayland compositor). However, that list appears when
> Pragha is run in Weston (another Wayland compositor).
>
> I had only been running
Hello, Pelle,
On Tue, 13 Apr 2021 00:12:40 +0200
Pelle wrote:
>
> It appears there is no way to sort an album (or several albums in a playlist)
> by track order. The available column headers for sorting are 'Title',
> 'Artist',
> 'Album' and 'Length'.
These are the default columns, indeed.
>
Hi, Kevin,
On Mon, 15 Mar 2021 07:07:36 -0600
Kevin Locke wrote:
>
> I've attached an updated version
> which matches & and | in addition to ; as command separators. We may
> also want to consider modifying the compgen expression in the same way.
I added this patch (with a changelog entry) to
On Mon, 15 Mar 2021, Kevin Locke wrote:
>
> Which appears to be a common idiom for only defining the function and
> completion if the command is in $PATH. I've attached an updated version
> which matches & and | in addition to ; as command separators. We may
> also want to consider modifying the
On Mon, 15 Mar 2021, Gabriel F. T. Gomes wrote:
>
> I'll check if it works correctly with the scripts currently installed
> under my /usr/share/bash-completion.
Perhaps we could also add && and || as command termination characters,
so that idioms like the following also get dete
Hi, Kevin,
On Sat, 13 Mar 2021, Kevin Locke wrote:
>
> I've attached a patch to fix the issue by requiring complete to follow a
> line break or semicolon. It obviously does not address the root of the
> problem of reliably differentiating a list of paths from a Bash script.
> (Which is not
On Thu, 04 Feb 2021, Daniel Kahn Gillmor wrote:
>
> (as i was writing this report, i realized that it's probably mainly an
> upstream bug, so i filed it at the URL above, but i figure it's worth
> tracking in the BTS as well since it affects other packages)
Thanks, and I agree. :)
Hi, William,
Thanks for your report.
On Fri, 04 Sep 2020, William Herrin wrote:
> set -u
> cd /
> cd ho[tab]
> bash: !ref: unbound variable
This is a known bug, which has been recently fixed upstream, and in
debian unstable/testing (see https://bugs.debian.org/741273#27).
> -- System
Hi, Andreas,
I need help to reproduce this bug.
On 15 May 2020, Andreas Beckmann wrote:
>with dh_missing defaulting to --fail-missing in compat level 13,
>dh_bash-completion needs to log the files it has installed s.t.
>dh_missing does not wrongly report
> dh_missing: error: missing files,
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: gabr...@debian.org, sergi...@debian.org, vasek.ge...@gmail.com
Severity: normal
Hi,
libcdio needs a transition (upstream bumped the SONAME without ABI break).
I built all the packages
On Fri, 31 Jul 2020, Sergio Durigan Junior wrote:
>
> Yeah, the list is large, indeed. I guess we'll find out whether this
> breaks something or not when it reaches unstable and starts to be used
> :-).
And if it breaks *before* people update debhelper's compat level, then
we know we broke it
Control: tags -1 + patch
Hi, Sergio,
<3 S2 <3 S2
On Thu, 30 Jul 2020, Sergio Durigan Junior wrote:
>
> So, here's the thing. We can't blindly rely on debhelper's
> filedoublearray anymore, because of the problem you guys pointed out
> above. Which means that bash-completion will probably
Control: severity -1 important
Control: tags -1 + confirmed
Hi, Anthony,
thanks for the report!
On 17 Jul 2020, Anthony Fok wrote:
>I ran into the following error while packaging the latest version of
>hugo package:
>
>dh_bash-completion: error: Cannot resolve variable
>
Hi, Vasyl,
On 26 Jul 2020, Vasyl Gello wrote:
>I need it to satisfy kodi build dependency in libcdio++. Actually, when Kodi
>19.0 goes live officially,
>I would like to have it in unstable, testing (if it gets released before the
>freeze takes place)
That sounds reasonable, and I'm already
Package: gnucash
Version: 1:3.10-1
Severity: wishlist
Hello,
Upstream gnucash released a new stable version, 4.0 [1]. Among the new
features, the "type-ahead search" would be very welcome.
Could you update it in Debian, please? :)
If you need help, just let me know. I could submit a merge
Hi, Vasyl,
On 25 Jul 2020, Vasyl Gello wrote:
>
>Can you please upload libcdio to unstable?
Yes.
The upload to experimental didn't help *me* much with the testing of
pragha, because, in order for pragha to use the new version, I also had
to rebuild (locally) libcdio-paranoia (if I install
Control: tags -1 + confirmed
On 30 May 2020, Amr Ibrahim wrote:
>
> In Debian pragha depends on libxfce4ui-2-0 and libxfce4util7, however,
> according to upstream*, pragha is independent of Xfce and libxfce4ui is
> optional and not strictly required to run the app. So I think the
> depends is
Hi, Vasyl,
On Mon, 29 Jun 2020, Vasyl Gello wrote:
> The MR I amended after Gabriel's review is stuck since June 2nd.
Yes, my bad.
> Gabriel, can you please revise the MR and upload the fixed package to the
> queue?
Will do (I'll try to do it today)! Thanks for the heads-up.
:)
On Fri, 12 Jun 2020, Sławomir Stańczak wrote:
>
> W dniu 11.06.2020 o 21:41, Gabriel F. T. Gomes pisze:
> > If I understand correctly, you would like for 'tar -cf ' to
> > complete with tar files already present in the file system.
>
> Yes. This prevents overwritin
On 10 Jun 2020, Sławomir Stańczak wrote:
>
>$ tar -cf 000/ not working
If I understand correctly, you would like for 'tar -cf ' to
complete with tar files already present in the file system. Although I
believe that this would be a reasonable thing to do, upstream
bash-completion seems to believe
On Tue, 02 Jun 2020, Bálint Réczey wrote:
>
> Done. I've omitted the last commit because I suggest using -1~exp0
> Debian version for the upload to experimental. IMO looks nicer when
> the upload to unstable has -1.
Thanks for the review. I'll fix this, then upload again to mentors.
On 01 Jun 2020, Bálint Réczey wrote:
>
>I've checked the package and it refers to
>https://salsa.debian.org/debian/libcdio as the packaging repo while it
>is not present.
>I fyou agree let me clone your packaging repo there, then I can review
>the changes.
Oh, please. And thank you. :)
>I can't
On 31 May 2020, Gabriel F. T. Gomes wrote:
>
>we will need a sponsor.
The package is now on mentors:
https://mentors.debian.net/package/libcdio
Balint, could you review it and, if everything is fine, sponsor it?
(I'm asking because Vasyl mentioned you are guiding the packaging of
Kodi, if
Hi, Vasyl,
On 24 May 2020, Vasyl Gello wrote:
>
>Yes experimental is OK for me, even though I uploaded libshairplay &
>libudfread to unstable queue. Balint asked me initially to target Kodi 19.0 to
>experimental so I will probably re-upload both libraries to experimental to
>keep everything
On 27 May 2020, Jürgen Kuri wrote:
>
>When I build the packages for Debian Jessie, everything works as expected,
>both completion scripts are installed into the path:
>
> $ ls -la /etc/bash_completion.d/
> total 24
> drwxr-xr-x 2 root root 4096 May 26 16:58 .
>
Hi, Vasyl,
on 24 May 2020, Vasyl Gello wrote:
>
>Gabriel has prepared 2.1.0 in his Salsa repo and I added C++ interfaces needed
>by Kodi 19.0:
>https://salsa.debian.org/gabrielftg-guest/libcdio/-/merge_requests/1
Thank you so much for writing this pull requests. I wasn't aware that
there was a
Hi, Andreas,
Could you point out a package that still uses dh_bash-completion? I'm
having a hard time finding one so that I can reproduce the problem
before working on the fix.
Thank you!
Hi, Hugo,
thanks for starting the work on this package. I'll be around if you
need help with packaging stuff, and I'll review your work when you have
something ready to share.
Cheers,
Gabriel
Control: reassign -1 mount
Control: merge -1 933934
Hi, наб,
Thanks for the report. I'll reassign it to the mount package, because
completions for umount are shipped by it, not by bash-completion.
Also, I'll mark it as a duplicate of bug 933934.
Cheers,
Gabriel
Sean Whitton, from FTP Master, reviewed the package and pointed out
that the file CODE_OF_CONDUCT.md is probably not suitable for
distribution in the main section. I agreed and repackaged the project,
as can be seen in:
https://salsa.debian.org/debian/pveclib/-/commits/master
(look for dfsg)
Control: retitle -1 ITA: libcdio-paranoia
Control: assign -1 !
I maintain pragha, which depends on this package, so I'll adopt it.
Thanks,
Gabriel
Control: retitle -1 ITA: libcdio
Control: assign -1 !
I maintain pragha, which depends on this package, so I'll adopt it.
Thanks,
Gabriel
Hi, Hugo,
thanks for reaching out.
On Mon, 27 Jan 2020, Hugo Ziviani wrote:
>
> I think this is not exactly a bug.
Are you saying this because you think that this is more like a
reasonable feature that is missing, as opposed to a bug that causes
crashes or wrong output? If so, I would say that
This might be related:
https://github.com/scop/bash-completion/issues/378
Control: reassign -1 util-linux
Reassigning to util-linux as the completion file belongs to it.
Control: retitle -1 bash-completion: "umount" completion breaks on spaces
Control: tags -1 + confirmed
On 02 Jan 2020, Philipp Marek wrote:
>With only the default "mawk" installed, auto-completion gives errors:
>
> $ umount /
> awk: line 18: function gensub never defined
> awk: line
Hi, thanks for your report. I'll have a closer look at your debugging
effort, but I'd like to reply fast and add that completion with variables
has known problems, indeed. There's a bug report upstream with more
information, here:
https://github.com/scop/bash-completion/issues/290
Cheers,
Forwarded upstream as https://github.com/scop/bash-completion/pull/359
On Sat, 26 Oct 2019, 積丹尼 Dan Jacobson wrote:
>All I know is I can't get any expansion at all even here:
>$ find . -path ./
Yes, I confirm that it doesn't.
>Why can't it ever expand anything at -path?
I'm trying to understand what to expand, thus I need your help.
>Is it because "the doctor
Control: merge 918430 927232
Control: stop
This bug report is a duplicate of 918430.
On 06 Jan 2019, 積丹尼 Dan Jacobson wrote:
>Package: bash-completion
>Version: 1:2.8-5
>File: /usr/share/bash-completion/completions/find
>
>No expansion is happening here:
>$ find /tmp/ -path /tm
>Please make it happen. Thanks.
I'm trying to understand what's the use case you want to enable.
I'll
Hi, Michael,
On 23 Oct 2019, Michael Lustfield wrote:
>Apologies- I missed your first line.
No problem, at all. :)
>I finished with a fair bit of packaging clean up and officially adopted
>rsnapshot. I'd be happy to co-maintain this package.
Awesome. I'm happy it has a new maintainer!
I'll
Hi, I would like to adopt it.
Have you had any problems with it that you would like to share with the
future maintainer?
Cheers,
Gabriel
On Wed, 04 Sep 2019 21:29:45 +0200 g...@iroqwa.org wrote:
> Package: wnpp
> Severity: normal
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> I
On Sat, 23 Feb 2019 10:52:43 -0300 "Gabriel F. T. Gomes"
wrote:
>
> Thanks for the information. I have forwarded this upstream as
> https://github.com/scop/bash-completion/pull/284
This has been integrated into bash-completion 2.9, which is now
available in Debian
On Wed, 10 Jul 2019 23:24:43 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
wrote:
>
> I do cpio -tvF and the screen flashes.
I did not understand this bug report, nor was I able to reproduce it.
Could you describe it in other words, and perhaps explain how I can
reproduce it? I never saw the
On Mon, Aug 05 2019, Laurent Bigonville wrote:
>
> I see that the bash-completion package ships unmount.linux and
> mount.linux. But the mount package also ships completion for these
> executable, are these redundant?
The .linux files are supposed to be used in linux-based distros, as
opposed to
Control: merge 922657 931685
Control: stop
On Tue, 09 Jul 2019 11:39:47 +0200 Michael Becker wrote:
>
> with an existing directory $HOME/devel
> ls $HOME/dev
> completes to
> ls \$HOME/devel/
This has the same root cause of bug https://bugs.debian.org/922657,
i.e.: in
On Sat, 22 Jun 2019 19:48:06 +0200 Adam Borowski wrote:
>
> Heck, just seconds ago, the package got uploaded with:
> Maintainer: Gabriel F. T. Gomes
> keyid: FD9CE2D8D7754B78AB279BBD2C3B436FEAC68101
> and I'm pretty sure that key EAC68101 is not yours.
Hahaha, it to
On 13 Jun 2019, Steven Munroe wrote:
>I need s work around for that, Then I will update/tag.
Thanks for the fixes and for the tagging.
With that, I was able to finish the package and send it for review
(see https://bugs.debian.org/930709).
Package: sponsorship-requests
Severity: wishlist
Hi, mentors,
I have filled the RFS template below, but I have a few words beforehand.
1. I know we are under the freeze, so I was a bit wary to send the RFS
now. On the other hand, I didn't actually find anything saying that I
should wait for
noowner -1
retitle -1 RFP: cr3 -- Cool Reader 3, an e-book reader
thanks
I didn't make any progress on this package, so I'm removing myself from
it and setting it back to RFP. Sorry... :(
If someone wants to work on the packaging, I can definitely help, just
let me know. :)
On Wed, 29 May 2019, Gabriel F. T. Gomes wrote:
>
>I submitted a pull request [2] upstream to foster this discussion.
>
>[...]
>
>[2] https://github.com/open-power-sdk/pveclib/pull/71
For the record: this pull request was superseded by pull request #73 [1],
which has been integr
On Sat, 25 May 2019 15:31:47 -0300 "Gabriel F. T. Gomes"
wrote:
>
> As-is sounds good to me. :)
On second thought, I have an usability question for you, which would
also be relevant for other distros that might ship pveclib...
The headers are currently installed under /usr
On Fri, May 24 2019, Steven Munroe wrote:
> In the current state, these libraries are only required for unit tests, but
> could be used for applications that need those constant values.
OK, if it can be useful for applications, than it's probably better to
distribute it, right away.
> [...] So
Hi, Steve,
After creating a initial version of the packaging [1], I got two
packages: one that contains the headers and the static library
(libpvec-dev_1.0.0-1_ppc64el.deb), and another that contains the shared
library (libpvec0_1.0.0-1_ppc64el.deb).
My first question would be: is that expected?
Package: wnpp
Severity: normal
I will start working on the packaging for pveclib
(https://github.com/open-power-sdk/pveclib).
Cheers,
Gabriel
On Wed, Apr 10 2019, Witold Baryluk wrote:
>
> I am using a free version of unrar, in package unrar-free in main repo of
> Debian:
>
> [...]
>
> $ unrar-free --version
> unrar 0.0.1
> $ unrar --version
> unrar 0.0.1
Oh, I see. Thanks for the explanation.
> Note that OPTION part is optional,
On Wed, Mar 13 2019, 積丹尼 Dan Jacobson wrote:
>
> OK, maybe even less,
> $ file /usr/bin/*|grep -c shell\ script
> 194
> $ ls /usr/bin/*.sh
> /usr/bin/gettext.sh
This only means that a very tiny fraction of shell scripts *inside*
/usr/bin have .sh extension. Anyhow, thanks for the clarification.
On Sun, Mar 10 2019, Gabriel F. T. Gomes wrote:
>
> https://github.com/scop/bash-completion/pull/291
Fixed upstream [1]. When a new upstream version gets released, I'll
close this bug report.
[1]
https://github.com/scop/bash-completion/commit/dd80f35279afd4f056dc191767b9869c9649d476
On Sun, Jan 20 2019, 積丹尼 Dan Jacobson wrote:
> Package: bash-completion
> Version: 1:2.8-5
> Severity: wishlist
> File: /usr/share/bash-completion/completions/sh
>
> I think 90% of shell scripts don't have a .sh extension.
> Therefore
> $ sh anyf
> should still complete to
> $ sh anyfile
You
Control: tags -1 + confirmed upstream
On Fri, Feb 01 2019, 積丹尼 Dan Jacobson wrote:
> Package: bash-completion
> Version: 1:2.8-5
>
> Why can't one enter a second option?
> $ grep --no-filename --c
Completions for grep are provided by the _longopt function, which
completes every option that
On Sun, Mar 10 2019, Gabriel F. T. Gomes wrote:
>
> It only adds the backslash to unset variables, but not when the variable
> is set, for instance:
>
> zless /usr/share/$PATH/
>
> does nothing, whereas
>
> zless /usr/share/$ASDF/
> zless /usr/share/\$ASD
Control: tags -1 + confirmed upstream
On Tue, Feb 19 2019, 積丹尼 Dan Jacobson wrote:
>
> $ set apt-show-versions
> $ zless /usr/share/doc/$@/ch
> $ zless /usr/share/doc/$@/ch
> chromium chromium-common chromium-sandbox chromium-shell
> $ zless /usr/share/doc/\$@/chromium
The backslash
On Thu, Feb 14 2019, 積丹尼 Dan Jacobson wrote:
>
> # set
> allexport hashall monitor nounset
> verbose
> braceexpand histexpandnoclobber onecmd
> vi
> emacs history
Control: tags -1 + confirmed upstream
On Sun, 09 Jul 2017 09:38:23 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
wrote:
>
> Cannot complete filenames at this point:
> $ set `cat /tmp/
Confirmed that it doesn't work.
> Even worse is
> $ set $(cat /tm
>
> $ set $(cat /tmbash: eval: line 22:
On Wed, Mar 06 2019, Witold Baryluk wrote:
>
> user@debian:~/Downloads/n$ unrar Notes\ of\ Obsession\ 1.0.0.7\ x64.rar
>
> unrar 0.0.1 Copyright (C) 2004 Ben Asselstine, Jeroen Dekkers
> Extracting from /home/user/Downloads/n/Notes of Obsession 1.0.0.7 x64.rar
>
> Extracting Notes of
Hi, thanks for the report. I have a few comments, see below...
On Tue, Mar 05 2019, Boruch Baum wrote:
>
> Performing an 'apt-get purge bash-completion' does not delete the folder
> /usr/share/bash-completion.
That's intentional. Many packages install completion files under
On Sun, Feb 24 2019, Daniel Lewart wrote:
> Package: bash-completion
> Version: 1:2.8-5
> Severity: minor
> Tags: patch
>
> Both "apt install bash-completion" and "apt purge bash-completion"
> generate the following warning:
> find: '/etc/bash_completion.d/': No such file or directory
>
>
On Tue, Feb 12 2019, Hans van Kranenburg wrote:
> On 2/12/19 1:35 AM, Gabriel F. T. Gomes wrote:
> >
> > That should be easy to do for Debian. On the other hand, I wonder if I
> > should work first with upstream to get it removed from there. Do you
> > know if the
On Wed, 20 Feb 2019 00:53:18 -0300 "Gabriel F. T. Gomes"
wrote:
>
> I tested that rebuilding flightgear with this dependency updated solves
> the METAR problem. Do you plan to upload a new binary version of
> flightgear, too? (I'm asking because the flight
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu: flightgear_1:2018.3.2+dfsg-2 . ANY . unstable . -m "rebuild against
libsimgear-dev 1:2018.3.2+dfsg-5"
Fetching of 'live weather' data was broken on flightgear, as reported in
Hi, I see that you forwarded this upstream as
https://github.com/scop/bash-completion/issues/282
I'm adding this note here for easier reference.
On Sun, 17 Feb 2019 20:54:34 + to...@debian.org (Dr. Tobias Quathamer)
wrote:
> Source: simgear
> Source-Version: 1:2018.3.2+dfsg-5
>
> We believe that the bug you reported is fixed in the latest version of
> simgear, which is due to be installed in the Debian FTP archive.
Thanks for this
1 - 100 of 213 matches
Mail list logo
