Re: New package - i3lock-color

2020-05-12 Thread Andrey Rahmatullin
On Tue, May 12, 2020 at 06:17:34PM -0400, Raymond Li wrote:
> Hi,
> 
> I maintain a popular lockscreen called i3lock-color. I've filed an ITP for
> it and have a .deb package ready. I need a .changes file to use dput to
> upload it to the mentors thinggy, but I have no idea how to get that file
> or really what to do at all. Would anyone mind giving me some help? Thanks.
How did you create that .deb?

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Bug#960477: RFS: iptux/0.7.6-2 -- Intranet communication tool for Linux

2020-05-12 Thread 铜豌豆 Linux
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name : iptux
Version : 0.7.6-2
Upstream Author : LI Daobing 
* URL : https://github.com/iptux-src/iptux
* License : GPL-2+
* Vcs : https://salsa.debian.org/chinese-team/iptux
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.7.6-2.dsc

Changes since the last upload:

[ Debian Janitor ]
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
.
[ 肖盛文 ]
* d/rules:
- delete export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
- delete override_dh_missing
* d/control:
- Bump debhelper-compat (= 13)
- Bump Standards-Version: 4.5.0
- add Rules-Requires-Root: no
- add new Uploaders

Regards,

-- 
肖盛文 Faris Xiao
邮箱:atzli...@yeah.net
微信:atzlinux
QQ:909868357
铜豌豆 Linux 
基于 Debian 的 Linux 中文桌面操作系统:https://www.atzlinux.com




signature.asc
Description: OpenPGP digital signature


Bug#960475: RFS: iptux/0.7.6-2 -- Intranet communication tool for Linux

2020-05-12 Thread atzlinux 肖盛文
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name : iptux
Version : 0.7.6-2
Upstream Author : LI Daobing 
* URL : https://github.com/iptux-src/iptux
* License : GPL-2+
* Vcs : https://salsa.debian.org/chinese-team/iptux
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.7.6-2.dsc

Changes since the last upload:

[ Debian Janitor ]
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
.
[ 肖盛文 ]
* d/rules:
- delete export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
- delete override_dh_missing
* d/control:
- Bump debhelper-compat (= 13)
- Bump Standards-Version: 4.5.0
- add Rules-Requires-Root: no
- add new Uploaders

Regards,

-- 
肖盛文 Faris Xiao
微信:atzlinux
QQ:909868357
铜豌豆 Linux 
基于 Debian 的 Linux 中文桌面操作系统:https://www.atzlinux.com




signature.asc
Description: OpenPGP digital signature


Bug#960462: RFS: libevpath/4.6.0-1 [ITP] -- Event transport middleware

2020-05-12 Thread Kyle Edwards
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: debian-scie...@lists.debian.org

Dear mentors,

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

 * Package name: libevpath
   Version : 4.6.0-1
   Upstream Author : Georgia Tech Research Corporation
 * URL : https://github.com/GTkorvo/evpath
 * License : BSD-3-clause
 * Vcs : https://gitlab.kitware.com/debian/libevpath
   Section : libs

It builds those binary packages:

  libevpath-dev - Event transport middleware - development files
  libevpath - Event transport middleware
  libevpath-enet - Event transport middleware - ENet transport module
  libevpath-libfabric - Event transport middleware - libfabric
transport module
  libevpath-ibverbs - Event transport middleware - ibverbs transport
module

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

  https://gitlab.kitware.com/debian/libevpath

Regards,

--
  Kyle Edwards



Bug#960397: RFS: oxygencursors/0.0.2012-06-kde4.8-3 [QA] [RC] -- Oxygen mouse cursor theme

