winehq packages for Debian
Hi guys, I'm a regular volunteer in the #winehq IRC channel (man_in_shack). Some of you may know me :) I also maintain a few applications on AppDB and have had a couple of bugs found and fixed via bugzilla posts. I've been building Wine packages for my Debian systems for a while and now I've written myself some helper scripts to make the task trivial :) I build both amd64 and i386 packages. I'd like to request that I take over Scott Ritchie's position as maintainer for the winehq Debian packages as he seems to have all but abandoned Debian package building. I have the following caveats: 1) I don't have a suitable place to upload the packages (in terms of bandwidth restrictions) 2) At the moment, I'm not sure if the packages are suitable for an apt repository, as I don't have proper Changelogs or source packages. I'm not entirely sure what I'd need to do for this, so help would be appreciated 3) I'm fully set up to produce etch packages (Scott's packages aren't etch-compatible any more) as well as packages for lenny and sid 4) I'm not asking to take over Ubuntu package building (Scott seems to be good at this, and I don't have nor want an Ubuntu system) 5) I can be *very* quick to produce packages, as in the day after release (or even building packages from non-release revisions in git if required) Involvement in wine is fun! Regards, Ben Klein
So your plan is to take over Debian packaging while abandoning Ubuntu packaging? You already mentioned he has abandoned packaging (however I see new packages created on 8th November) Is there some technical reason you can't do Ubuntu Debs? I am trying to understand what is different from Ubuntu and Debian which would prevent you making a package for both. On Mon, Nov 10, 2008 at 12:45 AM, Ben Klein <shacklein(a)gmail.com> wrote:
Hi guys,
I'm a regular volunteer in the #winehq IRC channel (man_in_shack). Some of you may know me :) I also maintain a few applications on AppDB and have had a couple of bugs found and fixed via bugzilla posts.
I've been building Wine packages for my Debian systems for a while and now I've written myself some helper scripts to make the task trivial :) I build both amd64 and i386 packages.
I'd like to request that I take over Scott Ritchie's position as maintainer for the winehq Debian packages as he seems to have all but abandoned Debian package building. I have the following caveats: 1) I don't have a suitable place to upload the packages (in terms of bandwidth restrictions) 2) At the moment, I'm not sure if the packages are suitable for an apt repository, as I don't have proper Changelogs or source packages. I'm not entirely sure what I'd need to do for this, so help would be appreciated 3) I'm fully set up to produce etch packages (Scott's packages aren't etch-compatible any more) as well as packages for lenny and sid 4) I'm not asking to take over Ubuntu package building (Scott seems to be good at this, and I don't have nor want an Ubuntu system) 5) I can be *very* quick to produce packages, as in the day after release (or even building packages from non-release revisions in git if required)
Involvement in wine is fun!
Regards,
Ben Klein
Ubuntu packages have been up to date (uploaded within a day of release). Debian keeps falling behind because there's no easy way for me to build and test on Debian (with Ubuntu I can just upload them to launchpad and have it work). Thanks, Scott Ritchie Andrew Fenn wrote:
So your plan is to take over Debian packaging while abandoning Ubuntu packaging?
You already mentioned he has abandoned packaging (however I see new packages created on 8th November) Is there some technical reason you can't do Ubuntu Debs?
I am trying to understand what is different from Ubuntu and Debian which would prevent you making a package for both.
On Mon, Nov 10, 2008 at 12:45 AM, Ben Klein <shacklein(a)gmail.com> wrote:
Hi guys,
I'm a regular volunteer in the #winehq IRC channel (man_in_shack). Some of you may know me :) I also maintain a few applications on AppDB and have had a couple of bugs found and fixed via bugzilla posts.
I've been building Wine packages for my Debian systems for a while and now I've written myself some helper scripts to make the task trivial :) I build both amd64 and i386 packages.
I'd like to request that I take over Scott Ritchie's position as maintainer for the winehq Debian packages as he seems to have all but abandoned Debian package building. I have the following caveats: 1) I don't have a suitable place to upload the packages (in terms of bandwidth restrictions) 2) At the moment, I'm not sure if the packages are suitable for an apt repository, as I don't have proper Changelogs or source packages. I'm not entirely sure what I'd need to do for this, so help would be appreciated 3) I'm fully set up to produce etch packages (Scott's packages aren't etch-compatible any more) as well as packages for lenny and sid 4) I'm not asking to take over Ubuntu package building (Scott seems to be good at this, and I don't have nor want an Ubuntu system) 5) I can be *very* quick to produce packages, as in the day after release (or even building packages from non-release revisions in git if required)
Involvement in wine is fun!
Regards,
Ben Klein
Thanks guys :) If there's still any doubt, Ubuntu packaging as as different from Debian as Mandriva or SUSE are from Red Hat. It's theoretically possible to produce packages that work for both but it's a pain to maintain. Scott can keep doing Ubuntu packages because he's well set up for it. I will be taking over only the Debian packaging. Don't think of it as inefficient use of resources; think of it as distributing the load. Yay :) 2008/11/10 Scott Ritchie <scott(a)open-vote.org>
Ubuntu packages have been up to date (uploaded within a day of release).
Debian keeps falling behind because there's no easy way for me to build and test on Debian (with Ubuntu I can just upload them to launchpad and have it work).
Thanks, Scott Ritchie
Andrew Fenn wrote:
So your plan is to take over Debian packaging while abandoning Ubuntu packaging?
You already mentioned he has abandoned packaging (however I see new packages created on 8th November) Is there some technical reason you can't do Ubuntu Debs?
I am trying to understand what is different from Ubuntu and Debian which would prevent you making a package for both.
On Mon, Nov 10, 2008 at 12:45 AM, Ben Klein <shacklein(a)gmail.com> wrote:
Hi guys,
I'm a regular volunteer in the #winehq IRC channel (man_in_shack). Some of you may know me :) I also maintain a few applications on AppDB and have had a couple of bugs found and fixed via bugzilla posts.
I've been building Wine packages for my Debian systems for a while and now I've written myself some helper scripts to make the task trivial :) I build both amd64 and i386 packages.
I'd like to request that I take over Scott Ritchie's position as maintainer for the winehq Debian packages as he seems to have all but abandoned Debian package building. I have the following caveats: 1) I don't have a suitable place to upload the packages (in terms of bandwidth restrictions) 2) At the moment, I'm not sure if the packages are suitable for an apt repository, as I don't have proper Changelogs or source packages. I'm not entirely sure what I'd need to do for this, so help would be appreciated 3) I'm fully set up to produce etch packages (Scott's packages aren't etch-compatible any more) as well as packages for lenny and sid 4) I'm not asking to take over Ubuntu package building (Scott seems to be good at this, and I don't have nor want an Ubuntu system) 5) I can be *very* quick to produce packages, as in the day after release (or even building packages from non-release revisions in git if required)
Involvement in wine is fun!
Regards,
Ben Klein
Ben Klein wrote:
Hi guys,
I'm a regular volunteer in the #winehq IRC channel (man_in_shack). Some of you may know me :) I also maintain a few applications on AppDB and have had a couple of bugs found and fixed via bugzilla posts.
I've been building Wine packages for my Debian systems for a while and now I've written myself some helper scripts to make the task trivial :) I build both amd64 and i386 packages.
You have it. I believe I've proven my incompetence with making timely Debian releases. Talk to me (YokoZar) on IRC. By the way, the reason the Debian packages started disappearing was because I kept running into problems setting up my Debian VMs. Also my apologies to the 10+ people who've emailed me asking where they've gone in the past two weeks - I kept expecting to have them up the next day, and never get around to it.
I'd like to request that I take over Scott Ritchie's position as maintainer for the winehq Debian packages as he seems to have all but abandoned Debian package building. I have the following caveats: 1) I don't have a suitable place to upload the packages (in terms of bandwidth restrictions)
I can put them in the same place now. The issue for me wasn't uploading them, but getting them built properly.
2) At the moment, I'm not sure if the packages are suitable for an apt repository, as I don't have proper Changelogs or source packages. I'm not entirely sure what I'd need to do for this, so help would be appreciated
Apt ignores the changelog anyway (even Ubuntu users don't see the "version differences" in update manager). It's not hard to get it right though, I'll mentor you.
3) I'm fully set up to produce etch packages (Scott's packages aren't etch-compatible any more) as well as packages for lenny and sid
Etch has some missing 32-bit libraries that will give you grief on amd64, by the way. That's one reason I sort of gave up on it.
4) I'm not asking to take over Ubuntu package building (Scott seems to be good at this, and I don't have nor want an Ubuntu system) 5) I can be *very* quick to produce packages, as in the day after release (or even building packages from non-release revisions in git if required)
Thanks, Scott Ritchie
participants (3)
-
Andrew Fenn -
Ben Klein -
Scott Ritchie