Re: uscan: sf watch redirector update trouble for tth

[Jerome BENOIT]

Hello List,


On 15/07/14 02:35, Jerome BENOIT wrote:
> Hello List !
> 
> It seems that the SourceForge watch redirector for tth [1] does not update 
> properly:
> since a couple of weeks the latest upstream version of tth at SourceForge [2] 
> has not been noticed.
> In short I am stuck, but I want to step forward: any idea ?

It was updated a few days ago: is it an accident or is the problem solved ?

Nevertheless, the gpg signature of the package does not seem reachable while it 
does exist.

Jerome

> 
> Thanks in advance,
> Jerome
> 
> [1] https://packages.qa.debian.org/t/tth.html
> [2] http://sourceforge.net/projects/tth/
> 
> 


-- 
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/53e32894.4090...@rezozer.net

Bug#756634: RFS: roxterm/2.9.1-1

[Vincent Cheng]

On Wed, Aug 6, 2014 at 3:01 PM, Tony Houghton  wrote:
> retitle 756634 RFS: roxterm/2.9.2-1
> thanks
>
> I think I've managed to fix the build now so that the debian package can be
> built repeatedly. Most of the changes are upstream so there is a new
> version. Please use the new link:
>
> http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_2.9.2-1.dsc
>
> Thanks for helping to improve this package and to get the new version into
> Debian.

Building twice in a row still fails (the date in AppInfo.xml can
change; you can easily just workaround this with extend-diff-ignore,
of course):

dpkg-source: info: local changes detected, the modified files are:
 roxterm-2.9.2/AppInfo.xml

Also, if you don't mind me being a bit pedantic, can you run
wrap-and-sort -s so that e.g. it'd be easier to review changes to your
deps and build-deps in debian/control?

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_tCrY5=i3NDNjBWZdo6a_-W3=s_1A+p6tuQ=nm1_zlm...@mail.gmail.com

Bug#750865: RFS: lynkeos.app/1.2-7

[Yavor Doganov]

At Tue, 5 Aug 2014 20:43:50 +0200,
Paul Gevers wrote:
> Could you add tilde to the dependency on gnustep-make (for backports)

I doubt that backports of GNUstep packages are feasible (because of
the library transitions).  Backporting gnustep-make, in particular,
will make gnustep-dl2 FTBFS and some packages will end up shipping no
documentation.

> Short description, the "for GNUstep" seems misplaced. I suggest to
> either insert an extra comma, or move the for GNUstep after Tool.

Right, I have reworded it.

> Description: Mac OS X is irrelevant

Removed (also extended the long description).

> I would simplify the patching of the png. Just include the binary
> file in the debian tree and copy/clean it during building.

Done.

> Update years in copyright: first file is from 1998

Done.

> Are the patches sent upstream?

No.  As some other GNUstep packages, this one is based on a very old
and unmaintained upstream release.  There's a wishlist bug to update
it to the current upstream version.  I've made some progress on that
front but I'm unlikely to complete the porting work in time for
jessie.  I marked all patches as "Forwarded: not-needed".

> Clean fails for me in my normal environment.

Again, I'd kindly ask you for some more information.  "fakeroot
debian/rules clean" is supposed to fail if the build-dependencies are
not installed as GNUSTEP_MAKEFILES will be undefined in that case.


-- 
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/87r40she3p.GNUs_not_UNIX!%ya...@gnu.org

Bug#751550: RFS: aclock.app/0.4.0-1 [ITA]

[Paul Wise]

On Thu, Aug 7, 2014 at 4:45 PM, Yavor Doganov wrote:

> There is no recipe to render the images from the .blend file.
...
> Furthermore, it is possible that the current upstream has no clue at
> all how to generate the images

This sounds like a problem to me.

> This is usually done only for users' convenience and not because of
> some bad upstream intentions.  It is rather annoying if you can't
> build a program because of some obscure dependency that cannot be
> installed (or is burdensome to install) for some reason.

I have the luxury of being a Debian user so I do tend to not worry
about that sort of thing any more.

> I agree.  My question was would be a violation if there was no
> ironclad way to determine what is the preferred form for modification.

If we have no indicators we generally assume upstream is releasing the
preferred form for modification.

> Thanks, I didn't know that.  Only one package build-depends on
> xcftools which again suggests that currently it is not a common
> practice in Debian to regenerate images from source.  If you want to
> change that you have to enforce it somehow via Policy or at least
> document it as a recommended practice.  That's all I wanted to say.

Agreed that it is not common practice, sadly. I think we have enough
in policy/DFSG to encourage this, we just need people to understand it
and actually care about it, which is the hard part.

-- 
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/CAKTje6EwrjHvHhyvNeG=Jn3=OXgiNvf38yPRzz7MB=14wtu...@mail.gmail.com

Bug#751698: RFS: talksoup.app/1.0alpha-32-g55b4d4e-2 [ITA]

[Yavor Doganov]

At Tue, 5 Aug 2014 21:25:20 +0200,
Paul Gevers wrote:
> Some remarks:

> Text about license file on Debian systems does not mention the version

Fixed.

> It would be nice if the patch header for origin of the patch contains
> URL instead of just "upstream"

I have picked only the relevant hunks from several commits and I don't
know how to indicate that properly while still complying with the DEP
and avoiding confusion.

> Patches need sending upstream?

Yes, thanks:

* link-libs.patch: Forwarded and marked as such with URL to the
  upstream bug.
* base-1.22.patch: Marked as "Applied-Upstream: 1.1".


-- 
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/87ppgch77j.GNUs_not_UNIX!%ya...@gnu.org

Bug#739889: RFS: twython/3.1.2-1 [ITP] -- Pure Python wrapper for the Twitter API

[Eriberto]

Sorry, but three last changes:

1. Remove requirements.txt from d/docs. This information is specific
to packager, not to final user.

2. In d/rules, remove the useless lines '# -*- makefile -*-' and '#
Uncomment this to turn on verbose mode.'

3. I studied the upstream repository and he doesn't declares a
version. You can see that after several changes in repository, after
your packaging, in 'setup.py' we can see 3.1.2 yet. So, use as version
the Git information: 0.0 to version, the date and Git commit (or other
similar format). An example: 0.0~git20140314.938cf1. In your case,
considering that you will update the upstream code:
0.0~git20140805.54647c. To see more examples: $ dpkg -l | grep -i git.

When you do it, I will upload your package. No more changes.

Thanks!

Eriberto