2020-05-12 Thread Christian Göttsche
Am Di., 12. Mai 2020 um 14:46 Uhr schrieb Adam Borowski :
> Alas, it fails to build:
>
> libpng error: Read Error
> /usr/bin/xcursorgen: PNG error while reading 180/pencil.png
> Background RRGGBBAA: ff00
> Area 0:0:32:32 exported to 60 x 60 pixels (180 dpi)
> Background RRGGBBAA: ff00
> Area 0:0:24:24 exported to 45 x 45 pixels (180 dpi)
> make[3]: *** [theme-yellow/CMakeFiles/theme-yellow.dir/build.make:203: 
> oxy-yellow/cursors/pencil] Error 1
> make[3]: *** Deleting file 'oxy-yellow/cursors/pencil'
> make[3]: *** Waiting for unfinished jobs
>
> I haven't investigated the fail, but as "Read Error" could be platform
> related, I tried on three different machines (2×amd64, 1×arm64) -- same.
>

Thanks for catching this.
It seems with bare cmake `add_custom_command`'s, they might get called
multiple times to generate the specified output. [1]
(So a subsequent generation might conflict with the concurrent usage
of the file.)
So I added a patch introducing custom targets.

> Also: why would you move the section?  This is a properly made theme that
> works with any WM/DE, not just KDE.  I don't know KDE team's policies,
> though, thus this is not a hard request -- feel free to ignore.

My bad, I though section x11 being for xserver related things (but
these cursors also work on wayland), but even weston is in the x11
category; reverted.

[1]: 
https://samthursfield.wordpress.com/2015/11/21/cmake-dependencies-between-targets-and-files-and-custom-commands/⠀⠀



New package - i3lock-color

2020-05-12 Thread Raymond Li
Hi,

I maintain a popular lockscreen called i3lock-color. I've filed an ITP for
it and have a .deb package ready. I need a .changes file to use dput to
upload it to the mentors thinggy, but I have no idea how to get that file
or really what to do at all. Would anyone mind giving me some help? Thanks.

Stay safe,
Raymond Li

Sincerely,
Raymond Li


Bug#960162: RFS: mgba/0.8.1+dfsg-1 -- Game Boy Advance emulator

2020-05-12 Thread Boyuan Yang
X-Debbugs-CC: r...@nardis.ca

Hi Ryan,

On Tue, 12 May 2020 12:30:16 -0700 Ryan Tandy  wrote:
> On Tue, May 12, 2020 at 09:22:23PM +0200, Tobias Frost wrote:
> >Hijacks are bad…
> >However there is the package salvaging process, please check if it is more
suitable:
> >
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
> 
> Thanks for the pointer. I think "team upload" is a better description of 
> what I'm attempting, but it didn't seem quite accurate as I'm not (yet) 
> a member of the relevant team.
> 
> I will check with the games team to see what they prefer, and will 
> follow the salvaging process if that's best.

Thanks for your interest in the package. I'd suggest to start the Salvaging
process if

 * you are really interested in maintaining it
 * the package is suitable for Salvaging (see definitions in Developers
Reference)
 * no one has objection on salvaging in the Games Team

(Even though I'm in the Games Team, I'm speaking on behalf of myself this
time. This email copy is also sent to Sergio.)

-- 
Thanks,
Boyuan


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


Bug#960162: RFS: mgba/0.8.1+dfsg-1 -- Game Boy Advance emulator

2020-05-12 Thread Ryan Tandy

On Tue, May 12, 2020 at 09:22:23PM +0200, Tobias Frost wrote:

Hijacks are bad…
However there is the package salvaging process, please check if it is more 
suitable:
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging


Thanks for the pointer. I think "team upload" is a better description of 
what I'm attempting, but it didn't seem quite accurate as I'm not (yet) 
a member of the relevant team.


I will check with the games team to see what they prefer, and will 
follow the salvaging process if that's best.


thanks,
Ryan



Bug#960162: RFS: mgba/0.8.1+dfsg-1 -- Game Boy Advance emulator

2020-05-12 Thread Tobias Frost
Hi Ryan,

On Sat, May 09, 2020 at 07:41:27PM -0700, Ryan Tandy wrote:
> Package: sponsorship-requests
> Severity: normal
> 
> This is a package hijack

Hijacks are bad…
However there is the package salvaging process, please check if it is more 
suitable:
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging

-- 
tobi



Bug#959057: RFS: dh-cmake/0.4 [ITP] -- Debhelper programs for CMake projects

2020-05-12 Thread Kyle Edwards
On Tue, 2020-05-12 at 14:35 +0300, Peter Pentchev wrote:
> Just a suggestion (somebody else already offered to sponsor the
> package):

Strange... I see the email in the debian-devel archives, but I never
received it. I wonder if it went to my spam folder. Thanks for the
heads up.

> could you take a look at Rules-Requires-Root in Policy 4.9.2
> and see if you couldn't set it in the Source control section?

Updated d/control with `Rules-Requires-Root: no`.

> Also, recent versions of debhelper introduced automatic handling of
> "--with something" if the dh-* package "Provides: dh-sequence-
> something"
> so that any packages that use it may build-depend (or B-D-I) on
> dh-sequence-something and debhelper will automatically assume "--with
> something", further simplifying the rules file.

Updated d/control to provide `dh-sequence-*`, and updated docs and
examples to suggest the modern approach.

Thanks!

Kyle



Bug#956731: RFS: check/0.14.0-0.1 [NMU] -- unit test framework for C

2020-05-12 Thread Christian Göttsche
Hi Tobias,

> it seems that check would be a candidate to be ITSed?

Do you mean ITA (Intent To Adopt)?



Bug#960370: RFS: jag/0.3.7-1 -- arcade and puzzle 2D game

2020-05-12 Thread Carlos Donizete Froes
Hi Peter,

> Hmm, I see that you have not uploaded these changes to the Salsa
> repository; it seems to me that you are in the habit of making changes
> somewhere else, then importing them in a single commit once the package
> has been uploaded. I think it might be a bit more useful for
> collaboration to have your work in the Salsa repository, too.
> Not a blocker, just something that caught my eye.

Exactly what I do, after uploading the package to mentors.d.n, I am waiting for
the sponsor to analyze the package and, after everything is right, send it to
the salsa repository.

I don't know if I have permission at this point to make my changes to my package
directly through the salsa repository.

I would like to find a link to do the correct procedure for this.

> The test definition in the debian/tests/control file has a "Depends:"
> line listing both "@" and "jag-data". It is my understanding that "@"
> stands for "all the binary packages built in this run", so "jag-data" is
> not needed there.

I understand, I will remove the "jag-data" in "Depends:". I am still adapting to
add autopkgtest to my packages.

> The test itself seems a bit weird to me, too. It looks like jag is
> a graphical application; I have not tried running the test, but I wonder
> if it might be better to explicitly specify something like a fake X
> server; right now I can't quite recall the name, but I'm pretty sure
> that I've seen some kind of "no real video output, but all the Xlib
> calls and events" server used for testing; it might have been Xvfb.

Sorry, I didn't get it right. Could you help me so I can specify better? :/

> On a related note, I see that in version 0.3.6-1 you removed the "same
> as source:Version" constraint in the jag dependency on jag-data; would
> it not be nice to at least have a ">= ${source:Version}" one so that if
> somebody runs "apt install jag", it pulls in a usable version of
> jag-data automatically?

In version 0.3.6-1, I removed ">= ${source:Version}" because one of the sponsors
told me that I wouldn't need this because "jag-data" is in the same package as
"jag". When I run "apt install jag", it automatically extracts "jag-data"
normally. But I can add again without any problems. :)

> Maybe for a future upload, but since you're using version 4 of the watch
> file format, have you considered using the @PACKAGE@, @ANY_VERSION@, etc
> variables that uscan provides now? Of course, it's up to the maintainer
> (you) whether that's more readable, but personally to me, it is.

What I learned at the moment, I use more to download via uscan from my GitLab
repository, whenever there is a new version of the software, and I type: "uscan
--force-download" and then "uupdate".

If you have another, more recent way, let me know where to find it so I can
improve myself.

Thanks and see you!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀  2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780


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


