RFS: libdc0 and valknut (ITA)

2009-11-10 Thread Maia Kozheva
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Mentors,

I am looking for a sponsor for my updates to the orphaned packages
libdc0 and valknut, taking over as the maintainer.

libdc0 version 0.3.23-1 can be found here:

http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=libdc0

valknut version 0.4.9-1 can be found here:

http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=valknut

Since valknut depends on the new version of libdc0, it should not be
uploaded until the former package is accepted and built.


Some more comments about these packages:

They are based on updated versions I uploaded to Ubuntu during the
Karmic development cycle, modified for Lintian cleanliness against the
latest version in unstable, as well as new copyright acknowledgements.

The version of libdc0 currently in Debian provides the binary packages
libdc0c2 and libdc0-dev. They are now libdc5 (new upstream soname) and
libdc-dev. I believe adding the soname number to the -dev package was a
mistake in the first place, and since valknut is the only package
depending on this library (and comes from the same upstream developers),
the rename will touch nothing once the valknut update follows libdc0.

Maia Kozheva
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJK+SO/AAoJEDqDNnQ69yYS3swIAMHg1RoKnsKf5wdYAVtliXxS
8tURW0z+q2x9YVt2aWC/yggMScmLLGs/yYOSgyrusiUSA9YWpgmtkAmu/XsNtu8m
tyMYbhc6g40dFvELcdkYCtjlMoipT2Q3TrBpLsQPerAliRVCnSXRz8JJPa9O+dNC
4KiC9pGjHPCzi1QWYlbHHXGLJo67+ptTgAS8Ww+abLTbKdLsfKs+Ok1xsIMDnOe9
kCsMxDvdpHN0rS/4TzQ3xkW5M75uAB67hH4noV5egre8sDyOkfbi1rH/HsoLA2Yx
3vnPyJQm5z5z3jX+pVwRbaReW/iF3rzAIKJsZVt3nQ/7sbKDKbyEqqY/2M91urM=
=M3wO
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: RFS: smplayer

2009-11-10 Thread Maia Kozheva
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07.11.2009 06:15, Kevin Coyner wrote:
 Uploaded.
 
 Thanks for packaging smplayer.
 
 Kevin
 
 

Thanks for the upload!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJK+SW3AAoJEDqDNnQ69yYSzB4IAIU7OISPfBTk3+Okmthpzx4O
2TsBbEsw81MuXiLCP7qRt19HWOMYxqChktOVyzZl7GdYB7u6YbkI3JowrOwpxmXn
3wkO00WZoiXDR2z1/ly3jcJ1SPa8xj1b4++VGACvhQ1VGUQHUzUuG3nrupR85oou
X4uFcLGZftJzgvACwnX2RQ5G4h2wrUqUm5IOkbQ3qRVnShPyrT473fbf0F7F6vAp
3oxWIcqigMXsOomJ96jBiRCS9u0ojY5aD+76TN/uIad3ivS6lPfp4QttWmV+qQ9W
CFKEqzdhSPdklplJfO7MJlLp5eULBeP/JvjjuVkbfskSuWzZMykP9qBq/jtVVxA=
=W2NO
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



RFS: libfile-copy-link-perl

2009-11-10 Thread Joel Roth
Hi Mentors, Sponsors and Maintainers,

I'm debianizing this Artistic/GPL 1+ perl
distribution, which is a dependency for a larger app I
also plan to release through Debian.

My first experience with this gently forgiving toolchain. :-) 
I've tried to dot my t's and cross my i's.

Any advice (and sponsorship) will be appreciated.

Details below.

Name: libfile-copy-link-perl
Version:  0.112-3
Uploaded: 2009-11-10 03:22:28
Description:  libfile-copy-link-perl - Perl extension for replacing a link by a 
copy of the linked file
Repository URL: 
http://mentors.debian.net/debian/pool/main/l/libfile-copy-link-perl
Section:  perl
Priority: optional
Lintian warnings: none
Lintian errors: none

http://mentors.debian.net/debian/pool/main/l/libfile-copy-link-perl/libfile-copy-link-perl_0.112-3.dsc

Regards,
-- 
Joel Roth


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



RFS: tclxml

2009-11-10 Thread Andrew O. Shadoura
Hello.

The previous maintainer on tclxml package orphaned it, while package has a bug 
rendering it completely unusable, and there's a new upstream version available 
with that bug fixed.

I'd like to take over maintainance, and I need a sponsor for that.

Package name: tclxml
Version:  3.2-1
Homepage: http://tclxml.sourceforge.net/
Author:   Steve Ball steve.b...@zveno.com
License:  BSD-style
Description:  Tcl library for XML parsing
 TclXML provides event-based parsing of XML documents.  The
 application may register callback scripts for certain document
 features, and when the parser encounters those features while parsing
 the document the callback is evaluated.

