Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 137553 - sys-fs/ntfsprogs Could not emerge version 1.13.0 with installer
Summary: sys-fs/ntfsprogs Could not emerge version 1.13.0 with installer
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-22 02:11 UTC by Marius Wachtler
Modified: 2006-06-23 20:50 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marius Wachtler 2006-06-22 02:11:45 UTC 
Hello
I started yesterday a gentoo installation, but it fails because ntfsprogs-1.13.0 is broken.

output:
>>> emerge (1 of 1) sys-fs/ntfsprogs-1.13.0 to /
!!! Security Violation: A file exists that is not in the manifest.
!!! File: files/digest-ntfsprogs-1.13.1
Exception received:
EmergePackageError :FATAL: emerge: Could not emerge sys-fs/ntfsprogs-1.13.0!
Comment 1 Horst Schirmeier 2006-06-22 02:19:08 UTC 
Run emerge --sync and retry.
Comment 2 Marius Wachtler 2006-06-22 03:14:26 UTC 
Hello
I'm using the graphical installer of gentoo.

I tested "emerge --sync" and run again the graphical installer but the error still exists. 

this are the sources in my installprofile.xml

<portage-snapshot>
http://gentoo.inode.at/snapshots/portage-latest.tar.bz2
<stage-tarball>
http://gentoo.inode.at/releases/x86/current/stages/stage3-i686-2006.0.tar.bz2

note: portage-latest.tar.bz2  == portage-20060621.tar.bz2
Comment 3 Sune Kloppenborg Jeppesen (RETIRED) gentoo-dev 2006-06-22 05:59:44 UTC 
Most likely not a security issue.

Reassigning to maintainer.
Comment 4 Andrew Gaffney (RETIRED) gentoo-dev 2006-06-23 20:50:27 UTC 
The has nothing to do with the installer or releng. The tree was broken when that particular snapshot was made. It looks as if the manifest is fixed now, so the problem is gone.