Bug#1068495: marked as done (sponsorship-requests: RFS: tack/1.09+20230201-1 [RC] -- terminfo action checker)

[Debian Bug Tracking System]

Your message dated Sat, 6 Apr 2024 14:41:26 +0200
with message-id 
and subject line Re: sponsorship-requests: RFS: tack/1.09+20230201-1 [RC] -- 
terminfo action checker
has caused the Debian Bug report #1068495,
regarding sponsorship-requests: RFS: tack/1.09+20230201-1 [RC] -- terminfo 
action checker
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.)


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

 * Package name : tack
   Version  : 1.09+20230201-1
   Upstream contact : Thomas Dickey 
 * URL  : https://invisible-island.net/ncurses/tack.html
 * License  : GPL-2+
 * Vcs  : https://salsa.debian.org/joachim-guest/tack
   Section  : misc

The source builds the following binary packages:

  tack - terminfo action checker

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/t/tack/tack_1.09+20230201-1.dsc

Changes since the last upload:

 tack (1.09+20230201-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure copyright file specification URI.
   * Bump debhelper from old 10 to 13.
   * Set debhelper-compat version in Build-Depends.
   * Fix field name case in debian/copyright (Upstream-name => Upstream-Name).
   * Use canonical URL in Vcs-Browser.
   * Fix field name case in debian/copyright (Upstream-contact ⇒
 Upstream-Contact).
 .
   [ Sven Joachim ]
   * New upstream snapshot.
 - Fixes FTBFS with -Werror=implicit-function-declaration
   (Closes: #1066469).
   * Update debian/watch to version 4, and look for tarballs on
 https://invisible-mirror.net.
   * Add a debian/watch.snapshot file for checking/downloading snapshots
 with uscan.
   * Update debian/upstream/signing-key.asc.
 - Add new key 19882D92DDA4C400C22C0D56CC2AF4472167BE03.
 - Drop old SHA1 key C52048C0C0748FEE.
   * Build-depend on libncurses-dev rather than on libncurses5-dev.
   * Bump Standards-Version to 4.6.2, no changes needed.
   * Update debian/copyright.
   * Add a debian/salsa-ci.yml file for the Salsa CI pipeline.
 - Disable the arm64 crossbuild job, not supported.


Some additional notes: the latest stable upstream release (1.09) of tack
is already over four years old and does not contain a fix for the FTBFS
bug #1066469.  I have asked for a 1.10 release, but since that has not
come forth yet, I decided to package the latest snapshot instead.  There
a no reverse dependencies and very few users, so the risk should be low.

I have not yet finalized debian/changelog and tagged a release on Salsa
to prevent confusion in case additional modifications are needed.  Will
do that once the package is accepted in the archive.

Cheers,
   Sven


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

Uploaded. Thanks!--- End Message ---

Bug#1068495: sponsorship-requests: RFS: tack/1.09+20230201-1 [RC] -- terminfo action checker

[Sven Joachim]

Package: sponsorship-requests
Severity: important


Dear mentors,

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

 * Package name : tack
   Version  : 1.09+20230201-1
   Upstream contact : Thomas Dickey 
 * URL  : https://invisible-island.net/ncurses/tack.html
 * License  : GPL-2+
 * Vcs  : https://salsa.debian.org/joachim-guest/tack
   Section  : misc

The source builds the following binary packages:

  tack - terminfo action checker

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/t/tack/tack_1.09+20230201-1.dsc

Changes since the last upload:

 tack (1.09+20230201-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure copyright file specification URI.
   * Bump debhelper from old 10 to 13.
   * Set debhelper-compat version in Build-Depends.
   * Fix field name case in debian/copyright (Upstream-name => Upstream-Name).
   * Use canonical URL in Vcs-Browser.
   * Fix field name case in debian/copyright (Upstream-contact ⇒
 Upstream-Contact).
 .
   [ Sven Joachim ]
   * New upstream snapshot.
 - Fixes FTBFS with -Werror=implicit-function-declaration
   (Closes: #1066469).
   * Update debian/watch to version 4, and look for tarballs on
 https://invisible-mirror.net.
   * Add a debian/watch.snapshot file for checking/downloading snapshots
 with uscan.
   * Update debian/upstream/signing-key.asc.
 - Add new key 19882D92DDA4C400C22C0D56CC2AF4472167BE03.
 - Drop old SHA1 key C52048C0C0748FEE.
   * Build-depend on libncurses-dev rather than on libncurses5-dev.
   * Bump Standards-Version to 4.6.2, no changes needed.
   * Update debian/copyright.
   * Add a debian/salsa-ci.yml file for the Salsa CI pipeline.
 - Disable the arm64 crossbuild job, not supported.


Some additional notes: the latest stable upstream release (1.09) of tack
is already over four years old and does not contain a fix for the FTBFS
bug #1066469.  I have asked for a 1.10 release, but since that has not
come forth yet, I decided to package the latest snapshot instead.  There
a no reverse dependencies and very few users, so the risk should be low.

I have not yet finalized debian/changelog and tagged a release on Salsa
to prevent confusion in case additional modifications are needed.  Will
do that once the package is accepted in the archive.

Cheers,
   Sven


signature.asc
Description: PGP signature

Bug#1058066: sponsorship-requests: Request sponsored upload for mini-httpd_1.30-6

[Alexandru Mihail]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "mini-httpd":

 * Package name : mini-httpd
   Version  : 1.30-6
   Upstream contact : Jef Poskanzer j...@mail.acme.com
 * URL  : https://www.acme.com/software/mini_httpd/
 * License  : BSD-2-clause
 * Vcs  : https://salsa.debian.org/debian/mini-httpd.git

The source builds the following binary packages:

  mini-httpd_1.30-6_arch.deb

For more information please see
https://salsa.debian.org/debian/mini-httpd.git
and 
https://salsa.debian.org/debian/mini-httpd/-/tags/debian%2F1.30-6


Changes since the last upload:

mini-httpd (1.30-6) unstable; urgency=medium

  * Modified 0003-fix-change-index-document-root and
0005-cgi-php to push index.mini-httpd.html to the end of known
index.* array, modified install script to copy the provided 
index.html into /var/www/html/index.html,
if not present (Closes: #1057842)
  * Moved package provided index.html file to
/usr/share/doc/mini-httpd/examples, to avoid lintian warning  
regarding doc location


Regards,
Alexandru Mihail
mini-httpd maintainer



signature.asc
Description: This is a digitally signed message part

Bug#1057332: sponsorship-requests: Bottom/0.9.6 -- A customizable cross-platform graphical process/system monitor for the terminal

[Robin Gustafsson]

Hi Douglas,

On 12/3/23 16:29, Douglas Baggett wrote:

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: doug.bagg...@gmail.com

This package `bottom` is **REALLY NICE**.

https://github.com/ClementTsang/bottom

The author has packages for debian already made from nightlys. It should
be easy to include them.

thanks!


Sounds like you may want a "Request for Package" (RFP) [1] instead.

The upstream's .deb files are not sufficient for inclusion in Debian. A 
Debian source package [2,3] is needed.


[1] https://wiki.debian.org/RFP
[2] https://www.debian.org/doc/debian-policy/ch-source.html
[3] https://wiki.debian.org/Packaging/SourcePackage

--
Regards,
Robin

GPG: B26C 2ED3 7324 6221 9C3D 1DFE 293A 3C91 D188 369C


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1057332: sponsorship-requests: Bottom/0.9.6 -- A customizable cross-platform graphical process/system monitor for the terminal

[Douglas Baggett]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: doug.bagg...@gmail.com

This package `bottom` is **REALLY NICE**. 

https://github.com/ClementTsang/bottom

The author has packages for debian already made from nightlys. It should
be easy to include them.

thanks!

Bug#1052364: marked as done (sponsorship-requests: Request sponsored upload for mini-httpd_1.30-5)

[Debian Bug Tracking System]

Your message dated Sun, 24 Sep 2023 22:55:25 +0200
with message-id 
and subject line Re: sponsorship-requests: Request sponsored upload for 
mini-httpd_1.30-5
has caused the Debian Bug report #1052364,
regarding sponsorship-requests: Request sponsored upload for mini-httpd_1.30-5
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.)


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

Hello Nicholas,
Requesting a sponsored upload for a new version of mini-httpd (mini-
httpd_1.30-5), fixing https://bugs.debian.org/491078 and
https://bugs.debian.org/1051374 (Serious).

https://salsa.debian.org/debian/mini-httpd/-/tags/debian%2F1.30-5

Thanks and have a tremendous day,
Alexandru Mihail




signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---

Johannes Schauer Marin Rodrigues uploaded this some days ago.--- End Message ---

Bug#1052364: sponsorship-requests: Request sponsored upload for mini-httpd_1.30-5

[Alexandru Mihail]

Package: sponsorship-requests
Severity: normal

Hello Nicholas,
Requesting a sponsored upload for a new version of mini-httpd (mini-
httpd_1.30-5), fixing https://bugs.debian.org/491078 and
https://bugs.debian.org/1051374 (Serious).

https://salsa.debian.org/debian/mini-httpd/-/tags/debian%2F1.30-5

Thanks and have a tremendous day,
Alexandru Mihail




signature.asc
Description: This is a digitally signed message part

Bug#1051453: sponsorship-requests: Screensaver for UKUI desktop environment.

[liudun]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: liudun@qq.com

Dear mentors,

I am looking for a sponsor for my package "ukui-screensaver":

 * Package name : ukui-screensaver
   Version  : 4.0.0.0-1
   Upstream contact : liu...@kylinos.cn
 * URL  : https://gitee.com/openkylin/ukui-screensaver
 * License  : GPL-3+
 * Vcs  : https://gitee.com/openkylin/ukui-screensaver
   Section  : x11

The source builds the following binary packages:

  ukui-screensaver - Screensaver for UKUI desktop environment

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

  https://mentors.debian.net/package/ukui-screensaver/

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

  dget -x https://mentors.debian.net/debian/pool/main/u/ukui-screensaver/ukui-
screensaver_4.0.0.0-1.dsc

Changes since the last upload:

 ukui-screensaver (4.0.0.0-1) unstable; urgency=medium
 .
   * New upstream release.

Regards

Bug#1051451: sponsorship-requests: Lightdm greeter for UKUI

[liudun]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: liudun@qq.com

Dear mentors,

I am looking for a sponsor for my package "ukui-greeter":

 * Package name : ukui-greeter
   Version  : 4.0.0.0-1
   Upstream contact : yangmin 
 * URL  : https://gitee.com/openkylin/ukui-greeter
 * License  : GPL-2+, GPL-3, GPL-3+
 * Vcs  : https://gitee.com/openkylin/ukui-greeter
   Section  : x11

The source builds the following binary packages:

  ukui-greeter - Lightdm greeter for UKUI

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

  https://mentors.debian.net/package/ukui-greeter/

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

  dget -x https://mentors.debian.net/debian/pool/main/u/ukui-greeter/ukui-
greeter_4.0.0.0-1.dsc

Changes since the last upload:

 ukui-greeter (4.0.0.0-1) unstable; urgency=medium
 .
   * New upstream release.

Regards

Bug#1051397: sponsorship-requests: UKUI authentication agent for PolicyKit-1.

[liudun]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: liudun@qq.com

Dear mentors,

I am looking for a sponsor for my package "ukui-biometric-auth":

 * Package name : ukui-biometric-auth
   Version  : 4.0.0.0-1
   Upstream contact : yangmin 
 * URL  : https://gitee.com/openkylin/ukui-biometric-auth
 * License  : GPL-3+
 * Vcs  : https://gitee.com/openkylin/ukui-biometric-auth
   Section  : admin

The source builds the following binary packages:

  libpam-biometric - Insertable authentication module for PAM
  ukui-polkit - UKUI authentication agent for PolicyKit-1

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

  https://mentors.debian.net/package/ukui-biometric-auth/

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

  dget -x https://mentors.debian.net/debian/pool/main/u/ukui-biometric-
auth/ukui-biometric-auth_4.0.0.0-1.dsc

Changes since the last upload:

 ukui-biometric-auth (4.0.0.0-1) unstable; urgency=medium
 .
   * New upstream release.

Regards

Bug#1051396: sponsorship-requests: UKUI interface provides the interface for system configuration and related libraries.

[liudun]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: liudun@qq.com

Dear mentors,

I am looking for a sponsor for my package "ukui-interface":

 * Package name : ukui-interface
   Version  : 4.0.0.0-1
   Upstream contact : liuhao 
 * URL  : https://gitee.com/openkylin/ukui-interface
 * License  : Apache-2.0, GPL-3+
 * Vcs  : https://gitee.com/openkylin/ukui-interface
   Section  : libs

The source builds the following binary packages:

  libukui-log4qt0 - transitional package
  libukui-log4qt1 - log4qt module
  libukui-log4qt-dev - log4qt interface
  libukui-common0 - common module
  libukui-common-dev - common interface

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

  https://mentors.debian.net/package/ukui-interface/

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

  dget -x https://mentors.debian.net/debian/pool/main/u/ukui-interface/ukui-
interface_4.0.0.0-1.dsc

Changes since the last upload:

 ukui-interface (4.0.0.0-1) unstable; urgency=medium
 .
   * New upstream release.

Regards

Bug#1051381: sponsorship-requests: UKUI interface provides the interface for system configuretion and related libraries.

[Bo YU]

On Thu, Sep 7, 2023 at 2:00 PM liudun  wrote:
>
> Package: sponsorship-requests
> Severity: wishlist
> X-Debbugs-Cc: liudun@qq.com
>
> Version:4.0.0.0-1 (View RFS template)
> Uploaded:   2023-09-07 05:52
> Source package: ukui-interface_4.0.0.0-1.dsc
> Distribution:   unstable
> Section:libs
> Priority:   optional
> Homepage:   https://gitee.com/openkylin/ukui-interface
> Vcs-Browser:https://gitee.com/openkylin/ukui-interface
> Vcs-Git:https://gitee.com/openkylin/ukui-interface.git
>

This is not right RFS template, Please paste txt from your mentor.
hint: click `View RFS template`.

BR,
Bo

Bug#1051381: sponsorship-requests: UKUI interface provides the interface for system configuretion and related libraries.

[liudun]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: liudun@qq.com

Version:4.0.0.0-1 (View RFS template)
Uploaded:   2023-09-07 05:52
Source package: ukui-interface_4.0.0.0-1.dsc
Distribution:   unstable
Section:libs
Priority:   optional
Homepage:   https://gitee.com/openkylin/ukui-interface
Vcs-Browser:https://gitee.com/openkylin/ukui-interface
Vcs-Git:https://gitee.com/openkylin/ukui-interface.git

Bug#1051255: sponsorship-requests: Kylin system layer developer kit

[xibowen]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "libkysdk-system":

 * Package name : libkysdk-system
   Version  : 2.2.3.5-1
   Upstream contact : Zhikai Chen 
 * URL  : https://gitee.com/openkylin/libkysdk-system
 * License  : LGPL-2.1 or LGPL-3, LGPL-3+, Expat
 * Vcs  : https://gitee.com/openkylin/libkysdk-system
   Section  : libs

The source builds the following binary packages:

  libkysdk-system - Kylin System Layer Developer Kit
  libkysdk-system-dev - Kylin System Layer Developer Kit - Development Library

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

  https://mentors.debian.net/package/libkysdk-system/

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

  dget -x https://mentors.debian.net/debian/pool/main/libk/libkysdk-
system/libkysdk-system_2.2.3.5-1.dsc

Changes for the initial release:

 libkysdk-system (2.2.3.5-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1031340)

We have uploaded the latest package witch is different from ITP version.

Regards,
--
  xibowen

Bug#1049996: sponsorship-requests: update libkysdk-base version, and upload the package to unstable

[xibowen]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "libkysdk-base":

 * Package name : libkysdk-base
   Version  : 2.2.0.0-1
   Upstream contact : Zhikai Chen 
 * URL  : https://gitee.com/openkylin/libkysdk-base
 * License  : LGPL-3
 * Vcs  : https://gitee.com/openkylin/libkysdk-base
   Section  : libs

The source builds the following binary packages:

  libkysdk-base - Kylin SDK basic library
  libkysdk-base-dev - development files for libkysdk-base
  libkysdk-timer - C style timer module
  libkysdk-timer-dev - development files for libkysdk-timer
  libkysdk-config - configuration file module
  libkysdk-config-dev - development files for libkysdk-config
  libkysdk-log - C style log module
  libkysdk-log-dev - development files for libkysdk-log
  libkysdk-utils - Basic tool function module
  libkysdk-utils-dev - development files for libkysdk-utils
  libkysdk-gsetting - gsetting configuration module
  libkysdk-gsetting-dev - gsetting configuration module, development package

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

  https://mentors.debian.net/package/libkysdk-base/

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

  dget -x https://mentors.debian.net/debian/pool/main/libk/libkysdk-
base/libkysdk-base_2.2.0.0-1.dsc

Changes since the last upload:

 libkysdk-base (2.2.0.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Upload to unstable.

Regards,
--
  xibowen

Bug#1049324: sponsorship-requests: Ukui time app widget for ukui desktop environment.Need a sponsor for this package

[xibowen]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "ukui-system-appwidget":

 * Package name : ukui-system-appwidget
   Version  : 4.0.0.1-1
   Upstream contact : wangyan 
 * URL  : https://gitee.com/openkylin/ukui-system-appwidget
 * License  : GPL-3+
 * Vcs  : https://gitee.com/openkylin/ukui-system-appwidget
   Section  : admin

The source builds the following binary packages:

  ukui-system-appwidget - ukui time app widget

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

  https://mentors.debian.net/package/ukui-system-appwidget/

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

  dget -x https://mentors.debian.net/debian/pool/main/u/ukui-system-
appwidget/ukui-system-appwidget_4.0.0.1-1.dsc

Changes for the initial release:

 ukui-system-appwidget (4.0.0.1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1043001)

Regards,
--
  xibowen

Bug#1041595: marked as done (sponsorship-requests: kylin SDK based on application level)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 01:34:32 +0200
with message-id <4f5f7eca-301b-bf3d-8b18-1d41d558e...@debian.org>
and subject line Re: sponsorship-requests: kylin SDK based on application level
has caused the Debian Bug report #1041595,
regarding sponsorship-requests: kylin SDK based on application level
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.)


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

 * Package name : libkysdk-applications
   Version  : 1.0.1-1
   Upstream contact : Zhen Sun 
 * URL  : https://gitee.com/openkylin/libkysdk-applications
 * License  : BSD-3-clause, LGPL-3, GPL-3
 * Vcs  : https://gitee.com/openkylin/libkysdk-applications
   Section  : libs

The source builds the following binary packages:

  libkysdk-applications - kylin SDK based on application level
  libkysdk-applications-dev - development for libkysdk-applications
  libkysdk-qtwidgets1 - add-on widgets and classes for Qt applications
  libkysdk-qtwidgets-dev - development files for libkysdk-qtwidgets
  libkysdk-widgetutils1 - window display control moudule
  libkysdk-widgetutils-dev - development files for libkysdk-widgetutils
  libkysdk-kabase1 - additional interface on application level
  libkysdk-kabase-dev - development files for libkysdk-kabase
  libkysdk-waylandhelper1 - Window management interface
  libkysdk-waylandhelper-dev - development files for libkysdk-waylandhelper
  libkysdk-alm1 - Application process management module
  libkysdk-alm-dev - development files for libkysdk-ukenv
  libkysdk-ukenv1 - Kylin system environment interface
  libkysdk-ukenv-dev - development files for libkysdk-ukenv modal
  libkysdk-notification1 - Kylin system notification interface
  libkysdk-notification-dev - development files for libkysdk-notification modal

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

  https://mentors.debian.net/package/libkysdk-applications/

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

  dget -x https://mentors.debian.net/debian/pool/main/libk/libkysdk-
applications/libkysdk-applications_1.0.1-1.dsc

Changes for the initial release:

 libkysdk-applications (1.0.1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1031661)

Regards,
--
  xibowen
--- End Message ---
--- Begin Message ---

This was already sent as #1041594.--- End Message ---

Bug#1041595: sponsorship-requests: kylin SDK based on application level

[xibowen]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "libkysdk-applications":

 * Package name : libkysdk-applications
   Version  : 1.0.1-1
   Upstream contact : Zhen Sun 
 * URL  : https://gitee.com/openkylin/libkysdk-applications
 * License  : BSD-3-clause, LGPL-3, GPL-3
 * Vcs  : https://gitee.com/openkylin/libkysdk-applications
   Section  : libs

The source builds the following binary packages:

  libkysdk-applications - kylin SDK based on application level
  libkysdk-applications-dev - development for libkysdk-applications
  libkysdk-qtwidgets1 - add-on widgets and classes for Qt applications
  libkysdk-qtwidgets-dev - development files for libkysdk-qtwidgets
  libkysdk-widgetutils1 - window display control moudule
  libkysdk-widgetutils-dev - development files for libkysdk-widgetutils
  libkysdk-kabase1 - additional interface on application level
  libkysdk-kabase-dev - development files for libkysdk-kabase
  libkysdk-waylandhelper1 - Window management interface
  libkysdk-waylandhelper-dev - development files for libkysdk-waylandhelper
  libkysdk-alm1 - Application process management module
  libkysdk-alm-dev - development files for libkysdk-ukenv
  libkysdk-ukenv1 - Kylin system environment interface
  libkysdk-ukenv-dev - development files for libkysdk-ukenv modal
  libkysdk-notification1 - Kylin system notification interface
  libkysdk-notification-dev - development files for libkysdk-notification modal

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

  https://mentors.debian.net/package/libkysdk-applications/

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

  dget -x https://mentors.debian.net/debian/pool/main/libk/libkysdk-
applications/libkysdk-applications_1.0.1-1.dsc

Changes for the initial release:

 libkysdk-applications (1.0.1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1031661)

Regards,
--
  xibowen

Bug#1041594: sponsorship-requests: kylin SDK based on application level

[xibowen]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "libkysdk-applications":

 * Package name : libkysdk-applications
   Version  : 1.0.1-1
   Upstream contact : Zhen Sun 
 * URL  : https://gitee.com/openkylin/libkysdk-applications
 * License  : BSD-3-clause, LGPL-3, GPL-3
 * Vcs  : https://gitee.com/openkylin/libkysdk-applications
   Section  : libs

The source builds the following binary packages:

  libkysdk-applications - kylin SDK based on application level
  libkysdk-applications-dev - development for libkysdk-applications
  libkysdk-qtwidgets1 - add-on widgets and classes for Qt applications
  libkysdk-qtwidgets-dev - development files for libkysdk-qtwidgets
  libkysdk-widgetutils1 - window display control moudule
  libkysdk-widgetutils-dev - development files for libkysdk-widgetutils
  libkysdk-kabase1 - additional interface on application level
  libkysdk-kabase-dev - development files for libkysdk-kabase
  libkysdk-waylandhelper1 - Window management interface
  libkysdk-waylandhelper-dev - development files for libkysdk-waylandhelper
  libkysdk-alm1 - Application process management module
  libkysdk-alm-dev - development files for libkysdk-ukenv
  libkysdk-ukenv1 - Kylin system environment interface
  libkysdk-ukenv-dev - development files for libkysdk-ukenv modal
  libkysdk-notification1 - Kylin system notification interface
  libkysdk-notification-dev - development files for libkysdk-notification modal

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

  https://mentors.debian.net/package/libkysdk-applications/

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

  dget -x https://mentors.debian.net/debian/pool/main/libk/libkysdk-
applications/libkysdk-applications_1.0.1-1.dsc

Changes for the initial release:

 libkysdk-applications (1.0.1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1031661)

Regards,
--
  xibowen

Bug#1031683: marked as done (sponsorship-requests: The package is lacked for ukui desktop)

[Debian Bug Tracking System]

Your message dated Tue, 21 Feb 2023 10:39:29 +0800
with message-id <1a3vudwdnm3-1a3x4bpspfw@nsmail7.0.0--kylin--1>
and subject line repeat bug
has caused the Debian Bug report #1031683,
regarding sponsorship-requests: The package is lacked for ukui desktop
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.)


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

 * Package name : libkysdk-applications
   Version  : 1.0.1-1
   Upstream contact : Zhen Sun 
 * URL  : https://gitee.com/openkylin/libkysdk-applications
 * License  : LGPL-3, GPL-3, BSD-3-clause
 * Vcs  : https://gitee.com/openkylin/libkysdk-applications
   Section  : libs

The source builds the following binary packages:

  libkysdk-applications - kylin SDK based on application level
  libkysdk-applications-dev - development for libkysdk-applications
  libkysdk-qtwidgets-dev - development files for libkysdk-qtwidgets
  libkysdk-qtwidgets - add-on widgets and classes for Qt applications
  libkysdk-widgetutils-dev - development files for libkysdk-widgetutils
  libkysdk-widgetutils - window display control moudule
  libkysdk-kabase - additional interface on application level
  libkysdk-kabase-dev - development files for libkysdk-kabase
  libkysdk-waylandhelper-dev - development files for libkysdk-waylandhelper
  libkysdk-waylandhelper - Window management interface
  libkysdk-alm - Application process management module
  libkysdk-alm-dev - development files for libkysdk-ukenv
  libkysdk-ukenv - Kylin system environment interface
  libkysdk-ukenv-dev - development files for libkysdk-ukenv modal

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

  https://mentors.debian.net/package/libkysdk-applications/

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

  dget -x https://mentors.debian.net/debian/pool/main/libk/libkysdk-
applications/libkysdk-applications_1.0.1-1.dsc

Changes for the initial release:

 libkysdk-applications (1.0.1-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #1031661)
--- End Message ---
--- Begin Message ---
repeat bug

 --- End Message ---

Bug#1031683: sponsorship-requests: The package is lacked for ukui desktop

[xibowen]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "libkysdk-applications":

 * Package name : libkysdk-applications
   Version  : 1.0.1-1
   Upstream contact : Zhen Sun 
 * URL  : https://gitee.com/openkylin/libkysdk-applications
 * License  : LGPL-3, GPL-3, BSD-3-clause
 * Vcs  : https://gitee.com/openkylin/libkysdk-applications
   Section  : libs

The source builds the following binary packages:

  libkysdk-applications - kylin SDK based on application level
  libkysdk-applications-dev - development for libkysdk-applications
  libkysdk-qtwidgets-dev - development files for libkysdk-qtwidgets
  libkysdk-qtwidgets - add-on widgets and classes for Qt applications
  libkysdk-widgetutils-dev - development files for libkysdk-widgetutils
  libkysdk-widgetutils - window display control moudule
  libkysdk-kabase - additional interface on application level
  libkysdk-kabase-dev - development files for libkysdk-kabase
  libkysdk-waylandhelper-dev - development files for libkysdk-waylandhelper
  libkysdk-waylandhelper - Window management interface
  libkysdk-alm - Application process management module
  libkysdk-alm-dev - development files for libkysdk-ukenv
  libkysdk-ukenv - Kylin system environment interface
  libkysdk-ukenv-dev - development files for libkysdk-ukenv modal

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

  https://mentors.debian.net/package/libkysdk-applications/

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

  dget -x https://mentors.debian.net/debian/pool/main/libk/libkysdk-
applications/libkysdk-applications_1.0.1-1.dsc

Changes for the initial release:

 libkysdk-applications (1.0.1-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #1031661)

Bug#1002295: marked as done (sponsorship-requests: multi-timer -- Set of countdown timers with alarm)

[Debian Bug Tracking System]

Your message dated Wed, 22 Dec 2021 01:19:29 +0100
with message-id 
and subject line Re: sponsorship-requests: multi-timer -- Set of countdown 
timers with alarm
has caused the Debian Bug report #1002295,
regarding sponsorship-requests: multi-timer -- Set of countdown timers with 
alarm
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.)


-- 
1002295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
Tags: patch
X-Debbugs-Cc: scorpion2...@protonmail.com

Dear mentors,

I am looking for a sponsor for my package "multi-timer":

 * Package name: multi-timer
   Version : 0.1.1-1
   Upstream Author : pippim.com 
 * URL : https://pippim.github.io/2018/05/23/Set-of-countdown-
timers-with-alarm.html
 * License : MIT
   Section : utils

This app uses yad to create sequentially timers, up to 19.
- Retains configuration between uses, saving it in ~/.multi-timer
- Up to 19 timers run sequentially in a set.
- Progress bar for each timer.
- Set of timers can be run multiple times.
- Progress bar for set.
- Progress bar for all sets.
- Optional prompt to start each timer and/or set.
- Optional pop-up message when each timer and/or set ends.
- Optional alarm when each timer and/or set ends.
- Optional lock screen when each timer OR set OR all sets end.
- Optional close progress bar display when all sets of timers end.
--- End Message ---
--- Begin Message ---

On Tue, 21 Dec 2021 21:51:11 +0100 Scorpion2185  
wrote:

 * URL : https://pippim.github.io/2018/05/23/Set-of-countdown-
timers-with-alarm.html


There is no Debian source package to download, so I am closing this request.--- End Message ---

Bug#1001930: marked as done (sponsorship-requests: Request for Package (RFP): gammy)

[Debian Bug Tracking System]

Your message dated Sun, 19 Dec 2021 23:29:13 +0100
with message-id 
and subject line Re: sponsorship-requests: Request for Package (RFP): gammy
has caused the Debian Bug report #1001930,
regarding sponsorship-requests: Request for Package (RFP): gammy
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.)


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

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? Eye irritation from blue light
   * damage.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Attempted to color correct with redshift.
   * What was the outcome of this action?  Too red.
   * What outcome did you expect instead?  Fine degrees of control with
   * both color and brightness adjustment.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-18-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---

Closing in favour of #1001875.
A RFS is supposed to ask for uploading a package that is already available to 
download.--- End Message ---

Bug#1001930: sponsorship-requests: Request for Package (RFP): gammy

[Randal South]

Package: sponsorship-requests
Severity: wishlist

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? Eye irritation from blue light
   * damage.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Attempted to color correct with redshift.
   * What was the outcome of this action?  Too red.
   * What outcome did you expect instead?  Fine degrees of control with
   * both color and brightness adjustment.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-18-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[bts-link] source package sponsorship-requests

[debian-bts-link]

#
# bts-link upstream status pull for source package sponsorship-requests
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #988923 (http://bugs.debian.org/988923)
# Bug title: RFS: distorm3/3.5.2b-1 [ITA] -- powerful disassembler library for 
x86/AMD64 binary streams (Python3 bindings)
#  * https://github.com/gdabah/distorm/pull/177
#  * remote status changed: (?) -> open
usertags 988923 + status-open

thanks

[bts-link] source package sponsorship-requests

[debian-bts-link]

#
# bts-link upstream status pull for source package sponsorship-requests
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #985815 (http://bugs.debian.org/985815)
# Bug title: RFS: usermanager/1.0.74+git20210323-1 [ITP] -- Graphical user 
manager
#  * https://github.com/xen0vas/UserManager/issues/29
#  * remote status changed: (?) -> open
usertags 985815 + status-open

thanks

Bug#983146: sponsorship-requests: Backup next generation (bung)

[Robin Gustafsson]

Charles,

> I tried hard to make a source .deb but did not manage to do so.  Would
> you like me to share the system I use to create the .deb?

A source package is required for inclusion in Debian. The binary
packages are built automatically on Debian infrastructure and must use
certain build tools for that to work. So, to proceed, there needs to
be a compliant source package.

If you want to maintain this package in Debian yourself, see the
"Introduction for maintainers" [1] page. If you hope to find someone
else to maintain it in Debian, you should instead file a "Request for
package" (RFP) bug to add it to the list of requested packages [2].

[1] https://mentors.debian.net/intro-maintainers/
[2] https://www.debian.org/devel/wnpp/requested

Regards,
Robin

Bug#983146: sponsorship-requests: Backup next generation (bung)

[Robin Gustafsson]

Hi Charles,

Where can I find the Debian source package? I found .deb files, but
not how they're generated.

Also, installing the files under /opt is disallowed for official packages.

Regards,
Robin

Bug#983146: sponsorship-requests: Backup next generation (bung)

[Antonio Russo]

Hello,

> Please change the email address on this bug report from 
> send_only.aurin...@auroville.org.in to b...@charlesmatkinson.org

See controlling the Debian BTS [1].

> I tried hard to make a source .deb but did not manage to do so.
> Would you like me to share the system I use to create the .deb?

Please see the new maintainers guide [2].

The long and short of it is: Debian manages thousands of software
packages and provides a huge amount of freedom to maintainers in
how they do so.  However, your package MUST build from a single
call to debian/rules (see [3], /FTBFSIASW/).

This baseline level of uniformity allows Debian to support many
architectures and provide support for the full duration of a Debian
release.

> bung was not a Debian package so I thought the appropriate place
> to install it was under /opt.  If it becomes a Debian package
> then it should be installed in the conventional places. 

Since you are submitting a package to be included in Debian,
it will not be accepted unless it is packaged in a way that
is suitable for Debian---all the files should be placed in
accordance with the Debian FHS (see [4] and [5]).

Once you do this, be sure to use lintian---I suggest at least
looking at the "pedantic" results:

 lintian --verbose -L ">=pedantic" $changes_file

Sponsors are more likely to look at a lintian-clean package.

Best,
Antonio

[1] https://www.debian.org/Bugs/server-control#submitter
[2] https://www.debian.org/doc/manuals/maint-guide/
[3] https://ftp-master.debian.org/REJECT-FAQ.html
[4] https://wiki.debian.org/FilesystemHierarchyStandard
[5] https://www.debian.org/doc/debian-policy/ch-opersys.html

Bug#983146: sponsorship-requests: Backup next generation (bung)

[Charles]

Hi Robin

Thanks for the prompt reply.

I tried hard to make a source .deb but did not manage to do so.  Would 
you like me to share the system I use to create the .deb?


bung was not a Debian package so I thought the appropriate place to 
install it was under /opt.  If it becomes a Debian package then it 
should be installed in the conventional places.


Best

Charles

On 20/02/2021 18:53, Robin Gustafsson wrote:

Hi Charles,

Where can I find the Debian source package? I found .deb files, but
not how they're generated.

Also, installing the files under /opt is disallowed for official packages.

Regards,
Robin

Bug#983146: sponsorship-requests: Backup next generation (bung)

[Charles]

Dear Maintainer,

Please change the email address on this bug report from 
send_only.aurin...@auroville.org.in to b...@charlesmatkinson.org


Best

Charles Atkinson

On 20/02/2021 08:34, Charles Atkinson wrote:

Package: sponsorship-requests
Severity: normal

Dear Maintainer,

bung has been developed over eight years as a campus backup utility, running
on Debian and a few Ubuntu systems.  It is known to be used on more than 100
computers

Documentation includes man pages and, available from
https://redmine.auroville.org.in/projects/bung/wiki/Bung_technology
user and programmer guides

Selected text from that page follows

bung is a set of wrapper scripts for several backup utilities:

* OpenLDAP (slapcat and tar)
* mysqldump
* pgdump
* rsync

bung also has:

* A "sysinfo" facility to generate system information reports
* Templated backups allowing custom backup commands.  Example templates are
   provided for Cisco switches and MikroTik routers

bung features:

* Automated backup to hotplug devices when they are plugged in with on-screen
   notifications to both character terminals and X displays
* Backup to remote file systems via ssh
* Custom commands (hooks) to run before and after the backup itself
* File system hierarchy standard (FHS) compliant installation under /opt. For
   cron jobs, documentation, the logcheck filter file and man pages, symlinks
   are created in the conventional places with targets under /opt. Fori
   convenience, /etc/opt/bung and /var/log/bung are created for configuration
   and logs
* GPLv2
* Logging designed to ease production support
* LVM snapshots
* man pages
* Mounting and unmounting local file systems
* Remote ssh command validation

Best

Charles Atkinson

Bug#983146: sponsorship-requests: Backup next generation (bung)

[Charles Atkinson]

Package: sponsorship-requests
Severity: normal

Dear Maintainer,

bung has been developed over eight years as a campus backup utility, running
on Debian and a few Ubuntu systems.  It is known to be used on more than 100 
computers

Documentation includes man pages and, available from
https://redmine.auroville.org.in/projects/bung/wiki/Bung_technology 
user and programmer guides

Selected text from that page follows

bung is a set of wrapper scripts for several backup utilities:

* OpenLDAP (slapcat and tar)
* mysqldump
* pgdump
* rsync

bung also has:

* A "sysinfo" facility to generate system information reports
* Templated backups allowing custom backup commands.  Example templates are 
  provided for Cisco switches and MikroTik routers

bung features:

* Automated backup to hotplug devices when they are plugged in with on-screen
  notifications to both character terminals and X displays
* Backup to remote file systems via ssh 
* Custom commands (hooks) to run before and after the backup itself
* File system hierarchy standard (FHS) compliant installation under /opt. For 
  cron jobs, documentation, the logcheck filter file and man pages, symlinks
  are created in the conventional places with targets under /opt. Fori
  convenience, /etc/opt/bung and /var/log/bung are created for configuration
  and logs
* GPLv2
* Logging designed to ease production support
* LVM snapshots
* man pages
* Mounting and unmounting local file systems
* Remote ssh command validation

Best

Charles Atkinson

Bug on sponsorship-requests not automatically forwarded to this mailinglist?

[Matthias Klein]

Hello All,

I'm a beginner to Debian packaging, and have created a package, uploaded
it to mentors.debian.net, and sent out an RFS bug via reportbug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978673

I thought until now that these bug reports are automatically forwarded
to this mailing list. Is this not the case, or is it just that something
went wrong with my bug report?

Many greetings,
Matthias




OpenPGP_signature
Description: OpenPGP digital signature

Bug on sponsorship-requests not automatically forwarded to this mailinglist?

[Matthias Klein]

Hello All,

I'm a beginner to Debian packaging, and have created a package, uploaded
it to mentors.debian.net, and sent out an RFS bug via reportbug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978673

I thought until now that these bug reports are automatically forwarded
to this mailing list. Is this not the case, or is it just that something
went wrong with my bug report?

Many greetings,
Matthias




OpenPGP_signature
Description: OpenPGP digital signature

Bug#969446: sponsorship-requests: vguitar-2.6 [ITP} -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).

[Nick Strauss]

Hi Boyuan Yang, 

I have added my source architecture to repo

apt-key adv --keyserver keyserver.ubuntu.com --recv-keys AB406C34
add to /etc/apt/sources.list.d
deb-src http://apt.nick-strauss.com/apt/debian jessie main
apt-get source vguitar

nick strauss

Bug#969445: sponsorship-requests: vguitar-2.6 [ITP} -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).

[Nick Strauss]

Package: sponsorship-requests
Severity: wishlist

Dear Mentor/Maintainer,

Package name: vguitar
Version : 2.5
Upstream Author : 
URL : http://nick-strauss.com
License : GPL

apt-key adv --keyserver keyserver.ubuntu.com --recv-keys AB406C34
add to /etc/apt/sources.list.d
deb [ arch=amd64 ] http://apt.nick-strauss.com/apt/debian jessie main
apt-get install vguitar

vguitar --help
man vguitar

-- System Information:
Debian Release: 8.4
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldoldstable'), (500, 
'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.55-1-pve (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fr_FR.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#932822: sponsorship-requests: runescape/0.5-3 -- Multiplayer online game set in a fantasy world

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: runescape
   Version : 0.5-3
   Upstream Author : Carlos Donizete Froes 
 * URL : https://gitlab.com/coringao/runescape
 * License : BSD-2-Clause
   Section : non-free/games

  It builds those binary packages:

  runescape - Multiplayer online game set in a fantasy world

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/non-free/r/runescape/runescape_0.5-3.dsc

  More information about runescape can be obtained from 
https://oldschool.runescape.com.

  Changes since the last upload:

  runescape (0.5-3) unstable; urgency=medium

  * Added the XS-Autobuild: yes header to debian/control.
  * Added a note about autobuilding to debian/copyright.

  Regards,
   Carlos Donizete Froes [a.k.a coringao]

Bug#931263: marked as done (sponsorship-requests: blastem/0.6.3.2-1 -- Fast and accurate Genesis emulator)

[Debian Bug Tracking System]

Your message dated Tue, 9 Jul 2019 10:20:30 +0200
with message-id <427e8443-f90a-b76d-2a07-7b5a12a0e...@debian.org>
and subject line Uploaded to debian unstable
has caused the Debian Bug report #931263,
regarding sponsorship-requests: blastem/0.6.3.2-1 -- Fast and accurate Genesis 
emulator
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.)


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

  Dear mentors,

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

 * Package name: blastem
   Version : 0.6.3.2-1
   Upstream Author : Michael Pavone 
 * URL : https://www.retrodev.com/blastem
 * License : GPL-3+
   Section : games

  It builds those binary packages:

  blastem - Fast and accurate Genesis emulator

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/blastem/blastem_0.6.3.2-1.dsc

  More information about BlastEm can be obtained from 
https://gitlab.com/coringao/blastem.

  Changes since the last upload:

  blastem (0.6.3.2-1) unstable; urgency=medium

  * New upstream release: 0.6.3.2

  blastem (0.6.3.1-1) unstable; urgency=medium

  * New upstream release (Closes: #926498)
  * Fix FTCBFS: (Thanks - Helmut Grohne)
+ Let dh_auto_build pass cross tools to make
  * Fixed spelling error in d/upstream/metadata

  Regards,
   Carlos Donizete Froes [a.k.a coringao]
--- End Message ---
--- Begin Message ---
Uploaded to debian unstable.--- End Message ---

Bug#931263: sponsorship-requests: blastem/0.6.3.2-1 -- Fast and accurate Genesis emulator

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: blastem
   Version : 0.6.3.2-1
   Upstream Author : Michael Pavone 
 * URL : https://www.retrodev.com/blastem
 * License : GPL-3+
   Section : games

  It builds those binary packages:

  blastem - Fast and accurate Genesis emulator

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/blastem/blastem_0.6.3.2-1.dsc

  More information about BlastEm can be obtained from 
https://gitlab.com/coringao/blastem.

  Changes since the last upload:

  blastem (0.6.3.2-1) unstable; urgency=medium

  * New upstream release: 0.6.3.2

  blastem (0.6.3.1-1) unstable; urgency=medium

  * New upstream release (Closes: #926498)
  * Fix FTCBFS: (Thanks - Helmut Grohne)
+ Let dh_auto_build pass cross tools to make
  * Fixed spelling error in d/upstream/metadata

  Regards,
   Carlos Donizete Froes [a.k.a coringao]

Bug#928500: sponsorship-requests: additional sponsor for gsequencer

[Joël Krähemann]

Package: sponsorship-requests
Severity: normal

Dear Maintainer,

Since my sponsor has not enough time to do a review for gsequencer
within next days, he gave me an advice to look for an additional sponsor.

https://salsa.debian.org/multimedia-team/gsequencer

best regards,
Joël Krähemann

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Kai Harries]

Hi,

itd  writes:

> Hi,
>
> Kai Harries:
>> The depender will break if the dependency is not at the path where it
>> used to be at build-time (by default /nix/store/...). All software
>> deployed by nix contains the full path to its dependencies. And all
>> dependencies are available inside the nix-store. The idea is to rely on
>> nothing that is outside the nix-store. 
>
> would `mount --bind /var/nix /nix` help? In other words, Debian package
> nix uses /var/nix. Additionally, the package ships a Debian.README which
> states that users need to either bind mount /var/nix to /nix or to
> disable binary downloads.

Yes, bind mounts should work. I had started a discussion on d-devel [1]
on the topic of the non-standard-toplevel-dir, and from there I got the
impression that a lintian override is the way to go.

>From the user experience view I would prefer not to resort to a
bind-mount, but I guess your proposal should work and is the next best
thing I can imagine.

Regards Kai

[1] https://lists.debian.org/debian-devel/2019/01/msg00010.html

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Kai Harries]

Dmitry Bogatov  writes:

> [2018-12-29 19:54] Vincent Bernat 
>> > Probably not. Violations of FHS is violation of policy, and to get
>> > authorization to policy violation is long road, starting with discussion
>> > on debian-devel@.
>> >
>> > But, can't we just configure Nix to store it under /var/nix?
>> 
>> This would break the ability to use pre-built stuff and make nix
>> slow.
>
> I belive you, but just for my curiosity, what will break if we download
> substitute (nar, almost tar archive) and extract it not in /nix, but in
> /var/nix?

The depender will break if the dependency is not at the path where it
used to be at build-time (by default /nix/store/...). All software
deployed by nix contains the full path to its dependencies. And all
dependencies are available inside the nix-store. The idea is to rely on
nothing that is outside the nix-store. 

For example an ldd on bash looks like this:

$ ldd 
/nix/store/ij6wirzff9id7jr071p04w4nk6hksc3y-bash-interactive-4.4-p23/bin/bash
/nix/store/ij6wirzff9id7jr071p04w4nk6hksc3y-bash-interactive-4.4-p23/bin/bash:
linux-vdso.so.1 (0x7ffe1a7d5000)
libreadline.so.7 => 
/nix/store/vvwxc17kpc39qbcz7qp7mkqa7fr0my84-readline-7.0p5/lib/libreadline.so.7 
(0x7f25b0593000)
libhistory.so.7 => 
/nix/store/vvwxc17kpc39qbcz7qp7mkqa7fr0my84-readline-7.0p5/lib/libhistory.so.7 
(0x7f25b0389000)
libncursesw.so.6 => 
/nix/store/2lbhgxlrhgnij2c3bm719xidymmhp0m0-ncurses-6.1-20181027/lib/libncursesw.so.6
 (0x7f25b011a000)
libdl.so.2 => 
/nix/store/7gx4kiv5m0i7d7qkixq2cwzbr10lvxwc-glibc-2.27/lib/libdl.so.2 
(0x7f25aff16000)
libc.so.6 => 
/nix/store/7gx4kiv5m0i7d7qkixq2cwzbr10lvxwc-glibc-2.27/lib/libc.so.6 
(0x7f25afb62000)

/nix/store/7gx4kiv5m0i7d7qkixq2cobra10lvxwc-glibc-2.27/lib/ld-linux-x86-64.so.2 
=> 
/nix/store/7gx4kiv5m0i7d7qkixq2cwzbr10lvxwc-glibc-2.27/lib64/ld-linux-x86-64.so.2
 (0x7f25b07def000)

Regards, Kai

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Dmitry Bogatov]

[2018-12-29 19:54] Vincent Bernat 
> > Probably not. Violations of FHS is violation of policy, and to get
> > authorization to policy violation is long road, starting with discussion
> > on debian-devel@.
> >
> > But, can't we just configure Nix to store it under /var/nix?
> 
> This would break the ability to use pre-built stuff and make nix
> slow.

I belive you, but just for my curiosity, what will break if we download
substitute (nar, almost tar archive) and extract it not in /nix, but in
/var/nix?

In mean time, I took a look at your debianization. Great work. One
question:

 * You install developer stuff (headers, pkg-config files) in nix
   package. It is not needed for mere user, so I believe you should
   make three binary packages -- nix, libnix and libnix-dev.

   By the way, who are users of nix development files?

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Vincent Bernat]

 ❦ 29 décembre 2018 18:33 +00, Dmitry Bogatov :