The package is lintian-clean, even with --pedantic.

The upload would fix these bugs: 519315, 540507

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/t/tclxml
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/t/tclxml/tclxml_3.2-1.dsc


Thank you.

-- 
WBR, Andrew


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


Re: RFS: luma (updated package)

2009-11-10 Thread Per
Charles Plessy wrote:
 these are excellent reasons for hijacking the package. Would you be
interested?

Yes and yes!

I was able to reach mornfall and he uploaded my changes.
He was listed with a dead email on that package, so that would have been
the reason for not showing any reaction before.

Mornfall also suggested to apply for maintainership, but first I'll try
to reach Bjorn again...


Per



signature.asc
Description: OpenPGP digital signature


Re: RFS: acx100 (updated package)

2009-11-10 Thread Patrick Matthäi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

M. van Brummelen schrieb:
 http://mentors.debian.net/debian/pool/main/e/earcandy/earcandy_0.5-1.1.dsc
 * Remove the increasing of the standards version.
 * = * Changed control-file, added python-wnck to Depend option (Closes:
 #539141)

 Better write it as:
 * Added python-wnck as a dependency.
   Closes: #539141
 Like suggested I changed the changelog comment.
 Then I did a rebuild of the package with pdebuild.
 I created a new diff file and send it to bts.
 I signed the package and uploaded it to mentors.debian.net.
 I would be happy if someone uploaded this package to fix a grave bug.

Your upload still lists:
- -Standards-Version: 3.8.1
+Standards-Version: 3.8.3


- --
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org

Comment:
Always if we think we are right,
we were maybe wrong.
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkr5YdkACgkQ2XA5inpabMc5+ACfXrkVKBDEMPkE31cMEKGz9e/3
LoMAnREoq4kO7k6PvKyXJv2mLn6rUpCW
=ezre
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



RFS: jaxodraw

2009-11-10 Thread Emilio Scattoni
Dear mentors,

I am looking for a sponsor for my package jaxodraw.

* Package name: jaxodraw
  Version : 2.0.0-1
  Upstream Author : JaxoDraw developers jaxodraw-de...@lists.sourceforge.net
* URL : http://jaxodraw.sourceforge.net/
* License : gpl
  Section : misc

It builds these binary packages:
jaxodraw   - A Java program for drawing Feynman diagrams

The package appears to be lintian clean.

My motivation for maintaining this package is: 
I decided to package because debian has given me 
so much and now I also want to give something to 
the community, and I know that is required. 
good job at all emilio.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/j/jaxodraw
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/j/jaxodraw/jaxodraw_2.0.0-1.dsc

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

Kind regards
 Emilio Scattoni


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: RFS: acx100 (updated package)

2009-11-10 Thread M. van Brummelen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Better write it as:
 * Added python-wnck as a dependency.
   Closes: #539141
 Like suggested I changed the changelog comment.
 Then I did a rebuild of the package with pdebuild.
 I created a new diff file and send it to bts.
 I signed the package and uploaded it to mentors.debian.net.
 I would be happy if someone uploaded this package to fix a grave
bug.

 Your upload still lists:
 - -Standards-Version: 3.8.1
 +Standards-Version: 3.8.3
Thanks for noticing  again *blush*
It is fixed now and uploaded it again to
http://mentors.debian.net/debian/pool/main/e/earcandy/


Regards,
Martijn van Brummelen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.9)

iEYEARECAAYFAkr5a+QACgkQ4yGTtsQpvi8PIACeNXpx9VjWqgYotCW0mz1PYV5A
6v0AnjukpM9s0/CWeXws4GA66OwWuO9T
=Ojs2
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: RFS: acx100 (updated package)

2009-11-10 Thread Patrick Matthäi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

M. van Brummelen schrieb:
 Better write it as:
 * Added python-wnck as a dependency.
   Closes: #539141
 Like suggested I changed the changelog comment.
 Then I did a rebuild of the package with pdebuild.
 I created a new diff file and send it to bts.
 I signed the package and uploaded it to mentors.debian.net.
 I would be happy if someone uploaded this package to fix a grave
 bug.
 Your upload still lists:
 - -Standards-Version: 3.8.1
 +Standards-Version: 3.8.3
 Thanks for noticing  again *blush*
 It is fixed now and uploaded it again to
 http://mentors.debian.net/debian/pool/main/e/earcandy/

Thanks, uploaded.
- --
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org

Comment:
Always if we think we are right,
we were maybe wrong.
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkr5c/YACgkQ2XA5inpabMciZQCfVn4Z8DGHmCLYan4cBwXhG9Oq
fRoAn2P0VYAH3R0nJN8ub1vl/HwQAKnJ
=UUuD
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: RFS: libqtintf4

2009-11-10 Thread Matthias Klumpp
Hello again!
I got this reply from Den Jean about the sources as statement:



[...]

Makefiles just serve to finally create calls to gcc,
these calls I wrote by hand (there was no qmake in qt2)
to more easily configure which Qt to use on the system. 
  - 2 different Qt's on a system: 
The system Qt used to be a Qt3 not so long ago (Debian stable is still
qt3/kde3)
or an old unwanted Qt4 (eg Qt 4.0 and you wanted Qt 4.4) 
  - cross compiling
The makefile would just pickup the wrong one. But for distro 
packaging, the system t is ofcourse the target Qt. 
Both methods can coexist.

I would propose to store the rpm and deb packages somewhere (fpc website?),
most distros allow the addition of package sources. 
  - one for latest stable lazarus in a stable source and 
  - an often refreshed one in a testing/cooker package source

The binding source is created by scripts, with many manual steps. 
A Qt binding is actually always alot of manual work (defining 
solutions to every exception, just read the so called typedef 
system of QtJambi or a kalyptus generator.

[...]


He will definitely nor re-write the interface using SMOKE (because it is
undocumented and not necessary. Also many applications depend on the
existing libqt4intf).
I dont's see why this package can not be included into Debian. The only
thing which blocks the inclusion is the lack of a make system like qmake,
right?
If at least one uses this software, it is relevant for Debian, I think.
Maybe they will switch to SMOKE later, but today the interface library is a
fixed standard if you want to create Qt4 applications with FPC. Do you have
comments on packaging?
Kind regards
   Matthias Klumpp


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: About software from other distribution

2009-11-10 Thread Matthew Palmer
On Wed, Nov 11, 2009 at 12:39:58AM +0800, Liang Guo wrote:
 Currently I'm using qspice, a  Simple Protocol for Independent Computing
 Environments (SPICE) client as my console to connect to KVM. qspice is a
 utility from RedHat Enterprise Linux 5.4,  and It is licensed under GNU
 GPLv2.
 
 qspice and related libraries can be downloaded from
 ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/os/SRPMS/ as
 SRPM format, may I package it for Debian ?

Sure, there doesn't appear to be an existing ITP, and the licence is fine.

- Matt


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: About software from other distribution

2009-11-10 Thread Boyd Stephen Smith Jr.
On Tuesday 10 November 2009 10:39:58 Liang Guo wrote:
 Currently I'm using qspice, a  Simple Protocol for Independent Computing
 Environments (SPICE) client as my console to connect to KVM. qspice is a
 utility from RedHat Enterprise Linux 5.4,  and It is licensed under GNU
 GPLv2.

 qspice and related libraries can be downloaded from
 ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/os/SRPMS/ as
 SRPM format, may I package it for Debian ?

It doesn't matter who upstream is, as long as the software is DFSG-free [1], 
the maintainer is willing to do the work, and it would be useful for Debian 
users [2] it can be considered for Debian.  Even if it is not DFSG-free, it 
might be allowed in non-free.

[1] In practice, patent or trademark claims could make something not DFSG-free 
even if the copyright holder uses a good license.  Or, (ala PINE) the 
copyright holder could have an odd view of a normally acceptable license.

[2] If there's already a package that fills the same role, your package might 
not be considered useful for Debian users.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/



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


Re: About software from other distribution

2009-11-10 Thread Liang Guo
Thanks, I'll working on it.

2009/11/11 Boyd Stephen Smith Jr. b...@iguanasuicide.net

 On Tuesday 10 November 2009 10:39:58 Liang Guo wrote:
  Currently I'm using qspice, a  Simple Protocol for Independent Computing
  Environments (SPICE) client as my console to connect to KVM. qspice is a
  utility from RedHat Enterprise Linux 5.4,  and It is licensed under GNU
  GPLv2.
 
  qspice and related libraries can be downloaded from
  ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/os/SRPMS/ as
  SRPM format, may I package it for Debian ?

 It doesn't matter who upstream is, as long as the software is DFSG-free
 [1],
 the maintainer is willing to do the work, and it would be useful for Debian
 users [2] it can be considered for Debian.  Even if it is not DFSG-free, it
 might be allowed in non-free.

 [1] In practice, patent or trademark claims could make something not
 DFSG-free
 even if the copyright holder uses a good license.  Or, (ala PINE) the
 copyright holder could have an odd view of a normally acceptable license.

 [2] If there's already a package that fills the same role, your package
 might
 not be considered useful for Debian users.
 --
 Boyd Stephen Smith Jr.   ,= ,-_-. =.
 b...@iguanasuicide.net   ((_/)o o(\_))
 ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
 http://iguanasuicide.net/\_/




-- 
Liang Guo
http://bluestone.cublog.cn


Re: RFS: tclxml

2009-11-10 Thread Sven Hoexter
On Tue, Nov 10, 2009 at 12:09:31PM +0200, Andrew O. Shadoura wrote:
 Hello.
 
 The previous maintainer on tclxml package orphaned it, while package has a 
 bug 
 rendering it completely unusable, and there's a new upstream version 
 available 
 with that bug fixed.
 
 I'd like to take over maintainance, and I need a sponsor for that.

Ok a few short remarks after a first look:
* There are a lot of commented out lines in debian/rules - need them or
  delete them. ;)
