Bug 436830

Summary:	New kernel is not emerging
Product:	Gentoo Linux	Reporter:	admin
Component:	[OLD] Server	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED INVALID
Severity:	minor	CC:	admin
Priority:	Low
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description admin 2012-10-01 20:20:47 UTC

Attempting to emerge the new hardened kernel.  Get the following error:
>>> Verifying ebuild manifests
!!! A file is not listed in the Manifest: '/usr/portage/sys-kernel/hardened-sources/hardened-sources-3.4.2-r1.ebuild'


Reproducible: Always

Steps to Reproduce:
1.emerge -DNu world
2.
3.
Actual Results:  
 * IMPORTANT: 1 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

Calculating dependencies... done!

>>> Verifying ebuild manifests
!!! A file is not listed in the Manifest: '/usr/portage/sys-kernel/hardened-sources/hardened-sources-3.4.2-r1.ebuild'

Expected Results:  
source is emerged

emerge -DNup world

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  NS    ] sys-kernel/hardened-sources-3.5.4-r1 [3.4.5] USE="-build -deblob -symlink" 

 * IMPORTANT: 1 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.


emerge -DNu world

 * IMPORTANT: 1 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

Calculating dependencies... done!

>>> Verifying ebuild manifests
!!! A file is not listed in the Manifest: '/usr/portage/sys-kernel/hardened-sources/hardened-sources-3.4.2-r1.ebuild'

Comment 1 admin 2012-10-01 20:31:46 UTC

Sorry for the bad bug.

The rsync didn't complete all the way.  I re-synced and it is emerging fine.