Patchwork

Source

git clone git://github.com/getpatchwork/patchwork

Mailinglist/Maintainer/URL

Dependencies

Software

Version

X-( Wheezy

(./) unstable/sid

Phyton2 Interpreter

>= 2.7

(./) 2.7.3-4

(./) 2.7.3-4

Phyton-Django

>= 1.5

X-( 1.4.5-1+deb7u4

(./) 1.6.1-2

phyton-psycopg2 Bindings

>= 2.0

(./) 2.4.5-1

(./) 2.4.5-1

Apache2 Webserver

>= 2.2

(./) 2.22-13

(./) 2.4.7-1

or

lighttpd Webserver

>= 1.4

(./) 1.4.31-4

(./) 1.4.33-1

mta-transport-agent

-

-

-

modpython libapache2-mod-python

>= 3.3

(./) 3.3.1-9

(./) 3.3.1-9

libjs-jquery

>= 1.3

(./) 1.7.2+dfsg-1

(./) 1.7.2+dfsg-1

MySQL

>= 5.5

(./) 5.5.33+dfsg-1

(./) 5.5.35+dfsg-1

or

Postgres

>= 9.0

(./) 9.1.11-1

(./) 9.1.11-1

Bash (some scripts)

>= 3.0

(./)

(./)

ITP Request

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703226

Staging Area

https://github.com/tijuca/patchwork

Helpers

Platform Specific Defines

As I always search for that while debugging KFreeBSD or Hurd build issues ...

gcc -dM -E -x c++ /dev/null # for C++
gcc -dM -E -x c /dev/null   # for C

Platform Endianness, Debian architectures and compiler host names

I can't remember mostly of the time what relationship between the Debian architecture names, Compiler specific hostnames and endianness exists ...

TODO: move this to ArchitectureSpecificsMemo

Debian architecture

Compiler host name

Endianness

RC platform

i386

i686-pc-linux-gnu

LE

amd64

x86_64-pc-linux-gnu

LE

armel

arm-unknown-linux-gnueabi

LE

armhf

arm-unknown-linux-gnueabihf

LE

arm64

aarch64-unknown-linux-gnu

LE

mips

mips-unknown-linux-gnu

BE

mips64el

mips64el-unknown-linux-gnuabi64

LE

mipsel

mipsel-unknown-linux-gnu

LE

ppc64el

powerpc64le-unknown-linux-gnu

LE

s390x

s390x-ibm-linux-gnu

BE

non RC platform

alpha

alpha-unknown-linux-gnu

LE

hppa

hppa-unknown-linux-gnu

BE

hurd-386

i686-pc-gnu

LE

kfreebsd-i386

i686-pc-kfreebsd-gnu

LE

kfreebsd-amd64

x86_64-pc-kfreebsd-gnu

LE

m68k

m68k-unknown-linux-gnu

BE

powerpc

powerpc-unknown-linux-gnu

BE

powerpcspe

powerpc-unknown-linux-gnuspe

BE

ppc64

powerpc64-unknown-linux-gnu

BE

sh4

sh4-unknown-linux-gnu

LE

sparc64

sparc64-unknown-linux-gnu

BE

x32

x86_64-pc-linux-gnux32

LE

Setting up Hooks with git-buildpackage

Every time I new set up my PC I also can't remember that. :-)

Setting up some global Hooks.

sudo mkdir /etc/pbuilder/hooks
cd !$
sudo ln -s /usr/share/doc/pbuilder/examples/C11screen
sudo ln -s /usr/share/doc/pbuilder/examples/D80no-man-db-rebuild

And enable them in the pbuilderrc.

sudo echo "HOOKDIR=/etc/pbuilder/hooks" >> /etc/pbuilderrc

Syncing source package and Debian files somethere

Instead of using scp with a complex call simply use dmcd

$ dcmd scp mypackage_99.2-1~exp1.dsc somehost.org:/foo/bar/mypackage-99.2

Searching for $package in Build-Depends,Build-Depends-Arch,Build-Depends-Indep

For preparation of a mass bug filing or simply research about the whole archive (depending on the used entries in sources.list), needs a installed package dctrl-tools and devscripts

$ grep-dctrl -FBuild-Depends,Build-Depends-Arch,Build-Depends-Indep $package /var/lib/apt/lists/*.debian.org_debian_dists_*Sources | dd-list --dctrl

make git-archive more useful

Sometimes I need to make a orig.tar.xz tarball from a upstream repo.

$ git config tar.tar.xz.command "xz -c"
git archive --format=tar.xz --output=../mypackage_99.2.orig.tar.xz mypackage-0.99.2 # use a tag or ID

Using OnBoard LED's on Cubieboard2

As the Allwinner OnBoard LED's are specific to the DTS implementation there is no Debian package or way to configure them. To use the LED's for anything useful you have to write the wished usage of them into a trigger file. The location of these files are predefined by the Device Tree definition, for the CB2 the location for the blue LED is in /sys/class/leds/cubieboard2:blue:usr/trigger and the green LED is triggered via /sys/class/leds/cubieboard2:green:usr/trigger.

There are various things on a CB2 that can be shown by a LED activity (other Allwinner devices may contain more options!).

To let the kernel show any specific action on than just write the keyword into the trigger file as root. For example if you want to see on the blue LED the activity of CPU0 and on the green LED R/W actions on the MMC1 put the following lines into /etc/rc.local before the exit 0 line.

....
echo cpu0 > /sys/class/leds/cubieboard2\:blue\:usr/trigger
echo mmc0 > /sys/class/leds/cubieboard2\:green\:usr/trigger
....

To enable/disable the LED activity without loosing the predefined action you can switch on/of the LED by writing into the brightness trigger as root.

echo 0 > /sys/class/leds/cubieboard2\:blue\:usr/brightness # switch of LED
echo 0 > /sys/class/leds/cubieboard2\:green\:usr/brightness # switch of LED

echo 1 > /sys/class/leds/cubieboard2\:blue\:usr/brightness # switch on LED, default state after boot
echo 1 > /sys/class/leds/cubieboard2\:green\:usr/brightness # switch on LED, default state after boot

Reading SoC Temperature on Cubieboard2

The path to the temperature on the SOC is depending on the DTB, so it differs between Jessie and Stretch. For Jessie the current value of the temperature on the board is stored in the following file.

$ cat /sys/devices/soc\@01c00000/1c25000.rtp/hwmon/hwmon0/temp1_input
30600

While Stretch uses a different path.

$ cat /sys/devices/platform/soc@01c00000/1c25000.rtp/hwmon/hwmon0/temp1_input
21300


CategoryHomepage