I'm making Ubuntu packages from source code of a geology program. I can make debs on my pc and also Launchpad is able to make binary packages for 32-bit OS.
I noticed an strange behavior of Launchpad. It makes both development (libfoo-dev) and shared library (libfoo) from uploaded source code for i386 though makes only binary package for amd64 from same code.
I'm trying to roll a package of a small and relatively simple Qt program.
The source tree has the appropriately filled debian/ subdirectory, with control, rules, changelog and other nessesary metadata.
In particular, the debian/control file declares about the binary package:
Depends: ${shlibs:Depends}, ${misc:Depends}
-- so that runtime dependencies could be determined automatically.
Howeve
We are switching over to using puppet for configuration management of our Linux based systems. We have several 3rd party packages which contain custom binary installers (think JDK) and are using RPM to build them into local-only non-distributed packages.
I'm running Fedora 11 on a 64 bit HP Pavillion. I installed a program (vuescan) but when I try to run it, I get error
while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
That presumably is because it can't find that library in /usr/lib. (It is of course in /usr/lib64.)
As many of you know the most used packages on GNU/Linux are deb and rpm.
deb is the extension of the Debian software package format and the most often used name for such binary packages.
RPM Package Manager (RPM) is a package management system. The name RPM variously refers to the .rpm file format, files in this format, software packaged in such files, and the package manager itself.
I have a package that incorporates an auto-generated debian/package.postinst.debhelper file into the generated binary. When I put my own code into a file at debian/package.postinst, the auto-generated file is no longer incorporated into the resulting binary.
How do I add custom code to the postinst file in the generated package without blocking the use of the auto-generated code?
is it possible to get file name/function name from shared library or binary.I need to debug the shared library but not able to determine the file name from shared library
In the old days, I create the root folder of my software, create a DEBIAN folder in it, and put all files inside, and use dpkg-deb to create a binary package.
Now I use dpkg-buildpackage to generate deb package from source files, I'm wondering what difference are between them ?
I created my first Debian package today by following the accepted answer at this AskUbuntu question. Everything went fine, and it installed properly afterwards. However, my script is written in python and depends on the BeautifulSoup library.
My plan is to send the package to a friend who I am nearly certain does not have pip or the like installed.
Email this page
