> it's a great thing to have a debian package for go. And since you are > keeping up with the weekly releases I don't need to build from upstream > myself anymore. One thing less I need to care about at work; thanks for > that and keep up the good work. Good decision to include the source and > documentation too, since I need both for reference and the one at their > webpage is only up to date with their last stable release. > > It would be nice to see the stable releases (those tagged "release" in > upstream) in testing too. Maybe consider "resolving" this bug for the > next stable upstream release and reopen it for the weely release after that. > The stable releases don't seem to happen that often (the last is about 2 > month old) and the API changes aren't that bad, so having the latest and > greatest golang release in the next stable would be a good thing imho.
Seems like good idea - could you ping me when there is a release tag? The only reason why to remove golang from testing is to not have it in stable, so what I can do is to let it into testing, but remove it after freeze. > Besides... ...gccgo just migrated to testing and its a pain to use, so > it would be nice if people using wheezy had the choice to use golang > alternatively (if they don't want to use sid, or just aren't aware of > the package in sid). No matter how bad the situation turns out to be, it > will be still an inprovement for those using wheezy. > PS.: If you need a helping hand with anything regarding these packages, > no matter what the task is, just ask. There seems to be a bug with dynamic linker with libc6 from experimental :). It would be great if you can solve that. And you can always send pull requests for git. O. -- Ondřej Surý <ond...@sury.org> -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
