Bug#867158: RFS: weresync/1.0.7-1 [ITP]

[Daniel Manila]

Another update mainly to math upstream version. There should be no
functional difference in package performance. Some language files were
moved in order to better work with Python's packaging system.

You can download the new package here:
https://mentors.debian.net/debian/pool/main/w/weresync/weresync_1.0.7-1.dsc


Sincerely,
Daniel Manila


signature.asc
Description: OpenPGP digital signature

Install documentation for a library to the library's documentation directory

[Ben Finney]

Howdy all,

How should I make library documentation available at a single obvious
location, for any of several binary packages of the library?


I am working on a package with the following dependencies::

Source: pyfoo

Package: python3-foo
Section: python
Suggests: python-foo-doc

Package: python-foo
Section: python
Suggests: python-foo-doc

Package: python-foo-doc
Section: doc

The ‘python-foo-doc’ package installs the HTML documentation for the
library. What I want is to install that into a single location, that all
three packages will use.


Maybe ‘/usr/share/doc/python-foo/’? The ‘dh_installdoc(1)’ tool has an
option to enable that. The man page says::

--link-doc=package
Make the documentation directory of all packages acted on be a
symlink to the documentation directory of package. This has no
effect when acting on package itself, or if the documentation
directory to be created already exists when dh_installdocs is
run. To comply with policy, package must be a binary package
that comes from the same source package.

That sounds very much like what I want. So, in ‘debian/rules’::

override_dh_installdocs:
dh_installdocs --link-doc=python-foo

That has the following effects:

* All three packages use ‘/usr/share/doc/python-foo/’ for their
  documentation target.

* Package ‘python3-foo’ installs a symlink in ‘/usr/share/doc/’ named
  ‘python3-foo’, pointing to ‘python-foo’.
  Package ‘python-foo-doc’ installs a symlink in ‘/usr/share/doc/’ named
  ‘python-foo-doc’, pointing to ‘python-foo’.

* Package ‘python3-foo’ gains “Depends: python-foo (= 1.2.3-1)”.
  Package ‘python-foo-doc’ gains “Depends: python-foo (= 1.2.3-1)”.

That last point is definitely not what I want; the documentation package
should not depend on the library package, and the Python 3 library
should not depend on the Python 2 library.

I understand why this dependency is enforced: it makes the directory
available to be the target of the symlink. But the dependency brings in
the whole library, which is not what I want.


How can I install the documentation at ‘/usr/share/doc/python-foo/’,
without spurious dependencies like above, and using the tools normally?

