Tag Info

Hot answers tagged

3

The command apt-get source pulseaudio will download the current source package files and extract them automatically for you. You will find the rules file in the debian directory inside the newly created source directory named after the package, here is how that looks on my installation: livewire@za20:~/Downloads$ apt-get source pulseaudio Reading package ...


2

Generally, <name>_<version>.orig.tar.xz or <name>_<version>.orig.tar.gz is the source archive, as released by the project. It's simply renamed to fit the vagaries of the Debian packaging system. Usually, for packaging purposes, you need to unpack <name>_<version>.orig.tar.xz in the current folder and then place the ...


2

If you received an email with Approved or Rejected, then you've uploaded your package successfully (but then it got rejected by any reason). See the rejected message: Source/binary (i.e. mixed) uploads are not allowed. Usually this is caused because you didn't created your package with debuild -S.


1

I assume that your target program is a c/c++ or similar language. You can include all files in one binary packages. But still the best to separate development files in another one. *-dev (not -devel) should include only headers, statics libs, shared libs and even binary tools if these tools only used for development. You can declare multiple binaries ...


1

The packaging (ie debuild) is not the hard part here: building the application is. There are many ways to build i386 binaries on a 64bits system Using a 32bits virtual machine Installing one via virtualbox is straightforward. This is by far the easiest but it will take a significant amount of disk space and you will need to setup the entire system from ...


1

For dependency information, you can see /var/lib/dpkg/status, which basically lists the contents of debian/control (with some additional information about the package itself) for each installed package. Additionally, you can look into /var/lib/dpkg/info to see the files installed, pre/post (un)installation scripts (if any), and configuration files (if any) ...


1

Use this command instead of dpkg-buildpackage -us -uc and all is fine: DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -rfakeroot -us -uc -b Tests are disabled and there are only built binary packages.



Only top voted, non community-wiki answers of a minimum length are eligible