On November 7, 2002 12:41 pm, Michael Wetherell wrote:
On Thursday 07 November 2002 3:44 pm, Dimitrie O. Paun wrote:
We're still missing one. Any takers?
Yes, I'd really like to do that. What do I have to do to join up?
You have to know what you are doing. This is _very_ imprortant, because we're better off *not* providing binary packages, then providing broken ones. And you have to be prepared to produce such a package shortly after Alexandre does the source tarball. Now, I don't know what people know about packaging, so I can not filter applicants :) But I ask you to do a self evaluation, and if you think you're up for the job, you're on. :) For now, I've added you to the list. Cool! -- Dimi.
On Thu, Nov 07, 2002 at 10:44:55AM -0500, Dimitrie O. Paun wrote:
We're still missing one. Any takers?
What do you mean by "Debian maintainer", precisely? The most recent wine package in Debian is version 0.0.20021007-1, uploaded October 20 by Ove Kaaven. Has Ove indicated that he is no longer interested in maintaining this package? (He has not so indicated to Debian!) Or do you have something else in mind when referring to a "Debian maintainer"? -- Steve Langasek postmodern programmer
On November 7, 2002 01:55 pm, Steve Langasek wrote:
What do you mean by "Debian maintainer", precisely? The most recent wine package in Debian is version 0.0.20021007-1, uploaded October 20 by Ove Kaaven. Has Ove indicated that he is no longer interested in maintaining this package? (He has not so indicated to Debian!) Or do you have something else in mind when referring to a "Debian maintainer"?
Woops. My bad, I didn't realise Ove is the Debian maintainer. How silly of me, I'll correct that right away. -- Dimi.
On Thursday 07 November 2002 6:59 pm, Dimitrie O. Paun wrote:
On November 7, 2002 01:55 pm, Steve Langasek wrote:
What do you mean by "Debian maintainer", precisely? The most recent wine package in Debian is version 0.0.20021007-1, uploaded October 20 by Ove Kaaven. Has Ove indicated that he is no longer interested in maintaining this package? (He has not so indicated to Debian!) Or do you have something else in mind when referring to a "Debian maintainer"?
Woops. My bad, I didn't realise Ove is the Debian maintainer. How silly of me, I'll correct that right away.
Ah, that explains that. I've just been by the Debian site and realised that there is still a maintainer, very much so, and I was about to ask what exactly was it I'd volenteered for. Anyway, no problem. Short career that. Mike
On Thu, 7 Nov 2002, Michael Wetherell wrote:
On Thursday 07 November 2002 6:59 pm, Dimitrie O. Paun wrote:
On November 7, 2002 01:55 pm, Steve Langasek wrote:
What do you mean by "Debian maintainer", precisely? The most recent wine package in Debian is version 0.0.20021007-1, uploaded October 20 by Ove Kaaven. Has Ove indicated that he is no longer interested in maintaining this package? (He has not so indicated to Debian!) Or do you have something else in mind when referring to a "Debian maintainer"?
Woops. My bad, I didn't realise Ove is the Debian maintainer. How silly of me, I'll correct that right away.
Ah, that explains that. I've just been by the Debian site and realised that there is still a maintainer, very much so, and I was about to ask what exactly was it I'd volenteered for.
If you want, you or someone else could help by checking the Debian bugs on the package though; I don't know which bugs have been fixed in a later Wine release, nor did I ever get around to figure out the best way to forward such bugs to the used-to-be-rather-unorganized way of handling bugs (the one bug (which should be simple since it came with a patch) I did try to forward to wine-devel a year and a half ago had still not been resolved last time I looked). So, since I've been a little lazy about those bugs, I've been thinking about delegating responsibility for that to someone else, at a minimum. I haven't yet felt in need of filing a RFA or anything yet, though... (and the most recent package is 0.0.20021031-1, uploaded a couple of days ago)
Ove Kaaven wrote:
On Thu, 7 Nov 2002, Michael Wetherell wrote:
On Thursday 07 November 2002 6:59 pm, Dimitrie O. Paun wrote:
On November 7, 2002 01:55 pm, Steve Langasek wrote:
What do you mean by "Debian maintainer", precisely? The most recent wine package in Debian is version 0.0.20021007-1, uploaded October 20 by Ove Kaaven. Has Ove indicated that he is no longer interested in maintaining this package? (He has not so indicated to Debian!) Or do you have something else in mind when referring to a "Debian maintainer"?
Woops. My bad, I didn't realise Ove is the Debian maintainer. How silly of me, I'll correct that right away.
Ah, that explains that. I've just been by the Debian site and realised that there is still a maintainer, very much so, and I was about to ask what exactly was it I'd volenteered for.
If you want, you or someone else could help by checking the Debian bugs on the package though; I don't know which bugs have been fixed in a later Wine release, nor did I ever get around to figure out the best way to forward such bugs to the used-to-be-rather-unorganized way of handling bugs (the one bug (which should be simple since it came with a patch) I did try to forward to wine-devel a year and a half ago had still not been resolved last time I looked). So, since I've been a little lazy about those bugs, I've been thinking about delegating responsibility for that to someone else, at a minimum. I haven't yet felt in need of filing a RFA or anything yet, though... (and the most recent package is 0.0.20021031-1, uploaded a couple of days ago)
I am not sure this is the best way but I would suggest that for each Debian bug in the you should start a bug in Wine's Bugzilla. (That is assuming the bug is actualy in wine in wine of course) you should provide a url link to the debian bug in wine and vice versa. -- Tony Lambregts
Ove Kaaven wrote:
If you want, you or someone else could help by checking the Debian bugs on the package though
Ok sounds good. Did you want me to just contact you with a list of bugs you can close out, or should I apply to become a Debian maintainer so that I can close them out? On Friday 08 November 2002 1:07 am, Tony Lambregts wrote:
I am not sure this is the best way but I would suggest that for each Debian bug in the you should start a bug in Wine's Bugzilla. (That is assuming the bug is actualy in wine in wine of course) you should provide a url link to the debian bug in wine and vice versa.
Ok, I'll create bugzilla bugs for any that arn't already in there.
On Fri, Nov 08, 2002 at 04:13:37AM +0000, Michael Wetherell wrote:
Ove Kaaven wrote:
If you want, you or someone else could help by checking the Debian bugs on the package though
Ok sounds good. Did you want me to just contact you with a list of bugs you can close out, or should I apply to become a Debian maintainer so that I can close them out?
Generally, the preferred method is to send a followup message to the Debian bug in the BTS stating that the bug can be closed -- or, with maintainer approval, to close the bug yourself. -- Steve Langasek postmodern programmer
On Fri, 8 Nov 2002, Michael Wetherell wrote:
Ove Kaaven wrote:
If you want, you or someone else could help by checking the Debian bugs on the package though
Ok sounds good. Did you want me to just contact you with a list of bugs you can close out, or should I apply to become a Debian maintainer so that I can close them out?
You don't have to be a Debian maintainer to access the Debian BTS. It works on the trust system, anyone at all can change (including closing) a bug on any package. This used to be a disadvantage when spammers started adding xxx-close(a)bugs.debian.org addresses to their database, but I think they just added a spam filter, there's still no real restrictions as far as I know. So if you want to close the bugs yourself, you can. But you can also send me a list if would rather have me close them anyway.
On Friday 08 November 2002 1:07 am, Tony Lambregts wrote:
I am not sure this is the best way but I would suggest that for each Debian bug in the you should start a bug in Wine's Bugzilla. (That is assuming the bug is actualy in wine in wine of course) you should provide a url link to the debian bug in wine and vice versa.
Ok, I'll create bugzilla bugs for any that arn't already in there.
Thanks.
participants (5)
-
Dimitrie O. Paun -
Michael Wetherell -
Ove Kaaven -
Steve Langasek -
Tony Lambregts