Bug#542671: vidalia: Should not suggest "update-rc.d -f" only
On Sun, Aug 23, 2009 at 06:11:20PM -0300, UlisesVitulli wrote: > Hi Jeremy! I only noticed your reply today. Bug submitter do *not* receive emails unless subscribed to the bug report, so you should keep the submitter in To: or Cc: fields unless you are only discussing with package maintainers. > I've to say I'm fully aware about this problem, unfortunately, I'm > almost sure policy is against of any interaction with other packages > files than the ones carried by itself , in this case, tor's init > scripts, so some kind of user-interaction must have to show up around > this. #542670 is indeed related. I really think you should ask weasel his opinion on this issue. Please not that dkg also wrote on blog entry on similar issues recently [1]. Maybe splitting the tor package between "tor" and "tor-bin" could be a solution to the issue currently affecting the vidalia package. [1] http://www.debian-administration.org/users/dkg/weblog/53 Cheers, -- Jérémy Bobbio.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#542671: vidalia: Should not suggest "update-rc.d -f" only
Package: vidalia Version: 0.1.15-1 Severity: normal Hi! In README.Debian, in order to prevent Tor to start automatically at boot time, it is suggested to use: # update-rc.d -f tor remove This suggestion is a bad one. When startup links are removed this way, they will be created again on the next upgrade (or reinstallation) of the tor package. Thus enabling it again on startup. Using the "disable" option of "update-rc.d" would probably be a better suggestion, here. But maybe it would be more user friendly to either: a) Ask (through debconf) about disabling Tor startup links; with "no" as a default; and do it in the postinst script. b) Change tor init script so that it does not start the daemon itself when a specific setting (maybe in /etc/default/vidalia) is set. This setting value could be asked through debconf as well. I am unsure about how policy compliant is option a). Option b) would need coordination with weasel (tor's package maintainer). Feel free to clone this bug to follow up on the previous ideas. Cheers, -- Jérémy Bobbio.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#542671: vidalia: Should not suggest "update-rc.d -f" only
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 tags 542671 confirmed thanks Hi Jeremy! I've to say I'm fully aware about this problem, unfortunately, I'm almost sure policy is against of any interaction with other packages files than the ones carried by itself , in this case, tor's init scripts, so some kind of user-interaction must have to show up around this. I'm trying to find out a possible nicer solution in the meantime. Thanks! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBCAAGBQJKkbB3AAoJEGin9OG0lUUKM/oP/A/synvQ3Glb+IWddJj3MB9o H456YAcBf689Qmp08ND8bYmTtVrF+Sg9wiG573Ss+xQI4AvMblfF3zRYZw6QZqHz 3c3/FiXjNIDHZXoRFAbuwWsrhT25X8a4ybTnMzS54dcBRWbbbp90mIGgl5Hge3Lx SWNI/3wmNcyQs2+dXO/aUlmG65XIRgSKw9L0lne2vYGR0pVOvm2+LJmgJxgLLmVR fRzU/pxfMeTj1uIbDip+63Vho61HGQSML68ec2kz3H7PRu5ifArxzQvjgOPBqbk9 XKcrxhFwqsnGc5ugPgx8QfCYiqMYivUBiXoTJ9mI1povEtg3YOtzxcUh6YFpVRJA H+n5sbYRV9YdoymxOVn0SDLkB3TF9DKajO2TYCAB53VKTJuWbu0rBJ9R8Gk1E37X wXEV8ogLqfAop5TCmTpdpRBdQlTBvCiPIYsdmMkntFGrx4hsKAozPOIySMoDupMA EpNwZqvloIbC801qkYkAhZsw4/81mWbHjHJxqrUnGNoSTSb3B8vLq4Y3Kh68lEl3 3hDsZqtBAsDnFAa4FPPh6EI7h55qBCLEtdgPDDbRaW5asx2bxk0X+Z3b5z7mtnE2 wpqDBOfLjBeLVZ49Uby9mlubyCBzZkfPejMvA4+eyy9TLnEafBT4NO54P2uI6Q3u /YPuOm1eG7XQDI4f52GM =ACse -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature
Bug#542671: Re: Bug#542671: vidalia: Should not suggest "update-rc.d -f" only
Jérémy Bobbio escribió: > I only noticed your reply today. Bug submitter do *not* receive emails > unless subscribed to the bug report, so you should keep the submitter > in To: or Cc: fields unless you are only discussing with package > maintainers. Sorry about the misunderstanding, I might have been in a rush when I answered to the BTS and forgot to check that. > #542670 is indeed related. I really think you should ask weasel his > opinion on this issue. Please not that dkg also wrote on blog entry on > similar issues recently [1]. Maybe splitting the tor package between > "tor" and "tor-bin" could be a solution to the issue currently affecting > the vidalia package. Thank you very much for the information, I found it really interesting indeed! I've indeed contacted Weasel already so we could end up with a widely useful solution, not only for Vidalia, but for any other Tor GUI application out there. Greetings, signature.asc Description: OpenPGP digital signature
