Re: RFS: blankon (updated package)
Hello, I jut reviewed the lastest version on your package on mentors (2.0-4). - It builds cleanly, and there is only one lintian warning : P: gnome-icon-theme-blankon: copyright-refers-to-symlink-license usr/share/common-licenses/GPL Because your copyright file states or any later version, you should instead mention /usr/share/common-licenses/GPL-2. - You should collapse changelog entries. Basically, end users do not need to know that you went through all this, a single entry is enough. - +nmuN version numbers are for native packages only. Here, you should use a '-N.N' version number (here, as you released a new upstream version, 2.0-0.1 so that it sorts before 2.0-1). I am not sure that it has been put in the policy, but see #542288 for details. Cheers, -- Etienne Millon signature.asc Description: Digital signature
RFS: git (updated package)
Dear mentors, I am looking for a sponsor for the new version 1:1.7.2.3-2.2 of the package git. It builds these binary packages: git- fast, scalable, distributed revision control system git-all- fast, scalable, distributed revision control system (all subpacka git-arch - fast, scalable, distributed revision control system (arch interop git-core - fast, scalable, distributed revision control system (obsolete) git-cvs- fast, scalable, distributed revision control system (cvs interope git-daemon-run - fast, scalable, distributed revision control system (git-daemon s git-doc- fast, scalable, distributed revision control system (documentatio git-email - fast, scalable, distributed revision control system (email add-on git-gui- fast, scalable, distributed revision control system (GUI) git-svn- fast, scalable, distributed revision control system (svn interope gitk - fast, scalable, distributed revision control system (revision tre gitweb - fast, scalable, distributed revision control system (web interfac The upload would fix these bugs: 607248 There is the usual list of complaints from lintian, all known and mostly harmless. This is a non-maintainer upload to fix a security bug in preparation for squeeze, so it didn't seem like the right time to fix them. Gerrit is on vacation (see debian-private) so again I am counting on you. The package can be found at the usual place. - git://repo.or.cz/debian-git/jrn.git squeeze-urgent - dget http://mentors.debian.net/debian/pool/main/g/git/git_1.7.2.3-2.2.dsc I would be happy if someone finds time to look it over. Kind regards, Jonathan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101216085055.ga31...@burratino
Re: RFS: pgfouine (updated package) (second try)
Hi Luis, On Wed, Dec 15, 2010 at 10:40:42PM -0500, Luis Uribe wrote: [...] I just check _again_ with lintian and the package it's clean. Well, check again... $ lintian -iI --pedantic pgfouine_1.2-2_amd64.changes P: pgfouine source: source-contains-cvs-control-dir rpm-specific/patches/CVS N: N:The upstream source contains a CVS directory. It was most likely N:included by accident since CVS directories usually don't belong in N:releases. When packaging a CVS snapshot, export from CVS rather than use N:a checkout. If an upstream release tarball contains CVS directories, you N:usually should report this as a bug to upstream. N: N:Severity: pedantic, Certainty: certain N: P: pgfouine source: source-contains-cvs-control-dir rpm-specific/sources/CVS P: pgfouine source: source-contains-cvs-control-dir rpm-specific/CVS P: pgfouine source: source-contains-cvs-control-dir include/listeners/error/CVS P: pgfouine source: source-contains-cvs-control-dir include/listeners/CVS P: pgfouine source: source-contains-cvs-control-dir include/listeners/query/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/web/css/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/web/js/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/web/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/reports/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/geshi/docs/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/geshi/geshi/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/geshi/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/artichow/php4/inc/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/artichow/php4/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/artichow/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/artichow/patterns/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/artichow/font/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/artichow/php5/inc/CVS P: pgfouine source: source-contains-cvs-control-dir include/reporting/artichow/php5/CVS P: pgfouine source: source-contains-cvs-control-dir include/lib/CVS P: pgfouine source: source-contains-cvs-control-dir include/postgresql/vacuum/listeners/CVS P: pgfouine source: source-contains-cvs-control-dir include/postgresql/vacuum/reporting/reports/CVS P: pgfouine source: source-contains-cvs-control-dir include/postgresql/vacuum/reporting/CVS P: pgfouine source: source-contains-cvs-control-dir include/postgresql/vacuum/parsers/CVS P: pgfouine source: source-contains-cvs-control-dir include/postgresql/vacuum/objects/CVS P: pgfouine source: source-contains-cvs-control-dir include/postgresql/vacuum/CVS P: pgfouine source: source-contains-cvs-control-dir include/postgresql/vacuum/lines/CVS P: pgfouine source: source-contains-cvs-control-dir include/postgresql/parsers/CVS P: pgfouine source: source-contains-cvs-control-dir include/postgresql/CVS P: pgfouine source: source-contains-cvs-control-dir include/postgresql/lines/CVS P: pgfouine source: source-contains-cvs-control-dir include/CVS P: pgfouine source: source-contains-cvs-control-dir CVS W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/CVS/ N: N:The package contains a control directory for a version control system. N:It was most likely installed by accident, since version control N:directories usually don't belong in packages. N: N:Severity: normal, Certainty: certain N: W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/lib/CVS/ W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/listeners/CVS/ W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/listeners/error/CVS/ W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/listeners/query/CVS/ W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/postgresql/CVS/ W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/postgresql/lines/CVS/ W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/postgresql/parsers/CVS/ W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/postgresql/vacuum/CVS/ W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/postgresql/vacuum/lines/CVS/ W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/postgresql/vacuum/listeners/CVS/ W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/postgresql/vacuum/objects/CVS/ W: pgfouine: package-contains-vcs-control-dir usr/share/pgfouine/include/postgresql/vacuum/parsers/CVS/ W: pgfouine: package-contains-vcs-control-dir
RFS: LeechCraft
Dear mentors! I'm looking for a sponsor for the leechcraft_0.4.55.72. This is my first try to include this package in Debian. Short description: LeechCraft is a free modular Internet client application. LeechCraft allows to browse the web, read RSS/Atom feeds, download files via BitTorrent, HTTP, FTP and DC, automatically stream, download or play podcasts and other media files and much more. Features can be easily added via plugins that can be integrated with each other with no effert while staying abstract from the exact implementation. Binary packages: leechcraft - Core executable of LeechCraft leechcraft-dbg - Debug symbols for LeechCraft leechcraft-dev - Files required for developmen for LeechCraft. leechcraft-full - Full LeechCraft installation leechcraft-iconset-oxygen - Oxygen-based iconset for LeechCraft leechcraft-iconset-tango - Iconset based on the Tango project for LeechCraft leechcraft-libplugininterface0.3.0 - Common library for LeechCraft leechcraft-libxmlsettingsdialog0.3.0 - Dynamic settings dialog builder for LeechCraft leechcraft-plugin-aggregator - RSS/Atom feed reader for LeechCraft leechcraft-plugin-anhero - Crash handler for LeechCraft leechcraft-plugin-auscrie - Screenshooter for LeechCraft leechcraft-plugin-azoth - XMPP messenger for LeechCraft leechcraft-plugin-chatter - IRC client for LeechCraft leechcraft-plugin-cstp - HTTP client for LeechCraft leechcraft-plugin-dbusmanager - D-Bus side of LeechCraft leechcraft-plugin-deadlyrics - Song lyrics finder for LeechCraft leechcraft-plugin-historyholder - History keeper for LeechCraft leechcraft-plugin-kinotify - Fancy notifications for LeechCraft leechcraft-plugin-lcftp - FTP client for LeechCraft leechcraft-plugin-lmp - Media Previewer for LeechCraft leechcraft-plugin-networkmonitor - Network monitor for LeechCraft leechcraft-plugin-newlife - Settings importer for LeechCraft leechcraft-plugin-poshuku - Web browser for LeechCraft leechcraft-plugin-poshuku-cleanweb - Ad filter for Web browser for LeechCraft leechcraft-plugin-poshuku-filescheme - file://-schemes support for the Web browser for LeechCraft leechcraft-plugin-poshuku-fua - Fake user agent plugin for Web browser for LeechCraft leechcraft-plugin-poshuku-wyfv - Flash video replacer for Web browser for LeechCraft leechcraft-plugin-secman - Security Manager plugin for LeechCraft leechcraft-plugin-secman-simplestorage - Simple storage backend for SecMan leechcraft-plugin-seekthru - OpenSearch-support plugin for LeechCraft leechcraft-plugin-shellopen - Support for opening files with external apps in LeechCraft leechcraft-plugin-summary - A quick summary of what's going on in LeechCraft leechcraft-plugin-tabpp - Tabbing experience enhancer for LeechCraft leechcraft-plugin-vgrabber - vkontakte.ru plugin for LeechCraft dget http://mentors.debian.net/debian/pool/main/l/leechcraft/leechcraft_0.4.55.72.dsc Thanks, -- Daniel Guzanoff
Re: RFS: git (updated package)
Hi Dne Thu, 16 Dec 2010 02:50:56 -0600 Jonathan Nieder jrnie...@gmail.com napsal(a): I am looking for a sponsor for the new version 1:1.7.2.3-2.2 of the package git. It builds these binary packages: git- fast, scalable, distributed revision control system git-all- fast, scalable, distributed revision control system (all subpacka git-arch - fast, scalable, distributed revision control system (arch interop git-core - fast, scalable, distributed revision control system (obsolete) git-cvs- fast, scalable, distributed revision control system (cvs interope git-daemon-run - fast, scalable, distributed revision control system (git-daemon s git-doc- fast, scalable, distributed revision control system (documentatio git-email - fast, scalable, distributed revision control system (email add-on git-gui- fast, scalable, distributed revision control system (GUI) git-svn- fast, scalable, distributed revision control system (svn interope gitk - fast, scalable, distributed revision control system (revision tre gitweb - fast, scalable, distributed revision control system (web interfac The upload would fix these bugs: 607248 There is the usual list of complaints from lintian, all known and mostly harmless. This is a non-maintainer upload to fix a security bug in preparation for squeeze, so it didn't seem like the right time to fix them. Gerrit is on vacation (see debian-private) so again I am counting on you. The package can be found at the usual place. - git://repo.or.cz/debian-git/jrn.git squeeze-urgent - dget http://mentors.debian.net/debian/pool/main/g/git/git_1.7.2.3-2.2.dsc I would be happy if someone finds time to look it over. Looks good, uploaded. -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: RFS: LeechCraft
Hi, Dear mentors! I'm looking for a sponsor for the leechcraft_0.4.55.72. This is my first try to include this package in Debian. I don't have time to do a proper review, but here are some comments: · This should not be a native package. · There is no need to repeat the Homepage and Section field for every binary package. The one for the source package is used by default. · Is it necessary to have extra packages for every plugin? If they are not large and don't have (large) additional dependencies, it might make more sense to just keep them in the main application package. · Some files are licensed as GPL-2 (at least lcnp/src/*). This causes an additional problem: GPL-2 without the or any later clause is incompatible with GPL-3. · What is the copyright and license for iconsets/crystalz/*? The License.txt file contains the Artistic License, but does not mention that the files are licensed under these terms. Neither are any copyright holders given. · In addition to these, even more licenses are used. There are also additional copyright holders. This should be documented in debian/copyright. · Why is the package limited to the i386 and amd64 architectures? · You build-depend on libcurl4-openssl-dev. I suspect this means the program is linked (possibly indirectly) against openssl. Note that OpenSSL's license is not GPL-compatible. · Please don't start the packages' short description in debian/control with a capital letter (unless the word is always capitalized). Regards, Ansgar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8739pyx9px@marvin.43-1.org
Re: RFS: LeechCraft
Il giorno gio, 16/12/2010 alle 12.17 +0300, Daniel Guzanoff ha scritto: Short description: LeechCraft is a free modular Internet client application. LeechCraft allows to browse the web, read RSS/Atom feeds, download files via BitTorrent, HTTP, FTP and DC, automatically stream, download or play podcasts and other media files and much more. Features can be easily added via plugins that can be integrated with each other with no effert while staying abstract from the exact -effert +effort (in the package too) (maybe, also -with no +with minimal) bye Pietro -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1292498767.5505.7.ca...@voubian.casa
Re: RFS: LeechCraft
Thanks for comments. We will work with the technical defects and license. Why is the package limited to the i386 and amd64 architectures? This application isn't tested on other architectures. I was going to add new architectures after testing these. Is this a bad idea? Is it necessary to have extra packages for every plugin? If they are not large and don't have (large) additional dependencies, it might make more sense to just keep them in the main application package. Many of plugins implement app-standartized interfaces. Some plugins implement more than one interface, some of plugins implement the same interface and are interchangable. It will be difficult for user to configure and organize plugins if they all contained in one package. I thought it would be more logical when interface == virtual_package.
Re: RFS: LeechCraft
Hi Dne Thu, 16 Dec 2010 15:32:39 +0300 Daniel Guzanoff melkor...@gmail.com napsal(a): Thanks for comments. We will work with the technical defects and license. Why is the package limited to the i386 and amd64 architectures? This application isn't tested on other architectures. I was going to add new architectures after testing these. Is this a bad idea? The usual way is to build for all architectures unless there is really some platform specific code. Testing is welcome, but it's hard to get access to all Debian architectures (especially if you are not DD). And if something breaks, you will get a bug report :-). -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: RFS: LeechCraft
You build-depend on libcurl4-openssl-dev. I suspect this means the program is linked (possibly indirectly) against openssl. Note that OpenSSL's license is not GPL-compatible. This library is linked with plugin (leechcraft-plugin-cftp), not main app. Plugins are released under LGPLv3. Is it okay?
Re: Time of a package to be processed by FTP-masters
Hi, On Wednesday 27 October 2010 16:24:38 Alexander Reichle-Schmehl wrote: 2.1- If so, what's would be the time appropriate to ask? 1 month for 1 Month sounds reasonable to me under normal circumstances. Two months have gone by, and no feedback. Is there any kind of alternative for these cases, a la Ubuntu PPA? I don't think so, from what I could gather... Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201012161708.48233.manuel.montez...@gmail.com
Re: Time of a package to be processed by FTP-masters
On 12/16/2010 11:08 AM, Manuel A. Fernandez Montecelo wrote: On Wednesday 27 October 2010 16:24:38 Alexander Reichle-Schmehl wrote: 2.1- If so, what's would be the time appropriate to ask? 1 month for 1 Month sounds reasonable to me under normal circumstances. Two months have gone by, and no feedback. We're in a freeze. Poking the FTPmasters will not be useful, unless there's a reason your package should get reviewed before everything else in the queue. As has been said before, the developer will be notified if there's a problem with his package. Is there any kind of alternative for these cases, a la Ubuntu PPA? I don't think so, from what I could gather... Yes, you can set up your own repository. See http://wiki.debian.org/HowToSetupADebianRepository for details. -- ╒═╕ │Luke Faraone ╭Debian / Ubuntu Developer╮│ │http://luke.faraone.cc╰Sugar Labs, Systems Admin╯│ │PGP: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506 │ ╘═╛ signature.asc Description: OpenPGP digital signature
Re: RFR/RFS: openvpn-auth-radius (new package, fixes retitled RFP)
Dear mentors, Please CC me in a reply, since I am not subscribed to the list. Thanks to Paul Wise for reviewing the source package. On Tue, Dec 14, 2010 at 04:58:23PM +0100, Helmut Grohne wrote: I am looking for a sponsor for my package openvpn-auth-radius. * Package name: openvpn-auth-radius Version : 2.1-1 Version 2.1-2 now. Upstream Author : Ralf Luebben * URL : http://www.nongnu.org/radiusplugin/ * License : GPL-2 Section : net It builds these binary packages: openvpn-auth-radius - OpenVPN RADIUS authentication module openvpn-auth-radius-dbg - debugging symbols for openvpn-plugin-radius The package appears to be lintian clean. It is now lintian --pedantic -I -E clean. The upload would fix these bugs: 556460 My motivation for maintaining this package is: The Cygnus Networks GmbH is using this software on Debian and Debian does not provide a package with this or similar functionality. Thus we packaged it for our own needs. Since we expect to use it for quite a bit of time, maintaining the package seems like a good fit. A few notes on the software: This package will have low popcon score. To be useful it requires a functional openvpn and radius setup. Most users probably want to run stable, so the package is created with backporting in mind. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/o/openvpn-auth-radius - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/o/openvpn-auth-radius/openvpn-auth-radius_2.1-1.dsc Now: dget http://mentors.debian.net/debian/pool/main/o/openvpn-auth-radius/openvpn-auth-radius_2.1-2.dsc I would be glad if someone uploaded or review this package for me. Version 2.1-2 incorporates most of Paul's suggestions. Here are the ones I intentionally left out: 1) I do not use override_foo rules, because they are not available for lenny without backporting. 2) I do not use source format 3.0, for easier backporting (potentially targeting etch). 3) uscan reports a newer version 2.1-beta1. I can prepare experimental packages if there is interest. Further comments are welcome as well as uploading the package to sid. However I will not respond to any mails during the remainder of this year. Helmut -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101216171756.ga24...@buero.cygnusnet.de
Re: Time of a package to be processed by FTP-masters
On Thursday 16 December 2010 18:28:33 Luke Faraone wrote: On 12/16/2010 11:08 AM, Manuel A. Fernandez Montecelo wrote: On Wednesday 27 October 2010 16:24:38 Alexander Reichle-Schmehl wrote: 2.1- If so, what's would be the time appropriate to ask? 1 month for 1 Month sounds reasonable to me under normal circumstances. Two months have gone by, and no feedback. We're in a freeze. Poking the FTPmasters will not be useful, unless there's a reason your package should get reviewed before everything else in the queue. As has been said before, the developer will be notified if there's a problem with his package. I won't poke them to review my package, as if it was the most important thing in the universe, before anything else. I just wanted to ask about its status and possible review because my package is already towards the front of the queue since a few weeks ago, and new packages behind mine are being approved constantly, and mine isn't. Why is this important? In this lapse of time of 2 months, my package (1.7.1 version) was already obsoleted (by 1.7.2, with a lot of bug fixes). So I was wondering if it's worth to invest time in creating a package for 1.7.2, or if the effort might be futile because the package won't be reviewed and approved under any circumstance until freeze is over. By that time 1.7.3 might be out, and my effort wasted again, so I would choose not to create the 1.7.2 package at this moment. I think that these are pretty reasonable things that a contributor can ask, to decide what to do with his free time, but maybe I am wrong. In any case, having unresolved doubts about this, the voluntary effort that I could put forward in the next few weeks will be spent elsewhere, where the effort will hopefully be more appreciated and won't be wasted for sure. Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201012161931.57837.manuel.montez...@gmail.com
Re: RFS: LeechCraft
Daniel Guzanoff wrote: Ansgar Burchardt wrote: You build-depend on libcurl4-openssl-dev. I suspect this means the program is linked (possibly indirectly) against openssl. Note that OpenSSL's license is not GPL-compatible. This library is linked with plugin (leechcraft-plugin-cftp), not main app. Plugins are released under LGPLv3. Is it okay? Difficult question. You might want to ask debian-legal or get the license of the main program clarified to allow it. Here's what the FSF has to say[1]: | Q: If a program released under the GPL uses plug-ins, what are the | requirements for the licenses of a plug-in? | | A: It depends on how the program invokes its plug-ins. [...] | If the program dynamically links plug-ins, and they make function | calls to each other and share data structures, we believe they form | a single program, [...] | This means | the plug-ins must be released under the GPL or a GPL-compatible free | software license, and that the terms of the GPL must be followed | when those plug-ins are distributed. Also see [2] concerning the OpenSSL/GPL incompatibility. This is perhaps a strange edge case because the interfaces provided by libcurl-openssl and libcurl-gnutls are not all that different. Luckily, that gives an easy way out: does the plugin work when built against libcurl4-gnutls-dev? Hope that helps, Jonathan [1] http://www.gnu.org/licenses/gpl-faq.html#GPLAndPlugins [2] http://people.gnome.org/~markmc/openssl-and-the-gpl.html -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101216205558.ga4...@burratino
Re: Time of a package to be processed by FTP-masters
On Thu, Dec 16, 2010 at 07:31:56PM +0100, Manuel A. Fernandez Montecelo wrote: Why is this important? In this lapse of time of 2 months, my package (1.7.1 version) was already obsoleted (by 1.7.2, with a lot of bug fixes). So I was wondering if it's worth to invest time in creating a package for 1.7.2, or if the effort might be futile because the package won't be reviewed and approved under any circumstance until freeze is over. By that time 1.7.3 might be out, and my effort wasted again, so I would choose not to create the 1.7.2 package at this moment. Freeze is a trying time for lots of bits of Debian and definitely for the ftp masters. The problem is your question about when they can look at your package revolves around when with the next version of Debian be released, and we all know the answer to that is when it's ready. If there is no real changes between the versions, I'd wait until the one sitting in the queue has made it through. If it is something important I'd update the pending package. It can be frustrating because you've done all this work and then.. nothing, but look on the bright side; you're not one of those poor ftp masters! - Craig -- Craig Small VK2XLZhttp://www.enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101216215118.ga17...@enc.com.au
RFS: 9menu (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.8-5 of my package 9menu. It builds these binary packages: 9menu - Creates X menus from the shell The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/9/9menu - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/9/9menu/9menu_1.8-5.dsc Fix comment from DACA[1] new service [1]:http://qa.debian.org/daca/cppcheck/sid/9menu_1.8-4.html I would be glad if someone uploaded this package for me. Kind regards daniel echeverry -- Epsilon http://www.rinconinformatico.net http://www.fitnessdeportes.com http://www.dragonjar.org Linux user: #477840 Debian user -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinzzdk3a+0sj6jwwmp9tktiqsay73p=hqq00...@mail.gmail.com
Re: Time of a package to be processed by FTP-masters
On 12/16/2010 01:31 PM, Manuel A. Fernandez Montecelo wrote: We're in a freeze. Poking the FTPmasters will not be useful, unless there's a reason your package should get reviewed before everything else in the queue. As has been said before, the developer will be notified if there's a problem with his package. I won't poke them to review my package, as if it was the most important thing in the universe, before anything else. I just wanted to ask about its status and possible review because my package is already towards the front of the queue since a few weeks ago, and new packages behind mine are being approved constantly, and mine isn't. From what I understand, the release team has asked the FTP Masters to avoid accepting new binary packages which introduce a transition, as Ogre does.¹ I think that's reason that your package is sitting in the queue. ¹: Correct me if I'm wrong about that, I have not inspected the package in NEW deeply -- ╒═╕ │Luke Faraone ╭Debian / Ubuntu Developer╮│ │http://luke.faraone.cc╰Sugar Labs, Systems Admin╯│ │PGP: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506 │ ╘═╛ signature.asc Description: OpenPGP digital signature
Re: Time of a package to be processed by FTP-masters
On Fri, Dec 17, 2010 at 2:31 AM, Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: I won't poke them to review my package, as if it was the most important thing in the universe, before anything else. I just wanted to ask about its status and possible review because my package is already towards the front of the queue since a few weeks ago, and new packages behind mine are being approved constantly, and mine isn't. Just so you know, NEW is not processed in strictly FIFO order. Why is this important? In this lapse of time of 2 months, my package (1.7.1 version) was already obsoleted (by 1.7.2, with a lot of bug fixes). So I was wondering if it's worth to invest time in creating a package for 1.7.2, or if the effort might be futile because the package won't be reviewed and approved under any circumstance until freeze is over. By that time 1.7.3 might be out, and my effort wasted again, so I would choose not to create the 1.7.2 package at this moment. There is no reason not to have the latest and greatest version in NEW, the ftpmasters will only review the latest version available in NEW. I think that these are pretty reasonable things that a contributor can ask, to decide what to do with his free time, but maybe I am wrong. In any case, having unresolved doubts about this, the voluntary effort that I could put forward in the next few weeks will be spent elsewhere, where the effort will hopefully be more appreciated and won't be wasted for sure. The ftpmasters not reviewing your package does not mean that your work is not appreciated and is a waste of time, on the contrary! Please try to think a bit more positively :) -- 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 Archive: http://lists.debian.org/aanlktik=6m8x0vc6ea292ratcbjwr5kdcb-2d8ylw...@mail.gmail.com
