Re: F11: Latest Sagator update blew up.
- From: Michael Schwendt <mschwendt@xxxxxxxxx>
- Date: Mon, 1 Mar 2010 11:05:02 +0100
On Sun, 28 Feb 2010 15:57:00 -0800, Daniel wrote:
FWIW, here is the sagator update problem:
Running Transaction
Installing :
sagator-core-1.2.0-1.fc11.noarch 1/4
Error unpacking rpm package sagator-core-1.2.0-1.fc11.noarch
error: unpacking of archive failed on file /usr/share/sagator: cpio:
lsetfilecon
Installing :
sagator-selinux-1.2.0-1.fc11.noarch 2/4
Error unpacking rpm package sagator-selinux-1.2.0-1.fc11.noarch
error: unpacking of archive failed on file /usr/share/sagator/selinux:
cpio: lsetfilecon
Installing :
sagator-1.2.0-1.fc11.noarch 3/4
Installing :
sagator-webq-1.2.0-1.fc11.noarch 4/4
Error unpacking rpm package sagator-webq-1.2.0-1.fc11.noarch
error: unpacking of archive failed on file /usr/share/sagator/srv/web:
cpio: lsetfilecon
Installed:
sagator.noarch
0:1.2.0-1.fc11
Failed:
sagator-core.noarch 0:1.2.0-1.fc11 sagator-selinux.noarch
0:1.2.0-1.fc11
sagator-webq.noarch 0:1.2.0-1.fc11
Could you also look into reporting stuff like that in the Fedora
Updates System and Bugzilla, please?
https://admin.fedoraproject.org/updates/sagator-1.2.0-1.fc11
http://bugz.fedoraproject.org/sagator
It has become really easy to leave comments and to open new bug reports.
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
- References:
- F11: Latest Sagator update blew up.
- From: Daniel B. Thurman
- F11: Latest Sagator update blew up.
- Prev by Date: Re: Fedora 12 shutdown hangs (after recent kernel update)
- Next by Date: Re: Looking for advise on a special grub setup.
- Previous by thread: F11: Latest Sagator update blew up.
- Next by thread: Re: Installing Fedora Core 12 on a system with a IT8212 SATA Controller
- Index(es):