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#34451 - [ecasound] 2.9.0-2 Installs a file in / (the root directory)
Attached to Project:
Arch Linux
Opened by smmilut (smmilut) - Monday, 25 March 2013, 12:53 GMT
Last edited by Ray Rashif (schivmeister) - Tuesday, 26 March 2013, 13:29 GMT
Opened by smmilut (smmilut) - Monday, 25 March 2013, 12:53 GMT
Last edited by Ray Rashif (schivmeister) - Tuesday, 26 March 2013, 13:29 GMT
|
DetailsDescription:
Package ecasound 2.9.0-2 installs a file in / (the root directory). $ pacman -Qo /ecasound.rb /ecasound.rb is owned by ecasound 2.9.0-2 $ ls -l /ecasound.rb -rwxr-xr-x 1 root root 5158 Mar 5 15:37 /ecasound.rb Additional info: - First line of the file says: # This is a native implementation of Ecasound's control interface for Ruby. - The only relevant thing i see could be line 33 in the PKGBUILD : # use vendor_ruby for ruby files sed -e 's/CONFIG\["sitedir"\]/CONFIG\["vendordir"\]/' -i configure But i have no idea how. - Seems like it happened after upgrade from 2.9.0-1 Steps to reproduce: Install the package, and ls / |
This task depends upon
Closed by Ray Rashif (schivmeister)
Tuesday, 26 March 2013, 13:29 GMT
Reason for closing: Fixed
Additional comments about closing: 2.9.0-3
Tuesday, 26 March 2013, 13:29 GMT
Reason for closing: Fixed
Additional comments about closing: 2.9.0-3
Comment by Ray Rashif (schivmeister) -
Tuesday, 26 March 2013, 11:04 GMT
Indeed, thanks for reporting. This is due to the ruby update which deprecated some things. Namcap's warning didn't scare me enough to take a look before pushing the last update (I thought it was a vendor/site dir issue which I could look into later). Sorry about that. Fix rolling soon.