* Is there a reason to build-dep on tcl 8.4? Otherwise build-dep on the
  tcl-dev package.
* One should try if you can utilize the 'tcltk-depends' helper script to
  get your depends from this tool and the ${tclsh:Depends} variable.
  (maybe take a look at tclcurl or mysqltcl)
* Note in debian/copyright that you're now maintaining the package.

There is a pkg-tcltk-devel mailinglist on lists.alioth.org,
it's worth posting RFS there too so that people interested in Tcl related
packages see them.

Sven
-- 
If God passed a mic to me to speak
I'd say stay in bed, world
Sleep in peace
   [The Cardigans - 03:45: No sleep]


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: RFS: tclxml

2009-11-10 Thread Andrew O. Shadoura
Hello.

On Tuesday 10 November 2009 18:36:16 Sven Hoexter wrote:
 Ok a few short remarks after a first look:
 * There are a lot of commented out lines in debian/rules - need them or
   delete them. ;)

Ok, removed most of them.

 * Is there a reason to build-dep on tcl 8.4? Otherwise build-dep on the
   tcl-dev package.

Fixed.

 * One should try if you can utilize the 'tcltk-depends' helper script to
   get your depends from this tool and the ${tclsh:Depends} variable.

Fixed, but it worked, hmm, a little bit strange: it added a dependency on tcl, 
but haven't added a dependency on tcllib. The first is not necessary when the 
second present. But I left {$tcl:Depends} in place and just added tcllib 
manually. Not sure it's the best way, though.

 * Note in debian/copyright that you're now maintaining the package.

Added a line Current maintainer: ...

 There is a pkg-tcltk-devel mailinglist on lists.alioth.org,
 it's worth posting RFS there too so that people interested in Tcl related
 packages see them.

Ok, I'm sending RFS there too.

-- 
WBR, Andrew


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


Re: RFS: libqtintf4

2009-11-10 Thread Sune Vuorela
On 2009-11-10, Matthias Klumpp matth...@nlinux.org wrote:
 Makefiles just serve to finally create calls to gcc,

And I  think the way the gcc calls are made requires a amazing amount of
RAM for no apparant reason.

 these calls I wrote by hand (there was no qmake in qt2)
 to more easily configure which Qt to use on the system. 
   - 2 different Qt's on a system: 
   The system Qt used to be a Qt3 not so long ago (Debian stable is still
 qt3/kde3)
 or an old unwanted Qt4 (eg Qt 4.0 and you wanted Qt 4.4) 

Unimportant what's in debian stable for a package targetted unstable.
and erm. talking about Qt2?
Qt2 was released in 1999. last Qt2 release was november 2001.
Qt3 was released in october 2001, last Qt3 code changing release was
march 2007. I'm not sure why this is relevant here.

 The binding source is created by scripts, with many manual steps. 

so the shipped 'source' is not actually 'preferred form of
modification'?

 A Qt binding is actually always alot of manual work (defining 
 solutions to every exception, just read the so called typedef 
 system of QtJambi or a kalyptus generator.

kalyptus is the old perl tool used for kdebindings, where there now (for
kde4.4 is a newer and better tool) written in c++ using the same parser
as used in kdevelop and others.

 He will definitely nor re-write the interface using SMOKE (because it is
 undocumented and not necessary. Also many applications depend on the
 existing libqt4intf).
 I dont's see why this package can not be included into Debian. The only
 thing which blocks the inclusion is the lack of a make system like qmake,
 right?

The thing that blocks inclusion is a 'interested sponsor'. I currently
maintain a set of bindings, where the smoke based bindings is the one
giving me least grief. And I'm not interested in sponsoring things that
increases my headaches.

 If at least one uses this software, it is relevant for Debian, I think.
 Maybe they will switch to SMOKE later, but today the interface library is a
 fixed standard if you want to create Qt4 applications with FPC. Do you have
 comments on packaging?


I haven't gotten to the packaging yet, because there is two things from
upstream that *needs* to be fixed.
1) The moc gerenated files *needs* to be generated on build, else the 
build might break on each new qt version.
2) The build system needs to be done in a way that doesn't kill buildds
when it can be avoided.

Anyways:
Why does it build-depend on libqt4-core ?
Why do you chmod +x the compile_lib script when you use bash to run it
anyways?
How do you make sure the build fails, if the compile_lib script fails?

/Sune


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org