Arch Linux

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!
Tasklist

FS#47292 - [dcadec] does not include libdcadec.so.0

Attached to Project: Arch Linux
Opened by Doug Newgard (Scimmia) - Tuesday, 08 December 2015, 07:09 GMT
Last edited by Maxime Gauduin (Alucryd) - Wednesday, 06 January 2016, 18:31 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Since the package does not include the libdcadec.so.0 symlink, ldconfig will create it leaving an unmanaged file in /usr/lib.

This is fixed upstream, https://github.com/foo86/dcadec/commit/5bc00958d64463483f9c875d2eaa851666a68d20. I don't know a good way to handle it, as any fix will now cause conflicting file errors.
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Wednesday, 06 January 2016, 18:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.2.0-1
Comment by Maxime Gauduin (Alucryd) - Tuesday, 08 December 2015, 07:21 GMT
Thx, I'll have a look at it tonight, I guess a pre-install hook to remove the offending file should do the trick.
Comment by Doug Newgard (Scimmia) - Tuesday, 08 December 2015, 07:46 GMT
I believe the pre-install scriptlets are run after the conflicting file checks, so that wouldn't do it.
Comment by Maxime Gauduin (Alucryd) - Tuesday, 08 December 2015, 08:34 GMT
Right, in that case I have an ugly solution which will require 2 steps: manually modify pacman's database post-install and post-upgrade (/var/lib/pacman/local/dcadec-0.1.0-2/files) in the install file without adding the conflicting file yet, then by the time there's a new release, everybody should be able to upgrade smoothly.
Comment by Oracle Speaks (test0987654321) - Wednesday, 09 December 2015, 06:58 GMT
I think you made a typo on line 4 of your dcadec.install file.

You typed:

libdcadec/so.0

Instead of:

libdcadec.so.0

Now pacman thinks a folder named libdcadec and a file named so.0 should exist.
Comment by Maxime Gauduin (Alucryd) - Wednesday, 09 December 2015, 07:19 GMT
Damn, thx for noticing, corrected in 0.1.0-3.

Loading...