Bug#754793: RFS: mosquitto/1.2.1-2 RC

[Roger Light]

Hi Eriberto,

>>> 3. Is normal this issue?

> I got this message in a clean jail and in cowbuilder/pbuilder. Please,
> try in cowbuilder:

Ok, I did get these in normal building (tried it in cowbuilder as
well). I've checked and they're not important. There won't be any
trace dumps in the next release. I don't think it needs changing here.

> A new observation. To solve this message:
>
> dpkg-shlibdeps: warning: package could avoid a useless dependency if
> debian/libmosquittopp1/usr/lib/libmosquittopp.so.1 was not linked
> against libgcc_s.so.1 (it uses none of the library's symbols)
>
> Add to d/rules:
>
> export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed

Great! I've tried adding --as-needed in various ways before without any luck.

I've uploaded a fixed version.

Cheers,

Roger


-- 
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/CAH7zdydcXnM=Esv4h0_Jma99Maz7sCQxut5H9RB4Kqe+E=1...@mail.gmail.com

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

[Joachim Wiedorn]

Hello Eriberto,

thank you for your reply and your hints.

Now I have updated all items as you have written. And finally I have
forwarded some patches to upstream and have added a notice into the 
patch files.

The updated package is already on mentors.d.n:

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

Alternatively, you can download the package with dget:

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

So I hope all is perfect for sponsoring!


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

---
Have a nice day.

Joachim (Germany)


signature.asc
Description: PGP signature

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

[Paul Gevers]

On 07-08-14 10:56, Yavor Doganov wrote:
>> 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.

Please see below. It is very similar to the other trace I sent you. I
think I finally understand. You recently fixed an issue in gnustep-make
which is exactly fixing this issue. As I am on wheezy, the gnustep-make
is not up-to-date. I already started on working my way through some of
the packages to backport them for local purposes (like this one ;) ) but
haven't got around the full set. That actually was the reason why I
requested the ~ in the dependencies on gnustep-make. Anyways, I accept
this failure, although I don't like it and I think that the clean target
should just work. If build dependencies are not present, obviously the
package is not build (or I think you can at least assume it) and clean
up should have less to do.

I have three more items (and then I will upload), but this time I
provide patches:
- Please install upstream changelog (as also noted by Lintian)
- Please fix a spelling error (found by Lintian): Written
- Please install the man page into a valid section for Debian. Of
  course it can be merged into the other manpage patch if you rather
  want that.

Paul

paul@wollumbin ~/tmp/sponsorships/lynkeos.app $ TEST=lintian pdebuild
dpkg-checkbuilddeps: Unmet build dependencies: gnustep-make (>= 2.6.6-2)
libavcodec-dev (>= 6:10.1) libavformat-dev (>= 6:10.1) libswscale-dev
(>= 6:10.1) libfftw3-dev libtiff-dev libgnustep-gui-dev
W: Unmet build-dependency in source
dpkg-buildpackage: source package lynkeos.app
dpkg-buildpackage: source version 1.2-7
dpkg-buildpackage: source changed by Yavor Doganov 
 dpkg-source --before-build lynkeos.app
dpkg-source: info: applying hurd-ftbfs-fix.patch
dpkg-source: info: applying compilation-errors.patch
dpkg-source: info: applying libav-build-fix.patch
dpkg-source: info: applying plist-icon.patch
dpkg-source: info: applying manpage-fix.patch
dpkg-source: info: applying libav-0.7.patch
dpkg-source: info: applying libav-9.patch
dpkg-source: info: applying libav-10.patch
dpkg-source: info: applying format-security.patch
dpkg-source: info: applying gcc-warnings.patch
dpkg-source: info: applying fix_manpage_section.patch
dpkg-source: info: applying fix_spelling_error.patch
dpkg-checkbuilddeps: Unmet build dependencies: gnustep-make (>= 2.6.6-2)
libavcodec-dev (>= 6:10.1) libavformat-dev (>= 6:10.1) libswscale-dev
(>= 6:10.1) libfftw3-dev libtiff-dev libgnustep-gui-dev
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/lynkeos.app'
/usr/bin/make -C Sources distclean
make[2]: Entering directory
`/media/home/paul/tmp/sponsorships/lynkeos.app/Sources'
GNUmakefile:1: /common.make: No such file or directory
GNUmakefile:42: /application.make: No such file or directory
make[2]: *** No rule to make target `/application.make'.  Stop.
make[2]: Leaving directory
`/media/home/paul/tmp/sponsorships/lynkeos.app/Sources'
make[1]: *** [override_dh_clean] Error 2
make[1]: Leaving directory `/media/home/paul/tmp/sponsorships/lynkeos.app'
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit
status 2


