Bug#898655: marked as done (RFS: speedcrunch/0.12.0-4 [RC])

2018-05-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 22:19:01 +0200
with message-id <20180523201901.uewmlunpolu2f...@angband.pl>
and subject line Re: Bug#898655: RFS: speedcrunch/0.12.0-4 [RC]
has caused the Debian Bug report #898655,
regarding RFS: speedcrunch/0.12.0-4 [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.)


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

* Package name: speedcrunch
  Version : 0.12.0-4
  Upstream Author : Helder Correia & others
* URL : http://speedcrunch.org
* License : GPL-2+
  Section : math

It builds those binary packages:

  speedcrunch - High precision calculator

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/s/speedcrunch/speedcrunch_0.12.0-4.dsc

Changes since the last upload:

  * d/control:
- update VCS-* urls
- bump Standards-Version
- use python3-sphinx instead of python-sphinx
  * d/compat: bump debhelper compat version to 10
  * d/patches, d/rules: build the HTML manual in a separate step
- Rebuilding the HTML manual during the build has proven fragile.
Instead,
  the manual is now built in a separate step and the application build
is
  pointed at the result of that build.
- Closes: #897531

---

In addition to some housekeeping, a change in... CMake? Qt? -- caused an
FTBFS. Instead of working around it, we changed the build process so that
building the HTML manual is now a separate step. This should be more
robust, but it makes d/rules a bit more complicated. I'm not sure I used
the dh_auto_* targets in the best possible fashion there.

Upstream bug:
https://bitbucket.org/heldercorreia/speedcrunch/issues/830/build-with-drebuild_manual-fails-on-debian

Regards,
Felix
--- End Message ---
--- Begin Message ---
On Mon, May 14, 2018 at 07:51:33PM +0200, Felix Krull wrote:
> * Package name: speedcrunch
>   Version : 0.12.0-4

> Changes since the last upload:
> 
>   * d/control:
> - update VCS-* urls
> - bump Standards-Version
> - use python3-sphinx instead of python-sphinx
>   * d/compat: bump debhelper compat version to 10
>   * d/patches, d/rules: build the HTML manual in a separate step
> - Rebuilding the HTML manual during the build has proven fragile.
> Instead,
>   the manual is now built in a separate step and the application build
> is
>   pointed at the result of that build.
> - Closes: #897531


> In addition to some housekeeping, a change in... CMake? Qt? -- caused an
> FTBFS. Instead of working around it, we changed the build process so that
> building the HTML manual is now a separate step. This should be more
> robust, but it makes d/rules a bit more complicated. I'm not sure I used
> the dh_auto_* targets in the best possible fashion there.

While it is vital that things are built from source, it doesn't matter how
you do it.

Building stuff during configure rather than compile is a bit strange, but
there's no non-philosophical reason to avoid doing so.

Thus... it's ok.

Uploaded.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ .globl _start↵.data↵rc: .ascii "/etc/init.d/rcS\0"↵.text↵_start
⣾⠁⢰⠒⠀⣿⡁ mov $57,%rax↵syscall↵cmp $0,%rax↵jne child↵parent:↵mov $61,%rax
⢿⡄⠘⠷⠚⠋⠀ mov $-1,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall↵jmp parent↵child:
⠈⠳⣄ mov $59,%rax↵mov $rc,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall--- End Message ---


Bug#899188: marked as done (RFS: urlwatch/2.11-1)

2018-05-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 21:34:03 +0200
with message-id <20180523193403.6jtqxfgoyojvl...@angband.pl>
and subject line Re: Bug#899188: RFS: urlwatch/2.11-1
has caused the Debian Bug report #899188,
regarding RFS: urlwatch/2.11-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.)


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

Dear mentors,

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

 * Package name: urlwatch
   Version : 2.11-1
   Upstream Author : Thomas Perl
 * URL : https://thp.io/2008/urlwatch/
 * License : BSD-3-clause
   Section : web

It builds those binary packages:
  urlwatch   - tool for monitoring webpages for updates

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

