Skip to main content


Showing posts from 2013

Hi! My name is... (what?) My name is... (who?) My name is... Slim Shady

On the 21st of November I have become a British citizen, and on the 9th of December I have changed my name by signing a statutory declaration with the following clauses: I absolutely and entirely renounce, relinquish and abandon the use of my former name of Dmitrijs Ļedkovs and assume, adopt and determine to take and use from the date hereof the new name of Dimitri John Ledkov in substitution for my former name of Dmitrijs Ļedkovs. I shall at all times hereafter, in all records, deeds, documents and other writings and in all actions and proceedings, as well as in all dealings and transactions and on all occasions whatsoever, use and subscribe my new name of Dimitri John Ledkov in substitution for my former name of Dmitrijs Ļedkovs so relinquished to the intent that I may hereafter be called, known and identified by the new name of Dimitri John Ledkov and not by my former name of Dmitrijs Ļedkovs. I authorise and require all persons, at all times, to identify, describe and addre

libnih (upstart dependency) ported to kFreeBSD/eglibc

Back in September at the Linux Plumbers Conference in New Orleans, James Hunt and I presented Upstart roadmap , which included porting Upstart to kFreeBSD/glibc. The first milestone is now complete. Libnih is ported to kFreeBSD/eglibc. During the course to get there the following has happened: Petr Salinger (ps-guest) adds waitid() support  to eglibc-2.18 packaging branch using  wait6 syscall Later libnih test-suite gets a test case failure, which is then reported to . Turns out some syscalls on FreeBSD returned bogus siginfo_t.si_status information in some cases. Luckily there is now a full test-case and kernel patch posted by Jilles Tjoelker. Once that's committed upstream, I'll push for uploads to the affected kernels in Debian. A few small patches applied to libnih, mostly adding POSIX compliant header includes and the like.  So with a patched libc and patched kernel one can compile libnih & run its test-suite. There are however some cavea

My Debian Activities: Multiarch & upstart on kFreeBSD hacking

Looks like there is a recent trend to publicize one's debian activities, so I thought I should join in =) Not so sure if MDA acronym would work for these types of posts... Multiarch I have been working on multi-arching additional libraries. In particular I am working on multiarching boost libraries. At the moment boost1.53 multiarched libraries are uploaded in the experimental, and I am still working out the quirks with those. At the same time I have submitted a patch to multiarch libicu-dev, which has been accepted by the maintainer and is currently waiting in new queue.  This brings us closer to multiarching all of boost libraries. But as it has been pointed out at the Multiarch BOF at Debconf'13, one doesn't have to wait for dependencies (be it libs or lib-devs) to be Multiarched before multi-arching your own library. If you do it right (put all or arch-specifi headers in multiarch location, and place libraries in multiarch location, split utilities into a separate p

Now, less cryptic - Cryptsetup changes in Saucy

Previously, whenever cryptsetup package was installed, its modules and utilities were unconditionally copied into initramfs. Making it quite large. But there are legitimate use cases of installing cryptsetup, yet not needing it in the initramfs. One only needs cryptsetup in the initramfs if root filesystem or resume devices are encrypted. I have therefore modified cryptsetup initramfs hooks to only include cryptsetup in the initramfs when necessary. I have tested multiple combinations and here is a small summary: No cryptsetup in initramfs, when: no encrypted devices present non-rootfs filesystems are encrypted (e.g. /var/lib is encrypted) swap is encrypted with random key file (i.e. non-persistent encrypted swap) Cryptsetup is in initramfs, when: rootfs is encrypted ( '/' ) swap is encrypted with a passphrase / key-file (i.e. can unlock & resume from hibernate) CRYPTSETUP='y' option is specified in /etc/initramfs-tools/initramfs.conf The last

abi-compliance-checker & dh / cdbs integration

dh-autoreconf is an amazing addon for running autoreconf, I just love it. abi-compliance-checker is an amazing tool for tracking API/ABI. Wouldn't it be great to glue abi-compliance-checker into dh / cdbs packaging?!  abi-compliance-checker (1.98.8-1~exp1) experimental; urgency=low  .    * New upstream release    * Add dh_acc to generate and compare library dumps at build time,      together with addons for dh(7) and cdbs.    * Bump standards version, bump debhelper to 9, use 3.0 (quilt) format,      update Vcs-Svn field to canonical form, remove obsolete      DM-Upload-Allowed.    * Apply a patch to allow suffixes on a-c-c abi dumps. Horay! So how does one use it? build-depend on dh-acc In your debian/rules call dh_acc somewhere appropriate dh $@ --with acc include /usr/share/cdbs/1/rules/ In your debian/libpackage-dev.acc Write a abi-compliance-checker descriptor (no need to include version) Build your package Copy the generated /usr/lib/$(multiarch)/

FTBFS fixes and other patches available for your package!