Description: Debian policy 12.1 says that man pages should be installed
 in sections 1 to 9.
Author: Paul Gevers 

--- a/GNUstep/lynkeos.1
+++ b/GNUstep/lynkeos.1
@@ -1,6 +1,6 @@
 .\" -*-Nroff-*-
 .\""
-.TH Lynkeos 1x 2005-04-17 "Lynkeos"
+.TH Lynkeos 1 2005-04-17 "Lynkeos"
 .SH NAME
 Lynkeos \- application dedicated to the processing of astronomical (mainly planetary) images taken with a webcam through a telescope.
 .SH SYNOPSIS

Description: Fix lintian reported spelling error
Author: Paul Gevers 

--- a/Sources/ffmpeg_access.c
+++ b/Sources/ffmpeg_access.c
@@ -358,7 +358,7 @@
   TIFFSetField(image, TIFFTAG_RESOLUTIONUNIT, RESUNIT_INCH);
   
   // Write the information to the file
-  printf("Writting file ... %d \n",width*height);
+  printf("Writing file ... %d \n",width*height);
   TIFFWriteEncodedStrip(image, 0, buffer, width*height*6);
   printf("done ...\n");
 

From 56647974dc1ca1a78d7180a66cf357ef59152680 Mon Sep 17 00:00:00 2001
From: Paul Gevers 
Date: Fri, 8 Aug 2014 20:44:59 +0200
Subject: [PATCH] install upstream ChangeLog into the binary package

---
 debian/rules |3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/rules b/debian/rules
index 30196d7..179d9b6 100755
--- a/debian/rules
+++ b/debian/rules
@@ -40,3 +40,6 @@ override_dh_link:
 override_dh_fixperm

Bug#757428: marked as done (RFS: nullmailer/1:1.13-1 [RC])

[Debian Bug Tracking System]

Your message dated Fri, 08 Aug 2014 16:24:40 +
with message-id 
and subject line closing RFS: nullmailer/1:1.13-1 [RC]
has caused the Debian Bug report #757428,
regarding RFS: nullmailer/1:1.13-1 [RC]
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.)


-- 
757428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Package nullmailer version 1:1.13-1 is in unstable now.
http://packages.qa.debian.org/nullmailer--- End Message ---

Bug#746392: marked as done (RFS: fast-cpp-csv-parser/3-1 ITP)

[Debian Bug Tracking System]

Your message dated Fri, 8 Aug 2014 13:08:41 -0300
with message-id 

and subject line Re: Bug#746392: RFS: fast-cpp-csv-parser/3-1 ITP
has caused the Debian Bug report #746392,
regarding RFS: fast-cpp-csv-parser/3-1  ITP
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.)


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

  Dear mentors,

  I am looking for a sponsor for my package "fast-cpp-csv-parser"

 * Package name: fast-cpp-csv-parser
   Version : 3-1
   Upstream Author : Ben Strasser 
 * URL : https://code.google.com/p/fast-cpp-csv-parser/
 * License : BSD-3-Clause
   Section : devel

  It builds those binary packages:

fast-cpp-csv-parser - Fast C++ CSV Parser

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

  http://mentors.debian.net/package/fast-cpp-csv-parser


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

dget -x
http://mentors.debian.net/debian/pool/main/f/fast-cpp-csv-parser/fast-cpp-csv-parser_3-1.dsc

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

  Changes since the last upload:

  * Initial release


  Regards,
   Jörg Frings-Fürst

-- 
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

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






signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Uploaded. Thanks for your work.

Regards,

Eriberto--- End Message ---

Bug#754793: RFS: mosquitto/1.2.1-2 RC

[Eriberto]

2014-08-08 11:29 GMT-03:00 Roger Light :

Hi Roger! Thanks for your reply.

>> 2. I found:
>>
>> # This product includes software developed by the OpenSSL Project for use in
>> # the OpenSSL Toolkit. (http://www.openssl.org/)
>> # This product includes cryptographic software written by Eric Young
>> # (e...@cryptsoft.com)
>> # This product includes software written by Tim Hudson (t...@cryptsoft.com)
>>
>> If you used external codes in your program, you must to put it in
>> d/copypyright too. The d/copyright must relate all licenses and
>> copyrights found in upstream code. See this 'drastic' example:
>> http://sources.debian.net/src/sleuthkit/4.1.3-4/debian/copyright.
>
> I don't include any openssl code, but do use it. My original paranoid
> interpretation of the licence requirements was that if I was using it,
> I had to put the above in a readme somewhere. I am no longer certain
> that this is the case. Either way, there is no direct openssl code
> included in the tar.

