Support for creating installer packages

Hello, lately, I created two packages that do little more than wrap software written in a scripting language (one Java, one Perl) so I could put them in a local repository for easy installation and deinstallation. In both cases, I expect upstream versions to change often. So I will probably find

Modifying a file from another package (rather than replacing it)

Hi (and happy hollidays)! I've written a couple of extensions to pbuilder. When my package gets installed, a file from the pbuilder package (/usr/sbin/pbuilder) must be modified for my extension to work. I'm looking for the "proper" way to apply a patch to that file. I would like to patch rather

Re: Modifying a file from another package (rather than replacing it)

Am 25.12.2010 13:25, schrieb Ben Hutchings: >> I've written a couple of extensions to pbuilder. When my package gets >> installed, a file from the pbuilder package (/usr/sbin/pbuilder) must be >> modified for my extension to work. I'm looking for the "proper" way to >> apply a patch to that file. >

Re: Modifying a file from another package (rather than replacing it)

Am 25.12.2010 20:18, schrieb Michael Banck: > > Why can't this be part of pbuilder itself? Did your patches got > rejected by the pbuilder author and if so, what was his rationale? > Maybe if he thinks they should not be part of pbuilder, they shouldn't > be part of another package either. > I

i386.changes vs source.changes

Hi, I recently noticed that when I'm packaging software sometimes a i386.changes file gets created, and sometimes a source.changes file gets created. I couldn't find an explanation in the New Maintainer's Guide or in the Policy Manual. I guess its something to do with the setup or type of the pac

Re: i386.changes vs source.changes

Luk Claes schrieb: > Malte Forkel wrote: >> Hi, >> >> I recently noticed that when I'm packaging software sometimes a >> i386.changes file gets created, and sometimes a source.changes file gets >> created. >> >> I couldn't find an explan

Re: i386.changes vs source.changes

Philipp Kern schrieb: > [Sorry about the terse reply.] > Not at all. Thanks for responding! > On 2009-05-14, Malte Forkel wrote: >> Well, just judging from a limited sample, all source.changes and >> i386.changes files I checked contain both Source and Binary fields. &g

Re: i386.changes vs source.changes

Russ Allbery schrieb: > Malte Forkel writes: > >> After some more checking and thinking, I guess I know what's causing >> my problems: Its me, probably! I assume the source.changes files are >> created while I setup everything for building a package, e.g. by >>

how to satisfy a patched build-dependency in debuild / pdebuild

Hi, an optional patch that I'd like to add to a package requires an additional build dependency. If I append that dependency to Build-Depends in debian/control as part of my patch, it is not checked in time. It seems, the build dependencies are checked (by debuild) or checked and satisfied (by pde

Re: how to satisfy a patched build-dependency in debuild / pdebuild

Sandro Tosi schrieb: > On Wed, May 20, 2009 at 14:28, Malte Forkel wrote: >> Hi, >> >> an optional patch that I'd like to add to a package requires an >> additional build dependency. If I append that dependency to >> Build-Depends in debian/control as par

Adding and using repositories during package installation?

Hi, I'm thinking about creating a metapackage to setup a software development environment. It would not only have to depend on some prerequisite packages, but also add repositories and install a package from one of them. Is there an acceptable way to do that? I guess I shouldn't use things like '

Re: Adding and using repositories during package installation?

Am 22.10.2014 um 15:38 schrieb Neil Williams: > Don't go messing with apt trusted files either, package the key as a > keyring package (like emdebian-archive-keyring) and depend on that. I'm nore sure: Do you think adding files in /etc/apt/sources.list.d (and using debconf to ask the user perform

Re: Adding and using repositories during package installation?

Am 22.10.2014 um 15:46 schrieb Wookey: > I take it that this package needs to be installed on the main system, > not just present for builds? Right, not just for builds. > If you use sbuild for builds, the new (in sbuild 0.65 - targetted for > jessie) --extra-package and --extra-repository option

apt-get fails with "system" message bus problem

Hello! Two weeks ago I posted the following question on Debian User. Since nobody on that list could help, I'm now trying my luck here. I'm sorry should you have already seen this before... I have written a little script to download a package from a repository specified on the command line. E.g.

Using Qt debug libraries without configure and qmake

Hi, I need your advise on how to deal with the way Debian packages the debug version of Qt libraries. I'm trying to package an existing software that includes a small Qt application. The software is not using autotools or qmake but fixed Makefiles. Building the release version is accomplished by

Re: Using Qt debug libraries without configure and qmake

Thanks for your help, guys! Now that I (hopefully) understand the Debian approach to providing debugging information, its obvious why I didn't find any useful information before: My questions were wrong. There are two questions which I'd still like to ask: - Is there any summary on how to provid

Managing left-over control files

Hi, I'm writing a transitional package to handle a software name change. The transitional package 'depends' on the new package, which itself 'replaces' the old package and takes over some of its control files. All other control files still belong to the transitional package after an upgrade. I ha

Re: Managing left-over configuration files

Am 14.12.2011 00:00, schrieb Malte Forkel: > Hi, > > I'm writing a transitional package to handle a software name change. > The transitional package 'depends' on the new package, which itself > 'replaces' the old package and takes over some of its contro

Re: Managing left-over configuration files

Am 14.12.2011 11:30, schrieb David Kalnischkies: > Hi, > > in general, such questions are better suited for debian-mentors@, > but here we go: > > ... > > I think what you mean is best described/covered with the advice to > have a look at the manpage of 'dpkg-maintscript-helper', but i must > con

How to update control file time stamps

Hi, wasn't there a command to update the time stamps of control files in the debian directory? Thanks, Malte

Re: How to update control file time stamps

Am 16.08.2015 um 16:39 schrieb Malte Forkel: > Hi, > > wasn't there a command to update the time stamps of control files in the > debian directory? > > Thanks, > Malte > > Sorry for being unclear. Some of the control files used for packaging end with a t

Re: How to update control file time stamps

Am 16.08.2015 um 18:02 schrieb Vincent Bernat: > > You can use dch --edit for that, I think. > Unfortunately, that's just for the changelog file.

Re: How to update control file time stamps

Am 16.08.2015 um 18:11 schrieb Bernd Zeimetz: > > you can use the --news option for that, asuming that your file is in a > similar format. > > --news > Specify that the newsfile (default debian/NEWS) is to be edited > Sorry, that doesn't work for me. If I specify any of the README

Re: How to update control file time stamps

Am 16.08.2015 um 19:00 schrieb Paul Wise: > > Sounds like removing the timestamps is the right thing to do here. > That's a creative way to deal with it :-) The footers were created by dh_make (see https://www.debian.org/doc/manuals/maint-guide/dother.en.html#readme). Most README's in /usr/share/d

Problem with dpkg-source -b outside of package source dir

Hello, according to the man page, dpkg-source -b takes an argument that is "the name of the directory containing the debianized source tree". But that does not work for me if the current directory is not the package's source directory. When I execute dpkg-source in the package's source directory