From: Michael Tremer <michael.tremer@ipfire.org>
To: Valters Jansons <valter.jansons@gmail.com>
Cc: location@lists.ipfire.org
Subject: Re: [PATCH] debian: Update libloc1.symbols for version 0.9.18
Date: Mon, 10 Mar 2025 21:13:27 +0000 [thread overview]
Message-ID: <B03BE429-8F21-4B8D-8D25-C54B9517BA10@ipfire.org> (raw)
In-Reply-To: <20250310204707.57029-1-valter.jansons@gmail.com>
Thank you! Merged!
> On 10 Mar 2025, at 20:47, Valters Jansons <valter.jansons@gmail.com> wrote:
>
> ---
> This seems to have been forgotten during tagging of 0.9.18.
>
> debian/libloc1.symbols | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/debian/libloc1.symbols b/debian/libloc1.symbols
> index 3770535..e4acb2b 100644
> --- a/debian/libloc1.symbols
> +++ b/debian/libloc1.symbols
> @@ -1,6 +1,7 @@
> libloc.so.1 libloc1 #MINVER#
> * Build-Depends-Package: libloc-dev
> LIBLOC_1@LIBLOC_1 0.9.4
> + LIBLOC_2@LIBLOC_2 0.9.18
> loc_as_cmp@LIBLOC_1 0.9.4
> loc_as_get_name@LIBLOC_1 0.9.4
> loc_as_get_number@LIBLOC_1 0.9.4
> @@ -101,6 +102,7 @@ libloc.so.1 libloc1 #MINVER#
> loc_network_overlaps@LIBLOC_1 0.9.5
> loc_network_prefix@LIBLOC_1 0.9.5
> loc_network_ref@LIBLOC_1 0.9.4
> + loc_network_reverse_pointer@LIBLOC_2 0.9.18
> loc_network_set_asn@LIBLOC_1 0.9.4
> loc_network_set_country_code@LIBLOC_1 0.9.4
> loc_network_set_flag@LIBLOC_1 0.9.4
> @@ -109,6 +111,7 @@ libloc.so.1 libloc1 #MINVER#
> loc_network_unref@LIBLOC_1 0.9.4
> loc_new@LIBLOC_1 0.9.4
> loc_ref@LIBLOC_1 0.9.4
> + loc_set_log_callback@LIBLOC_1 0.9.18
> loc_set_log_fn@LIBLOC_1 0.9.4
> loc_set_log_priority@LIBLOC_1 0.9.4
> loc_unref@LIBLOC_1 0.9.4
> --
> 2.48.1
>
>
prev parent reply other threads:[~2025-03-10 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 20:47 Valters Jansons
2025-03-10 21:13 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B03BE429-8F21-4B8D-8D25-C54B9517BA10@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=location@lists.ipfire.org \
--cc=valter.jansons@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox