On 16-12-13 16:22:08, Honza Silhan wrote: > On Mon, Dec 12, 2016 at 12:26 PM, arnaud gaboury > <arnaud.gaboury@xxxxxxxxx> wrote: > > > > > > On Mon, Dec 12, 2016 at 11:06 AM arnaud gaboury > <arnaud.gaboury@xxxxxxxxx> > > wrote: > >> > >> I want to upgrade from 24 to 25. Following this[0], I first run: > >> # dnf upgrade --refresh > >> > >> I am left with an issue for one package: > >> > >> ------------------------------ > >> Upgrading : httpd-2.4.23-5.fc24.x86_64 > >> 1/4 > >> Error unpacking rpm package httpd-2.4.23-5.fc24.x86_64 > >> Error unpacking rpm package httpd-2.4.23-5.fc24.x86_64 > >> error: unpacking of archive failed on file > /usr/sbin/suexec;584e75cb: > >> cpio: cap_set_file > >> ------------------------------------ > > > > > > > > EDIT: > > I was thinking as a hack to download the .rpm then install it with > > rpm -Uvh. But the extract fils again: > > > > # rpm -Uvh filesystem-3.2-37.fc24.x86_64.rpm > > Preparing... ################################# [100%] > > Updating / installing... > > 1:filesystem-3.2-37.fc24 ################################# [50%] > > error: unpacking of archive failed on file /proc: cpio: chown > > ------------------------------------------------------------ > > Is it possible to extract this file somewhere else than /proc ? I am > > not an expert in how rpm (or dnf) works step by step, but they shall > > at one point extract the archive. > > Hi, > > It seems like it fails on first package and rpm is not able to extract > the package content. Do you have write access on your system? > > If it was just one package problem then you could exclude that package > i.e.: "dnf upgrade -x filesystem". Why does the OP say that he has a problem with httpd, and then tries manually to install filesystem instead? -- ____________________________________________________________________ TonyN.:' <mailto:tonynelson@xxxxxxxxxxxxxxxxx> ' <http://www.georgeanelson.com/> _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx