I just truncate the name if its length is more than 66, and it doesn't impact
the RPM package generation and extraction. Thanks
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
See
https://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/pkgformat.html
covers the fundamentals of rpm package file format,
http://ftp.rpm.org/max-rpm/s1-rpm-file-format-rpm-file-format.html has more
background and rationale about the evolution.
But as ffesti already
Closed #974.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/974#event-2917182677___
Rpm-maint mailing list
I meet some problem when try to setup the dev env for debugging. Could you
point out the lead structure definition in source file? I find some code that
the name length is "66" in struct "rpmlead_s" which I think it's deprecated.
Thanks
--
You are receiving this because you are subscribed to
The java program create the RPM package with a spec file as input.
It's hard to tell why it can't work as only the extraction by standard RPM
command failed.
Maybe I can debug the RPM source code to find why it reports the err then I can
update the java code to meet the standard RPM extraction
No, the package name should not be limited. It looks like there is a bug in the
code creating the lead. But it is hard to tell where exactly this is. If your
Java program is creating the package directly without creating a spec file and
then running rpmbuild I would advice checking the code
Thanks, Festi. In fact, I use a java program which to create RPM package, which
refer to an old RPM API (RPM 4.4.2).
I can use it to create a RPM package and use the standard RPM command to parser
it, like rpm/rpm2cpio command.
I meet the name length limit problem when create RPM package, then
The lead is not really the data that's being used and it is only there for
legacy purpose. But RPM is expecting it to be in the format that is in the
code. You can't just change that data structure. Also this field contains the
NEVR of the package (Name:Epoch-Version-Release)
The actual name