-- 
 \  “Computer perspective on Moore's Law: Human effort becomes |
  `\   twice as expensive roughly every two years.” —anonymous |
_o__)  |
Ben Finney

Re: How to make a shared lib recognized by debhelpers?

[Andrey Rahmatullin]

What does file(1) return for this file?

-- 
WBR, wRAR


signature.asc
Description: PGP signature

How to make a shared lib recognized by debhelpers?

[Ole Streicher]

Hi,

I am currently adopting plplot [1], which included a simplification and
modernization of the build system (using modern debhelpers).

I now have the problem, that one of the shared libraries is probably not
detected correctly: "lintian" tells me

E: octave-plplot: unstripped-binary-or-object 
usr/lib/x86_64-linux-gnu/octave/site/oct/api-v51/x86_64-pc-linux-gnu/plplot_octave.oct
E: octave-plplot: missing-dependency-on-libc needed by 
usr/lib/x86_64-linux-gnu/octave/site/oct/api-v51/x86_64-pc-linux-gnu/plplot_octave.oct

The Depends: field of the package however contains the entry
${shlibs:Depends}, and this also works correctly for the other binary
packages built from the source.

The manpages of dh_makeshlibs, dh_shlibdeps and dh_strip didn't
enlighten me here. In the original plplot package, "strip" was called
directly in install-arch, which doesn't look very smart, because it
f.e. also prevents the creation of a proper debug image, and
dpkg-shlibdeps needs to be called lated as well explicitly for this
library.

How can I do a proper handling of the library here? I guess (I am not an
octave expert, however), that the name of the library shall not be
changed.

Best regards

Ole

Bug#860496: marked as done (RFS: drgeo/1.1.0-10.3 [NMU, RC])

[Debian Bug Tracking System]

Your message dated Mon, 17 Jul 2017 11:11:35 -0700
with message-id <20170717181135.4ohj7ekiiil2q...@iris.silentflame.com>
and subject line Closing inactive RFS
has caused the Debian Bug report #860496,
regarding RFS: drgeo/1.1.0-10.3 [NMU, RC]
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.)


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

Package: sponsorship-requests
Severity: important

Dear mentors,

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

* Package name: drgeo
  Version : 1.1.0-10.3
  Upstream Author : https://mentors.debian.net/package/drgeo
* URL : http://directory.fsf.org/wiki/Dr._geo
* License : GPLv2 or later
  Section : math

 It builds this binary packages:

   drgeo - interactive geometry software

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


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


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


   dget -x 
https://mentors.debian.net/debian/pool/main/d/drgeo/drgeo_1.1.0-10.3.dsc


 Changes since the last upload:

 * Fixed compatibility with Guile 2.0. (Closes: #707903)

--
Sincerely,
Patrick Hetu
--- End Message ---
--- Begin Message ---
Closing inactive RFS.  Please feel free to re-open if you have an
updated source package.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---

Bug#851937: marked as done (RFS: farbfeld/2.20170109-1 ITP)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jul 2017 11:04:49 -0700
with message-id <20170717180449.ewwrpalhxrbue...@iris.silentflame.com>
and subject line Re: Bug#851937: RFS: farbfeld/2.20170109-1 ITP
has caused the Debian Bug report #851937,
regarding RFS: farbfeld/2.20170109-1 ITP
to be marked as done.

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

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


-- 
851937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851937
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 "farbfeld"

* Package name : farbfeld
  Version  : 2.20170109-1
  Upstream Author  : Laslo Hunhold 
* Url  : http://tools.suckless.org/farbfeld
* Licenses : ISC
  Programming Lang : C
  Section  : graphics

 Farbfeld is a lossless image-format designed to be parsed and piped
 easily. It is designed to be as simple as possible, leaving the task
 of compression to outside tools, beating PNG's filesize in many
 cases.
 .
 This package contains tools for converting between farbfeld format
 and other image formats (png, jpeg, ppm, pam, git)

It builds those binary packages:

  * farbfeld

Please note, that package is maintained with dgit(1) tool using
dgit-maint-merge(7) workflow. In particular, it means that quilt
patches are squashed in source package and are not intended for
review. For more information about how to sponsor this package,
see dgit-sponsorship(7).

  Git repository: 
https://anonscm.debian.org/cgit/users/kaction-guest/farbfeld.git
  Git branch: master
  Orig tar.gz: from tag 2.20170109

With /bin/sh following commands should suffice:

  $ git clone https://anonscm.debian.org/cgit/users/kaction-guest/farbfeld.git 
farbfeld
  $ cd farbfeld
  $ git archive -o ../farbfeld_2.20170109.orig.tar.xz 2.20170109
  $ dgit sbuild

Regards,
  Dmitry Bogatov
--- End Message ---
--- Begin Message ---
Uploaded to NEW -- thank you for your help.

On Mon, Jul 17, 2017 at 09:45:42AM +0200, Paride Legovini wrote:
> > - your changes to the patch header do not make sense: the '3..' will not
> >   yield "the changes made by the Debian maintainer in the first upload
> >   of upstream version 3".
> 
> Should be fixed now. The 'debian/3-1' tag is still missing, I guess the
> right time to tag it is after the package is accepted.

Right, dgit creates the tag during the upload.

You probably want to fetch the tag from dgit-repos.[1]

> > - I disagree with you about Dmitry's `convert` patch.  It just
> > doesn't seem likely to me that there would be difficult merge
> > conflicts with new upstream versions, and it is indeed useful to
> > inform the user that convert is not available.  But I will defer to
> > your judgement -- if you're sure about dropping the patch, maybe
> > imagemagick should be moved to a hard dependency?
> 
> I still believe this patch belongs to upstream, and even if it's trivial
> to maintain it already prevented a clean 'git merge' of upstream version
> 3.

Ah, really?  I didn't realise that.

> The package works fine even without imagemagick, it just can't handle
> all those image formats. Imagemagick itself is not very kind when a
> helper binary is missing:
> 
> $ convert test.jpg test.webp
> convert-im6.q16: delegate failed `'cwebp' -quiet %Q '%i' -o '%o'' @
> error/delegate.c/InvokeDelegate/1919.
> 
> (cwebp is provided by the webp package, which is not even suggested by
> imagemagick).

