Bug#940231: RFS: lablie/0.6.1-2 -- CLI tool for printable labels generation from SVG templates

[Miroslav Kravec]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: lablie
   Version : 0.6.1-2
 * URL : https://gitlab.com/kravemir/lablie
 * License : Apache-2.0
 * Vcs : https://salsa.debian.org/debian/lablie
   Section : utils

It builds those binary packages:

  lablie - CLI tool for printable labels generation from SVG templates

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/l/lablie/lablie_0.6.1-2.dsc

Changes since the last upload:

   * debian/patches: make build reproducible with SOURCE_DATE_EPOCH

Kind regards,
Miroslav Kravec

Bug#939509: RFS: lablie/0.6.1-1 -- CLI tool for printable labels generation from SVG templates

[Miroslav Kravec]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: lablie
   Version : 0.6.1-1
 * URL : https://gitlab.com/kravemir/lablie
 * License : Apache-2.0
 * Vcs : https://salsa.debian.org/debian/lablie
   Section : utils

It builds those binary packages:

  lablie - CLI tool for printable labels generation from SVG templates

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/l/lablie/lablie_0.6.1-1.dsc

Changes since the last upload:

   * New upstream release
   * debian/compat: bump to 12
   * debian/control: update standards to 4.4.0, require debhelper >= 12
   * debian/lablie.poms: Adjust versions in JAR filenames in debian/lablie.poms
   * debian/patches: adjust debian patches for new release

Additionally, changes are pushed to:

  * https://salsa.debian.org/debian/lablie (except package release commit)
  * https://salsa.debian.org/kravemir-guest/lablie (including release commit)

Kind regards,
Miroslav Kravec

Debian Salsa packaging guidelines and conventions

[Miroslav Kravec]

Dear mentors,

I'm considering to move package sources to Debian salsa. And, I'm
quite unsure, what's a correct approach to do it. Especially, what are
conventions and guidelines for packaging.

Lets assume, that packaged software doesn't require any special
adjustments, and packaged software's upstream is stored in a publicly
available git repository. What's standard gbp.conf, and other
settings?

I very much like to stick to conventions, for easier cooperation, when
cooperation is needed. So, I'm looking for the  most recognized way to
package such projects hosted on git within Debian developers.

I did find https://wiki.debian.org/Salsa/Doc and
https://wiki.debian.org/Salsa/FAQ.

Kind regards,
Miroslav Kravec

Bug#935832: RFS: ddccontrol-db/20190826-1 -- monitor database for ddccontrol

[Miroslav Kravec]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "ddccontrol-db"

 * Package name: ddccontrol-db
   Version : 20190826-1
 * URL : https://github.com/ddccontrol/ddccontrol-db
 * License : GPL-2+
 * Vcs : https://github.com/ddccontrol/debian-ddccontrol-db
   Section : utils

It builds those binary packages:

  ddccontrol-db - monitor database for ddccontrol

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

  https://mentors.debian.net/package/ddccontrol-db

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

  dget -x 
https://mentors.debian.net/debian/pool/main/d/ddccontrol-db/ddccontrol-db_20190826-1.dsc

Changes since the last upload:

   * New upstream release
   * debian/control: update standards to 4.4.0, set Multi-Arch to foreign
   * debian/copyright: convert to machine-readable copyright file

Kind regards,
Miroslav Kravec

Re: Request for advice

[Miroslav Kravec]

Hello Sharon,

ITP stands for "Intention to package". If you really intent to finish
packaging, then you can leave it open. Maybe, only the specific
package is way to complex, and requires special way of packaging.
Closing the bug you can double the effort, as multiple people could
end up working on same package in parallel, from scratch.

Also, you can collaborate with others:

* reply to the ITP bug, that help is welcome, and indicate slow progress,
* publish yours packaging effort in salsa git repository,
* ask specific questions here on mentors.

> But, I was too optimistic of how much time I have to learn the
> packaging process and perform it.

For quick start, you can copy debian folder from different package
using same programming language, build system, similar libraries,..
Then adjust it to yours package, and run lintian over the whole thing.

Kind regards,
Miroslav Kravec

On Fri, May 10, 2019 at 1:51 PM Sharon Dvir  wrote:
>
> Dear mentors,
> I've opened an ITP bug for something I intend to package, so far so
> good.
> But, I was too optimistic of how much time I have to learn the
> packaging process and perform it.
>
> What is the considerate path forward?
> Should I close the bug or leave it until I'll have the time to fix all
> remaining issues and upload?
>
> Can I mark it 'slow-progress' somehow?
> Do I send beer to someone and apologize?
>
> Thanks.
>

Re: Presentation

[Miroslav Kravec]

Hi,

I took a quick look at the presentation. Looks to have nice potential
in it. Few points below:

> Debian GNU/Linux is a free (as in freedom) operating system (OS) for your 
> computer. An operating system is the set of basic programs and utilities that 
> make your computer run. [1]

Less (text) is more (focused presentation). I would remove part
describing what OS is, and based on audience, would explain the term
only orally (plus hyperlink in PDF).

I would also try to restructure "A brief definition" to get rid of
repetition of "Debian" on each bullet point.

> Internet Relay Chat

In 2019 the most of the people know, what chat is (or quickly
explained it orally). I would merge these three points to one "A real
time Text based Communication system", and focus on IRC pros and
differences.

> :-

For me, this looks a bit ugly.

> On a basic level it is:-

I would remove this sentence at all, and reword titles:

* What is Internet Relay Chat,
* What is ID with nickserv,

Also, I would move registration after definition, and renamed title to:

* Registration of ID with nickserv

Generally, I would first focus on the message to be told, and to whom.
Presentations are highly specific. And, people tend to get easily
bored, when there's too much details they already know, or are not
relevant to message. Also, people get bored, if they lose track on
some point, because of missing information. In either case, they'll
disconnect themselves, and will start day dreaming, or anti-social
ones will start disturbing others/speaker.

Kind regards,
Miroslav Kravec

On Thu, May 9, 2019 at 5:24 PM Paul Sutton  wrote:
>
> Hi
>
> Having worked on a presentation to promote Debian generally, I decided
> to work on one that could focus on IRC and how to get started.
>
> https://salsa.debian.org/zleap-guest/oftc-presentation
>
> I am not sure if this is useful, but I would anticipate this can form
> part of a series on getting started with Debian contributing.  It is
> early days on this at the moment but I am getting there slowly.
>
> I am not going to touch on IRC clients other than the web interface,
> once people are connected to IRC they are able to ask for further help
> and information on clients.
>
> Hope this helps
>
>
> Paul Sutton
>
>
> --
> Paul Sutton
> http://www.zleap.net
> https://www.linkedin.com/in/zleap/
> gnupg : 7D6D B682 F351 8D08 1893  1E16 F086 5537 D066 302D
>

Bug#927743: RFS: lablie/0.6.0-1 [ITP]

[Miroslav Kravec]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: lablie
  Version : 0.6.0-1
  Upstream Author : Miroslav Kravec 
* URL : https://gitlab.com/kravemir/lablie
https://kravemir.gitlab.io/lablie/
  Section : utils

It builds those binary packages:

  lablie - CLI tool for printable labels generation from SVG templates

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/l/lablie/lablie_0.6.0-1.dsc

