Bug#761643: RFS: libstrophe/0.8.6-1 [ITP]

2014-09-16 Thread Dariusz Dwornikowski 
> Hi Dariusz,
>  
> somehow the d/copyright is still not matching 100% to the code...
> At least for many files there is a "Copyright (c) 2005-2009 Collecta,
> Inc" which is not in d/copyright. So probably this copyright owner is
> missing for the * rule. Can you please fix it.

Yes I fixed this. 

> 
> Also, I'm missing see a proof for the "or later" option of the GPL, as
> it would have to be explictly stated by upstream, see GPL-3 §14. So
> write GPL-3 or ask upstream for clarification.

Fixed, yes they have GPL-3 not later.
> 
> (Please wrap your comment, there is also two empty lines at the end of
> the file and one empty line in the middle. Those are nitpicks, though) 

Wrapped. 

-- 
Dariusz Dwornikowski, 
  Institute of Computing Science, Poznań University of Technology
  www.cs.put.poznan.pl/ddwornikowski/  
  room 2.7.2 BTiCW | tel. +48 61 665 29 41


signature.asc
Description: Digital signature

Bug#761482: RFS: argyll/1.6.3-1 [ITA]

2014-09-16 Thread Jörg Frings-Fürst 
Hello Stephen,
Hello Bastien,


Am Montag, den 15.09.2014, 22:59 +0200 schrieb Stephen Kitt:
> Hi Bastien,
> 
> On Mon, 15 Sep 2014 20:28:54 +0200, Bastien ROUCARIES
>  wrote:
> > Le 14 sept. 2014 16:21, "Stephen Kitt"  a écrit :
> > > Upgrading argyll does reveal a real problem though... Given that you're
> > > shipping all the documentation in argyll-doc, and symlinking from the
> > other
> > > two packages, you need to replace the old directories with symlinks, using
> > > something like this in argyll's postinst:
> > 
> > Ar please use dpkg-maintainer-script-helper
> 
Bastien thanks for your comment.


> Ah right, thanks, the last time I checked dpkg-maintscript-helper didn't
> handle this case.
> 
> Jörg, it's dpkg-maintscript-helper dir_to_symlink...

I have create / added the dpkg-maintscript-helper calls to 
*.(postinst|preinst|postrm)

The package is uploaded to mentors[1]. 

Stephen can you remove it from the new queue and upload again?

[...]
> Regards,
> 
> Stephen


CU
Jörg


[1] http://mentors.debian.net/debian/pool/main/a/argyll/argyll_1.6.3-1.dsc


-- 
pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8  EBCB 422B 44B0 BE58 1B6E
pgp Key: BE581B6E
CAcert Key S/N: 0E:D4:56

Jörg Frings-Fürst
D-54526 Niederkail

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net







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

Bug#761636: RFS: raceintospace/1.1+dfsg1-1 [ITP]