Urgh, indeed, that's not very user-friendly.

> In general I believe it's better not to apply patches whenever
> possible, for several reasons. I understand this one is trivial, but
> the issue it addresses is, in my opinion, even more trivial.
> 
> This said, I left it in. I explained my general thought on the topic,
> but I value your feedback and while I think there is no strong reason to
> include this patch, I see there is no strong reason to oppose it.
> 
> I would be against a hard dependency on imagemagick.

Right, not sure why I suggested that.

[1]  http://browse.dgit.debian.org/farbfeld

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---

Bug#868088: marked as done (RFS: sysbench/1.0.8+ds-1 -- multi-threaded benchmark tool for database systems)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jul 2017 10:51:53 -0700
with message-id <20170717175153.esrqib57vs44y...@iris.silentflame.com>
and subject line Re: Bug#868088: RFS: sysbench/1.0.8+ds-1 -- multi-threaded 
benchmark tool for database systems
has caused the Debian Bug report #868088,
regarding RFS: sysbench/1.0.8+ds-1 -- multi-threaded benchmark tool for 
database systems
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.)


-- 
868088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: spwhit...@spwhitton.name

Dear mentors,

I am looking for a sponsor for "sysbench":

  Package name: sysbench
  Version : 1.0.8+ds-1
  Upstream Author : Alexey Kopytov
  URL : https://github.com/akopytov/sysbench
  License : GPL-2
  Section : misc

It builds a single binary package:
  sysbench - multi-threaded benchmark tool for database systems

Changes since last upload:
  * New upstream release.
  * Patches: remove 02 and 05: merged upstream.
  * Bump Standards-Version to 4.0.0 (from 3.9.8; no further changes).
  * Control: limit build-depend on libaio-dev to linux-only.


Git branch for use with dgit-maint-gbp workflow is available at:
 https://github.com/jcfp/debpkg-sysbench/tree/master/
 HEAD commit id a1ccb164415345c6b1c648018ed2ec5c75b5295a

As requested in dgit-sponsorship(7), some sample commands:
To generate the orig tarball:
 origtargz
or using pristine-tar directly:
 pristine-tar checkout ../sysbench_1.0.8+ds.orig.tar.gz

To build the source package:
 dgit --gbp build-source

To upload:
 dgit --gbp push


Regards.


pgpcq1UMgBZqQ.pgp
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Mon, Jul 17, 2017 at 08:42:09AM +0200, JCF Ploemen wrote:
> Thank you, all done.

And uploaded -- thanks!

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---

Bug#868668: RFS: parsedatetime/2.4-2

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the following package:

* Package name: parsedatetime
  Version : 2.4-2
  Upstream Author : Mike Taylor
* URL : https://pypi.python.org/pypi/parsedatetime
* License : Apache-2.0
  Section : python

Please check out the package by visiting the following URL:

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

Changes since the last upload:

  * Team upload

  [ Ghislain Antony Vaillant ]
  * Update the gbp configuration
  * Remove superfluous ${shlibs:Depends}
  * Release to unstable

Best regards,
Ghis

Bug#845710: marked as done (RFS: mongovi/1.0.0-1 [ITP])

[Debian Bug Tracking System]

Your message dated Mon, 17 Jul 2017 10:20:28 +
with message-id 
and subject line closing RFS: mongovi/1.0.0-1 [ITP]
has caused the Debian Bug report #845710,
regarding RFS: mongovi/1.0.0-1 [ITP]
to be marked as done.

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

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


-- 
845710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845710
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 "mongovi"

* Package name: mongovi
  Version : 1.0.0-1
  Upstream Author : me
* URL : https://github.com/timkuijsten/mongovi
* License : ISC
  Section : database

It builds those binary packages:

  mongovi- Command line interface for MongoDB

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


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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/m/mongovi/mongovi_1.0.0-1.dsc


Regards,

Tim
--- End Message ---
--- Begin Message ---
Package mongovi has been removed from mentors.--- End Message ---

Bug#851937: RFS: farbfeld/2.20170109-1 ITP

[Paride Legovini]

control: tag -1 -moreinfo

On 2017-07-15 02:28, Sean Whitton wrote:
> 
> Here is a review of 534d41f:

Thank you for reviewing it.

> - I think we should list Dmitry in the Uploaders: field

Done

> - your git history does not really give credit to Dmitry for his work.
>   I'd like to suggest starting again, and doing it like this:

This is because I didn't start using dgit from the beginning, and I
rebuilt debian/ in a separate working tree. Now I better understand
dgit's philosophy and I started over. The repository is still at

https://anonscm.debian.org/cgit/users/paride-guest/farbfeld.git/

but it's a new one, which retains the full history.

> - I also think it would be good to state in debian/changelog that most
>   of the Debianisation is due to Dmitry

Done

> - your changes to the patch header do not make sense: the '3..' will not
>   yield "the changes made by the Debian maintainer in the first upload
>   of upstream version 3".

Should be fixed now. The 'debian/3-1' tag is still missing, I guess the
right time to tag it is after the package is accepted.

> - I disagree with you about Dmitry's `convert` patch.  It just doesn't
>   seem likely to me that there would be difficult merge conflicts with
>   new upstream versions, and it is indeed useful to inform the user that
>   convert is not available.  But I will defer to your judgement -- if
>   you're sure about dropping the patch, maybe imagemagick should be
>   moved to a hard dependency?

I still believe this patch belongs to upstream, and even if it's trivial
to maintain it already prevented a clean 'git merge' of upstream version
3. The package works fine even without imagemagick, it just can't handle
all those image formats. Imagemagick itself is not very kind when a
helper binary is missing:

$ convert test.jpg test.webp
convert-im6.q16: delegate failed `'cwebp' -quiet %Q '%i' -o '%o'' @
error/delegate.c/InvokeDelegate/1919.

(cwebp is provided by the webp package, which is not even suggested by
imagemagick).

In general I believe it's better not to apply patches whenever possible,
for several reasons. I understand this one is trivial, but the issue it
addresses is, in my opinion, even more trivial.

This said, I left it in. I explained my general thought on the topic,
but I value your feedback and while I think there is no strong reason to
include this patch, I see there is no strong reason to oppose it.

I would be against a hard dependency on imagemagick.


Thanks again,

Paride

Bug#868088: RFS: sysbench/1.0.8+ds-1 -- multi-threaded benchmark tool for database systems

[JCF Ploemen]

Control: tag -1 -moreinfo

On Sat, 15 Jul 2017 16:01:25 -0700
Sean Whitton  wrote:

> Could you explain the need for this change, please?  Perhaps directly
> in the changelog.
> 
> Also, you need to run `dch -r` -- the changelog timestamp is behind
> changes you've made.

Thank you, all done. Libaio provides access to the Linux kernel
asynchronous I/O system calls, limiting its use and availability to
those architectures. For sysbench, it is optional but enabled by
default if found at build time.


New HEAD commit id is 4c390908513c4b61a66e3a9721ed9a03025030b2


pgpsb8rFM5tv9.pgp
Description: OpenPGP digital signature