Bug#960435: RFS: lebiniou/3.42.1-1 -- displays images that evolve with sound

2020-05-12 Thread Olivier Girondel


Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: lebiniou
   Version : 3.42.1-1
   Upstream Author : Olivier Girondel 
 * URL : https://biniou.net
 * License : GPL-2+
   Section : graphics

It builds this binary package:

  lebiniou - displays images that evolve with sound

The package appears to be lintian-clean.

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/l/lebiniou/lebiniou_3.42.1-1.dsc

Changes since the last upload:

  * New upstream release 3.42.1.

Regards,
  Olivier Girondel



Bug#960397: RFS: oxygencursors/0.0.2012-06-kde4.8-3 [QA] [RC] -- Oxygen mouse cursor theme

2020-05-12 Thread Christian Göttsche
Package: sponsorship-requests
Severity: important
X-Debbugs-CC: deb...@pusling.com, lisan...@debian.org, ans...@debian.org

Dear mentors,

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

 * Package name: oxygencursors
   Version : 0.0.2012-06-kde4.8-3
   Upstream Author : Riccardo Iaconelli 
 * URL : https://techbase.kde.org/Projects/Oxygen
 * License : GPL-3+
 * Vcs : None
   Section : kde

It builds those binary packages:

  oxygencursors - Oxygen mouse cursor theme

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/o/oxygencursors/oxygencursors_0.0.2012-06-kde4.8-3.dsc

