Custom Query (1145 matches)

Reported by geofft, 15 years ago.

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.

Reported by jdreed, 14 years ago.

We should repoint zulu's approx at mirrors.mit.edu.

Additionally, now that mirrors.mit.edu exists, it has been asserted that zulu's network link to mirrors is actually faster than zulu's approx cache (a vmware virtual disk), so maybe we should consider punting approx entirely.

Reported by achernya, 11 years ago.

Originally this ticket proposed death, claiming:

This is like just all over again, and we decided to punt that. Then again, lam and rs actually are pulled in by debathena-clients, so maybe they gets a gentler death.