Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35387 - [Torsocks] should put files in /usr/share/torsocks.
Attached to Project:
Community Packages
Opened by Evan Teitelman (paradoxial) - Monday, 20 May 2013, 19:00 GMT
Last edited by Daniel Micay (thestinger) - Tuesday, 21 May 2013, 02:14 GMT
Opened by Evan Teitelman (paradoxial) - Monday, 20 May 2013, 19:00 GMT
Last edited by Daniel Micay (thestinger) - Tuesday, 21 May 2013, 02:14 GMT
|
DetailsDescription:
The package 'torsocks' puts files directly in '/usr/share'. These files should be in the directory '/usr/share/torsocks'. Additional info: The following files are misplaced: /usr/share/DEBUG /usr/share/README /usr/share/README.TORDNS /usr/share/SOCKS4.protocol /usr/share/SOCKS5 /usr/share/compilewarnings.patch /usr/share/conffile.patch /usr/share/expectedresults.txt /usr/share/getaddrbyhost.patch /usr/share/getpeername.patch /usr/share/infiniteloop.patch /usr/share/localaddresses.patch /usr/share/run_tests.sh /usr/share/socks-extensions.txt /usr/share/tordns.patch |
This task depends upon
Closed by Daniel Micay (thestinger)
Tuesday, 21 May 2013, 02:14 GMT
Reason for closing: Fixed
Additional comments about closing: Thanks, these files were useless (they aren't even documentation) so I removed them from the package. I'm not sure why the upstream install target does this...
Tuesday, 21 May 2013, 02:14 GMT
Reason for closing: Fixed
Additional comments about closing: Thanks, these files were useless (they aren't even documentation) so I removed them from the package. I'm not sure why the upstream install target does this...