grizzler wrote:They're still releasing security updates. The one mentioned above is less than a month old.
That's what I was missing. Excuse me for being thick, GeneBenson.
Let's see if I can double my winnings:
Schoelje wrote:Unfortunately, after 3 hours of trying, I was unable to compile Alacarte for Debian.
It kept throwing missing dependencies which I could not find in the repositories and had to compile myself.
Hard-won lesson: let debian handle debian's dependencies.
- Code: Select all
$ apt-cache policy alacarte
$ sudo apt-get build-dep !$
$ apt-get source !$
# I see the version we have is already ahead of the repo's... is this the patch you posted to github?
$ cd alacarte-3.5.3 && dpkg-buildpackage -b -j$(nproc)
# debian's source compiles; no surprises
Pull upstream GNOME into the debian package:
- Code: Select all
$ git init && git commit -am 'initial'
$ git remote add gnome git://git.gnome.org/alacarte
$ git fetch --verbose gnome
$ git checkout -b integration
# incremental bumps with `git merge -s recursive -Xtheirs x.y.z` do succeed
# I'm sure blindly merging breaks things
# 3.5.3 -> 3.5.4 -> 3.5.5 -> 3.7.2
# `./configure && make` still works, but then, it's python
$ sudo checkinstall
# adjust the version, something like 3.7.2+kaboom
# now we have a proper .deb
Installing that and running alacarte
from a terminal fails
. Rolling back to debian's version also fails
I don't know py/gtk well enough to have much luck chasing the diffs. (sample
) You can see debian's patches
backed out; I tried reapplying those. No joy at runtime.
So, I'll keep what's in the RC and I upped the version to 3.7.1
You're asking for version hell, I think. AFAIK it's conventional for maintainers to use a suffix, so "3.5.3+schoelje2" would never conflict with GNOME's "3.5.4" tag, or anything similar debian might roll out.