As I said, If the upstream used a code inside tarball and it have a
copyright, you need mention it in d/copyright. But I saw now that no
OpenSSL element inside. The package depends libssl-dev.

>
>> 3. Is normal this issue?
>>
>> ./08-ssl-connect-no-auth.py python/08-ssl-connect-no-auth.test
>> Traceback (most recent call last):
>>   File "python/08-ssl-connect-no-auth.test", line 36, in 
>> mosq.loop()
>>   File "/sponsor/mosquitto2/mosquitto-1.3.4/lib/python/mosquitto.py",
>> line 725, in loop
>> ./08-ssl-connect-cert-auth.py python/08-ssl-connect-cert-auth.test
>> Traceback (most recent call last):
>>   File "python/08-ssl-connect-cert-auth.test", line 35, in 
>> mosq.loop()
>>   File "/sponsor/mosquitto2/mosquitto-1.3.4/lib/python/mosquitto.py",
>> line 725, in loop
>
> No it isn't, all tests should pass fine. Is it repeatable? Could you
> have had multiple sets of the tests running at once? That would have a
> good chance of causing failures.


I got this message in a clean jail and in cowbuilder/pbuilder. Please,
try in cowbuilder:

apt-get install cowbuilder
cowbuilder --create
cowbuilder --build mosquitto_1.3.4-1.dsc

A new observation. To solve this message:

dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/libmosquittopp1/usr/lib/libmosquittopp.so.1 was not linked
against libgcc_s.so.1 (it uses none of the library's symbols)

Add to d/rules:

export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed

Waiting for you. Thanks!

Eriberto


-- 
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+dxjcebdg-+fq34aqrhnwqj+vr_qmd+jynz93b3zusgo3...@mail.gmail.com

Bug#746392: RFS: fast-cpp-csv-parser/3-1 ITP

[Jörg Frings-Fürst]

Hola Eriberto,


Am Freitag, den 08.08.2014, 11:35 -0300 schrieb Eriberto:
> 2014-08-08 9:46 GMT-03:00 Jörg Frings-Fürst :
> > Hola Eriberto,
> 
> Hi Jörg! How are you?
>
> > sorry for my late answer. Yesterday I have a lot of trouble at work.
> 
> No problems. I can wait up to 126 days and 3 hours. Not more. :-)

Fine. Then I have enough time ;-)
> 
> > Thanks you for your review.
> 
> You're welcome.

[...]
> Note that this date is about commit, not about download. So, I need
> you change to 0.0~git20140429.0a2590.
> 
> You can use the whole commit number. But it will be very long. So,
> commonly, we put the three initial bytes. Git command uses it too.
> Example: commit 0a259084edadd08ea7ccaba4c6b38dd34a7c37cb. I can send
> this command to Git repository:
> 
> $ git tag -am "Tagging test1." myprogram/test1 0a2590
> 
> But, if you wish, you can use 0.0+git20140429~0a259084edad or
> 0.0~git20140429.0a259084edad. I need you change the date. (note that
> you can have several commits in same date)
> 

I have the Date corrected und the commit number shortened.

Also d/watch added and in d/control the ${shlibs:Depends} removed.
 
Package is uploaded to mentors and into git.


> Please, change the date and I will upload.
> 
> Have a nice day!
> 

You too..

> Cheers,
> 
> Eriberto
> 
> 

Many thanks

Jörg



-- 
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#746392: RFS: fast-cpp-csv-parser/3-1 ITP

[Eriberto]

I forgot to say: please, remove ${shlibs:Depends} from your d/control.

Thanks!


