[opensuse] batik - calls commitment to quality into question (broken since release and still not fixed?)
openSuSE Devs,
batik-1.7-211.2 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/share/batik: cpio: rename failed - Is a directory
This has been broken since 11.3 was released.....
On Mon, 09 Aug 2010 17:55:12 -0500, "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
batik-1.7-211.2 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/share/batik: cpio: rename failed - Is a directory
This has been broken since 11.3 was released.....
So open a bug report! That's what bugzilla is for, you know?
Philipp
On 08/09/2010 06:04 PM, Philipp Thomas wrote:
On Mon, 09 Aug 2010 17:55:12 -0500, "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
batik-1.7-211.2 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/share/batik: cpio: rename failed - Is a directory
This has been broken since 11.3 was released.....
So open a bug report! That's what bugzilla is for, you know?
Philipp
Done :p
https://bugzilla.novell.com/show_bug.cgi?id=629763
Add any additional comments you may have there.
David C. Rankin wrote:
On 08/09/2010 06:04 PM, Philipp Thomas wrote:
On Mon, 09 Aug 2010 17:55:12 -0500, "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
batik-1.7-211.2 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/share/batik: cpio: rename failed - Is a directory
This has been broken since 11.3 was released.....
So open a bug report! That's what bugzilla is for, you know?
Philipp
Done :p
https://bugzilla.novell.com/show_bug.cgi?id=629763
Add any additional comments you may have there.
I experienced this bug last night.
David's bug was marked as a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=619229 which was opened on July 1 and is still open with the last comment in November. There's no milestone for a fix. The priority is None.
Is there any intention to fix this bug?
Cheers, Dave
-
Dave Howorth -
David C. Rankin -
Philipp Thomas