nodirtokens just refuses to stay fixed. I think this line from lib/rpmlead.c speaks for itself: l->major = (_noDirTokens ? 4: 3);
What are you attempting with nodirtokens? That code went obsolete years and years ago. The code was used to bridge between rpm-3.0.4 -> rpm-3.0.5 Meanwhile a value of 4 in the lead existed for a short period of time before being forced (by LSB) to _ALWAYS_ be 3 independent of _nodirtokens. I.e. the code as written is just wrong.
Given that nodirtokens has been fixed a few times during rpm 4.x, I don't think the current maintainers share your view, Jeff. As for expectations, I expect it to do what rpmbuild states it does: --nodirtokens generate package header(s) compatible with (legacy) rpm[23] packaging Which in practice seems to mean versions 3 in the header and careful handling of file lists.
Uff, what a wonderfully dumb thinko :) Fixed in upstream now by just hardwiring the lead major to 3, conditionally using 4 does no good to anybody: the lead version is just irrelevant for anything but LSB "compliance" and LSB wants 3 in there.
Thanks, although it is a bit more than LSB compliance. Older versions of RPM seem to check the version number as I discovered this issue when trying to install an RPM on a thin client that uses an ancient version of RPM.
Re comment #2: Given that I asked a question, and stated a historical fact, I'm not sure how you can infer my view point. Have fun!
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.