Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2016-01-10 00:07:06 →
Size: 8963
Editor: PaulWise
Comment: fix link
← Revision 3 as of 2016-01-10 00:41:38 → ⇥
Size: 8908
Editor: PaulWise
Comment: drop duplicate link
Deletions are marked like this. Additions are marked like this.
Line 148: Line 148:
 * http://people.debian.org/~joeyh/d-i/test-logs.html

This is old and should probably deleted

Contents

  1. This is old and should probably deleted
    1. Happiness and World Domination
    2. stuff that I do
    3. random notes

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 wiki.debian.org :)

random notes

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

git svn clone svn+ssh://holger@svn.debian.org/svn/tux4kids/tuxtype/people/holger/tuxtype/trunk/ 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-buildpackage

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

  • cd trunk

  • svn propset mergeWithUpstream 1 debian

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": 

configure/cython::
    QUILT_PATCHES=debian/patches quilt push -a || test $$? = 2
clean::
    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 Makefile.inc
  4. vi Makefile.inc
  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

usertags

more random stuff

  • :zi in vim: disable folding
  • vim: revert undo / redo: ctrl-r
  • screen: always start with -S name
  • ctrl-a esc: enter copy-mode in screen, useful to move around
  • dpkg --compare-versions 0.79-3.2~holger1 lt 0.79-3.2 ; echo $?
  • To put a package on hold: echo pkgname hold | dpkg --set-selections
  • To remove the hold: echo pkgname install | dpkg --set-selections

  • echo 'Acquire::PDiffs "false";' > /etc/apt/apt.conf.d/99pdiff

  • netcat for dummies:
    • on host1: cat file | nc $host2 6666

    • on host2: nc -l -p 6666 | cat > file # needs to be interrupted with ctrl-c

  • alioth: as admin edit roles to configure a project
  • ssh qa.debian.org /org/qa.debian.org/mia/mia-query fubar@email

  • give a package back to rebuild it: <zobel> mail the buildd "retry" in body with the correct subject iin the mail, that usually means, just preply to the build log (and send the mail to buildd@foo)

  • svn propset svn:executable ON $file
  • svn propedit svn:ignore .

  • svn diff -r BASE:HEAD

  • openoffice.org: in menu -> format -> autoformat -> while entering (während der eingabe)

  • reporting kernel bugs: reportbug linux-image-$(uname -r)

  • compare ssh-fingerprint with the one in known_hosts: ssh-keygen -l -f .ssh/known_hosts|grep $HOSTNAME

  • shrinking virtualbox images
    • (dd if=/dev/zero of=$partition)
    • VBoxManage modifyvdi diskimage.vdi compact

  • press ~. to interrupt a ssh connection which has died

  • mediawiki navigation: edit /wiki/MediaWiki:Sidebar

  • http://stateful.de/~carsten/bin/apt-listrepository - tells where packages are installed from - [bug:504460]

  • [444028] acpid: problems with ACPI critical trip points

  • dinstall/mirror push:
    • dinstall: 1|7|13|19:52.
    • mirror push: about one hour later
  • examine initrds: 

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

fix bashisms

  • replace non-standard "==" by standard "="
  • replace non-standard "source" statement by POSIX "dot" command

lenny-feature-updates

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)

  • in general: no new upstream versions - use bpo for that
  • bugs fixed can have any severity, but the fix needs to be accepted in testing