Bug#763819: hdf4 not ready for sponsering

2014-10-03 Thread Andreas Tille
On Fri, Oct 03, 2014 at 11:53:21PM +0200, Johan Van de Wauw wrote:
> > I'd like to sponsor this package as requested on SoB Wiki page but there
> > are several lintian issues (including errors) which would cause an
> > auto-reject:
> 
> Thanks for taking time to review and sorry for your time. I'll try to
> find out what went wrong because I'm pretty sure that at least the
> lintian errors should not be present (they were present before and
> thought I fixed them in this upload).

OK, just touch the Wiki page if this is fixed or send an e-mail.

> Just two more questions/comments:
> 
> >
> > W: libhdf4-alt-dev: copyright-refers-to-versionless-license-file 
> > usr/share/common-licenses/GPL
> > W: libhdf4g-dev: copyright-refers-to-versionless-license-file 
> > usr/share/common-licenses/GPL
> > W: libhdf4-doc: copyright-refers-to-versionless-license-file 
> > usr/share/common-licenses/GPL
> >
> > seems to be easy to fix
> 
> Not really, since this license refers to the debian packaging work.
> The only reference points to this directory. I will ask the copyright
> holders to choose a version. Strictly speaking they might even have
> referred to different versions of the GPL.

This warning would not really stop me from sponsering if I just know
that it is somehow reflecting the history.
 
> > W: libhdf4 source: debian-watch-file-in-native-package
> > W: libhdf4 source: native-package-with-dash-version
> >
> > looks suspicious.  There are other not that important things but I'd
> > call the package in a bad state.
> Indeed suspicious and strange, I didn't get these. Wonder what went
> wrong. Probably something while rebasing.
> 
> Just a final remark: I am planning to make more changes (build only
> one library version without netcdf) after the freeze (it will require
> a transition). This can make the d/rules files and patches much
> easier. I'm now focusing on fixing bugs and ignoring some lintian
> errors, since it seems more useful to fix them when a "proper" package
> is built. Anyway, it had 134 lintian warnings before I started working
> on it, so it is definitely improving :-)

:-)
I'm pretty sure that you improved the package.

Thanks for your work on this

   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/20141004062002.gg29...@an3as.eu



