Re: wine-unstable in Debian

On Fri, Apr 27, 2012 at 10:44:08AM +0200, Stefano Zacchiroli wrote: > Right. Although we should be clear on what should happen with the > patches in the BTS. Otherwise people wouldn't know how (and if) they can > help, and that uncertainty would be a shame. Is the issue with the > binNMUs a reason

Re: wine-unstable in Debian

On 27/04/12 09:38, Goswin von Brederlow wrote: > Steve Langasek filed patches > for all the packages Ubuntu needed as multiarch. Look for the patches in: > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=multiarch-de...@lists.alioth.debian.org;tag=multiarch It seems that the multiarch tag ha

Re: wine-unstable in Debian

On Fri, Apr 27, 2012 at 10:28:04AM +0200, Philipp Kern wrote: > > And yes, that is not yet ready so any people pitching in and getting a > > library package multiarchified will help. The patches are in the BTS, > > they just need to be applied. > > Except that we still have problems with essential

Re: wine-unstable in Debian

On Fri, Apr 27, 2012 at 12:41:58AM +0200, Goswin von Brederlow wrote: > The plan for wheezy is that ia32-libs goes away. At least that it will > be just a transitional package that depends on the :i386 packages. > > And yes, that is not yet ready so any people pitching in and getting a > library p

Re: wine-unstable in Debian

Stefano Zacchiroli writes: > On Fri, Apr 27, 2012 at 12:41:58AM +0200, Goswin von Brederlow wrote: >> The plan for wheezy is that ia32-libs goes away. At least that it will >> be just a transitional package that depends on the :i386 packages. >> >> And yes, that is not yet ready so any people pi

Re: wine-unstable in Debian

On Fri, Apr 27, 2012 at 12:41:58AM +0200, Goswin von Brederlow wrote: > The plan for wheezy is that ia32-libs goes away. At least that it will > be just a transitional package that depends on the :i386 packages. > > And yes, that is not yet ready so any people pitching in and getting a > library p

Re: wine-unstable in Debian

Michael Gilbert writes: > On Wed, Apr 25, 2012 at 5:27 AM, Goswin von Brederlow > wrote: >> Jonas Smedegaard writes: >> >>> On 12-04-18 at 07:17pm, Simon McVittie wrote: I hesitate to suggest this if there's a possibility that the main wine package can come up to date before we freez

Re: wine-unstable in Debian

On Wed, Apr 25, 2012 at 11:27:37AM +0200, Goswin von Brederlow wrote: > I only sporadically read this thread. But isn't one of the problems with > wine that different things run with different wine versions? Related, is this considered a regression in Wine? That is, if app X works with wine Y but

Re: wine-unstable in Debian

On Wed, Apr 25, 2012 at 5:27 AM, Goswin von Brederlow wrote: > Jonas Smedegaard writes: > >> On 12-04-18 at 07:17pm, Simon McVittie wrote: >>> I hesitate to suggest this if there's a possibility that the main wine >>> package can come up to date before we freeze, but one way to have Wine >>> 1.4

Re: wine-unstable in Debian

On Wed, Apr 25, 2012 at 11:27:37AM +0200, Goswin von Brederlow wrote: > As a side note: One problem with wine is that it needs 32bit libraries > on amd64 and the state of ia32-libs. Ia32-libs does have some bugs open > concerning wine, specifically it doesn't allow building wine from source > (agai

Re: wine-unstable in Debian

