Bug#585409: wine 1.2/1.3 on Debian: what's the blocker?
Hi Antoine, On Sat, 19 Nov 2011 03:33:07 -0500, Antoine Beaupré anar...@debian.org wrote: It seems we are still without 1.2 in Debian. While I understand this is a difficult project, after reading through the history of this bug here, it seems to me that the package *may* ready to be uploaded... So what's the blocker here? Stephen - do you need a sponsor for this package? The blocker's effectively Ove - after I did what was necessary to get wine-gecko into Debian (with a sourceful rebuild, not just repackaging upstream's binaries) I was hoping Wine uploads would resume and we'd catch up with upstream within a reasonable timeframe. Unfortunately only four releases followed, packaging three upstream versions (1.1.33 to 1.1.35 inclusive), and since August there hasn't been any activity, including in the git repository. Ove's reason for uploading every single version of Wine is so that all versions of Wine end up available in the Debian snapshots archive, which can come in handy given that some Windows programs work better with older versions of Wine. It also means changes to the contents of Wine releases and packaging requirements can be made progressively. Unfortunately we're so far behind now that even with one release a day it would take a month and a half to catch up (10 remaining 1.1.x versions, 7 1.2 release candidates, 4 1.2.x versions and 34 1.3.x versions), not counting updating wine-gecko, and the effort involved seems enormous to me - at least I don't have the time and energy for that. What I can do though is update my Wine 1.2.x packages (see http://www.sk2.org/wine/wine_1.2.3-0.1.dsc for the current source) to use wine-gecko-unstable as it ended up in Debian - although I'd rather name the latter wine-gecko-1.0.0 (as used in my packages) since having wine (-stable) depend on wine-gecko-unstable is a bit unfortunate. It would be nice if the existing packaging team on Alioth could be extended, but I don't know whether that's possible without Ove's approval (or an Alioth administrator's intervention). I've had offers of sponsorship in the past, but if you're up for it (or Hilko) I'd appreciate it. (But don't just sponsor the existing packages mentioned above!) The next step, assuming we skip all the intervening unstable versions, would be to update wine-gecko (which is going to be a whole new bundle of fun given the changes since 1.0.0) and package Wine 1.3.33. I also have concerns about the fork between this package and the Ubuntu ones. Ending the fork could quickly bring Wine 1.2 and 1.3 in Debian. I bring up those concerns in a separate bug report (#649238). I should really reply in detail to your separate bug report, but apart from the sound drivers I don't have any objection to merging all the binary packages back together. As far as taking Ubuntu's packaging is concerned, I haven't looked at it in detail; I'm not sure though that the wine-gecko packaging would be acceptable for Debian since it doesn't build from the provided source. Regards, Stephen signature.asc Description: PGP signature
Bug#585409: [pkg-wine-party] Bug#585409: wine 1.2/1.3 on Debian: what's the blocker?
On Sun, Nov 20, 2011 at 5:59 PM, Stephen Kitt wrote: The blocker's effectively Ove - after I did what was necessary to get wine-gecko into Debian (with a sourceful rebuild, not just repackaging upstream's binaries) I was hoping Wine uploads would resume and we'd catch up with upstream within a reasonable timeframe. Unfortunately only four releases followed, packaging three upstream versions (1.1.33 to 1.1.35 inclusive), and since August there hasn't been any activity, including in the git repository. Ove's reason for uploading every single version of Wine is so that all versions of Wine end up available in the Debian snapshots archive, which can come in handy given that some Windows programs work better with older versions of Wine. It also means changes to the contents of Wine releases and packaging requirements can be made progressively. Unfortunately we're so far behind now that even with one release a day it would take a month and a half to catch up (10 remaining 1.1.x versions, 7 1.2 release candidates, 4 1.2.x versions and 34 1.3.x versions), not counting updating wine-gecko, and the effort involved seems enormous to me - at least I don't have the time and energy for that. Couldn't this be greatly simplified if only the 1.2.x (stable) versions were uploaded? I assume the plan is to release wheezy with one of the stable wine releases (either 1.2.x or 1.4.x if its ready in time); thus nothing really needs to be done with wine-unstable (especially since that is never going into a stable Debian release); let's just work on wine. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585409: [pkg-wine-party] Bug#585409: wine 1.2/1.3 on Debian: what's the blocker?
On Sun, Nov 20, 2011 at 06:26:19PM -0500, Michael Gilbert wrote: On Sun, Nov 20, 2011 at 5:59 PM, Stephen Kitt wrote: Unfortunately we're so far behind now that even with one release a day it would take a month and a half to catch up (10 remaining 1.1.x versions, 7 1.2 release candidates, 4 1.2.x versions and 34 1.3.x versions), not counting updating wine-gecko, and the effort involved seems enormous to me - at least I don't have the time and energy for that. Couldn't this be greatly simplified if only the 1.2.x (stable) versions were uploaded? I assume the plan is to release wheezy with one of the stable wine releases (either 1.2.x or 1.4.x if its ready in time); thus nothing really needs to be done with wine-unstable (especially since that is never going into a stable Debian release); let's just work on wine. Yes, that makes sense to me. 1.2.x isn't much use for gaming on ATI cards using the free drivers currently, but 1.4 should be out before Wheezy. Regards, Stephen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585409: [pkg-wine-party] Bug#585409: Bug#585409: wine 1.2/1.3 on Debian: what's the blocker?
* Michael Gilbert: Couldn't this be greatly simplified if only the 1.2.x (stable) versions were uploaded? I assume the plan is to release wheezy with one of the stable wine releases (either 1.2.x or 1.4.x if its ready in time); thus nothing really needs to be done with wine-unstable (especially since that is never going into a stable Debian release); let's just work on wine. If someone thinks that it's worthwhile to have pacakges of the unstable branch, one could upload those to experimental following upstream releases while still calleng them wine. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585409: [pkg-wine-party] Bug#585409: Bug#585409: Bug#585409: wine 1.2/1.3 on Debian: what's the blocker?
On Sun, Nov 20, 2011 at 6:41 PM, Hilko Bengen wrote: If someone thinks that it's worthwhile to have pacakges of the unstable branch, one could upload those to experimental following upstream releases while still calleng them wine. That's certainly one way to do it, and that's how it was done in the past, but the current approach seems to be separate wine-unstable package: http://packages.qa.debian.org/w/wine-unstable.html Not sure why one way or the other would be necessarily preferable. I suppose this way makes it possible to upload stable wine's to experimental first? Although I'm not sure why that would be necessary as those releases should be stable enough for unstable. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585409: [pkg-wine-party] Bug#585409: wine 1.2/1.3 on Debian: what's the blocker?
On Sat, 19 Nov 2011 14:52:55 +0100, Hilko Bengen ben...@debian.org wrote: * Antoine Beaupré: It seems we are still without 1.2 in Debian. While I understand this is a difficult project, after reading through the history of this bug here, it seems to me that the package *may* ready to be uploaded... A few weeks ago, I took Ove's 1.1.35-1 package that I found at git://git.debian.org/git/pkg-wine/wine.git and tried to build 1.2.3 with it. Very few fixes were needed and there is only a small number of issues that probably can be fixed in the packaging scripts. Interesting. Also note that the Ubuntu packages work fine, and have frequent releases. In my opinion, it would be best for users to get a package called wine (not wine-$version) into unstable as soon as possible. I don't care much. As long as there's a wine virtual package, people will find it. Ubuntu ships with wine-1.2 and wine-1.3. I could very well see the latter in experimental for example. I can't imagine that users are interested in packages of upstream's snapshot releases from 2 years ago. Indeed. Make that 3 years for 1.0. So what's the blocker here? Stephen - do you need a sponsor for this package? Since there are a few people who have been able to build their own packages, perhaps it is time to turn packaging of Wine in Debian into a real team effort. Honestly, I think we should just team up with the Ubuntu folks. They have done all the work for us already... http://packages.ubuntu.com/search?keywords=wine A. -- We should act only in such away that if everyone else acted as we do, we would accept the results. - Kant pgphoGuQaeYkd.pgp Description: PGP signature
Bug#585409: wine 1.2/1.3 on Debian: what's the blocker?
On Sun, 20 Nov 2011 23:59:23 +0100, Stephen Kitt st...@sk2.org wrote: I also have concerns about the fork between this package and the Ubuntu ones. Ending the fork could quickly bring Wine 1.2 and 1.3 in Debian. I bring up those concerns in a separate bug report (#649238). I should really reply in detail to your separate bug report, but apart from the sound drivers I don't have any objection to merging all the binary packages back together. As far as taking Ubuntu's packaging is concerned, I haven't looked at it in detail; I'm not sure though that the wine-gecko packaging would be acceptable for Debian since it doesn't build from the provided source. I do not want to step over anybody's toes here. If Ove still wants to maintain this package, he should, but it looks like he's overwhelmed and doesn't have time to do it. I do not have much time either, but I can sponsor uploads, that seems easy enough. Plus, I think that the stuff from Ubuntu is great - we should look into that first. They have 1.2 and 1.3 all rolled up and ready to go. Can you review their work? I can do some communications with them people if needs be. A. -- Man really attains the state of complete humanity when he produces, without being forced by physical need to sell himself as a commodity. - Ernesto Che Guevara pgpRNavXH0NNr.pgp Description: PGP signature
Bug#585409: [pkg-wine-party] Bug#585409: wine 1.2/1.3 on Debian: what's the blocker?
2011/11/20 Antoine Beaupré I should really reply in detail to your separate bug report, but apart from the sound drivers I don't have any objection to merging all the binary packages back together. As far as taking Ubuntu's packaging is concerned, I haven't looked at it in detail; I'm not sure though that the wine-gecko packaging would be acceptable for Debian since it doesn't build from the provided source. I do not want to step over anybody's toes here. If Ove still wants to maintain this package, he should, but it looks like he's overwhelmed and doesn't have time to do it. I do not have much time either, but I can sponsor uploads, that seems easy enough. Technically you're not supposed to upload major changes to packages in which you're not a team member (minor changes like NMUs are ok). So, I think the first step is for Ove to approve you as a team member, and that may require some work on your part (maybe preparing 1.1.36 would be good?). Plus, I think that the stuff from Ubuntu is great - we should look into that first. They have 1.2 and 1.3 all rolled up and ready to go. Can you review their work? I can do some communications with them people if needs be. I think the debian packaging is already of sufficient quality. It just needs to go through Ove's every release needs package process, and that's just tedious, but someone will need to do it. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585409: wine 1.2/1.3 on Debian: what's the blocker?
Hi, It seems we are still without 1.2 in Debian. While I understand this is a difficult project, after reading through the history of this bug here, it seems to me that the package *may* ready to be uploaded... So what's the blocker here? Stephen - do you need a sponsor for this package? I also have concerns about the fork between this package and the Ubuntu ones. Ending the fork could quickly bring Wine 1.2 and 1.3 in Debian. I bring up those concerns in a separate bug report (#649238). A. -- It is a miracle that curiosity survives formal education - Albert Einstein pgpCMAmAxnP6y.pgp Description: PGP signature
Bug#585409: [pkg-wine-party] Bug#585409: wine 1.2/1.3 on Debian: what's the blocker?
* Antoine Beaupré: It seems we are still without 1.2 in Debian. While I understand this is a difficult project, after reading through the history of this bug here, it seems to me that the package *may* ready to be uploaded... A few weeks ago, I took Ove's 1.1.35-1 package that I found at git://git.debian.org/git/pkg-wine/wine.git and tried to build 1.2.3 with it. Very few fixes were needed and there is only a small number of issues that probably can be fixed in the packaging scripts. In my opinion, it would be best for users to get a package called wine (not wine-$version) into unstable as soon as possible. I can't imagine that users are interested in packages of upstream's snapshot releases from 2 years ago. So what's the blocker here? Stephen - do you need a sponsor for this package? Since there are a few people who have been able to build their own packages, perhaps it is time to turn packaging of Wine in Debian into a real team effort. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