> Probably not. Violations of FHS is violation of policy, and to get
> authorization to policy violation is long road, starting with discussion
> on debian-devel@.
>
> But, can't we just configure Nix to store it under /var/nix?

This would break the ability to use pre-built stuff and make nix
slow.
-- 
Don't diddle code to make it faster - find a better algorithm.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Dmitry Bogatov]

[2018-12-27 11:24] Kai Harries 
> > [2018-02-26 22:46] Andrey Rahmatullin 
> >> On Sun, Feb 25, 2018 at 11:14:37PM +0100, Kai Harries wrote:
> >> > > The source package you've uploaded is broken, as .dsc mentions
> >> > > nix_1.11.15-2~a1.debian.tar.xz.
> >
> > Hi!
> >
> > What is state of affairs with packaging nix? I am interested in getting
> > things done, maybe I could contribute somehow?
> 
> We need to discuss with ftp-masters if we can get an exemption from
> the non-standard-toplevel-dir lintian rule (see this bug [1]). I am
> still planning to write a request to them, do you know if
> ftpmas...@debian.org would be the right address to start this
> discussion?

Probably not. Violations of FHS is violation of policy, and to get
authorization to policy violation is long road, starting with discussion
on debian-devel@.

But, can't we just configure Nix to store it under /var/nix?

