Custom Query (325 matches)


Show under each result:

Results (25 - 27 of 325)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Ticket Resolution Summary Owner Reporter
#29 worksforme Updating package kills WPS objects Yuri Dario dmik

It seems that updating a package that uses %wps_object_create... macros to create WPS objects causes these objects to be deleted (as upon yum remove) but not created back when installing the new version. At least, this happened here once. Needs investigation.

The quick fix is to do yum reinstall <package> -- this will restore WPS objects.

#30 wontfix WPS objects are killed on package update Yuri Dario dmik

If a package creates some WPS objects in %post and deletes them in %postun, updating such a package to a new version kills all WPS objects as if the package was uninstalled.

#31 fixed yum reports WarpIn database locked/in-use when it is not Yuri Dario Lewis Rosenthal


Odin 0.6.21632.0 (20110512-release) was installed under WarpIn?. Uninstalled, breaking Flash dependency. Restarted. Ran "yum install libodin" from prompt, and received:


Failed to access the WarpIn? database file:


Please close the WarpIn? application or, if it is not running, make sure that this file is not locked by another process, and try again.

This is not the only package to exhibit this behavior, thus, I do not think this is a packaging issue. I confirmed that the database was not in use, and was able to open it under UniMaint? (and closed it before re-trying yum).

I have had success with several other packages, though I am not sure what triggers the perceived lock on the database.

As "yum version" currently yields:

Error: Error accessing file for config file:///etc/yum/version-groups.conf

I can't get version info from there, however, dir reports:

8-28-11 10:58 1,330 124 yum.exe

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Note: See TracQuery for help on using queries.