Wheeze is planned to release very soon! There is still a fair amount of work to push the release out, but it does mean that a lot of fun can begin for jessie. Over the past cycle in Ubuntu, many packages where synced from experimental, many fixes were applied and many packages were upgraded ahead of debian version strings. If one goes to your package PTS page at: /$SCRPACKAGENAME One can find the following box titled "ubuntu" in it: Please click on "patches for VERSION STRING" to find: Useless irrelevant changes =) oh well, it happens FTBFS fixes due to GCC 4.8 (*) FTBFS fixes due to new GlibC FTBFS fixes due to multiarched Python2.7 and Python3.3 FTBFS fixes due to multiarched Tcl/Tk FTBFS fixes due to Python hash randomisation enabled FTBFS fixes due to Boost 1.53 (*) Fixes to minimise dependencies when bootstrapping packages Fixes to multiarch more and more libraries Fixes to enable package cross-building

avahi + apt-cacher-ng + sbuild ?!

Laptop enters the WiFi network and decides that it wants to build some packages using sbuild. At the same time, on this network there is apt-cacher-ng operating with most of packages cached. On the other hand, there is a project squid-deb-proxy which provides yet another apt proxy, but with the added bonus of avahi discovery. Can we throw all of this stuff together and make it work? Well let's try =) On ubuntu: $ sudo apt-get install apt-cacher-ng squid-deb-proxy-client On debian: Squid-deb-proxy-client is not packaged just fetch and install it. It's really just one python script & one conffile. Or I have published the python script and the config as part of this posts gist . Next all of the avahi magic, really is just publishing a service file & letting the python-script from the squid-deb-proxy-client package find it, and adding apt-conf.d snippet which calls the above mentioned script and generate correct proxy line. But we are running apt

Flash Nexus7 like a rock star

Are you tired of typing a hostname, username, password and WiFi password every time you flash Nexus7 with Ubuntu Core images? Do you wish to automate those boring steps? Do you wish you could reboot into fastboot mode over ssh without reaching and fiddling with volume down and power keys? Now you can! $ bzr branch lp:~ubuntu-nexus7/ubuntu-nexus7/preseed Has a nifty command called $ ./prepare-preseed By default it takes preseed.cfg, attempts to copy wifi.cfg or fetch current active WiFi connection settings from Network Manager's /etc/NetworkManager/system-connections/* downloads latest bootimg and twiddles it to include all of the above. After that you can fastboot flash standard user-data image + this cusom bootimg and voila, upon fastboot reboot ubiquity will come up and will automatically answer all the questions for you and boot into desktop with wifi connected. If you want to customize settings simply edit the sample preseed.cfg. If you do not want to always

X-Chat power-user upload

xchat (2.8.8-7ubuntu2) raring; urgency=low * Optimise default settings for efficient chatting + Make tab completion by default use last-used order, not alphabetical. This way for example if one is chatting with cjwatson, typing "cj " will complete to cjwatson and not cjohnston. Manual migration: ~/.xchat/xchat.conf: completion_sort = 1 + Do not focus channel upon entering, as that clears highlights when using a znc proxy. To be honest, there should be a distinction between manually joining new channels & auto-joining. (LP: #189222 ) Manual migration: ~/.xchat/xchat.conf: tab_new_to_front = 0 + Do not clear buffer with Ctrl-L shortcut. (LP: #304477 ) That shortcut is dominated by web-browsers changing URLs and causes context loss if the focus was accidently left on xchat. * Fix ftbfs, should link against gmodule. * Add xchat-indicator to recommends. (LP: #1048335 ) * Include svg icon (LP: #840673 ) --

Android Debug Bridge (adb) update for 4.2.2

To use adb against android 4.2.2 device one needs updated adb tool. This is now published in raring archive. If you are using quantal or precise, there is a backport published in the usual location of the nexus7-installer. add-apt-ppa -y ppa:ubuntu-nexus7/ubuntu-nexus7-installer Here are the instructions about the new adb from the android development website: When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog. This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.  -- ADB 

Help pick a motherboard for a desktop

I want a desktop computer and I am struggling with all the manufacturers website to find a motherboard with following requirements: supports UEFI Secure Boot has Intel Matrix Storage Technology  (aka Intel Raid) supports Ivy Bridge 22nm CPUs supports up to 32GB or RAM supports dual screens and 3D acceleration using preferably onboard Intel graphics Many manufacturers do state UEFI, but do not say if SecureBoot is available (either out of the box or via firmware upgrade). The Intel Rapid Storage comes with a few chipsets, but in most series it's an optional feature that may or may not be present. Any recommendations? Or ways on how to find these details about motherboards?

Thoughts on Debian package policies

configure,, config.guess & config.sub Are static, included copies of code that should always be rebuild during build. If they are not rebuild at build time, it should be documented/automated the relevant helpers that are needed to rebuild the package. If they are failing to rebuild it's RC since source code is provided that is effectively cannot be modified in the preferred form. They also should not be modified in patch form, as editing generated code is not preferred form of modification. Also it constantly hurts us when bringing up new kernels and architectures (recently kfreebsd, armhf, aarch64). dh_autoreconf is a great tool to achieve thiis s. no native packages Generally if software is useful in Debian Project it can be useful for other debian-like and unlike projects. In particular native packages do not offer the same patching flexibility as 3.0 (quilt), thus forcing downstream distributions to inline modify packages without DEP-3 headers. This hurts u


#stagetaken I have now permanently settled in the UK.