2014-08-08 11:35 GMT-03:00 Eriberto :
> 2014-08-08 9:46 GMT-03:00 Jörg Frings-Fürst :
>> Hola Eriberto,
>
> Hi Jörg! How are you?
>
>> sorry for my late answer. Yesterday I have a lot of trouble at work.
>
> No problems. I can wait up to 126 days and 3 hours. Not more. :-)
>
>> Thanks you for your review.
>
> You're welcome.
>
>>>
>>> I found several problems in this little package. Please:
>>>
>> fccp was one of my first debian packages. And after I hear thats very
>> difficult to find a sponsor for ITPs I don't spend more time in it.
>> Therefore a you have found a lot of mistakes :-( .
>
>
> The life is hard! :-D
>
>
>>> 2. d/copyright: is a good idea use the same license from upstream to
>>> debian/. It can avoid a possible conflict between licenses.
>> I prefer GPL for my work. In this package I don't see an conflict
>> between GPL and BSD. If there is a conflict in the future, I have no
>> problem to change the license.
>
> Ok!
>
>>> 7. d/rules: remove the useless comments and keep commented the verbose line.
>>>
>> Done. I've also added the section get-orig-source.
>
>
> Ok!
>
>
>>> 8. d/source.lintian-overrides: remove it. Create a d/watch and put an
>>> explanation about the situation. Or let the Lintian speak. I prefer a
>>> d/watch.
>> Override removed. And a useless d/watch only for the lintian? I think
>> then it is better to have a lintian info about that.
>
> I will explain about it. There are people and a team[1] that work
> around packages with missing or not working d/watch.
>
> The first step is verify the watch and fix it or create one. The
> second step is test the watch. So, a d/watch with a explanation will
> save time and efforts.
>
> Please, see here the sepwatch work[2].
>
>
> [1] https://alioth.debian.org/projects/sepwatch
> [2] https://alioth.debian.org/scm/viewvc.php/trunk/watchfiles/?root=sepwatch
>
>
>>> 2. While I was driving from work to my house, I thought ... Where you
>>> found the upstream version as being -3? I only found commits from Git
>>> in upstream repository. So, you must use 0.0, the date and Git commit
>>> as version (or other similar format). An example:
>>> 0.0~git20140314.938cf1. In your case: 0.0~git20140429.0a2590. To see
>>> more examples: $ dpkg -l | grep -i git.
>> I get the -3 from here:
>> https://code.google.com/p/fast-cpp-csv-parser/downloads/detail?name=csv_v3.h&can=1&q=
>>
>> But this is marked as deprecated. I have change the version to
>> 0.0+git20140808~0a259084edad-1
>
> Note that this date is about commit, not about download. So, I need
> you change to 0.0~git20140429.0a2590.
>
> You can use the whole commit number. But it will be very long. So,
> commonly, we put the three initial bytes. Git command uses it too.
> Example: commit 0a259084edadd08ea7ccaba4c6b38dd34a7c37cb. I can send
> this command to Git repository:
>
> $ git tag -am "Tagging test1." myprogram/test1 0a2590
>
> But, if you wish, you can use 0.0+git20140429~0a259084edad or
> 0.0~git20140429.0a259084edad. I need you change the date. (note that
> you can have several commits in same date)
>
> Please, change the date and I will upload.
>
> Have a nice day!
>
> Cheers,
>
> Eriberto


--
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+dxjdfhkh-6qxmjd_cu8pjo4mwomf9trc6wqdy+0pdxw2...@mail.gmail.com

Bug#756634: RFS: roxterm/2.9.3-1 (was 2.9.1-1)

[Tony Houghton]

retitle 756634 RFS: roxterm/2.9.3-1
thanks

On 08/08/14 09:48, Vincent Cheng wrote:

On Thu, Aug 7, 2014 at 6:06 AM, Tony Houghton  wrote:

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.


Have you tried building roxterm twice in a row in an up-to-date sid
chroot (you're probably already doing this since it's best practice
anyways, but it can't hurt to ask I guess)? Does that error message
still appear then? Ruling out differences in your build environment, I
don't see anything else that could be causing the problem you're
having with extend-diff-ignore.


To be honest I've been a bit lazy and not done that, but I've hopefully 
found another solution to the problem and also made sure to run a 
dist-upgrade before building.


I've changed upstream so that AppInfo.xml only gets written at the 
configure stage if it doesn't already exist, otherwise it only gets 
updated when generating the tarball. The new version is 2.9.3-1, dsc at 
.


Fingers crossed this problem is finally laid to rest!


--
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/53e4e665.8090...@realh.co.uk

Bug#746392: RFS: fast-cpp-csv-parser/3-1 ITP

[Eriberto]

2014-08-08 9:46 GMT-03:00 Jörg Frings-Fürst :
> Hola Eriberto,

Hi Jörg! How are you?

> sorry for my late answer. Yesterday I have a lot of trouble at work.

No problems. I can wait up to 126 days and 3 hours. Not more. :-)

> Thanks you for your review.

You're welcome.

>>
>> I found several problems in this little package. Please:
>>
> fccp was one of my first debian packages. And after I hear thats very
> difficult to find a sponsor for ITPs I don't spend more time in it.
> Therefore a you have found a lot of mistakes :-( .


The life is hard! :-D


>> 2. d/copyright: is a good idea use the same license from upstream to
>> debian/. It can avoid a possible conflict between licenses.
> I prefer GPL for my work. In this package I don't see an conflict
> between GPL and BSD. If there is a conflict in the future, I have no
> problem to change the license.

Ok!

>> 7. d/rules: remove the useless comments and keep commented the verbose line.
>>
> Done. I've also added the section get-orig-source.


Ok!


>> 8. d/source.lintian-overrides: remove it. Create a d/watch and put an
>> explanation about the situation. Or let the Lintian speak. I prefer a
>> d/watch.
> Override removed. And a useless d/watch only for the lintian? I think
> then it is better to have a lintian info about that.

I will explain about it. There are people and a team[1] that work
around packages with missing or not working d/watch.

The first step is verify the watch and fix it or create one. The
second step is test the watch. So, a d/watch with a explanation will
save time and efforts.

Please, see here the sepwatch work[2].


[1] https://alioth.debian.org/projects/sepwatch
[2] https://alioth.debian.org/scm/viewvc.php/trunk/watchfiles/?root=sepwatch


>> 2. While I was driving from work to my house, I thought ... Where you
>> found the upstream version as being -3? I only found commits from Git
>> in upstream repository. So, you must use 0.0, the date and Git commit
>> as version (or other similar format). An example:
>> 0.0~git20140314.938cf1. In your case: 0.0~git20140429.0a2590. To see
>> more examples: $ dpkg -l | grep -i git.
> I get the -3 from here:
> https://code.google.com/p/fast-cpp-csv-parser/downloads/detail?name=csv_v3.h&can=1&q=
>
> But this is marked as deprecated. I have change the version to
> 0.0+git20140808~0a259084edad-1

Note that this date is about commit, not about download. So, I need
you change to 0.0~git20140429.0a2590.

You can use the whole commit number. But it will be very long. So,
commonly, we put the three initial bytes. Git command uses it too.
Example: commit 0a259084edadd08ea7ccaba4c6b38dd34a7c37cb. I can send
this command to Git repository:

$ git tag -am "Tagging test1." myprogram/test1 0a2590

But, if you wish, you can use 0.0+git20140429~0a259084edad or
0.0~git20140429.0a259084edad. I need you change the date. (note that
you can have several commits in same date)

Please, change the date and I will upload.

Have a nice day!

Cheers,

Eriberto


--
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+dXJfm4ARmbQPHfoaR7KvDjHTN5gDKTj=qs_kaz6rhq3h...@mail.gmail.com

Bug#754793: RFS: mosquitto/1.2.1-2 RC

[Roger Light]

Hi Eriberto,

> 1. Update d/copyright. The current copyright for Troy is 2003-2013.

Oh yes, I missed that.

> 2. I found:
>
> # This product includes software developed by the OpenSSL Project for use in
> # the OpenSSL Toolkit. (http://www.openssl.org/)
> # This product includes cryptographic software written by Eric Young
> # (e...@cryptsoft.com)
> # This product includes software written by Tim Hudson (t...@cryptsoft.com)
>
> If you used external codes in your program, you must to put it in
> d/copypyright too. The d/copyright must relate all licenses and
> copyrights found in upstream code. See this 'drastic' example:
> http://sources.debian.net/src/sleuthkit/4.1.3-4/debian/copyright.

I don't include any openssl code, but do use it. My original paranoid
interpretation of the licence requirements was that if I was using it,
I had to put the above in a readme somewhere. I am no longer certain
that this is the case. Either way, there is no direct openssl code
included in the tar.

> 3. Is normal this issue?
>
> ./08-ssl-connect-no-auth.py python/08-ssl-connect-no-auth.test
> Traceback (most recent call last):
>   File "python/08-ssl-connect-no-auth.test", line 36, in 
> mosq.loop()
>   File "/sponsor/mosquitto2/mosquitto-1.3.4/lib/python/mosquitto.py",
> line 725, in loop
> ./08-ssl-connect-cert-auth.py python/08-ssl-connect-cert-auth.test
> Traceback (most recent call last):
>   File "python/08-ssl-connect-cert-auth.test", line 35, in 
> mosq.loop()
>   File "/sponsor/mosquitto2/mosquitto-1.3.4/lib/python/mosquitto.py",
> line 725, in loop

No it isn't, all tests should pass fine. Is it repeatable? Could you
have had multiple sets of the tests running at once? That would have a
good chance of causing failures.

Cheers,

Roger


-- 
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/cah7zdyfj2fwgcdjhnotocm7nmnj9j_qhchmje35+5blvwn1...@mail.gmail.com

Bug#728220: marked as done (RFS: fatcat/1.0.5-1 [ITP])

[Debian Bug Tracking System]

Your message dated Fri, 8 Aug 2014 10:37:13 -0300
with message-id 

and subject line Re: RFS: fatcat/1.0.5-1 [ITP]
has caused the Debian Bug report #728220,
regarding RFS: fatcat/1.0.5-1 [ITP]
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.)


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

Hello, I'm looking for a sponsor for my package:

* Package name: fatcat
  Version : 1.0.0
  Upstream Author : Grégoire Passault 
* URL : https://github.com/Gregwar/fatcat/
* License : MIT
  Programming Lang: C++
  Description : FAT32 explore, extract, repair, and forensic tool

fatcat is a tool to explore, extract, repair and forensic FAT32 filesystems
which i've named *fatcat*.

Its features:

   - Get information about FAT32 filesystem;
   - Explore FAT32 file system;
   - Read file or extract directories;
   - Retrieve file & directories that are deleted;
   - Backup & restore the FAT tables;
   - Hack the FAT table by writing on it;
   - Hack the entries by changing clusters and file sizes;
   - Perform a search for orphaned files & directories;
   - Compare and merge the FAT tables;
   - Repair unallocated directories &  files

I used it to repair & fix data coming from an actually broken hard drive

Sources are on GitHub:
https://github.com/Gregwar/fatcat

I built a sample package:
http://gregwar.com/fatcat/

I wrote some tutorials & examples:
https://github.com/Gregwar/fatcat/blob/master/docs/index.md

Associated ITP:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728125

Best regards,
Grégoire

Best regards
--- End Message ---
--- Begin Message ---
Uploaded. Thanks for your work.

Regards,

Eriberto--- End Message ---

Bug#757243: RFS: qmapshack/0.2.0+ds1-1

[Jaromír Mikeš]

Od: Tobias Frost 




Hello Tobias,


"- d/copyright is incomplete, there are at least 2 files not documented
for the 3rdParty folder. (CGetOpt.cpp and main.cpp) (The html file in
this dir is obviously generated by doxygen), the examples gpx are also
not in the copyright file. 

There are two animated gifs in src/animated, which are Loading
"indicators are from: http://ajaxload.info/"; (README in the file)
The site says "The gifs are totally free to use" .. This unfortunatly
does satisfy the DFSG rules, as for example the permissions for
modifying, distribution are not included. (So maybe contact the ownder
of ajaxload.info, because I assume that they are just not aware of the
fine details of copyright law)

Also there are three png without source in cursors .. one of the files
refer to a "Eric" (string in file), so also here upstream needs to
clearify copyright situation. (A image search on the net indicates
that this cursors are public domain.. http://www.rw-designer.com/cursor-set/
proton)

in src/icons/cache/COPYRIGHT I read
"All icons in this directory are from the Open Cache Manager project

http://opencachemanage.sourceforge.net/";

Checking that site tells me that that project has released files under 
Apache 2.0

Stopping here on checking copyright; you need to work through it again and 
probably also ask
upstream to take a little bit more care to more carefully document 
licenses... 


The manpage is basically empty. Please extent it (and submit it upstream.)

Nitpicks:
As you are already repacking, 
- you could also remove all the pre-generated icons (as you should 
regenerate them at build-time from the svgs :))
- you could e.g xz as compression method, instead of gz.


