Differences between revisions 146 and 147
Revision 146 as of 2008-02-17 02:29:24
Size: 4758
Editor: ?smarenka
Comment:
Revision 147 as of 2008-02-28 00:18:38
Size: 5037
Comment:
Deletions are marked like this. Additions are marked like this.
Line 26: Line 26:
 * Right now there is no security or proposed-updates type support for etch-m68k, but it is in the works.
 * The good news is it works fine.
 * A wanna-build for security or proposed-updates type support for etch-m68k has been created, but the autobuilders are currently focused on catching up with unstable distribution. Once m68k is caught up with unstable, cronos and diablos at nemesisnetworks.com are scheduled to begin building both.
 * The good news is that everything works, and we have an upgrade path for the future.
Line 35: Line 35:
 * Need to figure out how we're going to handle a testing distribution.  * Testing distribution being handled by Michael Casadevall, using a copy of the offical testing scripts.

This page tracks current issues with the [http://www.us.debian.org/ports/m68k/ m68k] port. User support and buildd admins are at debian-68k@lists.debian.org.

Other Places

Here

  • [#etch etch status]
  • [#testing testing status]
  • [#usertags usertags]
  • [#rcusertags RC usertags]
  • [#bugs bugs that need work]
  • [#binnmu binNMU instructions]

?Anchor(etch)

Etch-m68k Status

  • m68k didn't release with debian stable, but rather has it's own semi-supported, semi-released distribution called etch-m68k.
  • A wanna-build for security or proposed-updates type support for etch-m68k has been created, but the autobuilders are currently focused on catching up with unstable distribution. Once m68k is caught up with unstable, cronos and diablos at nemesisnetworks.com are scheduled to begin building both.
  • The good news is that everything works, and we have an upgrade path for the future.

?Anchor(testing)

Testing Status

  • m68k isn't even in lenny at the moment since the RMs felt the toolchain needs work.
  • glibc needs TLS support.
  • Submit gcc-snapshot test results.
  • Testing distribution being handled by Michael Casadevall, using a copy of the offical testing scripts.

Testing Links

?Anchor(usertags)

m68k usertags

{{{To: control@bugs.debian.org Subject: m68k usertags

user m68k-build@nocrew.org usertag bugnum + m68k thanks }}}

?Anchor(rcusertags)

m68k rc usertags

?Anchor(bugs)

Bugs

time-stamp skew

  • A missing automake build-dep may instead be time-stamp skew.
  • Search for skew in /usr/share/doc/autotools-dev/README.Debian.gz

?Anchor(binnmu)

binNMU notes

  • example to register dpkg_1.13.11 for a dpkg_1.13.11+b1 binNMU:

wanna-build -b m68k/build-db -d unstable -m "Rebuild with g++-4.0 for C++ +transition." --binNMU=1 dpkg_1.13.11

  • --binNMU=2 for second binNMU.
  • example to deregister any pending binNMU and return to Installed state:

wanna-build -b m68k/build-db -d unstable --binNMU=0 dpkg_1.13.11

Build Priority Notes

  • example usage to set one-time higher build-priority

wanna-build -b i386/build-db -d unstable --build-priority=1 xorg-x11_6.8.2.dfsg.1-7

  • example usage to set one-time lower build-priority

wanna-build -b i386/build-db -d unstable --build-priority=-1 xorg-x11_6.8.2.dfsg.1-7

  • For permanent build priorities, use --perm-build-priority instead of --build-priority

Not-For-Us Notes

  • to remove something from the not-for-us list, use --forget.
  • to move it from n-f-u to nb, use --forget, -o --take, --give-back.


CategoryPermalink