2014-08-07 3:58 GMT-03:00 Josué Ortega :
>
>
>
> On Tue, Aug 5, 2014 at 2:44 PM, Eriberto  wrote:
>>
>> Hi!
>>
>> No need rename. And is dh_installchangelogs, not dh_autoinstalldocs.
>>
>> Cheers,
>>
>> Eriberto
>>
>>
>> 2014-08-05 17:37 GMT-03:00 Josué Ortega :
>> >
>> > I have one question about dh_autoinstalldocs, should I rename the
>> > History.rst before
>> >  pass it as parementer to dh_autoinstalldocs?
>
>
>
> Hi Eriberto,
>
> I have made the changes you asked for.
> The new version is on mentors [0][1]. Thanks.
>
> Cheers,
>
> [0]:
> http://mentors.debian.net/debian/pool/main/t/twython/twython_3.1.2-1.dsc
> [1]: http://mentors.debian.net/package/twython
>
> --
> Josue Ortega
> Happy Hacking
> http://josueortega.org
> PGP key 4096R/AB4AFD3F 2012-08-20
> Fingerprint = 7733 B328 D279 5F5B E232  5ADD 0150 9D5C AB4A FD3F
>


--
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+dXJfeCKatyUUDW1aXFtpnF_yi304hXGeednHuK0=wxxi...@mail.gmail.com

Bug#751550: RFS: aclock.app/0.4.0-1 [ITA]

[Yavor Doganov]

Paul Wise wrote:
> On Thu, Aug 7, 2014 at 4:45 PM, Yavor Doganov wrote:
> > Furthermore, it is possible that the current upstream has no clue at
> > all how to generate the images
> 
> This sounds like a problem to me.

Why?  It is quite possible that they would never have to be modified
for the entire lifetime of the package.  As long as the possibility to
do so exists and the DFSG requirements are met, I don't see a problem.

> > This is usually done only for users' convenience 
> 
> I have the luxury of being a Debian user so I do tend to not worry
> about that sort of thing any more.

I was only explaining why it is relevant for many upstream developers.
If you are upstream you should not assume that all your users have
this luxury.  Even for Debian users it can be tedious -- there are
slow architectures and there are fast architectures that happen to
have slow machines which are still in wide use.

> > Only one package build-depends on xcftools which again suggests
> > that currently it is not a common practice in Debian to regenerate
> > images from source.
> 
> Agreed that it is not common practice, sadly. I think we have enough
> in policy/DFSG to encourage this, we just need people to understand it
> and actually care about it, which is the hard part.

I could be mistaken, but Policy/DFSG does not mention anything of that
kind, not even for .mo/.info/.pdf/autotools files, let alone images.
The presence of the source is required, which is pretty much
understandable and how it should be.  The rest is just one possible
interpretation, whether correct or not.


-- 
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/87oavwh6bp.GNUs_not_UNIX!%ya...@gnu.org

Bug#757226: Please inject pristine-tar for pynfft

[Andreas Tille]

Hi Ghislain,

please use `git import-orig --pristine-tar ` to make sure the
package can be easily built using git-buildpackage.

I also switched to debhelper 9 (as well as I did in pyfftw before
uploading) since there is no valid reason any more to use something
else.  Debhelper 9 supports automatic testing (if upstream provides
this) and this is a good reason to use this version.

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/20140807124324.go27...@an3as.eu

Bug#756634: RFS: roxterm/2.9.1-1

[Tony Houghton]

On 07/08/14 09:27, Vincent Cheng wrote:

On Wed, Aug 6, 2014 at 3:01 PM, Tony Houghton  wrote:

retitle 756634 RFS: roxterm/2.9.2-1
thanks

I think I've managed to fix the build now so that the debian package can be
built repeatedly. Most of the changes are upstream so there is a new
version. Please use the new link:

http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_2.9.2-1.dsc

Thanks for helping to improve this package and to get the new version into
Debian.


Building twice in a row still fails (the date in AppInfo.xml can
change; you can easily just workaround this with extend-diff-ignore,
of course):


Except that wasn't working for me, it said it was incompatible with 
source format 3.0 (Quilt) (see above). Or was it specifically my regex 
or syntax? It looked OK to me.


AppInfo.xml is a hangover from when I used to use the ROX desktop. 
Shipping it in the tarball allows users to see info about the app before 
compiling it. I don't know whether any roxterm users are still using 
that, but I don't want to delete the ROX bits just in case. Next time I 
change upstream I should change the build so that it doesn't regenerate 
AppInfo.xml, and get my update-tags script to change it instead (I'll 
keep forgetting if I rely on doing it manually).


But for now I'd like to fix this without a new upstream release. If I 
can't get extend-diff-ignore to work would it be OK to have debian/rules 
copy the file into debian at the start of the build and restore it 
afterwards? Or is that too nasty a kludge?



Also, if you don't mind me being a bit pedantic, can you run
wrap-and-sort -s so that e.g. it'd be easier to review changes to your
deps and build-deps in debian/control?


OK, one dep per line, that makes sense. Is there anything I should do to 
have it applied to other files generated from control after expanding

${misc:Depends} etc?


--
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/53e379c6.6040...@realh.co.uk

Bug#757225: Please do not change orig.tar.gz! [Was: pyfftw_0.9.2+dfsg-2_amd64.changes REJECTED]

[Andreas Tille]

Hi Ghislain,

I reimported the originally uploaded source tarball to the Git
repository and uploaded again.  Please make sure that the content of the
repository matches what was uploaded before in the future.

Kind regards

  Andreas.

- Forwarded message from Debian FTP Masters 
 -

Date: Thu, 07 Aug 2014 12:50:09 +
From: Debian FTP Masters 
To: Debian Science Maintainers 
, Ghislain Antony Vaillant 
, ti...@debian.org
Subject: pyfftw_0.9.2+dfsg-2_amd64.changes REJECTED



pyfftw_0.9.2+dfsg-2.dsc: Invalid size hash for pyfftw_0.9.2+dfsg.orig.tar.gz:
According to the control file the size hash should be 181992,
but pyfftw_0.9.2+dfsg.orig.tar.gz has 179826.

If you did not include pyfftw_0.9.2+dfsg.orig.tar.gz in you upload, a different 
version
might already be known to the archive software.

===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.


-- 
debian-science-maintainers mailing list
debian-science-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers


- End forwarded message -

-- 
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/20140807133901.gr27...@an3as.eu

Bug#728220: fatcat uploaded to mentors.debian.net

[Eriberto]

You didn't make all changes that I requested. Please, review my last mail.

There are still Lintian messages:

W: fatcat: hardening-no-relro usr/bin/fatcat
I: fatcat: hardening-no-fortify-functions usr/bin/fatcat

Eriberto

2014-08-07 10:57 GMT-03:00 Grégoire Passault :
> Hello,
>
> I've just fixed the lintian messages and uploaded to mentors
>
> Best regards,
> Grégoire Passault


--
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+dXJeK5UwGqennXM0-Uvvw7b=z3F=q8anmp6n8ge3a9zy...@mail.gmail.com

Help needed for wxWidgets 3.0 transition of TreeviewX

[Andreas Tille]

Hi,

one of the few packages in Debian Med which has more than 100 active
users according to popcon seems to have a serious problem:  The
wxwidgets3.0 transition either injected some bugs or just uncovered
existing bugs.  Since upstream moved away from this program and the
Debian Med team does not have wx-educated people I wonder whether some
kind soul could have a look into this problem.  I guess the problem
can be understood when reading the bug report from here:

   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751255#31

Any help would be really welcome.

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/20140807145702.gv27...@an3as.eu

Bug#757226: Please inject pristine-tar for pynfft

[Ghislain Vaillant]

Hi Andreas,

On Thu, 2014-08-07 at 14:43 +0200, Andreas Tille wrote:
> Hi Ghislain,
> 
> please use `git import-orig --pristine-tar ` to make sure the
> package can be easily built using git-buildpackage.
> 

Fixed. Sorry for omitting it.

> I also switched to debhelper 9 (as well as I did in pyfftw before
> uploading) since there is no valid reason any more to use something
> else.  Debhelper 9 supports automatic testing (if upstream provides
> this) and this is a good reason to use this version.
> 

You did well. Thanks for that.

> Kind regards
> 
>   Andreas.
> 
> -- 
> http://fam-tille.de
> 
> 

Cheers,
Ghislain


-- 
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/1407423644.2309.3.camel@lat644-lap

Bug#728220: fatcat uploaded to mentors.debian.net

[Eriberto]

Complementing my last email, see below why you still have a lintian message:

# blhc fatcat_1.0.4-1_amd64.build

CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/fatcat.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/fatcat.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/core/FatEntry.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/core/FatEntry.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/core/FatFilename.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/core/FatFilename.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/core/FatModule.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/core/FatModule.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/core/FatPath.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/core/FatPath.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/core/FatSystem.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/core/FatSystem.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/core/FatDate.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/core/FatDate.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/table/FatBackup.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/table/FatBackup.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/table/FatDiff.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/table/FatDiff.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/analysis/FatExtract.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/analysis/FatExtract.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/analysis/FatFix.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/analysis/FatFix.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/analysis/FatChain.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/analysis/FatChain.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/analysis/FatChains.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/analysis/FatChains.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/analysis/FatSearch.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/analysis/FatSearch.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /usr/bin/c++-g -O2 -fPIE
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security  -I/sponsor/fcat3/fatcat-1.0.4/src-o
CMakeFiles/fatcat.dir/src/analysis/FatWalk.cpp.o -c
/sponsor/fcat3/fatcat-1.0.4/src/analysis/FatWalk.cpp
2014-08-07 13:03 GMT-03:00 Eriberto Mota :




> 2014-08-07 11:54 GMT-03:00 Grégoire Passault :
>> I don't see your warning on any of my lintian outputs
>
> Please, see it: http://eriberto.pro.br/blog/?p=1289
>
> There is a message:
>
> I: fatcat: hardening-no-fortify-functions usr/bin/fatcat
>
>> However, I've changed my debian/rules and relro now seems to be used, I've
>> re-uploaded
>
> From one of my emails sent today (please, fix):
>
> -
>
> 1. Update the debhelper to 9. You must change d/com

Bug#728220: RFS: fatcat/1.0.4-1 [ITP]

[Eriberto Mota]

As I said before (Aug. 05), you must use lintian against
fatcat_1.0.4-1_amd64.changes, not fatcat_1.0.4-1.dsc.

Eriberto



2014-08-07 13:15 GMT-03:00 Grégoire Passault :
> Thanks for your response, however, even with your flags I can't see any
> warnings about hardening:
>
> gregwar@dell:~/fatcat/debian$ ~/lintian/frontend/lintian
> --profile=debian/main --pedantic --display-info --display-experimental
> fatcat_1.0.4-1.dsc
> N: Using profile debian/main.
> N: Setting up lab in /tmp/temp-lintian-lab-WwS_BhAWdj ...
> N: Unpacking packages in group fatcat/1.0.4-1
> N: 
> N: Processing source package fatcat (version 1.0.4-1, arch source) ...
> P: fatcat source: debian-watch-may-check-gpg-signature
> gregwar@dell:~/fatcat/debian$ ~/lintian/frontend/lintian
> --profile=debian/main --pedantic --display-info --display-experimental
> fatcat_1.0.4-1_amd64.changes
> N: Using profile debian/main.
> N: Setting up lab in /tmp/temp-lintian-lab-sD0jPNUisR ...
> N: Unpacking packages in group fatcat/1.0.4-1
> N: 
> N: Processing changes file fatcat (version 1.0.4-1, arch source amd64) ...
> N: 
> N: Processing source package fatcat (version 1.0.4-1, arch source) ...
> P: fatcat source: debian-watch-may-check-gpg-signature
> N: 
> N: Processing binary package fatcat (version 1.0.4-1, arch amd64) ...
> P: fatcat: no-upstream-changelog
> gregwar@dell:~/fatcat/debian$ ~/lintian/frontend/lintian
> --profile=debian/main --pedantic --display-info --display-experimental
> fatcat_1.0.4-1_amd64.deb
> N: Using profile debian/main.
> N: Setting up lab in /tmp/temp-lintian-lab-KXF0_Be69o ...
> N: Unpacking packages in group fatcat/1.0.4-1
> N: 
> N: Processing binary package fatcat (version 1.0.4-1, arch amd64) ...
> P: fatcat: no-upstream-changelog
>
> I fixed what you said
>
> 2014-08-07 18:03 GMT+02:00 Eriberto Mota :
>
>> 2014-08-07 11:54 GMT-03:00 Grégoire Passault :
>> > I don't see your warning on any of my lintian outputs
>>
>> Please, see it: http://eriberto.pro.br/blog/?p=1289
>>
>> There is a message:
>>
>> I: fatcat: hardening-no-fortify-functions usr/bin/fatcat
>>
>> > However, I've changed my debian/rules and relro now seems to be used,
>> > I've
>> > re-uploaded
>>
>> From one of my emails sent today (please, fix):
>>
>> -
>>
>> 1. Update the debhelper to 9. You must change d/compat and [...].
>>
>> 2. d/control:
>>
>>  [...]
>>   - The Vcs-{Browser,Git} must refer to
>> {https,git}//github.com/Gregwar/fatcat/tree/debian
>>   [...]
>>   - In short/long description: [...]. In two
>> last lines use semi-colons and dot.
>>
>> 3. d/copyright: in wrong format. Please, see an example here:
>>
>> http://metadata.ftp-master.debian.org/changelogs/main/b/bittwist/unstable_copyright
>>
>> -
>>
>>
>> Now, I saw you changed from utils to contrib/misc in d/control. What
>> is the reason?
>>
>> Eriberto
>>
>> PS: you can find more details about packaging at
>> https://www.debian.org/doc/manuals/maint-guide/
>
>
>
>
> --
> Grégoire Passault