On Wed, Apr 25, 2012 at 11:27:37AM +0200, Goswin von Brederlow wrote: > Since we now have multiarch this isn't going to get fixed in ia32-libs […] Given that multiarch is not likely to be completely ready soon, it makes sense to still fix bugs in ia32-libs if they're easy to fix. (Like importing

Re: wine-unstable in Debian

Jonas Smedegaard writes: > On 12-04-18 at 07:17pm, Simon McVittie wrote: >> I hesitate to suggest this if there's a possibility that the main wine >> package can come up to date before we freeze, but one way to have Wine >> 1.4 (and/or 1.2) in the distribution without NMUs/hijacks would be a >

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

Le Sun, Apr 22, 2012 at 09:34:58AM +0200, Jakub Wilk a écrit : > > Why is DEP-1 even marked as accepted? It's been rejected after all... Hi Jakub, DEP-1 was integrated it in the developers reference, in its revision 3.4.1 released in January 2009. Stefano then marked the DEP accpeted on the DEP

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Sunday, April 22, 2012 04:50:32, Stefano Zacchiroli wrote: > On Sun, Apr 22, 2012 at 11:49:08AM +0900, Charles Plessy wrote: > > If we would converge on a good rule of thumb to replace the nth NMU in > > a row to a QA orphaning, then I believe that the updated NMU section > > in the Developers R

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Sun, Apr 22, 2012 at 11:49:08AM +0900, Charles Plessy wrote: > If we would converge on a good rule of thumb to replace the nth NMU in > a row to a QA orphaning, then I believe that the updated NMU section > in the Developers Reference would then stay unchanged for a long time. I do see value in

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

* Charles Plessy , 2012-04-22, 11:49: The point of NMUs is *helping* a maintainer which, for different reasons, is temporarily unable to fix specific issues in their packages. If the NMU-er keeps that principle in mind, everything else descends more or less naturally. Hi Stefano, much of you

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

Le Sat, Apr 21, 2012 at 05:00:57PM +0200, Stefano Zacchiroli a écrit : > > The point of NMUs is *helping* a maintainer which, for different reasons, is > temporarily unable to fix specific issues in their packages. If the NMU-er > keeps that principle in mind, everything else descends more or less

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wed, Apr 18, 2012 at 11:28:33AM -0400, Chris Knadle wrote: > Thanks -- however after reading it, my opinion of NMUs has not changed, > except > for lowering of severity level. [And realistically at least in the general > case I don't think another DD is going to do an NMU if a bug is not RC.

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wed, Apr 18, 2012 at 02:57:39PM -0700, Steve Langasek wrote: > "Hijacks" are what they say on the tin. That's not a tool that should be > part of the toolkit, even as a weapon of last resort. We have a procedure > for orphaning packages whose maintainers are inactive, and we have the TC to > a

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

Le Wed, Apr 18, 2012 at 10:00:43AM -0400, Chris Knadle a écrit : > > But what I'm seeing is that there are "in-between" states, where there > doesn't > seem to be any correct action to take. If a maintainer is not completely MIA > but is going to not have any time for maintainership for 6 mont

Re: wine-unstable in Debian

On 12-04-18 at 07:17pm, Simon McVittie wrote: > I hesitate to suggest this if there's a possibility that the main wine > package can come up to date before we freeze, but one way to have Wine > 1.4 (and/or 1.2) in the distribution without NMUs/hijacks would be a > parallel wine-1.4 source packag

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wed, Apr 18, 2012 at 10:16:56AM +0100, Jon Dowland wrote: > On Wed, Apr 18, 2012 at 04:57:14PM +0800, Thomas Goirand wrote: > > what can we do if the maintainer doesn't admit his lack of time or his > > lack of skills/knowledge? My understanding is that in Debian, we are > > stuck, right? I beli

Re: wine-unstable in Debian

On 15/04/12 15:04, Ben Hutchings wrote: > On Sun, 2012-04-15 at 19:32 +0600, Andrey Rahmatullin wrote: >> On Sun, Apr 15, 2012 at 01:18:28PM +0200, Petr Baudis wrote: >>> I am rather dazzled that while there is working source package >>> of wine-1.5 ready, other people are working on gradually >>>

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

Quoting Chris Knadle (chris.kna...@coredump.us): > for lowering of severity level. [And realistically at least in the general > case I don't think another DD is going to do an NMU if a bug is not RC.] Have you seen the gazillion of localization NMUs I'm doing for about 4-5 years now? :-) As l

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wed, Apr 18, 2012 at 12:20:51PM -0400, Joey Hess wrote: > Package removal frequently causes collatoral damage, and in my > experience, those doing the removals rarely consider it, and are happy > wasting other people's time. Sometimes not removing a package causes collatoral damage and wastes o

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

Neil Williams wrote: > Equally, take a care about which packages your packages depend upon > because if there are optional components which bring in dependencies on > shoddy code, you may need to quickly back away from those dependencies > or face your own package being removed. This conflates the

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wednesday, April 18, 2012 11:42:33, Jon Dowland wrote: > On Wed, Apr 18, 2012 at 11:28:33AM -0400, Chris Knadle wrote: > > The way section 5.11 is written, it implies NMUs are for bug fixes only. > > It literally states "Fixing cosmetic issues or changing the packaging > > style in NMUs is disc

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wed, Apr 18, 2012 at 11:28:33AM -0400, Chris Knadle wrote: > The way section 5.11 is written, it implies NMUs are for bug fixes only. It > literally states "Fixing cosmetic issues or changing the packaging style in > NMUs is discouraged." Nowhere in the section is it implied that NMUs can be

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wednesday, April 18, 2012 10:21:45, Stefano Zacchiroli wrote: > On Wed, Apr 18, 2012 at 10:00:43AM -0400, Chris Knadle wrote: > > Debian has NMUs (Non-Maintainer Uploads) -- however this is mainly meant > > for uploading critical bug fixes without having to resort to hijacking > > the package, a

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wed, Apr 18, 2012 at 10:21 AM, Stefano Zacchiroli wrote: > On Wed, Apr 18, 2012 at 10:00:43AM -0400, Chris Knadle wrote: >> Debian has NMUs (Non-Maintainer Uploads) -- however this is mainly meant for >> uploading critical bug fixes without having to resort to hijacking the >> package, and AFAI

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wednesday, April 18, 2012 04:57:14 PM Thomas Goirand wrote: > On 04/18/2012 08:27 AM, Steve McIntyre wrote: > > If a maintainer isn't (capable of) doing the necessary work on a > > package themselves, then after a while the best thing they can do is > > admit that and cede control to others. It'

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wed, Apr 18, 2012 at 10:00:43AM -0400, Chris Knadle wrote: > Debian has NMUs (Non-Maintainer Uploads) -- however this is mainly meant for > uploading critical bug fixes without having to resort to hijacking the > package, and AFAIK not to be used to upload new versions of the software. Before

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wed, 18 Apr 2012 11:05:38 +0100 Moray Allan wrote: > On Wed, 2012-04-18 at 10:16 +0100, Jon Dowland wrote: > > We have hijacks, we have the tech committee: weapons of last resort. > > I was thinking about the same issue before this thread. My feeling is > that over the same time period in wh

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wednesday, April 18, 2012 04:57:14, Thomas Goirand wrote: > On 04/18/2012 08:27 AM, Steve McIntyre wrote: > > If a maintainer isn't (capable of) doing the necessary work on a > > package themselves, then after a while the best thing they can do is > > admit that and cede control to others. It's

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wed, 2012-04-18 at 10:16 +0100, Jon Dowland wrote: > We have hijacks, we have the tech committee: weapons of last resort. I was thinking about the same issue before this thread. My feeling is that over the same time period in which we've moved towards team maintenance, and moved to a lower thr

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wed, Apr 18, 2012 at 10:16:56AM +0100, Jon Dowland wrote: > On Wed, Apr 18, 2012 at 04:57:14PM +0800, Thomas Goirand wrote: > > what can we do if the maintainer doesn't admit his lack of time or his > > lack of skills/knowledge? My understanding is that in Debian, we are > > stuck, right? I beli

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On Wed, Apr 18, 2012 at 04:57:14PM +0800, Thomas Goirand wrote: > what can we do if the maintainer doesn't admit his lack of time or his > lack of skills/knowledge? My understanding is that in Debian, we are > stuck, right? I believe that was the message of Chris: we don't really > have procedures

Re: what to do is maintainer is lacking? (was: wine-unstable in Debian)

On 04/18/2012 08:27 AM, Steve McIntyre wrote: > If a maintainer isn't (capable of) doing the necessary work on a > package themselves, then after a while the best thing they can do is > admit that and cede control to others. It's not an easy thing to admit > "failure" like this, but it's better to

Re: wine-unstable in Debian

Please note that in the following I'm solely trying to help all involved, and that none of the below is meant to be criticism -- so if any is implied, that is strictly unintentional. On Tuesday, April 17, 2012 13:17:45, Stefano Zacchiroli wrote: > On Sun, Apr 15, 2012 at 03:07:54PM -0400, Chris

Re: wine-unstable in Debian

On Sun, Apr 15, 2012 at 03:07:54PM -0400, Chris Knadle wrote: > C) Current WINE maintainers are either MIA or time overload elsewhere. > Volunteers trying to help who have made additional 1.1.x packages are stuck > waiting because they do not have access to the pkg-wine git repo. Just to nitpic

Re: wine-unstable in Debian

On Sunday, April 15, 2012 09:32:53, Andrey Rahmatullin wrote: > On Sun, Apr 15, 2012 at 01:18:28PM +0200, Petr Baudis wrote: > > I am rather dazzled that while there is working source package > > > > of wine-1.5 ready, other people are working on gradually packaging > > wine-1.1.x releases; > >

Re: wine-unstable in Debian

On Sun, 2012-04-15 at 19:32 +0600, Andrey Rahmatullin wrote: > On Sun, Apr 15, 2012 at 01:18:28PM +0200, Petr Baudis wrote: > > I am rather dazzled that while there is working source package > > of wine-1.5 ready, other people are working on gradually packaging > > wine-1.1.x releases; > I'm sur

Re: wine-unstable in Debian

On Sun, Apr 15, 2012 at 01:18:28PM +0200, Petr Baudis wrote: > I am rather dazzled that while there is working source package > of wine-1.5 ready, other people are working on gradually packaging > wine-1.1.x releases; I'm surprised that not everyone involved is such dazzled. > Also, it seems

Re: wine-unstable in Debian

Hi! On Sat, Apr 14, 2012 at 11:23:47PM +0200, Kai Wasserbäch wrote: > I'm going to be brief: > (short version of > my motivation behind those packages). I have read that post originally, it explained well why you created the package

Re: wine-unstable in Debian

[Please don't CC me on messages to debian-devel.] Petr Baudis schrieb am 14.04.2012 16:51: > Hi! > > It appears that the last release of wine easily available in Debian > is from 2009, quite a surprising state for a high-profile project like > that. Kai Wasserbäch appears to be very kindly p

Re: wine-unstable in Debian

On Sat, Apr 14, 2012 at 05:56:58PM +0200, Adam Borowski wrote: > It's not even about unstable releases of wine, we're multiple major stable > releases past as well: > > Upstream has: > * devel 1.5.2 > * stable1.4 > > Debian has: > * unstable 1.0.1-3.5 > * experimental 1.1.24

Re: wine-unstable in Debian

2012-04-14 16:51, Petr Baudis skrev: I know that there is also an effort by Ove Kåven to bring wine up-to-date with some nice extras (thanks for that too!), but it seems to be quite slow-paced (the last status update I have found was from Sep 2011), so perhaps it would be beneficial to have wo

Re: wine-unstable in Debian

On Sat, Apr 14, 2012 at 04:51:56PM +0200, Petr Baudis wrote: > Hi! > > It appears that the last release of wine easily available in Debian > is from 2009, quite a surprising state for a high-profile project like > that. Kai Wasserbäch appears to be very kindly providing wine-unstable > packag

wine-unstable in Debian

Hi! It appears that the last release of wine easily available in Debian is from 2009, quite a surprising state for a high-profile project like that. Kai Wasserbäch appears to be very kindly providing wine-unstable packages for Debian at http://dev.carbon-project.org/debian/wine-unsta