> Furthermore I am waiting for the 2.2 Nix upstream release (see here [2])
> the master was not buildable for me the last time I tried it (see here
> [3]).

I will take a look.

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Kai Harries]

Kai Harries  writes:

> Dmitry Bogatov  writes:
>
>> [2018-02-26 22:46] Andrey Rahmatullin 
>>> On Sun, Feb 25, 2018 at 11:14:37PM +0100, Kai Harries wrote:
>>> > > The source package you've uploaded is broken, as .dsc mentions
>>> > > nix_1.11.15-2~a1.debian.tar.xz.
>>
>> Hi!
>>
>> What is state of affairs with packaging nix? I am interested in getting
>> things done, maybe I could contribute somehow?
>
> We need to discuss with ftp-masters if we can get an exemption from
> the non-standard-toplevel-dir lintian rule (see this bug [1]). I am
> still planning to write a request to them, do you know if
> ftpmas...@debian.org would be the right address to start this
> discussion?

Send out a request to ftpmaster.

>
> Furthermore I am waiting for the 2.2 Nix upstream release (see here [2])
> the master was not buildable for me the last time I tried it (see here
> [3]).
>
> Help with this or some of the other minor issues is welcome.
>
>
> [1] https://github.com/KaiHa/nix-debian/issues/20
> [2] https://github.com/KaiHa/nix-debian/issues/9
> [3] https://github.com/KaiHa/nix-debian/issues/21

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Kai Harries]

