[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1112455: marked as done (RFS: libonig/6.9.10-1 -- regular expressions library)

Your message dated Thu, 11 Sep 2025 22:34:29 +0200
with message-id <aMMyVUp23AmmV_pK@fernst.no-ip.org>
and subject line Re: Bug#1112455: RFS: libonig/6.9.10-1 -- regular expressions library
has caused the Debian Bug report #1112455,
regarding RFS: libonig/6.9.10-1 -- regular expressions library
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 owner@bugs.debian.org
immediately.)


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

Dear mentors,

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

 * Package name     : libonig
   Version          : 6.9.10-1
   Upstream contact : K.Kosako <kkosako0@gmail.com>
 * URL              : https://github.com/kkos/oniguruma
 * License          : BSD-2-clause, X11, FSFAP
 * Vcs              : https://git.jff.email/cgit/libonig.git
   Section          : libs

The source builds the following binary packages:

  libonig5 - regular expressions library
  libonig-dev - regular expressions library — development files

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/libo/libonig/libonig_6.9.10-1.dsc

or from

 git https://git.jff.email/cgit/libonig.git?h=release%2Fdebian%2F6.9.10-1


Changes since the last upload:

 libonig (6.9.10-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1097239).
     - Refresh symbols file.
   * Declare compliance with Debian Policy 4.7.2 (No changes needed).
   * debian/copyright:
     - Add year 2025 to myself.
     - Rewrite to make lrc happy.
   * debian/control:
     - Change Vcs-Git from git: to https:.

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


Jörg Frings-Fürst
DE-54470 Lieser
L-Għarb, Gozo, MT-GRB 1131


git:      https://git.jff.email/cgit/


Matrix:   @joergff:matrix.org

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

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


--- End Message ---
--- Begin Message --- 
Hello Jörg,

On Thu, Sep 11, 2025 at 08:29:56PM +0200, Jörg Frings-Fürst wrote:
> I have taken care of all the points.

Thanks! But you might want to s/obsolate/obsolete/ in d/changelog for
some future upload. ;-)

Hmm, what about these two items?

| Then there is a multi-arch hint "libonig-dev could be marked Multi-Arch:
| same" as listed on <https://tracker.debian.org/pkg/libonig>. Do you
| agree with this hint?
| 
| Now, given that libonig has seen quite some success, e.g. with it being
| a dependency of the popular "jq" tool, wouldn't it be beneficial to add
| some autopkgtests, maybe based on upstream's samples? Do you have any
| plans on this?

No show-stopper for now, but just wondering ...

> Libonig ist uploaded to mentors and into the git.

And now also locally built, signed, checked, and then uploaded.
Thus closing this RFS. Thank you for your continued contribution!

> I will consider your suggestion for a new upstream
> in the near future.

Well, let's see how the ecosystem will develop ...

Cheers,
Flo

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: