This is old and should probably deleted

Happiness and World Domination

Enrico on Happiness and World Domination

stuff that I do

quite outdated, but anyway:

I also maintain some information on this page, as I really like the ease of use of :)

random notes

git notes for migrating from svn-buildpackage setups to git and pristine-tar

git svn clone svn+ssh:// tuxtype-svn.git

git remote add tuxtype-svn ../tuxtype-svn.git
git fetch tuxtype-svn
git checkout tuxtype-svn/master
git checkout -b debian

git symbolic-ref HEAD refs/heads/upstream
rm .git/index 
git clean -fdx 
git-import-orig --upstream-branch=upstream --debian-branch=debian --pristine-tar ../../tux4kids/tuxtype/people/holger/tuxtype/tarballs/tuxtype_1.8.1.orig.tar.gz

git checkout debian
git merge upstream

git add debian/gbp.conf

git tag -s debian/1.8.1-5 -m 'Debian 1.8.1-5 release'

# for piuparts

git-import-orig --upstream-branch=master --no-merge --pristine-tar ../piuparts_0.42.tar.gz

svn-buildpackage: MergeWithUpstream

adding patches with quilt to a package

  1. add quilt to build-depends
  2. create debian/patches/ and put the patches there
  3. cd debian/patches ; ls > series

  4. add "QUILT_PATCHES=debian/patches quilt push -a || test $$? = 2" to the configure target in debian/rules

  5. add "QUILT_PATCHES=debian/patches quilt pop -a -R || test $$? = 2" to the clean target in debian/rules

  6. enjoy :)

Example for a python package "cython":

    QUILT_PATCHES=debian/patches quilt push -a || test $$? = 2
    QUILT_PATCHES=debian/patches quilt pop -a -R || test $$? = 2

Another option is to just use

include /usr/share/quilt/quilt.make

instead of 4. and 5, and then make the "configure" target depend on "patch" one, and "clean" target on the "unpatch" one:

configure: patch

clean: unpatch

adding more patches later

  1. export QUILT_PATCHES=debian/patches
  2. quilt new 200-etc-olsrd.patch
  3. quilt add
  4. vi
  5. quilt refresh

How to use it with svn-buildpackage:

  1. /usr/share/svn-buildpackage/contrib/svn-do (better, put it in your PATH)
  2. work with patches as described above
  3. exit 0

svn, knowing the diff before updating

  1. svn diff --revision HEAD
  2. svn up


more random stuff

  mkdir initrd
  cd initrd
  gzip -dc /var/lib/tftpboot/ltsp/i386/initrd.img| cpio -id

fix bashisms


a crazy idea to be discussed post lenny release...

i've talked with luk at debconf8 about point releases like debian-edu needs, in debian. and he told me, that people now complain about the less strict (=more frequent) updates of stable (basically, some people dislike them as every change for some is work, so they really only want critical or security fixes). so then i came up with the idea of doing new suite called lenny-feature-updates (similar to proposed-updates) - which would have less strict rules than updates to stable. i'd really like to go this path for squeeze, or maybe even lenny

some rules apply, just like for bpo or stable-proposed-updates (but obviously different rules)