lintian overrides [Was: Bug#763540: Review of psocksxx/0.0.5-1]

2014-10-03 Thread Paul Gevers
On 04-10-14 00:44, Paul Wise wrote:
> They are also not for
> experimental, pedantic or info level issues. So all of these issues
> should either be ignored or fixed but not overridden.

I have seen this before and I (as a maintainer) don't understand this
comment so bold as it is put here. I would say that overrides can help
you to see which items you (or your sponsee¹ in case of sponsorship)
already investigated. In the case of pedantic and info, you could even
say that an override is allowed when the item might be still valid but
for whatever reason is not going to be fixed (soon). I run the full
lintian on nearly every build I do and it help me to keep track of the
issue I think I still need to resolve. As long as each override has an
extensive and valid explanation, I don't see anything wrong with that
and I prefer it over having to scroll through items that are ignored
anyways.

As a sponsor, I always check all the overrides and only accept those I
understand. Documenting the reason goes a long way for that (as well as
it helps in the future to remember the original reasoning).

Paul

¹ Sorry for my English in case this word is wrong, I mean the person
that gets sponsored.



signature.asc
Description: OpenPGP digital signature


Bug#763810: RFS: cruft/0.9.16+nmu1 NMU

2014-10-03 Thread Alexandre Detiste
Hi,

> cruft is orphaned (#763888), so you dont do a NMU, as technically there
> is no maintainer. Instead, do a QA-upload. See
> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-qa-upload

Ok, it wasn't orphaned at the time I did the RFS.

Here is a new package:

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

> Of course, it would be even better if would consider adopting the
> package...

I would like to.

> As a QA upload allows you to fix litteraly everything, it would be great
> if you could reduce the bug count a little bit :)

I already solved 3 bugs, they will be automaticaly closed by the amended 
changelog.

Most others are not bugs, but feature requests;
my own biggest complaint is that it is s slow, even on a new PC.

After one week of thinkering, I had rewritten the cruft engine from scratch and 
it is already 30x to 100x faster.
https://github.com/a-detiste/cruft-ng
https://github.com/a-detiste/cruft-ng/wiki/Benchmark

It tries to have an output identical to cruft.

It doesn't support any command line argument at the moment
but it is already usefull to myself for testing the cruft ruleset, and fix it 
faster.

This let me also find new bugs in cruft: it doesn't grok multiarch,
and can't realise that libc6:amd64 & libc6 are the same thing.

I would like at first to package this as "cruft-ng (with Depends: cruft)"
so that users can compare output.

It's my first C++ program after 10 years of SQL & SAS, the code is ugly.

This in not even real C++, just C + strings + vectors + lot of calls to C 
library;
I would better rewrite it in plain C. Of course this won't be completed for 
Jessie.
 
> (So, yes, I'm willing to sponsor you if you bring the package into
> shape :-)
Ok, that would be great.

I've filled up the needed form for Debian Maintainer
https://nm.debian.org/public/person/detiste

 
> (Antonjy: You are listed as uploader... I assume that this is obsolete
> as your last upload for this package was 1998. please confirm)
Lintian complaints about that too.

Thanks !



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


Bug#763540: Review of psocksxx/0.0.5-1

2014-10-03 Thread Paul Wise
On Fri, 2014-10-03 at 13:36 +0200, Jörg Frings-Fürst wrote:

> New package is uploaded to mentors[1].

The package looks good to me. I don't have time for sponsorship but I
would encourage the regular sponsors on debian-mentors to upload this.

> The reason is that I want use GPL-3+ for my work. But for your intention
> I set the patch to the license of the source file(s). I thinks that's a
> good way, especially by sources with more then one licenses.

Fair enough.

> I have move the build part to override_dh_auto_build.
> I want to copy the doxygen generated docu in a subdir (docs). With
> d/*.docs are all files in doc directory. A second parameter link in
> d/*.install are not supported.

I see.

> Is a override necessary? Until now I only know the only errors and
> warnings are to be overwritten.

lintian overrides are only for scenarios where lintian is incorrect, not
for actual issues that you don't intend to fix. They are also not for
experimental, pedantic or info level issues. So all of these issues
should either be ignored or fixed but not overridden.

> This duplicate files comes from doxygen. 

If you would like to fix this, please checkout this tip:

https://wiki.debian.org/dedup.debian.net#Tips_for_reducing_duplication_in_packages

For debian-watch-may-check-gpg-signature there isn't much you can do
because upstream isn't releasing tarballs and Debian's infrastructure
for dealing with such upstreams isn't up to scratch yet (help welcome).
However you could ask upstream to OpenPGP-sign their git tags and
commits. Please point them at the following links too.

http://mikegerwitz.com/papers/git-horror-story
https://help.riseup.net/en/security/message-security/openpgp/best-practices
http://keyring.debian.org/creating-key.html
https://wiki.debian.org/Subkeys

> I have written a a patch to comment out this vars

You might want to adopt the upstream patch for this:

https://github.com/uditha-atukorala/psocksxx/commit/8c94cd9e7fe22ee6411bc9ed07419f4236577ea8.patch

> > $ cppcheck --enable=all -j8 --quiet -f .
...
> No changes

Please do forward the warnings upstream.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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


Bug#763819: hdf4 not ready for sponsering

2014-10-03 Thread Johan Van de Wauw
On Fri, Oct 3, 2014 at 10:33 PM, Andreas Tille  wrote:
> Hi Johan,
>
> I'd like to sponsor this package as requested on SoB Wiki page but there
> are several lintian issues (including errors) which would cause an
> auto-reject:

Thanks for taking time to review and sorry for your time. I'll try to
find out what went wrong because I'm pretty sure that at least the
lintian errors should not be present (they were present before and
thought I fixed them in this upload).

Just two more questions/comments:

>
> W: libhdf4-alt-dev: copyright-refers-to-versionless-license-file 
> usr/share/common-licenses/GPL
> W: libhdf4g-dev: copyright-refers-to-versionless-license-file 
> usr/share/common-licenses/GPL
> W: libhdf4-doc: copyright-refers-to-versionless-license-file 
> usr/share/common-licenses/GPL
>
> seems to be easy to fix

Not really, since this license refers to the debian packaging work.
The only reference points to this directory. I will ask the copyright
holders to choose a version. Strictly speaking they might even have
referred to different versions of the GPL.


>
> W: libhdf4 source: debian-watch-file-in-native-package
> W: libhdf4 source: native-package-with-dash-version
>
> looks suspicious.  There are other not that important things but I'd
> call the package in a bad state.
Indeed suspicious and strange, I didn't get these. Wonder what went
wrong. Probably something while rebasing.

Just a final remark: I am planning to make more changes (build only
one library version without netcdf) after the freeze (it will require
a transition). This can make the d/rules files and patches much
easier. I'm now focusing on fixing bugs and ignoring some lintian
errors, since it seems more useful to fix them when a "proper" package
is built. Anyway, it had 134 lintian warnings before I started working
on it, so it is definitely improving :-)


-- 
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/CAJOp35nqnqOGTmtR=sn73kx85znm3hh8x+nybxiku3bex5f...@mail.gmail.com



Bug#763819: hdf4 not ready for sponsering

2014-10-03 Thread Andreas Tille
Hi Johan,

I'd like to sponsor this package as requested on SoB Wiki page but there
are several lintian issues (including errors) which would cause an
auto-reject:

E: libhdf4-doc: doc-base-file-references-missing-file libhdf4-ref:13 
/usr/share/doc/libhdf4/html-reference/UG_Top.html
E: libhdf4-doc: doc-base-file-references-missing-file libhdf4-user:20 
/usr/share/doc/libhdf4/html-userguide/UG_Top.html

should be fixed in any case

W: libhdf4-alt-dev: copyright-refers-to-versionless-license-file 
usr/share/common-licenses/GPL
W: libhdf4g-dev: copyright-refers-to-versionless-license-file 
usr/share/common-licenses/GPL
W: libhdf4-doc: copyright-refers-to-versionless-license-file 
usr/share/common-licenses/GPL

seems to be easy to fix

W: libhdf4-doc: postinst-has-useless-call-to-install-docs
W: libhdf4-doc: prerm-has-useless-call-to-install-docs

is probably related to the errors above and

W: libhdf4 source: debian-watch-file-in-native-package
W: libhdf4 source: native-package-with-dash-version

looks suspicious.  There are other not that important things but I'd
call the package in a bad state.

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/20141003203348.gb29...@an3as.eu



Bug#763810: RFS: cruft/0.9.16+nmu1 NMU

2014-10-03 Thread Tobias Frost
Hallo Alexandre,

cruft is orphaned (#763888), so you dont do a NMU, as technically there
is no maintainer. Instead, do a QA-upload. See
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-qa-upload

Of course, it would be even better if would consider adopting the
package...

As a QA upload allows you to fix litteraly everything, it would be great
if you could reduce the bug count a little bit :)

(So, yes, I'm willing to sponsor you if you bring the package into
shape :-)

(Antonjy: You are listed as uploader... I assume that this is obsolete
as your last upload for this package was 1998. please confirm)

--
tobi 

On Fri, 2014-10-03 at 07:02 +0200, Alexandre Detiste wrote:
> Dear Maintainer, Uploaded, User
> 
> I am looking for a sponsor for my updated "cruft" package.
> 
> This includes fixes for all the changes that happened in Debian since 2011,
> like devtmpfs, systemd, grub2, cupsys -> cups ...
> 
>  * Package name: cruft
> Version : 0.9.16+nmu1 
>  * URL : https://github.com/a-detiste/cruft
>  * License : no change
> Section : admin
> 
> Here is a colordiff:
>   https://github.com/porridge/cruft/pull/3/files
> 
>   It builds those binary packages:
> cruft - program that finds any cruft built up on your system
> 
>  
> My plan was not to touch the "cruft" engine at all, only update the ruleset,
> but the current source won't even build without removing non existent 
> directories 
> "filters-frbn filters-miss" from DATADIRS in Makefile.in .
> 
> If this update succeds, I'll then have a look a the build & packaging too;
> using Lintian output as a starting point.
> 
> 
> 
>   To access further information about this package, please visit the 
> following URL:
> 
>   http://mentors.debian.net/package/cruft
> 
>   Alternatively, one can download the package with dget using this command:
> 
> dget -x 
> http://mentors.debian.net/debian/pool/main/c/cruft/cruft_0.9.16+nmu1.dsc
> 
> Alexandre Detiste
> 
> --
> 
> By the way, reportbug is itself broken at the moment (758619),
> so I didn't manage to CC you to the original RFS bug repport;
> you'll have to subscribe yourself manually to this bug.


--
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/1412366901.3620.17.ca...@edoras.loewenhoehle.ip



upstream changes release zip

2014-10-03 Thread Felix Natter
hi,

upstream Freeplane wants to replace the release zips/.tar.gzs because
they contain a freeplane-1.3.12_pre06/ instead of a freeplane-1.3.12/
directory. The software will be re-compiled (md5 changes), but There
will be absolutely no source code change.

I already packaged freeplane 1.3.12; I guess I don't need to change
the package because the upstream branch in git won't change?

Thanks and Best Regards,
-- 
Felix Natter


-- 
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/878ukxf5e1@bitburger.home.felix



Bug#763819: marked as done (RFS: spatialite-gui/1.7.1-5 [RC])

2014-10-03 Thread Debian Bug Tracking System
Your message dated Fri, 03 Oct 2014 16:25:08 +
with message-id 
and subject line closing RFS: spatialite-gui/1.7.1-5 [RC]
has caused the Debian Bug report #763819,
regarding RFS: spatialite-gui/1.7.1-5 [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.)


-- 
763819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: important
X-Debbugs-CC: pkg-grass-de...@lists.alioth.debian.org

Dear mentors,

I am looking for a sponsor for my package "spatialite-gui"

* Package name: spatialite-gui
  Version : 1.7.1-5
  Upstream Author : Alessandro Furieri 
* URL : https://www.gaia-gis.it/fossil/spatialite_gui/index
* License : GPL-3+
  Section : utils

It builds these binary packages:

spatialite-gui - user-friendly graphical user interface for SpatiaLite
spatialite-gui-dbg - user-friendly graphical user interface for
spatialite - debugging

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

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


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

dget -x
http://mentors.debian.net/debian/pool/main/s/spatialite-gui/spatialite-gui_1.7.1-5.dsc

More information about hello can be obtained from
https://www.gaia-gis.it/fossil/spatialite_gui/home.

Changes since the last upload:

  [ Ross Gammon ]
  * Team upload.
  * Add patch to fix crash when loading shapefiles.
Thanks to Alessandro Furieri (Closes: #761629)
  * Add .gitignore file to ignore quilt files

  [ Bas Couwenberg ]
  * Reorder and refrash patches.

Regards,
Ross Gammon



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Package spatialite-gui version 1.7.1-5 is in unstable now.
http://packages.qa.debian.org/spatialite-gui--- End Message ---


Bug#762536: marked as done (RFS: psensor/1.1.3-1)

2014-10-03 Thread Debian Bug Tracking System
Your message dated Fri, 03 Oct 2014 16:25:12 +
with message-id 
and subject line closing RFS: psensor/1.1.3-1
has caused the Debian Bug report #762536,
regarding RFS: psensor/1.1.3-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.)


-- 
762536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762536
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 "psensor"

 * Package name: psensor
   Version : 1.1.2-1
   Upstream Author : Jean-Philippe Orsini 
 * URL : http://wpitchoune.net/psensor
 * License : GPL-2.0
   Section : utils

  It builds those binary packages:

 psensor- display graphs for monitoring hardware temperature
 psensor-common - common files for Psensor and Psensor server
 psensor-server - Psensor server for monitoring hardware sensors remotely

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

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


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

dget -x
http://mentors.debian.net/debian/pool/main/p/psensor/psensor_1.1.2-1.dsc

  More information about psensor can be obtained from
http://wpitchoune.net/psensor.

  Changes since the last upload:

  * New upstream release.
  * debian/control
  + added dep to libxnvctrl-dev or nvidia-settings to enable
nvidia support and ease ubuntu sync.
  + removed build dep to gconf which is no more needed.
  + added build dep to libudisks2-dev.
  + removed hddtemp from "Recommends" field (psensor is using
udisks2 by default now but not psensor-server).
  * debian/psensor.install
  + removed gconf schema.
  * debian/copyright
  + added copyright information about checkpatch.pl.
  * debian/watch
  + added location of the release signature.
  * added debian/upstream/signing-key.asc

  Regards,
   Jean-Philippe Orsini



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Package psensor version 1.1.3-1 is in unstable now.
http://packages.qa.debian.org/psensor--- End Message ---


Bug#745721: marked as done (RFS: libzhuyin/0.9.99.20140929-1 [ITP])

2014-10-03 Thread Debian Bug Tracking System
Your message dated Fri, 3 Oct 2014 11:55:54 -0300
with message-id 

and subject line Re: Bug#745721: Name collision between libpinyin and libzhuyin 
(Was: Bug#745721: [Pkg-ime-devel] Bug#745721: RFS: libzhuyin/0.9.93-1)
has caused the Debian Bug report #745721,
regarding RFS: libzhuyin/0.9.99.20140929-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.)


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

Hi All,

I am looking for a sponsor for libzhuyin:

* Package name: libzhuyin
  Version : 0.9.93
  Upstream Author : Peng Wu 
* URL : https://github.com/libzhuyin/libzhuyin
* License : GPL2
  Programming Lang: C++
  Description : Zhuyin input method library

It builds the following packages:
- libzhuyin4
- libzhuyin4-data
- libzhuyin4-dev
- libzhuyin4-dbg

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

https://mentors.debian.net/package/libzhuyin

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

dget -x 
http://mentors.debian.net/debian/pool/main/libz/libzhuyin/libzhuyin_0.9.93-1.dsc


Please help to review if there is any problem in this package, and help to
upload if everything is okay. Also, please help to give me DM permission so
that I can help to maintain this package, thanks.

-- 
ChangZhuo Chen (陳昌倬) 
http://czchen.info/
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Uploaded.

Thanks for your work.

Cheers,

Eriberto


2014-10-03 11:31 GMT-03:00 ChangZhuo Chen (陳昌倬) :
> On Fri, Oct 03, 2014 at 09:38:15AM -0300, Eriberto wrote:
>> New situation: we already have a new Lintian (since yesterday).
>> Please, update the Standards-Version to 3.9.6.
>
> Just update the Standards-Version to 3.9.6. Looks like nothing need to
> change for 3.9.5 ~ 3.9.6. The package is in mentor [0], please help to
> review and sponsor, thanks.
>
> [0] https://mentors.debian.net/package/libzhuyin
> --
> ChangZhuo Chen (陳昌倬) 
> http://czchen.info/
> Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D--- End Message ---


Bug#745721: Name collision between libpinyin and libzhuyin (Was: Bug#745721: [Pkg-ime-devel] Bug#745721: RFS: libzhuyin/0.9.93-1)

2014-10-03 Thread Eriberto Mota
Uploaded.

Thanks for your work.

Cheers,

Eriberto


2014-10-03 11:31 GMT-03:00 ChangZhuo Chen (陳昌倬) :
> On Fri, Oct 03, 2014 at 09:38:15AM -0300, Eriberto wrote:
>> New situation: we already have a new Lintian (since yesterday).
>> Please, update the Standards-Version to 3.9.6.
>
> Just update the Standards-Version to 3.9.6. Looks like nothing need to
> change for 3.9.5 ~ 3.9.6. The package is in mentor [0], please help to
> review and sponsor, thanks.
>
> [0] https://mentors.debian.net/package/libzhuyin
> --
> ChangZhuo Chen (陳昌倬) 
> http://czchen.info/
> Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D


--
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+dxjfta7-6mh4crtqekqsmpmbqdmi2_kvfsvbnhj5xv5d...@mail.gmail.com



Bug#745721: Name collision between libpinyin and libzhuyin (Was: Bug#745721: [Pkg-ime-devel] Bug#745721: RFS: libzhuyin/0.9.93-1)

2014-10-03 Thread 陳昌倬
On Fri, Oct 03, 2014 at 09:38:15AM -0300, Eriberto wrote:
> New situation: we already have a new Lintian (since yesterday).
> Please, update the Standards-Version to 3.9.6.

Just update the Standards-Version to 3.9.6. Looks like nothing need to
change for 3.9.5 ~ 3.9.6. The package is in mentor [0], please help to
review and sponsor, thanks.

[0] https://mentors.debian.net/package/libzhuyin
-- 
ChangZhuo Chen (陳昌倬) 
http://czchen.info/
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D


signature.asc
Description: Digital signature


Bug#745721: Name collision between libpinyin and libzhuyin (Was: Bug#745721: [Pkg-ime-devel] Bug#745721: RFS: libzhuyin/0.9.93-1)

2014-10-03 Thread Eriberto
New situation: we already have a new Lintian (since yesterday).
Please, update the Standards-Version to 3.9.6.

Cheers,

Eriberto


2014-10-03 9:36 GMT-03:00 Eriberto :
> 2014-10-03 9:28 GMT-03:00 ChangZhuo Chen (陳昌倬) :
>>>
>>> Why you did a lintian override to amd64 only?
>>
>> The path contains multiarch tuple, so it only works on amd64. I tried to
>> build i386 package via pbuilder, and there is no "tEH" in library. So I
>> think it only happens in amd64.
>
>
> My last question: do you thought in other archs? Do you want keep
> [amd64]? (I will accept yes)
>
> 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+dxjcqrvjbvuejmko3gq3vpy87urqvyfu9h1v8zhuxpqs...@mail.gmail.com



Bug#745721: Name collision between libpinyin and libzhuyin (Was: Bug#745721: [Pkg-ime-devel] Bug#745721: RFS: libzhuyin/0.9.93-1)

2014-10-03 Thread Eriberto
2014-10-03 9:28 GMT-03:00 ChangZhuo Chen (陳昌倬) :
>>
>> Why you did a lintian override to amd64 only?
>
> The path contains multiarch tuple, so it only works on amd64. I tried to
> build i386 package via pbuilder, and there is no "tEH" in library. So I
> think it only happens in amd64.


My last question: do you thought in other archs? Do you want keep
[amd64]? (I will accept yes)

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+dxjfyk13qqznhvn4fag2cu+hjtzp_csnnh2cjjp8ggz9...@mail.gmail.com



Bug#745721: Name collision between libpinyin and libzhuyin (Was: Bug#745721: [Pkg-ime-devel] Bug#745721: RFS: libzhuyin/0.9.93-1)

2014-10-03 Thread 陳昌倬
On Wed, Oct 01, 2014 at 02:20:17PM -0300, Eriberto wrote:
> Do you removed V=1 from d/rules? Why?
> 
> Please, review my last mail saying about blhc and test the command to
> you understand the issue. Try to learn, not execute a command only.

Sorry about that, I just used to use DH_VERBOSE=1 to disable silent
rules for autotools. As I know, the problem is due to autotools silent
rules. To disable it, we can pass "--disable-silent-rules" during
configure or set V=1. Since V=1 is less verbose and shorter then
DH_VERBOSE=1, I change to use V=1 now.

As for blhc, I use it with the following command.

blhc --all libzhuyin_0.9.99.20140929-1_amd64.build

> 
> Why you did a lintian override to amd64 only?

The path contains multiarch tuple, so it only works on amd64. I tried to
build i386 package via pbuilder, and there is no "tEH" in library. So I
think it only happens in amd64.

If anyone know how to use wildcard in lintian-overrides, I can update
this override.


As usual, the package is in mentor [0], please help to review and
sponsor, thanks. The change is using "V=1" instead of "DH_VERBOSE=1" to
disable silent rules.

[0] https://mentors.debian.net/package/libzhuyin
-- 
ChangZhuo Chen (陳昌倬) 
http://czchen.info/
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D


signature.asc
Description: Digital signature


Bug#763540: Review of psocksxx/0.0.5-1

2014-10-03 Thread Jörg Frings-Fürst
Hello Paul,
Hello Harlan,

thanks for the review.

Am Mittwoch, den 01.10.2014, 12:50 +0800 schrieb Paul Wise:
> On Wed, Oct 1, 2014 at 10:18 AM, Harlan Lieberman-Berg wrote:
> 
[...]
> Some more minor issues that you might want to fix at some point:
> 
> The build process doesn't include -Wall in the build flags for gcc.
changed in d/rules.

> 
> libpsocksxx0 is missing a Pre-Depends on multiarch-support as it
> doesn't use ${misc:Pre-Depends}.
added

> You might want to build-dep on libcppunit-dev so that the build-time
> test suite is enabled.
added
>
> The git repository mentioned in Vcs-* does not exist.
My opinion was to prevent a repository with a not publish packet and to
save space. So i would create the repository shortly before upload into
the new queue. But I have done it now. 
> 
> Is there any particular reason you chose GPL-3+ for the Debian
> packaging instead of using the same as the upstream code (LGPL-3+)? If
> you ever develop patches that would mean the resulting binary packages
> are GPL-3+ not LGPL-3+ as upstream had intended and there is a very
> very slight chance this could cause license incompatibility issues as
> a result.
The reason is that I want use GPL-3+ for my work. But for your intention
I set the patch to the license of the source file(s). I thinks that's a
good way, especially by sources with more then one licenses.

> 
> compression = xz is the default for format 3.0 source packages, no
> need for it in debian/source/options. compression-level = 9 has no
> advantage (exact same size for the debian.tar.xz) over the default
> compression level for this tiny package so I wouldn't bother with it,
> removing this file might even reduce the size of the debian.tar.xz.
Removed
> 
> override_dh_installdocs should be removed, the make part should be in
> override_dh_auto_build and the cp part in libpsocksxx-doc.docs.
I have move the build part to override_dh_auto_build.
I want to copy the doxygen generated docu in a subdir (docs). With
d/*.docs are all files in doc directory. A second parameter link in
d/*.install are not supported.

> 
> You can pass arguments to dpkg-gensymbols like this: dh_makeshlibs --
> -plibpsocksxx0
I have removed the complete override

> 
> You should move the contents of README.Debian into a comment in
> libpsocksxx-doc.lintian-overrides since it isn't useful to users of
> the binary package looking for documentation.
ok. Done

> 
> I would suggest not installing the static library (remove *.a from
> debian/*.install) unless someone files a bug asking for it.
Removed

>
> README.md is not needed in the libpsocksxx0 library package since that
> will only be installed as a dep of other things.
Removed

> 
> The suggests from libpsocksxx0 to libpsocksxx-doc is not needed since
> that will only be installed as a dep of other things, please move that
> to libpsocksxx-dev since developers will install the -dev package and
> might also want the -doc package.
Ok. Done
> 
> The upstream test suite is hardcoding paths to test sockets in to
> /tmp, it should create those sockets in the test/build directory
> instead
Under work
> .
> 
> Automated checks:
> 
> https://wiki.debian.org/HowToPackageForDebian#Check_points_for_any_package
> https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git
> 
> $ lintian
> P: psocksxx source: debian-watch-may-check-gpg-signature
> X: libpsocksxx-doc: duplicate-files
> usr/share/doc/libpsocksxx-doc/docs/search/all_f.js
> usr/share/doc/libpsocksxx-doc/docs/search/functions_d.js
> X: libpsocksxx-doc: duplicate-files
> usr/share/doc/libpsocksxx-doc/docs/search/all_5.js
> usr/share/doc/libpsocksxx-doc/docs/search/functions_3.js
> X: libpsocksxx-doc: duplicate-files
> usr/share/doc/libpsocksxx-doc/docs/search/all_2.js
> usr/share/doc/libpsocksxx-doc/docs/search/functions_1.js
> X: libpsocksxx-doc: duplicate-files
> usr/share/doc/libpsocksxx-doc/docs/search/all_3.js
> usr/share/doc/libpsocksxx-doc/docs/search/functions_2.js
> X: libpsocksxx-doc: duplicate-files
> usr/share/doc/libpsocksxx-doc/docs/ftv2doc.png
> usr/share/doc/libpsocksxx-doc/docs/ftv2link.png
> X: libpsocksxx-doc: duplicate-files
> usr/share/doc/libpsocksxx-doc/docs/search/all_b.js
> usr/share/doc/libpsocksxx-doc/docs/search/functions_9.js
> X: libpsocksxx-doc: duplicate-files
> usr/share/doc/libpsocksxx-doc/docs/ftv2blank.png
> usr/share/doc/libpsocksxx-doc/docs/ftv2lastnode.png
> usr/share/doc/libpsocksxx-doc/docs/ftv2node.png
> usr/share/doc/libpsocksxx-doc/docs/ftv2vertline.png
> X: libpsocksxx-doc: duplicate-files
> usr/share/doc/libpsocksxx-doc/docs/ftv2plastnode.png
> usr/share/doc/libpsocksxx-doc/docs/ftv2pnode.png
> X: libpsocksxx-doc: duplicate-files
> usr/share/doc/libpsocksxx-doc/docs/ftv2mlastnode.png
> usr/share/doc/libpsocksxx-doc/docs/ftv2mnode.png
> X: libpsocksxx-doc: duplicate-files
> usr/share/doc/libpsocksxx-doc/docs/search/all_0.js
> usr/share/doc/libpsocksxx-doc/docs/search/variables_0.js
> X: libpsocksxx-doc: duplicate-files
> usr/sha

Bug#763853: RFS: python-trezor/0.5.3-1 ITP#763376 Python library for communicating with TREZOR Bitcoin Hardware wallet

2014-10-03 Thread Richard Ulrich
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

Package name: python-trezor
Version : 0.5.3-1
Upstream Author : Pavol Rusnak 
URL : https://github.com/trezor/python-trezor
License : public domain
Section : python

It builds those binary packages:

python-trezor - Python library for communicating with TREZOR Bitcoin
Hardware wallet

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

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


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

dget -x
http://mentors.debian.net/debian/pool/main/t/trezor/trezor_0.5.3-1.dsc

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

  
  It would be best if you could also review the two packages it depends
on in the same go: 
  * http://mentors.debian.net/package/hidapi
  * http://mentors.debian.net/package/mnemonic


  I have some questions:

  * The name for the binary package is clear to me: python-trezor, but
I'm not so certain about the correct name for the source package. 
It's called python-trezor on github, but only trezor on pypi, 
where the release tarball is from. 
  * Is there a better way to install the udev rule?
  * There is a binary deb package from https://mytrezor.com that
installs the same udev rule. Should I choose another name to
avoid conflicts?

  Regards,
   Richard Ulrich





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


Bug#762015: Subject: RFS: s3fs-fuse/1.78-1 [ITP #601789] -- FUSE-based file system backed by Amazon S3

2014-10-03 Thread Jakub Wilk

* Andrii Senkovych , 2014-10-02, 22:44:
Is it ok to look for a sponsor in some user lists? It seems readers of 
debian-cloud@lists.d.o may be interested in the package.


I think asking at debian-cloud@ is indeed your best bet.

--
Jakub Wilk


--
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/20141003081334.ga5...@jwilk.net