[PATCH] lib: Fix symbol versioning inheritance
authorColin Walters <walters@verbum.org>
Wed, 8 Jun 2022 20:27:30 +0000 (16:27 -0400)
committerSimon McVittie <smcv@debian.org>
Sun, 19 Jun 2022 19:58:51 +0000 (20:58 +0100)
I messed this up; the last release should inherit from the previous
release (N-1) and not the previous to that (N-2).

I think (hope) this isn't an ABI break...

Just noticed this when I was going to add a new symbol.

Applied-upstream: 2022.4, commit:145d91d1c96755bc61a468b5da1061547909121e

Gbp-Pq: Name lib-Fix-symbol-versioning-inheritance.patch

src/libostree/libostree-released.sym
tests/test-symbols.sh

index 8b8a722d8a74dfdc21318e8c0e927138a4148ded..5afdfd3e223523f5d8f14f58867fd7750d104161 100644 (file)
@@ -681,7 +681,7 @@ LIBOSTREE_2022.4 {
 global:
   ostree_fs_get_all_xattrs;
   ostree_fs_get_all_xattrs_at;
-} LIBOSTREE_2021.5;
+} LIBOSTREE_2022.2;
 
 /* NOTE: Only add more content here in release commits!  See the
  * comments at the top of this file.
index a888ef358473316d1e3f31e11a4bd0ec2570b492..a14849d56e77780bd42d767e3f171af1df1b456d 100755 (executable)
@@ -54,7 +54,7 @@ echo 'ok documented symbols'
 
 # ONLY update this checksum in release commits!
 cat > released-sha256.txt <<EOF
-fb66f84d9af5270ed34fdf9f70f97e59394336a9559f493917704bdffa19027d  ${released_syms}
+34ff6c97e20242a449b210f7452a12d0bb6ac9e135638f71c2d27b2f2b583ef3  ${released_syms}
 EOF
 sha256sum -c released-sha256.txt