Differences between revisions 18 and 19
Revision 18 as of 2005-11-01 13:13:59
Size: 2277
Editor: ?smarenka
Revision 19 as of 2005-11-01 15:54:03
Size: 2366
Editor: ?smarenka
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
 * Wouter is hot on the trail <http://www.grep.be/blog/en/computer/debian/m68k/327780>.


  • mac support, especially adb (can't d-i without it)
  • atari is missing support for framebuffer, keyboard, mouse, and serial, plus user space is broken (init dies when starting).


  • Atari and Mac SCC serial drivers missing
  • Atari ST-RAM swap code broken


  • bug triage: which m68k bugs have been fixed and should be closed, which still fail with the latest sid compiler and/or gcc-snapshot http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-4.0

  • bug fixing
  • debian bug #323686/pr 21123 cp_expr_size ICE (4.0.2-2): many packages including: kxmleditor_1.1.4-2, aleph_0.9.0-2.1, superkaramba_0.36-2
  • more to list [20051011] at least: wordtrans, texmacs, qdbm, kst, kile, kbear, ecos, celestia
  • debian bug #333536, gcc-4.0 (4.0.2-2) ICE in instantiate_virtual_regs_lossage: plptools_0.14-1, rsplib_1.0.0-1, ntop_3:3.2-1, cl-sql_3.3.3-1
  • debian bug #323016, gcc-4.0 (4.0.2-2) unable to find a register to spill in class 'ADDR_REGS': ruby1.8_1.8.3-2, tin 1.7.10+20050727, sharutils? -- workaround -01, fixed in 4.1?


xargs (dh_fixperms)

  • Looks something like

{{{> > dh_fixperms > > chown: cannot access > > `dedebian/libcommoncpp2-dev/usr/include/cc++2/cc++/common.h': No such file > > or directory chown: cannot access `TERM=unknown': No such file or directory > > dh_fixperms: command returned error code}}}

  • The offending command in dh_fixperms is find debian/caudium -print0 2>/dev/null | xargs -0r chown --no-dereference 0:0, with xargs being the culprit

  • Packages known to fail: libcommoncpp2_1.3.19-1, digikamimageplugins_0.7.4-4, drscheme_1:209-8, caudium_2:1.4.7-5, libclass-methodmaker-perl_2.07-2, mozilla_2:1.7.11-1, openssl097_0.9.7g-4, ncurses_5.5-1
  • Workaround: build under kernel 2.4 or better.

Buildds Seriously Behind

Other Stuff