Re: The non-existent unofficial sarge for amd64
Anders Boström <anders@netinsight.se> writes:
>>>>>> "KR" == Kurt Roeckx <Q@ping.be> writes:
>
> KR> On Fri, Jan 07, 2005 at 04:35:28PM +0100, Anders Boström wrote:
> >>
> >> As I wrote in my original question is /debian-pure64 not updated. Last
> >> update was 20041215.
Small update. Q did build a few new packages but he didn't override
the distribution to testing in the changes file and the packages ended
up in sid. The sid->sarge propagation (see below) should take care of
that at some point so I keep them as is as testcases.
> KR> Goswin seems to be rather sick at the moment. You will have to
> KR> wait until he's back.
>
> KR> I can't do anything about this until he's back.
>
> Another week has gone, and still no update of /debian-pure64
> testing. Is the "unofficial sarge for amd64" dead?
>
> Is the whole amd64 port of debian dependent of one person (Goswin)???
>
> / Anders
As for the sarge port, yes, everything is waiting for me and I'm sorry
for the delay.
But the debian amd64 port is far more than the sarge port and both
pure64 sid and the gcc-3.4/4.0 build repository are fully staffed and
working.
If you are specifically interested in getting sarge more in sync with
the official sarge you can join the team and familarize yourself with
the existing software and help script the missing bits and pieces.
What I'm currently stuck on is getting packages build for sid to
progress into sarge when they do in the official sarge but only if
that doesn't break our sarge. If you want to help out there you should
be familiar with Packages/Sources file syntax and graph theory.
MfG
Goswin
Reply to: