Bug#584234: inn2: innshellvars should not override $HOME

2010-09-24 Thread Julien ÉLIE
Hi Matthew, I think innshellvars* shouldn't over-ride $HOME. Also, It would be nice if there was a file in /etc you could use to tune what these programs do (e.g. to set other environment variables such as GNUPGHOME). Done in INN 2.5.3: http://inn.eyrie.org/trac/changeset/9110 I hope it

Bug#584234: inn2: innshellvars should not override $HOME

2010-08-10 Thread Julien ÉLIE
Hi Matthew, Also, It would be nice if there was a file in /etc you could use to tune what these programs do (e.g. to set other environment variables such as GNUPGHOME). That's an interesting idea. Would something like that suit you? ${pathetc}/innshellvars.local

Bug#584234: inn2: innshellvars should not override $HOME

2010-08-10 Thread Julien ÉLIE
Hi Russ, An interesting directory would be pathdb. Why not use pathdb for that pullnews state file? We have active.times and newsgroups there for instance. Instead of using .pullnews, why not use pullnews.marks (or any better name without an initial dot? marks was for high/low water marks)

Bug#584234: inn2: innshellvars should not override $HOME

2010-06-05 Thread Julien ÉLIE
Hi Russ, A few ideas, questions and comments in this mail. I'm sorry it is not well organized. They are rough thoughts! I see that pullnews uses $ENV{HOME}/.pullnews (with a remark in our code that is is also called ~/.pullnews). What should then be done for it? Should we use $pathnews

Bug#584234: inn2: innshellvars should not override $HOME

2010-06-05 Thread Russ Allbery
Julien ÉLIE jul...@trigofacile.com writes: An interesting directory would be pathdb. Why not use pathdb for that pullnews state file? We have active.times and newsgroups there for instance. Instead of using .pullnews, why not use pullnews.marks (or any better name without an initial dot?

Bug#584234: inn2: innshellvars should not override $HOME

2010-06-03 Thread Matthew Vernon
Marco d'Itri writes: On Jun 02, Matthew Vernon matt...@debian.org wrote: That breaks things. Most notably, it means that gpg will try and create files in pathnews/.gnupg so if pathnews is not the same as ~news things like buildinnkeyring and gpgverify won't work. If ~news !=

Bug#584234: inn2: innshellvars should not override $HOME

2010-06-03 Thread Marco d'Itri
I am lost. I expect that the upstream developers will reply. -- ciao, Marco signature.asc Description: Digital signature

Bug#584234: inn2: innshellvars should not override $HOME

2010-06-03 Thread Russ Allbery
Matthew Vernon matt...@sel.cam.ac.uk writes: Marco d'Itri writes: On Jun 02, Matthew Vernon matt...@debian.org wrote: That breaks things. Most notably, it means that gpg will try and create files in pathnews/.gnupg so if pathnews is not the same as ~news things like buildinnkeyring and

Bug#584234: inn2: innshellvars should not override $HOME

2010-06-03 Thread Julien ÉLIE
Hi Russ, windlord:~/dvl/inn-2.4/scripts svn log -r 7405 r7405 | eagle | 2005-10-08 18:43:33 -0700 (Sat, 08 Oct 2005) | 2 lines Set HOME to pathnews. This should resolve Debian Bug#307765. Looking at that bug, we started

Bug#584234: inn2: innshellvars should not override $HOME

2010-06-03 Thread Russ Allbery
Julien ÉLIE jul...@trigofacile.com writes: We can indeed set the keyring if we edit the file. I see that pullnews uses $ENV{HOME}/.pullnews (with a remark in our code that is is also called ~/.pullnews). What should then be done for it? Should we use $pathnews instead of $ENV{HOME} and

Bug#584234: inn2: innshellvars should not override $HOME

2010-06-02 Thread Matthew Vernon
Package: inn2 Version: 2.4.5-5 Severity: normal Hi, innshellvars, innshellvars.pl and innshellvars.tcl all set $HOME to the value of pathnews specified in inn.conf, over-riding the home directory of the news user. That breaks things. Most notably, it means that gpg will try and create

Bug#584234: inn2: innshellvars should not override $HOME

2010-06-02 Thread Matthew Vernon
Marco d'Itri writes: On Jun 02, Matthew Vernon matt...@debian.org wrote: That breaks things. Most notably, it means that gpg will try and create files in pathnews/.gnupg so if pathnews is not the same as ~news things like buildinnkeyring and gpgverify won't work. If ~news !=