FS#72867 - [ardour] mime file gets deleted upon mime type database update

Attached to Project: Community Packages
Opened by sekret (sekret) - Sunday, 28 November 2021, 21:42 GMT
Last edited by David Runge (dvzrv) - Wednesday, 12 January 2022, 18:59 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Andreas Radke (AndyRTR)
David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I have the command

pacman -Qkk | grep ^error

included in my update script, which shows me changes in files that belong to packages. After some updates there keeps appearing this line:

warning: ardour: /usr/share/mime/application/ardour.xml (No such file or directory)

Right now I had an update which ran those two hooks:

:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating the MIME type database...

After this update the above warning message appeared.

So it looks like this second hook, which updates the mime type database, deletes the file /usr/share/mime/application/ardour.xml I don't think the ConditionNeedsUpdate hook causes this.

I'm not sure if this is a bug in the hook (and so in the package shared-mime-info) or in ardour's mime type file, but it certainly is a bug.

This has been happening on my system for a long time (months, maybe even more than a year), so I don't know when this has begun to happen.

Additional info:
* package version(s)
ardour 6.9-3
shared-mime-info 2.0+115+gd74a913-1

* config and/or log files etc.
-

* link to upstream bug report, if any
-

Steps to reproduce:
Install ardour and run the update-mime-database hook afterwards, either manually (if that's possible) or by installing / updating a package which triggers this hook.
This task depends upon

Closed by  David Runge (dvzrv)
Wednesday, 12 January 2022, 18:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with ardour 6.9-4
Comment by David Runge (dvzrv) - Thursday, 02 December 2021, 19:35 GMT
@sekret: Thanks for reporting this.

It is a problem with the location of the file (which is an upstream build system issue). It should not end up in the location it currently ends up in.
I meant to do something about this a while ago, but forgot again (so thanks for the ticket as reminder).
Comment by David Runge (dvzrv) - Wednesday, 12 January 2022, 18:30 GMT
There has been a fix upstream for this [1].

I will apply this in the context of the soundtouch rebuild in 6.9-4.

[1] https://github.com/ardour/ardour/commit/b95078ae464f0d132d2d0a9d5727a72bd1ee88d7

Loading...