From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4ZBV4968frz3774 for ; Mon, 10 Mar 2025 21:13:29 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) client-signature RSA-PSS (4096 bits)) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4ZBV486XjVz2ywk for ; Mon, 10 Mar 2025 21:13:28 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4ZBV475bTcz28b; Mon, 10 Mar 2025 21:13:27 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1741641207; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VEEo8t6EF/uPjahZ/n5hpGvakLfs/gUu2xv96rY4qA4=; b=fjeuIZOPNRfj4BO/hnPdMvXHH1n8uhr1gm6ka8kEyScYzFBdak5spx072jlvizD1MFM4Mx sxASzyDEdzDyv5DA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1741641207; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VEEo8t6EF/uPjahZ/n5hpGvakLfs/gUu2xv96rY4qA4=; b=l/JVt8T7IA8E7XTBVSpvP5N8woXdfa2FeQmtwwHYuW3dGooTDnUw5OM8QiYpsmG1H0q2cF g3qSPJNnlyrtu+qtYe+jMMDb+ePNsaNNzYJ3KeO9J3/3gBTbVmZNO+QAVkTM83H1+UntXF W3bMMzeJ+TvGEnkDCdVplN8Y+z2duvDOZ6uLd6u8xD09E5CAv1C/i6AVsEULxpf419NHSX MxIlvsjlXC0xlB3nRnaDjYi/9BGijVHnEJNSxM6ZnagSs+4/JKy7lfwrf+TS/Ht7E4gGPB Dn9I2qXfN6MqJYnNnvzyW7Qtte5A8vzcggkEZTNEUwF8X+C+Pn+nwUS4D7SRdw== Content-Type: text/plain; charset=us-ascii Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: [PATCH] debian: Update libloc1.symbols for version 0.9.18 From: Michael Tremer In-Reply-To: <20250310204707.57029-1-valter.jansons@gmail.com> Date: Mon, 10 Mar 2025 21:13:27 +0000 Cc: location@lists.ipfire.org Content-Transfer-Encoding: 7bit Message-Id: References: <20250310204707.57029-1-valter.jansons@gmail.com> To: Valters Jansons Thank you! Merged! > On 10 Mar 2025, at 20:47, Valters Jansons 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 > >