Re: List of (un)sponsored packages on Mentors (approximate)

[Paul TBBle Hampson]

On Mon, Jul 23, 2007 at 06:35:06PM +0200, Bart Martens wrote:
> Here's also a list of packages needing a sponsor.
> http://people.debian.org/~bartm/borg/needssponsor.html

Your title= tagging has unfortunately barfed on my name, due
to the "TBBle" in it causing the quoted string to terminate
early.

(See the openjpeg entry for example)

-- 
---
Paul "TBBle" Hampson, B.Sc, LPI, MCSE
On-hiatus Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
[EMAIL PROTECTED]

Of course Pacman didn't influence us as kids. If it did,
we'd be running around in darkened rooms, popping pills and
listening to repetitive music.
 -- Kristian Wilson, Nintendo, Inc, 1989

License: http://creativecommons.org/licenses/by/2.1/au/
---


pgplh7EaHrfG5.pgp
Description: PGP signature

Re: RFS: bmpx (updated package)

[Thijs Kinkhorst]

Hi Thierry,

> I am looking for a sponsor for the new version 0.40.0~rc3-1
> of my package "bmpx".

Excellent work, I'm building it now and will upload it if no further problems 
arise.


thanks,
Thijs


pgpsRU7kBlbxX.pgp
Description: PGP signature

Re: List of (un)sponsored packages on Mentors (approximate)

[Kumar Appaiah]

On Thu, Jul 26, 2007 at 07:50:49PM +1000, Paul TBBle Hampson wrote:
> Your title= tagging has unfortunately barfed on my name, due
> to the "TBBle" in it causing the quoted string to terminate
> early.

Well, I don't think this page is necessary anymore, since better
options to check this are available (courtesy this thread). So, don't
bother too much; that page is going away in a while! :-)

Kumar
-- 
Kumar Appaiah,
462, Jamuna Hostel,
Indian Institute of Technology Madras,
Chennai - 600 036


signature.asc
Description: Digital signature

Re: (still) RFS: syck -- a fast YAML parser kit (updated/improved package)

[David Moreno Garza]

Thomas Jollans wrote:
> Hello mentors, (David: after your blog post I decided to Cc ;-) )

Way to go, baby :-)

> I am looking for a sponsor for the new version 0.55+svn256-1 of the
> package 'syck', which is already in Debian. Robert Jordens
> <[EMAIL PROTECTED]> is the registered maintainer and has given me
> permission to take the package, but has stopped respoding to my mail.

[...]

> it fixes bugs 324316, 359245, 378440, 415217, 418308, 432416
> 
> This upload would also enable the upload of my package python-syck,
> which would fix a user request and another bunch of bugs.
> 
> I hope this package not to be too much hassle; It's lintian and linda
> clean at any rate.
> 
> I would like to add that the package has been finished for over a month.
> (I first requested sponsorship on this list in 26 Jun...)
> 
> Thank you for reading this far,
> Looking forward to hearing from you

This is so cool.

Because of some very recent work, I was thinking on packaging the
YAML::Syck Perl module, which implements nicely the libsyck library.
I've been working with this for serializing objects into persistent
data.

Just as promised on my blog entry[1], I'll sponsor this.

1: http://www.damog.net/20070726/debian-maintainers/

-- 
David Moreno Garza <[EMAIL PROTECTED]> | http://www.damog.net/
 My <[EMAIL PROTECTED]> email address is not working, due to vacation
 period on the university and uncareful sysadmins. I won't lose your mail,
 but probably I will only get it until a couple of weeks from now. In the
 meantime, you can use my always mighty <[EMAIL PROTECTED]>. Thanks.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: List of (un)sponsored packages on Mentors (approximate)

[Kumar Appaiah]

On Thu, Jul 26, 2007 at 03:04:31PM -0500, Raphael Geissert wrote:
> I've made some changes to your script in order to improve it's results.
> The modified script can be downloaded from here:
> http://files.myopera.com/atomo64/files/mentors_comp.py
> and the results generated by the modified script:
> http://files.myopera.com/atomo64/files/output.test.html

Very nice!

Kumar
-- 
Kumar Appaiah,
462, Jamuna Hostel,
Indian Institute of Technology Madras,
Chennai - 600 036


signature.asc
Description: Digital signature

(still) RFS: syck -- a fast YAML parser kit (updated/improved package)

[Thomas Jollans]

Hello mentors, (David: after your blog post I decided to Cc ;-) )