Alternatively, one can download the package with dget using this command:
  dget -x https://mentors.debian.net/debian/pool/main/u/urlwatch/
urlwatch_2.11-1.dsc

More information about urlwatch can be obtained from
https://github.com/thp/urlwatch.

Changes since the last upload:

urlwatch (2.11-1) unstable; urgency=medium

  * New upstream release
  * Updated patches to new upstream sources
  * Removed trailing spaces
  * Removed X-Python3-Version per Lintian rule ancient-python-version-field
  * Updated Standards-Version to 4.1.4

Regards,

Maxime Werlen
--- End Message ---
--- Begin Message ---
On Sun, May 20, 2018 at 03:59:47PM +0200, Maxime Werlen wrote:
>  * Package name: urlwatch
>Version : 2.11-1

> urlwatch (2.11-1) unstable; urgency=medium
> 
>   * New upstream release
>   * Updated patches to new upstream sources
>   * Removed trailing spaces
>   * Removed X-Python3-Version per Lintian rule ancient-python-version-field
>   * Updated Standards-Version to 4.1.4

✓

-- 
⢀⣴⠾⠻⢶⣦⠀ .globl _start↵.data↵rc: .ascii "/etc/init.d/rcS\0"↵.text↵_start
⣾⠁⢰⠒⠀⣿⡁ mov $57,%rax↵syscall↵cmp $0,%rax↵jne child↵parent:↵mov $61,%rax
⢿⡄⠘⠷⠚⠋⠀ mov $-1,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall↵jmp parent↵child:
⠈⠳⣄ mov $59,%rax↵mov $rc,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall--- End Message ---


Bug#898975: marked as done (RFS: lua-moses/1.6.1+git20170613-2)

2018-05-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 21:27:52 +0200
with message-id <20180523192752.sdamjtbdwoaoi...@angband.pl>
and subject line Re: Bug#898975: RFS: lua-moses/1.6.1+git20170613-2
has caused the Debian Bug report #898975,
regarding RFS: lua-moses/1.6.1+git20170613-2
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.)


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

Dear mentors,

I am looking for a sponsor for my package "lua-moses":

 * Package name: lua-moses
   Version : 1.6.1+git20170613-2
   Upstream Author :
 * URL :
 * License : MIT
   Section : interpreters

The package can be obtained here:

  https://salsa.debian.org/science-team/lua-moses

which has passed all the tests of debomatic-amd64:

  
http://debomatic-amd64.debian.net/distribution#unstable/lua-moses/1.6.1+git20170613-2/buildlog

Changes since the last upload:

  lua-moses (1.6.1+git20170613-2) unstable; urgency=medium
  
* Packaging repo was moved to Science Team (Salsa).
  + Update Vcs-* fields accordingly.
* Maintainer is now Science Team. Move myself to Uploaders.
  + Move myself to Uploaders.
* Install guide docs.
  + Register the docs in doc-base.
* Add support for lua 5.3
  + Also lua5.3 tests in autopkgtest control file.
* Bump Standards-Version to 4.1.4 (no changes).
* Mark the package as Multi-Arch: foreign because it contains no
  arch-dep file.



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Fri, May 18, 2018 at 05:45:49AM +, Lumin wrote:
>  * Package name: lua-moses
>Version : 1.6.1+git20170613-2

> Changes since the last upload:
> 
>   lua-moses (1.6.1+git20170613-2) unstable; urgency=medium
>   
> * Packaging repo was moved to Science Team (Salsa).
>   + Update Vcs-* fields accordingly.
> * Maintainer is now Science Team. Move myself to Uploaders.
>   + Move myself to Uploaders.
> * Install guide docs.
>   + Register the docs in doc-base.
> * Add support for lua 5.3
>   + Also lua5.3 tests in autopkgtest control file.
> * Bump Standards-Version to 4.1.4 (no changes).
> * Mark the package as Multi-Arch: foreign because it contains no
>   arch-dep file.

✓

