Bug#876667: RFS: pragha/1.3.3-1

2017-09-24 Thread Gabriel F. T. Gomes 
Hi, Lukas,

Thanks for the new round of reviews.  You're making me learn a ton.
:)

On 24 Sep 2017, Lukas Schwaighofer wrote:

>On Sun, 24 Sep 2017 15:15:41 -0300
>"Gabriel F. T. Gomes"  wrote:
>>
>> In that same message [1], you suggested the use of a version control
>> system, but I don't know where to make it public (I know that alioth
>> is being discontinued, so I'm a bit lost with this).  
>
>I hope someone here will have a suggestion where your repository can
>live.

In the meantime, I can keep it in my personal server [1].  However, I
don't think it's a good place for keeping it in the long run, because I
do not fully trust myself as a sysadmin.  Hehehe.

[1] 
http://git.inconstante.eti.br/?p=pragha-debian.git;a=shortlog;h=refs/heads/unstable

>* The upstream tarball you uploaded to mentors is not exactly the same
>  one as on github:
>
>$ cmp pragha-1.3.3.tar.gz pragha_1.3.3.orig.tar.gz 
>pragha-1.3.3.tar.gz pragha_1.3.3.orig.tar.gz differ: byte 5, line 1

Where did you get pragha-1.3.3.tar.gz from?
I got it from 
https://github.com/pragha-music-player/pragha/archive/v1.3.3.tar.gz.

The files are not exactly the same, as you mentioned, but their
contents, after extraction, are identical.

>  If you use git and git-buildpackage, make sure to use the
>  "pristine-tar" feature.  When using this, a small delta file will be
>  added to a special pristine-tar branch.  This allows to reconstruct
>  the original tarball exactly as it was.

I wasn't aware of git-buildpackage, so I was making the tarball by hand
and building with debuild.  Thanks for pointing this out.  On the other
hand, I still do not understand how git-buildpackage works.  All my
attempts to use it still resulted in a source tarball (.orig.tar.gz)
that is not exactly the same as the tarball from upstream.

>* In the debian/watch file you should replace "" with
>  "pragha" (it also works as is, but then the downloaded tarball is
>  called "-1.3.3.tar.gz" before the symlink is created).

Done.

>* in debian/patches/fix-appstream-errors.patch:
>  - referencing the ITP bug here does not make sense; you should only
>use "Bug-Debian" if there is a bug in the Debian BTS that is
>related to the patch (for example, if someone reported in the
>Debian BTS that the appstream xml data is wrong)
>  - Instead here you should record the URL of your pull request:
>
>  Bug: https://github.com/pragha-music-player/pragha/pull/125

Makes sense.  Done.


I uploaded a new package, which contains these changes and which was
built with git-buildpackage.

Best regards,
Gabriel

Bug#869806: Update

2017-09-24 Thread Adam Borowski 
On Sun, Sep 24, 2017 at 11:04:35PM +, Julien Hartmann wrote:
> I updated the package from upstream release, which accounts for
> feedback from Adam. Thanks again to him for the time he took to try it
> despite not having the relevant hardware to test.
> 
>   * Compilation on non-x86 platforms should be fixed (tested on arm64).
> 
> New version is 0.5.0-1. It can be downloaded with
> 
> dget -x 
> https://mentors.debian.net/debian/pool/main/k/keyleds/keyleds_0.5.0-1.dsc

Cool!

> >> I see you're going to have trouble finding someone who can meaningfully
> >> review the package: it can't be tested without relevant hardware.  I for 
> >> one
> >> have a non-gaming Logitech keyboard, this daemon doesn't speak to it (not
> >> surprising -- no LEDs other than Num/Caps/Scroll).

For the bug log: I will _not_ sponsor this.

The way the daemon is started and integrated is quite complex, I don't
really know how it should be done, thus without a way to test any review
I can do would be worthless.  This differs from an untestable package
with generic packaging (like some s390-only thingy I just uploaded).

