Tag Info

New answers tagged

0

You can change the version number in the control file, sampkg/DEBIAN/control The control file is the core of the Debian package; it contains all relevant metadata. Things such as package name, version, supported architectures, and dependencies are all included in this file. Package: sampkg Version: 1.0.0 Architecture: all Essential: no Section: web ...


0

Have a look at git-buildpackage: Customizing snapshot numbers If the auto incrementing of the snapshot number doesn't suite you needs you can give any python expression that evaluates to a positive integer to calculate the new snapshot number: gbp dch -S -a --snapshot-number=1 gbp dch -S -a --snapshot-number='snapshot + 2' gbp dch -S -a ...


2

Because, your package is installed in release/environment that it will not able to work in, That means your packages control dependencies missing something. What I expect that you haven't put dependencies version conditions, which could used to let package to be installed on single release if the dependency version available only in that release, example ...


2

Within a Debian package, there's no way to say "Allow installations on 14.04 only". That has to happen at the apt repository level (which I'll get to shortly later). The semi-exception to this is that because Trusty is newer than Precise, Trusty will have some library packages renamed (which, as long as the user's not using a PPA that provides these ...


1

I would continue to use the pre/post inst scripts, preinst - This script executes before that package will be unpacked from its Debian archive (".deb") file. Many 'preinst' scripts stop services for packages which are being upgraded until their installation or upgrade is completed (following the successful execution of the 'postinst' script). ...



Top 50 recent answers are included