From patchwork Thu Feb 20 11:16:30 2025 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Adolf Belka X-Patchwork-Id: 8469 Return-Path: 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) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R11" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4Yz9gv5npFz3wbt for ; Thu, 20 Feb 2025 11:16:43 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (secp384r1) client-digest SHA384) (Client CN "mail02.haj.ipfire.org", Issuer "E5" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4Yz9gq1fHTznn; Thu, 20 Feb 2025 11:16:39 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4Yz9gp658Pz340B; Thu, 20 Feb 2025 11:16:38 +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) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R11" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4Yz9gl6QXCz30XF for ; Thu, 20 Feb 2025 11:16:35 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4Yz9gk51GTzWR; Thu, 20 Feb 2025 11:16:34 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1740050194; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=GHBZbQUiM1kRpW/2jl5e+GqJxizE5crkori2QoCVpgw=; b=d7k3Qm0lIQTH95Fdsid69BD14G7GpRGmgDPlchLMlTWz76KFCBYlltPPq3JmnLxKPdUC3e BNwPoJ830Cb0EnBw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1740050194; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=GHBZbQUiM1kRpW/2jl5e+GqJxizE5crkori2QoCVpgw=; b=VTeBAzU43D3IdN4WtkiqYV51TfIwQB8yBlGl6cnCOqGWX2WXYMZGNnwZ03mSOw1q3yhudE KcIF8uCrnQ3OCc2vqwf3XCtXiqZW20HkSxzPtP2fhQs+SiCEjmDrBuYE4I7QSdYArlMKBy 6/ODd8pOeGcDq2JqWg9D5yIQN+LTwaO1y4qhlF7j8qfYru6NUzZgB2mHyxZ+qBnk9xW3So gYFlv1UQp3TKwdk3hd5r0EfvViqY3FXNeepnnfVQu4BMO15Sg3Kw6rIhQigWzO9PcOnWGD RvhnjFBA6kYlw0hBjg3e2uniJRggPQKJBIonGxoQaJ2iBxfx3MNH2ToCJKTQCg== From: Adolf Belka To: development@lists.ipfire.org Subject: [PATCH 1/2] libyang: Update to version 3.7.8 Date: Thu, 20 Feb 2025 12:16:30 +0100 Message-ID: <20250220111631.5454-1-adolf.belka@ipfire.org> MIME-Version: 1.0 Message-ID-Hash: AGFLF5PDVJHCSNLABZ6OAGGK2TQDIWCY X-Message-ID-Hash: AGFLF5PDVJHCSNLABZ6OAGGK2TQDIWCY X-MailFrom: adolf.belka@ipfire.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.8 Precedence: list List-Id: IPFire development talk Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: - Update from version 2.1.148 to 3.7.8 - Update of rootfile - Submited as a set with a PAK_VER update of frr as frr needs to be shipped to use this new version. - In the changelog for moving the library from 2.x to 3.0 it mentions that there are some breaking changes but then says they are minor. The library versions are not alligned with the package version numbers. Following is what is said:- * Non-backwards-compatible changes between libyang version 2 and 3 are rather minor and can be summarized as providing * structured error information (instead of a single message), unifying **lyd_new_*()** function options, and some * minor changes such as removing deprecated functions or making a few functions inlined. However, there is another * large change that has not affected the API, specifically configuration system-ordered lists and leaf-lists are now * ordered based on their keys/values, respectively. Except for moderately slower performance and negligible increased * memory requirements, it should not affect existing applications (assuming they do not rely on the previous order of * these instances). - I tested this updated version of libyang with frr. frr built without any problems. It just has the requirement that libyang >= 2.1.128, so no restriction that it must not be version 3. I then installed the IPFire built with the updated libyang and installed the frr that was built with it. I was able to start frr successfully, so all the specified frr daemons successfully started. - I could only test that frr successfully had all the daemons start but could not test out actual functioning of frr as this is something I have never used. I would expect that if all the daemons start successfully then frr should be happy working with libyang-3.7.8 - Changelog 3.7.8 yanglint UTF8 support validation optimizations lots of bugfixes 3.4.2 data handling optimizations 32b build fixes various bugfixes 3.1.0 lots of improvements and bugfixes in various parts of the library 2.2.8 new SO version 3 with some non-backwards compatible changes transition manual from version 2 in docs (leaf-)list instance semantic ordering sorts instances based on their values or their key values minor performance cost logging API improved new parsing flag LYD_PARSE_STORE_ONLY avoids value validation run-time plugin support build improvements lots of other bugfixes and optimizations Tested-by: Adolf Belka Signed-off-by: Adolf Belka --- config/rootfiles/common/libyang | 6 +++--- lfs/libyang | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/config/rootfiles/common/libyang b/config/rootfiles/common/libyang index f06340422..2562e0229 100644 --- a/config/rootfiles/common/libyang +++ b/config/rootfiles/common/libyang @@ -1,13 +1,13 @@ #usr/bin/yanglint #usr/bin/yangre #usr/include/libyang -#usr/include/libyang/config.h #usr/include/libyang/context.h #usr/include/libyang/dict.h #usr/include/libyang/hash_table.h #usr/include/libyang/in.h #usr/include/libyang/libyang.h #usr/include/libyang/log.h +#usr/include/libyang/ly_config.h #usr/include/libyang/metadata.h #usr/include/libyang/out.h #usr/include/libyang/parser_data.h @@ -24,8 +24,8 @@ #usr/include/libyang/tree_schema.h #usr/include/libyang/version.h #usr/lib/libyang.so -usr/lib/libyang.so.2 -usr/lib/libyang.so.2.46.3 +usr/lib/libyang.so.3 +usr/lib/libyang.so.3.6.10 #usr/lib/pkgconfig/libyang.pc #usr/share/man/man1/yanglint.1 #usr/share/man/man1/yangre.1 diff --git a/lfs/libyang b/lfs/libyang index 49163a44d..fb35a1490 100644 --- a/lfs/libyang +++ b/lfs/libyang @@ -1,7 +1,7 @@ ############################################################################### # # # IPFire.org - A linux based firewall # -# Copyright (C) 2007-2024 IPFire Team # +# Copyright (C) 2007-2025 IPFire Team # # # # This program is free software: you can redistribute it and/or modify # # it under the terms of the GNU General Public License as published by # @@ -24,7 +24,7 @@ include Config -VER = 2.1.148 +VER = 3.7.8 THISAPP = libyang-$(VER) DL_FILE = $(THISAPP).tar.gz @@ -44,7 +44,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = e955958319a4ad8c241720c3a425ab2a298916b8ba34e91ff2b43bafaae65fb0d41c904af894d3c5025ab253a40cb6f4732137b195169785628f6cedeb054acb +$(DL_FILE)_BLAKE2 = c8a83babe5936e3c5bb80ea1d3762e8ad7db9f8e7cec5712f19559fe4de9605c87451360e8d75e36f897f608254ebc2322e3f6124c02f0cbe4cf8d38238f3b39 install : $(TARGET)