Changes since the last upload:

   * QA upload.
   * overhaul Debian packaging
 - switch to simple dh sequence
 - move install logic from custom scripts into cmake
 - use debhelper compat level 13
 - bump to standards version 4.5.0
 - move from section x11 to kde
 - update command line arguments for inkscape v1.0 (Closes: #959554)
   * d/patches: cherry-pick upstream commit correcting symlinks
(Closes: #848144)
   * d/copyright: convert to machine-readable format (DEP-5)

Regards,
  Christian Göttsche



Bug#959057: RFS: dh-cmake/0.4 [ITP] -- Debhelper programs for CMake projects

2020-05-12 Thread Peter Pentchev
On Tue, Apr 28, 2020 at 08:54:33PM +, Kyle Edwards wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "dh-cmake":
> 
>  * Package name: dh-cmake
>Version : 0.4
>Upstream Author : Kyle Edwards 
>  * URL : https://gitlab.kitware.com/debian/dh-cmake
>  * License : BSD-3
>  * Vcs : https://gitlab.kitware.com/debian/dh-cmake.git
>Section : devel
> 
> It builds those binary packages:
> 
>   dh-cmake - Debhelper programs for CMake projects
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://gitlab.kitware.com/debian/dh-cmake

Hi,

Just a suggestion (somebody else already offered to sponsor the
package): could you take a look at Rules-Requires-Root in Policy 4.9.2
and see if you couldn't set it in the Source control section?

Also, recent versions of debhelper introduced automatic handling of
"--with something" if the dh-* package "Provides: dh-sequence-something"
so that any packages that use it may build-depend (or B-D-I) on
dh-sequence-something and debhelper will automatically assume "--with
something", further simplifying the rules file.

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature


Bug#959897: RFS: awf-gtk2/2.0.0-3 [ITP] -- A widget factory is a theme preview application for GTK

2020-05-12 Thread Fabrice Creuzot

Hi! Thank you.

The version is -3 because I uploaded some test versions on 
mentors.debian.net. I tried to upload 2.0.0-1 many times, but it was 
refused, so I changed version number.


I'm confused about the lintian override 
(description-synopsis-starts-with-article) and "A Widget Factory". I use 
the lintian ovevride for initial "A"... Does I change the name to "A 
Widget Factory" anyway?


You say "Also: despite GTK2 being deprecated, having the gtk2 package 
would be great.", I agree x10. I have updated this tool to port a gtk2 
theme to gtk3.



Le 11/05/2020 à 22:54, Adam Borowski a écrit :

On Wed, May 06, 2020 at 07:51:53PM +0200, Fabrice Creuzot wrote:

  * Package name: awf-gtk2
Version : 2.0.0-3



Changes since the last upload:

* Initial debian package release (Closes: #959434)


Hi!
The package looks almost good to go:

* Debian revision: how come it's -3 on an initial upload?  Especially with
   nothing in the changelog?

   We don't bump a version just because you've tested it at home -- it often
   takes many, many test builds to get things right.  An exception is if a
   version of the package has been released to an audience, be they users of
   some Debian-based distribution, your team at works, etc -- having two
   different versions with the same number would give them a hardship.

* the real name (according to a Lintian override) is "A Widget Factory",
   yet you capitalize only the article.  For an English speaking person,
   that's for sure some common thing.  Could you please put it into title
   case (Ie, Starting Every Word with a Cap Letter)?

Both of these are common to either variant (gtk2 and gtk3).

Also: despite GTK2 being deprecated, having the gtk2 package would be great.
It already proven useful in finding out regressions in a theme I maintain
-- a bunch of functionality is wrong in gtk3, having both side-to-side
made that immediately visible.


Meow!





Bug#960370: RFS: jag/0.3.7-1 -- arcade and puzzle 2D game

2020-05-12 Thread Peter Pentchev
On Tue, May 12, 2020 at 02:13:16AM -0300, Carlos Donizete Froes wrote:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "jag"
> 
>  * Package name: jag
>Version : 0.3.7-1
>Upstream Author : XlabSoft & Industrial Infosystems
>  * URL : https://gitlab.com/coringao/jag/wikis
>  * License : GPL-3+
>  * Vcs : https://salsa.debian.org/games-team/jag
>Section : games

Hmm, I see that you have not uploaded these changes to the Salsa
repository; it seems to me that you are in the habit of making changes
somewhere else, then importing them in a single commit once the package
has been uploaded. I think it might be a bit more useful for
collaboration to have your work in the Salsa repository, too.
Not a blocker, just something that caught my eye.

> It builds those binary packages:
> 
>   jag - arcade and puzzle 2D game
>   jag-data - arcade and puzzle 2D game (data file)
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://mentors.debian.net/package/jag
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x https://mentors.debian.net/debian/pool/main/j/jag/jag_0.3.7-1.dsc
> 
> Changes since the last upload:
> 
>* New upstream release. FTCBFS bug fixed. (Closes: #958672)
>  - Fixed integrated qmake support for pkg-config. (Thanks Helmut Grohne)
>* Added autopkgtest.

The test definition in the debian/tests/control file has a "Depends:"
line listing both "@" and "jag-data". It is my understanding that "@"
stands for "all the binary packages built in this run", so "jag-data" is
not needed there.

The test itself seems a bit weird to me, too. It looks like jag is
a graphical application; I have not tried running the test, but I wonder
if it might be better to explicitly specify something like a fake X
server; right now I can't quite recall the name, but I'm pretty sure
that I've seen some kind of "no real video output, but all the Xlib
calls and events" server used for testing; it might have been Xvfb.

On a related note, I see that in version 0.3.6-1 you removed the "same
as source:Version" constraint in the jag dependency on jag-data; would
it not be nice to at least have a ">= ${source:Version}" one so that if
somebody runs "apt install jag", it pulls in a usable version of
jag-data automatically?

>* Added debian/docs.
>* debian/rules:
>  - export DEB_LDFLAGS_MAINT_APPEND removed.
>  - export QT_SELECT removed.
>* debian/watch:
>  - Fixed the requested URL in the uscan information.

Maybe for a future upload, but since you're using version 4 of the watch
file format, have you considered using the @PACKAGE@, @ANY_VERSION@, etc
variables that uscan provides now? Of course, it's up to the maintainer
(you) whether that's more readable, but personally to me, it is.

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature


Bug#956414: +1 we need more away from systemd

2020-05-12 Thread PICCORO McKAY Lenz
+1 good work.. please core DD this pacakge need a review! in devuan
works as expected

-- 
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com