Dmitry Bogatov  writes:

> [2018-02-26 22:46] Andrey Rahmatullin 
>> On Sun, Feb 25, 2018 at 11:14:37PM +0100, Kai Harries wrote:
>> > > The source package you've uploaded is broken, as .dsc mentions
>> > > nix_1.11.15-2~a1.debian.tar.xz.
>
> Hi!
>
> What is state of affairs with packaging nix? I am interested in getting
> things done, maybe I could contribute somehow?

We need to discuss with ftp-masters if we can get an exemption from
the non-standard-toplevel-dir lintian rule (see this bug [1]). I am
still planning to write a request to them, do you know if
ftpmas...@debian.org would be the right address to start this
discussion?

Furthermore I am waiting for the 2.2 Nix upstream release (see here [2])
the master was not buildable for me the last time I tried it (see here
[3]).

Help with this or some of the other minor issues is welcome.


[1] https://github.com/KaiHa/nix-debian/issues/20
[2] https://github.com/KaiHa/nix-debian/issues/9
[3] https://github.com/KaiHa/nix-debian/issues/21

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Dmitry Bogatov]

[2018-02-26 22:46] Andrey Rahmatullin 
> On Sun, Feb 25, 2018 at 11:14:37PM +0100, Kai Harries wrote:
> > > The source package you've uploaded is broken, as .dsc mentions
> > > nix_1.11.15-2~a1.debian.tar.xz.

Hi!

What is state of affairs with packaging nix? I am interested in getting
things done, maybe I could contribute somehow?

Bug#908850: marked as done ([sponsorship-requests] Need sponsor and maintainer status for geneweb package)

[Debian Bug Tracking System]

Your message dated Tue, 9 Oct 2018 22:14:49 -0400
with message-id 

and subject line Re: Bug#908850: [sponsorship-requests] Need sponsor and 
maintainer status for geneweb package
has caused the Debian Bug report #908850,
regarding [sponsorship-requests] Need sponsor and maintainer status for geneweb 
package
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.)


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

---

Hi,


For the last two years, I have worked on the maintenance of the geneweb
package with the help & sponsorship of Christian Perrier (which is still
the official maintainer of the package).
https://tracker.debian.org/pkg/geneweb
https://salsa.debian.org/GuillaumeBrochu-guest/geneweb-package-test

I would like to continue the work on the package, including the migration
of the git repository to Salsa. However, in a recent private communication
with Christian, he informed me that he is no longer available to continue
the sponsorship and package maintenance, and referred me to debian-mentors.

Therefore, I need a new sponsor to continue the work. My objectives are :
- migration of the git repository to Salsa (which was previously here :
https://anonscm.debian.org/cgit/collab-maint/geneweb.git/)
- fix an old bug with the import of a new upstream release and perhaps push
it into the stretch-backports, if possible;
- prepare for Buster;
- start to test the packaging of the next geneweb release (geneweb 7), and
perhaps push it into experimental, if possible.

For this, I need (1) a new sponsor from the Debian developers team and (2)
the transfer of the maintainer status of the geneweb package to me and/or
to the new sponsor.

Thank you and best regards,


Guillaume Brochu
--- End Message ---
--- Begin Message ---
X-Debbugs-CC: guillaume.bro...@gmail.com

Hi Guillaume,

Please prepare a new upload and submit a RFS bug after that. If a
stable preparation -- sponsorship relationship is not to be
established, at least Debian Developers on debian-mentors can review
your sponsorship request on a case-by-case basis.

Since this bug report is not actually a RFS request, I am closing it
for now. Please prepare your upload and resubmit another RFS when
ready.

--
Regards,
Boyuan Yang--- End Message ---

Bug#908850: [sponsorship-requests] Need sponsor and maintainer status for geneweb package

[Guillaume Brochu]

Package: sponsorship-requests
Severity: normal

---

Hi,


For the last two years, I have worked on the maintenance of the geneweb
package with the help & sponsorship of Christian Perrier (which is still
the official maintainer of the package).
https://tracker.debian.org/pkg/geneweb
https://salsa.debian.org/GuillaumeBrochu-guest/geneweb-package-test

I would like to continue the work on the package, including the migration
of the git repository to Salsa. However, in a recent private communication
with Christian, he informed me that he is no longer available to continue
the sponsorship and package maintenance, and referred me to debian-mentors.

Therefore, I need a new sponsor to continue the work. My objectives are :
- migration of the git repository to Salsa (which was previously here :
https://anonscm.debian.org/cgit/collab-maint/geneweb.git/)
- fix an old bug with the import of a new upstream release and perhaps push
it into the stretch-backports, if possible;
- prepare for Buster;
- start to test the packaging of the next geneweb release (geneweb 7), and
perhaps push it into experimental, if possible.

For this, I need (1) a new sponsor from the Debian developers team and (2)
the transfer of the maintainer status of the geneweb package to me and/or
to the new sponsor.

Thank you and best regards,


Guillaume Brochu

Bug#903872: sponsorship-requests: cavestory-nx/1.0.0-1 [ITP] -- Nostalgic side action adventure game

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "cavestory-nx"

 * Package name: cavestory-nx
   Version : 1.0.0-1
   Upstream Author : Carlos Donizete Froes 
 * URL : https://gitlab.com/coringao/cavestory-nx
 * License : BSD-2-Clause
   Section : non-free/games

  It builds those binary packages:

  cavestory-nx - Nostalgic side action adventure game
  cavestory-nx-data - Nostalgic side action adventure game (data files)

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

  https://mentors.debian.net/package/cavestory-nx

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

  dget -x 
https://mentors.debian.net/debian/pool/non-free/c/cavestory-nx/cavestory-nx_1.0.0-1.dsc

  More information about Cave Story NX can be obtained from 
https://gitlab.com/coringao/cavestory-nx.

  Regards,
   Carlos Donizete Froes [a.k.a coringao]

Re: sponsorship-requests

[Adam Borowski]

On Tue, May 29, 2018 at 12:14:41PM +0200, ox16 wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
>   Dear mentors, maintainer, developer
> 
>   I am looking for a sponsor for package fonts-labiryntowy  * 
> Package name: fonts-labiryntowy
>   Version : 1.53-1
>   Upstream Author : Marek   o...@o2.pl 
> * URL :  alfabet-ozdobny.appspot.com alfabet-ozdobny.appspot.com
> * License : sil
>   Section : fonts
> 
> 
>   Alternatively, one can download the package  salsa.debian.org 
> salsa.debian.org   Thanks

Please use "reportbug sponsorship-requests" instead; this will file it in
the bug tracking system (and CC to the mailing list), to ensure a record of
the review.

The packaging's state isn't bad, with errors I noticed during a cursory
review being:
* debian/dirs creates an unused directory in /usr/local which triggers
  postinst and postrm we don't want
* the changelog says the package is aimed at stable; all new packages need
  to go to unstable instead
* the copyright file claims the font is copyrighted by SIL International;
  that's obviously wrong.  You also have two definitions of one license name
  -- the license should be written in its own section.
* the first version should close an ITP bug

Which leads us to the ITP part.  Please "reportbug wnpp" to file an "Intent
To Package", including the font's proposed description (which you have
already written) and some reasoning why you think this package should be a
part of Debian.  Normally that second part is obvious, but an invented
alphabet is something that deserves a moment of thought.  ITP bugs are CCed
to debian-devel where the developers have a chance of commenting; they might
have some insight wrt how to mark a special font of this kind.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts
⣾⠁⢰⠒⠀⣿⡁ productivity.  You can read it, too, you just need the
⢿⡄⠘⠷⠚⠋⠀ right music while doing so.  I recommend Skepticism
⠈⠳⣄ (funeral doom metal).

Odp: Re: sponsorship-requests

[ox16]

Dnia 29 maja 2018 14:04 Ko Ko Ye` kokoye2...@gmail.com napisał(a):  * 
License : sil   you mean OFL-1.1 ?  yes, SIL OFL-1.1

Re: sponsorship-requests

[Ko Ko Ye`]

* License : sil

> you mean OFL-1.1 ?


On Tue, May 29, 2018 at 4:44 PM, ox16  wrote:

>
> Package: sponsorship-requests
> Severity: wishlist
>
>   Dear mentors, maintainer, developer
>
>   I am looking for a sponsor for package "fonts-labiryntowy"
>
> * Package name: fonts-labiryntowy
>   Version : 1.53-1
>   Upstream Author : Marek 
> * URL : https://alfabet-ozdobny.appspot.com/?str=labiryntowy
> * License : sil
>   Section : fonts
>
>
>   Alternatively, one can download the package 
> https://salsa.debian.org/ox16-guest/fonts-labiryntowy 
> <https://salsa.debian.org/ox16-guest/fonts-labiryntowy/tree/master/debian>
>
>
> Thanks
>
>
>


-- 

