| Summary: | sys-kernel/linux-headers-4.18: version bump | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Tomáš Mózes <hydrapolic> |
| Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kuzetsa, slyfox |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
packages which didn't fail (emerge.log)
/etc/portage/sets/header-test-onlystable (@header-test-onlystable) |
||
|
Description
Tomáš Mózes
2018-10-11 11:37:10 UTC
So far so good on ~amd64 virtual machine, glibc && gcc went fine, survived the reboot, testing the other apps from testing.txt mentioned in cvs. Created attachment 550594 [details] packages which didn't fail (emerge.log) --- DID NOT build glibc or qemu summary: # blacklist: suspect (unverified errors) # (need retesting on amd64) # net-dialup/linux-atm # sys-process/criu # media-video/vdr # sys-fs/udev # net-misc/dahdi # net-misc/dahdi-tools (attachment 1 [details] of 2) Created attachment 550596 [details] /etc/portage/sets/header-test-onlystable (@header-test-onlystable) (In reply to Sarah White from comment #3) > Created attachment 550594 [details] > packages which didn't fail (emerge.log) > > > --- > The test was not exhaustive, but emerge.log shows the non-blacklisted packages in this set were able to build without issue. (/oops/ tachment 2 of 2) - silly bugzilla @ comment #3 Thanks for the report and test! I'll take the opportunity to move CVS tree to git as well: bug # 668364 (In reply to Sarah White from comment #3) > # blacklist: suspect (unverified errors) > # (need retesting on amd64) > # net-dialup/linux-atm > # sys-process/criu > # media-video/vdr > # sys-fs/udev > # net-misc/dahdi > # net-misc/dahdi-tools > > (attachment 1 [details] of 2) Not sure I understand, but are there any packages that failed to build for you? If so, please could you attach the failed build logs? Sarah was kind enough to provide the logs at https://poindexter.ovh/~kuzetsa/gentoo/portage/ I checked the items and the build fails are because the tests were done on a stable machine, the newest packages can be compiled fine. media-video/vdr-2.2.0-r1: fails to build media-video/vdr-2.2.0-r3: works net-dialup/linux-atm-2.5.0: cannot reproduce (2.5.2 works too) net-misc/dahdi-2.10.2-r2: Kernel not configured; no .config found in /usr/src/linux (but fails to build even if you provide one) net-misc/dahdi-2.11.1-r1: works sys-fs/udev-238: fails to build sys-fs/udev-239: works sys-process/criu-3.6: fails to build sys-process/criu-3.9: works (In reply to Tomáš Mózes from comment #7) > Sarah was kind enough to provide the logs at > https://poindexter.ovh/~kuzetsa/gentoo/portage/ > I checked the items and the build fails are because the tests were done on a > stable machine, the newest packages can be compiled fine. > > media-video/vdr-2.2.0-r1: fails to build > media-video/vdr-2.2.0-r3: works > > net-dialup/linux-atm-2.5.0: cannot reproduce (2.5.2 works too) > > net-misc/dahdi-2.10.2-r2: Kernel not configured; no .config found in > /usr/src/linux (but fails to build even if you provide one) > net-misc/dahdi-2.11.1-r1: works > > sys-fs/udev-238: fails to build > sys-fs/udev-239: works > > sys-process/criu-3.6: fails to build > sys-process/criu-3.9: works (not sure I understood 100% perfectly) Ah, so you were able to reproduce those failures, but only for the stable-keyworded versions? I didn't actually regression test those stable versions to confirm the issue only happens on 4.18.x so I guess it's a good thing there's at least one version of those packages which works. It may not have been clear from Attachment 550596 [details] but: I didn't test: sys-block/sedutil (or) net-proxy/shadowsocks-libev, and like I said on comment #3 I didn't test qemu or glibc (slow builds) because those (and/or the deps) aren't stable-keyworded, and I prefer not to pollute that test system ::shrug:: (In reply to Sarah White from comment #8) > Ah, so you were able to reproduce those failures, > but only for the stable-keyworded versions? Yes, those stable keyworded packages fail to build, but the latest testing versions work fine. I haven't encountered any build failures after the linux-headers bump, so I would recommend adding the package (maybe without any KEYWORDS for some time). The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9232fd54a40d94bde459f8d93cd2227366b1d27d commit 9232fd54a40d94bde459f8d93cd2227366b1d27d Author: Sergei Trofimovich <slyfox@gentoo.org> AuthorDate: 2018-10-12 23:02:39 +0000 Commit: Sergei Trofimovich <slyfox@gentoo.org> CommitDate: 2018-10-13 09:44:11 +0000 sys-kernel/linux-headers: bump up to 4.18, bug #668306 Reported-by: Tomáš Mózes Tested-by: Sarah White Tested-by: Tomáš Mózes Closes: https://bugs.gentoo.org/668306 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> Package-Manager: Portage-2.3.51, Repoman-2.3.11 sys-kernel/linux-headers/Manifest | 2 + sys-kernel/linux-headers/linux-headers-4.18.ebuild | 60 ++++++++++++++++++++++ 2 files changed, 62 insertions(+) Tested on gcc/glibc rebuilds on amd64 myself. Tested on packages test list on x86 myself. Things mostly build fine. I've pushed it directly to ~arch. Thanks all! Thank you Sarah and Sergei :) |
