Bug 22592 - /var/lib/rpcbind not created during package install
Summary: /var/lib/rpcbind not created during package install
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-14 12:54 CET by Bit Twister
Modified: 2018-02-23 20:56 CET (History)
2 users (show)

See Also:
Source RPM: rpcbind-0.2.4-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Bit Twister 2018-02-14 12:54:15 CET
Description of problem: 7 dev0

/var/lib/rpcbind not created during package install

Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. clean Mageia-Cauldron-netinstall-nonfree-x86_64.iso install with
2. tainted and nonfree enabled, all package groups, and xfce DE only
3. Upon reboot, run pwck  -r

Workaround:  mkdir -p /var/lib/rpcbind
Comment 1 Marja Van Waes 2018-02-14 17:09:06 CET
Assigning to all packagers collectively, since there is no registered maintainer for this package.

Assignee: bugsquad => pkg-bugs
CC: (none) => marja11

Comment 2 David Walser 2018-02-16 20:53:20 CET
The rpcbind package in Mageia used to use /var/lib/rpcbind as the statedir (--with-statedir option to configure), but no longer does.  Now it uses /run/rpcbind.  /var/lib/rpcbind is still set as the home directory of the rpc user, but as it's a system user, it shouldn't matter that the directory doesn't exist.  Funny enough the SPEC still creates /var/lib/rpcbind in %install, but no longer packages it.  I suppose the home directory of the rpc user could be changed to /run/rpcbind, but it probably doesn't matter either way.
Comment 3 Bit Twister 2018-02-16 22:17:13 CET
(In reply to David Walser from comment #2)
>  Now it uses /run/rpcbind.  /var/lib/rpcbind is still set as the home
>  directory of the rpc user, but as it's a system user, it shouldn't 
> matter that the directory doesn't exist. 

I agree operationally is not affected, but why not set /run/rpcbind in the rpc user creation entry into passwd.
Or post-install command to create /var/lib/rpcbind.

As a system admain, I would prefer a clean result from pwck -r and grpck -r on a clean install.
Comment 4 Stig-Ørjan Smelror 2018-02-23 20:56:10 CET
(In reply to Bit Twister from comment #3)
> (In reply to David Walser from comment #2)
> >  Now it uses /run/rpcbind.  /var/lib/rpcbind is still set as the home
> >  directory of the rpc user, but as it's a system user, it shouldn't 
> > matter that the directory doesn't exist. 
> 
> I agree operationally is not affected, but why not set /run/rpcbind in the
> rpc user creation entry into passwd.
> Or post-install command to create /var/lib/rpcbind.
> 
> As a system admain, I would prefer a clean result from pwck -r and grpck -r
> on a clean install.

Thomas gave me an explanation on why we should not create stuff in /run.
https://bugs.mageia.org/show_bug.cgi?id=22574#c10

CC: (none) => smelror


Note You need to log in before you can comment on or make changes to this bug.