In the quimup-packaging repository on github, I track releases of Quimup (formerly known as Guimup), another graphical MPD-client written in Qt5. One may use the repository to create the corresponding installation packages for Ubuntu and Debian, or use the packages I’ve created.

 

Using and installing the packages

Quimup on Ubuntu

Ubuntu users can use the corresponding PPA for easy package installation by opening a terminal window (by pressing CTRL+ALT+T on the keyboard) and copying/pasting the following text, followed by pressing ENTER:

sudo add-apt-repository -y ppa:quimup/quimup
sudo apt-get update
sudo apt-get install quimup

 

Quimup on Debian

Users of Debian can install quimup using the following actions from the command line, which involves importing my public gpg key from MIT’s keyserver in to apt, and then adding my custom apt repository.

# become root
wget -O - "https://pgp.mit.edu/pks/lookup?op=get&search=0xFBF05DDFC04DF16B" | apt-key add -
echo "deb https://lacocina.nl/debian lacocina-stable/" | tee  /etc/apt/sources.list.d/lacocina.nl.list
apt-get update
apt-get install quimup

Alternatively, you can just download a single deb:

# become root
APPNAME="ssrc"
APPVERSION="1.4.0"
BUILDVERSION="3"
ARCH=$(uname -m | sed 's/x86_/amd/;s/i[3-6]86/i386/')
DIST=$(grep ^VERSION= /etc/os-release | sed 's/^.*(\([[:alpha:]]*\))"$/\1/')
DEB="${APPNAME}_${APPVERSION}-${BUILDVERSION}_${ARCH}~${DIST}.deb"
wget "https://lacocina.nl/packages/${DEB}"
dpkg -i ${DEB}

Quimup packages are available for all current Debian versions (amd64 only) and can be downloaded directly from https://lacocina.nl/packages/.
 

Q&A

Looking for other distibutions?

The upstream developer keeps a list, an arch package is available in the aur.

Notice a problem with the (upstream) software itself?

Please contact the upstream developer.

Have a bug regarding Debian and Ubuntu packaging?

Please submit a new bug in the appropriate issue tracker on github

Packaging updates

Changelog

• March 2015: upstream release 1.4.0, May 2015: upstream/1.4.0, debian/1.4.0-2
• June 2014: upstream release 1.3.2, (no packaging done)
• Dec 2013: upstream release 1.3.1, upstream/1.3.1, debian/1.3.1-1

Current packages

Quimup	Distribution	Release
1.4.0	Ubuntu	15.10, 15.04, 14.10, 14.04 LTS
	Debian	jessie/stable (8), stretch/testing, sid/unstable
1.3.2	(n.a.)	(n.a.)
1.3.1	Ubuntu	12.04 LTS, 12.10, 13.04.1 and 13.10.1
	Debian	squeeze(6), wheezy (7)

---

Technical details

From upstream tarball to local Debian packages and an Ubuntu ppa

After creating a basic working structure for packaging, I built the packages using the workflow described in PackagingWithGit on the Debian Wiki. For it to work reasonably smooth, I use the following branch layout:

master         # development of files in the ./debian subdirectory
debian/x.x.x-y # tagged branch for a debian package release
upstream/x.x.x # tagged branch for an upstream release

When the original tarball from Sourceforge is updated by Coon, you can update the master branch in the git repository using:

## 1. create an upstream/x.x.x branch,  
##    download the latest upstream tarball from sourceforge, 
##    and extract it contents in to the new branch, and switches
##    back to the `master' branch, where changes in the 
##    `debian'-subdirectory are tracked:
git-import-orig --uscan --verbose 
## 2. manually update files in the ./debian subdirectory (debian/changelog, 
##    debian/control, and if necessary debian/rules:
${editor:-emacs} debian/control debian/rules # ...
## 3. increase the debian version in debian/changelog
dch -i 
## 4. try to build the new version
git-buildpackage 
## 5. repeat 3. and 4. until it works, possibly adding `--git-ignore-new' to
##    `git-buildpackage'
## 6. commit the changes (to master)
git commit -a -m '(describe fix, reference github issue #x)'
## 7. tag the build; this creates the git branch/tag debian/x.x.x-y, 
##    where y is the debian version for the x.x.x. upstream version.
git-buildpackage --git-tag --git-ignore-new
## 8. publish the tagged debian/x.x.x-y version as a new branch.
## when only the ./debian files are updated, specify y like former y + 1
git push origin debian/x.x.x-y
## 9. publish the changes to the published master branch (necessary for bzr)
git push
## 10. request a new bzr `import` at https://code.launchpad.net/~quimup/quimup/HEAD
## 11. force a new build of the daily recipe at https://code.launchpad.net/~quimup/+recipe/quimup-daily

 

This updates the (pristine) sources from the latest Sourceforge tarball in the upstream/x.y.z branch, while having the debian-version tagged branch in debian/x.y.z-a and leaving my packaging work intact in the master branch. Super!

The changes in the github branch are automatically pulled by the bzr branch in launchpad on a daily basis. From that bzr branch I’ve created a daily packaging recipe, which builds packages for recent Ubuntu releases as soon as a change is detected in the bzr branch.

Phewww…

Obligatory screenshots