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

Bug#1058883: marked as done (RFS: libhx/4.19-1 -- Documentation files for libhx)

Your message dated Mon, 29 Jan 2024 08:55:15 +0100
with message-id <ZbdZ48sFoypRg38f@frost.de>
and subject line Re: Bug#1058883: RFS: libhx/4.19-1 -- Documentation files for libhx
has caused the Debian Bug report #1058883,
regarding RFS: libhx/4.19-1 -- Documentation files for libhx
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.)


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

   Package name     : libhx
   Version          : 4.19-1
   Upstream contact : Jan Engelhardt <jengelh@inai.de>
   URL              : https://inai.de/projects/libhx/
   License          : GPL-2+, LGPL-2.1+, WTFPL-2+
   Vcs              : https://git.jff.email/cgit/libhx.git
   Section          : libs

The source builds the following binary packages:

  libhx32 - C library providing queue, tree, I/O and utility functions
  libhx-dev - Development files for libhx
  libhx-doc - Documentation files for libhx

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/libh/libhx/libhx_4.19-1.dsc

or from

 git https://git.jff.email/cgit/libhx.git/?h=release%2Fdebian%2F4.19-1

or

 git (old) https://jff.email/cgit/libhx.git/?h=release%2Fdebian%2F4.19-1


Changes since the last upload:

 libhx (4.19-1) unstable; urgency=medium
 .
   * New upstream release.
     - Refresh symbols files.
   * Remove empty debian/libhx-dev.symbols.
   * debian/rules:
     - Remove build of libhx-dev.symbols.


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
D-54470 Lieser


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

Skype:    jff-skype@jff.email
Jami:     joergfringsfuerst
Telegram: @joergfringsfuerst
Matrix:   @joergff:matrix.snct-gmbh.de

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 --- 
Hi Jörg,

Am Sun, Dec 17, 2023 at 03:15:39PM +0100 schrieb Jörg Frings-Fürst:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "libhx":
> 
>    Package name     : libhx
>    Version          : 4.19-1
>    Upstream contact : Jan Engelhardt <jengelh@inai.de>
>    URL              : https://inai.de/projects/libhx/
>    License          : GPL-2+, LGPL-2.1+, WTFPL-2+
>    Vcs              : https://git.jff.email/cgit/libhx.git
>    Section          : libs
> 
Uploaded, thanks for your contribution.

If you find time, maybe you can fix those broken initian overrides:

I: libhx-dev: unused-override no-code-sections  [usr/share/lintian/overrides/libhx-dev:5]
I: libhx-dev: unused-override package-name-doesnt-match-sonames libHX-rtcheck [usr/share/lintian/overrides/libhx-dev:2]
I: libhx-dev: unused-override shared-library-lacks-prerequisites [usr/lib/x86_64-linux-gnu/libHX_rtcheck.so] [usr/share/lintian/overrides/libhx-dev:4]
I: libhx-dev: unused-override shared-library-lacks-version usr/lib/x86_64-linux-gnu/libHX_rtcheck.so libHX_rtcheck.so [usr/share/lintian/overrides/libhx-dev:3]

-- 
tobi

--- End Message ---
Reply to: