Tag Info

New answers tagged

1

According to man dh_installcron: --name=name Look for files named debian/package.name.cron.* and install them as etc/cron.*/name, instead of using the usual files and installing them as the package name. So name your debian/package-name.foobar.cron.d, and add to debian/rules: override_dh_installcron: dh_installcron --name=foobar


1

I've not tried myself the following commands, but they should work with none or minimal modification. How can I build a package from the development branch to install locally on my system ? Download branch $ bzr branch lp:~pmarchwiak/synapse-project/recoll-plugin Install dependencies $ sudo apt-get install devscripts equivs dh-autoreconf ...


1

Depends on what you're trying to achieve. If you need a package to conveniently uninstall later, then checkinstall would be a good choice: https://help.ubuntu.com/community/CheckInstall


0

It seems the_Seppi and bodhi.zazen are correct: the only clean way to do this is using a maintainer script to do the deed. From /usr/share/doc/ca-certificates/README.Debian: How to install local CA certificates ------------------------------------------------------------------ ... If you want to prepare a local package of ...


1

You can also create a Dsomething file stating the repository you want to add, for example, if HOOKDIR="${HOME}/.pbuilder-hooks/", then a file called $HOME/.pbuilder-hooks/D10addppa could exist with the following content: #!/bin/sh echo "deb deb http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu raring main" >> /etc/apt/sources.list echo "deb ...


0

You are missing the dependencies required to build your app, in the Build-Depends section of the debian/control file. Also, you should use sbuild or pbuilder to test local builds of your package, before uploading to a PPA on Launchpad, to ensure the package will build.


1

You will likely need to build a Debian package (.deb) and submit it for inclusion in the Debian or Ubuntu software repositories. Creating a package can be a complex process; detailed instructions are available on the Ubuntu Packaging Guide here.


1

To prevent dput from uploading (again) your orig.tar.gz file you need to remove it from the source.changes file. To do so, you basically have to change your call to the build command to add the -sd option. It will force the exclusion of the original orig.tar.gz source. From the dpkg-genchanges man pages: -sd Forces the exclusion of the original ...


0

It turned out to be the fault the crappy Ubuntu repo used by Gazebo. Apparently, it provides packages that conflict with those in the standard repo. I removed its PPA and uninstalled all broken packages and that resolved the error.


1

You're right, you'll have to follow the process to request a Backport: Backports must be approved by the Ubuntu Backporters team, but anybody can request a backport. As backports require testing before they can be approved, the backports team recommends that requesters of backports also test them when possible. Backports are requested by ...


0

Could you Add your debian/rules file as now I'm just guessing: At here Minimal debian/rules. With the Trusty the package building didn't work as the dh_auto_clean was executed too early. changelog at here: add override_dh_auto_clean to the debian/rules. With the Trusty the make is executed before the configure step; dh_auto_clean -> make (?) I ...



Top 50 recent answers are included