-- 
⢀⣴⠾⠻⢶⣦⠀ .globl _start↵.data↵rc: .ascii "/etc/init.d/rcS\0"↵.text↵_start
⣾⠁⢰⠒⠀⣿⡁ mov $57,%rax↵syscall↵cmp $0,%rax↵jne child↵parent:↵mov $61,%rax
⢿⡄⠘⠷⠚⠋⠀ mov $-1,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall↵jmp parent↵child:
⠈⠳⣄ mov $59,%rax↵mov $rc,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall--- End Message ---


Bug#897964: marked as done (RFS: uriparser/0.8.5-1)

2018-05-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 21:21:15 +0200
with message-id <20180523192115.crbcvappgdx2r...@angband.pl>
and subject line Re: Bug#897964: RFS: uriparser/0.8.5-1
has caused the Debian Bug report #897964,
regarding RFS: uriparser/0.8.5-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.)


-- 
897964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

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

  Dear mentors,

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

   Package name: uriparser
   Version : 0.8.5-1
   Upstream Author : Sebastian Pipping 
   URL : https://github.com/uriparser/uriparser
   License : BSD-3-clause, LGPL-2.1+, GPL-3+ 
   Section : libs

  It builds those binary packages:

 liburiparser-dev - development files for uriparser
 liburiparser-doc - documentation files for uriparser
 liburiparser1 - URI parsing library compliant with RFC 3986

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.8.5-1.dsc

or from git:

https://anonscm.debian.org/cgit/collab-maint/uriparser.git?h=release%2Fdebian%2F0.8.5-1


  Changes since the last upload:

  * New upstream release (Closes: #893316).
- Refresh symbols file.
- Refresh debian/copyright.
- Rewrite debian/upstream/metadata.
  * Remove trailing whitespaces:
- debian/changelog
- debian/control
- debian/rules
  * Migrate to debhelper 11:
- Change debian/compat to 11.
- Bump minimum debhelper version in debian/control to >= 11.
- Remove dh-autoreconf from Build-Depends.
  * Declare compliance with Debian Policy 4.1.4 (No changes needed).
  * Change to my new email address:
- debian/control
- debian/copyright
  * New README.source to explain the branching model used.
  * debian/rules:
- Switch to $(DEB_UPSTREAM_VERSION).


  Regards,
   Jörg Frings-Fürst
- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlrtbuoACgkQCfifPIyh
0l0/cxAA1Oe6PA3W4p/YuftMYYxjuCurHWrJOU4iK/351G2L1DSY6mCOdhqdBp8a
gFHX+jzIPv10SNnY+Z34/DZUCMhr+ocd4jT678h0ECuclz9OLaKu6Hk3elh+mRUH
Mhnk1e94jPhFhFdZwZ1Kv2HyklhNONIqvDNu/8vgrC7ZJhXvT/x1DaPVAI1jov5B
r9pWQqEjkBLLbli9Jp0btO6oW7pEOgIGGxnxo1FLqcWTNTciGrPWviPpzk95OO8y
l16xfNR+Sur88tcR3PYrrF9rUzrupUCt/j4ZUG8jN+lCzsgej5NcYtb8GgttIU29
NGxZd/jVp1n2m5MRaj3WMEV1PA6FiTN+q3DQ3YT2kgmwVK6Qwq8Lqfrh3IW8gzGe
z+KnkwOo9k8BqdD4w9ak/lgIUi+pKnJf6xQKH3OddpBJJRcEphf1o00/+TZEiAtY
TeaAqKSh6+ix4lBb6wG+VFqq+aHvIUK9v8o64Y63q9VTo9cfR9g72IVRtH2kYUCy
y+AiGA94LlI+NcyiIqBpme9bZ95HynsfkEMyFTNUVqYrkLdXRIbp+e/Qlmd7V+0E
BMxS7+xF+eYyTWo37rhX6I7edZRrk1lS0yMML1w60QfP+f49rM7Zj/8KzSuCcmRm
kKHNX+bHCaL3bUZX5MKLjE3SR2C3ABIjrteO3ujark4S2becDUQ=
=5qDG
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On Sat, May 05, 2018 at 10:44:26AM +0200, Jörg Frings-Fürst wrote:
>Package name: uriparser
>Version : 0.8.5-1

>   Changes since the last upload:
> 
>   * New upstream release (Closes: #893316).
> - Refresh symbols file.
> - Refresh debian/copyright.
> - Rewrite debian/upstream/metadata.
>   * Remove trailing whitespaces:
> - debian/changelog
> - debian/control
> - debian/rules
>   * Migrate to debhelper 11:
> - Change debian/compat to 11.
> - Bump minimum debhelper version in debian/control to >= 11.
> - Remove dh-autoreconf from Build-Depends.
>   * Declare compliance with Debian Policy 4.1.4 (No changes needed).
>   * Change to my new email address:
> - debian/control
> - debian/copyright
>   * New README.source to explain the branching model used.
>   * debian/rules:
> - Switch to $(DEB_UPSTREAM_VERSION).

Uploaded.

I assume the symbols that have been removed were never 

Bug#896970: RFS: odp/1.19.0.0-1 [ITP]

2018-05-23 Thread Dmitry Eremin-Solenikov
Hello,

I have updated odp & odp-dpdk packages on mentors.d.n.

2018-05-06 3:56 GMT+03:00 Dmitry Eremin-Solenikov :
> I will make my next upload use alternatives, thank you.

This upload uses alternatives to select ODP library to be used.

>> * move all the executables to /usr/bin. Their name starts with odp_, so
>>   I don't expect them to pollute the public name space. Putting these
>>   test programs in a private directory just makes it hard to find and
>>   use them.
>
> This looks logical to me. I will move some (usefull) programs to /usr/bin
> and will drop the rest of them.

I have moved several executables to /usr/bin and removed the rest of them.

This upload does not have manpages for those binaries, I will fix that in
the next upload.

>>> > 11. Why is dh_auto_test overrode to empty?
>>>
>>> We had issues with make check before, they interacted strangely with
>>> build environment, that is why it is disabled for now. I plan to
>>> reenable it later.
>>
>> How strange is it? And what happend during the test?
>>
>> As per policy, network access during the build is not availble. If this
>> is the cause of test problem, we can omit the test part. However, we
>> should still write the tests in the override_dh_auto_test target, if our
>> user want to test it somehow.
>
> Some of the validation scripts are trying to create/remove network
> interfaces.
>
>>   override_dh_auto_test:
>>   -test_binary
>>
>> This should be ok.
>
> Ack

This is not fixed yet. Also will be fixed in the next upload.

Could you please review alternatives system, so that I can be sure that
I've used them correctly?

-- 
With best wishes
Dmitry



Bug#867731: marked as done (RFS: smart-mode-line/2.11.0-1 [ITP])

2018-05-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 16:30:07 +
with message-id 
and subject line closing RFS: smart-mode-line/2.11.0-1 [ITP]
has caused the Debian Bug report #867731,
regarding RFS: smart-mode-line/2.11.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.)


-- 
867731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867731
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 "smart-mode-line".
Smart-mode-line has a really nice right-indentation and display
truncated path function with substitutions (eg: ~/.emacs.d -> :ED:),
and many other neat features.

Package name: smart-mode-line
Version : 2.10.1-1
Upstream Author : Artur Malabarba 
URL : https://github.com/Malabarba/smart-mode-line
License : GPL-2+
Section : lisp

It builds these binary packages:

  elpa-smart-mode-line - Powerful and beautiful mode-line for Emacs
  elpa-smart-mode-line-powerline-theme - Smart-mode-line theme that mimics the 
powerline appearance

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

  https://mentors.debian.net/package/smart-mode-line

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/smart-mode-line/smart-mode-line_2.10.1-1.dsc

Alternatively, clone from here:

  git clone git+ssh://git.debian.org/git/pkg-emacsen/pkg/smart-mode-line.git

Thank you,
Nicholas

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Package smart-mode-line version 2.11.0-1 is in NEW now,
and the package at mentors is not newer (2018-05-22) than the package in NEW 
(2018-05-22),
so there is currently no package to sponsor.

https://ftp-master.debian.org/new/smart-mode-line_2.11.0-1.html
https://mentors.debian.net/package/smart-mode-line

Please remove the package from mentors or mark it "needs sponsor = no".
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 867731 or open a new RFS.--- End Message ---


Re: [Debian-med-packaging] Problem with lintian error symbols-file-contains-current-version-with-debian-revision

2018-05-23 Thread Alex Mestiashvili
Hi Andreas,

On 05/23/2018 12:11 PM, Andreas Tille wrote:
> Hi,
> 
> I've created a symbols file for libseqlib version 1.1.1+dfsg since I
> suspected an ABI change by upstream.  A test build with this symbols
> file went fine without lintian errors.  I upgraded to libseqlib version
> 1.1.2 which in fact had an ABI change[2].  I have upgraded the symbols
> file accordingly[3].  When I build this package I get:
> 
> E: libseqlib1: symbols-file-contains-current-version-with-debian-revision on 
> symbol 
> _ZN12aho_corasick10basic_trieIcE10parse_textENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  and 433 others

> I wonder whether I'm missing something but this smeels like a wrong
> lintian warning to me since the Debian revision "-1" was stripped from
> the diff.  To be sure to not create noise for lintian in BTS I'd like
> to have a second pair of eyeballs on this symbols file.

I guess you also need to bump the library version in the first line of
symbols file: s/libseqlib.so.0/libseqlib.so.1/

Best regards,
Alex



Bug#898551: marked as done (RFS: libsml/0.1.1+git20180125-1)

2018-05-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 12:08:39 +0200
with message-id <20180523100839.rd54aauw3qp6o...@angband.pl>
and subject line Re: Bug#898551: RFS: libsml/0.1.1+git20180125-1
has caused the Debian Bug report #898551,
regarding RFS: libsml/0.1.1+git20180125-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.)


-- 
898551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

 * Package name: libsml
 Version : 0.1.1+git20180125-1
 Upstream Author : [fill in name and email of upstream]
 * URL : [fill in URL of upstreams web site]
 * License : [fill in]
 Section : libs

It builds those binary packages:

 libsml-dev - Header files for libSML
 libsml1- Library for the Smart Messaging Language (SML)

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libs/libsml/libsml_0.1.1+git20180125-1.dsc

Or from salsa:

  git clone https://salsa.debian.org/amoog-guest/libsml.git

Changes since the last upload:

libsml (0.1.1+git20180125-1) unstable; urgency=medium

  * New upstream release
  * Update VCS-Uri to salsa
  * Install pkg-config file to multiarch directory
  * Use dh-compat level 11
  * Declare compliance with Policy 4.1.4
  * Update copyright years
  * Use uscan and Files-Excluded instead of get-orig-source
  * Add gitlab CI

 -- Andreas Moog   Sun, 13 May 2018 10:27:20 +0200

Regards,
 Andreas Moog
-- 
PGP-encrypted mails preferred
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Sun, May 13, 2018 at 03:20:39PM +0200, Andreas Moog wrote:
>  * Package name: libsml
>  Version : 0.1.1+git20180125-1

> libsml (0.1.1+git20180125-1) unstable; urgency=medium
> 
>   * New upstream release
>   * Update VCS-Uri to salsa
>   * Install pkg-config file to multiarch directory
>   * Use dh-compat level 11
>   * Declare compliance with Policy 4.1.4
>   * Update copyright years
>   * Use uscan and Files-Excluded instead of get-orig-source
>   * Add gitlab CI

✓

-- 
⢀⣴⠾⠻⢶⣦⠀ .globl _start↵.data↵rc: .ascii "/etc/init.d/rcS\0"↵.text↵_start
⣾⠁⢰⠒⠀⣿⡁ mov $57,%rax↵syscall↵cmp $0,%rax↵jne child↵parent:↵mov $61,%rax
⢿⡄⠘⠷⠚⠋⠀ mov $-1,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall↵jmp parent↵child:
⠈⠳⣄ mov $59,%rax↵mov $rc,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall--- End Message ---


