On Sun, Oct 18, 2009 at 8:50 PM, Philipp Kern <pk...@debian.org> wrote:
> > I've been holding off on uploading the final, ported source package until > > the buildds are ready to run it. Until I upload, there are binaries in > > debian without corresponding source, which I imagine might offend some of > > the less practical members of the debian community. > > dak shouldn't allow this, to be honest. True, but it was a convenient way to get bootstrap packages into the archive where the buildd could find them in order to rebuild the package the package when I do a source upload. > but the solution would be to upload new ones and then binNMU them on the > official buildds. Yes. > But I guess it's not only bootstrapping that needs so much memory? > Correct. Every time the compiler compiles itself it will need 1GB of memory. I don't want to have to manually rebuild the package for each architecture on every release, so I am just going to support those architectures where the buildd can look after it now that I've made an upload for the target. TBH the problem should already autosolve itself with BD-Uninstallable > as mlton won't be available on the target architecture and that will only > clear up when it's uploaded for the first time. > > So the solution would be to just drop it from Packages-arch-specific, > I think. > Ok, great! Could you please remove it then? Danke schoen!
