Attaching new debdiff based on the current noble version.
** Patch added: "1097467-3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5766422/+files/1097467-3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Bah, looks like this upload got accidentally dropped by the subsequent
merge for noble. I'll rebase and re-proposed it when I've got some
time...
** Changed in: bash (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: bash (Ubuntu)
Assignee: Dan Bungert (dbungert) => Dave
Uploaded
** Changed in: bash (Ubuntu)
Assignee: (unassigned) => Dan Bungert (dbungert)
** Changed in: bash (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in
Doh, I always forget something...
** Patch added: "1097467-2.debdiff"
https://bugs.launchpad.net/gnubash/+bug/1097467/+attachment/5719318/+files/1097467-2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in
Actually, it would be nice if the new patch had some dep-3 headers (see
[1], `quilt --dep3` and maybe dep3changelog). In particular I think we
miss bug references an a description of the patch. Do you think you
could add the relevant ones? Thanks!
[1] https://dep-team.pages.debian.net/deps/dep3/
Thanks for digging into this issue and updating the relevant Debian bug,
refreshing the debdiff. This LGTM, tested locally, the manpage renders
fine. I am going to sponsor this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: gnubash
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1097467
Title:
bash does not fulfill --rcfile option properly
Status in
** Patch added: "1097467-1.debdiff"
https://bugs.launchpad.net/gnubash/+bug/1097467/+attachment/5719274/+files/1097467-1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
It appears this has come up before, and was discussed upstream. [1] and
[2] cover discussion of whether --rcfile should ignore the system-wide
bashrc (SYS_BASHRC hereafter), with the conclusion from upstream that it
should not. [3] is an attempt by someone to fix this upstream by
modifying bash's
** Changed in: bash (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1097467
Title:
bash does not fulfill --rcfile option properly
This discussion needs to be taken upstream, it's not our place to decide
what is right.
** Tags removed: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1097467
** Patch added: "manpage-is-wrong.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5611101/+files/manpage-is-wrong.debdiff
** Tags added: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "bash-is-wrong.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5611100/+files/bash-is-wrong.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
I'm unsure what the "correct" solution is here; could be that bash's
behaviour is wrong, or it could be that the documentation is wrong.
Rather than decide, I'm taking the cowards way out and attaching patches
for both solutions, leaving it to the maintainer to decide which is
appropriate :)
--
Hmm, on the other hand --norc does indeed suppress both user and system-
wide bashrc files. So, the man-page is correct in that instance, and
apparently the intent of bash is to allow the system-wide bashrc file to
be suppressed in certain circumstances. Which sways me back toward the
notion that
This has apparently been an issue for some considerable time. I've just
now run into it while delving into a failure in pexpect's test-suite
(during work on LP: #1987420), which apparently assumes that using
--rcfile will suppress both the user *and* the system's bashrc (as the
man-page
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bash (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
** Summary changed:
- bash does not fulfill --bashrc option properly
+ bash does not fulfill --rcfile option properly
** Description changed:
I am starting a bash shell using
- $ bash --noprofile --bashrc my-custom-bash-rc-file
+ $ bash --noprofile --rcfile my-custom-bash-rc-file
Due
18 matches
Mail list logo
