Your message dated Sat, 19 Sep 2015 15:05:32 +0000 with message-id <[email protected]> and subject line Re: Bug#481112: pbuilder: no longer possible to specify PATH has caused the Debian Bug report #481112, regarding pbuilder: no longer possible to specify PATH to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 481112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481112 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: pbuilder Version: 0.180 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i've been wondering why my builds have been taking longer in spite of having ccache installed and previously set up in my pbuilder chroot. for the longest time i just assumed i was doing something wrong and never bothered to look into it, but now i believe that this is a valid problem, perhaps caused by the fix for #439285 ? example: rangda[~] grep PATH /etc/pbuilderrc # Set the PATH I am going to use inside pbuilder: default is # "/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin" export PATH="/usr/lib/ccache:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin" export PATH2=hi rangda[~] sudo pbuilder --login --basetgz /var/cache/pbuilder/etch-amd64/base.tgz <snip> root@rangda:/# echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin root@rangda:/# echo $PATH2 hi so other environment variables are not affected. i'm not sure what the best way to solve this for the general case is, but i will probably solve this by modifying /etc/profile in my various pbuilder/cowbuilder chroots. thanks, sean - -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages pbuilder depends on: ii cdebootstrap 0.5.1 Bootstrap a Debian system ii coreutils 6.10-6 The GNU core utilities ii debconf [debconf-2.0] 1.5.21 Debian configuration management sy ii debianutils 2.28.5 Miscellaneous utilities specific t ii debootstrap 1.0.8 Bootstrap a basic Debian system ii gcc 4:4.2.3-8 The GNU C compiler ii wget 1.11.1-1 retrieves files from the web Versions of packages pbuilder recommends: ii cowdancer 0.45 Copy-on-write directory tree utili ii devscripts 2.10.26 scripts to make the life of a Debi ii fakeroot 1.9.5 Gives a fake root environment ii sudo 1.6.9p15-2 Provide limited super user privile - -- debconf information excluded -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIKefaynjLPm522B0RAv+qAJ9j4Wet6KI6p+V/zIjyz6CZf6W5VwCfT7u1 dFNbjg3vWTk6MYWLUA+ktd0= =SCJF -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---On Tue, May 13, 2008 at 09:11:22PM +0200, sean finney wrote: > i've been wondering why my builds have been taking longer in spite of > having ccache installed and previously set up in my pbuilder chroot. > for the longest time i just assumed i was doing something wrong and > never bothered to look into it, but now i believe that this is a valid > problem, perhaps caused by the fix for #439285 ? > > example: > > rangda[~] grep PATH /etc/pbuilderrc > # Set the PATH I am going to use inside pbuilder: default is > # "/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin" > export PATH="/usr/lib/ccache:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin" > export PATH2=hi > > rangda[~] sudo pbuilder --login --basetgz > /var/cache/pbuilder/etch-amd64/base.tgz > <snip> > root@rangda:/# echo $PATH > /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin > root@rangda:/# echo $PATH2 > hi > > so other environment variables are not affected. i'm not sure what the > best way to solve this for the general case is, but i will probably > solve this by modifying /etc/profile in my various pbuilder/cowbuilder > chroots. As others said, this is due to the chroot's /etc/profile which resets PATH. builds are not affected, only --login. There is really few we can do for this. If you need a weird PATH when you login just type it. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: Digital signature
--- End Message ---
