Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is a general *.deb package question, although the package in question happens to be a kernel package. There is all kinds of info on building a *.deb file from scratch, but I can't seem to find any info on editing an existing *.deb file.
Background:
I built a customized Debian kernel via make-kpkg, it produced a *.deb that I installed via dpkg. However, I noticed that I fat-fingered the "--version" parameter on the command-line, so I deleted the *.deb and recompiled with a proper "--version".
Question:
Looking back, would it have been feasible to un-archive the *.deb, edit the "control" file to change the version, re-archive the *.deb and install it?
It seems to me that this may not have worked, since I am assuming (hoping) that such messing around with a Debian package would cause dpkg a problem.
A deb file is just an ar archive. So, if you really want to mess around with it you can "ar x" it, edit some files, and then "ar c" it back together again. Whether or not this will cause problems with the package depends on exactly what you change. I suspect that in this instance there would be a large number of both text and binary files (not just the control file) that contain that version string and as such I would expect problems.
So, rerunning make-kpkg was probably the best thing to do.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.