On Tuesday 07 October 2008 14:27:40 Iain Lane wrote:
> It depends how conservative we want to be I guess. All of the fixes
> between Hardy and Intrepid are bug/buildfixes so there should be no new
> regressions introduced, but this is the only fix we really want.
> Subscribing motu-sru for an opinion.
well, I guess the fix for Debian #491909 would also be good to have.
I guess it makes sense to also have the watcher script that prints stuff
during build, as I don't want to pester our buildd admins again if the build
times out on sparc.
Oh, can you eventually open a separate bug for the SRU, so that it's not so
clattered with a lengthy history of comments? (and wrong assumptions from
myself *cough* ;))
>
> As for darcs, a simple grepping of the source shows that the version in
> Hardy calls getSymbolicLinkStatus so I guess it's still affected, if not
> as severely as 2.x. It's worth a rebuild in -updates IMHO.
Hi,
On Tuesday 07 October 2008 14:27:40 Iain Lane wrote:
> It depends how conservative we want to be I guess. All of the fixes
> between Hardy and Intrepid are bug/buildfixes so there should be no new
> regressions introduced, but this is the only fix we really want.
> Subscribing motu-sru for an opinion.
well, I guess the fix for Debian #491909 would also be good to have.
I guess it makes sense to also have the watcher script that prints stuff
during build, as I don't want to pester our buildd admins again if the build
times out on sparc.
Oh, can you eventually open a separate bug for the SRU, so that it's not so
clattered with a lengthy history of comments? (and wrong assumptions from
myself *cough* ;))
> Status so I guess it's still affected, if not
> As for darcs, a simple grepping of the source shows that the version in
> Hardy calls getSymbolicLink
> as severely as 2.x. It's worth a rebuild in -updates IMHO.
Ok, thanks!
Cheers,
Stefan.