2014-09-16 Thread Dariusz Dwornikowski 
On 16.09.14 01:05:05, Vincent Cheng wrote:
> Hi Dariusz,
> 
> On Mon, Sep 15, 2014 at 2:31 AM, Dariusz Dwornikowski
>  wrote:
> > Package: sponsorship-requests
> > Severity: wishlist
> >
> >   Dear mentors,
> >
> >   I am looking for a sponsor for my package "raceintospace"
> >
> >  * Package name: raceintospace
> >Version : 1.1+dfsg1-1
> >Upstream Author : Michael K McCarty 
> >  Pace Willisson 
> >  Krzysztof Kosciuszkiewicz 
> >  Will Glynn 
> >  * URL : http://www.raceintospace.org/
> >  * License : GPL-2+
> >Section : games
> >
> >   It builds those binary packages:
> >
> > raceintospace - free software version of the Liftoff! board game
> >  raceintospace-data - free software version of the Liftoff! board game - 
> > data file
> >
> >   To access further information about this package, please visit the 
> > following URL:
> >
> >   http://mentors.debian.net/package/raceintospace
> >
> >   Alternatively, one can download the package with dget using this command:
> >
> > dget -x 
> > http://mentors.debian.net/debian/pool/main/r/raceintospace/raceintospace_1.1+dfsg1-1.dsc
> >
> >   or go directly to the VCS:
> >   http://anonscm.debian.org/cgit/pkg-games/raceintospace.git
> >
> >   More information about raceintospace can be obtained from 
> > http://www.raceintospace.org/
> >
> >
> >   This is the initial release:
> >
> >   * Initial release (Closes: #748321)
> 
> I recall reviewing this several months back; I haven't looked at it
> again yet, but I remember that there were a number of issues with the
> package at the time that were left unfixed, most notably that the
> build system tries to fetch remote resources during the build itself.
> Has this since been fixed?

It does not try to fetch anymore if the dependencies are fulffiled.
Now, with the new patch they are. I could completely patch the system
to even not try when there are no deps presents (some weirdo archs
maybe ).

I also filled d/copyright completely and now it works with physfs 2.0,
which is in Debian. 

-- 
Dariusz Dwornikowski, 
  Institute of Computing Science, Poznań University of Technology
  www.cs.put.poznan.pl/ddwornikowski/  
  room 2.7.2 BTiCW | tel. +48 61 665 29 41


signature.asc
Description: Digital signature

Bug#761636: RFS: raceintospace/1.1+dfsg1-1 [ITP]

2014-09-16 Thread Vincent Cheng 
Hi Dariusz,

On Mon, Sep 15, 2014 at 2:31 AM, Dariusz Dwornikowski
 wrote:
> Package: sponsorship-requests
> Severity: wishlist
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "raceintospace"
>
>  * Package name: raceintospace
>Version : 1.1+dfsg1-1
>Upstream Author : Michael K McCarty 
>  Pace Willisson 
>  Krzysztof Kosciuszkiewicz 
>  Will Glynn 
>  * URL : http://www.raceintospace.org/
>  * License : GPL-2+
>Section : games
>
>   It builds those binary packages:
>
> raceintospace - free software version of the Liftoff! board game
>  raceintospace-data - free software version of the Liftoff! board game - data 
> file
>
>   To access further information about this package, please visit the 
> following URL:
>
>   http://mentors.debian.net/package/raceintospace
>
>   Alternatively, one can download the package with dget using this command:
>
> dget -x 
> http://mentors.debian.net/debian/pool/main/r/raceintospace/raceintospace_1.1+dfsg1-1.dsc
>
>   or go directly to the VCS:
>   http://anonscm.debian.org/cgit/pkg-games/raceintospace.git
>
>   More information about raceintospace can be obtained from 
> http://www.raceintospace.org/
>
>
>   This is the initial release:
>
>   * Initial release (Closes: #748321)

I recall reviewing this several months back; I haven't looked at it
again yet, but I remember that there were a number of issues with the
package at the time that were left unfixed, most notably that the
build system tries to fetch remote resources during the build itself.
Has this since been fixed?

Regards,
Vincent


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CACZd_tBAAm6xG6+nAb9B1_1_zOQtuQsER3LyeJ5LD6=9qgs...@mail.gmail.com

Bug#761645: marked as done (RFS: filezilla/3.9.0.5-0.1 -- Full-featured graphical FTP/FTPS/SFTP client)

2014-09-16 Thread Debian Bug Tracking System 
Your message dated Tue, 16 Sep 2014 00:53:20 -0700
with message-id 

and subject line Re: Bug#761645: RFS: filezilla/3.9.0.5-1 -- Full-featured 
graphical FTP/FTPS/SFTP client
has caused the Debian Bug report #761645,
regarding RFS: filezilla/3.9.0.5-0.1 -- Full-featured graphical FTP/FTPS/SFTP 
client
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.)


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

Dear mentors,

I am looking for a sponsor for filezilla 3.9.0.5-1.

The package is maintained in collab-main/git:
 http://anonscm.debian.org/gitweb/?p=collab-maint/filezilla.git

Changes since the last upload:

filezilla (3.9.0.5-1) unstable; urgency=medium

  * New upstream release
  * Acknowledging previous NMUs, thanks

 -- Adrien Cunin   Sun, 14 Sep 2014 12:11:33 +0200

Thanks,

-- 
Adrien Cunin aka Adri2000
Ubuntu MOTU Developer
Debian Contributor



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi Adrien,

On Mon, Sep 15, 2014 at 4:29 AM, Adrien Cunin  wrote:
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for filezilla 3.9.0.5-1.
>
> The package is maintained in collab-main/git:
>  http://anonscm.debian.org/gitweb/?p=collab-maint/filezilla.git
>
> Changes since the last upload:
>
> filezilla (3.9.0.5-1) unstable; urgency=medium
>
>   * New upstream release
>   * Acknowledging previous NMUs, thanks
>
>  -- Adrien Cunin   Sun, 14 Sep 2014 12:11:33 +0200

Built, signed, and uploaded; thanks for your contribution to Debian!

Regards,
Vincent--- End Message ---

Bug#761636: RFS: raceintospace/1.1+dfsg1-1 [ITP]

2014-09-16 Thread Vincent Cheng 
On Tue, Sep 16, 2014 at 1:08 AM, Dariusz Dwornikowski
 wrote:
> On 16.09.14 01:05:05, Vincent Cheng wrote:
>> Hi Dariusz,
>>
>> On Mon, Sep 15, 2014 at 2:31 AM, Dariusz Dwornikowski
>>  wrote:
>> > Package: sponsorship-requests
>> > Severity: wishlist
>> >
>> >   Dear mentors,
>> >
>> >   I am looking for a sponsor for my package "raceintospace"
>> >
>> >  * Package name: raceintospace
>> >Version : 1.1+dfsg1-1
>> >Upstream Author : Michael K McCarty 
>> >  Pace Willisson 
>> >  Krzysztof Kosciuszkiewicz 
>> >  Will Glynn 
>> >  * URL : http://www.raceintospace.org/
>> >  * License : GPL-2+
>> >Section : games
>> >
>> >   It builds those binary packages:
>> >
>> > raceintospace - free software version of the Liftoff! board game
>> >  raceintospace-data - free software version of the Liftoff! board game - 
>> > data file
>> >
>> >   To access further information about this package, please visit the 
>> > following URL:
>> >
>> >   http://mentors.debian.net/package/raceintospace
>> >
>> >   Alternatively, one can download the package with dget using this command:
>> >
>> > dget -x 
>> > http://mentors.debian.net/debian/pool/main/r/raceintospace/raceintospace_1.1+dfsg1-1.dsc
>> >
>> >   or go directly to the VCS:
>> >   http://anonscm.debian.org/cgit/pkg-games/raceintospace.git
>> >
>> >   More information about raceintospace can be obtained from 
>> > http://www.raceintospace.org/
>> >
>> >
>> >   This is the initial release:
>> >
>> >   * Initial release (Closes: #748321)
>>
>> I recall reviewing this several months back; I haven't looked at it
>> again yet, but I remember that there were a number of issues with the
>> package at the time that were left unfixed, most notably that the
>> build system tries to fetch remote resources during the build itself.
>> Has this since been fixed?
>
> It does not try to fetch anymore if the dependencies are fulffiled.
> Now, with the new patch they are. I could completely patch the system
> to even not try when there are no deps presents (some weirdo archs
> maybe ).

Yes, the build system should _never_ try to fetch any remote resource.
If build deps are unsatisfied, the result should be a FTBFS, not an
attempt to fetch the missing deps during the build itself; patch the
build system if you must in order to ensure this.

Regards,
Vincent


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CACZd_tBz_1oWs=LpdkkfN_KO_=cebahb7mqvcc4km65yq+4...@mail.gmail.com

Seqan used to build on kfreebsd but does not any more

2014-09-16 Thread Andreas Tille 
Hi,

the package seqan currently in testing previously built on all
architectures except sparc (even on kfreebsd-*)[1].  I needed to
fix some onrelated build issue and now the recent build log on
kfreebsd[2] says:

...
cd /«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-kfreebsd-gnu/core/demos && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/demo_file_speed.dir/link.txt 
--verbose=1
/usr/bin/c++   -g -O2 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2
-Wl,-z,relro CMakeFiles/demo_file_speed.dir/file_speed.cpp.o  -o 
../../bin/demo_file_speed  -lz 
CMakeFiles/demo_file_speed.dir/file_speed.cpp.o: In function `waitFor':
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:893: 
undefined reference to `aio_suspend64'
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:894: 
undefined reference to `aio_return64'
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:900: 
undefined reference to `aio_error64'
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:900: 
undefined reference to `aio_error64'
CMakeFiles/demo_file_speed.dir/file_speed.cpp.o: In function 
`asyncWriteAt':
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:842: 
undefined reference to `aio_write64'
CMakeFiles/demo_file_speed.dir/file_speed.cpp.o: In function `waitFor':
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:939: 
undefined reference to `aio_error64'
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:947: 
undefined reference to `aio_return64'
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:954: 
undefined reference to `aio_error64'
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:935: 
undefined reference to `aio_suspend64'
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:939: 
undefined reference to `aio_error64'
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:947: 
undefined reference to `aio_return64'
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:954: 
undefined reference to `aio_error64'
CMakeFiles/demo_file_speed.dir/file_speed.cpp.o: In function 
`asyncWriteAt':
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:842: 
undefined reference to `aio_write64'
CMakeFiles/demo_file_speed.dir/file_speed.cpp.o: In function `asyncReadAt':
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:797: 
undefined reference to `aio_read64'
CMakeFiles/demo_file_speed.dir/file_speed.cpp.o: In function `cancel':
/«BUILDDIR»/seqan-1.4.1+dfsg/core/include/seqan/system/file_async.h:994: 
undefined reference to `aio_cancel64'
collect2: error: ld returned 1 exit status
make[4]: *** [bin/demo_file_speed] Error 1
core/demos/CMakeFiles/demo_file_speed.dir/build.make:89: recipe for target 
'bin/demo_file_speed' failed
make[4]: Leaving directory 
'/«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-kfreebsd-gnu'
CMakeFiles/Makefile2:2435: recipe for target 
'core/demos/CMakeFiles/demo_file_speed.dir/all' failed
make[3]: *** [core/demos/CMakeFiles/demo_file_speed.dir/all] Error 2
make[3]: Leaving directory 
'/«BUILDDIR»/seqan-1.4.1+dfsg/obj-x86_64-kfreebsd-gnu'
make[2]: *** [all] Error 2


I'm wondering how this change was triggered and how to fix this.  I'm
specifically interested in kfreebsd-amd64 but fixing it on both
architectures would be a plus.

Kind regards

  Andreas.

[1] https://buildd.debian.org/status/package.php?p=seqan&suite=jessie
[2] 
https://buildd.debian.org/status/fetch.php?pkg=seqan&arch=kfreebsd-amd64&ver=1.4.1%2Bdfsg-2&stamp=1409680867

-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140916093546.gi4...@an3as.eu

Re: Seqan used to build on kfreebsd but does not any more

2014-09-16 Thread Steven Chamberlain 
Hi,

On 16/09/14 10:35, Andreas Tille wrote:
> the package seqan currently in testing previously built on all
> architectures except sparc (even on kfreebsd-*)[1].  I needed to
> fix some onrelated build issue and now the recent build log on
> kfreebsd[2] says:

> [1] https://buildd.debian.org/status/package.php?p=seqan&suite=jessie

Huh?  According to this it has _never_ built on kfreebsd:
https://buildd.debian.org/status/logs.php?pkg=seqan&arch=kfreebsd-amd64

(it is not marked as out-of-date either so is not a blocker for
migration, it only waits for the mips build)

I'd say the "jessie" view is misleading or, broken.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54180794.2030...@pyro.eu.org

buildd.debian.org/status/ broken (Was: Seqan used to build on kfreebsd but does not any more)

2014-09-16 Thread Andreas Tille 
Hi,

On Tue, Sep 16, 2014 at 10:49:08AM +0100, Steven Chamberlain wrote:
> 
> On 16/09/14 10:35, Andreas Tille wrote:
> > the package seqan currently in testing previously built on all
> > architectures except sparc (even on kfreebsd-*)[1].  I needed to
> > fix some onrelated build issue and now the recent build log on
> > kfreebsd[2] says:
> 
> > [1] https://buildd.debian.org/status/package.php?p=seqan&suite=jessie
> 
> Huh?  According to this it has _never_ built on kfreebsd:
> https://buildd.debian.org/status/logs.php?pkg=seqan&arch=kfreebsd-amd64
> 
> (it is not marked as out-of-date either so is not a blocker for
> migration, it only waits for the mips build)
> 
> I'd say the "jessie" view is misleading or, broken.

As Steven pointed out the jessie view seems to be broken.  I'm
forwarding this to debian-qa for further inspection.

Kind regards

Andreas. 

-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140916111909.gk4...@an3as.eu

Re: Seqan used to build on kfreebsd but does not any more

2014-09-16 Thread Andreas Tille 
Hi Steven,

On Tue, Sep 16, 2014 at 10:49:08AM +0100, Steven Chamberlain wrote:
> > [1] https://buildd.debian.org/status/package.php?p=seqan&suite=jessie
> 
> Huh?  According to this it has _never_ built on kfreebsd:
> https://buildd.debian.org/status/logs.php?pkg=seqan&arch=kfreebsd-amd64
> 
> (it is not marked as out-of-date either so is not a blocker for
> migration, it only waits for the mips build)
> 
> I'd say the "jessie" view is misleading or, broken.

Ahh, OK (fowarded to Debian QA list).  Any chance to fix the problem
anyway?  May be upstream could be interested?
 
Kind regards

   Andreas.

-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140916112051.gl4...@an3as.eu

Bug#757966: RFS: lutris/0.3.4-1 [ITP]

2014-09-16 Thread Eriberto 
Hi wRAR,

You need analyze the package to understand my words. Pierre, the
maintainer, already understood and replied me.

Thanks for your help and attention.

Cheers,

Eriberto


2014-09-16 0:11 GMT-03:00 Andrey Rahmatullin :
> On Mon, Sep 15, 2014 at 05:22:10PM -0300, Eriberto wrote:
>> To put a package in Debian you must remove the debian/ directory from
>> upstream source code and generate a new tarball. So, you must start a
>> new Debian package. You can use some ideas from upstream, not clone
>> the code only.
> I see several wrong statements here. Can you elaborate?
>
> --
> WBR, wRAR


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cap+dxjdttnqdrdahcl4pzzoy2mvlkeer_banyst6ouqnhy1...@mail.gmail.com

Bug#757966: RFS: lutris/0.3.4-1 [ITP]

2014-09-16 Thread Eriberto 
Hi Pierre,

Thanks for your fast reply. I will try help you.

1. d/changelog: please, use 'Initial release' instead of 'source
package automatically created by stdeb 0.6.0+git'.

2. d/control:
 - Change the Priority from extra to optional[1].
 - The upstream INSTALL file says that you must use Python 2.7.
So, change from 'python (<< 2.8), python (>= 2.7)' to 'python' in
Build-Depends and remove from Depends. The X-Python-Version field is
used to notify the system about the correct version to be used.
 - The same problem with X-Python-Version. Use 'X-Python-Version:
2.7'. More details here[2].
 - Please, create a VCS to control your debian/ versions. You can
use github or other. So, add the Vcs-Browser and Vcs-{Git|Svn|Cvs} to
d/control. You can see an example here[3].
 - In short description, is right the afirmation 'any video game'?
Is it real?
 - In long description, remove extra spaces in last three lines. I
saw in upstream site (GitHub) a list about some games that can be used
with lutris. To improve your long description and allow more people to
find your package via apt-cache search, I suggest add a list of
possible games.

[1] https://www.debian.org/doc/manuals/maint-guide/dreq.en.html#control
[2] 
https://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions
[3] 
http://sources.debian.net/src/yowsup/0.0~git20140314.938cf1-1/debian/control/

3. d/copyright: you should use the 1.0 format. Please, read this short
document[4] and fix this file.

[4] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

Other comment is that you must to list all upstream authors and
licenses in d/copyright.

4. d/lutris.6: I asked: "Where I can find the 'info' manual of the
game?", because your manpage says: "The full documentation for lutris
is maintained as a Texinfo manual.  If the info and lutris programs
are properly installed at your site, the command 'info lutris' should
give you access to the complete manual."

I would appreciate it if you put an example of installation of the
game in manpage (the complete line command).

5. d/rules:
- Please, remove all comments.
- Why you are installing a changelog from Ubuntu (made by
upstream)? Please, remove it and the file ChangeLog.

6. Add a d/README.source file saying about the changes need in
upstream tarball to generate the package.

Thanks for your work. I will wait your package.

Cheers,

Eriberto


2014-09-15 19:52 GMT-03:00 Pierre Rudloff :
> Hello,
>
> Sorry, I thought it was better to reuse an existing package.
> I have rebuilt it from scratch: http://mentors.debian.net/package/lutris
>
> Here are the answers to your questions:
> 1. It does not use it anymore.
> 2. I have set it to 9, which seems to be the current level.
> 3. It isn't a game but a game manager, so isn't a man page enough?
> 4. It has one now.
> 5. I think it should be in main, as it complies with the DFSG and does not
> rely on non-free packages.
>
> Regards,
>
>
> Le 15/09/2014 22:22, Eriberto a écrit :
>
>> Hi Pierre,
>>
>> I checked your package and you are using/cloning the original upstream
>> packaging.
>>
>> To put a package in Debian you must remove the debian/ directory from
>> upstream source code and generate a new tarball. So, you must start a
>> new Debian package. You can use some ideas from upstream, not clone
>> the code only.
>>
>> I would like you to answer some questions:
>>
>> 1. Why the package is using CDBS?
>>
>> 2. What is the current DH level?
>>
>> 3. Where I can find the 'info' manual of the game?
>>
>> 4. Why the package hasn't a X-Python-Version field?
>>
>> 5. Your package must be main, contrib or non-free? Why?
>>
>> If your want to put a package in Debian, you must have sufficient
>> skill to maintain this package and solve bugs etc. I suggest you look
>> at 'Debian New Maintainers' Guide'[1] and, after this, review your
>> package. If you have doubts, you can ask for help in Debian Mentors
>> List[2].
>>
>> I wish a good work for you.
>>
>> Cheers,
>>
>> Eriberto
>>
>> [1] https://www.debian.org/doc/manuals/maint-guide/
>> [2] https://lists.debian.org/debian-mentors/
>>
>>> 2014-08-12 17:04 GMT-03:00 Pierre Rudloff :



 Package: sponsorship-requests
 Severity: wishlist

 Dear mentors,

 I am looking for a sponsor for my package "lutris"

 * Package name: lutris
   Version : 0.3.4-1
   Upstream Author : Mathieu Comandon 
 * URL : https://lutris.net/
 * License : GPLv3
   Section : games

 It builds those binary packages:

  lutris - Install and play any video game easily

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

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

Bug#761482: RFS: argyll/1.6.3-1 [ITA]

2014-09-16 Thread Stephen Kitt 
Hi Jörg,

On Tue, 16 Sep 2014 09:26:04 +0200, Jörg Frings-Fürst
 wrote:
> Am Montag, den 15.09.2014, 22:59 +0200 schrieb Stephen Kitt:
> > Ah right, thanks, the last time I checked dpkg-maintscript-helper didn't
> > handle this case.
> > 
> > Jörg, it's dpkg-maintscript-helper dir_to_symlink...
> 
> I have create / added the dpkg-maintscript-helper calls to 
> *.(postinst|preinst|postrm)
> 
> The package is uploaded to mentors[1]. 
> 
> Stephen can you remove it from the new queue and upload again?

I've got the package removed from the new queue, but I noticed a couple more
changes I'd like to see in the package:
* rm_conffile should be replaced with dpkg-maintscript-helper too (and the
  latter added in the required scripts)
* icc/*.icm and ref/*.icm are public domain and should be listed as such in
  debian/copyright (see ref/ReadMe.txt and the ICM metadata)

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#757966: RFS: lutris/0.3.4-1 [ITP]

2014-09-16 Thread Pierre Rudloff 

Thanks for your help. I have updated the package on mentors.

1. Done.

2.
- Done.
- Done.
- Done.
- My work is now on GitHub: https://github.com/Rudloff/lutris-debian
GitHub uses the same URL for browser and git clone, you should I still 
fill both fields?
	- You can manually add to your Lutris library any game that can be 
installed on your computer (either natively or with Wine). Do you think 
the description can be misleading?

- Are you talking about game platforms? I've added a list of those.

3.
- I am not sure I understand. It does use the 1.0 format.
	- Where should I list the upstream authors? I don't see a field for 
this in the 1.0 format.


4. For some reason, help2man adds this statement at the end of every man 
page it generates. I removed it. I have also documented the different 
ways to install a game.


5. Lintian was complaining that the package did not include any upstream 
changelog so I added one from the upstream debian directory (oddly, I 
only contained information about the software itself and not the 
packaging). Anyway, I removed it.


6. I have added a generic README.source about quilt. Is this OK?

Please tell me if I did anything wrong. Thanks.

Regards,

Le 16/09/2014 15:59, Eriberto a écrit :

Hi Pierre,

Thanks for your fast reply. I will try help you.

1. d/changelog: please, use 'Initial release' instead of 'source
package automatically created by stdeb 0.6.0+git'.

2. d/control:
  - Change the Priority from extra to optional[1].
  - The upstream INSTALL file says that you must use Python 2.7.
So, change from 'python (<< 2.8), python (>= 2.7)' to 'python' in
Build-Depends and remove from Depends. The X-Python-Version field is
used to notify the system about the correct version to be used.
  - The same problem with X-Python-Version. Use 'X-Python-Version:
2.7'. More details here[2].
  - Please, create a VCS to control your debian/ versions. You can
use github or other. So, add the Vcs-Browser and Vcs-{Git|Svn|Cvs} to
d/control. You can see an example here[3].
  - In short description, is right the afirmation 'any video game'?
Is it real?
  - In long description, remove extra spaces in last three lines. I
saw in upstream site (GitHub) a list about some games that can be used
with lutris. To improve your long description and allow more people to
find your package via apt-cache search, I suggest add a list of
possible games.

[1] https://www.debian.org/doc/manuals/maint-guide/dreq.en.html#control
[2] 
https://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions
[3] 
http://sources.debian.net/src/yowsup/0.0~git20140314.938cf1-1/debian/control/

3. d/copyright: you should use the 1.0 format. Please, read this short
document[4] and fix this file.

[4] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

Other comment is that you must to list all upstream authors and
licenses in d/copyright.

4. d/lutris.6: I asked: "Where I can find the 'info' manual of the
game?", because your manpage says: "The full documentation for lutris
is maintained as a Texinfo manual.  If the info and lutris programs
are properly installed at your site, the command 'info lutris' should
give you access to the complete manual."

I would appreciate it if you put an example of installation of the
game in manpage (the complete line command).

5. d/rules:
 - Please, remove all comments.
 - Why you are installing a changelog from Ubuntu (made by
upstream)? Please, remove it and the file ChangeLog.

6. Add a d/README.source file saying about the changes need in
upstream tarball to generate the package.

Thanks for your work. I will wait your package.

Cheers,

Eriberto


2014-09-15 19:52 GMT-03:00 Pierre Rudloff :

Hello,

Sorry, I thought it was better to reuse an existing package.
I have rebuilt it from scratch: http://mentors.debian.net/package/lutris

Here are the answers to your questions:
1. It does not use it anymore.
2. I have set it to 9, which seems to be the current level.
3. It isn't a game but a game manager, so isn't a man page enough?
4. It has one now.
5. I think it should be in main, as it complies with the DFSG and does not
rely on non-free packages.

Regards,


Le 15/09/2014 22:22, Eriberto a écrit :


Hi Pierre,

I checked your package and you are using/cloning the original upstream
packaging.

To put a package in Debian you must remove the debian/ directory from
upstream source code and generate a new tarball. So, you must start a
new Debian package. You can use some ideas from upstream, not clone
the code only.

I would like you to answer some questions:

1. Why the package is using CDBS?

2. What is the current DH level?

3. Where I can find the 'info' manual of the game?

4. Why the package hasn't a X-Python-Version field?

5. Your package must be main, contrib or non-free? Why?

If your want to put a package in Debian, you must have suffici

Bug#761687: RFS: abraca/0.8.0+dfsg-1 -- Simple and powerful graphical client for XMMS2

2014-09-16 Thread Daniel Lintott 
Hi Guys,

On 16/09/14 07:23, Tobias Frost wrote:
> 
> There are no indications that the package has been orphaned, so it
> likely hasn't.
> 

In case your not aware, it seems the package has now been orphaned[1] as
of today (excellent work by Ricardo Mones).

Regards,

Daniel

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761830



signature.asc
Description: OpenPGP digital signature

Bug#761643: RFS: libstrophe/0.8.6-1 [ITP]

2014-09-16 Thread Tobias Frost 
On Tue, 2014-09-16 at 09:07 +0200, Dariusz Dwornikowski wrote:

> > Hi Dariusz,
> >  
> > somehow the d/copyright is still not matching 100% to the code...
> > At least for many files there is a "Copyright (c) 2005-2009 Collecta,
> > Inc" which is not in d/copyright. So probably this copyright owner is
> > missing for the * rule. Can you please fix it.
> 
> Yes I fixed this. 
> 
> > 
> > Also, I'm missing see a proof for the "or later" option of the GPL, as
> > it would have to be explictly stated by upstream, see GPL-3 §14. So
> > write GPL-3 or ask upstream for clarification.
> 
> Fixed, yes they have GPL-3 not later.
> > 
> > (Please wrap your comment, there is also two empty lines at the end of
> > the file and one empty line in the middle. Those are nitpicks, though) 
> 
> Wrapped. 
> 

We're there, almost... Last question: Do you want to change the license
of debian/* also to MIT and GPL-3 (without later)?

Tobi


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1410894780.14413.1.ca...@edoras.loewenhoehle.ip

automake and dh_auto_test

2014-09-16 Thread Jerome BENOIT 
Hello Forum,

I am wondering whether dh_auto_test works properly with Makefile generated via 
automake.
For my current packaging, I observe that, during a debuild building, 
dh_auto_test only
builds the test program (listed in check_PROGRAMS), but does not launch TESTS;
nevertheless, in hand mode, if dh_auto_test is ran twice, the check is performed
at the seconf launch (while the first launch only builds the test program).
Any hint ?

Thanks in advance,
Jerome


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54189229.7050...@rezozer.net

Re: automake and dh_auto_test

2014-09-16 Thread Paul Wise 
On Wed, Sep 17, 2014 at 3:40 AM, Jerome BENOIT wrote:

> Hello Forum,

 This is actually a mailing list :) 

> I am wondering whether dh_auto_test works properly with Makefile generated 
> via automake.

It should work properly if upstream is doing things the usual way.

> For my current packaging, I observe that, during a debuild building, 
> dh_auto_test only
> builds the test program (listed in check_PROGRAMS), but does not launch TESTS;
> nevertheless, in hand mode, if dh_auto_test is ran twice, the check is 
> performed
> at the seconf launch (while the first launch only builds the test program).
> Any hint ?

You might want to include some information about your particular
problem, otherwise we cannot help you effectively.

http://www.catb.org/~esr/faqs/smart-questions.html

I would suggest to include at least the name of the package you are
working on, a log of the package build with DH_VERBOSE=1, a pastebin
of the generated Makefile, a pastebin of debian/rules and a link to
the source package.

-- 
bye,
pabs

https://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: 
https://lists.debian.org/caktje6evoghow6vf+x4t-n+grztxcoko-wfw6l64wzodtwb...@mail.gmail.com

Bug#757966: RFS: lutris/0.3.4-1 [ITP]

2014-09-16 Thread Andrey Rahmatullin 
On Tue, Sep 16, 2014 at 09:13:01PM +0200, Pierre Rudloff wrote:
>   - My work is now on GitHub: https://github.com/Rudloff/lutris-debian
> GitHub uses the same URL for browser and git clone, you should I still fill
> both fields?
Of course, see
http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-VCS-fields

> 4. For some reason, help2man adds this statement at the end of every man
> page it generates. I removed it. I have also documented the different ways
> to install a game.

   -N, --no-info
  suppress pointer to Texinfo manual

> 6. I have added a generic README.source about quilt. Is this OK?
README.source is not needed if you don't repack the upstream tarball and use
dpkg to apply patches. See
http://www.debian.org/doc/debian-policy/ch-source.html#s-readmesource


-- 
WBR, wRAR


signature.asc
Description: Digital signature

How to use libgtest-dev in packaging projects (Was: ABySS version is out of date)

2014-09-16 Thread Andreas Tille 
Hi,

when trying to upgrade the abyss packaging
(git://git.debian.org/git/debian-med/abyss.git) I realised that the test
framework which switched to gtest is not as easy to use in packaging as
I expected.  According to README.Debian of libgtest-dev (which is in
line what Anthony wrote below) you need to build the test framework
first before you can use it.

I wonder how this can be done in the packaging process and whether we
have any example for doing this.

Kind regards

Andreas.

On Tue, Sep 16, 2014 at 04:48:12PM -0700, Anthony Raymond wrote:
> Hi Andreas,
> 
> I also had to compile the source that is part of the gtest package:
> sudo apt-get install libgtest-dev
> cd /usr/src/gtest && sudo cmake . && sudo make && sudo mv libg* /usr/lib/ && 
> cd -
> 
> I'm not sure of the best way to include gtest, but I found the above. How do 
> others use the gtest install from debian?
> 
> Thanks,
> Tony
> 
> On 2014-09-16, at 3:25 PM, Andreas Tille wrote:
> 
> Hi Anthony,
> 
> On Tue, Sep 16, 2014 at 02:13:33PM -0700, Anthony Raymond wrote:
> Hi Andreas, Steve,
> 
> I had to follow the instructions on this post to build libgtest.a and 
> libgtest_main.a:
> http://askubuntu.com/questions/145887/why-no-library-files-installed-for-google-test
> 
> Then I also had to add a check for libgtest in order to include -lgtest when 
> compiling the tests (see attached patch). I haven't had to do this when I 
> compile the gtest library myself, but it's not a big deal to add.
> 
> Thanks for the patch.  I applied the patch to the packaging but with no
> effect (=got the same error as below). :-(
> 
> Kind regards
> 
>   Andreas.
> 
> ...
> I commited the packaging for abyss 1.5.2 into our packaging git[1].
> Unfortunately it fails to run the unit tests since the build ended with
> 
> ...
> make[2]: Entering directory '/tmp/buildd/abyss-1.5.2/GapFiller'
> make[2]: Nothing to be done for 'check'.
> make[2]: Leaving directory '/tmp/buildd/abyss-1.5.2/GapFiller'
> make[2]: Entering directory '/tmp/buildd/abyss-1.5.2'
> make[2]: Nothing to be done for 'check-am'.
> make[2]: Leaving directory '/tmp/buildd/abyss-1.5.2'
> error: To use 'make check' command, please setup
> gtest header&library as shown on the Wiki
> Makefile:860: recipe for target 'check' failed
> make[1]: *** [check] Error 1
> make[1]: Leaving directory '/tmp/buildd/abyss-1.5.2'
> dh_auto_test: make -j1 check returned exit code 2
> debian/rules:6: recipe for target 'build' failed
> make: *** [build] Error 2
> 
> 
> While I dadded libgtest-dev to the Build-Depends and the build log says:
> 
> 
> ...
> checking for boost/unordered_set.hpp... yes
> checking gtest/gtest.h usability... yes
> checking gtest/gtest.h presence... yes
> checking for gtest/gtest.h... yes
> checking for pthread_create in -lpthread... yes
> checking for main in -lgtest_main... no
> checking for g++ option to support OpenMP... -fopenmp
> checking that generated files are newer than configure... done
> ...
> 
> 
> I think the gtest headers are reasonably installed but I wonder what
> "-lgtest_main... no" might mean, whether this is connected to the
> problem and how to fix this (Steve as maintainer of libgtest-dev in
> CC).
> 
> While I could cowardly skip the unit tests I would really prefer to
> run them.
> 
> BTW, since you asked what you can do to get abyss packaged for Debian:
> while the package is technically packaged it does not belong to the
> Debian distribution since it is regarded as non-free due to its
> licensing restriction to non-commercial use.  I wonder whether you might
> consider with the people in charge to use a non-restricted license.
> This would be really appreciated and if you want me to be more verbose
> about the advantages I could go more into details.
> 
> Kind regards
> 
>  Andreas.
> 
> [1] git://anonscm.debian.org/debian-med/abyss.git
> 
> --
> http://fam-tille.de
> 
> 
> 
> 
> 
> --
> http://fam-tille.de
> 

> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140917064006.gb7...@an3as.eu