--
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+dXJeGAJLoauQ-xD1Ki=zqeydampgy0d_k2mmev-wejy+...@mail.gmail.com

Bug#756331: RFS: aafigure/0.5-4 [ITA]

[Breno Leitao]

On 07/28/2014 06:52 PM, Daniel Lintott wrote:
> Hi,
> 
> I'm not a DD so cannot sponsor your package. I haven't tried to build
> the package, but a couple of comments.
Thank you, I addressed you concerns and I just uploaded a new package:

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


-- 
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/53e3ae20.5060...@br.ibm.com

Bug#728220: RFS: fatcat/1.0.4-1 [ITP]

[Eriberto]

Ok, sorry. Do you are using Debian Sid? Is it updated?

Please, reply to me and to the bug (reply all)


2014-08-07 13:40 GMT-03:00 Grégoire Passault :
> If you have a look to the log below, I run lintian about .changes .dsc and
> .deb


--
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+dxjfbpqhonrybiv5rtkblgvuk2cjsm-mnbkjae51ojvk...@mail.gmail.com

Bug#745777: RFS: ipad-charge/0~20131118.c82b032-1 [ITP] -- USB charging control utility to charge an Apple device

[Eriberto Mota]

tags 745777 moreinfo
thanks


Hi Benjamin,

Please,

1. The upstream doesn't put a tag in repository (GitHub). In this
case, the program not have an official version. So, you must use 0.0
as version, the date and Git commit as version (or other similar
format). An example:
0.0~git20140314.938cf1. In your case: 0.0~git20131118.c82b03 (the last
commit). To see more examples: $ dpkg -l | grep -i git.

2. In d/control:
  - Change the priority from extra to optional.
  - The Vcs-* must be used to add a VCS that control your
packaging, not the upstream code only.

3. d/copyright: update the years. There is code commited in 2013.
There is no indication in the code about GPL-2.0 or GPL-2.0+. So, use
GPL-2.0.

4. d/docs: no relevant information for final user. I suggest you
remove this file and create a README.Debian to say the Wiki URL.

5. d/rules: remove this useless text:

# -*- makefile -*-
# Sample debian/rules that uses debhelper.
# This file was originally written by Joey Hess and Craig Small.
# As a special exception, when this file is copied by dh-make into a
# dh-make output file, you may use that output file without restriction.
# This special exception was added by Craig Small in version 0.37 of dh-make.

# Uncomment this to turn on verbose mode.


6. d/watch: not working. Please, see it: http://eriberto.pro.br/blog/?p=1459

7. There are Lintian messages:

W: ipad-charge: hardening-no-relro usr/bin/ipad-charge
I: ipad-charge: hardening-no-fortify-functions usr/bin/ipad-charge

To fix, see:

- https://wiki.debian.org/Hardening
- http://sources.debian.net/src/mac-robber/1.02-2/debian/patches/Makefile.patch


W: ipad-charge: binary-without-manpage usr/bin/ipad-charge

You need to write a manpage. You can use txt2man to make it easier.
See an example here:
http://sources.debian.net/src/mac-robber/1.02-2/debian/man

Thanks for your work.

Regards,

Eriberto


2014-04-29 3:44 GMT-03:00 Dariusz Dwornikowski
:
>
> Hi Benny,
>
> I am not a DD, I cannot sponsor your package but here are some
> comments:
>
> Since it is your initial upload, the version should be -1, you bump
> the number only when you *release* a new package. Merge all the
> changes into 1.1-1 release.
>
> Other things to fix:
>
> - set homepage field in d/control to github project page
> - standards should be 3.9.5
> - make the package depend on debhelper >= 9 in d/control
> - when upstream releases on github, you can prepere a watch file,
>   something like that should be sufficient:
>
> version=3
> https://github.com/mkorenkov/ipad_charge/releases 
> .*/archive/v(\d[\d\.]+)\.tar\.gz
>
> - in d/copyright you did not add years to Files: *
> - patches are not described according to DEP-3 [1]
> - what about udev rules ? are they installed ?
> - did you check your package with pbuilder and/or piuparts ?
>
> We can review the package once more, when you fix.
>
> [1] http://dep.debian.net/deps/dep3/
>
> --
> 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
>
>
> --
> 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/20140429064420.ga2...@blackstar.cs.put.poznan.pl
>


--
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+dXJfim-k1QVnUwXoBDjn6=ciuc0uziwlhj2gqcrueq_o...@mail.gmail.com

Bug#751875: RFS: gorm.app/1.2.20-1

[Paul Gevers]

Control: tags -1 +pending -moreinfo

Hi Yavor,

On 06-08-14 13:25, Yavor Doganov wrote:
>> I find the man page rather short, is it reasonable to improve it?
> 
> I have extended it as much as I could.

Looks much better now, thanks.

>> I didn't check yet, but aren't you know installing the d/docs adn
>> d/examples files into all packages? Is that what you want?
> 
> They're installed only in the gorm.app package which is what I want.

Yes, sorry, as I said, I hadn't checked yet.

>> Did you already forwarded your patches?
> 
> No; link-libs will be rejected (for some reason upstream considers it
> a feature not to link the dynamically loadable modules), so I have to
> rework it somehow.  Regarding texinfo-fixes, I'd like to fix more
> (minor) issues before forwarding upstream but have postponed that as
> there are currently more important problems to deal with.

Again, as I have said before, it might be nice to document such things
in the header so it is clear for everybody.

> Could you please post the error message?

Please see below:
paul@wollumbin ~/tmp/sponsorships/gorm.app $ TEST=lintian pdebuild
dpkg-checkbuilddeps: Unmet build dependencies: libgnustep-gui-dev
cm-super-minimal
W: Unmet build-dependency in source
dpkg-buildpackage: source package gorm.app
dpkg-buildpackage: source version 1.2.20-1
dpkg-buildpackage: source changed by Yavor Doganov 
 dpkg-source --before-build gorm.app
dpkg-checkbuilddeps: Unmet build dependencies: libgnustep-gui-dev
cm-super-minimal
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
dpkg-buildpackage: warning: this is currently a non-fatal warning with
-S, but will probably become fatal in the future
 fakeroot debian/rules clean
dh clean
   dh_testdir
   dh_auto_clean
   debian/rules override_dh_clean
