Re: Request For Sponsor: Bug 731282

2013-12-04 Thread Andrei POPESCU
On Mi, 04 dec 13, 09:25:25, ChrisofBristol (gmail) wrote:
 I'm told that I need to file a separate RFS bug against the 
 sponsorship-requests pseudo-package.

JFTR, that was me, while triaging bugs filed against unknown packages.

 I have spent hours reading the documentation and I thought that I had 
 done this, I am totally mystified about what else I need to do and 
 how. Has anyone got any helpful suggestions please?

Let me try to explain in more detail how software gets packaged for 
Debian. Let's assume there is some interesting software that you want to 
see in Debian, in this case DIY Layout Creator. Let's assume the Debian 
package name would be diylc.

If you want to see this software included in Debian you must first 
consider whether you want to be a Maintainer and do the packaging 
yourself or you just want to propose the package for inclusion.

In the first case you can start by filing an ITP (Intent to Package) bug 
against the wnpp package. This is made in order to prevent double work 
(i.e. someone else working on the same software without knowing you do 
as well) and sometimes to track progress (if it takes too long).

Now you can start actually working on the package. Have you done this? 

You initial bugreport only mentions there is a package at some site, 
which might suggest you don't even want to maintain it yourself. In this 
case please retitle the ITP bug to RFP (Request for Package), to signal 
that you don't want to maintain it, but it would be nice for Debian to 
have it. Maybe somebody will be interested in maintaining it for Debian.

If I'm wrong and you do intend to be Maintainer you should first prepare 
a package and only then start looking for a sponsor (i.e. someone to 
upload the package for you to Debian, at least until you gain the 
necessary rights to do so yourself).

If something in my above explanations is not clear please follow-up on 
debian-mentors (not debian-user). Reply-To is set accordingly.

 By the way this suggest below from the documentation isn't any help
 as reportbug errors and so does the alternative suggested in the
 error message.

