Description of Problem:
/dev/vcsa* owned by root. This prevents cons.saver from working.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install dev-3.3-3 and look at /dev/vcsa* owner
It's owned by root
It should be owned by vcsa
The owner is set to 'vcsa' on my test machine here. Are any errors printed when
you install this package (or if installed at install-time, in the install.log file)?
Nope, no errors. I've rebuilt it from the src rpm and did an upgrade over an
existing dev. I didn't see any mention of user vcsa in the src, so I decided to
report it as a bug. Where this owner should come from? What part of MAKEDEV
The account should be created by the pre-install scriptlet in the dev package.
Yes, it is. But what part of MAKEDEV changes the /dev/vcsa* owner?
MAKEDEV does not change any ownerships automatically. The owner of the device
ownership is set (or changed) when the dev package is installed (or upgraded).
Of course. But let's put it the other way: when you build the binary rpm from
the sources, which part of that source rpm (MAKEDEV-3.3-3.src.rpm) is
responsible for changing the owner of /dev/vcsa* in that binary rpm?
The files manifest in the .spec file specifies the owner of the device, and RPM
stores that information directly in the package.
Yep, that's the point :-) So, where is it in the MAKEDEV.spec? I double-checked
it and the only reference to vcsa user is when it was created.
MAKEDEV prints out the ownerships when it is run during the %install phase, and
the list is processed by RPM. You can verify the result by running "rpm -qplv"
against the binary package.
I've just reinstalled using the latest tree and have verified that the
ownerships are set correctly. I'm inclined to mark this as WORKSFORME because,
well, it works for me.
Sanity check: you are using RPM to install the package, right?
I've rebuilt it from SRPM myself and then installed produced binary RPM. Did you
do the same? I did rpm -qlpv on this RPM and all files in it are owned by root.
I don't understand how it could work for you. Could something in the build
environment affect the ownership of these files?
If you are building the package as root, and the vcsa user does not exist on the
system when you build it, then I think the method used to generate the files
manifest might lose the ownership. 3.3-4 will use the same method when building
as the superuser as it does for non-privileged users, which should fix this.
You were right, that was the reason. The new version works just fine. You can
close this bug now. Thank you for your patience :-)