Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57506 - [linux] config doesn't pass validity check

Attached to Project: Arch Linux
Opened by Pierre Killy (pierre.killy) - Wednesday, 14 February 2018, 11:31 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 19 February 2018, 06:23 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Bartłomiej Piotrowski (Barthalion)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I use a linux kernel that I compile myself based on the linux package in core, following the instructions there: https://wiki.archlinux.org/index.php/Arch_Build_System

The last available version currently is 4.15.3-1.

In this version of the package, the config file does not pass validity check because of this commit: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=05386a4b06c7271f47adff718907f9768c489f40

Additional info:
* package version(s): 4.15.3-1


Steps to reproduce:
from svn root:
$ svn update linux
$ linux/trunk/
$ makepkg -si
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Monday, 19 February 2018, 06:23 GMT
Reason for closing:  Fixed
Comment by Ike Devolder (BlackEagle) - Wednesday, 14 February 2018, 15:04 GMT
This is not important, the version that is in the repo's has correct checksums. The next build will have correct checksums again.
Comment by Eli Schwartz (eschwartz) - Wednesday, 14 February 2018, 15:08 GMT
Who said it was "important"? This is low severity for a reason, but it is nevertheless an issue, hence why Scimmia assigned it instead of closing it...

We should strive to have our sources actually work, rather than just saying "you shouldn't use the sources, just install the binary packages".
Comment by Jan de Groot (JGC) - Wednesday, 14 February 2018, 15:51 GMT
There's a difference between trunk and repos/*. This is not just "use the binary".

Trunk can contain anything that isn't ready for release yet. The bugreport is valid though, someone working on a trunk checkout will have to look in svn log to find out that the config was changed without updating checksums.
Comment by Ike Devolder (BlackEagle) - Wednesday, 14 February 2018, 21:27 GMT
To be honest *if* you are checking out trunk you should be able to handle such issues. That's why I think this is still an invalid ticket

Loading...