RFS: rkward (updated package)
Dear mentors, I have already posted an RFS for this package two weeks ago, but did not receive any reply. Is there a recommended ping interval in such cases? --- I'm looking for a new sponsor for package rkward. My current sponsor, Roland Marcus Rutschmann in CC, would like to pass sponsoring for rkward to somebody who is actively using rkward, R or related packages on a regular basis. So, in the mid-term, I'm looking for a regular sponsor of rkward. In the short-term, I'm looking for someone to upload version 0.5.1-2 of rkward. The current version in Debian unstable (and testing) is 0.5.0d-3. The package can be found at http://rkward.sourceforge.net/debian/ . The project home page is at http://rkward.sourceforge.net . Description: a KDE frontend to the R statistics language RKWard aims to become an easy to use, transparent frontend to R, a powerful system for statistical computation and graphics. Besides a convenient GUI for the most important statistical functions, future versions will also provide seamless integration with an office-suite. Regards Thomas Friedrichsmeier signature.asc Description: This is a digitally signed message part.
Re: RFS: rkward (updated package)
Le Tue, Aug 18, 2009 at 11:05:34AM +0200, Thomas Friedrichsmeier a écrit : I'm looking for a new sponsor for package rkward. My current sponsor, Roland Marcus Rutschmann in CC, would like to pass sponsoring for rkward to somebody who is actively using rkward, R or related packages on a regular basis. Dear Thomas, you are making a good job with the Debian package. How about applying for upload rights? http://wiki.debian.org/Maintainers Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: congruity
Dear mentors, I am looking for a sponsor for my package congruity. * Package name: congruity Version : 13-1 Upstream Author : Stephen Warren s-t-concorda...@wwwdotorg.org * URL : http://sourceforge.net/projects/congruity * License : GPL-3+ Section : misc It builds these binary packages: congruity - graphical utility to configure Logitech Harmony remotes The package appears to be lintian clean. The upload would fix these bugs: 512599 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/c/congruity - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/c/congruity/congruity_13-1.dsc I would be glad if someone uploaded this package for me. Kind regards Mathieu Trudel -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: pdfchain (2nd try)
Dear mentors, I am looking for a sponsor for my package pdfchain. * Package name: pdfchain Version : 0.123-1 Upstream Author : Martin Singer (m_pow...@users.sourceforge.net) * URL : http://pdfchain.sourceforge.net/ * License : GPL-3+ Programming Lang: C++ Section : text It builds these binary packages: pdfchain - a graphical user interface for the PDF Tool Kit pdfchain a is GUI for pdftk, written in C++ with GTKmm. The package appears to be lintian clean. The upload would fix these bugs: 539866 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/pdfchain - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/pdfchain/pdfchain_0.123-1.dsc I've used the existing ubuntu-ppa package ( https://launchpad.net/pdfchain ) from Günther Bauer as template, but reworked it almost completely. Additionally, I've looked through the Fedora package. Since my last request 2 weeks ago, I've added a README.source and updated to debian-policy 3.8.3. I would be glad if someone uploaded this package for me. Kind regards Johann Felix Soden -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: jabberd14 (updated package) (fix a FTBFS)
Miguel Landaeta mig...@miguel.cc (18/08/2009): I am looking for a sponsor for the new version 1.6.1.1-3 of package jabberd14. The upload would fix this bug: 542131. Hi, please keep the submitter Cc'd when replying to some bug, or you're not going to receive any feedback, except in rare cases. (And I'd have sponsored you right away. ;)) Mraw, KiBi. signature.asc Description: Digital signature
RFS: nautilus-scripts-manager (2nd try)
Dear mentors, I am looking for a sponsor for my package nautilus-scripts-manager. * Package name: nautilus-scripts-manager Version : 1.2-1 Upstream Author : Pietro Battiston (me) * URL : http://www.pietrobattiston.it/nautilus-scripts-manager * License : GPL-3 Section : gnome It builds these binary packages: nautilus-scripts-manager - simple tool for nautilus scripts management The package is lintian clean. The upload would fix these bugs: 536878 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/n/nautilus-scripts-manager - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/n/nautilus-scripts-manager/nautilus-scripts-manager_1.2-1.dsc I would be glad if someone uploaded this package for me. Some background, for those who may be interested: - I wrote a relatively complex nautilus script ([1]) that I plan to package.[2] My goal was (mainly) to help people who don't know how to use/don't want to use the terminal (I do indeed use it regularly ;-) ... - ...but I realized that currently people /have/ to use the terminal to enable nautilus scripts (since it must be done on a user base by symlinking). - There is a tool to enable/disable them (nautilus-script-manager - notice mine has an s which prevents the clashing) which is packaged only in Ubuntu, is really very very simple... and still has no GUI. Moreover, it doesn't help changing/localizing/organizing the names of the scripts in the menu. - The non-userfriendliness of the whole system has led to some crazy choices in the Ubuntu packaging of nautilus scripts (see [3]) (notice all such packages currently depend on the old nautilus-script-manager, and I plan to ask to replace it with my nautilus-scripts-manager, at least as Recommends). That's why I wrote and packaged a scripts manager that I see as a (much better) replacement to Ubuntu's nautilus-script-manager, and as a way to cleanly introduce user-friendliness in Nautilus scripts (and hence Nautilus scripts in Debian). Notice pygtk is not a dependence for the app itself, but if it is not installed then the menu icon fails without warnings; that's why I put python-gtk2 in Depends. (anyway, if you have nautilus and python installed, you probably have pygtk, and if you don't, it's not such a huge dependence) My usual sponsor, Piotr Ożarowsk, already helped me fixing few minor problems upstream and in the packaging, but is currently too busy to sponsor nautilus-script-manager. thanks to anyone who read so far Pietro Battiston [1]: http://poisson.phc.unipi.it/~battiston/gueic/doku.php?id=gallery_uploader [2]: (but it will Recommends nautilus-scripts-manager, that's why I still don't ask for sponsorship) [3]: http://bugs.launchpad.net/ubuntu/+source/audio-convert/+bug/130055 signature.asc Description: Questa è una parte del messaggio firmata digitalmente
writing watch file for libproj4
Hi there, I am working on the libproj4 package: http://dl.maptools.org/dl/libproj4/ How would one write the watch file for it ? I tried: $ cat debian/watch version=3 http://dl.maptools.org/dl/libproj4/ lbp4_(.*)S\.tar\.gz It gives $ uscan --verbose --force-download -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: http://dl.maptools.org/dl/libproj4/ lbp4_(.*)S\.tar\.gz uscan warning: In debian/watch, no matching hrefs for watch line http://dl.maptools.org/dl/libproj4/ lbp4_(.*)S\.tar\.gz -- Scan finished Thanks, -- Mathieu signature.asc Description: OpenPGP digital signature
Re: writing watch file for libproj4
Talk to upstream and get them to fix their website. Alternatively, write a redirector website that downloads the page, parses it and regurgitates some sane HTML. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: writing watch file for libproj4
On Tue, Aug 18, 2009 at 5:16 PM, Paul Wisep...@debian.org wrote: Talk to upstream and get them to fix their website. Alternatively, write a redirector website that downloads the page, parses it and regurgitates some sane HTML. :( I thought I would be able to use the php script directly from uscan: http://dl.maptools.org/dl/libproj4/index.php Does anyone knows how to use links to download that from a simple shell script ? Thanks, -- Mathieu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: writing watch file for libproj4
On Tue, Aug 18, 2009 at 11:30 PM, Mathieu Malaterre mathieu.malate...@gmail.com wrote: I thought I would be able to use the php script directly from uscan: http://dl.maptools.org/dl/libproj4/index.php Does anyone knows how to use links to download that from a simple shell script ? Please just get upstream to fix the page. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: writing watch file for libproj4
On Tue, Aug 18, 2009 at 5:34 PM, Paul Wisep...@debian.org wrote: On Tue, Aug 18, 2009 at 11:30 PM, Mathieu Malaterre mathieu.malate...@gmail.com wrote: I thought I would be able to use the php script directly from uscan: http://dl.maptools.org/dl/libproj4/index.php Does anyone knows how to use links to download that from a simple shell script ? Please just get upstream to fix the page. Just for reference. It looks like debian simply rename libproj4 into libproj, from http://packages.debian.org/sid/libproj-dev -- Mathieu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: libsockets++
Dear mentors, I am looking for a sponsor for my package libsockets++. * Package name: libsockets++ Version : 2.3.5-2 Upstream Author : Anders Hedstrom gry...@alhem.net * URL : http://www.alhem.net/Sockets/ * License : GPL2 + OpenSSL Exemption Section : libs It builds these binary packages: libsockets++-dev - C++ sockets class library - development files libsockets++2 - C++ sockets class library The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libsockets++ - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libsockets++/libsockets++_2.3.5-2.dsc I would be glad if someone uploaded this package for me. Kind regards Leinier Cruz Salfran signature.asc Description: Esta parte del mensaje está firmada digitalmente
why?
why is so hard to find a sponsor? I have a package online since 2 weeks ago, I sent 3 RFS and I have found no sponsor yet. why signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: why?
Hi, why is so hard to find a sponsor? I have a package online since 2 weeks ago, I sent 3 RFS and I have found no sponsor yet. why It is most a lack of sponsor's time. Reviewing and testing packages (especially libraries) is not that easy and tend to consume significant amount of people's time. By the way, I briefly had a look at your package' upstream web site and docs, which look promising (sorry, lack of time for more), and I wonder how it compares to skstream, which is already available in Debian. I hope you will find a reviewer and hopefully a sponsor. Thanks for your time preparing this package, anyway. -- pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
icon/icon-generic in mime options
Hello all, Probably a stupid question, but anyway, I have a question regarding mime support. In my package I use the icon-generic field, but this field has only be included in shared-mime-info version 0.40. Should I ask debian-devel if it is ok to pre-depend on shared-mime-info (= 0.40) or is this way out of scope for that? Older versions of shared-mime-info quit with an error on unknown fields. See for the relevance [1] With kind regard, Paul [1] http://bugs.debian.org/541168 signature.asc Description: OpenPGP digital signature
RFS: nsis-2.45-1 [attn: pabs]
Hi,
Paul Wise (also known as pabs) offered me to take over the maintenance of the
Nullsoft Scriptable Install System (NSIS).
NSIS is an open source system to create Windows installers and it is licensed
under the zlib/libpng license.
The maintenance of the NSIS Debian package is handled via the collab-maint
subversion repository:
svn+ssh://svn.debian.org/svn/collab-maint/ext-maint/nsis/trunk respectively
http://svn.debian.org/wsvn/collab-maint/ext-maint/nsis/trunk/?op=log
I would propose the lastest revision (rev 14037) for upload.
I ensured via pbuilder that all dependent packages are listed. Lintian reports
the following known warnings and error:
W: nsis: non-standard-dir-in-usr usr/i586-mingw32msvc/
W: nsis: file-in-unusual-dir usr/i586-mingw32msvc/include/nsis/api.h
W: nsis: file-in-unusual-dir usr/i586-mingw32msvc/include/nsis/pluginapi.h
W: nsis: file-in-unusual-dir usr/i586-mingw32msvc/lib/nsis/libpluginapi.a
- These warnings are there because mingw32 targeted libs and header
files are searched for in the usr/i586-mingw32msvc directory.
E: nsis: embedded-zlib ./usr/bin/makensis
N: 1 tag overridden (1 warning)
- Upstream embeds a modified copy of zlib.
I updated to the latest Debian policy version (3.8.3) and checked the
items mentioned in /usr/share/doc/debian-policy/upgrading-checklist.txt.gz.
The minimum requirement of scons changed from version 0.96.93 to 0.98. The
package allows to be built either via gcc-mingw32 or mingw32. An access
violation in the Math plugin is fixed via a patch (also reported upstream) that
is incorporated to the original source by quilt.
I built the test installers via fakeroot debian/rules build and zipped the
resulting executables placed in the .test directory. Thereafter I unzipped
the test installers and run them on a Windows machine. I did that for both
gcc-mingw32 and mingw32.
Test results:
The waplugin.exe installer could not be completed because WinAmp is not
installed on my Windows machine. The StartMenu Test.exe would require that you
locate the file makensis.exe on your PC. I just created a dummy file for it
and thereafter I could sucessfully complete this test. The nsExec Test.exe
tries to execute the makenis.exe file using the path specified via ${NSISDIR}.
However the NSISDIR variable on Debian Linux specifies a UNIX path that is
not available on Windows. Therefore I replaced ${NSISDIR} with the real
path on Windows and rebuilt the nsExec Test.exe installer. This installer
performed the test as expected. All other test installer worked just fine.
Please let me know if I missed anything preventing the upload of this
package.
Thanks in advance,
Thomas
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: why?
Leinier Cruz Salfran wrote: I have a package online since 2 weeks ago, I sent 3 RFS and I have found no sponsor yet. why That was about when DebConf was ending. People were busy travelling home and catching up on their other lives I expect. Colin -- Colin Tuckley | +44(0)1223 293413 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Good advice is something a man gives when he is too old to set a bad example. - La Rochefoucaud -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: why?
Hi Dne Tue, 18 Aug 2009 01:46:04 + Leinier Cruz Salfran salfra...@ipigto.rimed.cu napsal(a): why is so hard to find a sponsor? I have a package online since 2 weeks ago, I sent 3 RFS and I have found no sponsor yet. why People are busy :-). Lot of DD's have been on DebConf, taking some vacation around it and now we try to keep up with piles of emails that ended up in our mailboxes. And if the package does not look enough attractive, you need to be patient. -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: RFS: libsockets++
Hi Dne Tue, 18 Aug 2009 01:44:08 + Leinier Cruz Salfran salfra...@ipigto.rimed.cu napsal(a): The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libsockets++ - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libsockets++/libsockets++_2.3.5-2.dsc Just quick review: - you add change license stuff in debian diff without any explanation - debian/rules contains lot of commented out things, it looks like this package is ideal candidate for minimal dh based debian/rules - please use patch system instead of directly patching sources - how did you choose soname for the library? what if upstream decides for different numbering later? - lintian -I --pendantic: I: libsockets++ source: debian-watch-file-is-missing I: libsockets++ source: binary-control-field-duplicates-source field section in package libsockets++2 P: libsockets++ source: direct-changes-in-diff-but-no-patch-system Ajp13Socket.cpp and 117 more -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: why?
On Tue, Aug 18, 2009 at 01:46:04AM +, Leinier Cruz Salfran wrote: why is so hard to find a sponsor? I have a package online since 2 weeks ago, I sent 3 RFS and I have found no sponsor yet. why The debian-mentors FAQ (http://people.debian.org/~mpalmer/debian-mentors_FAQ.html) has some hints on improving your chances of finding a sponsor. The chances are nobody has found your package interesting enough to take the (considerable) time required to check it and upload it. - Matt -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: why?
On 2009-08-18, Leinier Cruz Salfran salfra...@ipigto.rimed.cu wrote: --=-+HFkoxaqb4DFPsQ5uB2y Content-Type: text/plain Content-Transfer-Encoding: quoted-printable why is so hard to find a sponsor? I have a package online since 2 weeks ago, I sent 3 RFS and I have found no sponsor yet. why It depends very much on the kind of package. Wether it is something that is catchy or not. Wether it is something a debian developer finds useful or not. For example, I would be very reluctant to sponsor a first package of a person that was a new library without any application using it, whereas a interesting kde application might easier catch my eye. /Sune -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Requests to sponsor new library packages (was: why?)
Sune Vuorela nos...@vuorela.dk writes: For example, I would be very reluctant to sponsor a first package of a person that was a new library without any application using it, whereas a interesting kde application might easier catch my eye. That's interesting, thank you for that perspective. What do you propose, then, for a maintainer who wants to get a new package into Debian, but that package requires one or more separately-packaged libraries that *also* need to be sponsored into Debian before the “interesting” package can go in? -- \ “… one of the main causes of the fall of the Roman Empire was | `\that, lacking zero, they had no way to indicate successful | _o__) termination of their C programs.” —Robert Firth | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Requests to sponsor new library packages (was: why?)
On Wed, Aug 19, 2009 at 10:11:12AM +1000, Ben Finney wrote: Sune Vuorela nos...@vuorela.dk writes: For example, I would be very reluctant to sponsor a first package of a person that was a new library without any application using it, whereas a interesting kde application might easier catch my eye. That's interesting, thank you for that perspective. What do you propose, then, for a maintainer who wants to get a new package into Debian, but that package requires one or more separately-packaged libraries that *also* need to be sponsored into Debian before the “interesting” package can go in? I've had to do this with Perl modules once - I wanted to package a particular module, but it had a chain of dependencies that were not packaged yet. What I did was file a series of ITP bugs, stating my intentions clearly - first for the target package, saying This module also needs So-And-So and This-And-That, which will be ITP'd separately, and then for the dependencies, each ITP stating This module is needed for the packaging of So-And-So (ITP #NNN). A couple of days later, helpful people from the Debian Perl Group did the last part that I'd missed - made the ITP bugs block one another in the proper order. Thus, anyone who reads the library bug sees it is needed for ITP #NNN, and anyone who reads the original ITP bug sees blocked by #NNN and knows why it hasn't been RFS'd yet. G'luck, Peter -- Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 I've heard that this sentence is a rumor. pgpeCahtl8XsC.pgp Description: PGP signature
Re: Requests to sponsor new library packages (was: why?)
2009/8/19 Peter Pentchev r...@ringlet.net: I've had to do this with Perl modules once - I wanted to package a particular module, but it had a chain of dependencies that were not packaged yet. What I did was file a series of ITP bugs, stating my intentions clearly - first for the target package, saying This module also needs So-And-So and This-And-That, which will be ITP'd separately, and then for the dependencies, each ITP stating This module is needed for the packaging of So-And-So (ITP #NNN). A couple of days later, helpful people from the Debian Perl Group did the last part that I'd missed - made the ITP bugs block one another in the proper order. Thus, anyone who reads the library bug sees it is needed for ITP #NNN, and anyone who reads the original ITP bug sees blocked by #NNN and knows why it hasn't been RFS'd yet. For those who are filing lots of ITPs like this, a reminder of the devref recommendations about new packages: http://lists.debian.org/debian-project/2009/08/msg00301.html -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
