Bug#317264: [Pkg-shadow-devel] Bug#317264: login: Current su breaks pbuilder

2005-07-12 Thread Christian Perrier
Quoting Junichi Uekawa ([EMAIL PROTECTED]):
 
 Hi,
 
 Apart from being unhappy about a core component of 


I would actually appreciate that the I am unhappy comments about
this issue are taken away now. We have put a lot of efforts in solving
the thing as quickly as possible, you know..:)




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#317264: [Pkg-shadow-devel] Bug#317264: login: Current su breaks pbuilder

2005-07-12 Thread Junichi Uekawa
  Apart from being unhappy about a core component of 
 
 
 I would actually appreciate that the I am unhappy comments about
 this issue are taken away now. We have put a lot of efforts in solving
 the thing as quickly as possible, you know..:)

Okay; I'll just express that I forsee a bit more trouble 
while this transition takes place in sid.



regards,
junichi.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#317264: [Pkg-shadow-devel] Bug#317264: login: Current su breaks pbuilder

2005-07-08 Thread Christian Perrier
  Whenever I try to use pbuilder to build a package after upgrading the
  chroot today, I get:
 
  frobnitz:/tmp/kdenetwork# su -p daniel -- dpkg-source -x 
  kdenetwork_3.3.2-6.dsc
  /usr/bin/dpkg-source: line 3: my: command not found
  /usr/bin/dpkg-source: line 4: my: command not found
 
 
 This is very likely to be the fix for #276419 which is culprit here.
 
 Other team members, who looks more closely at this?

For the record:

From the #shadow IRC channel, here is Nicolas François (nekral)
analysis:
01:06  nekral hi
01:09  nekral I'm looking at the log and here are clarifications of my thought
01:12  nekral in #276419, we were asked not to concatenate all arguments 
before passing them to the shell (or command if -c)
01:15  nekral Another point was asked by 276419-submitter: not to add a -c 
argument to the executed shell when no command was provided to su (with -c)
01:16  nekral regarding the first point:
01:16  nekral  * the old behavior was not documented (Any arguments supplied 
after the username will be passed to the invoked  shell)
01:18  nekral  * the old behavior differ from current upstream (and probably 
from other distribution, upstream using a patch from redhat)
01:19  nekral  * applications requiring that the arguments are concatenated 
should concatenate themself
01:19  nekral Then regarding the second point:
01:21  nekral  * the man page does not indicate that -c is inserted in the 
list of arguments provided to the shell
01:24  nekral(thus su - $USERNAME -- -x should work and should execute 
a shell in debug mode (the arguments should be [shell, -x] and not 
[shell, -c, -x])
01:31  nekral Then, if too many packages relied on the previous behavior, and 
if only 276419-submitter push for the applied patch, then a pragmatical approch 
could be to revert
01:31  nekral (We can also only revert one of the above points)
01:33  nekral Zugschlus, I don't understand the point about your clamav-data 
testing script on debian-volatile
01:34  nekral did it occured with login 4.0.3-36?
01:34  nekral su - $ACCOUNT -c bash works nicely with login 4.0.3-36
01:37  nekral (also, I can't find any reference to su in clamav-data)
07:42  Zugschlus fsck, nekral isn't there
07:43  Zugschlus the testing script is not part of the package






Bug#317264: [Pkg-shadow-devel] Bug#317264: login: Current su breaks pbuilder

2005-07-07 Thread Christian Perrier
Quoting Daniel Schepler ([EMAIL PROTECTED]):
 Package: login
 Version: 1:4.0.3-36
 Severity: important
 
 Whenever I try to use pbuilder to build a package after upgrading the
 chroot today, I get:

 frobnitz:/tmp/kdenetwork# su -p daniel -- dpkg-source -x 
 kdenetwork_3.3.2-6.dsc
 /usr/bin/dpkg-source: line 3: my: command not found
 /usr/bin/dpkg-source: line 4: my: command not found


This is very likely to be the fix for #276419 which is culprit here.

Other team members, who looks more closely at this?




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]