FS#59801 - [dhcpcd] losing duid after each upgrade

Attached to Project: Arch Linux
Opened by Anonymous Submitter - Saturday, 25 August 2018, 11:34 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 31 August 2018, 15:24 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
  • Anonymous Submitter (2018-08-28)
Private No

Details

Every time I upgrade this package via pacman, it loses duid. I think it happens, because of https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/dhcpcd#n18 as duid is a file /var/lib/dhcpcd/duid . I think, pacman cleanes this directory every time.
So as duid changes, dhcp server on my router thinks, it is new device.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 31 August 2018, 15:24 GMT
Reason for closing:  Won't fix
Comment by Doug Newgard (Scimmia) - Tuesday, 28 August 2018, 05:08 GMT
No, pacman does not do that. Sounds like you have something else going on; custom pacman hook or something?
Comment by Anonymous Submitter - Tuesday, 28 August 2018, 19:28 GMT
Well, I'll check it again two days later as I am not at home right now, but, to be honest I don't think so. Last time I've checked, I did 'stat /var/lib/dhcpcd/duid' and last change date was the day of last upgrade, dhcpcd package was upgraded also. I have simple installation of Arch, followed by official installation guide: base, base-devel and also I have samba, aria2 and thansmission packages installed. But I've never wrote any pacman hooks by myself at all.
Can you, please, downgrade dhcpcd on two versions back via arch linux archive and then try to upgrade?
By the way, what does mean emptydirs option?
Comment by loqs (loqs) - Tuesday, 28 August 2018, 19:58 GMT
From man 5 PKGBUILD
emptydirs
Leave empty directories in packages.
It instructs makepkg not to remove empty directories when the package is created it has no meaning to pacman.
Pacman does not remove files not provided by the package. A .install file could but the dhcpcd package does not use one.
If you downgrade dhcpcd does that remove /var/lib/dhcpcd/duid?
Comment by Anonymous Submitter - Thursday, 30 August 2018, 15:22 GMT
Well. So first of all, here is my current state:
'stat /var/lib/dhcpcd/duid':
File: /var/lib/dhcpcd/duid
Size: 42 Blocks: 8 IO Block: 4096 regular file
Device: 802h/2050d Inode: 528900 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2018-08-30 17:46:16.857511875 +0300
Modify: 2018-06-09 20:12:44.074150474 +0300
Change: 2018-06-09 20:12:44.074150474 +0300
Birth: -

cat /var/log/pacman.log | grep dhcpcd
[2017-10-22 15:26] [ALPM] installed dhcpcd (6.11.5-1)
[2018-06-01 18:28] [ALPM] upgraded dhcpcd (6.11.5-1 -> 7.0.4-1)
So, the time of chaging was actually 2018-06-09 20:12, but not 2018-06-01 18:28. That's because after upgrading whole system at 06.01, I've just shutted down my PC. So I have full upgrade logs and journalctl logs of first starting up system after upgrade. If it can be useful, I'll upload it.
Now I'll try to upgrade whole system again and check the result. ...10 minutes later... that wasn't changed this time.
Comment by Anonymous Submitter - Thursday, 30 August 2018, 16:00 GMT
Well, so here is my theory:
As you can see [2018-06-01 18:28] [ALPM] upgraded dhcpcd (6.11.5-1 -> 7.0.4-1), I've upgraded dhcpcd from 6.11.5 to 7.0.4. So here it is - https://github.com/rsmarples/dhcpcd#upgrading
As pacman hasn't moved duid file to new location, it wasn't moved and dhcpcd created new one. No one noticed, as it is not too important.
Comment by Anonymous Submitter - Thursday, 30 August 2018, 16:05 GMT
I think, maintainers shoud add logic of moving old files to new location.
Comment by Doug Newgard (Scimmia) - Friday, 31 August 2018, 15:24 GMT
So this happened with the update to version 7, which was more than 6 months ago. Far too late to worry about it now.

Loading...