I am looking for a sponsor for the new version 0.55+svn256-1 of the
package 'syck', which is already in Debian. Robert Jordens
<[EMAIL PROTECTED]> is the registered maintainer and has given me
permission to take the package, but has stopped respoding to my mail.

The meta data:

* Package name: syck
  Version : 0.55+svn256-1
  Upstream Author : Why The Lucky Stiff <[EMAIL PROTECTED]>
* URL : http://whytheluckystiff.net/syck
* License : BSD
  Section : devel

Where to get the package:
http://mentors.debian.net/debian/pool/main/s/syck/syck_0.55+svn256-1.dsc

Why you really want to sponsor this:
YAML  is a great language, and syck is quite a good and
especially fast parser for it (the package includes PHP5 (was PHP4!)
bindings and the C lib). At the moment, syck is in a very lousy state in
Debian - an antique (and thus less useful) version full of bugs. After
this upload, the state of it would be much less lousy --- The fixed bugs
can be used as a simple inaccurate statistical proof here:

it fixes bugs 324316, 359245, 378440, 415217, 418308, 432416

This upload would also enable the upload of my package python-syck,
which would fix a user request and another bunch of bugs.

I hope this package not to be too much hassle; It's lintian and linda
clean at any rate.

I would like to add that the package has been finished for over a month.
(I first requested sponsorship on this list in 26 Jun...)

Thank you for reading this far,
Looking forward to hearing from you

Thomas Jollans


signature.asc
Description: This is a digitally signed message part

[RFS] stunnel -- Universal SSL tunnel for network daemons

[Luis Rodrigo Gallardo Cruz]

Dear mentors,

I am looking for a sponsor for the new version 2:4.20-1
of the package "stunnel", which I'm adpoting.

It builds these binary packages:
stunnel- Universal SSL tunnel for network daemons

The package is lintian/linda/piuparts clean.

The upload would fix these bugs: 382099, 416955

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/s/stunnel
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/s/stunnel/stunnel_4.20-1.dsc

This is a major update to the package, since I'm transitioning to
version 4. Eventually I'll upload a new stunnel4, which will be a
simple dummy upgrade package to pull in stunnel. I think it would be
convenient if both packages were to be sponsored by the same person.

I would also appreciate your guidance as to the handling of the open
bugs in this package and in stunnel4. My plan, right now, is to wait
for the upload, then clone and reassign the open bugs in stunnel4 to
stunnel, mark them all as found in the uploaded version, then manualy
send -done messages for the ones this upload closes. After that, when
I upload the new stunnel4 version, mark that as closing the original
stunnel4 bugs.

Kind regards,

-- 
Rodrigo Gallardo
GPG-Fingerprint: 7C81 E60C 442E 8FBC D975  2F49 0199 8318 ADC9 BC28


signature.asc
Description: Digital signature

Re: Getting involved with Debian development...

[Paul Cager]

Tim Hull wrote:
> Hi,
[...]
> Anyway, I am curious what exactly it entails to become a Debian developer,
> and what would be best to do if one wanted to involve
> oneself in Debian with this ultimate goal.  I do know of a couple things
> that aren't packaged that I may want to take a stab at at some point
> (xcalib and virtualbox some to mind immediately), and I also may want to
> work on documentation and the release structure/release packaging.
> (in using Debian and Ubuntu, there are things I like/dislike about both
> release structures). Can some current Debian developers fill me in a little
> on what would be best for me to do in this case?
[...]
> Tim Hull
> 

This is a good place to start:

 http://www.debian.org/doc/devel-manuals#maint-guide
 http://wiki.debian.org/HowToPackageForDebian
 http://www.debian.org/devel/join/

And this mailing list is a good place for questions, or the
#debian-mentors IRC channel on irc.debian.org.

Hope this helps,
Paul


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Getting involved with Debian development...

[Tim Hull]

Hi,

I've been interested in Linux for some time now, and have used various
distributions on and off.
My first distribution was Debian hamm, way back in 1999.  I still remember
getting KDE 1.0 to work
and configuring my ISA modem on that old Pentium II machine...  After that,
I went through Red Hat,
Mandrake, and a whole slew of minor distributions - but was always partial
to the "Debian way". I even installed Debian on some old 68k Macs back in
the day! I then went back to (gasp) Windows for a  period of time, had a
period on Kanotix/Ubuntu in 2004/05, and finally to Mac OS X.

