ArchAudio

ArchAudio is an Arch Linux third-party, community-led project. The way to file a bug for ArchAudio is the same as one for Arch Linux, so you should read the following before reporting your first task:

http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs to flag a package out-of-date, or if it is in Unsupported (AUR). In the former case, use our forums or mailing list - but only if the update is urgent. In the latter, use the Arch Linux forums (not ArchAudio).

You need to register for an account; the user database here is independent of the site and forums.

Tasklist

FS#22 - [csound5] /usr/bin/extract file system conflict with libextractor [community]

Attached to Project: ArchAudio
Opened by Philipp Überbacher (hollunder) - Tuesday, 24 August 2010, 23:07 GMT+1
Last edited by Ray Rashif (schivmeister) - Thursday, 14 October 2010, 17:44 GMT+1
Task Type Bug Report
Category Repositories → Packages: Testing
Status Closed
Assigned To holger (hm_b)
Philipp Überbacher (hollunder)
Operating System All
Severity Medium
Priority Normal
Reported Version Not Applicable
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Issue/Feature

both create /usr/bin/extract and thus conflict on a filesystem level

This task depends upon

Closed by  Ray Rashif (schivmeister)
Thursday, 14 October 2010, 17:44 GMT+1
Reason for closing:  Fixed
Comment by Ray Rashif (schivmeister) - Tuesday, 24 August 2010, 23:44 GMT+1

I’m not entirely sure whether they’re the same things, but either way we should rename the executables here or remove them (if they’re the same).

Comment by holger (hm_b) - Wednesday, 25 August 2010, 12:09 GMT+1

They are not the same - debian installs it as csound_extract.
I just did the same in the PKGBUILD.
I also removed some other cruft (an md5sum in /usr?!).

I don't know what would be a good value for march though... so i removed it... what do you think?

patch: http://aur.pastebin.com/STBka6vR

Comment by Philipp Überbacher (hollunder) - Wednesday, 25 August 2010, 15:14 GMT+1

I guess we'd need a march for i686 and another one for x86_64. Not sure what's sensible there.

Comment by Ray Rashif (schivmeister) - Wednesday, 25 August 2010, 23:03 GMT+1

I've taken a brief look at the PKGBUILD but it looks like the csound build system isn't trivial. I'd personally always prefer to use $CFLAGS if possible so:

_gccOptions="$CFLAGS"

Anyway, main issue solve so let's close this.

Loading...