This is the first upload:

  * Initial release (Closes: #927737)

This is finished packaging work of previous RFS:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907809#12, which had
violated policies about convenience copies of code. Also, the package
and whole project was renamed. Previous name, svg-labels, was pretty
much generic, and the name had been already used in an another
existing project.

Kind regards,
Miroslav Kravec

Re: Doubt: update-alternative during debian/rules? (GTK2 vs GTK3)

[Miroslav Kravec]

Dňa ut, 13. nov 2018 22:57 Santiago Vila  napísal(a):

> On Mon, Nov 12, 2018 at 01:26:11PM +0100, JOSE LUIS BLANCO CLARACO wrote:
>
> > And my question is: is it "acceptable" to run `update-alternatives`
> > during debian/rules? [...]
>
> I don't think so. Would that work at all if you are using fakeroot?
>

Certainly not acceptable. Package build should not touch anything outside
of package. Ie. no side effects.

>
Anyway, what would be the goal? If specific binary is needed, then setup
env vars correctly.

>

Bug#912010: RFS: lightvalue/0.8.1-1 [ITP]

[Miroslav Kravec]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: lightvalue
   Version : 0.8.1-1
   Upstream Author : Miroslav Kravec 
 * URL : https://gitlab.com/kravemir/lightvalue
 * License : Apache-2.0
   Section : java

It builds those binary packages:

liblightvalue-generator-java - Generator of lightweight Java
value/model classes
liblightvalue-gradle-plugin-java - Gradle plugin for LightValue generator

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

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

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

dget -x 
https://mentors.debian.net/debian/pool/main/l/lightvalue/lightvalue_0.8.1-1.dsc

More information about lightvalue can be obtained from
https://gitlab.com/kravemir/lightvalue.

Changes since the last upload:

  * Initial release. (Closes: #911472)

Kind regards,
Miroslav Kravec

Bug#910327: Fwd: Bug#910327: RFS: javapoet/1.11.1-1 [ITP]

[Miroslav Kravec]

Hello Tony,

can you please take a look at it again? It can be downloaded from
mentors, using same command (URL):

dget -x 
https://mentors.debian.net/debian/pool/main/j/javapoet/javapoet_1.11.1-1.dsc

I have explicitly listed files copyrighted by Google in
debian/copyright. And, I have left Square, Inc. as default for all (*)
files, as it's library's primary author.

Kind regards,
Miroslav Kravec

Bug#910327: Fwd: Bug#910327: RFS: javapoet/1.11.1-1 [ITP]

[Miroslav Kravec]

On Fri, Oct 5, 2018 at 5:43 AM tony mancill  wrote:
>
> Hello Miroslav,
>
> Thank you for packaging javapoet.  I was looking at doing this as a
> dependency for some of the OpenHFT libraries.
>
> One minor change I think we need to make to debian/copyright is to
> explicitly list the files that have Google and not Square as the
> copyright holder, but otherwise the package looks good.
>
> Just as you suggest below, I will push the packaging into a repo on
> salsa.debian.org (so the same as with picocli) and bring the package
> under Debian Java Maintainers with you as an Uploader.
>
> Cheers,
> tony
>
> On Thu, Oct 04, 2018 at 10:25:04PM +0200, Miroslav Kravec wrote:
> > Dear package maintainers,
> >
> > I'm looking for a sponsor for javapoet (see details of forwarded message).
> >
> > The package can be moved under Debian Java Maintainers, as was done for:
> >
> > * https://tracker.debian.org/pkg/picocli ,
> > * https://tracker.debian.org/pkg/gradle-apt-plugin .
> >
> > Or, you can leave me as maintainer, if you wouldn't like to move it
> > under Debian Java Maintainers.
> >
> > Kind regards,
> > Miroslav Kravec
> >
> > -- Forwarded message -
> > From: Miroslav Kravec 
> > Date: Thu, Oct 4, 2018 at 10:09 PM
> > Subject: Bug#910327: RFS: javapoet/1.11.1-1 [ITP]

Hello Tony,

thank you for review of packaging work. I'm glad you're interested in
getting this package to Debian.

I'll fix debian/copyright, and upload new version to mentors.

Kind regards,
Miroslav Kravec

Bug#910327: RFS: javapoet/1.11.1-1 [ITP]

[Miroslav Kravec]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: javapoet
   Version : 1.11.1-1
   Upstream Author : Square, Inc.
 * URL : https://github.com/square/javapoet
 * License : Apache-2.0
   Section : java

It builds those binary packages:

libjavapoet-java - Java API for generating .java source files

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/j/javapoet/javapoet_1.11.1-1.dsc

Changes since the last upload:

  * Initial release (Closes: #910313)

Kind regards,
Miroslav Kravec

Bug#903904: RFS: wannier90/2.1.0 -- maximally localized Wannier functions

[Miroslav Kravec]

Hello Andrius,

for testing dependencies of package, virtual machine is useful. I use VBox,
and create snapshot after clean install, plus base environment setup (ssh
key, VBox additions), but no other extra packages. Then, I can restore
snapshot and see what needs to be installed, and also I can test build on
almost clean install of system.

Kind regards,
Miroslav Kravec

Dňa st, 19. sep 2018 7:39 Andrius Merkys 
napísal(a):

> Hi Adam,
>
> On 09/17/2018 12:12 PM, Adam Borowski wrote:
> > ! LaTeX Error: File `subfigure.sty' not found.
>
> seems to a missing dependency again. This time I've tried dropping all
> texlive-* packages to detect ones needed. Could you please pull and try it
> one more time?
>
> Many thanks,
> Andrius
>
> --
> Andrius Merkys
> Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
> LT-10257 Vilnius, Lithuania
>
>

Bug#908892: RFS: picocli/3.5.2-2 [RC]

[Miroslav Kravec]

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


Dear mentors,

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

 * Package name: picocli
   Version : 3.5.2-2
   Upstream Author : Remko Popma 
 * URL : https://picocli.info/
 * URL (GitHub): https://github.com/remkop/picocli
 * License : Apache-2.0
   Section : java

It builds those binary packages:

libpicocli-java - Tiny command line interpreter library for Java
applications

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

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

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

dget -x 
https://mentors.debian.net/debian/pool/main/p/picocli/picocli_3.5.2-2.dsc

Changes since the last upload:

* debian/copyright: add missing copyright contributions (Closes: #908606)

Kind regards,
Miroslav Kravec

Copyright attribution for included snippets in debian/copyright

[Miroslav Kravec]

Dear mentors,

I'm solving RC (severity: serious) issue, for my uploaded package,
regarding debian/copyright. And, I'm not sure about copyright
attribution for included code snippets from blogs (code snippet
released under same license).

I have already described problem here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908606#17.

Can anybody help, please?

Kind regards,
Miroslav Kravec

Bug#908410: Fwd: Bug#908410: Acknowledgement (RFS: gradle-apt-plugin/0.10-1 [ITP])

[Miroslav Kravec]

On Mon, Sep 10, 2018 at 12:39 AM Emmanuel Bourg  wrote:

> > could you please take a look at this package, and sponsor upload, if
> > the packaging correct?
>
> Uploaded.


Thank you for sponsoring upload.

Very good packaging, well done!
>

Thanks! It took some effort, so I'm glad the package is considered to be
well packaged.

I see, that both packages are still in debian NEW queue:
* https://ftp-master.debian.org/new/gradle-apt-plugin_0.10-1.html
* https://ftp-master.debian.org/new/picocli_3.5.2-1.html

How long does it usually take to get package approved? And, is there any
further action needed?

Bug#908410: Fwd: Bug#908410: Acknowledgement (RFS: gradle-apt-plugin/0.10-1 [ITP])

[Miroslav Kravec]

Hello Emmanuel Bourg,

could you please take a look at this package, and sponsor upload, if
the packaging correct?

Kind regards,
Miroslav Kravec

-- Forwarded message -
Subject: Bug#908410: Acknowledgement (RFS: gradle-apt-plugin/0.10-1 [ITP])

You can follow progress on this Bug here: 908410:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908410.

Re: RFS: picocli/3.5.2-1 [ITP] -- mighty tiny CLI library for JVM applications

[Miroslav Kravec]

On Sun, Sep 9, 2018 at 5:01 PM Emmanuel Bourg  wrote:
>
> Le 09/09/2018 à 15:19, Miroslav Kravec a écrit :
>
> > Thanks. So, this would be enough for package to pass NEW queue?
>
> Checking the commit history isn't enough, sometimes the authors copy
> files from other projects and they have to be documented in
> debian/copyright too. I usually grep the project files for the words
> "Copyright" and "author", that's a good way to spot external source
> files imported into the project.

Now I see, why it's important to include copyright in source files, not just in
LICENSE/COPYING file as part of sources repository/distribution.

The upstream author just confirmed, that he's the author:
https://github.com/tbroyer/gradle-apt-plugin/issues/89

But, included plugin: id("com.github.hierynomus.license") version "0.14.0"
to gradle build. That would make more "fun" for next packaging...

Bug#908410: RFS: gradle-apt-plugin/0.10-1 [ITP]

[Miroslav Kravec]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "gradle-apt-plugin":

 * Package name: gradle-apt-plugin
   Version : 0.10-1
   Upstream Author :Thomas Broyer
 * URL : https://github.com/tbroyer/gradle-apt-plugin
 * License : Apache-2.0
   Section : java

It builds those binary packages:

gradle-apt-plugin - Gradle plugin to use Java annotation processors

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

  https://mentors.debian.net/package/gradle-apt-plugin

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

dget -x 
https://mentors.debian.net/debian/pool/main/g/gradle-apt-plugin/gradle-apt-plugin_0.10-1.dsc

Changes since the last upload:

  * Initial release (Closes: #908390)


Packaged version is 0.10 of gradle-apt-plugin. Because, version 0.11 and newer
are made for gradle-4.0.2 and newer:


https://github.com/tbroyer/gradle-apt-plugin/blob/v0.11/gradle/wrapper/gradle-wrapper.properties

Version v0.10 of gradle-apt-plugin, which is made for gradle of version 3.4:

https://github.com/tbroyer/gradle-apt-plugin/blob/v0.10/gradle/wrapper/gradle-wrapper.properties.

And, current gradle in debian sid is 3.4.1-7:
https://packages.debian.org/sid/gradle


Kind regards,
Miroslav Kravec

Re: RFS: picocli/3.5.2-1 [ITP] -- mighty tiny CLI library for JVM applications

[Miroslav Kravec]

On Sun, Sep 9, 2018 at 2:43 PM Emmanuel Bourg  wrote:
>
> Le 09/09/2018 à 14:35, Miroslav Kravec a écrit :
>
> > Regarding https://github.com/tbroyer/gradle-apt-plugin, I have
> > encountered a problem. I can't find copyright holder (author), just
> > Apache-2.0. Is that a blocker for package to be accepted?
> >
> > I can set author/copyright-holder to https://github.com/tbroyer/, or
> > extract name and email address from git logs. Would that be
> > acceptable, if there's no explicit statement in sources, itself?
>
> According to the Git history this looks like a one man project. So the
> copyright attribution would be:
>
>2015-2018, Thomas Broyer

Thanks. So, this would be enough for package to pass NEW queue?
Reading https://wiki.debian.org/NewQueue, there's standing:

NEW checking is about three things. In order of priority:
* trying to keep the archive legal,
* trying to keep the package namespace sane,
* trying to reduce the number of bugs in Debian.

Re: RFS: picocli/3.5.2-1 [ITP] -- mighty tiny CLI library for JVM applications

[Miroslav Kravec]

On Sun, Sep 9, 2018 at 10:23 AM Emmanuel Bourg  wrote:
>
> Le 09/09/2018 à 08:20, Miroslav Kravec a écrit :
>
> > Yes, I would like to. I have already following in mind:
> >
> > * Google Auto (for AutoValue): https://github.com/google/auto
> > * gradle-apt-plugin: https://github.com/tbroyer/gradle-apt-plugin
> > * my work-in-progress Java CLI tool: https://github.com/kravemir/svg-labels
>
> Nice, I can sponsor these as well.

Great, good to hear (see) that!

For google auto, I have created ITP bug, and started working on it.
Bug's location:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908372

Regarding https://github.com/tbroyer/gradle-apt-plugin, I have
encountered a problem. I can't find copyright holder (author), just
Apache-2.0. Is that a blocker for package to be accepted?

I can set author/copyright-holder to https://github.com/tbroyer/, or
extract name and email address from git logs. Would that be
acceptable, if there's no explicit statement in sources, itself?

Kind regards,
Miroslav Kravec

Bug#908346: closed by Bart Martens (closing RFS: picocli/3.5.2-1 [ ITP])

[Miroslav Kravec]

> > Sorry for that. It was already sponsored. I was already asleep, and
> > saw notification in the morning.
>
> FYI, you are replying to a robot. Bart runs a cron job to synchronise
> the state of the BTS with the state of the archives (ftp-master,
> mentors etc).

LOL,.. I've written a nice email reply to a robot. Thanks for info :-)

And, is it possible to download package from NEW queue, using dget?

Bug#908346: closed by Bart Martens (closing RFS: picocli/3.5.2-1 [ ITP])

[Miroslav Kravec]

> Package picocli version 3.5.2-1 is in NEW now,
> and the package at mentors is not newer (2018-09-08) than the package in NEW 
> (2018-09-08),
> so there is currently no package to sponsor.
>
> https://ftp-master.debian.org/new/picocli_3.5.2-1.html
> https://mentors.debian.net/package/picocli

Sorry for that. It was already sponsored. I was already asleep, and
saw notification in the morning.

> Please remove the package from mentors or mark it "needs sponsor = no".

Done.

> If for some reason you need to replace the package in NEW,
> then you can upload an updated package to mentors
> and feel free to reopen this RFS 908346 or open a new RFS.

It was a bit adjusted. At least maintainer was set to Debian Java
Maintainers, which is fine. Is it possible to download package from
queue, using dget?

Re: RFS: picocli/3.5.2-1 [ITP] -- mighty tiny CLI library for JVM applications

[Miroslav Kravec]

Hello Emmanuel,

> I'm willing to sponsor the picocli package since this is a dependency of
> JUnit 5.

Thank you for sponsoring picocli package!

I received notification with URL:
https://ftp-master.debian.org/new/picocli_3.5.2-1.html. I see, that
maintainer was changed to Debian Java Maintainers (no problem with
that). Is it standard for Java packages to have maintainer set to
Debian Java Maintainers? Or, is it standard for commonly used Java
libraries?

> Do you plan to work on other Java packages after picocli?

Yes, I would like to. I have already following in mind:

* Google Auto (for AutoValue): https://github.com/google/auto
* gradle-apt-plugin: https://github.com/tbroyer/gradle-apt-plugin
* my work-in-progress Java CLI tool: https://github.com/kravemir/svg-labels

Or, do you have something else, specific, in mind?

Kind regards,
Miroslav Kravec

RFS: picocli/3.5.2-1 [ITP] -- mighty tiny CLI library for JVM applications

[Miroslav Kravec]

Dear mentors and java packagers,

I'm looking for a sponsor for picocli package I've created. RFS is
located at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908346.

Could somebody help me getting this package sponsored? I'll be very thankful :-)

Kind regards,
Miroslav Kravec

Bug#908346: RFS: picocli/3.5.2-1 [ ITP]

[Miroslav Kravec]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: picocli
   Version : 3.5.2-1
   Upstream Author : Remko Popma 
 * URL : https://picocli.info/
 * URL (GitHub): https://github.com/remkop/picocli
 * License : Apache-2.0
   Section : java

It builds those binary packages:

libpicocli-java - mighty tiny CLI library for JVM applications

To access further information about this package, please visit the
following URL: https://mentors.debian.net/package/picocli

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

dget -x 
https://mentors.debian.net/debian/pool/main/p/picocli/picocli_3.5.2-1.dsc

The picocli's adoption is quite growing. It's now part of Groovy,
Micronaut, JUnit 5, and also some small applications. See
https://github.com/remkop/picocli#adoption.

Changes since the last upload:

  * Initial release (Closes: #908302)

Kind regards,
Miroslav Kravec

Bug#907809: RFS: svg-labels/0.3.0-1 [ITP]

[Miroslav Kravec]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "svg-labels":

 * Package name: svg-labels
   Version : 0.3.0-1
   Upstream Author : Miroslav Kravec 
 * URL : https://github.com/kravemir/svg-labels
 * License : Apache-2.0
   Section : utils

It builds those binary packages:

  svg-labels - CLI tool for printable labels generation from SVG templates

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

  https://mentors.debian.net/package/svg-labels

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/svg-labels/svg-labels_0.3.0-1.dsc

More information about svg-labels can be obtained from
https://github.com/kravemir/svg-labels.

Changes since the last upload:

  * Initial release (Closes: #907647)

Following lintian warning will be fixed with next upstream release
(0.4.0), which is being developed, and will contain manpage, or
support generation of a manpage.

  W: svg-labels: binary-without-manpage usr/bin/svg-labels

Following lintian pedantic notices will be fixed before next upload,
as I intend to package these separately, and then add them as
dependencies for svg-labels:

  P: svg-labels source: source-contains-prebuilt-java-object
debian/java_lib/auto-value-1.6.jar
  P: svg-labels source: source-contains-prebuilt-java-object
debian/java_lib/auto-value-annotations-1.6.jar
  P: svg-labels source: source-contains-prebuilt-java-object
debian/java_lib/gradle-apt-plugin-0.18.jar
  P: svg-labels source: source-contains-prebuilt-java-object
debian/java_lib/picocli-3.1.0.jar

The built binary package svg-labels contains only executable JAR (with
included dependencies), and shell wrapper/launcher script. Therefore,
its dependencies list doesn't contain libraries. This will change with
one of future uploads, which would install also JAR artifacts.

Kind regards,
Miroslav Kravec

Bug#900672: RFS: ddccontrol-db/20180602-1

[Miroslav Kravec]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

I am looking for a sponsor for my package "ddccontrol-db"

 * Package name: ddccontrol-db
   Version : 20180602-1
   Upstream Author : Miroslav Kravec 
 * URL : https://github.com/ddccontrol/ddccontrol-db
 * License : GPL v2
   Section : utils

It builds those binary packages:

ddccontrol-db - monitor database for ddccontrol

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

  https://mentors.debian.net/package/ddccontrol-db


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/ddccontrol-db/ddccontrol-db_20180602-1.dsc

Changes since the last upload:

  * New upstream release
  * debian/changelog: remove trailing newline

Kind regards,
Miroslav Kravec

Bug#897193: closed by Adam Borowski <kilob...@angband.pl> (Re: Bug#897193: RFS: ddccontrol-db/20171217-2)

[Miroslav Kravec]

> These issues are pretty much of nitpick level, not really worth your time to
> make an upload on their own.

Probably true. I wanted to make package more lintian clean, and it was
more like a learning experience for me.

Thanks for sponsoring upload(s).

Bug#897193: RFS: ddccontrol-db/20171217-2

[Miroslav Kravec]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

I am looking for a sponsor for my package "ddccontrol-db"

 * Package name: ddccontrol-db
   Version : 20171217-2
   Upstream Author : Miroslav Kravec <kravec.miros...@gmail.com>
 * URL : https://github.com/ddccontrol/ddccontrol-db
 * License : GNU General Public License v2.0
   Section : utils

It builds those binary packages:

ddccontrol-db - monitor database for ddccontrol

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

  https://mentors.debian.net/package/ddccontrol-db


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/ddccontrol-db/ddccontrol-db_20171217-2.dsc

Changes since the last upload:

* debian/changelog: fix file-contains-trailing-whitespace
* debian/compat, debian/control: bump debhelper to 11
* debian/control: update standards to 4.1.4
* debian/copyright: fix copyright-refers-to-symlink-license
* debian/rules: fix debian-rules-is-dh_make-template

Kind regards,
Miroslav Kravec

Bug#896995: RFS: ddccontrol/0.4.4-1

[Miroslav Kravec]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: ddccontrol
   Version : 0.4.4-1
   Upstream Author : Miroslav Kravec <kravec.miros...@gmail.com>
 * URL : https://github.com/ddccontrol/ddccontrol
 * License : GPL-2.0
   Section : utils

It builds those binary packages:

 ddccontrol - program to control monitor parameters
 gddccontrol - program to control monitor parameters (graphical interface)
 libddccontrol-dev - development files for ddccontrol
 libddccontrol0 - shared library for ddccontrol

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

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

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

dget -x 
https://mentors.debian.net/debian/pool/main/d/ddccontrol/ddccontrol_0.4.4-1.dsc

Changes since the last upload:

  * New upstream release (Closes: #888015)
  * debian/ddccontrol.install, debian/libddccontrol0.install:
update location of ddcpci binary (fixes binary-without-manpage),
install with library (ddcpci is used by the library)
  * debian/gddccontrol.lintian-overrides: add override for
desktop-command-not-in-package
  * debian/changelog, debian/control: fix file-contains-trailing-whitespace
  * debian/control: bump standards version to 4.1.4
  * debian/rules: enable bindnow hardening, fixes lintian hardening-no-bindnow

Kind regards,
Miroslav Kravec

Re: compiled binary file in source package

[Miroslav Kravec]

On Fri, Feb 9, 2018 at 10:02 AM, Ben Finney <bign...@debian.org> wrote:
> Miroslav Kravec <kravec.miros...@gmail.com> writes:
>
>> On Fri, Feb 9, 2018 at 9:38 AM, Paul Wise <p...@debian.org> wrote:
>> > https://wiki.debian.org/EmbeddedCodeCopies
>>
>> And, is there any official recommendation to get software (development
>> tools) rather packaged, and used as build dependency, than being
>> copied?
>
> I'm not sure I understand the question. I think you are asking about
> general-purpose, third-party-maintained development tools.
>
> If so: yes, the recommendation is that third-party-maintained software
> should not be bundled, but instead packaged for general use in a
> separate Debian package. That's what the document at the above URL is
> discussing; it includes a link to the relevant Debian Policy section.

Well, policy 
https://www.debian.org/doc/debian-policy/#convenience-copies-of-code
says, that a package should not include convenience copies of
software, for which there's already a package in Debian archive.

> If you mean something different, can you clarify?

I mean, whether Debian community officially encourages developers to
have their software packaged, if there's no technical need to include
their software as convenience copy.

Re: compiled binary file in source package

[Miroslav Kravec]

On Fri, Feb 9, 2018 at 9:38 AM, Paul Wise  wrote:
>> I got interested in this, as I want to use a tool, which isn't
>> packaged in debian. And upstream considers it to be a good idea to
>> include tool's sources into project, where it's used. I like more
>> clean solution - get the tool packaged into debian, then use the tool
>> in my project.
>
> That is a different scenario, it is an embedded code copy:
>
> https://wiki.debian.org/EmbeddedCodeCopies

And, is there any official recommendation to get software (development
tools) rather packaged, and used as build dependency, than being
copied?

Re: compiled binary file in source package

[Miroslav Kravec]

On Fri, Feb 9, 2018 at 5:14 AM, Ben Finney  wrote:
> A source package that contains a file that requires source not in Debian
> is one of the reasons given by FTP masters for rejecting a source
> package , as a
> “serious violation” of Debian policy.

Could you please provide the name of the policy? I've just read it,
and I haven't found one.

I found:
 - Generated files, which is fine, as long as there's corresponding
original form
 - Source missing, which is fine too, because it's not missing, it's in package

I got interested in this, as I want to use a tool, which isn't
packaged in debian. And upstream considers it to be a good idea to
include tool's sources into project, where it's used. I like more
clean solution - get the tool packaged into debian, then use the tool
in my project.

Bug#888246: RFS: ddccontrol/0.4.3-1

[Miroslav Kravec]

On Thu, Jan 25, 2018 at 11:24 PM, Antoine Beaupre <anar...@debian.org> wrote:
> I have found some minor issues in the package that I think should be
> fixed.
>
>  1. the lintian-override is not necessary. binary-without-manpage is
> just a warning, not an error, and we can live with it until the
> binary moves to the right place. in fact, it provides a good
> reminder that this still needs to be done, so do not override it.
>
>  2. in gbp.conf, "upstream-tree = 0.4.3" is out of place. it shouldn't
> be necessary because "upstream-tag = %(version)s" should work.

I have fixed these two issues. The override was already there, in the
original package. I have removed it as you suggested. It should be
fixed, not suppressed.

> Other comments, which are not blockers for an upload - but if you're
> going to reroll the package anyways, might as well consider fixing this:
>
>  3. could you clarify why the override_dh_autoreconf target is
> necessary? isn't autoreconf exactly designed for the purpose of
> running autogen.sh?

>From man page 'dh_autoreconf is responsible for calling
autoreconf...'. The autogen.sh contains also another command:
intltoolize --force

>  4. it is quite strange to see a 10k line diff for a patch release
> (0.4.2 -> 0.4.3). I would encourage you to release a new *major*
> version (e.g. 0.5.0 or 1.0.0) next time you make such significant
> changes. not sure you can fix this now that the tag is public on
> github, so maybe just a note for next time...

How did you perform diff? I ran following:

  $ tar -xvf  ddccontrol_0.4.3.orig.tar.gz
  $ tar -xvf ~/Downloads/ddccontrol_0.4.2.orig.tar.gz
  $ diff ddccontrol-0.4.2 ddccontrol-0.4.3 | wc -l
  305

But, there are messages in diff, that some files are not present in
latest version:

  Only in ddccontrol-0.4.2: ABOUT-NLS
  Only in ddccontrol-0.4.2: aclocal.m4
  Only in ddccontrol-0.4.2: ChangeLog
  Only in ddccontrol-0.4.2: config.guess
  Only in ddccontrol-0.4.2: config.rpath
  Only in ddccontrol-0.4.2: config.sub
  Only in ddccontrol-0.4.2: configure
  Only in ddccontrol-0.4.2: depcomp
  Only in ddccontrol-0.4.2: INSTALL
  Only in ddccontrol-0.4.2: install-sh
  Only in ddccontrol-0.4.2: intltool-extract.in
  Only in ddccontrol-0.4.2: intltool-merge.in
  Only in ddccontrol-0.4.2: intltool-update.in
  Only in ddccontrol-0.4.2: ltmain.sh
  Only in ddccontrol-0.4.2: m4
  Only in ddccontrol-0.4.2: Makefile.in
  Only in ddccontrol-0.4.2: missing
  Only in ddccontrol-0.4.2: mkinstalldirs
  Only in ddccontrol-0.4.2: README

These are mostly generated files, which shouldn't be in original
sources. New files are:

  Only in ddccontrol-0.4.3: autogen.sh
  Only in ddccontrol-0.4.3: CheckList
  Only in ddccontrol-0.4.3: commit.sh
  Only in ddccontrol-0.4.3: .gitignore
  Only in ddccontrol-0.4.3: README.md
  Only in ddccontrol-0.4.3: .travis.yml

These files aren't code related. And, some of them probably need some cleanup.

However, version 1.0.0 will be released once two major issues are done:

 * public API (headers, D-Bus) will be finished, and properly documented,
 * issue with root access/privileges requirement is fixed.

>  5. as lintian noticed, debian/copyright now has a formal syntax,
> specified by DEP5. no big deal, but you could do a refresh on that
> file. decopy is a tool that does this well.

I just found that there's --pedantic option to lintian. Well, there
are multiple notices, which should be fixed. I'll try to fix them all
with next releases.

> Once issues 1 and 2 are fixed, I'm happy to upload the package.

Great. The new upload is now present on mentors:
https://mentors.debian.net/package/ddccontrol

Kind regards,
Miroslav Kravec

Bug#888246: RFS: ddccontrol/0.4.3-1

[Miroslav Kravec]

Based on comments received on IRC (debian-mentors), I have made changes.

Increased compat and debhelper version to 11:

  * debian/compat: increased compatibility level to 11
  * debian/control:
* increased debhelper dependency version to 11

And, altered changelog (removed dh_makeshlibs version from log):

  * debian/libddccontrol0.postinst: removed, because ldconfig is called by
trigger added by dh_makeshlibs
  * debian/libddccontrol0.postrm: removed, because ldconfig is called by
trigger added by dh_makeshlibs

Bug#888246: RFS: ddccontrol/0.4.3-1

[Miroslav Kravec]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: ddccontrol
   Version : 0.4.3-1
   Upstream Author : https://github.com/orgs/ddccontrol/people
 * URL : https://github.com/ddccontrol/ddccontrol
 * License : GNU General Public License v2.0
   Section : utils

It builds those binary packages:

ddccontrol - program to control monitor parameters
gddccontrol - program to control monitor parameters (graphical
interface)
libddccontrol-dev - development files for ddccontrol
libddccontrol0 - shared library for ddccontrol

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

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

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

dget -x
https://mentors.debian.net/debian/pool/main/d/ddccontrol/ddccontrol_0.4.3-1.dsc

Changes since the last upload:

  ddccontrol (0.4.3-1) unstable; urgency=low

  * New upstream release
  * debian/compat: increased compatibility level to 10
  * debian/control:
* updated homepage to GitHub
* updated VCS urls to GitHub
* increased debhelper dependency version to 10
* added build dependencies to build the release
  * debian/ddccontrol.docs: use README.md
  * debian/gddccontrol.dirs: install icons folder
  * debian/gddccontrol.install: install icons (moved from pixmaps)
  * debian/gddccontrol.menu: removed, because there is .desktop file
  * debian/libddccontrol0.postinst: removed, because ldconfig is called by
trigger added by dh_makeshlibs/11
  * debian/libddccontrol0.postrm: removed, because ldconfig is called by
trigger added by dh_makeshlibs/11
  * debian/rules: use autogen.sh, and enable-doc at configure

 -- Miroslav Kravec <kravec.miros...@gmail.com>  Sat, 30 Dec 2017 11:56:57
+0100


Kind regards,
Miroslav Kravec