rpmbuild fails to validate path name requirements
Bug #638589 reported by
Jeff Johnson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| RPM |
New
|
Undecided
|
Unassigned | ||
| Fedora |
Won't Fix
|
Low
|
|||
Bug Description
tracker
Revision history for this message
|
|
#3 |
| tags: | added: debuginfo fedora |
| Changed in fedora: | |
| importance: | Unknown → Low |
| status: | Unknown → Won't Fix |
To post a comment you must log in.
rpmbuild apparently has strict requirements on the path names used during a
build. However before rpmbuild begins to run it does not validate the path names
to verify they are compliant with its internal requirements and instead will
process almost the entire build before failing with a cryptic error message
related to 1 character length differentials between arguments to a script
rpmbuild invokes.
More info from an email thread:
> Ok, it's simply as it says. /rpmbuild/build is 15 chars and /usr/src/debug
> is 14 chars. That's just a bad choice for the directory name. In koji
> builds go under /builddir/
> The default for vanilla rpmbuild is /usr/src/
>
> It's a technical limitation of the debugedit program that, like the error
> message says, the length of the top build directory name has to be 14 chars
> (to match /usr/src/debug), or more than 15 chars. It does a very limited
> kind of rewriting of the very complex DWARF formats, so there has to be
> enough room in the existing string table for the new directory name.
> Making it able to cope in the general case opens huge cans of worms, and is
> absolutely not going to happen any time soon (or ever in that program as it
> exists today).
>
> Suffice it to say it is far, far more work than is justified to avoid the
> arcane but trivial caveat that the base directory name used for builds must
> be at least 16 chars long.
Thank you very much Roland, I really appreciate the explanation! I would have
been really stuck without it.
The only thing I might take issue with is your belief the error message is
patently obvious. There is no reference to the top build directory or the
requirements for it's length. Just something cryptic about 1 character
differentials in arguments passed to what is essentially a private rpm utility
unlikely to ever be invoked directly.
May I suggest the error message be replaced with something which would direct a
developer to the root cause of the problem, especially since this is a somewhat
arcane limitation.
This is what rpmbuild spits out:
extracting debug info from
/var/tmp/
/usr/lib/
more than 1 char shorter
error: Bad exit status from /var/tmp/
I truly would never have matched the fact a build directory of "/rpmbuild/build"
was the offending culprit, the string does not even appear in the error message.
Maybe rpmbuild should stop immediately with an error if you invoke it with a
topdir which is unacceptable to it's internal operation.