FS#50499 - [linux-grsec] change in versioning broke update detection

Attached to Project: Community Packages
Opened by Sairon Istyar (saironiq) - Tuesday, 23 August 2016, 18:25 GMT
Last edited by Daniel Micay (thestinger) - Thursday, 01 September 2016, 20:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Daniel Micay (thestinger)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Switching from major.minor.timestamp-build to major.minor.patch.timestamp-build versioning scheme has broken pacman's ability to detect updated package.
The change was introduced in this commit: https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/linux-grsec&id=3643faeac42b65015c905a082e9e6e032192e133


Additional info:
warning: linux-grsec: local (4.7.201608131240-1) is newer than community (4.7.2.201608211829-1)
warning: linux-grsec-headers: local (4.7.201608131240-1) is newer than community (4.7.2.201608211829-1)


Steps to reproduce:
try updating packages
This task depends upon

Closed by  Daniel Micay (thestinger)
Thursday, 01 September 2016, 20:46 GMT
Reason for closing:  Fixed
Comment by Ernest (Bogus) - Wednesday, 24 August 2016, 10:37 GMT
The version number of the local installation is incomplete: 4.7.X.201608131240-1. 'X' stands for the missing number, which is given in the new version. Does the problem can be solved by just running 'sudo pacman -Syu' after the maintainer corrected the version number or do we have first to downgrade to a version with a correct specification and then update via pacman?
Comment by Giuseppe (G-G) - Wednesday, 24 August 2016, 16:07 GMT
Probably the simplest solution is to just download the last package version and install it with the -U option. After that future versions will be detected normally (unless this is going to happen again with version 4.8.0).
Comment by Daniel Micay (thestinger) - Wednesday, 24 August 2016, 19:36 GMT
The next version will bump the epoch and will switch the separator used for the grsecurity revision from . to something else like r. AFAIK, there hasn't been a grsecurity release based on a mainline kernel rather than a stable kernel since I started packaging it, so this hasn't come up before.
Comment by Ernest (Bogus) - Wednesday, 24 August 2016, 21:12 GMT
I hope that I do not violate the reporting rules when I want to thank Guiseppe (G-G) for the great advice. I downloaded from the mirror the tar.xz-packages for linux-grsec and linux-grsec-header (linked on the corresponding ArchLinux pages for these packages), and installed both with 'sudo pacman -U linux-grsec-4.7.2.201608211829-1-x86_64.pkg.tar.xz ' and 'sudo pacman -U linux-grsec-headers-4.7.2.201608211829-1-x86_64.pkg.tar.xz'. The system informed me about downgrading of these packages, but installation went fine. Subsequent update of the system with 'sudo pacman -Syu' worked like a charm and without the warnings reported in this bug. Thank you very much!

Loading...