Once again Debian has no updates. Is there any reason for this to happen? Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.winehq.org/pipermail/wine-users/attachments/20080430/c39ba1e4/attachment.htm
On Tuesday 29 April 2008 11:04:25 pm Jim Hall wrote:> Once again Debian has no updates. Is there any reason for this to happen?I could be wrong, but my understanding is that Ove Kaaven, the Debian maintainer of wine, is a volunteer with a life and a job to attend to, as well as the Debian flightgear/simgear packages to maintain. Just Debianwise, he has a lot to juggle (since both wine and simgear/flightgear are fairly active), but he is generally fairly timely about keeping it all up to date. -- Paul Johnson baloo at ursine.ca Explaination of .pgp part: http://linuxmafia.com/faq/Mail/rant-gpg.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. Url : http://www.winehq.org/pipermail/wine-users/attachments/20080430/38867cb3/attachment.pgp
> On Wed, Apr 30, 2008 at 8:08 PM, Paul Johnson <baloo at ursine.ca> wrote: >> On Tuesday 29 April 2008 11:04:25 pm Jim Hall wrote: >>> Once again Debian has no updates. Is there any reason for this to >> happen? >> I could be wrong, but my understanding is that Ove Kaaven, the Debian >> maintainer of wine, is a volunteer with a life and a job to attend to, as >> well as the Debian flightgear/simgear packages to maintain. Just >> Debianwise, >> he has a lot to juggle (since both wine and simgear/flightgear are fairly >> active), but he is generally fairly timely about keeping it all up to >> date. > With all due respect, I understand "volunter", "life", and "job". I was not > trying to be critical, only seeking an explanation. I'm sure you didn't mean > that two releases behind was "timely". Having said that, is there something > I (or anyone) can do to help?I understand the being busy part too, and so don't blame him or really can complain much, I just wouldn't say making updates every 3 or 4 versions as timely either (since that is normally how often the debian Wine packages are updated). Although, right now, 0.9.60 is in the unstable branch, and 0.9.59 was the version before that, so lately things are good.
Ove Kaaven wrote:> > The packaging structure of Scott's packages and mine are quite > different, by the way; they follow the Ubuntu-style packaging, not the > current Debian style. And I personally feel that his packaging might > work fine for Ubuntu, but less so for Debian; Debian has always had its > own way to do things (and those ways aren't always about making popular > decisions or following the wishes of whoever wrote their software)...Hmmm. That would have been good to have known when I was selecting which distribution to install. However, questions seeking this sort of information seem to get cut off pretty quickly.
> From: "Jim Hall" <volunteer.jim at gmail.com> > On Thu, May 1, 2008 at 8:21 AM, Keith Brown <spamtrap at hellmark.org> wrote: >> On Wed, Apr 30, 2008 at 8:08 PM, Paul Johnson <baloo at ursine.ca> wrote: >> I understand the being busy part too, and so don't blame him or really can >> complain much, I just wouldn't say making updates every 3 or 4 versions as >> timely either (since that is normally how often the debian Wine packages are >> updated). Although, right now, 0.9.60 is in the unstable branch, and 0.9.59 >> was the version before that, so lately things are good. > Thanks for the more detailed info, folks. But apples & oranges, I think. I > get my deb's from budgetdedicated (for etch). Are you suggesting that I use > the sid one? if so, will it work with etch? If it will that would solve a > whole lot of problems!From what I've seen, of the official debian packages, etch is absolutely horrible, and is way out of date (0.9.25), unless you use the backport. The backports tend to be the same release as Lenny, which right now is 0.9.59. Under normal conditions for debian, Testing can be as much as 8 releases out of date. I use sid, and so I go with the sid packages, and really have no problem (for a desktop, really not much of a reason to not use sid, since it is honestly far from unstable). As far as the wine packages in the sid pool go, like I said, they're normally a few versions out of date, but with the occasional spurt where no releases are missed. Also, it usually is a bit before the packages hit the pool (I remember .58 hit the package pool 8 days after the wine dev team released .59). Looking at my package archive for this machine, it went as follows .30, .31, 32, 33, .34, .39, .44, .47, .52, .53, .54, .56, .58, .59, and .60. 30 versions of wine, with a total of 15 packages in between.
Ove Kaaven wrote:> > Hmm, how would this have affected your decision, then? It's not like one > of these is really fundamentally better than the other, but admittedly, > they do represent different philosophies.If the most up-to-date Wine binary releases tend to lean toward one distribution or the other. That's what I was getting at. For instance, it looks (in my naivet?) like Scott's installation instructions have some issues that don't quite work the way they should in Debian. He and I have communicated about this. Had I been aware of this complication in advance I might have picked differently.