The other files in debian/ just need a wrap-and-sort run over it :)
Can you check if the override of the autoinstall target could be done with 
an d/install file?"



I already managed to fix few issues in packaging repo:

http://anonscm.debian.org/cgit/pkg-grass/qmapshack.git




I also contacted upstream and informed about licensing problems.

Things will be hopefully fixed with next upstream release. 





Biggest problem seems to be files src/animated, which are loading indicators
  from: http://ajaxload.info/";

I can't find any contact on Yannick Croissant ( creator of pages) anywhere :
( 


He is quite active in many projects, but nowhere is possible get email.





Any advice on this?





Thank you for reviewing.


 

best regards




Jaromir Mikes

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

[Grégoire Passault]

Hehe, sorry for that
Should be fixed


2014-08-08 13:19 GMT+02:00 Eriberto :

> 2014-08-08 7:57 GMT-03:00 Grégoire Passault :
> > Ok, you are right for the manpage and the version in the help
> >
> > I prefer letting disk.img before [options] however before this is more
> > handful if you want to do multiple operations using command line
>
> No problems!
>
>
> > I've also updated the d/copyright
>
>
> Oh no! You wrote 1024! I think I am melting your brain... :-P
>
> Review, please.
>
> Thanks.
>



-- 
Grégoire Passault

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

[Sven Hoexter]

On Fri, Aug 08, 2014 at 01:39:47AM +0100, Nick Leverton wrote:

Hi,

> 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

Thanks, uploaded.

Sven


-- 
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/20140808115927.ga4...@timegate.de

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

[Eriberto Mota]

tags 757414 moreinfo
thanks


Hi Joachim!

Please,

1. d/clean: you can safely remove chrony.html and chrony.info.

2. d/control: you can remove as build dependency the 'dpkg-dev (>=
1.16.1~)'. It is useless for DH9.