with regards *Ko Ko Ye`*

+95 97989 22022
+95 94500 22022
+95 9731 47907
kokoye2...@gmail.com
kokoye2...@ubuntu.com

skype: kokoye2007
jitsi: kokoye2007

http://ubuntu-mm.net
http://wiki.ubuntu.com/kokoye2007
http://wiki.ubuntu.com/MyanmarTeam http://loco.ubuntu.com/teams/ubuntu-mm

sponsorship-requests

[ox16]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors, maintainer, developer

  I am looking for a sponsor for package fonts-labiryntowy  * Package 
name: fonts-labiryntowy
  Version : 1.53-1
  Upstream Author : Marek   o...@o2.pl 
* URL :  alfabet-ozdobny.appspot.com alfabet-ozdobny.appspot.com
* License : sil
  Section : fonts


  Alternatively, one can download the package  salsa.debian.org 
salsa.debian.org   Thanks

Bug#896560: marked as done (sponsorship-requests: cavestory-nx/1.0.0-1 [ITP] -- NXEngine is a Cave Story game engine clone)

[Debian Bug Tracking System]

Your message dated Mon, 07 May 2018 16:22:31 +
with message-id <e1ffiuf-0002ud...@quantz.debian.org>
and subject line closing RFS: cavestory-nx/1.0.0-1 [ITP] -- NXEngine is a Cave 
Story game engine clone
has caused the Debian Bug report #896714,
regarding sponsorship-requests: cavestory-nx/1.0.0-1 [ITP] -- NXEngine is a 
Cave Story game engine clone
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.)


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

  Dear mentors,

  I am looking for a sponsor for my package "cavestory-nx"

 * Package name: cavestory-nx
   Version : 1.0.0-1
   Upstream Author : Carlos Donizete Froes <corin...@riseup.net>
 * URL : https://github.com/coringao/cavestory-nx
 * License : GPL-3+
   Section : contrib/games

  It builds those binary packages:

  cavestory-nx - NXEngine is a Cave Story game engine clone
  cavestory-nx-data - NXEngine is a Cave Story game engine clone (data files)

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

  https://mentors.debian.net/package/cavestory-nx

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

  dget -x 
https://mentors.debian.net/debian/pool/contrib/c/cavestory-nx/cavestory-nx_1.0.0-1.dsc

  More information about 'Cave Story NX' can be obtained from 
https://github.com/coringao/cavestory-nx.

  Regards,
   Carlos Donizete Froes [a.k.a coringao]
--- End Message ---
--- Begin Message ---
Package cavestory-nx has been removed from mentors.--- End Message ---

Bug#898093: sponsorship-requests: fonts-myanmar/1.0-2 [ITA] -- friendly greeter

[kokoye2007]

Package: sponsorship-requests
Severity: normal

Dear Maintainer,

  I am looking for a sponsor for my package "fonts-myanmar"

 * Package name: fonts-myanmar
   Version : 1.0-1
   Upstream Author : Debian Fonts Task Force 
<pkg-fonts-de...@lists.alioth.debian.org>
 * URL : https://launchpad.net/ttf-burmese-fonts
 * License : gpl3
   Section : fonts

  It builds those binary packages:

fonts-myanmar - ttf myanmar fonts:
 fonts-myanmar-angoun - myanmar fonts: angoun;
 fonts-myanmar-ayar - ttf myanmar fonts: ayar;
 fonts-myanmar-chatu - myanmar fonts: chatu;
 fonts-myanmar-chatulight - myanmar fonts: chatulight;
 fonts-myanmar-gantgaw - myanmar fonts: gantgaw;
 fonts-myanmar-khyay - myanmar fonts: khyay;
 fonts-myanmar-kuttar - myanmar fonts: kuttar;
 fonts-myanmar-myanmar3 - ttf myanmar fonts: Myanmar3;
 fonts-myanmar-myanmarcensus - ttf myanmar fonts: MyanmarCensus;
 fonts-myanmar-nayone - myanmar fonts: nayone;
 fonts-myanmar-njaun - myanmar fonts: njaun;
 fonts-myanmar-pauklay - myanmar fonts: pauklay;
 fonts-myanmar-phetsot - myanmar fonts: phetsot;
 fonts-myanmar-phiksel - myanmar fonts: phiksel;
 fonts-myanmar-phikselsmooth - myanmar fonts: phikselsmooth;
 fonts-myanmar-ponenyet - myanmar fonts: ponenyet;
 fonts-myanmar-pyidaungsu - ttf myanmar fonts: Pyidaungsu;
 fonts-myanmar-sabae - myanmar fonts: sabae;
 fonts-myanmar-sagar - myanmar fonts: sagar;
 fonts-myanmar-sanpya - myanmar fonts: sanpya;
 fonts-myanmar-squarelight - myanmar fonts: squarelight;
 fonts-myanmar-tagu - myanmar fonts: tagu;
 fonts-myanmar-thuriya - myanmar fonts: thuriya;
 fonts-myanmar-unicode - ttf myanmar unicode fonts
 fonts-myanmar-waso - myanmar fonts: waso;
 fonts-myanmar-yinmar - myanmar fonts: yinmar;
 fonts-myanmar-zawgyi - ttf myanmar fonts: ZawgyiOne2008;

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

  https://mentors.debian.net/package/fonts-myanmar


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

dget -x 
https://mentors.debian.net/debian/pool/main/f/fonts-myanmar/fonts-myanmar_1.0-1.dsc

  More information about fonts-myanmar can be obtained from 
https://www.ubuntu-mm.net and launchpad.net/ttf-burmese-fonts

with regards with SC DFSG

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

Kernel: Linux 4.15.0-21-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#896560: sponsorship-requests: cavestory-nx/1.0.0-1 [ITP] -- NXEngine is a Cave Story game engine clone

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "cavestory-nx"

 * Package name: cavestory-nx
   Version : 1.0.0-1
   Upstream Author : Carlos Donizete Froes <corin...@riseup.net>
 * URL : https://github.com/coringao/cavestory-nx
 * License : GPL-3+
   Section : contrib/games

  It builds those binary packages:

  cavestory-nx - NXEngine is a Cave Story game engine clone
  cavestory-nx-data - NXEngine is a Cave Story game engine clone (data files)

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

  https://mentors.debian.net/package/cavestory-nx

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

  dget -x 
https://mentors.debian.net/debian/pool/contrib/c/cavestory-nx/cavestory-nx_1.0.0-1.dsc

  More information about 'Cave Story NX' can be obtained from 
https://github.com/coringao/cavestory-nx.

  Regards,
   Carlos Donizete Froes [a.k.a coringao]

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Andrey Rahmatullin]

On Sun, Feb 25, 2018 at 11:14:37PM +0100, Kai Harries wrote:
> > The source package you've uploaded is broken, as .dsc mentions
> > nix_1.11.15-2~a1.debian.tar.xz.
> 
> My fault, GitHub doesn't like '~' in file names so I have uploaded
> the files with an '.' instead of '~'. I have uploaded a new version [1]
> that does not use the '~' in the version.
Thank you.
Please use verbose build output.
Please switch to the current debhelper compat level.
The Vcs-* tags don't point to the packaging repo.
You hardcode "perl5/site_perl/5.26.1/x86_64-linux-gnu-thread-multi" in
d/rules.
Does the package really need to include development files?
The source ships embedded code copies of at least bsdiff and parts of
boost. It even builds and installs bsdiff and bspatch binaries. And the
copyrights and licenses of this source are not listed in d/copyright.
Putting the whole LGPL in d/copyright is wrong. And it says "LGPL-2.1"
while the manual says "LGPL-2.1+".
src/libexpr/parser-tab.* and doc/manual/style.css licenses are not
mentioned in d.copyright. 

> > The version, 1.11.15-2~a1, is wrong for an initial Debian upload.
> 
> I have used 1.11.16-1 now. But I am not 100% sure that this is an
> correct version number for the initial upload!?
It is, why not?

> > Also, the version in the RFS subject is not the package version.
> 
> My fault I missed a number in my RFS. What should I do to fix
> this. Create a new RFS? (BTW I have now taken a newer upstream version).
You should retitle this one.

> > You need to run lintian from unstable on your package and fix main issues
> > before asking for sponsorship.
> 
> Only two warnings left:
> 
>   W: nix: manpage-has-errors-from-man usr/share/man/man1/nix-store.1.gz 1235: 
> warning [p 13, 9.7i]: can't break line
>   W: nix: binary-without-manpage usr/bin/nix-generate-patches
That's definitely not true.

E: nix changes: unreleased-changes
W: nix source: debhelper-tools-from-autotools-dev-are-deprecated dh ... --with 
autotools_dev (line 18)
P: nix source: package-uses-old-debhelper-compat-version 9
W: nix source: build-depends-on-obsolete-package build-depends: dh-systemd => 
use debhelper (>= 9.20160709)
I: nix source: out-of-date-standards-version 3.9.8 (released 2016-04-06) 
(current is 4.1.3)
I: nix source: testsuite-autopkgtest-missing
X: nix source: upstream-metadata-file-is-missing
P: nix source: debian-watch-does-not-check-gpg-signature
I: nix: hardening-no-fortify-functions usr/bin/nix-daemon
I: nix: hardening-no-fortify-functions usr/bin/nix-instantiate
I: nix: hardening-no-fortify-functions usr/bin/nix-store
I: nix: hardening-no-fortify-functions ... use --no-tag-display-limit to see 
all (or pipe to a file/program)
I: nix: spelling-error-in-binary usr/bin/nix-collect-garbage refered referred
I: nix: hardening-no-bindnow usr/bin/nix-collect-garbage
I: nix: spelling-error-in-binary usr/bin/nix-daemon refered referred
I: nix: hardening-no-bindnow usr/bin/nix-daemon
I: nix: spelling-error-in-binary usr/bin/nix-env refered referred
I: nix: hardening-no-bindnow usr/bin/nix-env
I: nix: spelling-error-in-binary ... use --no-tag-display-limit to see all (or 
pipe to a file/program)
I: nix: hardening-no-bindnow ... use --no-tag-display-limit to see all (or pipe 
to a file/program)
P: nix: no-upstream-changelog
I: nix: spelling-error-in-copyright GNU Library Public License GNU Library 
General Public License
W: nix: package-installs-deprecated-upstart-configuration 
etc/init/nix-daemon.conf
W: nix: pkg-config-unavailable-for-cross-compilation 
usr/lib/pkgconfig/nix-expr.pc
W: nix: pkg-config-unavailable-for-cross-compilation 
usr/lib/pkgconfig/nix-main.pc
W: nix: pkg-config-unavailable-for-cross-compilation 
usr/lib/pkgconfig/nix-store.pc
W: nix: manpage-has-errors-from-man usr/share/man/man1/nix-store.1.gz 1235: 
warning [p 13, 9.7i]: can't break line
W: nix: binary-without-manpage usr/bin/nix-generate-patches
I: nix: possible-documentation-but-no-doc-base-registration
X: nix: shlib-calls-exit usr/lib/nix/libnixexpr.so
X: nix: shlib-calls-exit usr/lib/nix/libnixmain.so
X: nix: shlib-calls-exit usr/lib/nix/libnixstore.so
I: nix: systemd-service-file-missing-documentation-key 
lib/systemd/system/nix-daemon.service
I: nix: systemd-service-file-missing-install-key 
lib/systemd/system/nix-daemon.service


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[KAction]

>   W: nix: manpage-has-errors-from-man usr/share/man/man1/nix-store.1.gz 1235: 
> warning [p 13, 9.7i]: can't break line
>   W: nix: binary-without-manpage usr/bin/nix-generate-patches
> 
> I hope this is acceptable.

// I am not DD; did not read source.

As far as I know, lintian warnings and errors are never acceptable. And,
as a user, I understand, why missing manpage is treated so severe.

I am not familiar with nix, but if nix-generate-patches is not
end-user-command, you could install it into private directory, that
would fix second warning.
 

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Kai Harries]

Hello,

Andrey Rahmatullin  writes:

> Control: tags -1 + moreinfo
>
> The source package you've uploaded is broken, as .dsc mentions
> nix_1.11.15-2~a1.debian.tar.xz.

My fault, GitHub doesn't like '~' in file names so I have uploaded
the files with an '.' instead of '~'. I have uploaded a new version [1]
that does not use the '~' in the version.


> I don't think the package is even buildable tbh, looking at
> debian/nix-docs.docs.

This was an accident. I somehow overlooked this file that was generated
by dh_make. I have removed it now.

> The version, 1.11.15-2~a1, is wrong for an initial Debian upload.

I have used 1.11.16-1 now. But I am not 100% sure that this is an
correct version number for the initial upload!?

> Also, the version in the RFS subject is not the package version.

My fault I missed a number in my RFS. What should I do to fix
this. Create a new RFS? (BTW I have now taken a newer upstream version).

> You need to run lintian from unstable on your package and fix main issues
> before asking for sponsorship.

Only two warnings left:

  W: nix: manpage-has-errors-from-man usr/share/man/man1/nix-store.1.gz 1235: 
warning [p 13, 9.7i]: can't break line
  W: nix: binary-without-manpage usr/bin/nix-generate-patches

I hope this is acceptable.

>
> -- 
> WBR, wRAR

[1] https://github.com/KaiHa/nix-debian/releases/tag/1.11.16-1

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Andrey Rahmatullin]

Control: tags -1 + moreinfo

The source package you've uploaded is broken, as .dsc mentions
nix_1.11.15-2~a1.debian.tar.xz.
I don't think the package is even buildable tbh, looking at
debian/nix-docs.docs.
The version, 1.11.15-2~a1, is wrong for an initial Debian upload.
Also, the version in the RFS subject is not the package version.
You need to run lintian from unstable on your package and fix main issues
before asking for sponsorship.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#879759: marked as done (sponsorship-requests: ponyprog/3.0.0)

[Debian Bug Tracking System]

Your message dated Mon, 6 Nov 2017 23:08:55 +0500
with message-id <20171106180855.27smmnnsnn4q4...@belkar.wrar.name>
and subject line Re: Bug#879759: sponsorship-requests: ponyprog/3.0.0
has caused the Debian Bug report #879759,
regarding sponsorship-requests: ponyprog/3.0.0
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.)


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

I am looking for a sponsor for project from Claudio Lanconelli 
<claudiolancone...@gmail.com> "PonyProg"

 * Package name: ponyprog
   Version : 3.0.0
   Upstream Author : Claudio Lanconelli
 * URL : https://github.com/lancos/ponyprog
 * License : GPLv2
   Section : tools, c++, qt

It possible to build followed packages with CMake/CPack:

  ponyprog debian package - the binary file with language files
  ponyprog source files package - source code of project

The source code you can download from here: 
https://sourceforge.net/projects/ponyprog/files/PonyProg%20sources/3.0.0/ponyprog-3.0.0.tar.gz/download

or from github:
https://github.com/lancos/ponyprog


This program is the porting of PonyProg2000 project to Qt4/Qt5 toolkit.
I can support this project with help from Claudio under Linux.

Regards,

Qt developer
 Eduard Kalinowski

--- End Message ---
--- Begin Message ---
This is not a RFS as you don't seem to have a package yet. If that's true,
please look at https://mentors.debian.net/intro-maintainers and start
doing the packaging as outlined there. Otherwise please file a correct RFS
with a package link. I'm closing this.

-- 
WBR, wRAR


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

Bug#879759: sponsorship-requests: ponyprog/3.0.0

[Andrey Rahmatullin]

This is not a RFS as you don't seem to have a package yet. If that's true,
please look at https://mentors.debian.net/intro-maintainers and start
doing the packaging as outlined there. Otherwise please file a correct RFS
with a package link. I'm closing this.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#879759: sponsorship-requests: ponyprog/3.0.0

[Eduard Kalinowski]

Package: sponsorship-requests
Severity: wishlistDear mentors,

I am looking for a sponsor for project from Claudio Lanconelli 
<claudiolancone...@gmail.com> "PonyProg"

 * Package name: ponyprog
   Version : 3.0.0
   Upstream Author : Claudio Lanconelli
 * URL : https://github.com/lancos/ponyprog
 * License : GPLv2
   Section : tools, c++, qt

It possible to build followed packages with CMake/CPack:

  ponyprog debian package - the binary file with language files
  ponyprog source files package - source code of project

The source code you can download from here: 
https://sourceforge.net/projects/ponyprog/files/PonyProg%20sources/3.0.0/ponyprog-3.0.0.tar.gz/download

or from github:
https://github.com/lancos/ponyprog


This program is the porting of PonyProg2000 project to Qt4/Qt5 toolkit.
I can support this project with help from Claudio under Linux.

Regards,

Qt developer
 Eduard Kalinowski

Bug#876519: sponsorship-requests: RFS: tack/1.08-0.1 [RC, NMU]

[Tobias Frost]

Hi Sven,

many thanks for updating the package! I've just uploaded it.

Many thanks for your contributions to Debian!

--
tobi

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Kai Harries]

Package: sponsorship-requests
Severity: wishlist

Dear Mentors,

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

* Package name: nix
  Version : 1.1.15
  Upstream Author : Eelco Dolstra
* URL : https://nixos.org/nix/
* License : LGPL v2.1
  Section : devel

It builds those binary packages:

  nix - Purely functional package manager
  
To access further information about this package, please visit the
following URL:

https://github.com/KaiHa/nix-debian/releases

If you haven't been exposed to Nix up to now, this [1] might give you a
good introduction to Nix.

It is a really impressive tool and I would be happy if it could be
included into Debian. 

[1] https://nixos.org/nix/about.html

Regards,

Kai Harries

Bug#876519: sponsorship-requests: RFS: tack/1.08-0.1 [RC, NMU]

[Sven Joachim]

On 2017-09-23 10:54 +0200, Sven Joachim wrote:

> Package: sponsorship-requests
> Severity: important
>
> I am looking for a sponsor for an NMU of the "tack" package,
> https://tracker.debian.org/pkg/tack.
>
> This is a new upstream version fixing an FTBFS bug with current
> ncurses[1] and a segfault problem[2].  In addition to that, I have fixed
> the debian/watch file which was no longer working[3].
>
> I have tried to keep the changes under debian/ minimal, but the upstream
> changes are quite large (34 files changed, 10268 insertions, 4831
> deletions).  Still, considering that this is a leaf package with low
> popcon and the maintainer has not replied to any of the bugs, packaging
> a new upstream release seemed appropriate to me.
>
> A detailed log of what I broke is on the git repository at [4] (the
> Debian changelog has not been finalized there yet, will push if/when the
> package gets accepted into Debian).
>
> 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862472
> 2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716377
> 3. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873288
> 4. https://anonscm.debian.org/git/users/joachim-guest/tack.git/log/?h=nmu

I guess it would have helped if I had mentioned that I have actually
uploaded the package to mentors.debian.net[1,2].  Except for the now
finalized debian/changelog, it matches what is in the above git
repository.

Cheers,
   Sven

1. https://mentors.debian.net/package/tack
2. https://mentors.debian.net/debian/pool/main/t/tack/tack_1.08-0.1.dsc

Bug#876519: sponsorship-requests: RFS: tack/1.08-0.1 [RC, NMU]

[Sven Joachim]

Package: sponsorship-requests
Severity: important

I am looking for a sponsor for an NMU of the "tack" package,
https://tracker.debian.org/pkg/tack.

This is a new upstream version fixing an FTBFS bug with current
ncurses[1] and a segfault problem[2].  In addition to that, I have fixed
the debian/watch file which was no longer working[3].

I have tried to keep the changes under debian/ minimal, but the upstream
changes are quite large (34 files changed, 10268 insertions, 4831
deletions).  Still, considering that this is a leaf package with low
popcon and the maintainer has not replied to any of the bugs, packaging
a new upstream release seemed appropriate to me.

A detailed log of what I broke is on the git repository at [4] (the
Debian changelog has not been finalized there yet, will push if/when the
package gets accepted into Debian).

Cheers,
   Sven

1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862472
2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716377
3. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873288
4. https://anonscm.debian.org/git/users/joachim-guest/tack.git/log/?h=nmu

Bug#861371: sponsorship-requests: Looking for sponsorship for libgdamm package

[Gianfranco Costamagna]

last thing: there seems to be already an Ubuntu package, so for sure you should 
start from that
packaging.

https://launchpad.net/ubuntu/+source/libgdamm5.0


G.

Bug#861371: sponsorship-requests: Looking for sponsorship for libgdamm package

[Gianfranco Costamagna]

control: tags -1 moreinfo

>I am looking for a sponsor for my package libgdamm


the package as is is a no-no.
lots of useless stuff in packaging, incomplete copyright, wrong VCS-Git
field (and missing repo), debhelper 9 instead of 10, missing package 
description, rules file
that should be fixed (don't call autogen.sh but fix autoreconf to do its
job correctly).

If you want your package in Debian, try fixing lintian first, open an ITP
bug, get in touch with pkg-gnome team, and come back with a more suitable 
package.

(sorry but I can't review it right now, too much missing stuff!)

cheers,

G.

Bug#861371: sponsorship-requests: Looking for sponsorship for libgdamm package

[Pavlo Solntsev]

Package: sponsorship-requests
Severity: normal
Tags: upstream

Dear Maintainer,

I am looking for a sponsor for my package libgdamm

* Package name: libgdamm
  Version : 4.99.11
  Upstream Author : Murray Cumming <murr...@usa.net>
* URL : https://github.com/GNOME/libgdamm
* License : LGPL
  Programming Lang: C++
  Description : C++ wrappers for libgda

 C++ wrappers for libgda

It builds those binary packages:
 libgdamm - C++ wrappers for libgda
 libgdamm-dbgsym  - Debug symbols for libgdamm
 libgdamm-dev - C++ wrappers for libgda. Development files.
 libgdamm-doc - C++ wrappers for libgda. Documentation.

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

 https://github.com/GNOME/libgdamm

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

  dget -x
https://mentors.debian.net/debian/pool/main/libg/libgdamm/libgdamm_4.99.11-1.dsc

  More information about libgdamm can be obtained from
https://github.com/GNOME/libgdamm.

  Changes since the last upload:

 No changes on my side. Upstream version in active development. The specified
above version is not upstream. It is the latest stable version.

  Regards,
  -Pavlo Solntsev



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#859776: marked as done (sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor)

[Debian Bug Tracking System]

Your message dated Sun, 9 Apr 2017 01:57:56 +0200
with message-id <20170408235756.rfvifcughvrk6...@angband.pl>
and subject line Re: Bug#859776: sponsorship-requests: vis/0.3 [ITP] -- A a 
modern and legacy free Vim-like text editor
has caused the Debian Bug report #859776,
regarding sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free 
Vim-like text editor
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.)


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

Dear mentors,

I'm looking for a sponsor for "vis":

 * Package name: vis
   Version : 0.3
   Upstream Author : Marc André Tanner <m...@brain-dump.org>
 * URL : https://github.com/martanne/vis
 * License : ISC
   Section : editors

It's my main editor, so I'm willing to keep the package well maintained and up
to date. To access further information about this package please visit:

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

Thank you,

Paride Legovini
--- End Message ---
--- Begin Message ---
On Sat, Apr 08, 2017 at 12:56:40PM +0200, Paride Legovini wrote:
> On 2017-04-07 19:54, Adam Borowski wrote:
> > On Fri, Apr 07, 2017 at 05:52:21PM +0200, Paride Legovini wrote:
> >> On 2017-04-07 15:39, Adam Borowski wrote:
> >>> On Fri, Apr 07, 2017 at 12:54:22PM +0200, Paride Legovini wrote:
> >>>>  * Package name: vis
> >>>>Version : 0.3
> > 
> > Seems to be fine, except for two error messages I get:
> > 
> > /usr/share/vis/themes/default-256.lua:23: attempt to index a nil value 
> > (local 'lexers')
> > WARNING: could not find lpeg module
> 
> The package now Recommends: lua-lpeg, that is the dependency you are
> missing. The upstream README.md lists it as an "optional runtime
> dependency", so I think Recommends: is appropriate.

I'd still prefer a nicer message, or no error at all -- but that's not a
blocker for the initial version.  Let's get a working version in, there'll
be plenty of time to improve it later.

> I also changed the priorities for the alternatives for 'editor' and 'vi'
> (see debian/postinst). The rationale is that it's OK to prefer vis to
> very basic flavors of vim, lettings the ones with more features win. I
> also didn't want to override nano, as it is the editor suggested to less
> experienced users. Seems reasonable to me, but I'd like to have some
> feedback.

I'm not a vi user, but from the gist of things I see that vis tries to be a
good _editor_ but not necessarily a good _vi_.  That sounds like you'd want
a pretty low priority for "vi" but a decent one for "editor".  But I haven't
researched the priorities either, someone else might have better feedback
here.


Uploaded; I've done most testing on armhf as I suppose you did amd64
yourself; armhf is also the architecture I used for the binary upload so it
will have no build log.


ᛗᛖᛟᚹ!
-- 
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second
⠈⠳⣄ preimage for double rot13!--- End Message ---

Bug#859776: sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor

[Paride Legovini]

On 2017-04-07 19:54, Adam Borowski wrote:
> On Fri, Apr 07, 2017 at 05:52:21PM +0200, Paride Legovini wrote:
>> On 2017-04-07 15:39, Adam Borowski wrote:
>>> On Fri, Apr 07, 2017 at 12:54:22PM +0200, Paride Legovini wrote:
  * Package name: vis
Version : 0.3
> 
> Seems to be fine, except for two error messages I get:
> 
> /usr/share/vis/themes/default-256.lua:23: attempt to index a nil value (local 
> 'lexers')
> WARNING: could not find lpeg module
> 

The package now Recommends: lua-lpeg, that is the dependency you are
missing. The upstream README.md lists it as an "optional runtime
dependency", so I think Recommends: is appropriate.

I also changed the priorities for the alternatives for 'editor' and 'vi'
(see debian/postinst). The rationale is that it's OK to prefer vis to
very basic flavors of vim, lettings the ones with more features win. I
also didn't want to override nano, as it is the editor suggested to less
experienced users. Seems reasonable to me, but I'd like to have some
feedback.

Paride

Bug#859776: sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor

[Adam Borowski]

On Fri, Apr 07, 2017 at 05:52:21PM +0200, Paride Legovini wrote:
> On 2017-04-07 15:39, Adam Borowski wrote:
> > On Fri, Apr 07, 2017 at 12:54:22PM +0200, Paride Legovini wrote:
> >>  * Package name: vis
> >>Version : 0.3

Seems to be fine, except for two error messages I get:

/usr/share/vis/themes/default-256.lua:23: attempt to index a nil value (local 
'lexers')
WARNING: could not find lpeg module

-- 
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second
⠈⠳⣄ preimage for double rot13!

Bug#859776: sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor

[Paride Legovini]

On 2017-04-07 15:39, Adam Borowski wrote:
> On Fri, Apr 07, 2017 at 12:54:22PM +0200, Paride Legovini wrote:
>>  * Package name: vis
>>Version : 0.3
> 
>> It's my main editor, so I'm willing to keep the package well maintained and 
>> up
>> to date.
> 
> If, per the home page, it's not fully vi compatible, it can't be entirely
> bad :p  Let's see how it fares, especially with basic vi tests like no other
> way to exit it than kill -9 on another terminal. :)

Let's see :)

> I'm afraid I didn't get that far with review, though:
> 
> creating config.mk... done
> checking for pkg-config... no
> checking for libcurses...
>  checking for ncursesw... no
>  checking for ncurses... no
>  checking for libcurses... no
> ./configure: cannot find libcurses
> debian/rules:7: recipe for target 'override_dh_auto_configure' failed

Should be fixed now: I added a build-dependency to pkg-config.

> Also, the distribution is set to UNRELEASED.  For an actual upload (even if
> just to mentors if it's meant for sponsoring rather than review only),
> please change it to "unstable".

Done, thank you for your feedback.

Paride

Bug#859776: sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor

[Adam Borowski]

On Fri, Apr 07, 2017 at 12:54:22PM +0200, Paride Legovini wrote:
>  * Package name: vis
>Version : 0.3

> It's my main editor, so I'm willing to keep the package well maintained and up
> to date.

If, per the home page, it's not fully vi compatible, it can't be entirely
bad :p  Let's see how it fares, especially with basic vi tests like no other
way to exit it than kill -9 on another terminal. :)


I'm afraid I didn't get that far with review, though:

creating config.mk... done
checking for pkg-config... no
checking for libcurses...
 checking for ncursesw... no
 checking for ncurses... no
 checking for libcurses... no
./configure: cannot find libcurses
debian/rules:7: recipe for target 'override_dh_auto_configure' failed


Also, the distribution is set to UNRELEASED.  For an actual upload (even if
just to mentors if it's meant for sponsoring rather than review only),
please change it to "unstable".


ᛗᛖᛟᚹ!
-- 
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second
⠈⠳⣄ preimage for double rot13!

Bug#859776: sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor

[Paride Legovini]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I'm looking for a sponsor for "vis":

 * Package name: vis
   Version : 0.3
   Upstream Author : Marc André Tanner <m...@brain-dump.org>
 * URL : https://github.com/martanne/vis
 * License : ISC
   Section : editors

It's my main editor, so I'm willing to keep the package well maintained and up
to date. To access further information about this package please visit:

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

Thank you,

Paride Legovini

Bug#835347: marked as done (sponsorship-requests: RFS asn1c/0.9.27+dfsg-1 -- ASN.1 compiler for C)

[Debian Bug Tracking System]

Your message dated Wed, 24 Aug 2016 21:31:33 +0300
with message-id <1c4b8286-50f5-4f2e-ac73-46cf7ee3d...@gmail.com>
and subject line Re: Bug#835347: sponsorship-requests: RFS asn1c/0.9.27+dfsg-1 
-- ASN.1 compiler for C
has caused the Debian Bug report #835347,
regarding sponsorship-requests: RFS asn1c/0.9.27+dfsg-1 -- ASN.1 compiler for C
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.)


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

RFS asn1c/0.9.27+dfsg-1 -- ASN.1 compiler for C

Dear mentors,

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

* Package name: asn1c
  Version : 0.9.27+dfsg-1
  Upstream Author : Lev Walkin <v...@lionet.info>
* URL : https://github.com/vlm/asn1c
* License : BSD-2-Clause
  Section : misc

Previous versions of the package were mentored by Arno Töll since 2012 
(prepared for jessie).
New versions of "asn1c" partially fixed some bugs from existing patches, 
several patches are reported
upstream so the package delta is continiously decreasing. New uploads may fix 
build bugs with m68k and
make the build reproducible.


It builds those binary packages:

  asn1c - ASN.1 compiler for C

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/a/asn1c/asn1c_0.9.27+dfsg-1.dsc

Changes since the last upload:

  * New upstream release
  * Updated policy version to 3.9.8
  * Drop patches 03_nodebugoutcheck, 05_nooverflowtests, 06_implicitdecl,
07_asneeded as they are fixed in upstream
  * Changed watch to new upstream home
  * Changed fonts for the generated PDF documentation


Regards,
 Eugene Seliverstov
--- End Message ---
--- Begin Message ---

> On 24.08.2016, at 19:19, Gianfranco Costamagna <locutusofb...@debian.org> 
> wrote:
> 
> Hi,
> 
>> RFS asn1c/0.9.27+dfsg-1 -- ASN.1 compiler for C
> 
> ok, done!
> 
> G.

Thank you!

---
Best regards,
Eugene Seliverstov--- End Message ---

Bug#835347: sponsorship-requests: RFS asn1c/0.9.27+dfsg-1 -- ASN.1 compiler for C

[Eugene Seliverstov]

> On 24.08.2016, at 19:19, Gianfranco Costamagna  
> wrote:
> 
> Hi,
> 
>> RFS asn1c/0.9.27+dfsg-1 -- ASN.1 compiler for C
> 
> ok, done!
> 
> G.

Thank you!

---
Best regards,
Eugene Seliverstov

Bug#835347: sponsorship-requests: RFS asn1c/0.9.27+dfsg-1 -- ASN.1 compiler for C

[Gianfranco Costamagna]

Hi,

>RFS asn1c/0.9.27+dfsg-1 -- ASN.1 compiler for C

ok, done!

G.

Bug#835347: sponsorship-requests: RFS asn1c/0.9.27+dfsg-1 -- ASN.1 compiler for C

[Eugene Seliverstov]

Package: sponsorship-requests
Severity: normal

RFS asn1c/0.9.27+dfsg-1 -- ASN.1 compiler for C

Dear mentors,

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

* Package name: asn1c
  Version : 0.9.27+dfsg-1
  Upstream Author : Lev Walkin <v...@lionet.info>
* URL : https://github.com/vlm/asn1c
* License : BSD-2-Clause
  Section : misc

Previous versions of the package were mentored by Arno Töll since 2012 
(prepared for jessie).
New versions of "asn1c" partially fixed some bugs from existing patches, 
several patches are reported
upstream so the package delta is continiously decreasing. New uploads may fix 
build bugs with m68k and
make the build reproducible.


It builds those binary packages:

  asn1c - ASN.1 compiler for C

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/a/asn1c/asn1c_0.9.27+dfsg-1.dsc

Changes since the last upload:

  * New upstream release
  * Updated policy version to 3.9.8
  * Drop patches 03_nodebugoutcheck, 05_nooverflowtests, 06_implicitdecl,
07_asneeded as they are fixed in upstream
  * Changed watch to new upstream home
  * Changed fonts for the generated PDF documentation


Regards,
 Eugene Seliverstov

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

2016-01-25 18:27 GMT+01:00 Mattia Rizzolo :

>
> So, given that those are still warnings (that would be nice to get rid
> of), and that are for sure not blockers, what would you think about
>
uploading it as it's now and work on it on a later time?
>

I think that's a good idea, we will sort it out later. The latest upload is
available on the mentors site.
Anyway this whole procedure was a really important experience, some
modification will be done on the upstream side to.
So I hope with the next release we will move forward much faster. Thank you
for being so patient with me. :)

BR,
Gergely

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Mattia Rizzolo]

On Tue, Jan 26, 2016 at 12:19:09PM +0100, Jakub Wilk wrote:
> * Pilisi Gergely , 2016-01-22, 14:55:
> >export DEB_BUILD_MAINT_OPTIONS = hardening=+all
> >export CPPFLAGS=$(shell dpkg-buildflags --get CPPFLAGS)
> >export CFLAGS=$(shell dpkg-buildflags --get CFLAGS)
> >export CXXFLAGS=$(shell dpkg-buildflags --get CXXFLAGS)
> >export LDFLAGS=$(shell dpkg-buildflags --get LDFLAGS)
> 
> Note that $(shell) constructs are not affected by variables exported in the
> same makefile.
> 
> >export CCFLAGS=$(shell dplg-buildflags --get CFLAGS)
> 
> Typo: s/dplg/dpkg/.

oh, thank you, indeed!
Your email made me try some more, and I get a better state in blhc.
I noticed that the faulty flag is pie-related.
I applied this:

--- eclipse-titan-5.4.1/debian/rules2016-01-22 13:30:30.0 +
+++ eclipse-titan-5.4.1/debian/rules2016-01-26 23:42:37.0 +
@@ -1,12 +1,9 @@
 #!/usr/bin/make -f
 export V=1
 export DH_VERBOSE=1
-export DEB_BUILD_MAINT_OPTIONS = hardening=+all
-export CPPFLAGS=$(shell dpkg-buildflags --get CPPFLAGS)
-export CFLAGS=$(shell dpkg-buildflags --get CFLAGS)
-export CXXFLAGS=$(shell dpkg-buildflags --get CXXFLAGS)
-export LDFLAGS=$(shell dpkg-buildflags --get LDFLAGS)
-export CCFLAGS=$(shell dplg-buildflags --get CFLAGS)
+
+export DEB_BUILD_OPTIONS=hardening=+all,-pie
+export CCFLAGS = $(shell DEB_BUILD_OPTIONS=hardening=+all,-pie dpkg-buildflags 
--get CFLAGS)
 
 %:
dh $@ --verbose --parallel

Which I like some more than your version (I want to remember you that
debhlper with compat 9+ exports those flags by itself, except CCFLAGS
which is non-standard)

Still, I couldn't carry this thing further.
Given that I like this more, can I upload this instead? :)

> >What is wrong with that? :(
> 
> blhc(1) is invaluable for debugging hardening issues.

Yeah, I do use it, even if usually the thing I fixed in the past were
quite easy to fix and I had ever had the need to look at its output
closer than just glancing over it.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Jakub Wilk]

* Pilisi Gergely , 2016-01-22, 14:55:

export DEB_BUILD_MAINT_OPTIONS = hardening=+all
export CPPFLAGS=$(shell dpkg-buildflags --get CPPFLAGS)
export CFLAGS=$(shell dpkg-buildflags --get CFLAGS)
export CXXFLAGS=$(shell dpkg-buildflags --get CXXFLAGS)
export LDFLAGS=$(shell dpkg-buildflags --get LDFLAGS)


Note that $(shell) constructs are not affected by variables exported in 
the same makefile.



export CCFLAGS=$(shell dplg-buildflags --get CFLAGS)


Typo: s/dplg/dpkg/.


What is wrong with that? :(


blhc(1) is invaluable for debugging hardening issues.

--
Jakub Wilk

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Mattia Rizzolo]

On Fri, Jan 22, 2016 at 02:55:38PM +0100, Pilisi Gergely wrote:
> First of all, thank you for the help. :) The new package is on the mentors
> site.

> I fixed this with exporting the build flags in the debian/rules file:
> 
> export DEB_BUILD_MAINT_OPTIONS = hardening=+all
> export CPPFLAGS=$(shell dpkg-buildflags --get CPPFLAGS)
> export CFLAGS=$(shell dpkg-buildflags --get CFLAGS)
> export CXXFLAGS=$(shell dpkg-buildflags --get CXXFLAGS)
> export LDFLAGS=$(shell dpkg-buildflags --get LDFLAGS)
> export CCFLAGS=$(shell dplg-buildflags --get CFLAGS)

oh, I see, you laso have CCFLAGS, which is kinda of non-standard (and as
such not exported.

> Now the code compiles perfectly, but I still can't see any hardening on the
> binaries.
> Lintian still throws hardening-no-fortify-functions and
> hardening-no-relro...
> 
> What is wrong with that? :(

I'm pretty lost in this :\
I think this needs a more thorough look into the build system to
understan what's wrong with it, but these days I can't really look at
it.

So, given that those are still warnings (that would be nice to get rid
of), and that are for sure not blockers, what would you think about
uploading it as it's now and work on it on a later time?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

First of all, thank you for the help. :) The new package is on the mentors
site.

2016-01-17 14:09 GMT+01:00 Mattia Rizzolo :

>
> but most importantly, I couldn't get eclipse-titan build today.
> First it failed with
>
> /usr/bin/ld: LoggerPlugin_dynamic.o: undefined reference to symbol
> 'dlclose@@GLIBC_2.2.5'
> //lib/x86_64-linux-gnu/libdl.so.2: error adding symbols: DSO missing from
> command line
> collect2: error: ld returned 1 exit status
> Makefile:307: recipe for target 'libttcn3-dynamic.so' failed
>
>
> Then, I added -ldl to LDFLAGS and retried, just to have
>
> Parallel_main.o: In function `main':
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:203: undefined reference
> to `TCov::close_file()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:208: undefined reference
> to `TTCN_Runtime::install_signal_handlers()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:209: undefined reference
> to `TTCN_Snapshot::initialize()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:210: undefined reference
> to `TTCN_Logger::initialize_logger()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:211: undefined reference
> to `TTCN_Logger::set_executable_name(char const*)'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:212: undefined reference
> to `TTCN_Logger::set_start_time()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:218: undefined reference
> to `Module_List::pre_init_modules()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:219: undefined reference
> to `TTCN_Runtime::hc_main(char const*, char const*, unsigned short)'
> Parallel_main.o: In function `TTCN_Runtime::is_hc()':
> /build/eclipse-titan-5.4.1/core/Runtime.hh:92: undefined reference to
> `TTCN_Runtime::executor_state'
> Parallel_main.o: In function `main':
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:246: undefined reference
> to `TTCN_Runtime::restore_signal_handlers()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:247: undefined reference
> to `TTCN_Logger::close_file()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:248: undefined reference
> to `TCov::close_file()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:251: undefined reference
> to `TTCN_Logger::clear_parameters()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:252: undefined reference
> to `PORT::clear_parameters()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:253: undefined reference
> to `COMPONENT::clear_component_names()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:254: undefined reference
> to `TTCN_EncDec::clear_error()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:256: undefined reference
> to `TTCN_Logger::terminate_logger()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:257: undefined reference
> to `TTCN_Snapshot::terminate()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:223: undefined reference
> to `COMPONENT::clear_component_names()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:226: undefined reference
> to `TTCN_Logger::close_file()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:227: undefined reference
> to `TCov::close_file()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:229: undefined reference
> to `TTCN_Logger::set_start_time()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:233: undefined reference
> to `TTCN_Runtime::ptc_main()'
> Parallel_main.o: In function `process_options':
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:136: undefined reference
> to `TTCN_Runtime::install_signal_handlers()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:137: undefined reference
> to `TTCN_Logger::initialize_logger()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:138: undefined reference
> to `Module_List::pre_init_modules()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:139: undefined reference
> to `Module_List::list_testcases()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:143: undefined reference
> to `TTCN_Logger::terminate_logger()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:157: undefined reference
> to `Module_List::print_version()'
> Parallel_main.o: In function `main':
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:231: undefined reference
> to `TTCN_Runtime::mtc_main()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:235: undefined reference
> to `TTCN_error(char const*, ...)'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:242: undefined reference
> to `TTCN_Logger::log_str(TTCN_Logger::Severity, char const*)'
> Parallel_main.o: In function `__static_initialization_and_destruction_0':
> /build/eclipse-titan-5.4.1/core/../common/version.h:94: undefined
> reference to `reffer::reffer(char const*)'
> Parallel_main.o: In function `JSON_Tokenizer::JSON_Tokenizer(bool)':
> /build/eclipse-titan-5.4.1/core/../common/JSON_Tokenizer.hh:115: undefined
> reference to `JSON_Tokenizer::init(char const*, unsigned long)'
> Parallel_main.o: In function `__static_initialization_and_destruction_0':
> 

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Mattia Rizzolo]

On Thu, Jan 14, 2016 at 02:31:25PM +0100, Pilisi Gergely wrote:
> please check the new version. I fixed a couple of things, but the remaining
> ones got me...

sorry, took some time.  My routine started again after the
winter/christmas break.. :)

A thing.  you changed the .orig.tar.gz.  Don't do that.  Once a release
has been made you can't really change it.
Those are the diffs between the old one and this:
https://paste.debian.net/366300/
Technically speaking, since that file has not yet been uploaded to
ftp-master it can still be changed, but what about other users of it?

> 2016-01-13 15:22 GMT+01:00 Mattia Rizzolo :
> > hardening-wrapper can just go away, the package builds fine anyway.
> > The canonical way to have hardening buildflags is to export
> > DEB_BUILD_MAINT_OPTIONS=hardening=+all in d/rules (instead of
> > DEB_BUILD_HARDENING).
> > Having a look at Makefile.cfg I see:
> > * CFLAGS ain't used (instead there is a CCFLAGS variable);
> > * CXXFLAGS ignores the external env.
> > You may need to patch it a bit.
> 
>  hardening-wrapper wiped out, but new lintian warning showed up:
> hardening-no-relro.
> Tried to DEB_BUILD_MAINT_OPTIONS=hardening=+all, warning still there.
> Tried to set CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS) and use it
> in the Makefile, same result.

In debian/rules, the line about the hardening was commented out.
That means something.

Anyway, adding debian-specific code to upstream is not that nice, other
distributions would have troubles for nothing.  CFLAGS & friends are in
the env, so there is no real need to call dpkg-buildflags that way.
Just do something like 

-CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS)
+CPPFLAGS := $(CPPFLAGS)

or directly

CPPFLAGS += -DYY_NO_INPUT

In the diff in the tarball I see some changes from CCFLAGS to CFLAGS.
whatever, dpkg-buildflags exports/uses CFLAGS and not CCFLAGS, but you
can avoid changing upstream sources by just adding
export CCFLAGS = $(shell dplg-buildflags --get CFLAGS)
in d/rules, but YMMV, your call here.


but most importantly, I couldn't get eclipse-titan build today.
First it failed with

/usr/bin/ld: LoggerPlugin_dynamic.o: undefined reference to symbol 
'dlclose@@GLIBC_2.2.5'
//lib/x86_64-linux-gnu/libdl.so.2: error adding symbols: DSO missing from 
command line
collect2: error: ld returned 1 exit status
Makefile:307: recipe for target 'libttcn3-dynamic.so' failed


Then, I added -ldl to LDFLAGS and retried, just to have

Parallel_main.o: In function `main':
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:203: undefined reference to 
`TCov::close_file()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:208: undefined reference to 
`TTCN_Runtime::install_signal_handlers()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:209: undefined reference to 
`TTCN_Snapshot::initialize()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:210: undefined reference to 
`TTCN_Logger::initialize_logger()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:211: undefined reference to 
`TTCN_Logger::set_executable_name(char const*)'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:212: undefined reference to 
`TTCN_Logger::set_start_time()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:218: undefined reference to 
`Module_List::pre_init_modules()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:219: undefined reference to 
`TTCN_Runtime::hc_main(char const*, char const*, unsigned short)'
Parallel_main.o: In function `TTCN_Runtime::is_hc()':
/build/eclipse-titan-5.4.1/core/Runtime.hh:92: undefined reference to 
`TTCN_Runtime::executor_state'
Parallel_main.o: In function `main':
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:246: undefined reference to 
`TTCN_Runtime::restore_signal_handlers()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:247: undefined reference to 
`TTCN_Logger::close_file()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:248: undefined reference to 
`TCov::close_file()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:251: undefined reference to 
`TTCN_Logger::clear_parameters()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:252: undefined reference to 
`PORT::clear_parameters()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:253: undefined reference to 
`COMPONENT::clear_component_names()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:254: undefined reference to 
`TTCN_EncDec::clear_error()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:256: undefined reference to 
`TTCN_Logger::terminate_logger()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:257: undefined reference to 
`TTCN_Snapshot::terminate()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:223: undefined reference to 
`COMPONENT::clear_component_names()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:226: undefined reference to 
`TTCN_Logger::close_file()'
/build/eclipse-titan-5.4.1/core/Parallel_main.cc:227: undefined reference to 
`TCov::close_file()'

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

please check the new version. I fixed a couple of things, but the remaining
ones got me...

2016-01-13 15:22 GMT+01:00 Mattia Rizzolo :

> 2)
> hardening-wrapper can just go away, the package builds fine anyway.
> The canonical way to have hardening buildflags is to export
> DEB_BUILD_MAINT_OPTIONS=hardening=+all in d/rules (instead of
> DEB_BUILD_HARDENING).
> Having a look at Makefile.cfg I see:
> * CFLAGS ain't used (instead there is a CCFLAGS variable);
> * CXXFLAGS ignores the external env.
> You may need to patch it a bit.


 hardening-wrapper wiped out, but new lintian warning showed up:
hardening-no-relro.
Tried to DEB_BUILD_MAINT_OPTIONS=hardening=+all, warning still there.
Tried to set CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS) and use it
in the Makefile, same result.


> 4)
> there are a bunch of debug-file-with-no-debug-symbols and that
> postinst-has-useless-call-to-ldconfig that makes me itch.  I feel there
> is something weird going on, but I wouldn't know what it is.
>

Can't find out what's this. Checked the Makefile, the standard output, but
I can't see anything related to this.

>
> 5)
> do you even look at what lintian says on mentors?
> I: eclipse-titan source: wildcard-matches-nothing-in-dep5-copyright
> mctr2/editline (paragraph at line 5)
> I: eclipse-titan source: unused-file-paragraph-in-dep5-copyright paragraph
> at line 5
>
> the order of the paragraphs in d/copyright is important.  the wildcard
> in the second paragraph overrides the first.  so you need to swap them.
>

Switched the paragraphs, deleted unnecessary white spaces, etc... didn't
worked.
Checked every part of
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0 but
nothing. No more ideas.


> Furthermore I don't see a paragraph for debian/, as I can read it now
> the copyright for debian/* is of "Ericsson Telecom AB".
>

Is this a problem? I'm working at Ericcson, and I'm doing it as part of my
job. :)


>
>
>
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  http://mapreri.org  : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
>

Bug#809642: sponsorship-requests: RFS: digikam/4:4.14.0-1.1~bpo8+1 [NMU]

[Matthias Erich Popp]

Am Mittwoch, 13. Januar 2016, 15:23:30 schrieb Gianfranco Costamagna:
> Hi,
> I did a dch --bpo and uploaded on debomatic
> 
> http://debomatic-amd64.debian.net/distribution#jessie-backports/digikam/4.14
> .0-3~bpo8+1/buildlog
> 
> Matthias, does it work for you? I can upload it on backports if nobody
> objects.
> 
> I did some basic tests and the application is starting correctly on a clean
> jessie+bpo system.
> 
> (I could use a version on mentors, but you need to fix the versioning
> scheme)
> 
> cheers,
> 
> Gianfranco
> 
> 
> 
> 
> Il Domenica 10 Gennaio 2016 16:15, Steve M. Robbins  ha
> scritto: Hello Matthias,
> 
> Thank you for your interest in backporting digikam.  I can't speak for the
> other maintainers, but I personally do not have time to maintain backports
> and I would welcome your efforts to do so.
> 
> I have not looked at your package.  But I was a little surprised that the
> proposed backport of 4.14.0-1 was versioned 4.14.0-1.1~bpo8+1.   I did read
> through http://backports.debian.org/Contribute/ (thanks to Mattia Rizzolo
> for the reference!) and under the "basic rules" it says to simply append
> "~bpo..." to the version.  Do you really also need to change from "-1" to
> "-1.1"?
> 
> Best,
> -Steve
> 
> On January 2, 2016 12:13:59 PM Gianfranco Costamagna wrote:
> > Control: tags -1 moreinfo
> > 
> > Hi Matthias, if you need a backport, please ask the team or the previous
> > uploaders to perform it.
> > 
> > I cced the actual maintainers for the package, they will follow up with an
> > upload if possible (I hope).
> > 
> > BTW this kind of requests are usually performed with a bug against the
> > package, unless the package is mostly unmaintained.
> > 
> > cheers,
> > 
> > G.


The upload from debomatic  is ok. I can download pictures from my camera a 
Canon Powersshot SX 110 IS.

My problem with the versions number is . Its a NMU Upload for the backports.
Is this 4.14.0-1.1~bpo8+1 or this correct 4.14.0-1~bpo8+1.1 ? 

dch -n --bpo isn't  working.   

The output from lintian.


N:Check: nmu, Type: source
N: 
W: digikam source: source-nmu-has-incorrect-version-number 4:4.14.0-3~bpo8+1
N: 
N:A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a
N:native package). This is to prevent stealing version numbers from the
N:maintainer.
N:
N:Maybe you didn't intend this upload to be a NMU, in that case, please
N:double-check that the most recent entry in the changelog is
N:byte-for-byte identical to the maintainer or one of the uploaders. If
N:this is a local package (not intended for Debian), you can suppress this
N:warning by putting "local" in the version number or "local package" on
N:the first line of the changelog entry.
N:
N:Refer to Debian Developer's Reference section 5.11.2 (NMUs and
N:debian/changelog) for details.
N:
N:Severity: normal, Certainty: certain
N:
N:Check: nmu, Type: source


with best regards from Dortmund Matthias

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

sorry for removing the bug from my mail, won't happen again. :)
I'm trying to reproduce this:

"About ditching hardening-wrapped in favour of just using what
dpkg-buildflags do:
whatever I use the .dsc you provided, just removed hardening-wrapper or
enable the hardening build flags using DEB_BUILD_MAINT_OPTIONS, the
build fails with

In file included from jnimw.cc:8:0:
jnimw.h:14:17: fatal error: jni.h: No such file or directory
compilation terminated.
../Makefile.genrules:87: recipe for target 'jnimw.o' failed "

This is a typical error message if the compiler can't find a valid JDK on
your system. Do you have /usr/lib/jvm/default-java on your system?
It's a symlink to the default jdk: default-java -> java-1.7.0-openjdk-amd64
I think if openjdk-7-jdk is installed then then the default-java symlink
must be there.

BR,
Gergely

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

The new package is done, everything is fixed, I hope. I didn't changed
anything in the source, just under the debian/ directory. Should I upload
the package as before or use the dquilt method as
https://www.debian.org/doc/manuals/maint-guide/update suggests?
If I'm right, the update method is for the change in the upstream source,
or?

2016-01-13 12:38 GMT+01:00 Pilisi Gergely :

>
>
> 2016-01-13 12:24 GMT+01:00 Mattia Rizzolo :
>
>>
>> mattia@chase ~ % apt-file search /usr/lib/jvm/default-java
>> default-jre-headless: /usr/lib/jvm/default-java
>>
>> Indeed adding it to build-deps the package builds.
>> Make sure to do your test builds inside a clean chroot.
>>
>
> Oh, just missed this dep, thank you.
>
>
>>
>> BTW, I don't see an update package on mentors (if you meant to upload
>> one).  I can't do much if I can't see what you've done till now :)
>
>
> I want to fix everything what you asked. I'm almost done, just testing the
> copyright part. If it looks good then I'll upload the new package. ;)
> Will back to you soon.
>
>

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Mattia Rizzolo]

On Wed, Jan 13, 2016 at 08:56:55AM +0100, Pilisi Gergely wrote:
> I'm trying to reproduce this:
> 
> "About ditching hardening-wrapped in favour of just using what
> dpkg-buildflags do:
> whatever I use the .dsc you provided, just removed hardening-wrapper or
> enable the hardening build flags using DEB_BUILD_MAINT_OPTIONS, the
> build fails with
> 
> In file included from jnimw.cc:8:0:
> jnimw.h:14:17: fatal error: jni.h: No such file or directory
> compilation terminated.
> ../Makefile.genrules:87: recipe for target 'jnimw.o' failed "
> 
> This is a typical error message if the compiler can't find a valid JDK on
> your system. Do you have /usr/lib/jvm/default-java on your system?
> It's a symlink to the default jdk: default-java -> java-1.7.0-openjdk-amd64
> I think if openjdk-7-jdk is installed then then the default-java symlink
> must be there.

it's not.  Inside the chroot where I build the package:
root@chase:~# ls -l /usr/lib/jvm/
total 0
lrwxrwxrwx 1 root root  20 Dec 12 23:44 java-1.7.0-openjdk-amd64 -> 
java-7-openjdk-amd64
drwxr-xr-x 7 root root 220 Jan 13 11:14 java-7-openjdk-amd64

now, if you need such things, you should build-depend on something that
provides that file.

mattia@chase ~ % apt-file search /usr/lib/jvm/default-java
default-jre-headless: /usr/lib/jvm/default-java

Indeed adding it to build-deps the package builds.
Make sure to do your test builds inside a clean chroot.

BTW, I don't see an update package on mentors (if you meant to upload
one).  I can't do much if I can't see what you've done till now :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

2016-01-13 12:24 GMT+01:00 Mattia Rizzolo :

>
> mattia@chase ~ % apt-file search /usr/lib/jvm/default-java
> default-jre-headless: /usr/lib/jvm/default-java
>
> Indeed adding it to build-deps the package builds.
> Make sure to do your test builds inside a clean chroot.
>

Oh, just missed this dep, thank you.


>
> BTW, I don't see an update package on mentors (if you meant to upload
> one).  I can't do much if I can't see what you've done till now :)


I want to fix everything what you asked. I'm almost done, just testing the
copyright part. If it looks good then I'll upload the new package. ;)
Will back to you soon.

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Gianfranco Costamagna]

Hi,
>The new package is done, everything is fixed, I hope. I didn't changed 
>anything in the source, just under the debian/ directory. Should I upload the 
>package as >before or use the dquilt method as 
>https://www.debian.org/doc/manuals/maint-guide/update suggests?
>If I'm right, the update method is for the change in the upstream source, or?


please read

http://mentors.debian.net/intro-maintainers

(TL:TR)
gbp buildpackage -S -sa
dput mentors ../filename_foo_source.changes


cheers

G.

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Mattia Rizzolo]

On Wed, Jan 13, 2016 at 02:44:25PM +0100, Pilisi Gergely wrote:
> Hi,
> 
> the new package is available on the mentors site:

ok, new iteration :)

1)
Well, I'm conviced that --verbose passed to dh is not what I had in mind
with "verbose building".
I still see

  (C++)  Object.cc
  (CC)   record.c
  (C++)  OCSV.cc
  (CC)   record_of.c
  (CC)   union.c
  (C++)  Tag.cc
  (C++)  PredefFunc.cc
  (C++)  TableConstraint.cc
  (C++)  AST.cc
  (C++)  TokenBuf.cc

that's ↑ not's verbose at all.

Here's an hint for you: this a makefile-based project.  to have GNU make
be more verbose, is enough to export V=1.  This gave me indeed a verbose
output of compilation flags, but somehow the build failed this way (??).
It's very easy to make this program fail to build, feel fragile...

2)
hardening-wrapper can just go away, the package builds fine anyway.
The canonical way to have hardening buildflags is to export
DEB_BUILD_MAINT_OPTIONS=hardening=+all in d/rules (instead of
DEB_BUILD_HARDENING).
Having a look at Makefile.cfg I see:
* CFLAGS ain't used (instead there is a CCFLAGS variable);
* CXXFLAGS ignores the external env.
You may need to patch it a bit.

3)
please fix the following lintian warnings:
W: eclipse-titan: script-with-language-extension usr/bin/ttcn3_archive.pl
I: eclipse-titan: package-contains-empty-directory usr/share/titan/etc/asciiart/
W: eclipse-titan: manpage-has-errors-from-man 
usr/share/man/man1/ttcn3_logfilter.1.gz 11: warning: macro `..' not defined
W: eclipse-titan: manpage-has-errors-from-man 
usr/share/man/man1/ttcn3_logformat.1.gz 54: a space character is not allowed in 
an escape name
W: eclipse-titan: executable-not-elf-or-script usr/bin/ttcn3_archive.pl

