Bug#900456: RFS: libtoxcore/0.2.2-1

2018-05-30 Thread Yangfl
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: libtoxcore
   Version : 0.2.2-1
   Upstream Author : Tox Project
 * URL : https://tox.chat
 * License : GPL-3+
   Section : libs

It builds those binary packages:

 libtoxcore-dev - Distributed, secure messenger - development headers
 libtoxcore2 - Distributed, secure messenger

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

https://salsa.debian.org/yangfl-guest/c-toxcore


Changes since the last upload:

  * New upstream release
  * Fix FTBFS on hurd-i386
  * Disable buggy autotest


Regards,
 Yangfl



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

2018-05-30 Thread Yanhao Mo
On Thu 05/31 11:05, Nobuhiro Iwamatsu wrote:
> Hi,
> 
> I uploaded, it's in NEW queue.
> 
> Best regards,
>   Nobuhiro

Thanks a lot ~

-- 
Yanhao Mo


signature.asc
Description: PGP signature


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

2018-05-30 Thread Nobuhiro Iwamatsu
Hi,

I uploaded, it's in NEW queue.

Best regards,
  Nobuhiro

2018-05-23 15:03 GMT+09:00 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
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6



Bug#900453: RFS: deepin-notifications/3.3.1-1

2018-05-30 Thread Yanhao Mo
Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "deepin-notifications"

 * Package name: deepin-notifications
   Version : 3.3.1-1
   Upstream Author : Deepin Technology Co., Ltd.
 * URL : https://github.com/linuxdeepin/deepin-notifications
 * License : GPL-3+
   Section : x11

  It builds those binary packages:

deepin-notifications - System notifications for Deepin Desktop Environment

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

  https://mentors.debian.net/package/deepin-notifications


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/deepin-notifications/deepin-notifications_3.3.1-1.dsc

  More information about hello can be obtained from 
https://salsa.debian.org/pkg-deepin-team/deepin-notifications

  Changes since the last upload:

deepin-notifications (3.3.1-1) unstable; urgency=medium

  * New upstream version 3.3.1

 -- Yanhao Mo   Thu, 31 May 2018 08:15:26 +0800

-- 
Yanhao Mo


signature.asc
Description: PGP signature


Bug#888859: RFS: iolang/2017.09.06+dfsg-1 [ITP]

2018-05-30 Thread Lumin
control: tags -1 +morefino

On Fri, Feb 23, 2018 at 12:05:41AM +0800, Yangfl wrote:
> 
> d/copyright should have provided a list of removed files (see Files-Excluded).
>
> By the way, I have made a PR to upstream to remove ConvertUTF and it
> has accepted. The next release will not affected by this.

Sounds good.

> Added deps on libjs-jquery. Source of jquery.js is now provided.
> 
> Also move Flux resource files to /usr/share/ .

As discussed previously, there are several issues remained to be solved
before the next round of review:

1. A packaging repo. This is a complicated package, with a proper
   packaging repo it will be easier to track the changes.

2. Add the upstream correctness tests to the dh_auto_test target.
   I believe this is necessary because it's a language package. Any
   unit test failure may trigger unexpected potential problems.

3. Your effort is appreciated. However, as previously discussed, you
   should make sure whether you would be interested in this package
   for a while. As you said, you don't quite use this package.
   I guess it's hard for one to keep interest on a package he/she
   doesn't care about.

thanks.



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

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

Thank for your review.

2018-05-25 9:31 GMT+03:00 Lumin :
> On Wed, May 23, 2018 at 07:50:57PM +0300, Dmitry Eremin-Solenikov wrote:
>> Hello,
>>
>> I have updated odp & odp-dpdk packages on mentors.d.n.
>
> Please file another RFS bug for the odp-dpdk package since it is a
> different source.

Sure, filled #900407.

>> 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.
>
> The package is going in the right way, but the alternatives still needs
> to be improved.

Thanks. I've updated -dev packages to also use alternatives.

> Nitpickings about the updated package:
>
> 1. README.Debian
>"Library packages should contain libodp-linux.so.FOO"
>It should be "libodp-linux.so.SOVER", which is more precise.

Hmm. I have checked buster package lists. Only blas/lapack packages
use soname as virtual package name in provides. The rest of packages
use libsomethingSOVER. Wouldn't it be logical to stick to convention
used by the rest of packages?

> 2. command `dot` comes from graphviz, but it is missing from B-D.

Ack, fixed.

>
> 3. libodp-generic119 should provide libodp-linux.so.119 instead of
>libodp-linux119. And applications that need libodp-linux.so.119
>could declare Depends: libodp-linux.so.119 | libodp-generic119 .
>
>This is similar to libblas.so.3 | libblas3 setting of the BLAS
>implementations.

See above.


> 4. libodp-generic-dev should Privides: libodp-linux.so .
>odp-generic/libodp-linux.so should be registered in the alternatives
>system to provide a /usr/lib/DEB_HOST_MULTIARCH/libodp-linux.so .
>
>The static library /usr/lib/x86_64-linux-gnu/libodp-linux.a should
>be put to the /.../odp-generic directory, and be registered as a slave
>of the libodp-linux.so alternative.
>
>I also noticed that the symlink points to an invalid path.
>Please solve this issue by the alternatives system as said above.
>
>root@bfb95763d3d6 ~/odp-1.19.0.1# ll 
> /usr/lib/x86_64-linux-gnu/libodp-linux.so
>lrwxrwxrwx 1 root root 23 May 23 16:01 
> /usr/lib/x86_64-linux-gnu/libodp-linux.so -> libodp-linux.so.119.0.1
>
> libblas3 and libopenblas-base and their corresponding -dev packages are
> good examples at this point. If you have doubts, you can carefully
> examine these packages which may possibly provide help.

I have fixed alternatives usage for -dev packages (and removed Conflicts
entry in d/contron and README.Debian files).

> Please ping me if you have question, or ready for the next round of
> review :-)

New packages are uploaded to mentors.d.n. Hopefully with this upload
I will have just two remaining issues:
 - manpages
 - dh_auto_test override.

I plan to look onto adding package autotests afterwards.

-- 
With best wishes
Dmitry



Bug#896970: marked as done (RFS: odp/1.19.0.1-1 [ITP])

2018-05-30 Thread Debian Bug Tracking System
Your message dated Wed, 30 May 2018 10:33:13 +
with message-id 
and subject line closing RFS: odp/1.19.0.1-1 [ITP]
has caused the Debian Bug report #896970,
regarding RFS: odp/1.19.0.1-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.)


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


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

 * Package name: odp
   Version : 1.19.0.0-1
   Upstream Author : Linaro / ODP community
 * URL : https://www.opendataplane.org/
 * License : [fill in]
   Section : libs

  It builds those binary packages:

 libodp-common-dev - OpenDataPlane library (common development files)
 libodp-generic-dev - OpenDataPlane reference implementation library 
(development)
 libodp-generic119 - OpenDataPlane reference implementation library (runtime)
 libodphelper-dev - OpenDataPlane helper library (development)
 libodphelper119 - OpenDataPlane helper library (runtime)
 odp-doc- OpenDataPlane library (documentation)
 odp-linux-examples - OpenDataPlane examples

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/o/odp/odp_1.19.0.0-1.dsc

  More information about odp can be obtained from
  https://www.opendataplane.org.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Package odp has been removed from mentors.--- End Message ---


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

2018-05-30 Thread Dmitry Eremin-Solenikov
Package: sponsorship-requests
Severity: normal
Control: block -1 by 896970
Control: block 899383 by -1

Dear mentors,

I am looking for a sponsor for my package "odp-dpdk"

 * Package name: odp-dpdk
   Version : 1.19.0.0-1
   Upstream Author : Linaro / ODP community
 * URL : https://www.opendataplane.org/
 * License : BSD-3-Clause
   Section : libs

It builds those binary packages:

  libodp-dpdk-dev - OpenDataPlane DPDK faceplate library (development)
  libodp-dpdk119 - OpenDataPlane DPDK faceplate library (runtime)

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

https://mentors.debian.net/package/odp-dpdk


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

  dget -x 
https://mentors.debian.net/debian/pool/main/o/odp-dpdk/odp-dpdk_1.19.0.0-1.dsc

More information about hello can be obtained from https://www.opendataplane.org.
These packages provide hardware-optimized implementation of ODP API
(using DPDK as a backend).

-- 
With best wishes
Dmitry Eremin-Solenikov

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Re: VCS repositories

2018-05-30 Thread Warlich, Christof
Dear Gregor, dear Russ,

many thanks for your help, that's even much better than the information I was 
hoping for :-). Particularly the sources API and dgit are real gems that I 
would probably not have found myself.

Cheers,

Chris