It is not helpful at all to say reportbug errors without providing the 
error message :(

Hope this explains,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature


Re: Request For Sponsor: Bug 731282

2013-12-04 Thread ChrisofBristol (gmail)

Andrei

I think I'll probably just give up - I feel like I'm banging my head 
against a brick wall. I don't think I want to spend a week or so 
studying reams of documentation learning what all this is about - I 
learned how to make a (compiled) deb package and then how to create a 
repository and make it available in less time than I have already spent 
trying to disentangle the documentation to understand what is required, 
I got the (source) deb package put onto GetDeb with one email message.


I didn't bother posting the error message because I didn't want to spend 
hours getting involved in a debate about why the suggestions in an error 
message caused another error message with a piece of software that I 
would only use once. That was not what I came her for - it would be more 
banging my head against a brick wall.


Anyway, I appreciate your attempts to help - thank you.

Chris


On 04/12/13 10:18, Andrei POPESCU wrote:

On Mi, 04 dec 13, 09:25:25, ChrisofBristol (gmail) wrote:

I'm told that I need to file a separate RFS bug against the
sponsorship-requests pseudo-package.

JFTR, that was me, while triaging bugs filed against unknown packages.


I have spent hours reading the documentation and I thought that I had
done this, I am totally mystified about what else I need to do and
how. Has anyone got any helpful suggestions please?

Let me try to explain in more detail how software gets packaged for
Debian. Let's assume there is some interesting software that you want to
see in Debian, in this case DIY Layout Creator. Let's assume the Debian
package name would be diylc.

If you want to see this software included in Debian you must first
consider whether you want to be a Maintainer and do the packaging
yourself or you just want to propose the package for inclusion.

In the first case you can start by filing an ITP (Intent to Package) bug
against the wnpp package. This is made in order to prevent double work
(i.e. someone else working on the same software without knowing you do
as well) and sometimes to track progress (if it takes too long).

Now you can start actually working on the package. Have you done this?

You initial bugreport only mentions there is a package at some site,
which might suggest you don't even want to maintain it yourself. In this
case please retitle the ITP bug to RFP (Request for Package), to signal
that you don't want to maintain it, but it would be nice for Debian to
have it. Maybe somebody will be interested in maintaining it for Debian.

If I'm wrong and you do intend to be Maintainer you should first prepare
a package and only then start looking for a sponsor (i.e. someone to
upload the package for you to Debian, at least until you gain the
necessary rights to do so yourself).

If something in my above explanations is not clear please follow-up on
debian-mentors (not debian-user). Reply-To is set accordingly.


By the way this suggest below from the documentation isn't any help
as reportbug errors and so does the alternative suggested in the
error message.

It is not helpful at all to say reportbug errors without providing the
error message :(

Hope this explains,
Andrei



--
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/529f0522.3010...@gmail.com



RFS: dict-freedict-*

2013-12-04 Thread Sebastian Humenda
Hello,

after the FreeDict packages got orphaned, I as a member of the FreeDict project
decided to step up to package the packages for Debian, otherwise there would be
no dictionary databases from FreeDict in the archives.

The package seems to be lintian-clean with --pedantic.

Currently, there are 78 imported dictionaries resulting in 79 packages and a
source archive. To provide *one* download link, I made up a tarball with all
required files:
  http://crustulus.de/downloads/freedict.tar.bz2
The source can be obtained using git:
  git clone ssh://git.debian.org/git/pkg-freedict/pkg-freedict.git

For any questions, please feel free to contact me off-list or at the packaging
group's mailing list at pkg-freedict-disc...@lists.alioth.debian.org.

Thanks!
Sebastian
-- 
Web: http://www.crustulus.de | Blog: 
http://www.crustulus.de/cgi-bin/blog.cgi?de-0
Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html
FreeDict: Free multilingual dictionary databases - http://www.freedict.org


signature.asc
Description: Digital signature


Bug#731036: RFS: think-rotate/3.0-1

2013-12-04 Thread Henrique de Moraes Holschuh
On Tue, 03 Dec 2013, Martin Ueding wrote:
  Mostly because the package would not contain the
  majority of the stand-alone thinkpad-specific tools and utils (such as tpb,
  thinkbat, thinkfan, etc).
 
 That is the problem, it is just screen rotation and docking. “-scripts”
 sounds like some assorted scripts, and does not feel like it is claiming
 to be complete like “-utils” would.

think-scripts (or thinkpad-scripts) is fine, IMHO.

However, please do be aware that we already have some thinkpad-specific
scripts or functionality in packages:

acpi-fakekey  (mostly to reroute input events into legacy acpi-like events)
acpi-support

So it is best to make sure there is no duplication, etc.

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
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/20131204124556.gf17...@khazad-dum.debian.net



Bug#731337: RFS: xlsxwriter/0.5.1-1

2013-12-04 Thread Sylvain Pineau

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package xlsxwriter

Package name: xlsxwriter
Version : 0.5.1-1
Upstream Author : John McNamara jmcnam...@cpan.org
URL : https://github.com/jmcnamara/XlsxWriter
License : BSD
Section : python

It builds those binary packages:

python-xlsxwriter - Python module for creating Excel XLSX files.
python3-xlsxwriter - Python 3 module for creating Excel XLSX files.

To access further information about this package, please visit the following 
URL:

http://mentors.debian.net/package/xlsxwriter


Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/x/xlsxwriter/xlsxwriter_0.5.1-1.dsc

Regards,
Sylvain Pineau


--
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/529f2611.7010...@canonical.com



Bug#731341: RFS: xlsxwriter/0.5.1-1 [ITP]

2013-12-04 Thread Sylvain Pineau

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package xlsxwriter

Package name: xlsxwriter
Version : 0.5.1-1
Upstream Author : John McNamara jmcnam...@cpan.org
URL : https://github.com/jmcnamara/XlsxWriter
License : BSD
Section : python

It builds those binary packages:

python-xlsxwriter - Python module for creating Excel XLSX files.
python3-xlsxwriter - Python 3 module for creating Excel XLSX files.

To access further information about this package, please visit the following 
URL:

http://mentors.debian.net/package/xlsxwriter


Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/x/xlsxwriter/xlsxwriter_0.5.1-1.dsc

Regards,
Sylvain Pineau


--
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/529f28dc.6060...@canonical.com



Bug#728510: RFS: secpanel/1:0.6.1-2 (second try)

2013-12-04 Thread Daniel Echeverry
Hi!

Please, Could some DD have a look at my package?

Really, thank you very much!

Regards
Daniel

-- 
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
Linux user: #477840
Debian user
Software libre http://www.rinconinformatico.net


Bug#730623: marked as done (RFS: nauty/2.5r6+ds-1 [ITA] -- library for graph automorphisms)

2013-12-04 Thread Debian Bug Tracking System
Your message dated Wed, 04 Dec 2013 16:27:00 +
with message-id e1vofhw-mg...@quantz.debian.org
and subject line closing RFS: nauty/2.5r6+ds-1 [ITA] -- library for graph 
automorphisms
has caused the Debian Bug report #730623,
regarding RFS: nauty/2.5r6+ds-1 [ITA] -- library for graph automorphisms
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
730623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: sponsorship-requests
Severity: normal

Dearr mentors,

 I am looking for a sponsor for my package nauty

 * Package name: nauty
   Version : 2.5r6+ds-1
   Upstream Author : Brendan McKay b...@cs.anu.edu.au
 Adolfo Piperno pipe...@di.uniroma1.it
 * URL : http://pallini.di.uniroma1.it
 * License : ad hoc
   Section : non-free/math

 It builds those binary packages:

   libnauty2  - library for graph automorphisms -- library package
   libnauty2-dbg - library for graph automorphisms -- debug symbols package
   libnauty2-dev - library for graph automorphisms -- development package
   nauty - library for graph automorphisms -- interface and tools
   nauty-doc  - library for graph automorphisms -- user guide

 To access further information about this package, please visit the following 
URL:

   http://mentors.debian.net/package/nauty


 Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/non-free/n/nauty/nauty_2.5r6+ds-1.dsc

 More information about hello can be obtained from http://www.example.com.

 Changes since the last upload:

   nauty (2.5r6+ds-1) unstable; urgency=low

   * New upstream version.
   * New maintainer (Closes: #725407).
   * Debianization:
 - debian/copyright:
   - refresh;
   - bump format to DEP-5 .
 - debian/control:
   - introduce the debug symbols package libnauty-dbg;
   - gather documentations (user guide and technical notes)
 into the dedicated package nauty-doc;
   - Description fields, refresh;
   - debhelper build-dep, bump to = 9;
   - Standards Version, bump to 3.9.4;
   - Vcs-* headers, canonicalize.
 - debian/patches/ patches:
   - autotoolize from scratch to permit a full dh integration
 (Closes: #727929);
   - prepend nauty- to the name of the nauty tools;
   - bump format to DEP-3.
 - debian/watch, update;
 - debian/repack, repack script to clean up and gain weight;
 - debian/rules:
   - fully integrate dh;
   - get-orig-source uscan based target which downloads the currently
 packaged upstream tarball and repacks it;
   - default target which basically queries package status with uscan
 -- output in DEHS format;
   - debian/ man pages, now generated on fly by help2man through the
 autotools machinery.
   - debian/*:
 - propagate SONAME `current version' index change due to new ABI;
 - introduce `version script' files to consolidate the ABI;
 - explicit multi-arch support.
   * Gather headers into a dedicated folder named after the package.
   * Provide a library for each nauty `variant' wrt upstream source tarball.
   * Provide pkg-config support (only for the nauty `automatic variant').
   * Provide an ad hoc script to build (and clean) the upstream source examples.
   * Minor fixes, enhancements and full autotools support have been submitted to
 the upstream maintainers.

   -- Jerome Benoit calcu...@rezozer.net  Tue, 26 Nov 2013 20:27:57 +

Regards,
Jerome BENOIT
---End Message---
---BeginMessage---
Package nauty has been removed from mentors.---End Message---