I'd recommend bothering someone who has a clue about udev and DE startup.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts
⣾⠁⢰⠒⠀⣿⡁ productivity.  You can read it, too, you just need the
⢿⡄⠘⠷⠚⠋⠀ right music while doing so.  I recommend Skepticism
⠈⠳⣄ (funeral doom metal).

Bug#869806: Update

2017-09-24 Thread Julien Hartmann 
Hello,

I updated the package from upstream release, which accounts for
feedback from Adam. Thanks again to him for the time he took to try it
despite not having the relevant hardware to test.

  * Compilation on non-x86 platforms should be fixed (tested on arm64).

New version is 0.5.0-1. It can be downloaded with

dget -x 
https://mentors.debian.net/debian/pool/main/k/keyleds/keyleds_0.5.0-1.dsc

Thanks!


On Fri, Sep 22, 2017 at 12:28 PM, Julien Hartmann
 wrote:
> Hello,
>
> Noted, I'll keep updating there then, hoping for the best.
>
> Thanks for taking the time to try and build it.
> Yes, gaming keyboards expose a second HID interface to deal with
> non-standard features, and that's the one keyleds talks to. So it just
> shouldn't find any device if no gaming keyboard is connected.
>
> Being able to build it on non-x86 platforms is definitely part of the
> objectives. It was created with this in mind, though actual tests are
> still on the "TODO" side of the list. I missed the fact that
> __builtin_cpu_init only exists on platforms where gcc actually detects
> things. I'm opening an issue for this and fix will be in next release.
>
> Thanks!
>
>
> On Thu, Sep 21, 2017 at 9:43 PM, Adam Borowski  wrote:
>> On Thu, Sep 21, 2017 at 01:17:57PM +, Julien Hartmann wrote:
>>> Hello,
>>> I updated the package from upstream. I don't know if I am supposed to
>>> file another RFS or just append to this one?
>>
>> The previous one hasn't been sponsored yet, so you're merely updating the
>> request rather than asking for a new upload.  Appending to the RFS bug is
>> preferred.  One sponsored upload -- one RFS.
>>
>>> New version is 0.4.3-1. It can be downloaded with
>>> dget -x 
>>> https://mentors.debian.net/debian/pool/main/k/keyleds/keyleds_0.4.3-1.dsc
>>
>> I see you're going to have trouble finding someone who can meaningfully
>> review the package: it can't be tested without relevant hardware.  I for one
>> have a non-gaming Logitech keyboard, this daemon doesn't speak to it (not
>> surprising -- no LEDs other than Num/Caps/Scroll).
>>
>> The package fails to build on architectures other than amd64 and i386, as
>> its code to detect ISA extensions uses x86-only features despite obvious
>> attempts of the build system to be portable.  It'd be nice to fix this as
>> fancy-schmancy keyboards are in no way x86-specific: you can attach one both
>> to an $89 Pinebook (arm64) or to a $6.5k Talos 2 (ppc64el).
>>
>>
>> Meow!
>> --
>> ⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts
>> ⣾⠁⢰⠒⠀⣿⡁ productivity.  You can read it, too, you just need the
>> ⢿⡄⠘⠷⠚⠋⠀ right music while doing so.  I recommend Skepticism
>> ⠈⠳⣄ (funeral doom metal).

Bug#871693: RFS: tinymux/2.10.1.14-1 [RC]

2017-09-24 Thread Stephen Dennis 
Control: tags 871693 - moreinfo


On Sun, Sep 24, 2017 at 2:16 PM, Stephen Dennis 
wrote:

> The latest package at mentors has the version restriction removed.
>
> On Wed, Aug 16, 2017 at 1:03 PM, Andrey Rahmatullin 
> wrote:
>
>> On Wed, Aug 16, 2017 at 01:00:21PM -0600, Stephen Dennis wrote:
>> > > > > By the way, binutils (>= 2.28.0) is wrong, as 2.28-1 is not >=
>> 2.28.0.
>> > > > >
>> > > >
>> > > > Fixing.
>> > > You've changed it to >= 2.25-5. Why? Also, why this restriction is
>> needed?
>> > >
>> >
>> > I don't know what the guidance is for versions, so I picked the versions
>> > for Jessie (oldstable). There's nothing in the code that would prevent
>> it
>> > from being built with older versions of these dependencies.
>> Then why do you have a version restriction at all?
>>
>> --
>> WBR, wRAR
>>
>
>

Bug#871693: RFS: tinymux/2.10.1.14-1 [RC]

2017-09-24 Thread Stephen Dennis 
The latest package at mentors has the version restriction removed.

On Wed, Aug 16, 2017 at 1:03 PM, Andrey Rahmatullin  wrote:

> On Wed, Aug 16, 2017 at 01:00:21PM -0600, Stephen Dennis wrote:
> > > > > By the way, binutils (>= 2.28.0) is wrong, as 2.28-1 is not >=
> 2.28.0.
> > > > >
> > > >
> > > > Fixing.
> > > You've changed it to >= 2.25-5. Why? Also, why this restriction is
> needed?
> > >
> >
> > I don't know what the guidance is for versions, so I picked the versions
> > for Jessie (oldstable). There's nothing in the code that would prevent it
> > from being built with older versions of these dependencies.
> Then why do you have a version restriction at all?
>
> --
> WBR, wRAR
>

Bug#876649: marked as done (RFS: qterm/1:0.7.2-1)

2017-09-24 Thread Debian Bug Tracking System 
Your message dated Sun, 24 Sep 2017 22:07:06 +0200
with message-id <20170924200706.bemn7jntvbnkv...@angband.pl>
and subject line Re: Bug#876649: RFS: qterm/1:0.7.2-1
has caused the Debian Bug report #876649,
regarding RFS: qterm/1:0.7.2-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.)


-- 
876649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
On Sun, Sep 24, 2017 at 07:43:23PM +0800, Boyuan Yang wrote:
>  * Package name: qterm
>Version : 1:0.7.2-1

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

✓

-- 
⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts
⣾⠁⢰⠒⠀⣿⡁ productivity.  You can read it, too, you just need the
⢿⡄⠘⠷⠚⠋⠀ right music while doing so.  I recommend Skepticism
⠈⠳⣄ (funeral doom metal).--- End Message ---

Bug#867727: RFS: parlatype/1.5.2-1 [ITP]

2017-09-24 Thread Ross Gammon 
Control: tags -1 moreinfo

Hi Gabor,

Good work. We are nearly there!

The only thing I spotted, was the lack of a docbase file to help people
fire up the docs locally:
https://www.debian.org/doc/manuals/maint-guide/dother.en.html#doc-base

Would you like to maintain this within the Debian Multimedia Team? If so:
https://wiki.debian.org/DebianMultimedia/Join
and then follow the stuff in the Develop Packaging link there (to create
the git repository etc).
We can always do this before the next upload if you prefer. Just let me
know.

Some minor things we can work on for next time:
1. Lintian complains about there being no upstream changelog. As you are
upstream, maybe you can fix this? It is a nice service to our users to
see what changed in each version without going online. The Debian
changelog only contains changes in the packaging.
2. It would be nice to add some autopkgtests. For parlatype, that might
just be to run the binary command without a file to check that it
installs & doesn't crash. For the library & gir library you can compile
a simple app against the libraries to check they compile & run OK. If
you search on Debian Codesearch you will find examples.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#876667: RFS: pragha/1.3.3-1

2017-09-24 Thread Lukas Schwaighofer 
Hi Gabriel,

thanks for improving upon our suggestions.

On Sun, 24 Sep 2017 15:15:41 -0300
"Gabriel F. T. Gomes"  wrote:
> Lukas,
> In that same message [1], you suggested the use of a version control
> system, but I don't know where to make it public (I know that alioth
> is being discontinued, so I'm a bit lost with this).

I hope someone here will have a suggestion where your repository can
live.

> I think I solved all other problems you pointed out.

Looks like it.  I just took another look and saw a few more minor
things:

* The upstream tarball you uploaded to mentors is not exactly the same
  one as on github:

$ cmp pragha-1.3.3.tar.gz pragha_1.3.3.orig.tar.gz 
pragha-1.3.3.tar.gz pragha_1.3.3.orig.tar.gz differ: byte 5, line 1

  If you use git and git-buildpackage, make sure to use the
  "pristine-tar" feature.  When using this, a small delta file will be
  added to a special pristine-tar branch.  This allows to reconstruct
  the original tarball exactly as it was.

* In the debian/watch file you should replace "" with
  "pragha" (it also works as is, but then the downloaded tarball is
  called "-1.3.3.tar.gz" before the symlink is created).

* in debian/patches/fix-appstream-errors.patch:
  - referencing the ITP bug here does not make sense; you should only
use "Bug-Debian" if there is a bug in the Debian BTS that is
related to the patch (for example, if someone reported in the
Debian BTS that the appstream xml data is wrong)
  - Instead here you should record the URL of your pull request:

  Bug: https://github.com/pragha-music-player/pragha/pull/125


> Last but not least, I sent this message to debian-mentors (the right
> place to ask question, right?).  Please let me know if I got this
> wrong.

I think you got everything right.  The debian-mentors list will
automatically receive messages sent to the RFS bug, so there is no need
to explicitly CC it (but it doesn't hurt either).

I'm not a Debian Developer so I cannot sponsor your upload.  I hope you
find a sponsor soon!

Regards
Lukas

Re: Bug#876667: RFS: pragha/1.3.3-1

2017-09-24 Thread Gabriel F. T. Gomes 
Breno,

Lukas (CC) pointed out some problems [1] with the packaging of Pragha.
For instance, the fact that I did not open a RFS properly.  I should
have sent the RFS message to sub...@bugs.debian.org, not to #592985.

This is a proper RFS (I think I got it right this time).  :)

[1] https://lists.debian.org/debian-mentors/2017/09/msg00298.html


Lukas,

In that same message [1], you suggested the use of a version control
system, but I don't know where to make it public (I know that alioth is
being discontinued, so I'm a bit lost with this).

I think I solved all other problems you pointed out.


Last but not least, I sent this message to debian-mentors (the right
place to ask question, right?).  Please let me know if I got this wrong.

Bug#872652: Problems building package

2017-09-24 Thread Ghislain Vaillant 



On 24/09/17 11:19, Andreas Tille wrote:

On Sun, Sep 24, 2017 at 08:39:02AM +0100, Ghislain Vaillant wrote:


Are you sure your cowbuilder setup is ok? This is usually not a good sign:


BTW, the issue happens inside the clean target which is run *before*
chrooting into cowbuilder chroot.


I have pushed a new version which gets rid of this side effect. Could 
you try again with the latest tip of the master branch?


Ghis

Bug#876667: RFS: pragha/1.3.3-1

2017-09-24 Thread Gabriel F. T. Gomes 
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: pragha
   Version : 1.3.3-1
   Upstream Author : Matias De lellis 
 * URL : https://pragha-music-player.github.io/
 * License : GPL-3+
   Section : sound

It builds those binary packages:

  pragha - Lightweight Music Player

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/pragha/pragha_1.3.3-1.dsc


Regards,
Gabriel F. T. Gomes

Bug#876624: marked as done (RFS: qr-tools/1.4~bzr23-1 [QA])

2017-09-24 Thread Debian Bug Tracking System 
Your message dated Sun, 24 Sep 2017 22:03:20 +0800
with message-id <1620452.1v0gNil1JH@hosiet-tp>
and subject line Re: RFS: qr-tools/1.4~bzr23-1 [QA]
has caused the Debian Bug report #876624,
regarding RFS: qr-tools/1.4~bzr23-1 [QA]
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.)


-- 
876624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
在 2017年9月24日星期日 CST 上午11:17:39，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

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

2017-09-24 Thread Herbert Fortes 
Hi Boyuan Yang,

Uploaded.

Thanks for your work!



Regards,
Herbert

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

Bug#872736: RFS: dtkwidget/2.0.0-1 [ITP]

2017-09-24 Thread Yanhao Mo 
Hi czchen,

Very sorry to bother you again.
I just notised that I incorrectly set Maintainer's address to
pkg-dee...@list.alioth.debian.org, but the real address is
pkg-deepin-de...@lists.alioth.debian.org. I have corrected it and
re-uploaded it to mentors.debian.net. Please re-check and upload the
package.

