On Mon, Mar 21, 2011 at 09:27:14AM +0100, Yajo wrote: > > I brought this up a week ago. The blocker right now is getting gcc-4.5 > > into sid first. Once that's in place, hopefully Ove will be around to > > review and sponsor work, otherwise the MIA/orphaning process will need > > to be started. > > We have already gcc-4.5 in sid and testing.
Yes, and I'm working on getting mingw-w64 into unstable; see the debian-gcc archives for details of the problems I'm facing just now (although there's a quick workaround if I can't get things working properly). > > I vote for this bug: > > * 1.2.1 is marked as stable > > * 1.3.4 is nice to have in "experimental" > > Instead of that, wouldn't be better this?: > - wine: stable branch, currently 1.2.2 > - wine-unstable: development branch, currently 1.3.16 > > This way, wine-unstable could be migrated to testing, for those who > want to try it. Ove already has wine/wine-unstable packages, so that's already what is planned. Note that 1.3.16 uses wine-gecko 1.2.0 which uses very different packaging compared to 1.0.0 and 1.1.0, so wine 1.2.2 is the current focus... I'm not sure though that allowing wine-unstable into testing would be a good idea, since testing is the next stable and I'm not sure we'd want to ship wine-unstable in stable. Regards, Stephen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