3. d/copyright: please, revise all upstream code and update this file.
You must add 2014 to upstream and packaging dates. I found extra names
and licenses. Tip: you can use '$ grep -sriC5 copyright *'.

4. d/dirs: the d/install will create the /usr/share/chrony directory.
So, you can remove it from d/dirs.

5. d/rules: remove the useless line '# -*- makefile -*-'

I will wait for you. Thanks!

Cheers,

Eriberto




2014-08-07 18:44 GMT-03:00 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


-- 
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+dXJfsNqgsgL7mr-TH_KFzdN2-UGF=uqyham-sa_wfva5...@mail.gmail.com

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

[Eriberto]

2014-08-08 7:57 GMT-03:00 Grégoire Passault :
> Ok, you are right for the manpage and the version in the help
>
> I prefer letting disk.img before [options] however before this is more
> handful if you want to do multiple operations using command line

No problems!


> I've also updated the d/copyright


Oh no! You wrote 1024! I think I am melting your brain... :-P

Review, please.

Thanks.


--
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+dXJe6aThRX9V_WDsMaT-j4iq2aXQc7NUc8e=waawq5zt...@mail.gmail.com

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

[Grégoire Passault]

Ok, you are right for the manpage and the version in the help

I prefer letting disk.img before [options] however before this is more
handful if you want to do multiple operations using command line