Though Mac OS X is good, its closed nature has annoyed me somewhat - one
striking example is that one can't
even disable "sleep on lid close"!  I've also wanted to get involved in
development/testing - especially with this being my senior
year in college - and the world of Mac OS X is oriented around closed
projects and closed source.  As a result, I've been working with
Linux on my MacBook some - for the most part, Debian and Ubuntu - and
investigating various bugs, testing things like Compiz
and various wireless drivers, and delving into the actual source code some.

Anyway, I am curious what exactly it entails to become a Debian developer,
and what would be best to do if one wanted to involve
oneself in Debian with this ultimate goal.  I do know of a couple things
that aren't packaged that I may want to take a stab at at some point
(xcalib and virtualbox some to mind immediately), and I also may want to
work on documentation and the release structure/release packaging.
(in using Debian and Ubuntu, there are things I like/dislike about both
release structures). Can some current Debian developers fill me in a little
on what would be best for me to do in this case?

I should just point out a few things, though, so I don't get flamed if any
of this comes up later (I've heard some nightmare stories involving Debian
development).  First of all, I'm also looking into Ubuntu, for many of the
same reasons - I'm still undecided as to what project I'm going to get
involved in.  Secondly, I may not be as passionate about free software as
some within the project - while I definitely prefer it, I will use non-free
software if it works significantly better for my purposes or allows me to
use my hardware (i.e. wireless drivers).  Finally, I am inexperienced where
it comes to low-level C coding (though I can generally understand at least
some of it).

Tim Hull

RFS: qink

[Adam Cécile (Le_Vert)]

Dear mentors,

I am looking for a sponsor for my package "qink".

* Package name: qink
  Version : 0.3.1-1
  Upstream Author : Moris Ravasio <[EMAIL PROTECTED]>
Matvey Kozhev <[EMAIL PROTECTED]>
* URL : http://code.google.com/p/qink/
* License : GPL
  Section : admin

It builds these binary packages:
qink   - Simple printer ink level monitor based on libinklevel and Qt4

The package appears to be lintian clean.

The upload would fix these bugs: 434748

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/q/qink
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget http://mentors.debian.net/debian/pool/main/q/qink/qink_0.3.1-1.dsc

I would be glad if someone uploaded this package for me.

Kind regards
 Adam Cécile


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Getting involved with Debian development...

[Matthew Palmer]

On Thu, Jul 26, 2007 at 04:13:06PM -0400, Tim Hull wrote:
> Anyway, I am curious what exactly it entails to become a Debian developer,
> and what would be best to do if one wanted to involve
> oneself in Debian with this ultimate goal.

The FQ... the FAQ... 

http://people.debian.org/~mpalmer/debian-mentors_FAQ.html

- Matt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: List of (un)sponsored packages on Mentors (approximate)

[Raphael Geissert]

On 26/07/07, Kumar Appaiah <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 26, 2007 at 07:50:49PM +1000, Paul TBBle Hampson wrote:
> > Your title= tagging has unfortunately barfed on my name, due
> > to the "TBBle" in it causing the quoted string to terminate
> > early.
>
> Well, I don't think this page is necessary anymore, since better
> options to check this are available (courtesy this thread). So, don't
> bother too much; that page is going away in a while! :-)

He was talking about Bart's page.
I've made some changes to your script in order to improve it's results.
The modified script can be downloaded from here:
http://files.myopera.com/atomo64/files/mentors_comp.py
and the results generated by the modified script:
http://files.myopera.com/atomo64/files/output.test.html

I've also modified it so it doesn't show the 'handled' RFS'.

>
> Kumar
> --
> Kumar Appaiah,
> 462, Jamuna Hostel,
> Indian Institute of Technology Madras,
> Chennai - 600 036
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGqLdySd75awtatOcRAnM8AJ4lYbfhMM2XJeM0XiyOsZNZhrMjMACfZCQD
> ZvVbURkxCSJvkfNtzy10ELI=
> =z4zJ
> -END PGP SIGNATURE-
>
>

Regards,
-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

Say NO to Microsoft Office broken standard.
See http://www.noooxml.org/petition


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

fig2sxd

[Alexander Bürger]

Dear sponsors,

four weeks ago I uploaded a new version of my package fig2sxd to 
mentors.debian.net, but unfortunately it is still waiting for a sponsor.


The new version includes modifications which should makes the code 
compatible with g++ 4.3 (bug 417183), and it adds a new feature 
requested by a user, namely writing the .sxd file to stdout.


Two problems with the previous upload attempts are gone:
* removed the typo in the bug number present in version 0.17-1
* public gpg key should now be available.


