Bug#876991: RFS: proxychains-ng/4.12-1 [ITP]

[Boyuan Yang]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: epsilo...@gmail.com a...@debian.org

Dear mentors,

I am looking for a sponsor for my package "proxychains-ng".

 * Package name: proxychains-ng
   Version : 4.12-1
   Upstream Author : rofl0r 
 * URL : https://github.com/rofl0r/proxychains-ng
 * License : GPL-2
   Section : net

  It builds those binary packages:

libproxychains4 - runtime shared library for proxychains-ng
 proxychains4 - redirect connections through socks/http proxies

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

  https://mentors.debian.net/package/proxychains-ng


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

dget -x https://mentors.debian.net/debian/pool/main/p/proxychains-ng/
proxychains-ng_4.12-1.dsc

  Git packaging repository:

https://anonscm.debian.org/git/collab-maint/proxychains-ng.git

We know that current proxychains package is long dead upstream. This 
proxychains-ng is a continuation of the original project with some 
improvements.

I intend to discuss with the maintainer of proxychains to provide 
"proxychains" binary using either "Provides:" relationship or Debian's 
alternatives system after it gets accepted into the archive.

  Changes since the last upload:

 proxychains-ng (4.12-1) unstable; urgency=low
 .
   * Initial release. Closes: #823128

Regards,
Boyuan Yang

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

Bug#876798: RFS: nixnote2/2.0.2-1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: nixnote2
   Version : 2.0.2-1
   Upstream Author : Randy Baumgarte 
 * URL : http://nixnote.org
 * License : GPL-2+
   Section : utils

  It builds those binary packages:

nixnote2   - Open Source Evernote client

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

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

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

dget -x https://mentors.debian.net/debian/pool/main/n/nixnote2/
nixnote2_2.0.2-1.dsc

  Git packaging repository:

https://anonscm.debian.org/git/collab-maint/nixnote2.git

Changes since last upload:

 nixnote2 (2.0.2-1) unstable; urgency=medium
 .
   * New upstream release.
 + Force UTF-8 encoding by default. (Closes: #864978)
   * Refresh patches.
   * Bump Standard-Version to 4.1.0.

Regards,
Boyuan Yang

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

Bug#876624: RFS: qr-tools/1.4~bzr23-1 [QA]

[Boyuan Yang]

在 2017年9月25日星期一 CST 下午12:39:53，Ramiro Algozino 写道：
> Hello Boyuang,
> 
> Thank you for CCing me and thank you for your work, specially migrating to
> Qt5, I've been trying to update qrtools for a while but never found the
> time to do it.
> 
> I will try to test your contribution this week and push it to launchpad if
> you don't mind.
> 
> Best regards,

Great, please go ahead.

There are still several bugs left, see [1]. I have requested to join the 
Launchpad qr-tools-developers group. If you accept this request, I could try 
my best to push fixes upstream.

[1] https://anonscm.debian.org/git/collab-maint/qr-tools.git/tree/debian/BUGS

Regards,
Boyuan Yang

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

Bug#876649: RFS: qterm/1:0.7.2-1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org

Dear mentors and chinese-developers folks,

  I am looking for a sponsor for my package "qterm".

 * Package name: qterm
   Version : 1:0.7.2-1
   Upstream Author : Xiaoqiang Wang 
 * URL : https://github.com/qterm/qterm
 * License : GPL-2+ with OpenSSL exception
   Section : x11

  It builds those binary packages:

qterm - BBS client for X Window System written in Qt

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/q/qterm/
qterm_0.7.2-1.dsc

  Git packaging repository:

https://anonscm.debian.org/git/chinese/qterm.git


  Changes since the last upload:

 qterm (1:0.7.2-1) unstable; urgency=medium
 .
   * New upstream release.
 + Extend port number selection up to 65535. (Closes: #764889)
   * Remove broken icon symlink.
 (Closes: #851902, LP: #581199)
   * Bump Standards-Version to 4.1.0. (No changes needed)
   * Drop all patches, applied upstream.

Regards,
Boyuan Yang

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

Bug#876624: RFS: qr-tools/1.4~bzr23-1 [QA]

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: david4...@gmail.com algoz...@gmail.com

Dear mentors,

This is a QA upload for package "qr-tools", which might went a little bit too 
far from simply a QA. Anyway here is the information:

 * Package name: qr-tools
   Version : 1.4~bzr23-1
   Upstream Author : David Green 
 * URL : https://launchpad.net/qr-tools
 * License : GPL-3+
   Section : python

  It builds those binary packages:

python-qrtools - high level library for reading and generating QR codes
 qtqr  - Qt frontend for QR code generator and decoder

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

  https://mentors.debian.net/package/qr-tools


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

dget -x 
https://mentors.debian.net/debian/pool/main/q/qr-tools/qr-tools_1.4~bzr23-1.dsc


  Git packaging repository:

https://anonscm.debian.org/git/collab-maint/qr-tools.git


Changes since the last upload:
 qr-tools (1.4~bzr23-1) unstable; urgency=high
 .
   * QA upload.
 + Set package maintainer to Debian QA Group.
   * New upstream snapshot.
 + Fix incompatibility with new PIL library.
   (Closes: #812556; Closes: #847150)
 + Add option to select whether to show WiFi password when writing it.
   * Replace python-imaging dep with python-pil. (Closes: #866475)
   * Apply wrap-and-sort -abst.
   * Bump debhelper compat to v10.
   * Use Standards-Version 4.1.0.
   * Add patch to migrate to Qt5. (Closes: #875142)
   * Add patch to prevent crashing when given file is not an image.
   * Add patch to provide zh_CN translation.
   * Add patch to fix crashing with malformed URL.
   * Update qtqr.desktop in debian/ dir.
 + Add zh_CN translation.
 + Edit Exec key to comply with Desktop Entry Specification.
   * Update qtqr.1 man page accordingly.
   * Set package qtqr in section "utils".
   * Document all known bugs in debian/BUGS file.

...as you can see, it's more than just a QA upload. The biggest part is the 
migration from PyQt4 to PyQt5 (since Qt4 is to be removed soon). AFAIK the 
program is working well after the migration (tested locally).

I am CC-ing upstream authors here in hope that we could get contributions 
merged back later.

Regards,
Boyuan Yang

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

Bug#876286: RFS: xml2/0.5-1 [QA,RC]

[Boyuan Yang]

Package: sponsorship-requests
Severity: important
X-Debbugs-CC: Patrick Schoenfeld 

Dear mentors,

I intend to deal with the RC bug #506805 with a QA upload for package xml2.

According to descriptions in Bug #754418 [1], xml2 upstream is dead but we 
have a newer release tarball somewhere around the Internet. I picked the 
tarball from Fedora project and have it packaged. Changes have been reviewed 
by me and no problems were found (only fixes). Anyone interested can review 
changes in the packaging repository [2].

Upstream import commit ID:  7cf024c51b18c48f85b764902aa6e2dd66eeac9d

P.S. I intend to do some stable uploads as well later.

 * Package name: xml2
   Version : 0.5-1
 * URL : [defunct]
 * License : GPLv2
   Section : utils

  It builds those binary packages:

xml2  - Convert between XML, HTML, CSV and a line-oriented format

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/x/xml2/xml2_0.5-1.dsc


  Git packaging repository:

https://anonscm.debian.org/git/collab-maint/xml2.git


  Changes since the last upload:
 xml2 (0.5-1) unstable; urgency=high
 .
   * QA upload.
 + Set maintainer to Debian QA Group.
   * New upstream release, tarball taken from Fedora. (Closes: #754418)
 - Fix corruption when dealing with UTF-8 files. (Closes: #506805)
 - Fix hardcoded ISO-8859-1 encoding. (Closes: #698072)
 - Fix a bug in 2csv.c to avoid a strdup on null pointer.
 - Update include path for libxml2.
 - Changes around autotools.
 - Update usage string for 2csv. (Closes: #506788)
   * Cleanup in packaging system.
 + Set Standards-Version to 4.1.0.
 + Use canonical Vcs URL.
 + Bump debhelper compat and version dependency to v10.
 + Drop dh-autoreconf (not needed in debhelper v10)
 + Use "3.0 (quilt)" as source package format.
   * Drop watch file (dead upstream)
   * Drop all patches, merged upstream.
   * Update README.source description.

Regards,
Boyuan Yang

[1] https://bugs.debian.org/754418
[2] https://anonscm.debian.org/git/collab-maint/xml2.git


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

Bug#875679: closing 875679

[Boyuan Yang]

close 875679 
thanks

Already sponsored by Dmitry.

Regards,
Boyuan Yang

Bug#875679: RFS: goldendict/1.5.0~rc2+git20170908+ds-1

[Boyuan Yang]

在 2017年9月14日星期四 CST 上午10:54:42，Dmitry E. Oboukhov 写道：
> Hi, Boyuan!
> 
> > commit 45d460fcc8c86f50e6bff1c505396dd4d7c462df
> > Author: Boyuan Yang <073p...@gmail.com>
> > Date:   Wed Sep 13 16:16:48 2017 +0800
> > 
> > debian: prepare new release 1.5.0~rc2+git20170908+ds-1
> >  
> >  config.cc   |   3
> >  -
> >  debian/changelog|  10
> >  ++- debian/control 
> >  |   2 + ...sable-autostart-control =>
> >  0001-Disable-default-autostart.patch} |  17 +++--
> >  debian/patches/8e11d2a0bdec3ccf24ebb61d468b005543b899ee.patch   |
> >  115 -- debian/patches/series
> >|   4 +- debian/patches/wordnet-dict-paths
> >|  14  debian/rules   
> >  |   5 ++ debian/watch   
> >  |   5 ++ preferences.ui 
> >  |   3 - 10 files
> >  changed, 34 insertions(+), 144 deletions(-)
> 
> You dropped patch debian/patches/wordnet-dict-paths, so Your version
> goldendict can not use wordnet dictionaries (see Debian packages
> wordnet and goldendict-wordnet).
> 
> Could You revert the patch?
> 
> PS: Debian contains package "wordnet". The patch created an
> integration between goldendict and wordnet.

I believe this patch is long merged upstream.

https://github.com/goldendict/goldendict/blob/master/config.cc#L345

$ git show-ref HEAD
1b9d894a60ff7059e3f5a6d5fd3e23a2745f431d refs/remotes/origin/HEAD

$ git blame config.cc
[...]
55749e23 src/config.cc (Konstantin Isakov   2009-04-09 19:03:28 +  341) 
ba1f38b9 config.cc (Tvangeste   2013-07-18 20:22:41 +0200  342) 

if ( QDir( "/usr/share/opendict/dictionaries" ).exists() )
ba1f38b9 config.cc (Tvangeste   2013-07-18 20:22:41 +0200  343) 
  
c.paths.push_back( Path( "/usr/share/opendict/dictionaries", true ) );
ba1f38b9 config.cc (Tvangeste   2013-07-18 20:22:41 +0200  344) 
af0fceb7 config.cc (Tvangeste   2013-07-18 20:14:01 +0200  345) 

if ( QDir( "/usr/share/goldendict-wordnet" ).exists() )
af0fceb7 config.cc (Tvangeste   2013-07-18 20:14:01 +0200  346) 
  
c.paths.push_back( Path( "/usr/share/goldendict-wordnet", true ) );
af0fceb7 config.cc (Tvangeste   2013-07-18 20:14:01 +0200  347) 
107c75ce src/config.cc (Konstantin Isakov   2009-04-04 19:20:09 +  348) 

if ( QDir( "/usr/share/WyabdcRealPeopleTTS" ).exists() )
c6cbaa64 config.cc (Julian Depetris Chauvin 2013-02-02 19:00:19 -0300  349) 
  
c.soundDirs.push_back( SoundDir( "/usr/share/
WyabdcRealPeopleTTS","WyabdcRealPeopleTTS" ) );
[...]

$ git show af0fceb7 | cat
commit af0fceb7f189506d198452875ab06e670438592a
Author: Tvangeste 
Date:   Thu Jul 18 20:14:01 2013 +0200

Preconfigure goldendict-wordnet path (patch by Dmitry E. Oboukhov)

diff --git a/config.cc b/config.cc
index 75923d9..6d2798c 100644
--- a/config.cc
+++ b/config.cc
@@ -308,6 +308,9 @@ Class load() throw( exError )
 if ( QDir( "/usr/share/dictd" ).exists() )
   c.paths.push_back( Path( "/usr/share/dictd", true ) );
 
+if ( QDir( "/usr/share/goldendict-wordnet" ).exists() )
+  c.paths.push_back( Path( "/usr/share/goldendict-wordnet", true ) );
+
 if ( QDir( "/usr/share/WyabdcRealPeopleTTS" ).exists() )
   c.soundDirs.push_back( SoundDir( "/usr/share/WyabdcRealPeopleTTS", 
"WyabdcRealPeopleTTS" ) );

Regards,
Boyuan Yang

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

Bug#875679: RFS: goldendict/1.5.0~rc2+git20170908+ds-1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: un...@debian.org

Dear mentors and Dmitry,

I am looking for a sponsor for the package I co-maintain, "goldendict".

This upload would update the package "goldendict" to its latest snapshot. 
Goldendict upstream has been pretty stable recently and no major regressions 
were found. I believe this upload should be appropriate. Meanwile, this upload 
tries to eliminate lintian warnings and errors.

 * Package name: goldendict
   Version : 1.5.0~rc2+git20170908+ds-1
   Upstream Author : Abs62 
 * URL : http://goldendict.org
 * License : GPL-3+
   Section : utils

  It builds those binary packages:

goldendict - feature-rich dictionary lookup program

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/g/goldendict/
goldendict_1.5.0~rc2+git20170908+ds-1.dsc


  Alioth Git packaging repository:

https://anonscm.debian.org/git/collab-maint/goldendict.git

  Changes since the last upload:

goldendict (1.5.0~rc2+git20170908+ds-1) unstable; urgency=medium
 .
  * New upstream snapshot. (Closes: #867497)
+ Enable support for Zim dictionaries.
+ Enable support for Chinese conversion.
  * Remove third-party maclibs and winlibs (+ds).
  * Apply "wrap-and-sort -abst".
  * Bump Standards-Version to 4.1.0.
  * Switch from cdbs to debhelper v10+.
+ Bump debian/compat to 10.
+ Enable full hardening.
  * Update man page for goldendict accordingly.
  * Drop menu file (per ctte's decision in #741573).
  * Refresh patches. 
  * Limit libhunspell version (>= 1.6.1).
  * Refresh watch file.

Regards,
Boyuan Yang

Bug#874428: RFS: goldendict/1.5.0~git20160508.g92b5485-1.2 [RC, NMU]

[Boyuan Yang]

在 2017年9月8日星期五 CST 下午11:51:44，Dmitry E. Oboukhov 写道：
> >>> Man thanks Boyuan for taking care about goldendict!
> >>> 
> >>>> Dear mentors and Dmitry,
> >>>> 
> >>>>* Add myself into uploaders list. (Hijacking package)
> >>> 
> >>> As I learned on DebConf17'S we've have a (proposed) process for
> >>> this. Lets bring it to live and salvage the package as described here:
> >>> https://lists.debian.org/debian-devel/2012/09/msg00654.html
> >>> 
> >>> (please, involve the MIA team if you find neglected packages.)
> >>> 
> >>> Thanks for caring about goldendict,
> >>> --
> >>> tobi
> >> 
> >> Wondering if there's any concensus on this topic. Replies in this thread
> >> shows there are still some disagreement on concrete actions of
> >> "Salvaging" packages. An article on Debian Wiki or email on
> >> debian-devel-announce would be much more convincing.
> > 
> > We've had a discussion @DebConf17 (in the "if you love a package let it
> > go" BOF) where this link was brought up by the audience as an possible
> > solution to the problem that some packages are quite neglected. AFAIR it
> > was suggested that we've give the process a try.
> > 
> > While I understand that you'd like some official announcement, we're not
> > yet there -- this will only happen once we've tried it serveral times :)
> > But the salvaing process will for sure generate less friction than a
> > hijack.> 
> >> Besides, MIA Team is not the right option here; DDPO shows that the
> >> maintainer is still active on other packages. [2]
> > 
> > While the MIA team has power on cases like this, we also handle cases
> > where e.g the maintainer has appearantly too much on his plate; at least
> > we can get in touch with the maintainer and indeed that helps quite often
> > to find a solution. (Note that I am also MIA team member)
> > 
> >> Thanks,
> >> Boyuan Yang
> >> 
> >> [2] https://qa.debian.org/developer.php?email=unera%40debian.org
> 
> If You want to be a maintainer, feel free to add to uploader's
> list yourself . I uploaded the package if someone asked me or if I
> found some new interesting functions.
> So if You need to upload a new version, ping me, or adopt the package if
> you consider my work unsatisfactory :)

Thank you for your mail. I believe this NMU should act as the beginning of 
adoption. I am willing to package its newer snapshots and fix bugs later.

It would be great if somebody could help sponsor this NMU now since the 
original maintainer shows up and agrees with it.

Many thanks to everyone involved here. (especially the MIA team)

Regards,
Boyuan Yang

Bug#872196: closing 872196

[Boyuan Yang]

close 872196 
thanks

Sponsored by SZ Lin.

Thanks,
Boyuan Yang

Bug#870042: closing 870042

[Boyuan Yang]

close 870042 
thanks

Already sponsored and entered NEW queue.

Thanks,
Boyuan Yang

Bug#874428: RFS: goldendict/1.5.0~git20160508.g92b5485-1.2 [RC, NMU]

[Boyuan Yang]

在 2017年9月6日星期三 CST 上午7:44:25，Tobias Frost 写道：
> On Wed, Sep 06, 2017 at 12:11:57PM +0800, Boyuan Yang wrote:
> 
> Man thanks Boyuan for taking care about goldendict!
> 
> > Dear mentors and Dmitry,
> > 
> >* Add myself into uploaders list. (Hijacking package)
> 
> As I learned on DebConf17'S we've have a (proposed) process for
> this. Lets bring it to live and salvage the package as described here:
> https://lists.debian.org/debian-devel/2012/09/msg00654.html
> 
> (please, involve the MIA team if you find neglected packages.)
> 
> Thanks for caring about goldendict,
> --
> tobi

Wondering if there's any concensus on this topic. Replies in this thread shows 
there are still some disagreement on concrete actions of "Salvaging" packages. 
An article on Debian Wiki or email on debian-devel-announce would be much more 
convincing.

Besides, MIA Team is not the right option here; DDPO shows that the maintainer 
is still active on other packages. [2]

Thanks,
Boyuan Yang

[2] https://qa.debian.org/developer.php?email=unera%40debian.org

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

Bug#874428: RFS: goldendict/1.5.0~git20160508.g92b5485-1.2 [RC, NMU]

[Boyuan Yang]

Package: sponsorship-requests
Severity: important
X-Debbugs-CC: un...@debian.org

Dear mentors and Dmitry,

I am looking for a sponsor for Dmitry's package "goldendict". This would be an 
NMU and I would like to see it into DELAYED/7. Detailed explanations at 
bottom.

 * Package name: goldendict
   Version : 1.5.0~git20160508.g92b5485-1.2
   Upstream Author : Abs62 
 * URL : http://goldendict.org
 * License : GPL-3+
   Section : utils

  It builds those binary packages:

goldendict - feature-rich dictionary lookup program

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

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

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

dget -x https://mentors.debian.net/debian/pool/main/g/goldendict/
goldendict_1.5.0~git20160508.g92b5485-1.2.dsc

  Debomatic build result:

http://debomatic-amd64.debian.net/distribution#unstable/goldendict/
1.5.0~git20160508.g92b5485-1.2/buildlog

  Changes since last upload:

 goldendict (1.5.0~git20160508.g92b5485-1.2) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Ack previous upload. Thank you Gianfranco!
   * Add myself into uploaders list. (Hijacking package)
   * Add watch file. (Closes: #793039)
   * Update Vcs-* field. (Closes: #864667)
   * Drop .install file. (Closes: #837677)
   * Drop .menu file as per ctte's decision.
   * Build against Qt5. (Closes: #784468)

  Source debdiff attached.

  Explanations:

Package goldendict hasn't seen any updates since Jun 2016. Bug accumulated and 
now we have RC bug (Qt4 removal). Goldendict can be built against Qt5 without 
any problems.

I have been submitting bugs/patches and pushing experimental commits into 
packaging Git repository (on collab-maint) since last year. With lots of 
emails, However, I could not get *any* reply from the original maintainer.

Now in September 2017, I decide to do some NMUs to fix lasting problems. With 
Dmitry in LowThresholdNMU list [1], I think it might be even better if I could 
be added into uploaders list as well. I use goldendict often and am willing to 
maintain this package in the long term.

Dmitry, please tell me your opinion towards the maintenance of goldendict 
package. I am more than willing to push new upstream versions or prepare NMUs 
as you wish.

For mentors interested in this package, please check this NMU again and help 
sponsor it if you find it appropriate. Any suggestions would be welcome too.

Thanks,
Boyuan Yang

[1] https://wiki.debian.org/LowThresholdNmudiff -Nru goldendict-1.5.0~git20160508.g92b5485/debian/changelog goldendict-1.5.0~git20160508.g92b5485/debian/changelog
--- goldendict-1.5.0~git20160508.g92b5485/debian/changelog	2016-06-04 00:14:27.0 +0800
+++ goldendict-1.5.0~git20160508.g92b5485/debian/changelog	2017-09-06 10:44:58.0 +0800
@@ -1,3 +1,16 @@
+goldendict (1.5.0~git20160508.g92b5485-1.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Ack previous upload. Thank you Gianfranco!
+  * Add myself into uploaders list. (Hijacking package)
+  * Add watch file. (Closes: #793039)
+  * Update Vcs-* field. (Closes: #864667)
+  * Drop .install file. (Closes: #837677)
+  * Drop .menu file as per ctte's decision.
+  * Build against Qt5. (Closes: #784468)
+
+ -- Boyuan Yang <073p...@gmail.com>  Wed, 06 Sep 2017 10:44:58 +0800
+
 goldendict (1.5.0~git20160508.g92b5485-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru goldendict-1.5.0~git20160508.g92b5485/debian/control goldendict-1.5.0~git20160508.g92b5485/debian/control
--- goldendict-1.5.0~git20160508.g92b5485/debian/control	2015-09-23 17:25:35.0 +0800
+++ goldendict-1.5.0~git20160508.g92b5485/debian/control	2017-09-06 10:44:58.0 +0800
@@ -2,6 +2,8 @@
 Priority: optional
 Section: utils
 Maintainer: Dmitry E. Oboukhov 
+Uploaders:
+ Boyuan Yang <073p...@gmail.com>,
 Standards-Version: 3.9.6
 Build-Depends: cdbs, debhelper (>= 7),
  libeb16-dev,
@@ -13,19 +15,22 @@
  libxtst-dev,
  libbz2-dev,
  libhunspell-dev,
- libphonon-dev,
- libqt4-dev (>= 4.5.1),
- libqtwebkit-dev,
+ libphonon4qt5-dev,
+ libqt5webkit5-dev,
+ libqt5x11extras5-dev,
+ libqt5svg5-dev,
  libvorbis-dev,
  libx11-dev,
- libxtst-dev,
  pkg-config,
- qt4-qmake,
+ qtbase5-dev,
+ qttools5-dev,
+ qttools5-dev-tools,
+ qt5-qmake,
  x11proto-record-dev,
- zlib1g-dev
+ zlib1g-dev,
 Homepage: http://goldendict.org
-VCS-Browser: http://git.debian.org/?p=collab-maint/goldendict.git;a=summary
-VCS-Git: git://git.debian.org/collab-maint/goldendict.git
+Vcs-Browser: https://anonscm.debian.org/git/collab-maint/goldendict.git
+Vcs-Git: https://anonscm.debian.org/git/collab-maint/goldendict.git
 
 Package: goldendict
 Suggests: goldendict-wordnet
@@ -60,4 +65,4 @@
 translation of a word chosen from another application.
   * Support for global hotkeys. You can spawn the program window at
 

Bug#872973: closing 872973

[Boyuan Yang]

close 872973 0.6.4-1
thanks

Sponsored by aron@ .

Thanks,
Boyuan Yang

Bug#872973: RFS: iptux/0.6.4-1 [RC]

[Boyuan Yang]

Package: sponsorship-requests
Severity: important
X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org

Dear mentors,

I am looking for a sponsor for the package "iptux"

 * Package name: iptux
   Version : 0.6.4-1
   Upstream Author : LI Daobing 
 * URL : https://github.com/iptux-src/iptux/
 * License : GPL-2+
   Section : net


  It builds those binary packages:

iptux - Intranet communication tool for Linux

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/i/iptux/
iptux_0.6.4-1.dsc

  Git packaging repository:

https://anonscm.debian.org/git/chinese/iptux.git

  Changes since the last upload:

 iptux (0.6.4-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release (2017-08-22)
 + Fix FTBFS with gcc-7 (Closes: #853458)
   * Remove LI Daobing from uploaders list. (Closes: 841794).
 Thank you for your previous work.
   * Bump debhelper compat to v10.
   * Apply wrap-and-sort -abst.
   * Update debian/control file.
 - Remove build-dep autotools-dev. (not needed)
 + Bump Standards-Version to 4.1.0.
   * Update debian/rules file.
 + Add full hardening and --as-needed linker option.
   * Add myself into debian/copyright list.
   * Fix a typo in debian/iptux.1.

Regards,
Boyuan Yang

Bug#872971: RFS: gmchess/0.29.6-3 [RC]

[Boyuan Yang]

Package: sponsorship-requests
Severity: important
X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org

Dear mentors and chinese-developers folks,

I am looking for a sponsor for the package "gmchess".

 * Package name: gmchess
   Version : 0.29.6-3
   Upstream Author : lerosua 
 * URL : [defunct]
 * License : GPL-2+
   Section : games

  It builds those binary packages:

convert-pgn - chess book format converter
 eleeye - Chinese chess (Xiangqi) engine
 gmchess- Chinese chess game (Xiangqi)
 libeval0   - support library for eleeye
 libeval0-dev - support library for eleeye - development file

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/g/gmchess/
gmchess_0.29.6-3.dsc

  Git packaging repository:

https://anonscm.debian.org/git/chinese/gmchess.git

  Changes since last upload:

 gmchess (0.29.6-3) unstable; urgency=medium
 .
   * Team Upload.
   * Add myself into uploaders list.
   * Ack previous NMU. Thanks Adrian!
   * Drop debian/menu file (should not coexist with desktop file).
   * Bump debhelper compat to v10.
 + Drop dep autotools-dev, not needed.
   * Update Standards-Version to 4.1.0.
   * Add patch to fix FTBFS with gcc-7. Closes: #853423

Regards,
Boyuan Yang

Bug#872530: RFS: qevercloud/3.0.3+ds-3 [RC]

[Boyuan Yang]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name: qevercloud
   Version : 3.0.3+ds-3
   Upstream Author : Dmitry Ivanov 
 * URL : https://github.com/d1vanov/QEverCloud
 * License : MIT
   Section : libs

  It builds those binary packages:

libqt5qevercloud3 - Unofficial Evernote Cloud API library for Qt5
 qevercloud-doc - QEverCloud library documentation
 qt5qevercloud-dev - Development files for libqt5qevercloud

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/q/qevercloud/
qevercloud_3.0.3+ds-3.dsc

  Git packaging repo on Alioth:

https://anonscm.debian.org/git/collab-maint/qevercloud.git

This upload would drop Qt4 packages (to cooperate with Qt4's removal) and fix 
the RC bug #871202.

 Changes since the last upload:

 qevercloud (3.0.3+ds-3) unstable; urgency=medium
 .
   * d/patches: refresh patch 0003 to fix FTBFS with gcc-7.
 (Closes: #871202)
   * d/control: bump Standards-Version to 4.0.1 (no changes needed)
   * d/control: remove Qt4-related package for upcoming Qt4 removal.
   * d/rules: review and remove Qt4 related instructions.

Regards,
Boyuan Yang

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

Bug#870621: closing 870621

[Boyuan Yang]

close 870621 
thanks

Sponsored by szlin@. Thanks!

Regards,
Boyuan Yang

Bug#870042: RFS: gsettings-qt/0.1+16.04.20170729-1 [ITP]

[Boyuan Yang]

2017-07-31 9:07 GMT+08:00 Boyuan Yang <073p...@gmail.com>:
> 2017-07-31 9:04 GMT+08:00 Lisandro Damián Nicanor Pérez Meyer
> :
>> On sábado, 29 de julio de 2017 11:21:40 -03 Pino Toscano wrote:
>>> Hi,
>>>
>>> I'm not uploading it myself,
>>
>> Neither me, but I wanted to add some more info to what Pino already provided.
>>
>>> but there are various things that ought to
>>> be fixed:
>>>
>>> a) qtchooser is not needed in Build-Depends, it's an "implementation
>>>detail"
>>
>> You might want to take a look at
>>
>> <http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html>
>>
>>> b) we don't use a "qtdeclarative5-" prefix for QML modules, but
>>>"qml-module-"
>>
>> See <http://pkg-kde.alioth.debian.org/qmlmodulesnaming.html>
>>
>>
>>
>> --
>> Alas, I am dying beyond my means.
>>   Oscar Wilde, as he sipped champagne on his deathbed
>>
>> Lisandro Damián Nicanor Pérez Meyer
>> http://perezmeyer.com.ar/
>> http://perezmeyer.blogspot.com/
>
> Thank you all for the detailed review, which really helps.
>
> I'm not really familiar with C++/Qt/KDE packaging but this package
> falls in this range as a dependency unfortunately.
> I will read those instructions and fix problems.
>
> Regards,
> Boyuan Yang

OK. All problems mentioned above should be fixed now, both in git repo
and source package
on mentors.debian.net. (Many thanks to pino@ and perezmeyer.)

Future development and upstream maintenance is likely be taken by
Deepin Co.,Ltd. if
Canonical quits since Deepin software depends on this package heavily.
Pkg-deepin team
is working together with deepin upstream on it. As a result I believe
n) should not be a blocker
for package uploading.

Package maintainer was set back to pkg-deepin since we are taking care
of it in reality. Thanks
for the suggestion.

After enabling the test, this package would fail one test in Debian
Unstable. Investigations show
that it is a bug of Qt 5.7. [1][2] This bug has been fixed since Qt 5.8.
Qt in Ubuntu already have this bug fixed by backporting upstream patch.

With no visible time schedule for new Qt in Debian, I choose to
disable that test for now and re-enable
it after Qt 5.9 enters unstable. Meanwhile, anyone interested please
consider reviewing the package
again and help sponsor this package if you feel comfortable. This
package is blocking the workflow of
pkg-deepin team and it would be great if we could get the problem
fixed in a reasonable time period.

* https://anonscm.debian.org/git/collab-maint/gsettings-qt.git
* https://mentors.debian.net/package/gsettings-qt

[1] https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1624251
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871265

Regards,
Boyuan Yang

Bug#870621: RFS: deepin-gettext-tools/1.0.6+git20170811-1 [ITP]

[Boyuan Yang]

Reopening this bug to circumvent accidentally removal of package from 
mentors.d.n.

Mentors.debian.net keeps rejecting the new upload (403 forbidden). I will 
reupload the source package once cronjob on the server have the cruft cleaned 
up (maybe several hours later). Meanwhile, you may still check package status 
from debomatic-amd64 or alioth git repository as previously mentioned in the 
bug report.

Thanks,
Boyuan Yang

Bug#870621: RFS: deepin-gettext-tools/1.0.6+git20170731-1 [ITP]

[Boyuan Yang]

在 2017年8月11日星期五 CST 上午9:32:49，ChangZhuo Chen (陳昌倬) 写道：
> On Fri, Aug 11, 2017 at 04:00:57PM +0800, Boyuan Yang wrote:
> > Hi Liang,
> > 
> > I have those problems fixed in Git repository as well as uploaded source
> > package on
> > debomatic-amd64.d.n and mentors.d.n:
> > 
> > * https://anonscm.debian.org/git/pkg-deepin/deepin-gettext-tools.git
> 
> * The license of src/desktop_ts_convert.pl is GPL-3, not GPL-3+.
> 
> Other part look good to me.

My fault. Rechecked and this problem is fixed in Git repository now. I have 
also asked upstream whether they would unify script license to GPL-3+ in next 
commit/release.

Build result also available on debomatic-amd64:

http://debomatic-amd64.debian.net/distribution#unstable/deepin-gettext-tools/
1.0.6+git20170811-1/buildlog

Regards,
Boyuan Yang

Bug#870621: RFS: deepin-gettext-tools/1.0.6+git20170731-1 [ITP]

[Boyuan Yang]

X-Debbugs-CC: pkg-deepin-de...@lists.alioth.debian.org

在 2017年8月3日星期四 CST 下午11:44:31，Liang Guo 写道：
> Hi,
> 
> I have a quick look of this package, this is my comment:
> 
> * d/compat should be 10
> *  please ask upstrem to add license header to  desktop_ts_convert.pl
> and  policy_ts_convert.py
> * please fix binary-without-manpage lintian warning.
> 
> Thanks,

Hi Liang,

I have those problems fixed in Git repository as well as uploaded source 
package on
debomatic-amd64.d.n and mentors.d.n:

* https://anonscm.debian.org/git/pkg-deepin/deepin-gettext-tools.git
* 
http://debomatic-amd64.debian.net/distribution#unstable/deepin-gettext-tools/1.0.6+git20170811-1/buildlog

Please help review and sponsor this upload if you find it appropriate.

Thanks!

--
Regards,
Boyuan Yang

Bug#870621: RFS: deepin-gettext-tools/1.0.6+git20170731-1 [ITP]

[Boyuan Yang]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: pkg-deepin-de...@lists.alioth.debian.org czc...@debian.org 
bluestonech...@gmail.com

Dear mentors,

I am looking for a sponsor for my package "deepin-gettext-tools"

 * Package name: deepin-gettext-tools
   Version : 1.0.6+git20170731-1
   Upstream Author : Deepin Technology Co., Ltd.
 * URL : https://github.com/linuxdeepin/deepin-gettext-tools
 * License : GPL-3+
   Section : devel

This package is Deepin's wrapper to various gettext tools. It is the build 
dependency
to various Deepin software.

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

  https://mentors.debian.net/package/deepin-gettext-tools


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-gettext-tools/deepin-gettext-tools_1.0.6+git20170731-1.dsc

  Build status on debomatic-amd64:


http://debomatic-amd64.debian.net/distribution#unstable/deepin-gettext-tools/1.0.6+git20170731-1/buildlog

  Git packaging repository:

https://anonscm.debian.org/git/pkg-deepin/deepin-gettext-tools.git/

  Changes since last upload:

 deepin-gettext-tools (1.0.6+git20170731-1) unstable; urgency=medium
 .
   * Initial Release. (Closes: #870380)

Regards,
Boyuan Yang

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

Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]

[Boyuan Yang]

在 2017年7月31日星期一 CST 下午1:00:02，Liang Guo 写道：
> On Mon, Jul 31, 2017 at 10:17 AM, Boyuan Yang <073p...@gmail.com> wrote:
> > Sure. I have reminded them of this issue. I will update debian/copyright
> > file as soon as new upstream version (with fixes) gets released. My
> > opinion is that this issue shouldn't be a blocker for upload.
> 
> IMO, upstream should fix this problem BEFORE it can be uploaded to Debian,
> But I'm not sure if it is madated in Debian, I advice you raise this
> problem in debian-devel
> or debian-legel maillist.

According to my understanding [1], this should be a recommendation and not a 
requirement for using (L)GPL licenses.

Anyway I prepared a new snapshot for dtkcore with upstream fixes:

* https://anonscm.debian.org/git/pkg-deepin/dtkcore.git
* https://mentors.debian.net/package/dtkcore

I am still working with upstream to track their changes. Maybe we should push 
an initial version into Debian archive first.

[1] https://www.gnu.org/licenses/gpl-faq.html#NoticeInSourceFile

Regards,
Boyuan Yang

Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]

[Boyuan Yang]

在 2017年7月31日星期一 CST 下午1:31:22，Liang Guo 写道：
> On Mon, Jul 31, 2017 at 1:13 PM, Boyuan Yang <073p...@gmail.com> wrote:
> >>> Meanwhile, source packages on debomatic-amd64, mentors.d.o and Git
> >>> repository has been updated already to fix problems of non-existent
> >>> pkg-deepin team (See #868544). I believe the source package should be
> >>> ready for an upload.>> 
> >> Cannot you cate pkg-deepin team in alioth?  It's a good idea to
> >> maintain package by
> >> team.
> > 
> > Unfortunately not at this time. I asked on #alioth yesterday but no
> > one stepped out to deal with the team creation request.  formorer said
> > it is not his part of job and I don't know who is going to take care
> > of related works.
> 
> I have created project pkg-deepin on alioth, pease join in
> 
> https://alioth.debian.org/projects/pkg-deepin/

Registered and entered the group. Thank you very much!

Regards,
Boyuan Yang


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

Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]

[Boyuan Yang]

2017-07-31 13:00 GMT+08:00 Liang Guo :
> On Mon, Jul 31, 2017 at 10:17 AM, Boyuan Yang <073p...@gmail.com> wrote:
>>
>> Sure. I have reminded them of this issue. I will update debian/copyright file
>> as soon as new upstream version (with fixes) gets released. My opinion is 
>> that
>> this issue shouldn't be a blocker for upload.
> IMO, upstream should fix this problem BEFORE it can be uploaded to Debian, But
> I'm not sure if it is madated in Debian, I advice you raise this
> problem in debian-devel

Perhaps. I will try to urge upstream to make a new tag (release) with
the fix to circumvent this problem.

> or debian-legel maillist.
>
>>
>> Meanwhile, source packages on debomatic-amd64, mentors.d.o and Git repository
>> has been updated already to fix problems of non-existent pkg-deepin team (See
>> #868544). I believe the source package should be ready for an upload.
> Cannot you cate pkg-deepin team in alioth?  It's a good idea to
> maintain package by
> team.

Unfortunately not at this time. I asked on #alioth yesterday but no
one stepped out to deal with the team creation request.  formorer said
it is not his part of job and I don't know who is going to take care
of related works.


If I write down pkg-deepin now in d/control, the package will be
rejected according to ftp-masters' words.

>
> Thanks,
> --
> Liang Guo

Regards,
Boyuan Yang

Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]

[Boyuan Yang]

在 2017年7月31日星期一 CST 上午9:53:58，Liang Guo 写道：
> Have you ask upstream to correct source file's license header ?
> 
> Thanks,

Sure. I have reminded them of this issue. I will update debian/copyright file 
as soon as new upstream version (with fixes) gets released. My opinion is that 
this issue shouldn't be a blocker for upload.

Meanwhile, source packages on debomatic-amd64, mentors.d.o and Git repository 
has been updated already to fix problems of non-existent pkg-deepin team (See 
#868544). I believe the source package should be ready for an upload.

Regards,
Boyuan Yang

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

Bug#870042: RFS: gsettings-qt/0.1+16.04.20170729-1 [ITP]

[Boyuan Yang]

2017-07-31 9:04 GMT+08:00 Lisandro Damián Nicanor Pérez Meyer
:
> On sábado, 29 de julio de 2017 11:21:40 -03 Pino Toscano wrote:
>> Hi,
>>
>> I'm not uploading it myself,
>
> Neither me, but I wanted to add some more info to what Pino already provided.
>
>> but there are various things that ought to
>> be fixed:
>>
>> a) qtchooser is not needed in Build-Depends, it's an "implementation
>>detail"
>
> You might want to take a look at
>
> <http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html>
>
>> b) we don't use a "qtdeclarative5-" prefix for QML modules, but
>>"qml-module-"
>
> See <http://pkg-kde.alioth.debian.org/qmlmodulesnaming.html>
>
>
>
> --
> Alas, I am dying beyond my means.
>   Oscar Wilde, as he sipped champagne on his deathbed
>
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/

Thank you all for the detailed review, which really helps.

I'm not really familiar with C++/Qt/KDE packaging but this package
falls in this range as a dependency unfortunately.
I will read those instructions and fix problems.

Regards,
Boyuan Yang

Bug#868544: Debian Bug #868544: RFS (dtksettings) Rejected

[Boyuan Yang]

X-Debbugs-CC: czc...@debian.org felixonm...@archlinux.org

在 2017年7月29日星期六 CST 下午6:08:37，Gianfranco Costamagna 写道：
> Seems to have been rejected
> 
> G.

Ack. The package is rejected since pkg-deepin does not exist (yet) on Alioth.

Here is the plan:

* Poke Alioth admins on IRC #alioth and DebConf (with the help of debconf 
attendees) and see when will pkg-deepin be set up.

* Before that, temporarily set packages as self-maintained.

Regards,
Boyuan Yang

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

Bug#870042: RFS: gsettings-qt/0.1+16.04.20170729-1 [ITP]

[Boyuan Yang]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: czc...@debian.org debian-qt-...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "gsettings-qt".

 * Package name: gsettings-qt
   Version : 0.1+16.04.20170729-1
   Upstream Author : Canonical Ltd.
 * URL : https://launchpad.net/gsettings-qt
 * License : LGPL-3
   Section : libs


  It builds those binary packages:

 libgsettings-qt-dev - Library to access GSettings from Qt - devel
 libgsettings-qt1 - Library to access GSettings from Qt
 qtdeclarative5-gsettings1.0 - QML Bindings for GSettings

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

  https://mentors.debian.net/package/gsettings-qt

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

dget -x https://mentors.debian.net/debian/pool/main/g/gsettings-qt/
gsettings-qt_0.1+16.04.20170729-1.dsc

  Alternatively, one can view build status on deb-o-matic amd64:
dget -x http://debomatic-amd64.debian.net/debomatic/unstable/pool/
gsettings-qt_0.1+16.04.20170729-1/gsettings-qt_0.1+16.04.20170729-1.dsc

  Git packaging repository can be found on Alioth:
https://anonscm.debian.org/git/collab-maint/gsettings-qt.git

  Changes since last upload:

 gsettings-qt (0.1+16.04.20170729-1) unstable; urgency=medium
 .
   * Initial Release in Debian. (Closes: #870031)
   * Fix FTBFS problem due to incorrect link path. (LP: #1706682)

Regards,
Boyuan Yang

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

Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]

[Boyuan Yang]

2017-07-27 22:47 GMT+08:00 Liang Guo :
> On Thu, Jul 27, 2017 at 10:25 PM, ChangZhuo Chen  wrote:
>> On Thu, Jul 27, 2017 at 09:30:52PM +0800, Boyuan Yang wrote:
>>>   Alioth packaging repository:
>>>
>>> https://anonscm.debian.org/git/collab-maint/dtkcore.git
>>
>> * The copyrights in src/log/* are different from other files, please
>>   check copyright header of every file and list them in
>>   debian/copyright.
>>
>> * This symbol control file for libdtkcore.so is missing. Please help to
>>   add it.
>
> Agree, beside these problem, please notice:
>
> * debian/docs is empty please remove
>
> * Their should be an short license declaration in each *.{c,h,cpp}
> file.  For GPL3 license files, the short license should like this:
> 
> Copyright (C)   
>
> This program is free software: you can redistribute it and/or modify
> it under the terms of the GNU General Public License as published by
> the Free Software Foundation, either version 3 of the License, or
> (at your option) any later version.
>
> This program is distributed in the hope that it will be useful,
> but WITHOUT ANY WARRANTY; without even the implied warranty of
> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> GNU General Public License for more details.
>
> You should have received a copy of the GNU General Public License
> along with this program.  If not, see <http://www.gnu.org/licenses/>.
>
> Please ask the original author to complete the license declaration.
>
> * debian/copyright file should obey DEP-5 proposal[1]
>
>
> [1] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>
>
> --
> Liang Guo
> http://guoliang.me/

Thank you all for detailed review with this package.

I have checked the packaging src again with check-all-the-things and
fixed all problems that can be fixed in debian/ directory. d/copyright
information has been updated after manual check with the source code.

Detailed changes can be found on
anonscm.debian.org/git/collab-maint/dtkcore.git git repository. Source
packages on mentors.d.o and debomatic-amd64.d.o are also updated
accordingly.

Thanks,
Boyuan Yang

Bug#869898: RFS: dtkcore/0.3.3-1 [ITP]

[Boyuan Yang]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: czc...@debian.org

Dear mentors,

I am looking for a sponsor for my package "dtkcore".

This source package provides a library used by various software from Deepin 
Linux. This is the dependency of many Deepin software and DDE (Deepin Desktop 
Environment).

This package is parallel with previous "dtksettings" thus can be uploaded at 
the same time without conflicts/dependency problems.

* Package name: dtkcore
  Version : 0.3.3-1
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://www.deepin.org/
   Section : devel

  It builds those binary packages:

 libdtkcore-dev - Deepin Tool Kit Core Devel library
 libdtkcore1 - Deepin Tool Kit Core library

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

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

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

dget -x https://mentors.debian.net/debian/pool/main/d/dtkcore/
dtkcore_0.3.3-1.dsc

  Alternatively, one can retrieve more information from debomatic-amd64:

http://debomatic-amd64.debian.net/distribution#unstable/dtkcore/0.3.3-1/

  Alioth packaging repository:

https://anonscm.debian.org/git/collab-maint/dtkcore.git

   More information about hello can be obtained from https://github.com/
linuxdeepin/dtkcore .

  Changes since the last upload:

 dtkcore (0.3.3-1) unstable; urgency=medium
 .
   * Initial release (Closes: #869894)

Regards,
Boyuan Yang

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

Bug#868544: closing 868544

[Boyuan Yang]

close 868544 
thanks

Sponsored by czchen@. Thx!

Regards,
Boyuan Yang

Bug#868827: closing 868827

[Boyuan Yang]

close 868827 
thanks

Closing this one, duplicated with #868544.

Bug#868544: RFS: dtksettings/0.1.7-1 [ITP]

[Boyuan Yang]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org

Dear mentors and chinese-developers folks,

I am looking for a sponsor for my package "dtksettings".

This source package provides libraries and a simple tool to deal with json 
configurations files used by softwares from Deepin Linux. This is the 
dependency 
of many Deepin softwares and DDE (Deepin Desktop Environment).

Note that the missing man page for /usr/bin/dtk-settings-tool: upstream does 
not provide any man pages for this simple wrapper tool. I intent to open a 
Debian bug and forward it to upstream after the initial upload.

* Package name: dtksettings
  Version : 0.1.7-1
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://github.com/linuxdeepin/dtksettings
   Section : devel

  It builds those binary packages:

libdtksettings-bin - Deepin Tool Kit Settings tool
 libdtksettings-dev - Deepin Tool Kit Settings library (development files)
 libdtksettings1 - Deepin Tool Kit Settings library
 libdtksettingsview-dev - Deepin Tool Kit Settings UI library (development 
files)
 libdtksettingsview1 - Deepin Tool Kit Settings UI library

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

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

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

dget -x https://mentors.debian.net/debian/pool/main/d/dtksettings/
dtksettings_0.1.7-1.dsc

  Alternatively, one can retrieve more information from debomatic-amd64:

http://debomatic-amd64.debian.net/distribution#unstable/dtksettings/
0.1.7-1/

  Alioth packaging repository:

https://anonscm.debian.org/git/collab-maint/dtksettings.git

   More information about hello can be obtained from https://github.com/
linuxdeepin/dtksettings .

  Changes since the last upload:

 dtksettings (0.1.7-1) unstable; urgency=medium
 .
   * Initial release (Closes: #868494)

Regards,
Boyuan Yang

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

Bug#867149: RFS: galternatives/0.13.5+nmu3+deb8u1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "galternatives" into *oldstable* 
(jessie-pu).

 * Package name: galternatives
   Version : 0.13.5+nmu3+deb8u1
   Upstream Author : [not active]
 * URL : [defunct]
 * License : GPL-1+
   Section : admin

It builds those binary package(s):
galternatives - graphical setup tool for the alternatives system

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/g/galternatives/
galternatives_0.13.5+nmu3+deb8u1.dsc

  Alternatively, one can view built package on deb-o-matic-amd64:

http://debomatic-amd64.debian.net/distribution#oldstable/galternatives/
0.13.5+nmu3+deb8u1/buildlog

  Git repository on Alioth:
https://anonscm.debian.org/git/collab-maint/galternatives.git/log/?
h=jessie

Changes since last upload:

 galternatives (0.13.5+nmu3+deb8u1) jessie; urgency=medium
 .
   * Adopt package, switch maintainer information.
   * Fix the bug which causes properties window blank. Closes: #325172

Explanations:

* This (old)stable upload was approved by stable release managers.
  See http://bugs.debian.org/866967 .

* Bug #325172 was already fixed in Debian testing/unstable in galternatives/
0.13.6 and Debian Stretch in galternatives/0.13.5+nmu4+deb9u1 in stretch-pu.


Regards,
Boyuan Yang

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

Bug#866199: RFS: shadowsocks-libev/3.0.7+ds-1

[Boyuan Yang]

Package: sponsorship-requests
X-Debbugs-CC: Roger Shimizu 
Severity: normal

Dear mentors,

I am looking for a sponsor for co-maintained package "shadowsocks-libev".

 * Package name: shadowsocks-libev
   Version : 3.0.7+ds-1
   Upstream Author : Max Lv 
 * URL : https://shadowsocks.org
 * License : GPL-3+
   Section : net

  It builds those binary packages:

libshadowsocks-libev-dev - lightweight and secure socks5 proxy 
(development files)
 libshadowsocks-libev2 - lightweight and secure socks5 proxy (shared library)
 shadowsocks-libev - lightweight and secure socks5 proxy

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

  https://mentors.debian.net/package/shadowsocks-libev


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

dget -x https://mentors.debian.net/debian/pool/main/s/shadowsocks-libev/
shadowsocks-libev_3.0.7+ds-1.dsc

  Alternatively, one can retrieve built packages from deb-o-matic-amd64:

http://debomatic-amd64.debian.net/distribution#unstable/shadowsocks-libev/
3.0.7+ds-1/buildlog

  Alioth Git repo:

https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git

  Changes since the last upload:

 shadowsocks-libev (3.0.7+ds-1) unstable; urgency=medium
 .
   * New upstream release 3.0.7
   * debian/control:
 Bump Standards-Version to 4.0.0, no changes required.
   * debian/patches:
 - drop all backported patches.

Regards,
Boyuan Yang

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

Bug#866088: RFS: galternatives/0.13.5+nmu4+deb9u1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "galternatives" into *stable* 
(stretch-pu).

 * Package name: galternatives
   Version : 0.13.5+nmu4+deb9u1
   Upstream Author : [not active]
 * URL : [defunct]
 * License : GPL-1+
   Section : admin

It builds those binary package(s):
galternatives - graphical setup tool for the alternatives system

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/g/galternatives/
galternatives_0.13.5+nmu4+deb9u1.dsc

  Alternatively, one can view built package on deb-o-matic-amd64:

http://debomatic-amd64.debian.net/distribution#stable/galternatives/
0.13.5+nmu4+deb9u1/buildlog

  Git repository on Alioth:
https://anonscm.debian.org/git/collab-maint/galternatives.git/log/?
h=stretch

Changes since last upload:

 galternatives (0.13.5+nmu4+deb9u1) stretch; urgency=medium
 .
   * Adopt and switch maintainer information.
   * Fix the bug which causes properties window blank. Closes: #325172

Explanations:

* This stable upload was approved by stable release managers.
  See http://bugs.debian.org/864757 .

* Bug #325172 was already fixed in Debian testing/unstable in galternatives/
0.13.6 .


Regards,
Boyuan Yang


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

Bug#865669: RFS: nixnote2/2.0-1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: nixnote2
   Version : 2.0-1
   Upstream Author : Randy Baumgarte 
 * URL : http://nixnote.org
 * License : GPL-2+
   Section : utils

  It builds those binary packages:

nixnote2   - Open Source Evernote client

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

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

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

dget -x https://mentors.debian.net/debian/pool/main/n/nixnote2/
nixnote2_2.0-1.dsc

  Build logs on debomatic-amd64:

http://debomatic-amd64.debian.net/distribution#unstable/nixnote2/2.0-1/
buildlog

  Packaging git repository:

  https://anonscm.debian.org/git/collab-maint/nixnote2.git

  Changes since the last upload:

 nixnote2 (2.0-1) unstable; urgency=medium
 .
   * Upload to unstable.

Regards,
Boyuan Yang

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

Bug#864702: RFS: galternatives/0.13.6 [ITA]

[Boyuan Yang]

在 2017年6月13日星期二 +08 上午10:10:33，Boyuan Yang 写道：
> I am looking for a sponsor for adopted package "galternatives"
> It builds those binary package(s):
> galternatives - graphical setup tool for the alternatives system
> 
> Unfortunately mentors.d.o upload is temporarily 403 here, so one can
> download the package with dget using:
> 
> http://debomatic-amd64.debian.net/debomatic/unstable/pool/
> galternatives_0.13.6/galternatives_0.13.6.dsc

Now I am able to upload onto mentors.debian.net.
You may also retrieve source package from:

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

dget -x 
https://mentors.debian.net/debian/pool/main/g/galternatives/galternatives_0.13.6.dsc

https://anonscm.debian.org/git/collab-maint/galternatives.git

Thanks!

Regards,
Boyuan Yang


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

Bug#864702: RFS: galternatives/0.13.6 [ITA]

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org

Dear mentors and chinese-developers folks,

I am looking for a sponsor for adopted package "galternatives"

 * Package name: galternatives
   Version : 0.13.6
   Upstream Author : [not active anymore]
 * URL : [defunct]
 * License : GPL-1+
   Section : admin

It builds those binary package(s):
galternatives - graphical setup tool for the alternatives system

Unfortunately mentors.d.o upload is temporarily 403 here, so one can download 
the package with dget using:

http://debomatic-amd64.debian.net/debomatic/unstable/pool/
galternatives_0.13.6/galternatives_0.13.6.dsc

Or please use git repository on Alioth.d.o:

https://anonscm.debian.org/git/collab-maint/galternatives.git

Changes since last upload:

galternatives (0.13.6) unstable; urgency=medium

  * Adopt package. (Closes: #856289)
  * Fix the bug that properties subwindow become blank.
(Closes: #325172)
  * Apply "wrap-and-sort -abst".
  * d/compat: bump to v10.
  * d/menu: drop obsoleted xpm file and menu file.
  * debian/control:
+ Bump Standards-Version to 3.9.8. (No changes needed)
+ Bump dependency to debhelper to 10~.
+ Write collab-maint url for Vcs-*.
  * d/copyright: rewrite with machine-readable format.
- Explicitly mark license as GPL-1+ since original declaration
  only said "GPL".
  * d/rules:
+ Fix grammar for "dh" tool.
  * translation:
+ Refresh translations.
+ Add Simplified Chinese translation.
  * add a .gitignore file for .mo files.
  * bump "galternatives" python package version to 0.13.6.
  * remove obsoleted line for "list-mos.sh" in setup.py.

Regards,
Boyuan Yang

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

Bug#862070: RFS: nixnote2/2.0-1~exp1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "nixnote2" into experimental.

 * Package name: nixnote2
   Version : 2.0-1~exp1
   Upstream Author : Randy Baumgarte 
 * URL : http://nixnote.org
 * License : GPL-2+
   Section : utils

  It builds those binary packages:

nixnote2   - Open Source Evernote client

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

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

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

dget -x https://mentors.debian.net/debian/pool/main/n/nixnote2/
nixnote2_2.0-1~exp1.dsc

  Git packaging repository:

  https://anonscm.debian.org/git/collab-maint/nixnote2.git

  Deb-o-matic build log:

http://debomatic-amd64.debian.net/distribution#experimental/
nixnote2/2.0-1~exp1/buildlog

  Changes since the last upload:

 nixnote2 (2.0-1~exp1) experimental; urgency=medium
 .
   * New upstream stable release.
   * Update Homepage URL to use nixnote.org.
   * Refresh d/copyright information.
   * Refresh patches:
 + Drop old patches 0002-0004, applied upstream.
 + Cherry-pick upstream patch for command line import.
 + Cherry-pick upstream patch for plugin-path finding.

Sincerely,
Boyuan Yang

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

Bug#861757: RFS: fonts-fandol/0.3-1 [ITP]

[Boyuan Yang]

在 2017年5月4日星期四 CST 上午8:09:13，Paul Wise 写道：
> On Thu, 4 May 2017 00:38:24 +0200 Adam Borowski wrote:
> > I'm not entirely sure .otf are the real sources, despite the upstream
> > providing only otf.  For now, let's assume they are, unless there's
> > evidence to the contrary (not sure what the README means).
> 
> The README is pretty clear that the fonts are compile to OpenType using
> AFDKO from FontForge and or Inkscape source. AFDKO is not in Debian
> main so this font should go to contrib. In addition, no FontForge
> source format or SVG files were released and the font is under the
> GPL so I don't think we can distribute this at all. Please ask the
> ftp-masters to reject this package from NEW.

In the email from upstream, he seems unwilling to solve this so-called 
"problem" in his POV. OTF fonts and so-called "source" (CID postscript fonts) 
only differs on font encapsulation, which means they can convert to each other 
without losing information. That is different from typical compilation process. 
AFDKO is only a convert tool, not a compiler. Upstream said he is releasing 
.otf fonts under GPL and that should not bother with AFDKO or other tools, 
which is used in font development.

As a result, upstream (and I) are in doubt whether this would cause rejection 
in Debian.

There are lots of fonts in Debian with only .ttf or .otf fonts as source. Is 
there a convincing policy that regulates sources of fonts in Debian? (e.g.
what is "source" and what is "binary"?)

P.S. AFDKO packaging is being worked on packaging.
 (http://anonscm.debian.org/cgit/pkg-fonts/afdko.git)

--
Boyuan Yang

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

Bug#861757: RFS: fonts-fandol/0.3-1 [ITP]

[Boyuan Yang]

在 2017年5月4日星期四 +08 上午8:09:13，Paul Wise 写道：
> The README is pretty clear that the fonts are compile to OpenType using
> AFDKO from FontForge and or Inkscape source. AFDKO is not in Debian
> main so this font should go to contrib. In addition, no FontForge
> source format or SVG files were released and the font is under the
> GPL so I don't think we can distribute this at all. Please ask the
> ftp-masters to reject this package from NEW.

That's a pity. I'm contacting upstream author to see what we can do next. 
(e.g. releasing proper src and/or help packaging AFDKO #762252).

--
Boyuan Yang

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

Bug#861757: RFS: fonts-fandol/0.3-1 [ITP]

[Boyuan Yang]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "fonts-fandol"

 * Package name: fonts-fandol
   Version : 0.3-1
   Upstream Author : Clerk Ma 
 * URL : https://www.ctan.org/pkg/fandol
 * License : GPL-3 with fonts exception
   Section : fonts


  It builds those binary packages:

fonts-fandol - Fandol fonts designed for Chinese typesetting

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

  https://mentors.debian.net/package/fonts-fandol

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

dget -x 
https://mentors.debian.net/debian/pool/main/f/fonts-fandol/fonts-fandol_0.3-1.dsc

 Packaging Git repository:
https://anonscm.debian.org/git/collab-maint/fonts-fandol.git

 Changes since the last upload:

fonts-fandol (0.3-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #861720)

--
Sincerely,
Boyuan Yang

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

Bug#858083: RFS: libbloom/1.4-2

[Boyuan Yang]

Control: retitle -1 RFS: libbloom/1.4-2
Control: severity -1 normal

> If you create one repo in collab-maint, I'll mirror my repo there.

Everyone in collab-maint group can set up a repo (including yourself). Anyway 
here it is:

https://anonscm.debian.org/git/collab-maint/libbloom.git

--
Sincerely,
Boyuan Yang


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

Bug#857131: RFS: fgrun/2016.4.0-1 [RC]

[Boyuan Yang]

在 2017年4月10日星期一 +08 下午10:59:27，Markus Wanner 写道：
> @Boyuan: could you please:
> 
>  a) change the watch file to point to the github mirror and
> release tags you found? (Or provide some other way of automatically
> fetching an orig.tar.gz?)

Done. I'm using GitHub.

> 
>  b) commit your changes to alioth / collab-maint (do you have access,
> there?)

https://anonscm.debian.org/git/collab-maint/fgrun.git

Done. (master, upstream/2016.04 tag, pristine-tar)

> 
>  c) add yourself as an uploader, I'm happy to review and sponsor
> uploads of fgrun for you.

Done.

Source pkg:
https://mentors.debian.net/debian/pool/main/f/fgrun/fgrun_2016.4.0-1.dsc

Build status:
http://debomatic-amd64.debian.net/distribution#unstable/fgrun/2016.4.0-1/
buildlog

Changes:

 fgrun (2016.4.0-1) unstable; urgency=medium
 .
   * Team upload.
 + Acked by original maintainer.
   * New upstream release. (Closes: #839357)
 - Drop patches applied upstream.
 - Refresh patches.
   * Add myself onto uploaders list.
   * Switch upstream to GitHub mirror.
 - Update corresponding debian/watch file using GitHub. (Closes: #851845)
   * Bump debhelper compat version to v10.
   * Apply "wrap-and-sort -abst".
   * Update Homepage information on SourceForge.

Looking forward to your review and sponsorship.

--
Sincerely,
Boyuan Yang


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

Bug#859663: RFS: manpages-zh/1.6.3-1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "manpages-zh" into unstable.

Unblock request already filed and acked by release team (see #859631).

 * Package name: manpages-zh
   Version : 1.6.3-1
   Upstream Author : Boyuan Yang <073p...@gmail.com>
 * URL : https://github.com/man-pages-zh/manpages-zh
 * License : GFDL-1.2+
   Section : doc

It builds those binary packages:

manpages-zh - Chinese manual pages

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

  https://mentors.debian.net/package/manpages-zh

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

dget -x https://mentors.debian.net/debian/pool/main/m/manpages-zh/
manpages-zh_1.6.3-1.dsc

Alternatively, one can check build results on debomatic-amd64:

  http://debomatic-amd64.debian.net/distribution#unstable/manpages-zh/
1.6.3-1/

Commits pushed onto Alioth:

https://anonscm.debian.org/git/chinese/manpages-zh.git

Changes since the last upload:

 manpages-zh (1.6.3-1) unstable; urgency=medium
 .
   * Upload onto unstable.
   * Mark manpages-zh package Multi-Arch: foreign.

Regards,
Boyuan Yang

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

Bug#859604: RFS: manpages-zh/1.6.3-1~exp1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "manpages-zh" into experimental.

 * Package name: manpages-zh
   Version : 1.6.3-1~exp1
   Upstream Author : Boyuan Yang <073p...@gmail.com>
 * URL : https://github.com/man-pages-zh/manpages-zh
 * License : GFDL-1.2+
   Section : doc

It builds those binary packages:

manpages-zh - Chinese manual pages

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

  https://mentors.debian.net/package/manpages-zh

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

dget -x https://mentors.debian.net/debian/pool/main/m/manpages-zh/
manpages-zh_1.6.3-1~exp1.dsc

Alternatively, one can check build results on debomatic-amd64:

  http://debomatic-amd64.debian.net/distribution#unstable/manpages-zh/
1.6.3-1~exp1/

Commits pushed onto Alioth:

https://anonscm.debian.org/git/chinese/manpages-zh.git

Changes since the last upload:

 manpages-zh (1.6.3-1~exp1) experimental; urgency=medium
 .
   * New upstream release.
 + Add some translations for systemd man pages.

As the package maintainer and upstream maintainer, I would like to see the new 
version into experimental first to check if there is any file conflict. If 
everything is OK, I may request an unblock pre-approval before uploading onto 
unstable (since the debdiff would be huge).

Regards,
Boyuan Yang

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

Bug#859238: RFS: microsoft-gsl/0.1~2017.03.20~git16a6a41-1

[Boyuan Yang]

I suggest renaming microsoft to ms too. Otherwise this RFS might not be 
completed due to copyright concerns. It seems that all existing packages use 
"ms" instead of "microsoft".

Nicholas, what do you think?

--
Sincerely,
Boyuan Yang

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

Bug#859235: RFS: telegram-desktop/1.0.27-1 -- official telegram messaging application

[Boyuan Yang]

X-Debbugs-CC: Коля Гурьев 

Now that the RFS is blocked by other packages, could you please try to add 
patch for #859057? The patch is tested by someone on Ubuntu and is working 
well (at least on little-endian machines).

Plus, could you please add the workaround for #859172? The patch is simple but 
could avoid crashing on GTK-based DEs. We need a real solution in the future.

diff --git a/debian/control b/debian/control
index 91fa74cb..ffba1455 100644
--- a/debian/control
+++ b/debian/control
@@ -29,7 +29,7 @@ Vcs-Browser: https://github.com/mymedia2/tdesktop
 
 Package: telegram-desktop
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, qt5-image-formats-plugins 
(>=5.5)
+Depends: ${shlibs:Depends}, ${misc:Depends}, qt5-image-formats-plugins 
(>=5.5), libappindicator3-1
 Description: official telegram messaging app
  Telegram is a messaging app with a focus on speed and security, it is
  super-fast, simple and free. You can use Telegram on all your devices at the

--
Sincerely,
Boyuan Yang


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

Bug#857131: RFS: fgrun/2016.4.0-0.1 [RC, NMU]

[Boyuan Yang]

X-Debbugs-CC: pkg-fgfs-c...@lists.alioth.debian.org

在 2017年3月8日星期三 SGT 下午1:06:02，Markus Wanner 写道：
> I kind of allow developers to out-source that task (i.e. to github) and
> only provide tags. Unfortunately, I didn't find a similar solution with
> Sourceforge, yet. (It seems it's all there, but uscan would have to be
> extended to handle Sourceforge.)

I understand that tarballs are important and could greatly reduce extra works.

Fgrun is really important for flightgear and we should not leave it behind, so 
I made some investigations.

Good news: one of flightgear devs set up a mirror on GitHub and sync every 15 
minutes. If you don't mind using a (frequently synchronized) mirror as d/watch 
upstream, we could switch watch target onto GitHub (with proper tarball 
support) and update files in this RFS and/or Alioth Git repo. What do you 
think?

--
Sincerely,
Boyuan Yang

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

Bug#857131: RFS: fgrun/2016.4.0-0.1 [RC, NMU]

[Boyuan Yang]

OT}/${MSVC_3RDPARTY_DIR}/include ${MSVC_3RDPARTY_ROOT}/install/${OSG_MSVC}/OpenScenegraph/include ${MSVC_3RDPARTY_ROOT}/install/${OSG_MSVC}/SimGear/include)
+
+  GET_FILENAME_COMPONENT(MSVC_ROOT_PARENT_DIR ${MSVC_3RDPARTY_ROOT} PATH)
   find_path(BOOST_ROOT boost/version.hpp
+  ${MSVC_ROOT_PARENT_DIR}
 			${MSVC_3RDPARTY_ROOT}/boost
 			${MSVC_3RDPARTY_ROOT}/boost_1_51_0
 			${MSVC_3RDPARTY_ROOT}/boost_1_50_0
@@ -124,8 +130,8 @@
 
 set(NOMINMAX 1)
 set( WINSOCK_LIBRARY "ws2_32.lib" )
-
-endif(WIN32)
+
+endif(WIN32)
 
 set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} ${WARNING_FLAGS} ${MSVC_FLAGS} -D_REENTRANT")
 set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${WARNING_FLAGS} ${MSVC_FLAGS} -D_REENTRANT")
@@ -170,7 +176,7 @@
 	if (ENABLE_NLS)
 		set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -DENABLE_NLS")
 	endif (ENABLE_NLS)
-
+
 else (ENABLE_NLS AND GETTEXT_FOUND)
 
 set( INTL_LIBRARY "" )
@@ -224,7 +230,7 @@
 endif()
 
 if ( CMAKE_DL_LIBS )
-   list(APPEND FLTK_LIBRARIES ${CMAKE_DL_LIBS}) 
+   list(APPEND FLTK_LIBRARIES ${CMAKE_DL_LIBS})
 endif()
 
 set( CMAKE_REQUIRED_INCLUDES ${FLTK_INCLUDE_DIR} )
@@ -240,7 +246,7 @@
 HAVE_FLTK_1_3)
 
 	if ( NOT HAVE_FLTK_1_3 )
-		message( SEND_ERROR "FLTK 1.3 is required" ) 
+		message( SEND_ERROR "FLTK 1.3 is required" )
 	endif ( NOT HAVE_FLTK_1_3 )
 
 endif ( FLTK_FOUND )
diff -Nru fgrun-3.4.0.final/debian/changelog fgrun-2016.4.0/debian/changelog
--- fgrun-3.4.0.final/debian/changelog	2016-07-24 16:28:17.0 +0800
+++ fgrun-2016.4.0/debian/changelog	2017-03-08 00:55:51.0 +0800
@@ -1,3 +1,17 @@
+fgrun (2016.4.0-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream release. (Closes: #839357)
+- Drop patches applied upstream.
+- Refresh patches.
+  * Switch upstream to SourceForge.
+- Update corresponding debian/watch file. (Closes: #851845)
+  * Bump debhelper compat version to v10.
+  * Apply "wrap-and-sort -abst".
+  * Update Homepage information on SourceForge.
+
+ -- Boyuan Yang <073p...@gmail.com>  Wed, 08 Mar 2017 00:55:51 +0800
+
 fgrun (3.4.0.final-3) unstable; urgency=medium
 
   [ Gianfranco Costamagna ]
diff -Nru fgrun-3.4.0.final/debian/compat fgrun-2016.4.0/debian/compat
--- fgrun-3.4.0.final/debian/compat	2016-01-23 15:39:09.0 +0800
+++ fgrun-2016.4.0/debian/compat	2017-03-08 00:55:51.0 +0800
@@ -1 +1 @@
-9
+10
diff -Nru fgrun-3.4.0.final/debian/control fgrun-2016.4.0/debian/control
--- fgrun-3.4.0.final/debian/control	2016-07-24 16:25:33.0 +0800
+++ fgrun-2016.4.0/debian/control	2017-03-08 00:55:51.0 +0800
@@ -2,20 +2,30 @@
 Section: games
 Priority: optional
 Maintainer: Debian FlightGear Crew 
-Uploaders: Christopher Baines ,
- Markus Wanner 
-Build-Depends: debhelper (>= 9), cmake, libfltk1.3-dev, fluid,
- libsimgear-dev (>= 3.4.0~), libboost-dev, libexpat-dev,
- zlib1g-dev (>= 1:1.2.3.4.dfsg-3)
+Uploaders:
+ Christopher Baines ,
+ Markus Wanner ,
+Build-Depends:
+ cmake,
+ debhelper (>= 10~),
+ fluid,
+ libboost-dev,
+ libexpat-dev,
+ libfltk1.3-dev,
+ libsimgear-dev (>= 3.4.0~),
+ zlib1g-dev (>= 1:1.2.3.4.dfsg-3),
 Standards-Version: 3.9.8
-Homepage: http://fgrun.sourceforge.net/
+Homepage: https://sourceforge.net/p/flightgear/fgrun/
 Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/fgrun.git
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/fgrun.git
 
 Package: fgrun
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
-Recommends: flightgear
+Depends:
+ ${misc:Depends},
+ ${shlibs:Depends},
+Recommends:
+ flightgear,
 Description: graphical frontend for running FlightGear
  FlightGear Launch Control (FGRun) is a graphical frontend for running the
  FlightGear Flight Simulator (fgfs).
diff -Nru fgrun-3.4.0.final/debian/copyright fgrun-2016.4.0/debian/copyright
--- fgrun-3.4.0.final/debian/copyright	2016-01-23 15:39:10.0 +0800
+++ fgrun-2016.4.0/debian/copyright	2017-03-08 00:55:51.0 +0800
@@ -7,7 +7,7 @@
 Copyright: 2010, Bernie Bright
2010, Frederic Bouvier
 License: GPL-2+
- 
+
 Files: src/Fl_Table.cxx
  src/Fl_Table.H
  src/Fl_Table_Row.cxx
@@ -47,4 +47,3 @@
  .
  A copy of the license is available on Debian systems at
  /usr/share/common-licenses/LGPL-2
-
diff -Nru fgrun-3.4.0.final/debian/patches/add-debian-defaults.diff fgrun-2016.4.0/debian/patches/add-debian-defaults.diff
--- fgrun-3.4.0.final/debian/patches/add-debian-defaults.diff	2016-01-23 15:39:10.0 +0800
+++ fgrun-2016.4.0/debian/patches/add-debian-defaults.diff	2017-03-08 00:55:51.0 +0800
@@ -1,8 +1,15 @@
-Description: Add default directories used by Debian
- If not given, fgrun asks the user to provide several directories. We
- ease this process by defaulting to the install locations used by Debian.
-Author: Markus Wanner 
+From: Markus Wanner 
+Date: Mon, 10 Feb 2014 13:37:04 +0100
+Subject: Add default dire

Bug#856016: RFS: manpages-zh/1.6.0-2

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org

Dear mentors and chinese-developers folks,

I am looking for a sponsor for my package "manpages-zh" into unstable.

* Package name : manpages-zh
  Version  : 1.6.0-2
  Upstream Author  : [myself]
* Url  : https://github.com/man-pages-zh/manpages-zh
* License : GFDL-1.2+
  Section  : doc

 It builds those binary packages:

manpages-zh - Chinese manual pages

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

  https://mentors.debian.net/package/manpages-zh

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

dget -x https://mentors.debian.net/debian/pool/main/m/manpages-zh/
manpages-zh_1.6.0-2.dsc

 Alternatively, one can download the package from deb-o-matic-amd64:

http://debomatic-amd64.debian.net/distribution#unstable/manpages-zh/1.6.0-2/
buildlog

  Changes since the last upload:
 manpages-zh (1.6.0-2) unstable; urgency=medium
 .
   * Pick several upstream new man pages.
 - Move chroot(1) to chroot(8). (Closes: #856010)
 - Update pages for coreutils. (Closes: #856011)

Notes:

  * I intend to push it into Debian Unstable and request an unblock later.
  * Lintian warnings are fixed-upstream. But since we are in deep freeze, I am 
not sure if the Release Team would allow me to push a new upstream version, so 
not fixed here.

--
Sincerely,
Boyuan Yang

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

Bug#851756: telegram-desktop/1.0.13-1

[Boyuan Yang]

When we are checking  a debian package, lintian is always the best friend.

Running lintian against telegram-desktop 1.0.12 gives the following 
information:

% lintian -E -I --pedantic ./*.dsc ./*.deb
P: telegram-desktop source: source-contains-autogenerated-visual-c++-file 
Telegram/Resources/winrc/Telegram.rc
P: telegram-desktop source: source-contains-autogenerated-visual-c++-file 
Telegram/Resources/winrc/Updater.rc
P: telegram-desktop source: source-contains-autogenerated-visual-c++-file 
Telegram/Resources/winrc/resource1.h
P: telegram-desktop source: debian-watch-may-check-gpg-signature
I: telegram-desktop: hardening-no-fortify-functions usr/bin/telegram-desktop
I: telegram-desktop: spelling-error-in-binary usr/bin/telegram-desktop catched 
caught
I: telegram-desktop: spelling-error-in-binary usr/bin/telegram-desktop ment 
meant
I: telegram-desktop: spelling-error-in-binary usr/bin/telegram-desktop Lenght 
Length
I: telegram-desktop: spelling-error-in-binary ... use --no-tag-display-limit 
to see all (or pipe to a file/program)
I: telegram-desktop: spelling-error-in-manpage usr/share/man/man1/telegram-
desktop.1.gz Allows to Allows one to
I: telegram-desktop: desktop-entry-contains-encoding-key usr/share/
applications/telegramdesktop.desktop:2 Encoding
I: telegram-desktop: desktop-entry-lacks-keywords-entry usr/share/
applications/telegramdesktop.desktop

This might be helpful when correcting spelling mistakes.

Another good tool is check-all-the-things [1], which is provided by Debian 
since Stretch. This tool checks enormous aspects and warns you in the output.

[1] https://tracker.debian.org/pkg/check-all-the-things

--
Sincerely,
Boyuan Yang

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

Bug#849493: RFS: vc/1.3.0-1 [ITP]

[Boyuan Yang]

在 2017年1月27日星期五 CST 下午1:04:26，Boyuan Yang 写道：
> Hi all,
> 
> This is the owner of RFP bug for vc package (#846491) and let's push
> the process forward a little bit.
> 
> On Sun, 1 Jan 2017 21:10:49 +0100, Andreas Henriksson wrote:
> > In Debian we have one shared namespace for all packages (and
> > potential binaries, etc.). Shorter names often leads to
> > collisions in the namespace.
> > I don't see any other package currently named "vc" but still
> > staying away from any 2letter name [...]
> > [...]
> 
> I think the name "vc" and binary name "vc-dev" should be acceptable.
> The reason is that "vc" is highly unlikely to be used by other packages
> because *Ubuntu* named this package as "vc" and "vc-dev".
> See http://packages.ubuntu.com/zesty/vc-dev.
> 
> That said, we should get into contact with upstream author if we really
> want an alternative name.
> 
> Note that "libvc" cannot be used because we already have "libvc" and
> "libvc-dev".

Hello all,

Ubuntu just released a new version of vc (https://launchpad.net/ubuntu/
+source/vc/1.3.0-0ubuntu1). This could be reused by Debian.

Aleksey, are you still working towards this RFS? If yes, you may take a look 
at this Ubuntu package. If not, please disown and close this bug (#849493).

Still I think the name "vc" and "vc-dev" should be acceptable. Changing into 
other name will cause split between Debian and all Ubuntu derivatives.

--
Thanks,
Boyuan Yang


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

Bug#851756: RFS: telegram-desktop/1.0.6-1 [ITP]

[Boyuan Yang]

Hi,

I just heard that someone filed an RFS for telegram-desktop. Good job! Wish 
that you could make this package into good shape and put it into Debian.

> I can't understand how pristine-tar works. Should I manually download [...]

You should use upstream tarball when applicable. If we use the tarball which 
is *identical* with the tarball released by upstream, we can have confidence 
that no source code is modified in the distribution version of this software. 
If upstream signs the tarball, we may also verify its integrity using gpg. 
(Debian supports such check via debian/watch file and public key inside debian/ 
dir. Well, that's not the case for telegram-desktop so never mind.)

Downloading manually can be unnecessary. If you carefully write debian/watch 
file, the "uscan" tool can do it for you according to information in d/watch 
file. If you don't really want to hack into d/watch, then manual download 
should be needed.

A big trouble is that upstream usually bundles lots of third-party sources 
into its release. You will need to write detailed d/copyright file for those 
files.

Of course you may still use gbp-generated orig tarball. The decision is up to 
you.

--

Here are my incomplete reviews for current packaging (1.0.6). Note that I am 
not a DD nor DM, so I won't be able to sponsor your package.

* I really don't recommend using "ronn" tool to generate man page. Even we 
have ronn in Debian, ronn is already dead upstream [1] and we shouldn't use a 
dead tool in build toolchain. Writing man pages manually won't take up too 
much time, or at least we can consider tools other than ronn (yes, there are 
other tools available).

* Please consider explicitly enable (full) hardening flags in d/rules and test 
if the build can pass.

* Is the hard Depends: to fcitx-frontend-qt5 necessary? Your instruction would 
make everyone who installs telegram-desktop to install fcitx, which is an 
Input Method Framework. I recommend you downgrade it to Suggests.

* Build-depends fcitx-frontend-qt5 seems very wrong. Could you please explain 
why you add this one?

[1] https://github.com/rtomayko/ronn/

After all, this is a big software and the package may need further polishment. 
Please keep going ahead. I am looking forward to seeing telegram-desktop 
inside Debian.

--
Sincerely,
Boyuan Yang


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

Bug#849493: RFS: vc/1.3.0-1 [ITP]

[Boyuan Yang]

Hi all,

This is the owner of RFP bug for vc package (#846491) and let's push
the process forward a little bit.

On Sun, 1 Jan 2017 21:10:49 +0100, Andreas Henriksson wrote:
> In Debian we have one shared namespace for all packages (and
> potential binaries, etc.). Shorter names often leads to
> collisions in the namespace.
> I don't see any other package currently named "vc" but still
> staying away from any 2letter name [...]
> [...]

I think the name "vc" and binary name "vc-dev" should be acceptable.
The reason is that "vc" is highly unlikely to be used by other packages
because *Ubuntu* named this package as "vc" and "vc-dev".
See http://packages.ubuntu.com/zesty/vc-dev.

That said, we should get into contact with upstream author if we really
want an alternative name.

Note that "libvc" cannot be used because we already have "libvc" and
"libvc-dev".

--
Sincerely,
Boyuan Yang

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

Bug#851348: RFS: nixnote2/2.0~beta11-1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: nixnote2
   Version : 2.0~beta11-1
   Upstream Author : Randy Baumgarte 
 * URL : http://nevernote.sourceforge.net/[1]
 * License : GPL-2+
   Section : utils

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/n/nixnote2/
nixnote2_2.0~beta11-1.dsc

Alternatively, one can obtain binary packages and lintian checks on 
debomatic-amd64:

  http://debomatic-amd64.debian.net/distribution#unstable/nixnote2/2.0~beta11-1/
buildlog

Changes since the last upload:
nixnote2 (2.0~beta11-1) unstable; urgency=medium
 .
   * New upstream release.
   * Switch back to build with Qt5 as upstream recommends.
 - Refresh patch about qevercloud library.
   * No longer mark as +dfsg, all files are dfsg compatible.
 - Drop old patch 0001 for README.txt, upstream has refreshed it.
 - Drop old patch 0003 for purple-theme, licensed under GPL-2+.
 - Update watch file.
 - Update README.source.
   * Cherry-pick several upstream commits.
 - Add patch 0002 for switching default notebook.
 - Add patch 0003 to fix the bug about tagging with Qt5.
 - Add patch 0004 to fix the bug about searching "-" in a note.

Regards,
Boyuan Yang


[1] http://nevernote.sourceforge.net/


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

Bug#851346: RFS: qevercloud/3.0.3+ds-2

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: qevercloud
   Version : 3.0.3+ds-2
   Upstream Author : Dmitry Ivanov 
 * URL : https://github.com/d1vanov/QEverCloud[1]
 * License : MIT
   Section : libs

  It builds those binary packages:

 libqt4qevercloud3 - Unofficial Evernote Cloud API library for Qt4
 libqt5qevercloud3 - Unofficial Evernote Cloud API library for Qt5
 qevercloud-doc - QEverCloud library documentation
 qt4qevercloud-dev - Development files for libqt4qevercloud
 qt5qevercloud-dev - Development files for libqt5qevercloud

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/q/qevercloud/
qevercloud_3.0.3+ds-2.dsc

ALternatively, one can find binary packages and lintian checks on 
debomatic-amd64:

  http://debomatic-amd64.debian.net/distribution#unstable/qevercloud/3.0.3+ds-2/
buildlog

Changes since the last upload:
 qevercloud (3.0.3+ds-2) unstable; urgency=medium
 .
   * d/control: update VCS links.
   * d/control: set Multi-Arch hints.
 - set qevercloud-doc as M-A: foreign.
 - set qt5qevercloud-dev as M-A: same.
 - set qt4qevercloud-dev as M-A: same.

This upload only fixes issues around Debian metadata and Multi-Arch hints. The 
library 
itself is not touched.

Regards,
Boyuan Yang


[1] https://github.com/d1vanov/QEverCloud


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

Bug#850081: RFS: qterm/1:0.7.1-1 [RC, ITA]

[Boyuan Yang]

Package: sponsorship-requests
Severity: important
X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org

Dear mentors and chinese-developers folks,

I am looking for a sponsor for the package "qterm".

 * Package name: qterm
   Version : 1:0.7.1-1
   Upstream Author : Xiaoqiang Wang 
 * URL : https://github.com/qterm/qterm
 * License : GPL-2+ with OpenSSL exception
   Section : x11

  It builds those binary packages:

qterm - BBS client for X Window System written in Qt

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/q/qterm/
qterm_0.7.1-1.dsc

  Alternatively, one can download the package from debomatic-amd64:

http://debomatic-amd64.debian.net/distribution#unstable/qterm/0.7.1-1/

  Alternatively, one can obtain the source code from git repository:

https://anonscm.debian.org/git/chinese/qterm.git

Changes since the last upload:

 qterm (1:0.7.1-1) unstable; urgency=medium
 .
   * New maintainer. (Closes: #841821)
   * ACK previous NMU. Thanks!
   * New upstream release.
 - Switch to new upstream.
 - Add support to OpenSSL 1.1.0. (Closes: #828524)
   * Put package under Debian Chinese Team.
 - Remove LI Daobing from maintainer list.
   Thank you for all your contribution!
 - Add myself onto uploaders list.
   * Switch from cdbs to dh/debhelper buildsystem.
   * Rewrite copyright file with machine-readable format.
   * Bump debhelper compat v7 -> v10.
   * Bump standard version to 3.9.8.
   * Remove obsolete menu file.
   * Remove obsolete xpm icons.
   * Add a patch to cherry-pick upstream license change.
 - Fixes gpl-openssl license issue.
 - Update d/copyright file.

Some explanations:

Piuparts error on debomatic-amd64 website is a false alarm and should be 
ignored.

Regards,
Boyuan Yang

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

Bug#849844: RFS: manpages-zh/1.6.0-1

[Boyuan Yang]

在 2017年1月2日星期一 SGT 下午12:23:49，Sean Whitton 写道：
> debian/ is not part of the upstream code, so changes should be listed in
> d/changelog.  Other Debian contributors should be able to quickly
> determine which uploads changed which control files, by looking at
> d/changelog.  So please be more verbose.

Thanks for your advice. Now I mention the modification of d/control and
d/docs inside the changelog.

New packages have been uploaded onto mentors.d.n and debomatic-amd64.
The git repository on Alioth
(https://anonscm.debian.org/git/chinese/manpages-zh.git) is updated too.

Thanks,
Boyuan Yang


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

Bug#849844: RFS: manpages-zh/1.6.0-1

[Boyuan Yang]

在 2017年1月1日星期日 SGT 下午5:28:47，Sean Whitton 写道：
> control: owner -1 !
> control: tag -1 +moreinfo
> 
> Dear Boyuan,
> 
> Can I sponsor from
> <https://anonscm.debian.org/git/chinese/manpages-zh.git>?
> 
> If so, I see changes to d/control and d/docs which are not documented in
> the Debian changelog.

Sure, please go ahead.

I didn't document them since they look more like implementation detail (e.g, 
upstream changes in build tools, perl->python, README renaming, etc), users 
may read upstream ChangeLog if they are interested. Anyway the version on 
mentors and the one in Git repository are kept in consistency.

--
Thanks,
Boyuan Yang

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

Bug#849844: RFS: manpages-zh/1.6.0-1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org

Dear mentors and chinese-developer folks,

I am looking for a sponsor for my package "manpages-zh".

 * Package name: manpages-zh
   Version : 1.6.0-1
   Upstream Author : Boyuan Yang <073p...@gmail.com>
 * URL : https://github.com/man-pages-zh/manpages-zh
 * License : GFDL-1.2+
   Section : doc

It builds the following packages:

manpages-zh - Chinese manual pages

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

https://mentors.debian.net/package/manpages-zh

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

dget -x https://mentors.debian.net/debian/pool/main/m/manpages-zh/
manpages-zh_1.6.0-1.dsc

Alternatively, one can download packages on debomatic-amd64:

http://debomatic-amd64.debian.net/distribution#unstable/manpages-zh/
1.6.0-1/buildlog

Changes since last upload:
 manpages-zh (1.6.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - Import more translations for coreutils.
 - Various updates.

Some explanations:

This is a new upstream release, mainly about cleanup for historical cruft.

Lintian warnings for man pages is being tracked by upstream and will release
fixes in next release. Those warnings do not affect user experience.

Regards,
Boyuan Yang


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

Bug#848093: RFS: manpages-zh/1.5.4.1-1

[Boyuan Yang]

2016-12-14 19:20 GMT+08:00 Gianfranco Costamagna :
> d/compat <-- still "9"
>
> this is why you didn't drop "--with autoreconf" from rules file, right?
> (please drop it)

Yes. Problem solved.

>
>
> debian/copyright.old seems useless, right?

Initially I wanted to keep it inside the source package, but on a second thought
it is indeed useless. Deleted.

> why did you drop all the manpages?
> the old package was installing a lot of stuff
> https://packages.debian.org/sid/all/manpages-zh/filelist
>
> the new one seems to install only one
> http://debomatic-amd64.debian.net/distribution#unstable/fortune-zh/2.0/contents
> (but they are available inside the sources)

This is fortune-zh package, not manpages-zh. (Though both are under the "Debian
Chinese Team" umbrella :-p )

Indeed I dropped ~15 man pages but there are still 200+ left.

Please visit 
http://debomatic-amd64.debian.net/distribution#unstable/manpages-zh/1.5.4.1-1/buildlog
directly.


Now packages on deb-o-matic-amd64, mentors.d.o and git repo are all
updated again.

Thanks,

Boyuan Yang

Bug#848093: RFS: manpages-zh/1.5.4.1-1

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: cjwat...@debian.org
X-Debbugs-CC: a...@debian.org
X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org

Dear mentors and chinese-developer folks,

I am looking for a sponsor for the team package "manpages-zh".

 * Package name: manpages-zh
   Version : 1.5.4.1-1
   Upstream Author : [ switching to myself ]
 * URL : https://github.com/man-pages-zh/manpages-zh
 * License : GFDL-1.2+
   Section : doc

It builds those binary packages:

manpages-zh - Chinese manual pages

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

  https://mentors.debian.net/package/manpages-zh

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

dget -x https://mentors.debian.net/debian/pool/main/m/manpages-zh/
manpages-zh_1.5.4.1-1.dsc

Alternatively, one can obtain binary package and its piuparts / buildlog / 
buildinfo information at deb-o-matic:

http://debomatic-amd64.debian.net/distribution#unstable/manpages-zh/
1.5.4.1-1

All changes have been pushed onto team git repository:

https://anonscm.debian.org/git/chinese/manpages-zh.git

Explanations for the new upload:

The original maintainer, LI Daobing, is retiring (as the MIA Team indicates 
[1]). This upload would take over this package and get the package back into 
good shape.

Even though there are still many outdated man pages in this release, at least 
we are moving one step forward into the cleanup of old cruft and improve the 
situation, and the bug solved in groff and man-db [2] would greatly help 
improve the typesetting quality of Chinese man pages in Stretch.

[1] https://bugs.debian.org/841805
[2] https://bugs.debian.org/848030

Explanations for lintian checks and package itself:

Lintian warnings on deb-o-matics about zh.tmac is a false-positive, since 
zh.tmac was added yesterday and does not exist in Jessie yet. This file will be 
in Stretch however.

Lintian error on mentors.d.n is a false-positive, since mentors system is old 
and does not recognize debhelper v10, in which dh-autoreconf is a dependency 
of debhelper, so no need to worry. Clean chroot is successful on fresh 
unstable system.

Changes since the last upload:

 manpages-zh (1.5.4.1-1) unstable; urgency=medium
 .
   * Team upload.
   * ACK previous NMU. Thank you Colin!
   * Remove LI Daobing from uploaders list. (Closes: #841805)
 Thank you for all your contributions!
   * New upstream release.
 - Switch to new upstream.
 - Remove all conflict man pages.
 - Remove some nonexist command pages. (Closes: #723565)
 - Import some translations of coreutils.
 - Various fixes.
   * Apply "wrap-and-sort -abst".
   * d/rules: switch to dh buildsystem.
   * d/control:
 - Add myself into uploaders list.
 - Bump standards version to 3.9.8.
 - Use debhelper compat v10, drop dh-autoreconf dep.
 - Update Vcs-* fields.
   * d/watch: info update.
   * d/copyright: rewrite with machine-readable format.

Regards,
 Boyuan Yang

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

Bug#847210: RFS: shutter/0.93.1-1.1 [NMU]

[Boyuan Yang]

在 2016年12月9日星期五 SGT 下午1:12:05，Gianfranco Costamagna 写道：
> Hi,
> 
> >https://mentors.debian.net/debian/pool/main/s/shutter/
> >
> >shutter_0.93.1-1.1.dsc
> 
> sponsored in deferred/10, please forward patches upstream!

Thank you very much!

Patches are, in fact, retrieved from upstream issues replies, so no need to 
worry about patch upstreaming.

--
Sincerely,
Boyuan Yang



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

Bug#847210: RFS: shutter/0.93.1-1.1 [NMU]

[Boyuan Yang]

在 2016年12月6日星期二 SGT 下午10:32:20，Boyuan Yang 写道：
> It builds those binary packages:
> 
> shutter   - feature-rich screenshot program
> 
> To access further information about this package, please visit the following
> URL:
> 
> http://debomatic-amd64.debian.net/distribution#unstable/shutter/0.93.1-1.1
> 
> Note: Strangely mentors.debian.net accepted my upload but nothing showed up
> on mentors website, so I have to use some alternatives. Sorry for the
> inconvenience. Scroll to the bottom of that page and you'll find buildlog,
> lintian, buildinfo, dsc link and built deb file. The failing piuparts is a
> false alarm. Please read that report for detailed info.
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x http://debomatic-> 
> amd64.debian.net/debomatic/unstable/pool/shutter_0.93.1-1.1/shutter_0.93.1-1
> .1.dsc

FYI, this package finally somehow showed up on mentors.debian.net.
One may find package information on:

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

And alternatively one can download the package with dget:

https://mentors.debian.net/debian/pool/main/s/shutter/
shutter_0.93.1-1.1.dsc

Git commits can be found on anonscm.d.o:

https://anonscm.debian.org/git/collab-maint/shutter.git/log/

P.S. The previous RFS mail has already been CC-ed to the original maintainer. 
I haven't received any response yet.

Thanks!

--
Sincerely,
Boyuan Yang



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

Bug#847210: RFS: shutter/0.93.1-1.1 [NMU]

[Boyuan Yang]

FYI, changes for this NMU can be found in collab-maint to ease the review:

https://anonscm.debian.org/git/collab-maint/shutter.git/log/

Thanks!

--
Sincerely,
Boyuan Yang

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

Bug#847210: RFS: shutter/0.93.1-1.1 [NMU]

[Boyuan Yang]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the package "shutter".

It is an NMU, which would fix the long-standing #819149 and #847051.

The maintainer of the package has disappeared for quite some time and the
package has experienced 4 NMUs since 2012. The QA/MIA Team has started dealing
with it.

It builds those binary packages:

shutter   - feature-rich screenshot program

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

http://debomatic-amd64.debian.net/distribution#unstable/shutter/0.93.1-1.1

Note: Strangely mentors.debian.net accepted my upload but nothing showed up on
mentors website, so I have to use some alternatives. Sorry for the
inconvenience. Scroll to the bottom of that page and you'll find buildlog,
lintian, buildinfo, dsc link and built deb file. The failing piuparts is a
false alarm. Please read that report for detailed info.

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

  dget -x http://debomatic-
amd64.debian.net/debomatic/unstable/pool/shutter_0.93.1-1.1/shutter_0.93.1-1.1.dsc

Changes since the last upload:

   * Non-maintainer upload.
   * Add patch to fix messy display for non-latin characters.
 (Closes: #847051, LP: #1556021, LP: #1618310)
   * Add patch to fix crash on sending email.
 (Closes: #819149, LP: #1469840)
   * Add libgtk2-appindicator-perl into Recommends list.
 This helps utilize libappindicator and provide with better
 user experience for tray icon.

Regards,

--
Boyuan Yang



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#832704: RFS: nixnote2/2.0~beta10+dfsg-1 [ITP] -- Open Source Evernote client

[Boyuan Yang]

在 2016年11月13日星期日 CST 下午2:43:47，Sean Whitton 写道：
> plus some other minor comments below.  The blocker:
> 
> hephaestus ~ % nixnote2
> QSqlDatabase: QSQLITE driver not loaded
> QSqlDatabase: available drivers: QMYSQL3 QMYSQL
> ERROR 2016-11-13 14:38:58.946 ( sql/databaseconnection.cpp @ 44 ) Error
> opening database:  QSqlError(-1, "Driver not loaded", "Driver not loaded")
> 
> Any ideas?

A missing dependency libqt4-sql-sqlite caused this problem. It seems that
the automatic dh_shlibdeps failed to list it inside Depends list (it only 
listed libqt4-sql). A explicit dependency was added the latest commit.

> > * Some minor modification to package description in debian/control.
> 
> 1. There's a grammatical error in your change: s/provide/provides/.
> 
> 2. The sentence doesn't really make sense.  Maybe s/and/to/ is what you
> meant?

Fixed.

> > * Copyright information update for beta10 version.
> 
> 3. Are you installing the plugins at present, 'hunspell' and 'webcam'?
> Contents of package suggests not.  Upstream seems to think they belong
> in separate binary packages.  What do you think about that?

Added debian/README.Debian file to explain the situation. The plugin structure
won't support Qt5, plus upstream placed the plugin inside /usr/share, which is 
not acceptable. The building system (CMake) for plugins is not in standard 
status, too. My choice is not to install the plugins and wait until upstream 
provides with a better solution.

Patching may be possible but that would be painful.

> > Blhc on debomatic reported some missing CXXFLAGS (-fPIE). However
> > since new gcc has already set -fPIE by default since 6.2.0-7, this
> > should be harmless.
> 
> Yes.  Lintian would be complaining if it wasn't being passed.

Again this needs patching, so I would choose to look into it later until some 
real problem comes up.

> 4. I'm curious why you nuked gbp.conf.  Entirely up to you, of course.

I found git-buildpackage not reading the "debian/gbp.conf" at all unless I 
list it explicitly inside environment variable, which is different from words 
written in man 5 gbp.conf. Command line arguments should be a better choice 
for me.

> 5. Your Forwarded: headers got eaten at some point.  Would be nice to
> restore them.

Well it is a problem hiding in gbp pq, which will eat non-mandatory headers 
when exporting patches because git commit does not preserve those information. 
Maybe I fill file a bug report (feature request?) later.

> 6. You could install the new screenshot.png to
> /usr/share/doc/nixnote2/examples (see dh_installexamples(1)).

Done.


Git repository updated on
https://anonscm.debian.org/git/collab-maint/nixnote2.git
Package on debian-mentors updated:
https://mentors.debian.net/package/nixnote2
Package built on debomatic:
http://debomatic-amd64.debian.net/distribution#unstable/
nixnote2/2.0~beta10+dfsg-1/


Sincerely,
Boyuan Yang


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

Bug#832704: RFS: nixnote2/2.0~beta10+dfsg-1 [ITP] -- Open Source Evernote client

[Boyuan Yang]

retitle 832704 RFS: nixnote2/2.0~beta10+dfsg-1 [ITP] -- Open Source
Evernote client
thanks

Hi Sean,

Since the dependency qevercloud has entered unstable, it is perfectly
fine to move towards nixnote2. I have prepared the 2.0~beta10 version
of nixnote2 package, which should address previous problems.

Detailed changes since 2.0~beta9+dfsg:

* Legacy code about old OpenOffice.org was further explained in README.source.
* Move packaging Git repository to collab-maint, now I have write
permission there. The old GitHub repository still exists and in an
up-to-date state.
* Some minor modification to package description in debian/control.
* Switched back to build with Qt4. This is not ideal but will help
squashing bugs raised when using Qt5. I will switch back to build
against Qt5 once upstream declared that the Qt5 version is in mature
state.
* Copyright information update for beta10 version.

Package on debian-mentors:

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

Packaging repository can be found at

https://anonscm.debian.org/git/collab-maint/nixnote2.git

Deb-o-matic-amd64 build status:


http://debomatic-amd64.debian.net/debomatic/unstable/pool/nixnote2_2.0~beta10+dfsg-1/nixnote2_2.0~beta10+dfsg-1.dsc

Blhc on debomatic reported some missing CXXFLAGS (-fPIE). However
since new gcc has already set -fPIE by default since 6.2.0-7, this
should be harmless.

Looking forward to further review.


Sincerely,
Boyuan Yang

Bug#836903: RFS: qevercloud/3.0.3+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

X-Debbugs-CC: a...@debian.org

Hello Sean,

在 2016年10月13日星期四 CST 下午6:41:17，Sean Whitton 写道：
> control: tag -1 + confirmed - moreinfo
> control: noowner -1
> 
> Hello,
> 
> I'm going away for the weekend, so I'm marking this as confirmed as the
> only remaining issue is extremely minor (see below).
> 
> I think that commit 240db346c4abfd3d6ccb1c9db36c7880db289f6a is ready
> for upload to Debian, though it would be nice if the below is fixed.

Thank you for all your patience and kind review!

Maybe it is the right time for me to seek for a DD to sponsor this package.

This package ("src:qevercloud") is a Qt library that provides access to 
Evernote Cloud API. It is supposed to act as the dependency of package
"nixnote2" (RFS: #832704, ITP: #609849), which is an unofficial Qt-based
feature-rich Evernote client for Linux.

Working Git repository: https://github.com/hosiet/qevercloud
mentors.d.n: https://mentors.debian.net/package/qevercloud
prebuilt package on deb-o-matic-amd64:
 http://debomatic-amd64.debian.net/distribution#unstable/qevercloud/
3.0.3+ds-1/buildlog

P.S. Please ignore the piuparts warning on debomatic.d.o, which is a false
alarm due to the site's network error.

> You should put the comments above the warning (currently below).  That
> way, they are associated together.

I read articles from lintian.d.o again and confirmed the correct grammar. The
new git commit 2dcb474cb2dc2b977b0ba5f1363fd321d3cd28ac has fixed this
problem.

All related files/packages on GitHub / debian-mentors / deb-o-matic has been
updated to latest commit.

Thanks!

Sincerely,
Boyuan Yang

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

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

Hello Sean,

2016-10-12 21:49 GMT+08:00 Sean Whitton :
> I suggest:
>
> 1) override the jquery warning, with a comment pointing to README.jquery
> (there is a special format for lintian override comments)

I am not quite sure about what the special format for lintian override comment
is. I only found that comments in different place would have different effect
of showing / not showing in the verbose log. Could you please check the
grammar of my newly added `debian/qevercloud-doc.lintian-overrides' file?
At least lintian is accepting it.

> 2) ensure that dh_doxygen is run after you build the documentation.  It
> does various things like symlink template files.

Added. Looks like things are going well in build log.


The refreshed package has been uploaded to debomatic-amd64 / GitHub /
debian-mentors.


Sincerely,
Boyuan Yang

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

Hello Sean,

2016-10-12 10:43 GMT+08:00 Sean Whitton :
> Hello Boyuan,
>
> Have you read /usr/share/doc/doxygen/README.jquery?
>
> I think you shouldn't be symlinking jquery.

Wow, I did not read it before since I trusted lintian :p

Looks like it is kind of disagreement between the packager / uploader of
doxygen and debian policy.

I found bug #736360 and dh_doxygen really interesting, but still kind of
confused. dh_doxygen did not mention this embedding problem in its
manpage, and those Debian bug reports did not give a final solution
either. So what should I do? Just override the lintian warning?


Sincerely,
Boyuan Yang

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

Hello Sean,

2016-10-09 8:36 GMT+08:00 Sean Whitton :
> Hello Boyuan,
>
>> Added a patch to disable the instructions about PDFs in Doxyfile.
>
> Upstream has made a new release 3.0.3 incorporating a fix o/
>
> Could you try building the docs with this new release, please?

I made a new release with 3.0.3 called 3.0.3+ds.

The new version has been uploaded without modification about .so
symlink; see the discussion below.

>
> Btw, the Forwarded: header should point at patches submitted, not bug
> reports without patches.  You should include the issue URI in the patch
> description, instead.  (Doesn't matter if you're able to drop the
> patch.)

OK. (Those patches are dropped.)

>> > One more thing -- the .so should be installed as
>> > libqt?evercloud.so.3.0.0, with a symlink from libqt?evercloud.so.3.
>> > See ch. 8 of Debian policy for an explanation of this practice.
>>
>> Patch added (0010-patch-library-soname-chain.patch).
>>
>> Issue forwarded: https://github.com/d1vanov/QEverCloud/issues/7
>
> In addition, the symlink in the -dev package conventionally points at
> libqt?evercloud.so.3.0.0, rather than at libqt?evercloud.so.3 (again,
> see ch. 8 of Policy which specifies that this should be a "symlink
> pointing to the shared library", though I suppose that could be
> interpreted to include pointing via another symlink).

That is an interesting issue. In my opinion, as long as the -dev package
always keep the same version as the library package (as required
by Debian Policy), symlinking to libfoobar.so.3 seems to have the same
function as symlinking to libfoobar.so.3.0.0.

I made a small investigation on my own Debian testing. doing
`file /usr/lib/x86_64-linux-gnu/*.so` would return some interesting results.
While many libfoobar.so files is symlinking to final library so files,
there are lots of other files are symlinking to another symlink, for example
libfoobar.so.3, which makes a symlink toolchain. Examples include
libpython3.5m, libkf5 series, libopencv, libform and so on.

Given so many examples, I think it should be acceptable. What do you think?


The updated version of qevercloud can be found on GitHub/debian-mentors/
debomatic-amd64.

Sincerely,
Boyuan Yang

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

dependency if
> debian/libqt5qevercloud3/usr/lib/i386-linux-gnu/libqt5qevercloud.so.3
> was not linked against libQt5Gui.so.5 (it uses none of the library's
> symbols)
> dpkg-shlibdeps: warning: package could avoid a useless dependency if
> debian/libqt5qevercloud3/usr/lib/i386-linux-gnu/libqt5qevercloud.so.3
> was not linked against libdl.so.2 (it uses none of the library's
> symbols)
>
> Do you know whether those unneeded dependencies may be avoided?

Writing "export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed" in
debian/rules to clean the unneeded links. libQt5Gui is gone now but libdl
still exists.

Well they look harmless and I would just leave them there.

> One more thing -- the .so should be installed as
> libqt?evercloud.so.3.0.0, with a symlink from libqt?evercloud.so.3.  See
> ch. 8 of Debian policy for an explanation of this practice.

Patch added (0010-patch-library-soname-chain.patch).

Issue forwarded: https://github.com/d1vanov/QEverCloud/issues/7

>
> Thanks!  I'm excited to see the completion of this RFS!
>
> --
> Sean Whitton

Thanks. The GitHub repo / debian-mentors / debomatic-amd64 files are
update-to-date now.


Sincerely,
Boyuan Yang

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

Hello,

2016-09-17 22:31 GMT+08:00 Sean Whitton :
> The packaging is in great shape.  Here's a review for you.
[...]

FYI, I made a small update after last update, which is to fix the d/control file
to raise the debhelper dependency from 9 to 10.

The GitHub repository and mentors package have been updated.


--
Sincerely,
Boyuan Yang

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

Hello,

2016-09-17 22:31 GMT+08:00 Sean Whitton :
> Hello Boyuan,
>
> On Wed, Sep 14, 2016 at 12:23:48PM +0800, Boyuan Yang wrote:
>> Yes, they are up-to-date now. The package on debian-mentors is also
>> updated.
>
> The packaging is in great shape.  Here's a review for you.

Thank you for your detailed review!

All the statements below are fixed/adjusted.

> Must-fixes:
> ---
>
> 1. The changelog entry won't close the ITP unless you put a # in front of
> the bug number!

That is indeed my mistake. Fixed.

> 2. We need to test building something against your new shared library,
> and we'll need to confirm that the right dependencies get generated for
> it by dpkg-shlibdeps.  If you haven't done so already, could you update
> your nixnote packaging to use your new qevercloud shlib, please?

The new version (2.0~beta9+dfsg-1) was pushed to GitHub, mentors
and debomatic-amd64.
Source package changed (ds -> dfsg) due to unclear license status (as
discussed previously in nixnote2 RFS).

> 3. In a recent commit you renamed debian/{*.symbols => *.symbols.amd64}.
> So now you are not providing any symbols files for other architectures.
> But for a shared library, you need to provide a symbols or shlibs file
> for all the reasons described in ch. 8 of the Debian Policy Manual.
>
> I assume that you did this rename because the symbols files is
> architecture-dependent.  That probably means it's very fragile: changes
> which don't break the ABI might change the symbols file.  This is a
> known issue with C++ shared libs.[1]

It was indeed because of architecture-dependent symbols of C++.

>
> You need to make the symbols file less fragile (some suggestions
> involving sed(1) here[2]) so that it will work for all archs, or switch
> to a shlibs file instead.  README.md suggests that upstream is aware of
> the issue of ABI compatibility, so shlibs files might be enough.

Anyway I switched to shlibs using dh_makeshlibs. It is reasonable for
this package to depend on upstream to keep ABI comaptibility, but I
will also try to test symbol files on each release (even it is not included
in the tarball, it can be stored in the git history).

> Suggestions:
> 
>
> 1. Please add Forwarded: headers to the patches.

Added (mostly Forwarded: not-needed).

> 2. It seems like debhelper's cmake buildsystem
> (/usr/share/perl5/Debian/Debhelper/Buildsystem/cmake.pm) should handle
> what your 0001 patch does.  Are there situations where we wouldn't want
> GNUInstallDirs?  If not, please submit a bug against debhelper.

I was trying to bypass problem No.12 using this patch but failed. After that
I forgot to remove this patch (since it will not harm anything).

This patch is removed now.

> 3. README.md suggests that there is doxygen documentation available for
> generation and install.  Please consider installing this in a new
> qevercloud-doc binary package.

The new qevercloud-doc added.

I dropped the tex / pdf / postscript files in the -doc package because
they are not that
useful when html files are provided as well.

> 4. Since you added a "Section:" field to each binary package, the
> "Section: libs" at the top of the file does nothing.  Better to remove
> it.

Now I declared the Section in the source package section and removed
the duplicated Section:libs in binary packages.

> 5. Since debhelper 10 has just been released, consider using compat
> level 10.

Just switched.

> 6. Are you sure you need the debian/*.dirs files?  Have you tried
> building without them?  They are very rarely necessary these days.

Those files are leftovers from original upstream debian packaging
scripts and are (of course) not useful at all in this situation.

Now removed.

> 7. In your rules file you make a lot of explicit calls to dh_auto_*.
> When you do something like this
>
> override_dh_auto_clean:
> dh_auto_clean
> rm -rf $(_QEVERCLOUD_QT5_BUILDDIR)
>
> it's fine, because it's clear to a reader that you are appending to an
> automatic command.  However, when you do this:
>
> custom_regenerate_source_code:
> (cd $(_QEVERCLOUD_GENERATOR_DIR); cmake .;)
> dh_auto_build --buildsystem=makefile -- -C 
> $(_QEVERCLOUD_GENERATOR_DIR)
> mkdir -p QEverCloud/src/generated
> etc.
>
> the dh_auto_build line is quite hard to understand -- someone would need
> to look up the makefile buildsystem.  It would be better to replace that
> with an explicit call to $(MAKE).  In dh_auto_build(1) it says "If it
> doesn't work, you're encouraged to skip using dh_auto_build at all, and
> just run the build process manually."

That is reasonable indeed. Switched to call $(MAKE).

> 8. 

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

Hello,

2016-09-12 21:34 GMT+08:00 Sean Whitton :
> Dear Boyuan,
>
> On Sun, Sep 11, 2016 at 08:48:15AM +0800, Boyuan Yang wrote:
>> > - status of lemon parser currently unclear
>>
>> This is fixed in the RFS of qevercloud before already. Of course we are
>> using the lemon parser from Debian. The bundled source code of lemon
>> is discarded in the source package. Sorry I didn't update the situation
>> on that Github thread, which is a little bit outdated.
>
> Great.
>
>> You suggested the separate packaging of qevercloudgenerator, but now we
>> seems to agree that since it is not useful for anything other than building
>> qevercloud,  it should not be packaged separately.
>
> Right.
>
>> Now the problem is focused on the separation of evernote-thrift files.
>>
>> I believe you suggested packaging thrift files alone, since the
>> separated package
>> can be used by other packages (most likely as a Build-Depend?), and to deal
>> with the FTBFS of qevercloud after the version bump of evernote-thrift, we 
>> can
>> include multiple copies. Did you suggest the coexistence of multiple versions
>> of evernote-thrift in the Debian repository, for example,
>> "evernote-thrift-1-25" and
>> "evernote-thrift-1-28"? Or if I misunderstood, it is just one package
>> "evernote-thrift"
>> but provides different versions of files inside one binary package (e.g.,
>> /usr/share/evernote/thrift/1.25/foobar and
>> /usr/share/evernote/thrift/1.28/foobar)?
>
> No, I was suggesting that you just embed the thrift files in your
> qevercloud source package, as you wanted to do originally.
>
> When I said "multiple versions in the archive" I meant copies in various
> source packages, but not in any binary packages.
>
>> Personally I am against the separated package of evernote-thrift, and
>> the main reason is that it is not useful; thrift files are technically
>> used by no one other than evernote people; developers are
>> encouraged/guided to use official Evernote SDK released by evernote,
>> which is already a generated project from the thrift files; no one
>> else is parsing thrift files by him/herself.
>
> Right.  They shouldn't be installed: just present in the qevernote
> source package for the purposes of regeneration.
>
> Could you confirm that your git repository is up-to-date with our
> discussion, so I can (finally!) do a review of your packaging, please?

Yes, they are up-to-date now. The package on debian-mentors is also
updated.


Sincerely,
Boyuan Yang

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

ion of
automake/autoconf
generated files and the versioning/packaging problem of shared libraries. I have
heard that in the (unreleased) debhelper compat level 10 the regeneration of
autotools files is the default behaviour, which indicates the changes
of people's
thoughts.

Sincerely,
Boyuan Yang

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

2016-09-08 0:52 GMT+08:00 Sean Whitton :
> The issue is that then we then have multiple copies of the thrift files
> in Debian: a copy in each source package that needs them, either for
> regeneration or in debian/missing-sources/.
>
> Suppose there is an Evernote protocol change, or some other bug that
> means the thrift files get updated.  If there is one copy of them in
> Debian, we just update that, and then binNMU all the packages that use
> it, and we're done.

Unfortunately things will not be the case, at least not for Evernote thrift
files.

I had some discussions to the current maintainer of QEverCloud about
the possibility of updating thrift IDL files and regenerate again.
https://github.com/d1vanov/QEverCloud/issues/5

He just told me it is not possible, since the generator needs to be
updated. Update in Evernote thrift files will simply leads to FTBFS
without the update in the generator.

> Otherwise, if there are lots of copies, we have to update each package
> separately.  That's significantly more work, and can't be done by just
> one person, but needs the involvement of the maintainers of all those
> packages.
>
> This is especially relevant if we need to update the thrift files in a
> Debian stable release: updates to packages in a released version of
> Debian have to go through a careful vetting procedure, and this means we
> only have to do that once.  That saves a lot of time (and indeed makes
> it feasible at all).
>
> It's possible I've misunderstood the purpose of the thrift files, though
> -- if there was an Evernote API change, they would have to change and
> the corresponding language-specific generators re-run, right?

In this specific case, we also need to notice the slow evolvement of
Evernote Cloud API (>= 3 years, longer than Debian stable release cycle.
Take a look at Evernote official SDK)
and the backward compatibility of the API. Not updating API will not cause
problems, and it is the author of program (i.e., nixnote2 author) who has
the responsibility to update the level of API itself uses. Even if the Evernote
API is updated according to the new thrift files by packagers, the added methods
will not be utilized until the program author decide to switch to the
new API, and
the changed/removed methods may lead to FTBFS.

>> Is there really any previous example in Debian, that one package
>> *should* and *do* Build-Depend on another *binary* package that only
>> contains some description files or source codes?
>
> I'm not sure about a package that only contains source code alone, but I
> can give you an example of one that contains source code plus some other
> stuff: dh-elpa.  If you look in the emacsen-common folder of its source
> package, you'll find some scripts.  Those get copied into every elpa-*
> binary package (with the package name substituted in).  And dh-elpa is
> added to the elpa-* package's Built-Using field.
>
> Before dh-elpa, there was a copy of those emacsen-common scripts in
> every single Emacs lisp addon package (and in package that have not yet
> been converted, it's still there, e.g. s-el).  That meant that fixing
> bugs in those scripts or improving/reworking the Emacs Lisp addon
> packaging policy[1] means updating every single Emacs Lisp addon source
> package, and re-uploading.
>
> Thanks to dh-elpa we can update the scripts in all elpa-* packages just
> by changing dh-elpa, and rebuilding the elpa-* packages.[2]

Unfortunately Evernote thrift files are neither lisp nor shared libraries.
I understand the advantage that common files get updated separately and
a rebuild solves the rest of the problem, but this is not the current case.

>> I checked ebib and find that I know nothing about emacs lisp and its 
>> debhelper.
>> Where did it remove any file?
>
> Take a look at the two overrides in d/rules.  You shouldn't need to know
> anything about Emacs lisp to understand those.

Are we talking about the same package? :p

I ran `apt-get source ebib' and got ebib v4.5.2. The debian/rules is
nothing more
than one line of `dh $@ --parallel --with elpa'.


Sincerely,
Boyuan Yang

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

Hello,

2016-09-07 23:15 GMT+08:00 Sean Whitton :
> control: owner -1 !
> control: tag -1 +moreinfo
>
> Dear Boyuan,
>
> Thanks for this!  Before I do a proper review let's talk about the
> source code/repacking situation.
>
> Are there/could there be other libraries that use code generated from
> the Evernote thrift files?  For example, bindings for another language
> (python, haskell, perl)?  If so, the Evernote thrift files should be in
> their own package, and this package can build-depend on it.

If you are talking about bindings in other languages (python / haskell
/ perl /...)
for *Evernote Cloud API*, then yes such projects do exist. For example,
https://github.com/evernote/evernote-sdk-python and
https://github.com/evernote/evernote-sdk-python3 and
https://github.com/evernote/evernote-sdk-perl and
https://github.com/evernote/evernote-sdk-csharp and
https://github.com/evernote/evernote-sdk-cpp .
Note that even Evernote developers does not use thrift code directly.
All files are
generated with some third-party generator. The motivation is clear:
for interpreted languages (perl/python/...), parsing thrift
description files in runtime
is too time consuming and impossible. And for compiled languages (C/C++/C#/...),
OK, they just don't bother with the regeneration process. It is a
one-shot process,
the generated c/cpp/c# source codes are still clear and readable, ready to be
embedded into other projects or made into shared library. Packaging separately
is useless to other people.

Thrift files should be regarded as language-independent source code; It does
not make sense for one package to Build-Depend to another package which
only contains some source code. Those codes should be part of its own
source code.

Is there really any previous example in Debian, that one package *should* and
*do* Build-Depend on another *binary* package that only contains some
description files or source codes?

> That would clean things up a bit, but it wouldn't help with
> QEverCloudGenerator -- I guess that no packages other than qevercloud
> itself will use that, right?  If it would be easier for you to maintain,
> you could put QEverCloudGenerator in its own package and build-depend on
> it, but that's your choice.

That would make things even more complicated and add another barely useless
binary package into Debian, so I am not intended to pack QEverCloudGenerator
separately.

> It looks like you are have removed the files you are going to regenerate
> from the upstream tarball.  That's okay, but you don't have to do it --
> you can just delete them before you regenerate them/just overwrite
> them.  See the ebib source package for a very simple example of
> regenerating a file without removing it from the upstream tarball.

I checked ebib and find that I know nothing about emacs lisp and its debhelper.
Where did it remove any file?

What I do know is that I can override dh_clean and delete some files
sooner or later.
Overwriting seems reasonable, too.

> Let me know what you think of these suggestions.

Basically I just don't want to generate more binary packages. The current source
structure is acceptable to me, and the only problem is to decide the proper way
to regenerate source code and build the library. I may choose either to hack the
debian/rules file or to patch cmake instructions. The current implementation is
to hack debian/rules.

Sincerely,
Boyuan Yang

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt

[Boyuan Yang]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

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

 * Package name: qevercloud
   Version : 3.0.2+ds-1
   Upstream Author : Dmitry Ivanov 
 * URL : https://github.com/d1vanov/QEverCloud
 * License : MIT
   Section : libs

  It builds those binary packages:

libqt4qevercloud3 - Unofficial Evernote Cloud API library for Qt4
libqt5qevercloud3 - Unofficial Evernote Cloud API library for Qt5
qt4qevercloud-dev - Development files for libqt4qevercloud
qt5qevercloud-dev - Development files for libqt5qevercloud

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/q/qevercloud/qevercloud_3.0.2+ds-1.dsc

  Alternatively, one can browse the packaging scripts on GitHub:

https://github.com/hosiet/QEverCloud

  Alternatively, one can download pre-built deb packages or download
the source package on deb-o-matic:


http://debomatic-amd64.debian.net/distribution#unstable/qevercloud/3.0.2+ds-1/

This is a new package and will work as the dependency of nixnote2
(RFS: #832704) to replace nixnote2's bundled qevercloud library source
files.

Previous discussions can be found in the nixnote2 RFS, start from Message #70:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832704#70

In order to regenerate some generated cpp source/headers files, the
source code of an extra generator
(https://github.com/d1vanov/QEverCloudGenerator) and the upstream
Thrift IDL files release by Evernote Corporation
(https://github.com/evernote/evernote-thrift) was included, which made
the build system (as written in debian/rules, plus patch in
debian/patches) somehow ugly and hacky.

I am wondering if such instructions are acceptable. Reviews and
suggestions are welcomed.

  Regards,
   Boyuan Yang

Bug#832704: RFS: nixnote2/2.0~beta8+20160727+ds-1 [ITP] -- Open Source Evernote client

[Boyuan Yang]

ker.cpp hardcodes paths to OpenOffice
> dictionaries in /opt.  They're not installed to /opt on Debian.  And
> maybe you need a dependency on libreoffice.

The software already has a dependency to libhunspell to provide spell checking
feature with top priority as stated in the source code. I believe
those legacy paths
of OO.o should not cause problems if they still exist in the source code.

Libreoffice is not needed as well, according to the author [2]. So I
am not intended
to fix it.

[2] https://github.com/baumgarr/nixnote2/issues/183#issuecomment-234800970


Plus, some typos in the source code are found and written in the PR
sent to upstream.


OK. Now I believe all copyright-related issues are fixed or explained by now.
The GitHub repository is updated and the new version has been uploaded onto
mentors.debian.net/package/nixnote2.

Let's see if there is any further question :-)

Sinerely,
Boyuan Yang

Bug#832704: RFS: nixnote2/2.0~beta8+20160727+ds-1 [ITP] -- Open Source Evernote client

[Boyuan Yang]

Hello,

2016-08-24 11:56 GMT+08:00 Sean Whitton :
>> Since it is a debian-source (ds) package, I am not sure which original 
>> tarball
>> should be provided with pristine-tar. Anyway, I put both the ds-modified and
>> the original tarball with pristine-tar inside now. (Check the
>> pristine-tar branch.)
>
> I meant the tarball that you want to have uploaded to Debian.

Got it. :)

>> FYI, this software is debian-sourced because it used to contain some
>> useless scripts (custom hacky scripts for deb / rpm / targz packaging)
>> and a jar file (which is not acceptable in Java packaging). The
>> ds-version merely delete those files.
>
> You can do this if it's convenient, but you don't need to -- it's only
> non-DFSG-free files that have to be filtered out.  You can just not
> install the .jar, which might be easier than making a +ds tarball
> everytime upstream makes a new release.

That would be great. Personally since 2.0~beta9 < 2.0~beta9+ds,
I would like to defer it to next upstream release.

> Also, you could consider using .xz compression for the orig tarball to
> save space on the Debian mirror network.  You can set that in gbp.conf
> if you're using gbp to generate tarballs.

Fixed in d/watch, d/gbp.conf and pristine-tar branch.

> On Thu, Aug 11, 2016 at 12:58:00PM +0800, Boyuan Yang wrote:
>> > Is the GitHub repo that this package is based on a fork of Nevernote?  I
>> > think you should change the Homepage: field to point at the GitHub
>> > repo.  Or are they controlled by the same person?
>>
>> They are controlled by the same person and actually they are the *same
>> project*. Actually the author is still using nevernote page on
>> Sourceforge to distribute pre-built nixnote2 packages.
>
> I filed https://github.com/baumgarr/nixnote2/issues/198

Great, I will track upstream response.

> The opencv patch has now disappeared.  Was that deliberate?

Yes. It was merged upstream.

>> > You're installing README.md but this file contains no useful
>> > information.  The README.txt file looks more useful.  Does that get
>> > installed to the help/ dir?  I couldn't tell without building the
>> > package, sorry!
>>
>> I did not install README.txt, since this file mainly describes the situation
>> of source (not the binary). Should I install it anyway?
>
> I was thinking that the index of other documentation might be useful --
> it explains the purpose of theme.ini. shortcut_howto.txt etc.
> colors.txt is an example file so it should go into
> /usr/share/doc/nixnote2/examples.

Sure. It is installed using dh_installexamples(1) now.

> There are some problems with your copyright file:
>
> - You're using an outdated format, and the URI in Format-Specification:
>   doesn't work.  Please check policy for the current format.
>
> - You need a "Files: *" paragraph, and "icons/*" doesn't need to be a
>   separate paragraph.
>
> - You should add yourself to the copyright for debian/*.
>
> - There is a syntax error too :)  In the GPL-2+ paragraph.

Hold on, are you looking at upstream copyright file?
That file is outdated and not used. Please check the file on Debian branch:

https://github.com/hosiet/nixnote2/blob/debian/debian/copyright

> - Looks like the manpage is copyright Vincent Cheng.

Fixed.

> Docs go in /usr/share/doc/nixnote2 not /usr/share/nixnote2 -- you're
> installing several to the wrong place, but some to the right place.

Fixed. Now everything other than theme.ini and shortcuts.txt are installed
as docs. The only two files are left because they are shipped as fixed config
files.

> The comments in your d/rules file are great.  Have you filed an upstream
> bug about the broken `make install`?  You could provide them with your
> d/install file to help.

Thanks, I will file the issue later. This is not of top priority.
Previously upstream did not provide the `make install' target but to rely on
`cp'. That target was added recently from a PR but the quality is poor.


I updated the GitHub repository and dsc package on mentors again.

Sincerely,
Boyuan Yang

Bug#832704: RFS: nixnote2/2.0~beta8+20160727+ds-1 [ITP] -- Open Source Evernote client

[Boyuan Yang]

Control: tag -1 -moreinfo
X-Debbugs-CC: debian-mentors@lists.debian.org

2016-08-21 1:02 GMT+08:00 Sean Whitton :
> control: tag -1 +moreinfo
>
> Please don't edit published history -- I wanted to use `git diff` to
> check the changes you had made in response to my review, but now I have
> to just check the whole package from scratch.

Thank you for your advice. I will not force-push commits from now on.

> Could you confirm that https://github.com/hosiet/nixnote2 is the version
> that should be reviewed, please?

Yes. To be more concrete, commit d9e10186a9433a3ca57b8c75427e1926b0164fbc
on branch "debian" is the current debian packaging branch. Commit
b2d66576bb2b9a3c33fa7cc6af69f703082b54d8 on branch master is the
ds-modified upstream source code, and "upstream" branch is the original
upstream release.

> (I can obtain the tarball from mentors, but you might consider adding it
> to your git repository using pristine-tar(1).)

Since it is a debian-source (ds) package, I am not sure which original tarball
should be provided with pristine-tar. Anyway, I put both the ds-modified and
the original tarball with pristine-tar inside now. (Check the
pristine-tar branch.)

FYI, this software is debian-sourced because it used to contain some useless
scripts (custom hacky scripts for deb / rpm / targz packaging) and a jar file
(which is not acceptable in Java packaging). The ds-version merely delete
those files.

The newly-packaged nixnote2 version 2.0~beta9+ds has been pushed onto
https://mentors.debian.net/package/nixnote2 and GitHub, in which the only
change is to enable pristine-tar support.

Thanks and I am still looking forward to further review and sponsorship.

--
Regards,
Boyuan Yang

Bug#832704: RFS: nixnote2/2.0~beta9+ds-1 [ITP] -- Open Source Evernote client

[Boyuan Yang]

Control: reopen -1
Control: tag -1 -moreinfo
X-Debbugs-CC: locutusofb...@debian.org
X-Debbugs-CC: spwhit...@spwhitton.name
X-Debbugs-CC: a...@debian.org

Hello all,

Sorry for the accidentally removal of nixnote2 from
mentors.debian.net. Upstream tagged the new version days ago and I was
trying to upload the latest version. The final version should be on
mentors now.

I believe the package is suitable for another review again. The java
part of the package was reviewed by Markus on debian-java already [1]
and other problems raised by Sean was fixed too.

You may obtain the source package from mentors.debian.net for dsc file
[2] and ds-suffixed source tarball [3].

Looking forward to further review and sponsorship.

[1] https://lists.debian.org/debian-java/2016/08/msg00038.html
[2] 
https://mentors.debian.net/debian/pool/main/n/nixnote2/nixnote2_2.0~beta9+ds-1.dsc
[3] 
https://mentors.debian.net/debian/pool/main/n/nixnote2/nixnote2_2.0~beta9+ds.orig.tar.gz

--
Sincerely,
Boyuan Yang

Bug#832704: RFS: nixnote2/2.0~beta8+20160727+ds-1 [ITP] -- Open Source Evernote client

[Boyuan Yang]

> I can't sponsor the upload, but I hope the following review is useful to
> you.

Thank you very much for your detailed review. I would like to explain
those problems here for you and anyone who might be interested:

> Since I am not familiar with Java packaging, it would be advisable to
> ask on the Debian java packaging group mailing list for someone to
> review those parts of the package.

OK,  I will take a try.

> Must-fixes
> --
>
> Is the GitHub repo that this package is based on a fork of Nevernote?  I
> think you should change the Homepage: field to point at the GitHub
> repo.  Or are they controlled by the same person?

They are controlled by the same person and actually they are the *same
project*. Actually the author is still using nevernote page on
Sourceforge to distribute pre-built nixnote2 packages.

> Your version number indicates that you are packaging a beta release.
> Generally, only full upstream releases are uploaded to Debian unstable,
> rather than testing releases/release candidates.  Is there some good
> reason for using this version?

Upstream is keeping "beta" string in version for several years and
there is no sign that he/she will make a "non-beta" release in near
future. However the function of nixnote2 is complete and everything
works well now. Personally I think it is suitable for the release.

> The description of the "exclude opencv linking" doesn't explain why
> opencv support is disabled "for now".  Please explain.

In upstream trunk the opencv-related functions are disabled and
removed. The developer intends to make it into a plugin, so I disabled
related builds. What's more, I noticed that Debian is preparing
opencv2-3 transition, so my personal preference is to pack the
opencv-related plugin after the transition is completed.

> Vcs-* should point at your packaging repository, not the upstream git
> repository.

Yes. I am pointing to my packaging repository.

> You should remove the "ignore-branch" and "builder" settings from
> gbp.conf.  Those should only be set in ~/.gbp.conf or /etc/gbp.conf.

Thanks. I will fix it later.

> I can't try building and installing this package because I can't get a
> correct orig tarball.  The version on mentors seems to be out-of-date,
> and the version the watch file downloads conflicts with your
>  repo (which is what I'm looking
> at).  How can I get the correct orig tarball?

Really sorry I did not try to build from mentors. I will look into it
afterwards.

> Suggested improvements
> --
>
> There are a lot of build-dependencies.  It would be nice to run
> `wrap-and-sort -abst`.

Sure I will fix it.

> README.Debian is meant for users, but what you have written in there is
> only really relevant to Debian contributors.  Perhaps rename it to
> README.source, or just remove it.  You could also cite the relevant
> section of policy (and the version of policy in which the section had
> that number).

Thanks, I will try.

> The watch file looks like it will only work for the current version,
> because the repack suffix contains a part of the current version
> string.  Could it be made more general?

Sure. Will be fixed after next upstream release.

> Could you explain why you Recommends: mimetex and Suggests: cups?

Mimetex is used for latex support of evernote notes, as described by the author.
Cups is needed for note printing, but it is totally fine not to
install it if the user do not need to print.

> You're installing README.md but this file contains no useful
> information.  The README.txt file looks more useful.  Does that get
> installed to the help/ dir?  I couldn't tell without building the
> package, sorry!

I did not install README.txt, since this file mainly describes the situation
of source (not the binary). Should I install it anyway?

> I'm not sure you need to override dh_installchangelogs.  It usually
> detects filenames like 'changelog.txt'.  But I might be wrong.
>
> At debhelper compat 9, I think that you could remove a lot of lines from
> your rules file.  For example, you probably don't need these lines:
>
> DPKG_EXPORT_BUILDFLAGS = 1
> include /usr/share/dpkg/default.mk
> include /usr/share/dpkg/buildflags.mk

Thanks for these advices, I will try it out.

Bug#832704: RFS: nixnote2/2.0~beta8+20160727+ds-1 [ITP] -- Open Source Evernote client

[Boyuan Yang]

Package: sponsorship-requests
Severity: wishlist

Package: sponsorship-requests
Severity: wishlist

Dear mentors,
I am looking for a sponsor for my package "nixnote2"

* Package name: nixnote2
  Version : 2.0~beta8+20160727+ds-1
  Upstream Author : Randy Baumgarte 
* URL : http://nevernote.sourceforge.net/
* License : GPL-2
  Section : utils

It builds those binary packages:

nixnote2 - Open Source Evernote client

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

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

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

dget -x
https://mentors.debian.net/debian/pool/main/n/nixnote2/nixnote2_2.0~beta8+20160727+ds-1.dsc

Alternatively, one can access package debian/ directory via git from URL:

https://github.com/hosiet/nixnote2.git

Regards,
Boyuan Yang

In need of help before RFS

[Boyuan Yang]

Hello all,

I am working on my ITP for nixnote2, an open-source Evernote desktop
client (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609849) and
met some problems. I hope someone could help solve my problems here:

1. Upstream put some *CA certificates* of VeriSign and Thawte inside
repository and intends to install it into final binary package. I
don't know how to write copyright information for these files.  What
should I do to deal with this problem?

BTW, I looked into the source package of `ca-certificates' and found
that those CA certificates was provided by Mozilla in MPL-2.0 in a
completely different type and was somehow transformed into usable
certificates when building binary package.

2. Even though it is a C++/Qt project, upstream is providing a small
prebuilt .jar file for feature enhancement. The source code for the
.jar file is provided as well. Does it mean that I should drop
prebuilt jar file and rebuild it from source code utilizing the
toolchain of Java during building process?

3. When adding debian-specific patches, do I have to write
pseudo-headers for patch diff file? It is clear that patches generated
by dpkg-source or gbp provides such patches templates as well as "diff
--git" format diff files, but when I am trying to manage patches with
quilt, the generated patches are just plain traditional "diff -u"
style patch files.

4. There is one source file which is licensed under
*public-domain*(see the d/copyright file for detail, the whole project
is under GPL-2 though). I found some words about this situation
(https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#public-domain)
but still have little idea about writing correct copyright paragraph
in debian/copyright file. Should I just leave the body of license
empty, or should I add some description words here? And should I leave
the copyright-holder line empty, or just delete the "Copyright: "
line? I am in need of your suggestions. A concrete example would be
much appreciated.

For those who may be interested, my current work is hosted on
https://github.com/hosiet/nixnote2 .

Thanks,
Boyuan Yang