I've also updated the d/copyright


2014-08-08 12:50 GMT+02:00 Eriberto :

> I am test your program. I suggest these changes in you code (optional for
> you):
>
>
> --- fatcat-1.0.5.orig/man/fatcat.1  2014-08-07 18:34:36.0 -0300
> +++ fatcat-1.0.5/man/fatcat.1   2014-08-08 07:47:07.185209964 -0300
> @@ -11,7 +11,7 @@
>  ..
>
>  .\" Contact g.passa...@gmail.com to correct errors or typos.
> -.TH man 8 "29 October 2013" "1.0" "fatcat man page"
> +.TH man 1 "07 August 2014" "1.0.5" "fatcat man page"
>  .SH NAME
>  fatcat \- FAT filesystem explore, extract, repair, and forensic tool
>  .SH SYNOPSIS
> diff -Naur fatcat-1.0.5.orig/src/fatcat.cpp fatcat-1.0.5/src/fatcat.cpp
> --- fatcat-1.0.5.orig/src/fatcat.cpp2014-08-07 18:34:36.0 -0300
> +++ fatcat-1.0.5/src/fatcat.cpp 2014-08-08 07:44:58.849205858 -0300
> @@ -20,9 +20,9 @@
>
>  void usage()
>  {
> -cout << "fatcat v1.0, Gregwar " << endl;
> +cout << "fatcat v1.0.5, Gregwar " << endl;
>  cout << endl;
> -cout << "Usage: fatcat disk.img [options]" << endl;
> +cout << "Usage: fatcat [options] disk.img" << endl;
>  cout << "  -i: display information about disk" << endl;
>  cout << "  -O [offset]: global offset (may be partition place)" <<
> endl;
>  cout << endl;
>
>
> Note that the manpage level MUST be changed from 8 to 1, as showed above.
>
> Thanks,
>
> Eriberto
>
>
>
> 2014-08-08 7:40 GMT-03:00 Eriberto :
> > No problems. But your d/copyright is wrong now. Change to:
> >
> > Files: *
> > Copyright: 2013-2014 Grégoire Passault 
> > License: MIT
> >
> > I was going upload your package. But, considering you need to change
> > the d/copyright and that I had a problem in my system that generated
> > false positives (sorry for this again), you can safely remove these
> > lines from d/rules:
> >
> > export DEB_BUILD_MAINT_OPTIONS = hardening=+all
> > DPKG_EXPORT_BUILDFLAGS = 1
> > include /usr/share/dpkg/buildflags.mk
> >
> > Send me your final package and I will upload it.
> >
> > Cheers,
> >
> > Eriberto
> >
> >
> > 2014-08-07 18:35 GMT-03:00 Grégoire Passault :
> >> Actually, I've updated it to 1.0.5, which adds some features
> >> Is it a problem?
>



-- 
Grégoire Passault

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

[Eriberto]

I am test your program. I suggest these changes in you code (optional for you):


--- fatcat-1.0.5.orig/man/fatcat.1  2014-08-07 18:34:36.0 -0300
+++ fatcat-1.0.5/man/fatcat.1   2014-08-08 07:47:07.185209964 -0300
@@ -11,7 +11,7 @@
 ..

 .\" Contact g.passa...@gmail.com to correct errors or typos.
-.TH man 8 "29 October 2013" "1.0" "fatcat man page"
+.TH man 1 "07 August 2014" "1.0.5" "fatcat man page"
 .SH NAME
 fatcat \- FAT filesystem explore, extract, repair, and forensic tool
 .SH SYNOPSIS
diff -Naur fatcat-1.0.5.orig/src/fatcat.cpp fatcat-1.0.5/src/fatcat.cpp
--- fatcat-1.0.5.orig/src/fatcat.cpp2014-08-07 18:34:36.0 -0300
+++ fatcat-1.0.5/src/fatcat.cpp 2014-08-08 07:44:58.849205858 -0300
@@ -20,9 +20,9 @@

 void usage()
 {
-cout << "fatcat v1.0, Gregwar " << endl;
+cout << "fatcat v1.0.5, Gregwar " << endl;
 cout << endl;
-cout << "Usage: fatcat disk.img [options]" << endl;
+cout << "Usage: fatcat [options] disk.img" << endl;
 cout << "  -i: display information about disk" << endl;
 cout << "  -O [offset]: global offset (may be partition place)" << endl;
 cout << endl;


Note that the manpage level MUST be changed from 8 to 1, as showed above.

Thanks,

Eriberto



2014-08-08 7:40 GMT-03:00 Eriberto :
> No problems. But your d/copyright is wrong now. Change to:
>
> Files: *
> Copyright: 2013-2014 Grégoire Passault 
> License: MIT
>
> I was going upload your package. But, considering you need to change
> the d/copyright and that I had a problem in my system that generated
> false positives (sorry for this again), you can safely remove these
> lines from d/rules:
>
> export DEB_BUILD_MAINT_OPTIONS = hardening=+all
> DPKG_EXPORT_BUILDFLAGS = 1
> include /usr/share/dpkg/buildflags.mk
>
> Send me your final package and I will upload it.
>
> Cheers,
>
> Eriberto
>
>
> 2014-08-07 18:35 GMT-03:00 Grégoire Passault :
>> Actually, I've updated it to 1.0.5, which adds some features
>> Is it a problem?


--
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+dXJdHWJcP-Sc+T2sfaa+PU8e13PoeLM49y=ocjyr_746...@mail.gmail.com

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

[Eriberto]

No problems. But your d/copyright is wrong now. Change to:

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

I was going upload your package. But, considering you need to change
the d/copyright and that I had a problem in my system that generated
false positives (sorry for this again), you can safely remove these
lines from d/rules:

export DEB_BUILD_MAINT_OPTIONS = hardening=+all
DPKG_EXPORT_BUILDFLAGS = 1
include /usr/share/dpkg/buildflags.mk

Send me your final package and I will upload it.

Cheers,

Eriberto


2014-08-07 18:35 GMT-03:00 Grégoire Passault :
> Actually, I've updated it to 1.0.5, which adds some features
> Is it a problem?


--
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+dxjejvyiz4sk1bogy2cvhoykzxb3wctj-ovsaqti_8sm...@mail.gmail.com

Bug#757442: RFS: polyphone/1.4 [RFP]

[Davy Triponney]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: polyphone
   Version : 1.4-1
   Upstream Author : Davy Triponney (davy.tripon...@gmail.com)
 * URL : www.polyphone.fr
 * License : GPL v3

It builds this binary package:

polyphone

To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/polyphone


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

dget -x 
http://mentors.debian.net/debian/pool/main/p/polyphone/polyphone_1.4-1.dsc

More information about Polyphone can be obtained from http://www.polyphone.fr.


Regards,
Davy Triponney

Bug#756634: RFS: roxterm/2.9.1-1

[Vincent Cheng]

On Thu, Aug 7, 2014 at 6:06 AM, Tony Houghton  wrote:
> 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.

Have you tried building roxterm twice in a row in an up-to-date sid
chroot (you're probably already doing this since it's best practice
anyways, but it can't hurt to ask I guess)? Does that error message
still appear then? Ruling out differences in your build environment, I
don't see anything else that could be causing the problem you're
having with extend-diff-ignore.

> 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?

FTBFS when built twice in a row isn't actually RC-buggy behaviour, so
if you still can't get extend-diff-ignore to work for you, then I'm
fine with uploading your package as-is.

>> 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?

Nope, I don't care about the contents of substvars and other generated
files; wrap-and-sort is there to make it easier for me to review
changes to your _source_ package, after all.

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_tdcmdmo4+wskdzao_u7nqcvdlnnkrpohw4hfywxkhd...@mail.gmail.com