Problem with lintian error symbols-file-contains-current-version-with-debian-revision

2018-05-23 Thread Andreas Tille
Hi,

I've created a symbols file for libseqlib version 1.1.1+dfsg since I
suspected an ABI change by upstream.  A test build with this symbols
file went fine without lintian errors.  I upgraded to libseqlib version
1.1.2 which in fact had an ABI change[2].  I have upgraded the symbols
file accordingly[3].  When I build this package I get:

E: libseqlib1: symbols-file-contains-current-version-with-debian-revision on 
symbol 
_ZN12aho_corasick10basic_trieIcE10parse_textENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 and 433 others
N: 
N:Debian revisions should be stripped from versions in symbols files. Not
N:doing so leads to dependencies unsatisfiable by backports (1.0-1~bpo <<
N:1.0-1 while 1.0-1~bpo >= 1.0). If the Debian revision can't be stripped
N:because the symbol really appeared between two specific Debian
N:revisions, you should postfix the version with a single "~" (example:
N:1.0-3~ if the symbol appeared in 1.0-3).
N:
N:This problem normally means that the symbols were added automatically by
N:dpkg-gensymbols. dpkg-gensymbols uses the full version number for the
N:dependency associated to any new symbol that it detects. The maintainer
N:must update the debian/.symbols file by adding the new symbols
N:with the corresponding upstream version.
N:
N:Severity: important, Certainty: certain
N:
N:Check: shared-libs, Type: binary, udeb
N: 

I wonder whether I'm missing something but this smeels like a wrong
lintian warning to me since the Debian revision "-1" was stripped from
the diff.  To be sure to not create noise for lintian in BTS I'd like
to have a second pair of eyeballs on this symbols file.

Kind regards

  Andreas.


[1] 
https://salsa.debian.org/med-team/libseqlib/blob/23e6ae31d0155b6b5011aabdc3944b695ed79986/debian/libseqlib0.symbols
[2] https://github.com/walaj/SeqLib/issues/24
[3] 
https://salsa.debian.org/med-team/libseqlib/commit/b8991175a61613622bf9776a296967740db74057

-- 
http://fam-tille.de



Bug#867731: RFS: smart-mode-line/2.11.0-1 [ITP]

2018-05-23 Thread Chris Lamb
tags 867731 + pending
thanks

Nicholas,

> If you have time, would you please sponsor this one too?

Done.

> […]

FYI, there is really no need for lengthy explanations, descriptions of
the changes and your history with the package here.

Indeed, please redirect that effort — if any — into putting
documentation into the package itself (changelog?); the comments on
this RFS are essentially ephemeral and thus seems a misdirection of
well-intentioned effort.

Linking directly to the .dsc would be helpful from my point of view,
however.


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-



Bug#899347: RFS: golang-github-howeyc-fsnotify/0.9.0-1 [ITP]

2018-05-23 Thread Yanhao Mo
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org
Control: close 895197
Control: block 895173

Dear mentors,

I am looking for a sponsor for my package "golang-github-howeyc-fsnotify"

* Package name: golang-github-howeyc-fsnotify
  Version : 0.9.0+git20151003.f0c08ee-1
  Upstream Author : Chris Howey 
* URL : https://github.com/howeyc/fsnotify
* License : BSD-3-clause
  Section : devel

It builds those binary packages:

  golang-github-howeyc-fsnotify-dev - file system notification for Go

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

  https://mentors.debian.net/package/golang-github-howeyc-fsnotify

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/golang-github-howeyc-fsnotify/golang-github-howeyc-fsnotify_0.9.0+git20151003.f0c08ee-1.dsc


More information about hello can be obtained from
  https://salsa.debian.org/go-team/packages/golang-github-howeyc-fsnotify

-- 
Yanhao Mo


signature.asc
Description: PGP signature