Re: Proposal for collaborative maintenance of packages

skaller <[EMAIL PROTECTED]> writes: > Actually this is what happens now, and the process isn't all that fast, > and isn't all the coherent: the most popular new architecture -- the one > set to dominate the desktop market IMHO -- and the primary arch of > Ubuntu -- namely x86_64 -- isn't even buil

Re: Proposal for collaborative maintenance of packages

skaller <[EMAIL PROTECTED]> writes: > I might be willing to package some of these things myself. What puts me > off is not doing the packaging work -- its having to hassle about > getting a DD to upload it. And then hassle them every time there is an > upgrade. I don't really like hassling people

Re: Proposal for collaborative maintenance of packages

On Wed, 2005-12-28 at 23:50 -0200, Gustavo Franco wrote: > > (...) > > I wasn't addressing your point specifically. Instead, I'm raising > > another one. The whole Debian system is a serious pain and an > > impediment to cooperation. Ubuntu is not much better. > > > > I should not have to be a DD

Re: RFS: gmysqlcc -- GTK+ client for mysql databases

Sorry for the late! Laszlo Boszormenyi wrote: It looks good, but I have some points: - please close your ITP from debian/changelog; Yes, at the moment I upload the package I did not have the ITP. - debian/README contains your changes to upstream source, but not debian/changelog; This is

Re: Proposal for collaborative maintenance of packages

On Thu, Dec 29, 2005 at 02:14:14PM +1100, skaller wrote: > On Wed, 2005-12-28 at 20:44 -0500, Justin Pryzby wrote: > > > > EG: My comp is on the net sometimes and sitting here idle. > > > I'd be happy if Debian used it occasionally to build binaries. > > > Where is the web page telling me how to a

Re: Proposal for collaborative maintenance of packages

On Wed, 2005-12-28 at 20:44 -0500, Justin Pryzby wrote: > > EG: My comp is on the net sometimes and sitting here idle. > > I'd be happy if Debian used it occasionally to build binaries. > > Where is the web page telling me how to advise Debian autobuilder > > how to access my comp?? > That won't h

Re: Proposal for collaborative maintenance of packages

On Thu, 2005-12-29 at 13:05 +1100, Matthew Palmer wrote: > On Thu, Dec 29, 2005 at 12:13:31PM +1100, skaller wrote: > > This is how Wikipedia works and why it is successful. With minimal > > fuss I have contributed some comments and a couple of changes. > > How easy is it for a Wikipedia comment t

Re: Proposal for collaborative maintenance of packages

> (...) > I wasn't addressing your point specifically. Instead, I'm raising > another one. The whole Debian system is a serious pain and an > impediment to cooperation. Ubuntu is not much better. > > I should not have to be a DD to commit to > the archive -- ANYONE should be able to commit perhaps

Re: Proposal for collaborative maintenance of packages

On Thu, Dec 29, 2005 at 12:13:31PM +1100, skaller wrote: > This is how Wikipedia works and why it is successful. With minimal > fuss I have contributed some comments and a couple of changes. How easy is it for a Wikipedia comment to contain a rootkit, though? - Matt -- To UNSUBSCRIBE, email to

Re: Proposal for collaborative maintenance of packages

On Thu, Dec 29, 2005 at 12:13:31PM +1100, skaller wrote: > On Wed, 2005-12-28 at 21:27 -0200, Gustavo Franco wrote: > > skaller wrote: > > > On Wed, 2005-12-28 at 13:37 -0200, Gustavo Franco wrote: > I would beg of those with interest in Debian to try to > figure out a way to streamline the process

Re: RFS: libjavascript-rpc-perl -- Perl module to process Remote procedure

Jonas Genannt <[EMAIL PROTECTED]> writes: > Russ Allbery wrote: >> The package looks fine, except that you didn't need to repackage the >> upstream source. The package build tools don't care in the slightest >> what directory the upstream source unpacks into; they just care that >> the tar.gz fil

Re: Proposal for collaborative maintenance of packages

On Wed, 2005-12-28 at 21:27 -0200, Gustavo Franco wrote: > skaller wrote: > > On Wed, 2005-12-28 at 13:37 -0200, Gustavo Franco wrote: > > > >> it's > >>just a matter to publish the patches (a good PQM will do that for you) > >>and let the others branch' maintainers do the merge when necessary. >

