Dear mentors,

I am looking for a sponsor for my package "libcap-ng":

  * Package name    : libcap-ng
    Version         : 0.7.9-3
    Upstream Author :
  * URL             : https://people.redhat.com/sgrubb/libcap-ng
  * License         :
  * Vcs             : https://salsa.debian.org/haava/libcap-ng
    Section         : libs

The source builds the following binary packages:

   libcap-ng-dev - Development and header files for libcap-ng
   libcap-ng0 - alternate POSIX capabilities library
   libcap-ng-utils - Utilities for analysing and setting file
capabilities
   python3-cap-ng - Python3 bindings for libcap-ng

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

https://mentors.debian.net/package/libcap-ng/

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

   dget -x
https://mentors.debian.net/debian/pool/main/libc/libcap-ng/libcap-ng_0.7.9-3.dsc

Changes since the last upload:

  libcap-ng (0.7.9-3) unstable; urgency=medium
  .
    * New maintainer Closes: #1011366
    * d/control:
      - Change architecture to linux-any. Closes: #961966
      - Apply multiarch hints for package libcap-ng-dev. Closes: #983476
      - Bump debhelper to version 13.
      - Remove no longer needed build-dependencies; dh-autoreconf and
        autotools-dev
      - Remove trailing-whitespace.
      - Remove duplicated section field.
      - Change to secure URI for homepage.
      - Move package into Vcs repository.
      - Document Rules-Requires-Root.
      - Update package description.
    * Drop d/compat, use debhelper-compat in d/control instead.
    * d/not-installed: Don't install .la files.
    * d/watch:
      - Remove unnecessary comments and empty lines.
      - Bump to version 4.
      - Use secure URI.
    * Change patches to gbp-pq format.
    * d/p/02_fix_armel_segfault_memset.patch: Add DEP-3 compliant header.
    * Build Python library for all supported Python3 versions and specify
      correct module name regarding autodep8 tests. Closes: #973276
    * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository
      and Repository-Browse.
    * wrap-and-sort


There is still some work to be done, including a newer release, it will
be handled in a separate upload, if/when this ITS goes through.

Regards,
Håvard

Thanks for salvaging! Uploaded to DELAYED/7 as requested.
I have forked the salsa repo to debian namespace and invited you.
Also, made some trivial changes.

Thanks for the sponsoring Bastian!
I know the package is already uploaded, but is this a hard requirement
for you? I would prefer to have it under my own namespace.
I noticed you updated the copyright, thanks.
I deliberately put that part of, since I needed to update it after the
inclusion of the latest upstream release anyway. Nothing major, but it
would save me some time to not go through the files twice.


Håvard

Am 10.06.22 um 17:35 schrieb Håvard F. Aasen:

Kind of. If (when) you become unresponsive and someone else is taking over the package, we can keep that.
I would really like to keep it that way. Please tag the uploaded version when it has arrived in the archive.

Not sure if I agree with you on this one, you proved yourself how easy
it is to move the repository, this will be just as easy if I become
unresponsive at a later time.
Most of my worries is because of [1]. By placing it in the Debian
namespace it is now in the "Debian Team" where every DD can do
whatever they want.
Will do.

I will keep the repo in the Debian namespace for now and not push
this further, but personally I feel that demanding packages to be
part of a team isn't the best approach.


[1]
https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22Debian.22_group

That "whatever" indeed include
smart, good, needed, desired and even stupid things.

Aiming for perfect is good, reaching good is much better.


Groeten
Geert Stappers
DD


P.S.

In an ideal world will happen a stupid thing only once.

[1] https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22Debian.22_group