Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1393 - problem with `Version: 2.6.1' in dev-2.6.1-2.src.rpm
problem with `Version: 2.6.1' in dev-2.6.1-2.src.rpm
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm (Show other bugs)
arm7 Linux
high Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Depends On:
  Show dependency treegraph
Reported: 1999-03-01 22:43 EST by stewart
Modified: 2008-03-06 14:57 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-03-26 19:44:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description stewart 1999-03-01 22:43:58 EST
I think this is an rpm related bug...  On the arm I cannot
get the latest dev package to rebuild, it dumps core.

rpm -vv -ba dev.spec
+ exit 0
Processing files: dev
D: File 1342: 060640 root.disk   /dev/xdb8
D: File 1343: 020664 root.root   /dev/zero
Segmentation fault (core dumped)

If I change Version: to `Version: 2.6' in the spec file it
builds fine.

This is with rpm-2.91-17 or the latest from cvs
Comment 1 stewart 1999-03-01 23:16:59 EST
OK, ignore most of what I wrote last time...  When I changed the
version it used the previous tar ball...

The only difference between dev 2.6 and 2.6.1, that I can see, is
2.6.1 has:
So I don't know if this is rpm related or dev related...  Well aside
from the fact rpm should not dump core :-)
Comment 2 Bill Nottingham 1999-03-22 18:43:59 EST
is this still happening with the latest rpm?
Comment 3 Jeff Johnson 1999-03-26 19:44:59 EST
Fixed in rpm-2.93. There was a uid/gid in the dev tarball
that was not in /etc/passwd or /etc/group that caused a segfault.
Rpm now defaults to the builder's user/group if it can't look
up a uid/gid.

Note You need to log in before you can comment on or make changes to this bug.