[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-16 Thread Launchpad Bug Tracker
This bug was fixed in the package bash - 4.3-14ubuntu1.3

---
bash (4.3-14ubuntu1.3) xenial; urgency=medium

  * Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes: #781367
  * Add autopkgtest for the built-in path.

 -- Dimitri John Ledkov   Fri, 03 May 2019 14:57:15
+0100

** Changed in: bash (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  Won't Fix
Status in bash source package in Xenial:
  Fix Released
Status in bash source package in Bionic:
  Fix Released
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Released
Status in bash source package in Eoan:
  Fix Released
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-16 Thread Launchpad Bug Tracker
This bug was fixed in the package bash - 4.4.18-2ubuntu1.1

---
bash (4.4.18-2ubuntu1.1) bionic; urgency=medium

  * Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes: #781367
  * Add autopkgtest for the built-in path.

 -- Dimitri John Ledkov   Fri, 03 May 2019 14:50:32
+0100

** Changed in: bash (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  Won't Fix
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Released
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Released
Status in bash source package in Eoan:
  Fix Released
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-16 Thread Launchpad Bug Tracker
This bug was fixed in the package bash - 5.0-3ubuntu1.1

---
bash (5.0-3ubuntu1.1) disco; urgency=medium

  * Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes: #781367
  * Add autopkgtest for the built-in path.

 -- Dimitri John Ledkov   Fri, 03 May 2019 14:31:24
+0100

** Changed in: bash (Ubuntu Disco)
   Status: Fix Committed => Fix Released

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  Won't Fix
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Released
Status in bash source package in Eoan:
  Fix Released
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-13 Thread Bug Watch Updater
** Changed in: bash (Debian)
   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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  Won't Fix
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-13 Thread Mathew Hodson
** Also affects: bash (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781367
   Importance: Unknown
   Status: Unknown

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  Won't Fix
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released
Status in bash package in Debian:
  Unknown

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-09 Thread Dimitri John Ledkov
** Changed in: bash (Ubuntu Trusty)
   Status: In Progress => Won't Fix

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  Won't Fix
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-09 Thread Dimitri John Ledkov
(xenial-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(xenial-amd64)root@ottawa:~# dpkg-query -W bash
bash4.3-14ubuntu1.3

Xenial looks good.

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-09 Thread Dimitri John Ledkov
(bionic-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(bionic-amd64)root@ottawa:~# dpkg-query -W bash
bash4.4.18-2ubuntu1.1

Bionic looks good.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-09 Thread Dimitri John Ledkov
(disco-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(disco-amd64)root@ottawa:~# dpkg-query -W bash
bash5.0-3ubuntu1.1


Disco looks good.

** Tags removed: verification-needed-disco
** Tags added: verification-done-disco

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-09 Thread Adam Conrad
Hello Philippe, or anyone else affected,

Accepted bash into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bash/4.4.18-2ubuntu1.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: bash (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

** Changed in: bash (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-09 Thread Dimitri John Ledkov
Trusty is closed for SRUs, here is the diff that may be suitable for
ESM.

** Patch added: "trusty-bash.diff"
   
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+attachment/5262678/+files/trusty-bash.diff

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  In Progress
Status in bash source package in Bionic:
  In Progress
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-09 Thread Ɓukasz Zemczak
Hello Philippe, or anyone else affected,

Accepted bash into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bash/5.0-3ubuntu1.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: bash (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-disco

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  In Progress
Status in bash source package in Bionic:
  In Progress
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-03 Thread Launchpad Bug Tracker
This bug was fixed in the package bash - 5.0-3ubuntu2

---
bash (5.0-3ubuntu2) eoan; urgency=medium

  * Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes: #781367
  * Add autopkgtest for the built-in path.

 -- Dimitri John Ledkov   Fri, 03 May 2019 14:31:24
+0100

** Changed in: bash (Ubuntu Eoan)
   Status: Fix Committed => Fix Released

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  In Progress
Status in bash source package in Bionic:
  In Progress
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  In Progress
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-05-03 Thread Dimitri John Ledkov
** Also affects: bash (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: bash (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: bash (Ubuntu Eoan)
   Importance: Medium
   Status: Fix Released

** Also affects: bash (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: bash (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: bash (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: bash (Ubuntu Eoan)
   Status: Fix Released => In Progress

** Changed in: bash (Ubuntu Cosmic)
   Status: New => Fix Released

** Changed in: bash (Ubuntu Disco)
   Status: New => In Progress

** Changed in: bash (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Changed in: bash (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: bash (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: bash (Ubuntu Trusty)
   Status: New => In Progress

** Also affects: bash (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: bash (Ubuntu Precise)
   Status: New => Fix Released

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Committed
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  In Progress
Status in bash source package in Bionic:
  In Progress
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  In Progress
Status in bash source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2019-04-30 Thread Dimitri John Ledkov
** Description changed:

+ [Impact]
+ 
+  * The fallback path built into bash contains '.' which leads to
+ unexpected addition of the current working directory. It should not be
+ there, just like it isnt' in pre-precise and cosmic+.
+ 
+ [Test Case]
+ 
+  * $ env -u PATH /bin/bash -c 'echo $PATH'
+ 
+ Should not have '.' as any component. Nor should there be any empty
+ components, i.e. '::'.
+ 
+ [Regression Potential]
+ 
+  * Normally PATH is always set by either init, systemd, or any other
+ hypervisor. Thus this only affects executions under bash, when it was
+ started without any environment - e.g. booting with 'init=/bin/bash'.
+ 
+ [Other Info]
+  
+  * Original bug report.
+ 
  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:
  
  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  
  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2018-09-12 Thread Launchpad Bug Tracker
This bug was fixed in the package bash - 4.4.18-2ubuntu3

---
bash (4.4.18-2ubuntu3) cosmic; urgency=medium

  * Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes: #781367
  * Add autopkgtest for the built-in path.

 -- Dimitri John Ledkov   Wed, 12 Sep 2018 15:22:11
+0100

** Changed in: bash (Ubuntu)
   Status: New => Fix Released

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released

Bug description:
  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2018-09-12 Thread Dimitri John Ledkov
@philippe-vaucher
I'm not quite concerned about what other distros do. Imho, it is buggy to not 
have `sbin` in the default built-in bash path - so i'd call fedora's bash 
built-in path still buggy ;-)

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  New

Bug description:
  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2016-09-05 Thread Philippe Vaucher
For information this bug does not happen on Fedora/CentOS

philippe@pv-desktop:~$ docker run -it --rm fedora:latest bash -c "unset PATH; 
/bin/bash -c 'echo \$PATH'"
/usr/local/bin:/usr/bin


** Bug watch added: Debian Bug tracker #781367
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781367

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  New

Bug description:
  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2016-09-05 Thread Philippe Vaucher
Ah, found the same bug in Debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=781367

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  New

Bug description:
  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2016-08-22 Thread Philippe Vaucher
** Tags removed: trusyt
** Tags added: trusty

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  New

Bug description:
  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2016-08-22 Thread Brian Murray
** Tags added: trusyt xenial

** Changed in: bash (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  New

Bug description:
  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

2016-08-17 Thread Philippe Vaucher
** Package changed: ubuntu => bash (Ubuntu)

-- 
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/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  New

Bug description:
  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp