On Thu, Aug 04, 2005 at 03:23:13AM -0700, Steve Langasek wrote:
> I've unfrozen pango1.0, at any rate; pango and jigdo can both enter
> testing once they've aged and all builds are available. I don't think
> that the gcc-defaults change is urgent enough that it warrants shorting
> the testing peri
On Thu, Aug 04, 2005 at 05:43:11AM -0400, Nathanael Nerode wrote:
> So there's something weird keeping gcc-defaults out of etch.
> gcc-defaults is waiting for gcc-3.4.
> britney thinks that updating gcc-3.4 in testing will break jigdo
> on arm. Presumably this is because jigdo in testing depends
So there's something weird keeping gcc-defaults out of etch.
gcc-defaults is waiting for gcc-3.4.
britney thinks that updating gcc-3.4 in testing will break jigdo
on arm. Presumably this is because jigdo in testing depends on
"libstdc++6-0" on arm, which isn't going to exist any more.
jigdo in u
3 matches
Mail list logo
