Bug#884665: RFS: ooniprobe/2.2.0-1.1 [NMU]

2017-12-18 Thread Nicolas Braud-Santoni
Package: sponsorship-requests
Severity: normal
Control: block 884370 by -1
Control: tag 884370 + pending
X-Debbugs-CC: i...@debian.org, j...@debian.org

Dear mentors,

I am looking for a sponsor for the package “ooniprobe”:

 * Package name: ooniprobe
   Version : 2.2.0-1.1
 * URL : https://ooni.torproject.org/
 * License : BSD-2
   Section : contrib/net


The source package can be found on mentors.debian.org:

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

Alternatively, the packaging repository is available on alioth.d.o:

https://anonscm.debian.org/git/pkg-privacy/packages/ooniprobe.git


Changes since the last upload:

  * Non-maintainer upload
Cleared with irl@
  * debian/control
* Suggest obfs4proxy rather than obfsproxy (Closes: #884370)
* Declare compliance with policy v4.1.2
  Switched to `Priority: optional`
* Switch to debhelper 10



Best,

  nicoo


signature.asc
Description: PGP signature


Bug#884429: Uploaded to unstable

2017-12-18 Thread Nicolas Braud-Santoni
Control: reopen -1

Upload was rejected (something something non-existing signature file referenced
in .changes); I'm just reopening this so we don't forget about it.


signature.asc
Description: PGP signature


Bug#884665: marked as done (RFS: ooniprobe/2.2.0-1.1 [NMU])

2017-12-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 Dec 2017 11:18:22 +
with message-id 
and subject line Re: Bug#884665: RFS: ooniprobe/2.2.0-1.1 [NMU]
has caused the Debian Bug report #884665,
regarding RFS: ooniprobe/2.2.0-1.1 [NMU]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
884665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Control: block 884370 by -1
Control: tag 884370 + pending
X-Debbugs-CC: i...@debian.org, j...@debian.org

Dear mentors,

I am looking for a sponsor for the package “ooniprobe”:

 * Package name: ooniprobe
   Version : 2.2.0-1.1
 * URL : https://ooni.torproject.org/
 * License : BSD-2
   Section : contrib/net


The source package can be found on mentors.debian.org:

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

Alternatively, the packaging repository is available on alioth.d.o:

https://anonscm.debian.org/git/pkg-privacy/packages/ooniprobe.git


Changes since the last upload:

  * Non-maintainer upload
Cleared with irl@
  * debian/control
* Suggest obfs4proxy rather than obfsproxy (Closes: #884370)
* Declare compliance with policy v4.1.2
  Switched to `Priority: optional`
* Switch to debhelper 10



Best,

  nicoo


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi,

Uploaded.

Thanks,
Iain.



signature.asc
Description: OpenPGP digital signature
--- End Message ---


Bug#884697: RFS: logrotate/3.13.0-1 ITA

2017-12-18 Thread Christian Göttsche
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: logrotate
  Version : 3.13.0-1
  Upstream Author : Kamil Dudka 
* URL : https://github.com/logrotate/logrotate/
* License : GNU General Public License v2.0
  Section : admin

It builds those binary packages:

  logrotate  - Log rotation utility

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/l/logrotate/logrotate_3.13.0-1.dsc

The source of the package can be found at
https://github.com/cgzones/logrotate_deb.

Changes since the last upload:

logrotate (3.13.0-1) unstable; urgency=medium

  * New upstream version 3.13.0 (Closes: #879262)

  * debian:
- Switch to debhelper 10
- Support logrotation triggered by systemd timer

- control:
  + Set myself as maintainer
  + Bump standards version to 4.1.1
  + Update vcs fields
  + add minimal autotest suite
- cron.daily: Align with upstream
- logrotate.conf: align with upstream
- patches:
  + Refresh patches, drop upstream applied ones
  + spelling fix
  + add upstream patch about .dpkg-tmp taboo
- rules:
  + Enable hardening
  + Add dh_missing --fail-missing
  + Simplify statefile change
  + set correct path for mail command

 -- Christian Göttsche   Mon, 18 Dec 2017 13:28:48 +0100


Regards,
   Christian Göttsche



Bug#884740: RFS: pokemmo/1.4.2-1 [ITP] -- Multiplayer online game based on the Pokemon universe

2017-12-18 Thread Carlos Donizete Froes
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: pokemmo
   Version : 1.4.2-1
   Upstream Author : Carlos Donizete Froes 
 * URL : https://github.com/coringao/pokemmo
 * License : GPL-3.0+
   Section : contrib/games

  It builds those binary packages:

  pokemmo - Online game based on the Pokemon universe

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/contrib/p/pokemmo/pokemmo_1.4.2-1.dsc

  More information about PokeMMO can be obtained from https://pokemmo.eu.

  Regards,
   Carlos Donizete Froes


Bug#884651: RFS: stlcmd/1.0-1 [ITP]

2017-12-18 Thread Adam Borowski
On Sun, Dec 17, 2017 at 09:54:10PM -0700, John Allwine wrote:
>  * Package name: stlcmd
>Version : 1.0-1

>   stlcmd - Suite of commands for generating, inspecting and
> manipulating STL files.

Alas, it fails to build:
/bin/sh: 2: help2man: not found

I also don't see any copyright data for src/csgjs/ which obviously comes
from a different set of authors.

The .orig tarball's signature seems to be missing -- despite you apparently
wanting it to be signed (debian/upstream/signing-key.asc is present).

The target distribution is set to UNRELEASED, I assume you wanted unstable
instead, right?


Meow!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.



Bug#883751: marked as done (RFS: deepin-calculator/1.0.1-1 [ITP])

2017-12-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 Dec 2017 21:58:48 +0100
with message-id <20171218205848.ux5z5o7psywdg...@angband.pl>
and subject line Re: Bug#883751: RFS: deepin-calculator/1.0.1-1 [ITP]
has caused the Debian Bug report #883751,
regarding RFS: deepin-calculator/1.0.1-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Dear mentors,

I am looking for a sponsor for my package "deepin-calculator"

 * Package name: deepin-calculator
   Version : 1.0.1-1
   Upstream Author : Deepin Technology Co., Ltd.
 * URL : https://github.com/linuxdeepin/deepin-calculator
 * License : GPL-3+
   Section : math


  It builds those binary packages:

deepin-calculator - Calculator for deepin

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

  https://mentors.debian.net/package/deepin-calculator

  Git repo:

https://anonscm.debian.org/git/pkg-deepin/deepin-calculator.git

Regards,
Yangfl
--- End Message ---
--- Begin Message ---
On Thu, Dec 07, 2017 at 04:04:41PM +0800, Yangfl wrote:
>  * Package name: deepin-calculator
>Version : 1.0.1-1

> deepin-calculator - Calculator for deepin

✓

-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.--- End Message ---


Bug#881199: marked as done (RFS: python-coloredlogs/7.3-1)

2017-12-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 Dec 2017 22:25:09 +0100
with message-id <20171218212509.z7blvnrzpgz3y...@angband.pl>
and subject line Re: Bug#881199: RFS: python-coloredlogs/7.3-1
has caused the Debian Bug report #881199,
regarding RFS: python-coloredlogs/7.3-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
881199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the following package:

* Package name: coloredlogs
  Version : 7.3-1
  Upstream Author : Peter Odding 
* URL : https://coloredlogs.readthedocs.io
* License : Expat
  Section : python

Please check out the package by visiting the following URL:


https://anonscm.debian.org/cgit/python-modules/packages/python-coloredlogs.git

Changes since the last upload:

  * New upstream version 7.3
  * Bump the standards version to 4.1.1
  * Add recommended get-orig-source target

Best regards,
Ghis
--- End Message ---
--- Begin Message ---
On Wed, Nov 08, 2017 at 07:42:26PM +, Ghislain Vaillant wrote:
> * Package name: coloredlogs
>   Version : 7.3-1

> Changes since the last upload:
> 
>   * New upstream version 7.3
>   * Bump the standards version to 4.1.1
>   * Add recommended get-orig-source target

✓

-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.--- End Message ---


Bug#884651: RFS: stlcmd/1.0-1 [ITP]

2017-12-18 Thread John Allwine
Thanks Adam!

Ack, I just introduced that help2man issue fixing the lintian warnings about 
man pages. Will reorganize a bit to fix that.

The signing-key.asc is for uscan when checking for updates in the watch. Am I 
supposed to sign the orig tar ball?

I left it as UNRELEASED as that was suggested in the walkthrough I went 
through. I can change it to unstable.

Will add the original license of CSG.js as well.

John Allwine
Owner of Allwine Designs
http://www.allwinedesigns.com

> On Dec 18, 2017, at 3:29 PM, Adam Borowski  wrote:
> 
>> On Sun, Dec 17, 2017 at 09:54:10PM -0700, John Allwine wrote:
>> * Package name: stlcmd
>>   Version : 1.0-1
> 
>>  stlcmd - Suite of commands for generating, inspecting and
>> manipulating STL files.
> 
> Alas, it fails to build:
> /bin/sh: 2: help2man: not found
> 
> I also don't see any copyright data for src/csgjs/ which obviously comes
> from a different set of authors.
> 
> The .orig tarball's signature seems to be missing -- despite you apparently
> wanting it to be signed (debian/upstream/signing-key.asc is present).
> 
> The target distribution is set to UNRELEASED, I assume you wanted unstable
> instead, right?
> 
> 
> Meow!
> -- 
> // If you believe in so-called "intellectual property", please immediately
> // cease using counterfeit alphabets.  Instead, contact the nearest temple
> // of Amon, whose priests will provide you with scribal services for all
> // your writing needs, for Reasonable And Non-Discriminatory prices.



Bug#884429: Uploaded to unstable

2017-12-18 Thread Gianfranco Costamagna
control: close -1
On Mon, 18 Dec 2017 17:31:27 +0100 Nicolas Braud-Santoni 
 wrote:
> Control: reopen -1
> 
> Upload was rejected (something something non-existing signature file 
> referenced
> in .changes); I'm just reopening this so we don't forget about it.

I'm trying harder.

G.



signature.asc
Description: OpenPGP digital signature


Bug#884651: RFS: stlcmd/1.0-1 [ITP]

2017-12-18 Thread Adam Borowski
On Mon, Dec 18, 2017 at 06:36:00PM -0700, John Allwine wrote:
> Thanks Adam! I really appreciate you taking the time to look through
> this. I'm still unclear on how to include the .asc file in my upload.
> The dput command takes the .changes file, which determines which files
> are uploaded, so how do I include the .asc file since it's not listed?
> Do I manually edit the .changes file? Is there another method with
> more control over what I upload?

Just have it in the parent directory when you build the source (with
dpkg-buildpackage -S or a wrapper which calls it), next to .orig.


Meow!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.



Bug#884651: RFS: stlcmd/1.0-1 [ITP]

2017-12-18 Thread Adam Borowski
On Mon, Dec 18, 2017 at 04:00:53PM -0700, John Allwine wrote:
> The signing-key.asc is for uscan when checking for updates in the watch. 
> Am I supposed to sign the orig tar ball?

Well, how else can uscan verify it?
It's also used to verify the orig tarball once it's in the archive.

On the other hand, signed tarballs are far less useful when maintainer is
the same person as upstream -- you don't need to rely on any untrusted
paths.

> I left it as UNRELEASED as that was suggested in the walkthrough I went
> through.  I can change it to unstable.

Usually, UNRELEASED means the package is not yet ready for uploading.  This
obviously conflicts with a request to upload the package to the official
archive.  I can change this myself, but it's better to ask.

> Will add the original license of CSG.js as well.

Both the fork and the original have plausibly looking statements on their
front pages on GitHub.  That is:

Copyright (c) 2012 Joost Nieuwenhuijse (jo...@newhouse.nl)
Copyright (c) 2011 Evan Wallace (http://madebyevan.com/)
License: MIT


Meow!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.



Bug#884651: RFS: stlcmd/1.0-1 [ITP]

2017-12-18 Thread John Allwine
> Well, how else can uscan verify it?
> It's also used to verify the orig tarball once it's in the archive.
The watch file describes how to download the upstream tar ball and its
signature file. I'm not sure what to do here. Right now I do a debsign
on the .changes file and it signs the .dsc file as well. Then I use
dput which uploads all the files listed in the changes file to
mentors.debian.net. Do I manually sign the .orig file before that?

> Usually, UNRELEASED means the package is not yet ready for uploading.  This
> obviously conflicts with a request to upload the package to the official
> archive.  I can change this myself, but it's better to ask.
I changed this to unstable.

> Both the fork and the original have plausibly looking statements on their
> front pages on GitHub.  That is:
>
> Copyright (c) 2012 Joost Nieuwenhuijse (jo...@newhouse.nl)
> Copyright (c) 2011 Evan Wallace (http://madebyevan.com/)
> License: MIT

I added those as well as 2017 @jscad, which is listed in the LICENSE
file in its github repo.

As for the help2man issues. I added help2man to the Build-Depends
field in debian/control, is that all I need to do? How do I test that
it works?

My latest changes are up: https://mentors.debian.net/package/stlcmd



Bug#882116: reopening RFS: sqlcl-package/0.1.0 [ITP]

2017-12-18 Thread Lazarus Long
As requested by Chris Lamb a justification of why the package should
be native was added to the changelog, hence it needs sponsoring again
to be uploaded back to the NEW queue.

Thank you very much,

-- 
Lazarus



Bug#884651: RFS: stlcmd/1.0-1 [ITP]

2017-12-18 Thread John Allwine
Maybe I'm using an old version that doesn't pick that up? Or I'm not
naming it correctly? Here's the script that I run in an unbuntu docker
image: 
https://github.com/AllwineDesigns/build_stlcmd_deb/blob/master/build_stlcmd.sh
( (If you have docker installed you can clone that repo and do a
docker build . to try it out)
You can see at line 11 that I'm downloading the .asc file (right after
downloading the .orig file). At the bottom I'm using debuild to build
the package, but it's not picking up the .asc file.

On Mon, Dec 18, 2017 at 6:41 PM, Adam Borowski  wrote:
> On Mon, Dec 18, 2017 at 06:36:00PM -0700, John Allwine wrote:
>> Thanks Adam! I really appreciate you taking the time to look through
>> this. I'm still unclear on how to include the .asc file in my upload.
>> The dput command takes the .changes file, which determines which files
>> are uploaded, so how do I include the .asc file since it's not listed?
>> Do I manually edit the .changes file? Is there another method with
>> more control over what I upload?
>
> Just have it in the parent directory when you build the source (with
> dpkg-buildpackage -S or a wrapper which calls it), next to .orig.
>
>
> Meow!
> --
> // If you believe in so-called "intellectual property", please immediately
> // cease using counterfeit alphabets.  Instead, contact the nearest temple
> // of Amon, whose priests will provide you with scribal services for all
> // your writing needs, for Reasonable And Non-Discriminatory prices.



Bug#884651: marked as done (RFS: stlcmd/1.0-1 [ITP])

2017-12-18 Thread Debian Bug Tracking System
Your message dated Tue, 19 Dec 2017 02:03:22 +0100
with message-id <20171219010322.i5hea3tp5cxn5...@angband.pl>
and subject line Re: Bug#884651: RFS: stlcmd/1.0-1 [ITP]
has caused the Debian Bug report #884651,
regarding RFS: stlcmd/1.0-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Dear mentors,

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

 * Package name: stlcmd
   Version : 1.0-1
   Upstream Author : John Allwine 
 * URL : https://www.github.com/AllwineDesigns/stl_cmd
 * License : GPL
   Section : misc

It builds those binary packages:

  stlcmd - Suite of commands for generating, inspecting and
manipulating STL files.

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/s/stlcmd/stlcmd_1.0-1.dsc

  More information about stl_cmd can be obtained from
https://www.allwinedesigns.com/blog/stlcmd.

  Changes since the last upload:

  * Initial release. (Closes: #884310)


  Regards,
   John Allwine
--- End Message ---
--- Begin Message ---
On Mon, Dec 18, 2017 at 05:35:54PM -0700, John Allwine wrote:
> The watch file describes how to download the upstream tar ball and its
> signature file. I'm not sure what to do here. Right now I do a debsign
> on the .changes file and it signs the .dsc file as well. Then I use
> dput which uploads all the files listed in the changes file to
> mentors.debian.net. Do I manually sign the .orig file before that?

The tarball is properly signed on Github.  The watch file also correctly
refers to it.  What was missing, was the .asc file in your upload to
mentors.  All I had to do was to force uscan to download current version
(uscan -ddv) and repack the source.

It's fine now.  You'd just want to remember, the next time you'll upload
Debian packaging of a new upstream release, to have the .asc file sitting on
the disk next to the orig tarball -- the tools will do the right thing
automatically.

> > Both the fork and the original have plausibly looking statements on their
> > front pages on GitHub.  That is:
> >
> > Copyright (c) 2012 Joost Nieuwenhuijse (jo...@newhouse.nl)
> > Copyright (c) 2011 Evan Wallace (http://madebyevan.com/)
> > License: MIT
> 
> I added those as well as 2017 @jscad, which is listed in the LICENSE
> file in its github repo.

Looks fine to me.

> As for the help2man issues. I added help2man to the Build-Depends
> field in debian/control, is that all I need to do? How do I test that
> it works?

By building in a fresh clean environment.  Of the two tools which automate
this, pbuilder is slower but a lot easier to use.

> My latest changes are up: https://mentors.debian.net/package/stlcmd

Looks great.  Uploaded to NEW; any additional changes can go as -2.


Meow!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.--- End Message ---


Bug#884752: RFS: fcitx-skk/0.1.4-0.2 [NMU]

2017-12-18 Thread Boyuan Yang
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: pkg-ime-de...@lists.alioth.debian.org yyat...@debian.or.jp 
d...@debian.org

Dear mentors,

I am looking for a sponsor for package "fcitx-skk" as an NMU.

This NMU would move package fcitx-skk under pkg-ime team. It has been approved 
by its original maintainer, see [1].

[1] 
https://lists.alioth.debian.org/pipermail/pkg-ime-devel/2017-December/006719.html

 * Package name: fcitx-skk
   Version : 0.1.4-0.2
   Upstream Author : Weng Xuetian 
 * URL : https://github.com/fcitx/fcitx-skk
 * License : GPL-2+
   Section : utils

  It builds those binary packages:

fcitx-skk  - Japanese SKK input engine for Fcitx

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

  https://mentors.debian.net/package/fcitx-skk


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

dget -x 
https://mentors.debian.net/debian/pool/main/f/fcitx-skk/fcitx-skk_0.1.4-0.2.dsc

  Git packaging repository:

http://anonscm.debian.org/git/collab-maint/fcitx-skk.git

  Plain diff:

commit 0e217f89ece547c5c00857a1eb6d9cb21aa82091
Author: Boyuan Yang <073p...@gmail.com>
Date:   Mon Dec 18 19:28:48 2017 +0800

debian: Prepare NMU to switch pkg into pkg-ime team

diff --git a/debian/changelog b/debian/changelog
index bbdaf6d..f7ee608 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+fcitx-skk (0.1.4-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Put package into pkg-ime team with maintainer's approval.
+
+ -- Boyuan Yang <073p...@gmail.com>  Mon, 18 Dec 2017 19:27:51 +0800
+
 fcitx-skk (0.1.4-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --git a/debian/control b/debian/control
index 4f75f3d..dd0b1c3 100644
--- a/debian/control
+++ b/debian/control
@@ -1,7 +1,9 @@
 Source: fcitx-skk
 Section: utils
 Priority: optional
-Maintainer: Yusuke YATSUO 
+Maintainer: IME Packaging Team 
+Uploaders:
+ Yusuke YATSUO ,
 Build-Depends: cmake,
debhelper (>= 9),
fcitx-bin (>= 1:4.2.6),

  Changes since the last upload:

fcitx-skk (0.1.4-0.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Put package into pkg-ime team with maintainer's approval.

 -- Boyuan Yang <073p...@gmail.com>  Mon, 18 Dec 2017 19:27:51 +0800

Regards,
Boyuan Yang

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


Bug#884752: [Pkg-ime-devel] Bug#884752: RFS: fcitx-skk/0.1.4-0.2 [NMU]

2017-12-18 Thread Aron Xu
Please don't update for only a maintainer change, it's kinda a waste
of resource.


-- 
Regards,
Aron Xu