Re: Interest in packaging GNU Shishi and GNU Generic Security Service?

Simon Josefsson <[EMAIL PROTECTED]> writes: > I renamed the upstream release to shishi_0.0.23.orig.tar.gz and placed > it in ../. That seem to have done the trick, thanks! > (Couldn't it have used shishi-0.0.23.tar.gz? I'm not sure if I > understand the significance of my step.) The packaging

Re: Proposal for collaborative maintenance of packages

skaller wrote: > On Wed, 2005-12-28 at 13:37 -0200, Gustavo Franco wrote: > >> it's >>just a matter to publish the patches (a good PQM will do that for you) >>and let the others branch' maintainers do the merge when necessary. > > > Publishing patches is a serious pain in the backside > and a hu

Re: Proposal for collaborative maintenance of packages

On Wed, 2005-12-28 at 13:37 -0200, Gustavo Franco wrote: > it's > just a matter to publish the patches (a good PQM will do that for you) > and let the others branch' maintainers do the merge when necessary. Publishing patches is a serious pain in the backside and a huge impediment to cooperation.

mdf2iso already packaged in Ubuntu Universe

A few months back, I filed the ITP Bug#310876 . Just as I'm finally uploading this to mentors.debian.net and about to look for a sponsor, I discovered that Lukas Fittl had packaged this in Ubuntu Universe. Lukas, do you plan to upload it to Debian, too? If not,

Re: new pkg: libcrypt-simple-per

On Wed, Dec 28, 2005 at 07:33:31PM +0100, Sandro Tosi wrote: > Hi all, > while still studing new maintainers' guide & debian policy to create a > correct deb package, should I open an ITP bug? Yes; > Against what? Yes, use 'reportbug wnpp'. > More in general, what is the usual way to create a new

RFS: libalgorithm-dependency-perl -- Base class for implementing various dependency trees in Perl

Hello, I am searching for an sponsor for my libalgorithm-dependency-perl package. * Package name: libalgorithm-dependency-perl Version : 1.101 Upstream Author : Adam Kennedy <[EMAIL PROTECTED]> * URL : http://search.cpan.org/~adamk/ * License : GPL Descripti

Re: new pkg: libcrypt-simple-per

Hi all, while still studing new maintainers' guide & debian policy to create a correct deb package, should I open an ITP bug? Against what? wnpp? More in general, what is the usual way to create a new package? something like this: 1. choose a program 2. open an ITP bug 3. package it 4. drop an em

Re: Proposal for collaborative maintenance of packages

Henrique de Moraes Holschuh wrote: > On Tue, 20 Dec 2005, Russ Allbery wrote: > >>You just lost the people that I'm talking about. I can explain a >>changeset, but merges are deep black magic that are extremely difficult to >>understand except at a highly abstract level, and when using a distribu

Re: Taking over different packages with a single source package

On Wed, Dec 28, 2005 at 12:48:09PM +0100, Danai SAE-HAN (?$B4ZC#BQ) wrote: > Op maa 26 dec 2005 18:40:13 +0100 schreef Justin Pryzby: > > On Sun, Dec 25, 2005 at 10:34:04PM +0100, Danai SAE-HAN (?$B4ZC#BQ) wrote: > >> Op zon 25 dec 2005 17:30:07 +0100 schreef Justin Pryzby: > >> > >> > On Sat, Dec

RFS: bmeps, command line tool for converting bitmap images to eps-files

I'm looking for a sponsor for a set of deb-packages of bmeps and the libraries. This application is a tool to convert various bitmaps to eps-format. It is released by the upstream author Dirk Krause under LGPL. The upstream web-site is at http://bmeps.sourceforge.net. >From the control file: The

RFS: libsimpledb -- C++ ODBC database API

Hello, I am searching for an sponsor for my libsimpledb package. * Package name: libsimpledb Version : 1.3 Upstream Author : Russell Kliese <[EMAIL PROTECTED]> * URL : http://simpledb.sourceforge.net/ * License : LGPL-2.1 Description : C++ ODBC database