Bug#888906: marked as done (RFS: groonga/7.1.1-1)

[Debian Bug Tracking System]

Your message dated Thu, 1 Feb 2018 05:41:11 +0100
with message-id <20180201044111.pzlfsqharteqs...@angband.pl>
and subject line Re: Bug#888906: RFS: groonga/7.1.1-1
has caused the Debian Bug report #888906,
regarding RFS: groonga/7.1.1-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.)


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

Dear mentors,

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

* Package name: groonga
  Version : 7.1.1-1
  Upstream Author : Groonga Project 
* Url : http://groonga.org/
* Licenses: LGPL-2.1
  Section : database

It builds those binary packages:

  * groonga
  * groonga-server-common
  * groonga-server-gqtp
  * libgroonga-dev
  * libgroonga0
  * groonga-tokenizer-mecab
  * groonga-token-filter-stem
  * groonga-plugin-suggest
  * groonga-bin
  * groonga-httpd
  * groonga-doc
  * groonga-examples
  * groonga-munin-plugins

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

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

Alternatively, one can download the package with dget using this command:
dget -x 
https://mentors.debian.net/debian/pool/main/g/groonga/groonga_7.1.1-1.dsc


More information about groonga can be obtained from
http://groonga.org/

Changes since last upload:

  * New upstream release.
  * debian/control
- Bump Standards-Version, no other changes are required.

Regards,


pgpoZENKlGONW.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Wed, Jan 31, 2018 at 11:43:59AM +0900, Kentaro Hayashi wrote:
> * Package name: groonga
>   Version : 7.1.1-1

> Changes since last upload:
> 
>   * New upstream release.
>   * debian/control
> - Bump Standards-Version, no other changes are required.

✓

-- 
⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration
⣾⠁⢰⠒⠀⣿⡁ camps is back.  What about KL Warschau (operating until 1956)?
⢿⡄⠘⠷⠚⠋⠀ Zgoda?  Łambinowice?  Most ex-German KLs?  If those were "soviet
⠈⠳⣄ puppets", Bereza Kartuska?  Sikorski's camps in UK (thanks Brits!)?--- End Message ---

Re: question about lintian overrides

[Paul Wise]

On Thu, Feb 1, 2018 at 7:47 AM, Elías Alejandro wrote:

> "Exec=env GDK_BACKEND=x11 uget-gtk %u"

I'm guessing this will break for users running apps under Wayland
instead of X11. I think it would be best to remove "env
GDK_BACKEND=x11" so that Wayland works and the lintian warning goes
away.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Re: question about lintian overrides

[Ben Finney]

Elías Alejandro  writes:

> W: uget: desktop-command-not-in-package
> usr/share/applications/uget-gtk.desktop env
> I've checked the file "uget-gtk.desktop" (created by the upstream) and
> there's a line:
> "Exec=env GDK_BACKEND=x11 uget-gtk %u"

In your opinion, is there a better way to do this? Can the ‘Exec’ value
be re-written so it detects correctly as a command provided by the
package?

> I was thinking solve this issue with an override lintian file:
> uget.lintian-overrides
> but I still get this warning.

You will need to show the content of that file before we can say what
might be wrong with it.

> Do you have experience with this issue? Maybe override it can be a bad
> option?

Maybe; with your knowledge as a maintainer of that package, you might
find a more suitable change that upstream can use.

> Please cc'me.

Please subscribe to this forum, in order to participate more smoothly.

-- 
 \   “A computer once beat me at chess, but it was no match for me |
  `\ at kick boxing.” —Emo Philips |
_o__)  |
Ben Finney 

question about lintian overrides

[Elías Alejandro]

Hello all,
I was running "lintian -i -I --pedantic" and I get:
W: uget: desktop-command-not-in-package
usr/share/applications/uget-gtk.desktop env
I've checked the file "uget-gtk.desktop" (created by the upstream) and
there's a line:
"Exec=env GDK_BACKEND=x11 uget-gtk %u"
I was thinking solve this issue with an override lintian file:
uget.lintian-overrides
but I still get this warning.
Do you have experience with this issue? Maybe override it can be a bad option?
My lintian versión: 2.5.72

Please cc'me.

Thanks!
Elías

Bug#888807: RFS: qstardict/1.3-1

[Tobias Frost]

Control: tags -1 moreinfo

Hi Boyuan,

here's your review:

- small typo in d/copyright: Alexander had maintained the package in
  2007 and 2008. Also it should be "Comment:" (singular)
- Please review d/copyright. I found at least one file which is not
  properly recorded (wrong license and wrong copyright holder)
- don't install README.md -- it does not have extra information beyond
  a package  description and compilation instructions (which are useless
  for the users of the binary package)
  There is also a slight bug in it: The URLs at the bottom seems
  outdated, they will forward to the github project from the watch file.
  Maybe at least report that to upstream.)
- Please upstream the manpage (Alexander as upstream should include it
  there so that other distributions will also benefit from it)
- The embedded libqxt -- can you use the Debian packaged version?
- Some lintian stuff:
N: Processing binary package qstardict (version 1.3-1, arch amd64) ...
I: qstardict: spelling-error-in-binary usr/bin/qstardict writen written
I: qstardict: spelling-error-in-binary
usr/lib/qstardict/plugins/libstardict.so wil will
I: qstardict: spelling-error-in-binary
usr/lib/qstardict/plugins/libstardict.so formated formatted
I: qstardict: desktop-entry-lacks-keywords-entry
usr/share/applications/qstardict.desktop
(spelling errors should be at least sent upstream, but they
are quite easy to fix and then a patch can be sent upstream :))
note that the spelling errors might also needs fixing in the
translation templates.
- check-all-the-things also found a bit of stuff.
- The watch file is not working.

Future homework (optional -- bonus points area ;-))
- There are many bugs on the BTS that needs bug triaging, e.g
  #494701, #611106, #699940 and maybe others too.  It is possible that
  those bugs are not valid anymore, as they are quite old already.
  Please document the findings in the BTS, file them upstream and/or
  link them to upstream bugs if relevant :)
- Please check with upstream if they have the source for the pngs
  which where obviously created with inkscape (check all the things
  told so). They should be included in the source...
# Check with upstream where the Inkscape SVG source files are.
$ find . -type f \( -iname '*.png' -o -iname '*.gif' -o -iname '*.jpg'
-o -iname '*.jpeg' \) -exec grep -nHiF inkscape {} +
Binary file ./qstardict/pixmaps/system-search.png matches
Binary file ./qstardict/pixmaps/download.png matches
Binary file ./qstardict/pixmaps/plugin.png matches

Please fix the points above, and then remove the moreinfo tag to
signal that it is ready for another round.

Many thanks!

-- 
tobi


signature.asc
Description: PGP signature

How to sensibly announce a finalised packaging if I do not intend to upload myself (Was: packjpg packaging: C++ help needed)

[Andreas Tille]

Hi Juhani,

On Wed, Jan 31, 2018 at 07:35:47PM +0200, Juhani Numminen wrote:
> 
> The compilation succeeds if I modify the patch not to define DEV_INFOS:
> 
> $ git diff -U0
> diff --git a/debian/patches/dev.patch b/debian/patches/dev.patch
> index 02869a1..415ebda 100644
> --- a/debian/patches/dev.patch
> +++ b/debian/patches/dev.patch
> @@ -14 +14 @@ Description: include developer functions
> -+#define DEV_INFOS // uncomment to include developer information
> ++// #define DEV_INFOS // uncomment to include developer information^M
> 
> (Afterwards I ran "quilt push -a ; quilt refresh" to clean up the patch.)
> 
> With DEV_INFOS defined, packjpg.cpp tries to use member functions that
> were removed in https://github.com/packjpg/packJPG/commit/bb72a4e1b.

Thanks for the hint.  This works and I think I have completed the
packaging.  However, I think I will not upload since the result of
the compression is no usable JPG format any more.  Thus I've added
an according paragraph to the description:

 The compression is done into a packJPG native format PJG which can
 not be used by any image viewer.  To use the image again you need to
 re-do the compression step using packJPG.  Thus the compression is
 only helpful for archiving the images.

So if somebody is interested in taking over packjpg[1] that's fine but
since I have no use personally I will not do the final upload.  Do we
have any proper method to announce a ready packaging for somebody
to pick up.  The closest I know would be an RFP bug - but I'm not
really requesting the packaging, thought.

Kind regards

  Andreas.

[1] https://anonscm.debian.org/git/pkg-phototools/packjpg.git

-- 
http://fam-tille.de

request for reviews/sponsorship

[Sebastian Kuzminsky]

Hello Mentors, I'm an aspiring maintainer looking for feedback on a 
package I've made.


I'm interested in personal fabrication technologies, and to that end 
I've packaged dxf2gcode, a CAM program that takes 2d drawings of parts 
and produces g-code for running on CNC mills and lathes.  (This software 
is a bit like a slicer for 3d printing, but targets subtractive 
fabrication techniques instead of additive.)


Here is my ITP:  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888298

Here is my package on mentors.d.n: 
https://mentors.debian.net/package/dxf2gcode


And here is my RFS (which I should have used the mentors.d.n RFS 
template for, but didn't): 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888526



Thanks!


--
Sebastian Kuzminsky

Re: packjpg packaging: C++ help needed

[Juhani Numminen]

Andreas Tille kirjoitti 31.01.2018 klo 14:49:
> Hi,
> 
> I stumbled upon unfinished packaging for packjpg in collab-maint SVN[1].
> I intended to save the current packaging state to Git before SVN will be
> closed down and consiered pkg-phototools a better place than
> collab-maint.  So I updated the packaging to latest upstream and pushed
> the packaging to Git[2].
> 
> When trying to build[2] I stumbled upon
> 
> ...
> g++ -c -o aricoder.o aricoder.cpp -I. -O3 -Wall -pedantic -funroll-loops 
> -ffast-math -fsched-spec-load -fomit-frame-pointer -std=c++14 -DUNIX
> packjpg.cpp: In function 'bool pack_pjg()':
> packjpg.cpp:3312:22: error: 'class Writer' has no member named 'getpos'
>   dev_size = str_out->getpos();^M
> ...
> 
> 
> Unfortunately I have no idea how to fix this.  Any hints?

The compilation succeeds if I modify the patch not to define DEV_INFOS:

$ git diff -U0
diff --git a/debian/patches/dev.patch b/debian/patches/dev.patch
index 02869a1..415ebda 100644
--- a/debian/patches/dev.patch
+++ b/debian/patches/dev.patch
@@ -14 +14 @@ Description: include developer functions
-+#define DEV_INFOS // uncomment to include developer information
++// #define DEV_INFOS // uncomment to include developer information^M

(Afterwards I ran "quilt push -a ; quilt refresh" to clean up the patch.)

With DEV_INFOS defined, packjpg.cpp tries to use member functions that
were removed in https://github.com/packjpg/packJPG/commit/bb72a4e1b.

> Kind regards
> 
> Andreas.

Regards,
Juhani

packjpg packaging: C++ help needed

[Andreas Tille]

Hi,

I stumbled upon unfinished packaging for packjpg in collab-maint SVN[1].
I intended to save the current packaging state to Git before SVN will be
closed down and consiered pkg-phototools a better place than
collab-maint.  So I updated the packaging to latest upstream and pushed
the packaging to Git[2].

When trying to build[2] I stumbled upon

...
g++ -c -o aricoder.o aricoder.cpp -I. -O3 -Wall -pedantic -funroll-loops 
-ffast-math -fsched-spec-load -fomit-frame-pointer -std=c++14 -DUNIX
packjpg.cpp: In function 'bool pack_pjg()':
packjpg.cpp:3312:22: error: 'class Writer' has no member named 'getpos'
  dev_size = str_out->getpos();^M
  ^~
packjpg.cpp:3314:27: error: 'class Writer' has no member named 'getpos'
  dev_size_hdr += str_out->getpos() - dev_size;^M
   ^~
packjpg.cpp:3340:23: error: 'class Writer' has no member named 'getpos'
   dev_size = str_out->getpos();^M
   ^~
packjpg.cpp:3343:35: error: 'class Writer' has no member named 'getpos'
   dev_size_zsr[ cmp ] += str_out->getpos() - dev_size;^M
   ^~
packjpg.cpp:3344:23: error: 'class Writer' has no member named 'getpos'
   dev_size = str_out->getpos();^M
   ^~
...


Unfortunately I have no idea how to fix this.  Any hints?

Kind regards

Andreas.

[1] https://anonscm.debian.org/viewvc/collab-maint/deb-maint/packjpg/
[2] https://anonscm.debian.org/cgit/pkg-phototools/packjpg.git

-- 
http://fam-tille.de

Re: Solved Re: Bug#883702: mentors.debian.net for lina acidentally deleted

[Geert Stappers]

On Wed, Jan 31, 2018 at 03:00:41AM +0100, Albert van der Horst wrote:
> Mattia Rizzolo schreef op 2018-01-30 21:58:
> >On Tue, Jan 30, 2018 at 09:45:48PM +0100, Albert van der Horst wrote:
> >>
> >>What can I do from here?
> >
> >You probably have an .upload file lying around there that is blocking
> >dput.  Either remove that .upload file or use -f.
> 
> I can't find a local .upload file.
> 
> I saw the -f option in dput but I'm reluctant to use an -f option which
> should be reserved for situations where you really know what you're
> doing. That was clearly not the case with me.
> 
> Now that you advice using it, and I can see you're an experienced
> Debian developer, I tried it. It worked. Thanks.

:-)


> What remains is reopening the RFS issue.

:-) I think you missed 
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883702#51


Cheers
Your Sponsor
-- 
Leven en laten leven