Ticket #436 (closed enhancement: fixed)

Opened 12 years ago

Last modified 12 years ago

repository and build process for patched schroot 1.3

Reported by: geofft Owned by: geofft
Priority: normal Milestone: Karmic Deploy (Canceled)
Component: login chroot Keywords:
Cc: Fixed in version:
Upstream bug:

Description

The debathenificator doesn't currently support starting with a completely separate source package (because that's not its intent; the intent is to modify the source package in each supported distro), so I can't use it for our schroot 1.3 backport. I currently have a clone of upstream's git repo with some additional patches in debuild:/home/debuild/geofft/schroot/schroot (the patches are also in /mit/geofft/debathena/schroot), and I'm building and uploading it to jaunty-development by running sbuild and reprepro myself. This is very not sustainable and needs to be fixed before the package escapes to anything other than -development.

Also, I've specifically backported schroot 1.3 to Jaunty, so it may not fit well with our multi-distribution model -- there's no point of this anyway. But somehow we need to be keeping our patches for schroot in Athena SVN and make our build scripts/infrastructure capable of building it.

Change History

comment:1 Changed 12 years ago by broder

  • Status changed from new to closed
  • Resolution set to fixed

I've imported schroot wholesale into /trunk/debathena/third/schroot, and committed geofft's patches on top of it. This should be a sufficient solution for the short term.

In the medium-to-long term, geofft's one patch that actually changes functionality (r24170) should be incorporated into upstream. Once they've uploaded a version with that patch to Debian, it'll sync into Lucid. The rest of the patches are purely for backporting. At that point we can get Ubuntu to backport schroot, and/or we can declare our backport equivalent to an eventual backport from Ubuntu (in which case we wouldn't have to debathenify it)

Note: See TracTickets for help on using tickets.