Thanks,
-- YanhaoMo


signature.asc
Description: PGP signature

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

2017-09-24 Thread 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#872652: Problems building package

2017-09-24 Thread Andreas Tille 
On Sun, Sep 24, 2017 at 08:39:02AM +0100, Ghislain Vaillant wrote:
> 
> Are you sure your cowbuilder setup is ok? This is usually not a good sign:

BTW, the issue happens inside the clean target which is run *before*
chrooting into cowbuilder chroot.

Kind regards

 Andreas. 

-- 
http://fam-tille.de

Bug#872652: Problems building package

2017-09-24 Thread Andreas Tille 
On Sun, Sep 24, 2017 at 08:39:02AM +0100, Ghislain Vaillant wrote:
> 
> > $ gbp-build
> > gbp:info: Tarballs 'python-pymeasure_0.4.6.orig.tar.gz' not found at 
> > '../tarballs/'
> > gbp:info: Exporting 'WC' to 
> > '/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
> > gbp:info: Moving 
> > '/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
> >  to 
> > '/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
> > I: using cowbuilder as pbuilder
> > dpkg-checkbuilddeps: error: Unmet build dependencies: python3-all 
> > python3-pandas python3-pyqtgraph (>= 0.9.10) python3-pytest-runner 
> > python3-pyvisa python3-serial (>= 2.7) python3-sphinx 
> > python3-sphinx-rtd-theme
> > W: Unmet build-dependency in source
> > dpkg-source: info: using options from 
> > python-pymeasure-0.4.6/debian/source/options: 
> > --extend-diff-ignore=^[^/]+\.egg-info/
> > dpkg-source: info: applying No-privacy-breach.patch
> > dh clean --with python3,sphinxdoc --buildsystem=pybuild
> > debian/rules override_dh_auto_clean
> > make[1]: Entering directory 
> > '/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
> > dh_auto_clean
> > I: pybuild base:184: python3.6 setup.py clean
> > 
> > Note: Bypassing https://pypi.python.org/simple/pytest-runner/ (disallowed 
> > host; see http://bit.ly/1dg9ijs for details).
> > 
> > Couldn't find index page for 'pytest-runner' (maybe misspelled?)
> > 
> > Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
> > http://bit.ly/1dg9ijs for details).
> > 
> > No local packages or working download links found for pytest-runner
> > Traceback (most recent call last):
> >File "setup.py", line 70, in 
> >  keywords="measure instrument experiment control automate graph plot"
> >File "/usr/lib/python3.6/distutils/core.py", line 108, in setup
> >  _setup_distribution = dist = klass(attrs)
> >File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 325, in 
> > __init__
> >  self.fetch_build_eggs(attrs['setup_requires'])
> >File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 446, in 
> > fetch_build_eggs
> >  replace_conflicting=True,
> >File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
> > 855, in resolve
> >  dist = best[req.key] = env.best_match(req, ws, installer)
> >File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
> > 1127, in best_match
> >  return self.obtain(req, installer)
> >File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
> > 1139, in obtain
> >  return installer(requirement)
> >File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 518, in 
> > fetch_build_egg
> >  return cmd.easy_install(req)
> >File 
> > "/usr/lib/python3/dist-packages/setuptools/command/easy_install.py", line 
> > 691, in easy_install
> >  raise DistutilsError(msg)
> > distutils.errors.DistutilsError: Could not find suitable distribution for 
> > Requirement.parse('pytest-runner')
> > E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
> > python3.6 setup.py clean
> > dh_auto_clean: pybuild --clean --test-pytest -i python{version} -p "3.6 
> > 3.5" returned exit code 13
> > debian/rules:12: recipe for target 'override_dh_auto_clean' failed
> > make[1]: *** [override_dh_auto_clean] Error 25
> > make[1]: Leaving directory 
> > '/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
> > debian/rules:9: recipe for target 'clean' failed
> > make: *** [clean] Error 2
> > gbp:error: '~/bin/git-pbuilder ''' failed: it exited with 2
> > 
> > 
> > :-(
> 
> Not sure what to tell you. Both debomatic and my local sbuild do not report
> such issues.
> 
> Are you sure your cowbuilder setup is ok? This is usually not a good sign:
> 
> dpkg-checkbuilddeps: error: Unmet build dependencies [...]
> 
> And would explain why you are getting:
> 
> Could not find suitable distribution for Requirement.parse('pytest-runner')

I just did a fresh

  sudo cowbuilder --create

before - no change. :-(

Kind regards

  Andreas. 

-- 
http://fam-tille.de

Bug#872652: Problems building package

2017-09-24 Thread Ghislain Vaillant 



On 23/09/17 18:15, Andreas Tille wrote:

On Sat, Sep 23, 2017 at 10:39:35AM +0100, Ghislain Vaillant wrote:

Frederic gave a hint to bug #873921.


Now that the situation with pandas / statsmodels is resolved, the package
builds fine [1].

[1] 
http://debomatic-amd64.debian.net/distribution#unstable/python-pymeasure/0.4.6-1/buildlog

Could you push it to the archive please?


$ gbp-build
gbp:info: Tarballs 'python-pymeasure_0.4.6.orig.tar.gz' not found at 
'../tarballs/'
gbp:info: Exporting 'WC' to 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
gbp:info: Moving 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-tmp'
 to 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
I: using cowbuilder as pbuilder
dpkg-checkbuilddeps: error: Unmet build dependencies: python3-all python3-pandas 
python3-pyqtgraph (>= 0.9.10) python3-pytest-runner python3-pyvisa python3-serial 
(>= 2.7) python3-sphinx python3-sphinx-rtd-theme
W: Unmet build-dependency in source
dpkg-source: info: using options from 
python-pymeasure-0.4.6/debian/source/options: 
--extend-diff-ignore=^[^/]+\.egg-info/
dpkg-source: info: applying No-privacy-breach.patch
dh clean --with python3,sphinxdoc --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
dh_auto_clean
I: pybuild base:184: python3.6 setup.py clean

Note: Bypassing https://pypi.python.org/simple/pytest-runner/ (disallowed host; 
see http://bit.ly/1dg9ijs for details).

Couldn't find index page for 'pytest-runner' (maybe misspelled?)

Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).

No local packages or working download links found for pytest-runner
Traceback (most recent call last):
   File "setup.py", line 70, in 
 keywords="measure instrument experiment control automate graph plot"
   File "/usr/lib/python3.6/distutils/core.py", line 108, in setup
 _setup_distribution = dist = klass(attrs)
   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 325, in 
__init__
 self.fetch_build_eggs(attrs['setup_requires'])
   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 446, in 
fetch_build_eggs
 replace_conflicting=True,
   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 855, 
in resolve
 dist = best[req.key] = env.best_match(req, ws, installer)
   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1127, 
in best_match
 return self.obtain(req, installer)
   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1139, 
in obtain
 return installer(requirement)
   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 518, in 
fetch_build_egg
 return cmd.easy_install(req)
   File "/usr/lib/python3/dist-packages/setuptools/command/easy_install.py", 
line 691, in easy_install
 raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution for 
Requirement.parse('pytest-runner')
E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean
dh_auto_clean: pybuild --clean --test-pytest -i python{version} -p "3.6 3.5" 
returned exit code 13
debian/rules:12: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 25
make[1]: Leaving directory 
'/home/andreas/debian-maintain/alioth/debian-science/git/packages/build-area/python-pymeasure-0.4.6'
debian/rules:9: recipe for target 'clean' failed
make: *** [clean] Error 2
gbp:error: '~/bin/git-pbuilder ''' failed: it exited with 2


:-(


Not sure what to tell you. Both debomatic and my local sbuild do not 
report such issues.


Are you sure your cowbuilder setup is ok? This is usually not a good sign:

dpkg-checkbuilddeps: error: Unmet build dependencies [...]

And would explain why you are getting:

Could not find suitable distribution for Requirement.parse('pytest-runner')

Ghis