make[1]: Entering directory `/media/home/paul/tmp/sponsorships/gorm.app'
/usr/bin/make -C Documentation distclean
make[2]: Entering directory
`/media/home/paul/tmp/sponsorships/gorm.app/Documentation'
GNUmakefile:2: /common.make: No such file or directory
GNUmakefile:30: /documentation.make: No such file or directory
make[2]: *** No rule to make target `/documentation.make'.  Stop.
make[2]: Leaving directory
`/media/home/paul/tmp/sponsorships/gorm.app/Documentation'
make[1]: *** [override_dh_clean] Error 2
make[1]: Leaving directory `/media/home/paul/tmp/sponsorships/gorm.app'
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit
status 2

> Any errors should be ignored by gnustep-make by default.

Might it be that not gnustep-make is used?

> Adding a hyphen triggers a lintian warning, so I've added a check for
> the presence of the .info file instead.

Sure, I saw the same after I posted.

>> Most importantly, I am not convinced yet, that the debian/copyright file
>> is a proper description of the situation. Some items that I saw and I
>> like clarification for:
>> + in the README: Icons - Mostly by Andrew Lindsay.   Gorm application
>> icon by Jesse Ross. Code -  GormViewKnobs.m adapted from code by Gerrit
>> van Dyk.
> 
> I cannot put this in debian/copyright as that file should document
> copyright, not authorship.  Gorm is an official GNU package and
> copyright is assigned to the FSF.

Ack.

>> + GormImageInspector/GormNSSplitViewInspector and many more contain the
>> header "All Rights reserved". Please check with upstream.
> 
> These files are most probably instantiated with Gorm itself which puts
> this notice.  I'll ask upstream to replace it with the actual license
> notice.  "All rights reserved" has no legal weight anyway.

Thanks.

>> + Documentation/COPYING and most GNUmakefiles say GPL-2+
> 
> The former is correct.  Apparently most makefiles were omitted during
> the switch to GPL-3+.  I'll ask upstream to rectify this.

Ack.

>> The d/copyright file mentions Examples/* but that does not exist in the
>> root. So, what do you mean.
> 
> Thanks, it should have been Documentation/Examples/*.  Fixed.

Thought so. Thanks.

I have already build the binary and I will upload as-is, but lintian
also warns me about a spelling error:
I: gorm.app: spelling-error-in-binary
usr/lib/gorm.app/libGormCore.so.1.2.20 Recieved Received

And I saw that several document seem to be double installed, e.g.:
./usr/share/GNUstep/Documentation/README
./usr/share/doc/gorm.app/README
and
./usr/share/GNUstep/Documentation/NEWS
./usr/share/doc/gorm.app/NEWS.gz
Maybe it makes sense to install everything under
/usr/share/GNUstep/Documentation/ into /usr/share/doc/gorm.app and
creating a softlink from one to the other, as Debian users expect to
find the documentation in the /usr/share/doc location while GNUstep
users might look in the other location.

Paul




signature.asc
Description: OpenPGP digital signature

Bug#728220: RFS: fatcat/1.0.4-1 [ITP]

[Daniel Lintott]

Hi Eriberto, Grégoire,

I thought I'd just run a test build to see if I could reproduce the
missing hardening... and I can't.

I built the package using an unstable sbuild chroot, and have run both
lintian and blhc on the results.

Neither complained about any missing hardening.

For reference I used:
lintian v2.5.25~bpo70+1
blhc 0.04 (installed from bpo)

Regards

Daniel

On 07/08/14 18:06, Eriberto wrote:
> Ok, sorry. Do you are using Debian Sid? Is it updated?
> 
> Please, reply to me and to the bug (reply all)
> 
> 
> 2014-08-07 13:40 GMT-03:00 Grégoire Passault :
>> If you have a look to the log below, I run lintian about .changes .dsc and
>> .deb
> 
> 



signature.asc
Description: OpenPGP digital signature

Bug#756331: RFS: aafigure/0.5-4 [ITA]

[Daniel Lintott]

Hi Breno,

On 07/08/14 17:49, Breno Leitao wrote:
> On 07/28/2014 06:52 PM, Daniel Lintott wrote:
>> Hi,
>>
>> I'm not a DD so cannot sponsor your package. I haven't tried to build
>> the package, but a couple of comments.
> Thank you, I addressed you concerns and I just uploaded a new package:
> 
> http://mentors.debian.net/package/aafigure

I've added the debian-python mailing list to the email, as per Scott's
comments [1]:

> If you'd like to continue to maintain it within the team, it is relatively 
> easy to get team sponsorship.  If so, please update the package in the DPMT 
> svn and then you can ask for sponsorship via the team ML or on IRC.

I would say, it would be a good idea to liaise with them... especially
as the package gives the VCS in the python-modules team.

With regards to the VCS, from a quick look it looks like there is going
to be some housekeeping needed... as the 0.5-4 version in Debian doesn't
match 0.5-4 in VCS (and is UNRELEASED).

I'm not familiar with the SVN packaging workflow, so I can't really
comment more on what would be needed here, but I expect someone from the
python-modules team will have the answer.

Onto the package...

1. It's probably a good idea to add yourself to the debian/copyright
under the debian/* section (and possibly add Super Nathan Weber as well,
since he prepared the last version in Debian)

2. debian/compat & debian/control - debhelper these should probably be
bumped to 9 (or 8 at least)

3. debian/control - personally I would wrap-and-sort -s this which will
split the Build-Depends, Depends, Recommends to one per line which makes
it easier to diff.

4. debian/rules - this could probably be tidied up to use short-format
dh, but I haven't tried this


Apart from them, the package builds fine and it is lintian clean.

Regards,

Daniel Lintott


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



signature.asc
Description: OpenPGP digital signature

Bug#728220: RFS: fatcat/1.0.4-1 [ITP]

[Eriberto Mota]

Really. I made a new jail and the problem is not showed. My jail is
old and I need a new. So, the hardening is ok.

Thanks a lot Daniel. Your help on mentors is always welcome.

Grégoire, forget my notes about the hardening. Keep d/rules as-is now.
Please, fix the other problems.

Thanks,

Eriberto


2014-08-07 15:43 GMT-03:00 Daniel Lintott :
> Hi Eriberto, Grégoire,
>
> I thought I'd just run a test build to see if I could reproduce the
> missing hardening... and I can't.
>
> I built the package using an unstable sbuild chroot, and have run both
> lintian and blhc on the results.
>
> Neither complained about any missing hardening.
>
> For reference I used:
> lintian v2.5.25~bpo70+1
> blhc 0.04 (installed from bpo)
>
> Regards
>
> Daniel
>
> On 07/08/14 18:06, Eriberto wrote:
>> Ok, sorry. Do you are using Debian Sid? Is it updated?
>>
>> Please, reply to me and to the bug (reply all)
>>
>>
>> 2014-08-07 13:40 GMT-03:00 Grégoire Passault :
>>> If you have a look to the log below, I run lintian about .changes .dsc and
>>> .deb
>>
>>
>


--
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+dXJd3PyTQ1yhibYLjex_j3eraeHCwf86�gh9bfbhe3...@mail.gmail.com

Bug#728220: RFS: fatcat/1.0.4-1 [ITP]

[Grégoire Passault]

Thanks Daniel for the information

The other problems should be fixed in my last upload


2014-08-07 21:40 GMT+02:00 Eriberto Mota :

> Really. I made a new jail and the problem is not showed. My jail is
> old and I need a new. So, the hardening is ok.
>
> Thanks a lot Daniel. Your help on mentors is always welcome.
>
> Grégoire, forget my notes about the hardening. Keep d/rules as-is now.
> Please, fix the other problems.
>
> Thanks,
>
> Eriberto
>
>
> 2014-08-07 15:43 GMT-03:00 Daniel Lintott :
> > Hi Eriberto, Grégoire,
> >
> > I thought I'd just run a test build to see if I could reproduce the
> > missing hardening... and I can't.
> >
> > I built the package using an unstable sbuild chroot, and have run both
> > lintian and blhc on the results.
> >
> > Neither complained about any missing hardening.
> >
> > For reference I used:
> > lintian v2.5.25~bpo70+1
> > blhc 0.04 (installed from bpo)
> >
> > Regards
> >
> > Daniel
> >
> > On 07/08/14 18:06, Eriberto wrote:
> >> Ok, sorry. Do you are using Debian Sid? Is it updated?
> >>
> >> Please, reply to me and to the bug (reply all)
> >>
> >>
> >> 2014-08-07 13:40 GMT-03:00 Grégoire Passault :
> >>> If you have a look to the log below, I run lintian about .changes .dsc
> and
> >>> .deb
> >>
> >>
> >
>



-- 
Grégoire Passault

Bug#728220: RFS: fatcat/1.0.4-1 [ITP]

[Eriberto]

Grégoire, please, follow the default in d/copyright. You need to
understand that 'Grégoire upstream' != 'Grégoire packager'. The
correct is:



Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: fatcat
Source: https://github.com/Gregwar/fatcat

Files: *
Copyright: 2013 Grégoire Passault 
License: MIT

Files: debian/*
Copyright: 2014 Grégoire Passault 
License: MIT

License: MIT
 Copyright (c) <2013> Grégoire Passault
 .
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
 in the Software without restriction, including without limitation the rights
 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 copies of the Software, and to permit persons to whom the Software is furnished
 to do so, subject to the following conditions:
 .
 The above copyright notice and this permission notice shall be included in all
 copies or substantial portions of the Software.
 .
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.



I think that is the last change. Thanks.

Eriberto

2014-08-07 17:25 GMT-03:00 Grégoire Passault :
> Thanks Daniel for the information
>
> The other problems should be fixed in my last upload
>
>
> 2014-08-07 21:40 GMT+02:00 Eriberto Mota :
>
>> Really. I made a new jail and the problem is not showed. My jail is
>> old and I need a new. So, the hardening is ok.
>>
>> Thanks a lot Daniel. Your help on mentors is always welcome.
>>
>> Grégoire, forget my notes about the hardening. Keep d/rules as-is now.
>> Please, fix the other problems.
>>
>> Thanks,
>>
>> Eriberto
>>
>>
>> 2014-08-07 15:43 GMT-03:00 Daniel Lintott :
>> > Hi Eriberto, Grégoire,
>> >
>> > I thought I'd just run a test build to see if I could reproduce the
>> > missing hardening... and I can't.
>> >
>> > I built the package using an unstable sbuild chroot, and have run both
>> > lintian and blhc on the results.
>> >
>> > Neither complained about any missing hardening.
>> >
>> > For reference I used:
>> > lintian v2.5.25~bpo70+1
>> > blhc 0.04 (installed from bpo)
>> >
>> > Regards
>> >
>> > Daniel
>> >
>> > On 07/08/14 18:06, Eriberto wrote:
>> >> Ok, sorry. Do you are using Debian Sid? Is it updated?
>> >>
>> >> Please, reply to me and to the bug (reply all)
>> >>
>> >>
>> >> 2014-08-07 13:40 GMT-03:00 Grégoire Passault :
>> >>> If you have a look to the log below, I run lintian about .changes .dsc
>> >>> and
>> >>> .deb
>> >>
>> >>
>> >
>
>
>
>
> --
> Grégoire Passault


--
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+dxjdn0zb+jh-1snffaqyxw7gh+8hlesxwysyehoovyuv...@mail.gmail.com

Bug#728220: RFS: fatcat/1.0.4-1 [ITP]

[Grégoire Passault]

Ok, it's done


2014-08-07 23:07 GMT+02:00 Eriberto :

> Grégoire, please, follow the default in d/copyright. You need to
> understand that 'Grégoire upstream' != 'Grégoire packager'. The
> correct is:
>
>
>
> Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> Upstream-Name: fatcat
> Source: https://github.com/Gregwar/fatcat
>
> Files: *
> Copyright: 2013 Grégoire Passault 
> License: MIT
>
> Files: debian/*
> Copyright: 2014 Grégoire Passault 
> License: MIT
>
> License: MIT
>  Copyright (c) <2013> Grégoire Passault
>  .
>  Permission is hereby granted, free of charge, to any person obtaining a
> copy
>  of this software and associated documentation files (the "Software"), to
> deal
>  in the Software without restriction, including without limitation the
> rights
>  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
>  copies of the Software, and to permit persons to whom the Software is
> furnished
>  to do so, subject to the following conditions:
>  .
>  The above copyright notice and this permission notice shall be included
> in all
>  copies or substantial portions of the Software.
>  .
>  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
>  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
>  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
> THE
>  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
>  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
> FROM,
>  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
>  THE SOFTWARE.
>
>
>
> I think that is the last change. Thanks.
>
> Eriberto
>
> 2014-08-07 17:25 GMT-03:00 Grégoire Passault :
> > Thanks Daniel for the information
> >
> > The other problems should be fixed in my last upload
> >
> >
> > 2014-08-07 21:40 GMT+02:00 Eriberto Mota :
> >
> >> Really. I made a new jail and the problem is not showed. My jail is
> >> old and I need a new. So, the hardening is ok.
> >>
> >> Thanks a lot Daniel. Your help on mentors is always welcome.
> >>
> >> Grégoire, forget my notes about the hardening. Keep d/rules as-is now.
> >> Please, fix the other problems.
> >>
> >> Thanks,
> >>
> >> Eriberto
> >>
> >>
> >> 2014-08-07 15:43 GMT-03:00 Daniel Lintott :
> >> > Hi Eriberto, Grégoire,
> >> >
> >> > I thought I'd just run a test build to see if I could reproduce the
> >> > missing hardening... and I can't.
> >> >
> >> > I built the package using an unstable sbuild chroot, and have run both
> >> > lintian and blhc on the results.
> >> >
> >> > Neither complained about any missing hardening.
> >> >
> >> > For reference I used:
> >> > lintian v2.5.25~bpo70+1
> >> > blhc 0.04 (installed from bpo)
> >> >
> >> > Regards
> >> >
> >> > Daniel
> >> >
> >> > On 07/08/14 18:06, Eriberto wrote:
> >> >> Ok, sorry. Do you are using Debian Sid? Is it updated?
> >> >>
> >> >> Please, reply to me and to the bug (reply all)
> >> >>
> >> >>
> >> >> 2014-08-07 13:40 GMT-03:00 Grégoire Passault :
> >> >>> If you have a look to the log below, I run lintian about .changes
> .dsc
> >> >>> and
> >> >>> .deb
> >> >>
> >> >>
> >> >
> >
> >
> >
> >
> > --
> > Grégoire Passault
>



-- 
Grégoire Passault

Bug#728220: RFS: fatcat/1.0.4-1 [ITP]

[Grégoire Passault]

Actually, I've updated it to 1.0.5, which adds some features
Is it a problem?


2014-08-07 23:30 GMT+02:00 Grégoire Passault :

> Ok, it's done
>
>
> 2014-08-07 23:07 GMT+02:00 Eriberto :
>
> Grégoire, please, follow the default in d/copyright. You need to
>> understand that 'Grégoire upstream' != 'Grégoire packager'. The
>> correct is:
>>
>>
>>
>> Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>> Upstream-Name
>> :
>> fatcat
>> Source: https://github.com/Gregwar/fatcat
>>
>> Files: *
>> Copyright: 2013 Grégoire Passault 
>> License: MIT
>>
>> Files: debian/*
>> Copyright: 2014 Grégoire Passault 
>> License: MIT
>>
>> License: MIT
>>  Copyright (c) <2013> Grégoire Passault
>>  .
>>  Permission is hereby granted, free of charge, to any person obtaining a
>> copy
>>  of this software and associated documentation files (the "Software"), to
>> deal
>>  in the Software without restriction, including without limitation the
>> rights
>>  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
>>  copies of the Software, and to permit persons to whom the Software is
>> furnished
>>  to do so, subject to the following conditions:
>>  .
>>  The above copyright notice and this permission notice shall be included
>> in all
>>  copies or substantial portions of the Software.
>>  .
>>  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
>> OR
>>  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
>>  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
>> THE
>>  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
>>  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
>> FROM,
>>  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
>>  THE SOFTWARE.
>>
>>
>>
>> I think that is the last change. Thanks.
>>
>> Eriberto
>>
>> 2014-08-07 17:25 GMT-03:00 Grégoire Passault :
>> > Thanks Daniel for the information
>> >
>> > The other problems should be fixed in my last upload
>> >
>> >
>> > 2014-08-07 21:40 GMT+02:00 Eriberto Mota :
>> >
>> >> Really. I made a new jail and the problem is not showed. My jail is
>> >> old and I need a new. So, the hardening is ok.
>> >>
>> >> Thanks a lot Daniel. Your help on mentors is always welcome.
>> >>
>> >> Grégoire, forget my notes about the hardening. Keep d/rules as-is now.
>> >> Please, fix the other problems.
>> >>
>> >> Thanks,
>> >>
>> >> Eriberto
>> >>
>> >>
>> >> 2014-08-07 15:43 GMT-03:00 Daniel Lintott :
>> >> > Hi Eriberto, Grégoire,
>> >> >
>> >> > I thought I'd just run a test build to see if I could reproduce the
>> >> > missing hardening... and I can't.
>> >> >
>> >> > I built the package using an unstable sbuild chroot, and have run
>> both
>> >> > lintian and blhc on the results.
>> >> >
>> >> > Neither complained about any missing hardening.
>> >> >
>> >> > For reference I used:
>> >> > lintian v2.5.25~bpo70+1
>> >> > blhc 0.04 (installed from bpo)
>> >> >
>> >> > Regards
>> >> >
>> >> > Daniel
>> >> >
>> >> > On 07/08/14 18:06, Eriberto wrote:
>> >> >> Ok, sorry. Do you are using Debian Sid? Is it updated?
>> >> >>
>> >> >> Please, reply to me and to the bug (reply all)
>> >> >>
>> >> >>
>> >> >> 2014-08-07 13:40 GMT-03:00 Grégoire Passault > >:
>> >> >>> If you have a look to the log below, I run lintian about .changes
>> .dsc
>> >> >>> and
>> >> >>> .deb
>> >> >>
>> >> >>
>> >> >
>> >
>> >
>> >
>> >
>> > --
>> > Grégoire Passault
>>
>
>
>
> --
> Grégoire Passault
>



-- 
Grégoire Passault

Bug#757414: RFS: chrony/1.30-1 - Set the computer clock from time servers on the Net

[Joachim Wiedorn]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "chrony":

 * Package name: chrony
   Version : 1.30-1
   Upstream Author : Miroslav Lichvar 
 * URL : http://chrony.tuxfamily.org
 * License : GPL-2
   Section : admin

It builds those binary packages:

chrony - Set the computer clock from time servers on the Net

By the way it would be very nice if someone want to set the "DM" flag for
me to this package.

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

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

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

dget -x
http://mentors.debian.net/debian/pool/main/c/chrony/chrony_1.30-1.dsc

More information about chrony can be obtained from
http://chrony.tuxfamily.org/


Changes since the last upload:

  * New upstream release with following bugfixes:
- Fix crash when selecting with multiple preferred sources.
- Fix frequency calculation with large frequency offsets.
- Fix code writing drift and RTC files to compile correctly.
- Fix -4/-6 options in chronyc to not reset hostname set by -h.
- Fix refclock sample validation with sub-second polling interval.
- Set stratum correctly with non-PPS SOCK refclock and local stratum.
- Modify dispersion accounting in refclocks to prevent PPS getting
stuck with large dispersion and not accepting new samples.
- Move faq.txt (PHP style) to a plain text file FAQ. Closes: #415729

  * Add gpg signature of upstream developer for use with uscan.
  * Update debian/watch, add check of upstream gpg signature.
  * Update all patches.

  * Bugfix: Use /etc/adjtime in postinst script to recognize
  UTC hardware clock.  Closes: #680498
  * Use logrotate instead of cron script. Closes: #323966
  * debian/rules: disable test simulation.


Regards,
   Joachim Wiedorn


signature.asc
Description: PGP signature

Bug#757428: RFS: nullmailer/1:1.13-1 [RC]

[Nick Leverton]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name: nullmailer
   Version : 1:1.13-1
   Upstream Author : Bruce Guenter 
 * URL : http://untroubled.org/nullmailer/
 * License : GPL-2+
   Section : mail

It builds those binary packages:

  nullmailer - simple relay-only mail transport agent

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

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


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

  dget -x 
http://mentors.debian.net/debian/pool/main/n/nullmailer/nullmailer_1.13-1.dsc

Changes since the last upload:

  * New upstream release (Closes: #757221, LP: #236715 by adding back-off).
  * Remove patch 07_sendquit.diff as nullmailer now does this itself.
  * B-D on automake and dh-autoreconf rather than automake1.11 and
autotools-dev (new patch 13_fix_automake.diff).
  * B-D on libgnutls28-dev (Closes: #752308) | libgnutls-dev
  * Use pidofproc -p $PIDFILE in our initscript rather than just pidof
(Closes: #687827, thanks to Lorenz Schori for the fix).
  * Update Standards-Version to 3.9.5 (no changes required).
  * Add documentation for the smtp, qmqp and smtpd modules (Closes: #682800).


Thankyou,

Nick Leverton


-- 
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/20140808003947.ga19...@leverton.org

Bug#756965: marked as done (RFS: spatialite-tools/4.2.0-1~exp1)

[Debian Bug Tracking System]

Your message dated Fri, 08 Aug 2014 04:24:58 +
with message-id 
and subject line closing RFS: spatialite-tools/4.2.0-1~exp1
has caused the Debian Bug report #756965,
regarding RFS: spatialite-tools/4.2.0-1~exp1
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.)


-- 
756965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756965
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 my package "spatialite-tools"

 Package name: spatialite-tools
 Version : 4.2.0-1~exp1
 Upstream Author : Alessandro Furieri 
 URL : https://www.gaia-gis.it/fossil/spatialite-tools/
 License : GPL-3.0+
 Section : science

It builds those binary packages:

 spatialite-bin - Geospatial extension for SQLite - tools

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

http://mentors.debian.net/package/spatialite-tools


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

  dget -x 
http://mentors.debian.net/debian/pool/main/s/spatialite-tools/spatialite-tools_4.2.0-1~exp1.dsc

More information about spatialite-tools can be obtained from 
https://www.gaia-gis.it/fossil/spatialite-tools/.

Changes since the last upload:

  * New upstream release.
  * Refresh patches:
- 00-add_automake_foreign.patch
- 03-fix_typos.patch
- 07-succesfully-typo.patch
- 08-indifferently-typo.patch
- 10-no-sqlite-check.patch
  * Update copyright file.
  * Add man page for:
- spatialite_xml_collapse
- spatialite_xml_load
- spatialite_xml_print
  * Add patch to fix 'OUTPUT' typo.


Regards,
 Bas Couwenberg
--- End Message ---
--- Begin Message ---
Package spatialite-tools version 4.2.0-1~exp1 is in experimental now.
http://packages.qa.debian.org/spatialite-tools--- End Message ---

Bug#751875: marked as done (RFS: gorm.app/1.2.20-1)

[Debian Bug Tracking System]

Your message dated Fri, 08 Aug 2014 04:24:58 +
with message-id 
and subject line closing RFS: gorm.app/1.2.20-1
has caused the Debian Bug report #751875,
regarding RFS: gorm.app/1.2.20-1
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.)


-- 
751875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751875
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 my package "gorm.app".
It builds these binary packages:

gorm.app   - Visual Interface Builder for GNUstep
gorm.app-dbg - Visual Interface Builder for GNUstep - debugging symbols
libgorm-dev - Clone of the InterfaceBuilder framework - development files
libgorm1   - Clone of the InterfaceBuilder framework - runtime library

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

  http://mentors.debian.net/package/gorm.app

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

  dget -x 
http://mentors.debian.net/debian/pool/main/g/gorm.app/gorm.app_1.2.20-1.dsc

Changes since the last upload:

* New upstream release:
  - Compatible with current GNUstep libraries (Closes: #749750).
* Ack NMU, thanks gregor herrmann.
* Debian/control (Maintainer): Set to the GNUstep team.
  (Uploaders): Add myself.
  (Build-Depends): Bump debhelper to >= 9, remove texi2html.  Add
  imagemagick, texlive-fonts-recommended and cm-super-minimal.
  (Depends): Remove dpkg | install-info, add ${misc:Depends} and
  ${gnustep:Depends}.
  (Conflicts, Replaces): Remove; obsolete.
  (libgorm-dev, libgorm1, gorm.app-dbg): New packages.
  (Vcs-Git, Vcs-Browser): New fields.
  (Standards-Version): Compliant with 3.9.5.
* debian/compat: Set to 9.
* debian/watch: Update to version 3.
* debian/source/format: Switch to 3.0 (quilt).
* GormCore/GormPrivate.m: Revert local modifications (present upstream).
* debian/patches/texinfo-fixes.patch: New; fix errors/warnings with
  texinfo/5.x.  Correct dircatecory/direntry.
* debian/patches/link-libs.patch: New; fix build with ld --no-undefined.
* debian/patches/series: Create.
* debian/rules: Rewrite for modern dh.  Move resources to /usr/share.
  Install all libraries except libGorm as private.  Enable hardening.
* debian/dirs:
* debian/overrides: Delete.
* debian/preinst:
* debian/examples:
* debian/gorm.app.install:
* debian/libgorm-dev.install:
* debian/libgorm1.install: New file.
* debian/doc-base: Correct Section, Index and Files.
* debian/menu: Add icon.
* debian/Gorm.desktop: Make it valid, add Keywords field.
* debian/README.Debian: Delete; obsolete.
* debian/docs: Remove ANNOUNCE; duplicated with NEWS.
* debian/copyright: Rewrite in format 1.0.
--- End Message ---
--- Begin Message ---
Package gorm.app version 1.2.20-1 is in NEW now,
and the package at mentors is not newer (2014-07-15) than the package in NEW 
(2014-08-06),
so there is currently no package to sponsor.

http://ftp-master.debian.org/new/gorm.app_1.2.20-1.html
http://mentors.debian.net/package/gorm.app

Please remove the package from mentors or mark it "needs sponsor = no".
If for some reason you need to replace the package in NEW,
then you can upload an updated package to mentors
and feel free to reopen this RFS 751875 or open a new RFS.--- End Message ---