4)
there are a bunch of debug-file-with-no-debug-symbols and that
postinst-has-useless-call-to-ldconfig that makes me itch.  I feel there
is something weird going on, but I wouldn't know what it is.

5)
do you even look at what lintian says on mentors?
I: eclipse-titan source: wildcard-matches-nothing-in-dep5-copyright 
mctr2/editline (paragraph at line 5)
I: eclipse-titan source: unused-file-paragraph-in-dep5-copyright paragraph at 
line 5

the order of the paragraphs in d/copyright is important.  the wildcard
in the second paragraph overrides the first.  so you need to swap them.
Furthermore I don't see a paragraph for debian/, as I can read it now
the copyright for debian/* is of "Ericsson Telecom AB".




-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#809642: sponsorship-requests: RFS: digikam/4:4.14.0-1.1~bpo8+1 [NMU]

[Gianfranco Costamagna]

Hi,
I did a dch --bpo and uploaded on debomatic

http://debomatic-amd64.debian.net/distribution#jessie-backports/digikam/4.14.0-3~bpo8+1/buildlog

Matthias, does it work for you? I can upload it on backports if nobody objects.

I did some basic tests and the application is starting correctly on a clean 
jessie+bpo system.

(I could use a version on mentors, but you need to fix the versioning scheme)

cheers,

Gianfranco




Il Domenica 10 Gennaio 2016 16:15, Steve M. Robbins <st...@sumost.ca> ha 
scritto:
Hello Matthias,

Thank you for your interest in backporting digikam.  I can't speak for the 
other maintainers, but I personally do not have time to maintain backports and 
I would welcome your efforts to do so.

I have not looked at your package.  But I was a little surprised that the 
proposed backport of 4.14.0-1 was versioned 4.14.0-1.1~bpo8+1.   I did read 
through http://backports.debian.org/Contribute/ (thanks to Mattia Rizzolo for 
the reference!) and under the "basic rules" it says to simply append "~bpo..." 
to the version.  Do you really also need to change from "-1" to "-1.1"? 

Best,
-Steve


On January 2, 2016 12:13:59 PM Gianfranco Costamagna wrote:
> Control: tags -1 moreinfo
> 
> Hi Matthias, if you need a backport, please ask the team or the previous
> uploaders to perform it.
> 
> I cced the actual maintainers for the package, they will follow up with an
> upload if possible (I hope).
> 
> BTW this kind of requests are usually performed with a bug against the
> package, unless the package is mostly unmaintained.
> 
> cheers,
> 
> G.
> 
> 
> 
> 
> Il Sabato 2 Gennaio 2016 11:34, Matthias Erich Popp <oquo8...@gmx.de> ha
> scritto: Package: sponsorship-requests
> Severity: normal
> 
> Package: sponsorship-requests
>   Severity: normal
> 
>   Dear mentors,
> 
>   I am looking for a sponsor for my package "digikam"
> 
> * Package name: digikam
>Version : 4:4.14.0-1.1~bpo8+1
> * URL : http://www.digikam.org
>Section : graphics
> 
>   It builds those binary packages:
> 
> digikam- digital photo management application for KDE
> digikam-data - digiKam architecture-independant data
> digikam-doc - handbook for digiKam
> digikam-private-libs - private libraries for digiKam and kipi plugins
> kipi-plugins - image manipulation/handling plugins for KIPI aware programs
> kipi-plugins-common - kipi-plugins architecture-independent data
> showfoto   - image viewer/editor for KDE
> 
>   To access further information about this package, please visit the
> following URL:
> 
>  http://mentors.debian.net/package/digikam
> 
> 
>   Alternatively, one can download the package with dget using this command:
> 
> dget -x
> http://mentors.debian.net/debian/pool/main/d/digikam/digikam_4.14.0-1.1~bpo8
> +1.dsc
> 
>   More information about hello can be obtained from http://www.example.com.
> 
>   Changes since the last upload:
> 
>   * Non-maintainer upload.
>   * Rebuild for jessie-backports.t changelog entry]
> 
> 
>   Regards,
>Matthias Erich Popp
> 
> 
> 
> -- System Information:
> Debian Release: 8.2
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (450,
> 'stable'), (4, 'testing'), (3, 'unstable'), (2, 'oldstable') Architecture:
> amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.2.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

the new package is available on the mentors site:

https://mentors.debian.net/package/eclipse-titan

BR,
Gergely

2016-01-13 14:13 GMT+01:00 Gianfranco Costamagna <
costamagnagianfra...@yahoo.it>:

> Hi,
> >The new package is done, everything is fixed, I hope. I didn't changed
> anything in the source, just under the debian/ directory. Should I upload
> the package as >before or use the dquilt method as
> https://www.debian.org/doc/manuals/maint-guide/update suggests?
> >If I'm right, the update method is for the change in the upstream source,
> or?
>
>
> please read
>
> http://mentors.debian.net/intro-maintainers
>
> (TL:TR)
> gbp buildpackage -S -sa
> dput mentors ../filename_foo_source.changes
>
>
> cheers
>
> G.
>

Bug#809451: sponsorship-requests: librep/0.92.5-1 [ITA]

[Jose M Calhariz]

On 09/01/16 21:07, Mattia Rizzolo wrote:
> On Sat, Jan 09, 2016 at 06:57:08PM +, Jose M Calhariz wrote:
>>> I'm going to try rebuilding the rdeps in the later today or tomrrow, and
>>> I'll report back the results.
>> Ok.
> that clearly fails because the header moved from e.g. rep.h =>
> rep/rep.h.
> Well, guess thtat's expected, also the two rdeps come from the same
> project so well, guess we're just going to upload this to experimental,
> and prepare the 2 rdeps later (that you said you're going to adopt,
> actually you own only 1 ITA, btw).

Fixed the ITA.

>
>> I have trimed the changelog.  Is not yet very good, but I hope that is
>> good enough.
> that's quite up to you, except some bits.
> the rewrite of d/copyright using copyright-format-1.0 should be
> documented, the rest looks documented enough to me.
>
>> And I will talk with upstream about this things.
> cool.
>
>
> ok, once you do this I'll upload, and we shall go one with one r-dep,
> I'd say, wouldn't you? :)
>

The next r-dep neads to be rep-gtk, the sawfish needs the newer versions
of librep and rep-gtk.


Kind regards
Jose M Calhariz





signature.asc
Description: OpenPGP digital signature

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

just a quick report on my progress...

2015-12-17 18:18 GMT+01:00 Mattia Rizzolo :

>
> Ok, first, a question: do you do your debian packaging in git?
>

I'm cloning form a git repository, then clean up everything which is git
related. Why do you ask? Is there a problem with that?


And, here is a review:
>
> * trailing whitespace on the changelog line.
>

FIXED


> * maybe you're happy to discover tools like `wrap-and-sort`, to wrap the
>   Build-Depends and Depends line (and sort other stuff, and removing
>   trailing whitespaces in some other files)
>

Thank you for the hint, it's a really useful tool. ;)


> * please don't cp files that way in d/rules, I find that ugly. instead,
>   use a debian/eclipse-titan.install file.  See dh_install(1) for more
>   info.  On a related note, I prefer using $(CURDIR) instead of $$(pwd)
>   + this will also make debian/eclipse-titan.dirs useless
>   + if you need to rename files dh-exec can help you a bit, if you want
>

FIXED


> * during the compilation there are several errors like
> ./TTCN3.hh:58:39: fatal error: RT1/TitanLoggerApiSimple.hh: No such
> file or directory
>   is this to be expected & ok?
>

It's expected and it's OK.


> * is there a way to have a more verbose build, showing all the command
>   line?
>

Added --verbose to debian/rules, I hope it'll help.


> * you told me that you could get it to build with hardening-wrapper,
>   well, to me it doesn't (see below) :)
>

Working on it, currently I don't know what is the reason of this. :/


> * can you enable parallel building? (see debhelper(7))
>

DONE


> * debian/copyright is totally inadequate.
>   + personally I won't be totally happy without a copyright following
> copyright-format 1.0
>   + anyway, please pick a random package from the archive and try having
> a look at what a copyright file normally looks like.
>

Will do after the hardening issue is resolved.

I move forward a little bit slow because I had a lot to do in these days
but now I can work on this almost full time, so I'll back to you soon with
all these corrections done I hope. ;)

Happy New Year
Gergely Pilisi