Rpm install cpio bad magic




















Sorry, the interesting information is the RPM version on the target and its provenance. I edited my comment above. The target machine has newer rpm version — Gionelle Tribiana. Pkg installation should work.

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.

The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Related Hot Network Questions. Question feed. The issue I now see is that the pager in KDE fails. There is no pager on the task bar. No open apps on the task bar. If I scroll on the background to move between virtual desktops processes crash. Reported to KDE guys and a fix was applied there was no check for no virtual screens when it tried to change but that doesn't seem to be present in Tumbleweed yet or if there isn't fixing my issue - I've even tried a new user so it's not some old user setting kicking around.

I was doing this on a home setup but have a virtual server at work that I really need to do as it's up for days plus and sees same rpm issue. There I can get the beastie snapshot before I play so can easily roll back but it just works now. Bookmarks Bookmarks Digg del. All times are GMT Additional info: The rpm is attached. It was generated with a minimal gradle script using the nebula. It can be recreated by running 'gradle fooRpm' in a directory containing build.

Commenting out the 'link' line in build. The resulting rpm can be successfully installed on Fedora 21, so the problem seems to be specific to the symlink. I don't know enough about the rpm file format yet to figure out if the problem is with the rpm itself but somehow earlier rpm versions are more forgiving, or if it is an obscure bug here in rpm 4.

The third entry is the symlink. The cpio header is getting read correctly by rpm, including reading the file size as 21 bytes. In this case it is returning a size of 0 for this symlink instead of Is there an easy way to dump the full file info from the rpm? Obviously the zero size is the problem. Does it use rpmbuild somehow?



0コメント

  • 1000 / 1000