Yukiharu YABUKI の tDiary

_ 今日の予定など

Hostelにカメラを忘れる。あとで取りに行かねば。今日の予定としては、bugs.debian.org and debbugs, embedded debian(netconfも気になるが),

_ armel アーキテクチャ

Debian の Arm って、浮動小数点計算がIEEEではないのでIEEEに準拠するべく arm-el というアーキテクチャで作り直している模様。gcc や カーネルも作り直し。Rikuなどがやっている。tool chain をつくりなおしてばりばりとコンパイルをしているとのこと。

_ [Debconf7] bugs.debian.org and debbugs

upper talk room, 集音マイクやビデオの準備がうまく準備されている。中継を行っているようだが、日本ではリレーサーバーがないので見れない。 アジアでは http://debian.nctu.{net,edu.tw}:8000 で見れるようだ。

メールが届いたら、スパムフィルターを通って、1メール、1プロセスで処理される。

Getting the version information

• Version information from dak
• track of the version from which a package is decended
• Track version by the source/version combination
• Accenssible via Debbugs::Versions

setting per-bug versions

• found - version in which the bug has been found
• fixed - version n which the bug is fixed
• set and removed via found, notfound, fixed, notfixed

Common pitfalls

• Why is my package still buggy?

  • Not built on all architechures
  • Look at the graphs [#419103] http://bugs.debian.org/419103

• Non-versioned -done message

  • Should only be used for invalid bugs
  • Makes RM's job difficult

• Difference buetween "buggy" and "done"

Recent Enhancements

• Subversions
• Version graphs
• SOAP
• Modularization
• Versioning aware archival
• Sorting by age
• Versioning aware bugscan (Steinar)
• Versioning aware mail system
• Encoding aware mail system
• Test suite
• Full text searching
• archive / un-archive support
• force merge
• Searching by owner
• Not showing boring information

Version Graphs

色分けで、治っている。ぶっこわれている状態をツリー状に表示

SOAP Example

SOAPで問い合わせるよう、ワンライナーでも問い合わせられる X-< これは普通プログラムから問い合わせだろう。

Test Suite

.

全文検索

デモあり。

Sorting by age

• Append ;order=age
• Part of the recent Modified at ... ; change

Future Enhancements

• More SOAP methods
• Control abstraction
• Control methods in submit messages
• Integration with MOLE?
• Better statistics
• Templates for all output
• Templates for output

How you can help

• Checkout the bzr

The Debbugs Team

.

_ [Debconf7] embedded Debian --- Emdebian. Embedded development (The Debian Way)

. Overview

• What is Emdebian?
• Short history
• Technical challenges
• Composite method
• Using the tools
• Future help
• How I can help

What is Emdebian?

• Officall sub-project of Debian
• Bringing Debian to embedded systems
• Takes full advantage of the existing multiarchitecture support
• Provide free, commuinity supported, embedded development tools
• .

History

• Project started in 2000 by Frank Smith
• Produced Embedsys and toolchain
• In 2001 update to CML2 and new project lead
• In 2003 Embedsys update to Kconfig
• In 2005 Stag, then stage and Slind
• .

Why use Debina?

• The main non-commerical GNU/LInux distribution

Techniical challenges

• Debian is mosty about navite development
• The size of the binaries is no an siisue on desktop systems
• Lots of decumentstation included - not needed on the embedded systems
• Dalings with optimissations
• Software management on the target vs host
• Using other C librarries then glibc
• Rmove perl from "Essential".

Composite Method(1)

  Re-use the package management system, including reprepro, apt, dpkg, debhelper etc.
  Add support for flexibile cross-compliation- (dpkg-cross, apt-cross, & emdebian-tools)
  Reduce package size and dependencies, remove all doucmentation.
  Split out translation files as packages
  Keep emdebian change in SVN as patches, support debian/xcontrol.
  Binary package should be installable on the development host then target
  

Composite Method(2)

  Packages:dpkg-cross, apt, cross, emdebian-toosls
  Prebuild binary toolchains for cross-building on i386, amd64, and powerpc
  Patches to remove manpages ....
  

Composite Method(3)

  All parameters are controlled in normal debian/control files.
  Adatpted build scripts (emdebian-tools) apply patches in correct sequence, cross-build the patched package and manage the emdebian patch files and...
  

Translation file size

  /usr/share/locale:219mb, /usr/share/doc:250mb
  

Normal package management 通常のdebian package の話 Adaped scheme . Handling package methods

 CDBS:Patch debian/rules to use --- これがよさげ。
 debhelper:Patch debian/rules to remove or wrap all relevant dh-* rules. Check debian/rules and remove manual dpkg or install commands that are not removed by the patch. Remove udeb and doc package from debian/control.
 dpkg and other method: No automated packages, generate patches from manual changes.
  

Role of emdebian-tools

    Patch debian/contorol to remove udeb and doc packages
    Patch debian/rules to ....
  

Using emdebian-tools

  1. Run 'emsetup --vervose --simlate' to see waht need to be modified
  2. re-run 'emsetup -v' to sinstall a cross0building toolchain and update the tools from the Emdebian toolchain repsitory
  3 Get the Debian package with 'emsource' to prepare inital pactches and create SVN records
  ....
  

Emdebian work-flow .... Emdebian patch files

    emdebian-control.patch ( and emdebian-control.in.ptch if present) - patches to remove udeb and docs package and strip out unwanted dependcies
    endebian-changelog.patch - appends the endebian verison
    emdebian-rule.patch - removes debhelper or hand-wriiten rules that install documentstion ofr other unswanted files
    ....
Common problems
    
      ./configure - if used, add supoort for cross compilling to debian/urles using -build and --host with valules form debg-architecture. (NOT CDBS)
      -nodocs & -nocheck - Please add support via DEB_BUILD_OPTIONS or ./configure.
      idmpotnt options - avoid trying to patch or clean a file that can not be generated in a cross-build
      internal objects - if the package builds a program to do an internal task during the build, provide a way to do the task without executing compiled code for to avoid the task completely.
    
Emdebian package changes
    
    The package is essentially the same(only smaller)
    Emdebian patches remove un-wanted documentation  and add local handling
    ....
    
Current and future development
    
    Automate dmdebian toolchain updates
    Package GPE for ARM
    Cross-compiling with emdebiuild
    Aid creation of cache files used wieth './configure --cache-file'
    empdebuild to cross-build installed a chroot ...
    ....
    
Cross-building in a chroot
    
      Customized package set.
    empdebuild use pbuilder & debootstrap
    debian/xcontrol file (& patch file) to specify Build-Cross-Depends: -dev-packages require by e.g. arm-linux-gnu-gcc & install by apt-cross
    Separates cross deb from native -dev.
    Include support for a testing chroot during gcc translation  in unstable
    
Getting help or helping out
    
  Subscribe to the mailing list
  IRC channel
  ....
    

_ [Debconf7] ひるめしどき

学食で、長だの列ができて部屋を跨いでしまった。わたしは、Green サラダとパスタ。他の方は、Fish and Chips でした。食事をしていたら、名古屋にいたという男性がご一緒したいということで、しばし歓談。

_ [Debconf7] Debian Live

Debianのサブプロジェクトとして活動している。ツールをUbuntuのcasperからforkして作成。国際化も国コードやキーボードを入れるようにするみたい。

_ [Debconf7] The New ARM ABI(EABI) --- Debian armel Port

Debian Armを、効率良く動かすために根本から直す。

_ [Debconf7] Daytrip 申し込み

6月20日(水曜日)に、グラスゴーの小さな島に daytrip するとのこと。 20GBP. 今日の夕食後に申し込みに来て欲しいというメールがきていた。

_ [Debian] ライブラリをパッケージ化するときの安全弁

(http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html)を理解せずに、dh_make で library を作ろうとすると、

Source: libhoge
Priority: extra
Maintainer: Yukiharu YABUKI 
Build-Depends: debhelper (>= 5), autotools-dev
Standards-Version: 3.7.2
Section: libs
 
Package: libhoge-dev
Section: libdevel
Architecture: any
Depends: libhogeBROKEN (= ${Source-Version})
Description: <insert up to 60 chars description>
 <insert long description, indented with spaces>
 
Package: libhogeBROKEN
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: <insert up to 60 chars description>
 <insert long description, indented with spaces>

のように、注意しろやってメッセージが出てる。

_ [Debconf7] Maintaining Packages With Git

Git を使ってパッケージをメンテナンスするという話題について。

_ [Debian] debian-community.org

(http://debian-community.org/) Debian JPの planet もここに参加するのがよさげか。

_ [Debconf7] Wacky idea

Wacky idea = おれ、こんな凄いこと考えちゃったぜ。ってのをディスカッションしてまともなものにする。

いまは、ian jackson による。upstream, ディストリビューション, 派生ディストリビューション で無駄なことしてないか? これらを包括するような VCS(Version Control System)って作れないか? って話。まずは、標準 i/f を定義することができるのか。って所が問題だねってことでオチがつきそう。

idea : define a common interface in a declarative language (or a point to an external system) that models 90% of existing systems, allowing for their replacement.

Translation debs

(http://wiki.debian.org/i18n/TranslationDebs?action=show&redirect=TranslationDebs) If translations are small, packaging overhead is relatively large. so consolidation is desired. The extreme is Ubuntu's approach, using a 100MB package.