The package can be found on mentors.debian.net:
- URL:
 http://mentors.debian.net/debian/pool/main/f/fig2sxd
- Source repository:
 deb-src http://mentors.debian.net/debian unstable main contrib non-free
- dget
 http://mentors.debian.net/debian/pool/main/f/fig2sxd/fig2sxd_0.17-2.dsc


I would appreciate if somebody could sponsor the package, or point me at 
remaining problems.


Best wishes,

Alexander Bürger

Re: fig2sxd

[Piotr Ożarowski]

why 0.17-2 and not 0.17-1?


pgp5dSB2afWad.pgp
Description: PGP signature

Re: RFS: switchconf

[Thijs Kinkhorst]

Hi Jose,

On Thursday 26 July 2007 01:30, Jose Manuel dos Santos Calhariz wrote:
> I am the upstream author of switchconf package, that is in etch, and I
> have prepared a new version of switchconf.  This version fixes an
> unreported bug introduced in the last version, add tests to check if
> switchconf still works as expected and a change to the copyrigth file
> to give atribution of my work to my employer.

I've taken a look and have some minor comments:

* In the 'dist' target of the makefile, you do not use maximum compression
  for the orig.tar.gz. You can consider compressing it with -9 or GZIP=--best

* You've gotten a couple of typos into the package. Here's the ones I saw:
  - changelog: "upstrean"/upstream, rigth/right and midle/middle

* The README file you install doesn't really contain much information over
  the information already present in /usr/share/doc/switchconf. Is it actually
  necessary?

* You could consider to update the debhelper compat level to 5.

Since it looks fine otherwise, I've uploaded your package. Maybe you can 
correct these points in your repository for a next upload. Thanks for your 
efforts!


Thijs


pgpziLghvodL3.pgp
Description: PGP signature

Re: Doubts about PHP

[Steve Langasek]

On Mon, Jul 23, 2007 at 03:07:23PM +, [EMAIL PROTECTED] wrote:
> On Sun, Jul 22, 2007 at 02:47:41PM -0700, Steve Langasek wrote:
> > On Sun, Jul 22, 2007 at 07:12:47PM +0200, Gregory Colpart wrote:
> > > On Thu, Jul 19, 2007 at 06:06:14PM -0500, Raphael Geissert wrote:

> > > > That's exactly the reason why I recommend to Depend on php5.
> > > > $ apt-cache show php5 | grep Depends
> > > > Depends: libapache2-mod-php5 (>= 5.2.3-1) | php5-cgi (>= 5.2.3-1),
> > > > php5-common (>= 5.2.3-1)

> > > > That's more than enough.

> > > * For web server, I recommend:

> > > Depends: apache2 | httpd

> > > * For PHP depends, if your application is compatible with PHP4, you
> > > should let php4 and php4-cgi (because php4-cgi is not in depends
> > > of virtual package php4 in sarge):

> > Which makes it not particularly relevant to newly-packaged software.  In
> > fact, you can pretty much drop the 'php4' alternative altogether now, since
> > php5 was in etch and php4 won't be in lenny.

> while I wouldn't want to encourage anyone to use php4 ... ;-)

> what about backports?

> if a package actually works with an older version of supporting
> software, why not use that usefull information in the dependencies
> instead of throwing it away ?

> Saying that package x depends on package y >= 5 when in fact x depends
> on y >= 4, just because that version of package x is being packaged for
> unstable and there is no y < 5 in unstable really seems like a lost 
> opportunity to me :-(   

That is not the reason at all.

First of all, this is not an instance of saying php (>= 4) instead of php
(>= 5); this is saying php5 | php4 | php4-cgi vs. php5.  If it were simply
the case of getting the versioning right on a single versioned dependency, I
would agree with you, but alternative dependencies do come with some cost.
First, they add complexity to dependency resolution, which when compounded
can cause problems for aptitude and britney.  Second, particularly in the
case of php applications, maintainers almost never correctly express the
package's real dependencies.  For instance, if a package requires "php with
mysql support", this often gets expressed as "php5 | php4, php5-mysql |
php4-mysql", but that relationship is satisfied by combinations of packages
that may not be usable together for the target application -- e.g., it's
satisfied by php5 + php4-mysql, but php4-mysql's own dependencies are
satisfiable by phpapi-$foo which is provided by php4-cli, so you can install
these packages together and satisfy your web app's dependencies without
having a usable pairing.

So in the case of php-related packages, yes, I do think that new packages
should not bother with the alternative dependencies on php4*.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]