Tag Info

New answers tagged

0

I found the following solution with debsign and the -p option: use debuild without the signature, as you mentioned use then debsign with -p option setting the passphrase to use, like this debsign \ -p'gpg --passphrase-file /home/myname/my_passphrase_file.txt --batch --no-use-agent'\ -S -kMYKEYID package_source.change Still having some other issues, ...


0

There are two questions here, the first is about the icon; this is actually provided by the app data package which has a pre-set number of defined icons. You can find it in: /usr/share/app-install/icons/ But it won't help you put an icon in the software center. No custom packages have icons in the software center. The second is about the screenshot. ...


3

Create a script, in my example foo #!/bin/bash # Create a temporary folder in /tmp dir=$(mktemp -d) # Extract the deb file dpkg -x "$1" "$dir" printf "\n%s\n\n" "$1" # Show the package architecture information dpkg --info $1 | \ awk '/Architecture/ {printf "defined dpkg architecture is:\t%s\n", $2}' # Show the executable format via find and awk for ...


2

Your install file paths should be relative to the package directory (which contains debian/), and not relative to debian/myproject unless you used the -B option. From man dh_install: FILES debian/package.install List the files to install into each package and the directory they should be installed to. The format is a set of lines, where ...


1

A DEB package is just an archive with very specific contents. You can open it in any archive manager you like (such as File Roller or whatever) and the contents are laid out as if you empty it into /. All you need to do is locate a binary and query its file type. This isn't usually necessary - if the filename has i386 in it, it should be i386. Your case is ...


-1

Each deb package declares an architecture, eg. "i386" or "all". However this is only a declaration, and it can be declared wrong (intentionally for some reason, or eg. by error in some package building script). What can you about to verify the real package architecture: # verify, if package supports multiple architectures (and possibly has some bug): dpkg ...


1

Package: ResolutionX Version: 1.0-0 Section: base Priority: optional Architecture: all Build-Depends: debhelper (>= 9) Maintainer: Bilal Bernardot Description: ResolutionX A simple tool to enable you to have your desired resolution without requiring graphics drivers. This paragraph is a mish-mash of fields for source and binary packages. The first ...


2

According to the web page linked below Snappy is just the new name for Click packages see http://news.softpedia.com/news/ubuntu-desktop-built-with-snappy-packages-486556.shtml "The Snappy packages, formerly known as Click packages, are a new approach to package management that allows for transactional updates, and they also provide better security."


3

It says in section 3.1: It's useful to have a slightly customized default, so let's create an alias dquilt for Debian packaging by adding the following lines to ~/.bashrc dquilt is a customized quilt command, not a package unto itself. In short when dquilt is run it runs quilt with a set of customized parameters defined in ~/.bashrc.


1

TL;DR Yes, your versioning would work. A short copy and paste from Building a source package – Versioning Versioning Ubuntu package names are suffixed by the version number of the package. This allows Ubuntu to distinguish newer packages from older ones and so remain up to date. If you're creating an alternative version of a package ...


0

Is JDK 8 required? I tend to get mostly everything to work with openjdk-7-jdk But then again, I have never worked with ant or python-for-android.



Top 50 recent answers are included