Red Hat Bugzilla – Bug 91966
New version (0.38.05) of Devlabel is available (but 0.41.01 will make life easier for you)
Last modified: 2014-03-16 22:36:34 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030509
Description of problem:
According to the site "http://www.lerhaupt.com/devlabel/devlabel.html" there's a
newer version of Devlabel available than the version in current (30 may 2003)
According to the .spec file this newer version has additional features,
bugfixes, code cleanups and updates to the manpage.
.... Could be interesting for Red Hat Enterprise Linux users.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Checkout current Rawhide
2. Checkout "http://www.lerhaupt.com/devlabel/devlabel.html"
devlabel 0.26 fails if you create a link to hdx6,
then remove dx4 ( so hdx6 is renamed to hdx5 ).
0.3x.x versions can handle this situation.
Although there is a possible config file incompatibility ( but nothing
0.38.07 will be in rawhide in the next day or three.
by the way, that config file incompatability can be handled with `devlabel
reverseremap`. this prints a warning that its about to ditch column 3 (uuids)
of /etc/sysconfig/devlabel and refigure it out based on what's in column 2 (last
known device name). to actually do it you have to also specify --force.
Bill, you should have waited until we ( me and Gary ) work out an automatic
upgrade script :-(
IMO "rpm -U devlabel-x.x.x.rpm" should be all that is needed for smooth
upgrade. Requiring manual execution of some commands is bad, consider automatic
updates, mass updates etc ...
Hey, if you don't want me to put it in, don't send me mails saying this new
version is available. :)
Seriously, this is much like upgrades of other apps we have that don't read old
The latest version (0.40.03) has a solution for this. ( note : I did not
downloaded it yet myself ).
Include this version ! :-)
Yes, 0.40 handles the upgrade process. This will significantly decrease
customer issues. As well, I have worked with Tom Coughlan to fix some of uuid
handling issues for weird cases. Specifically, if the association value is
non-zero for a page83 id (meaning its the uuid based on the port and is
unstable), scsi_unique_id no longer returns it. As well, if a device returns
two identifiers of the same page and type, devlabel concatenates them rather
than breaking. Latest is 0.41.01.