From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C3DF03858D3C; Tue, 11 Oct 2022 09:49:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C3DF03858D3C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1665481771; bh=RDUvXUAE+i7cjHRCxpAg0RqhFcXQGPQShVWrSb+eVHU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=PPcV3i4p0MHCvxER5ke9wgYB0eCyjJTU/AAKKCqYxujYG4rYzGBampHNT+p7ICWhg qP/nVbuGwoxEQvRMo9aDDL9qNBrE1lWDeWqXV3hdxzFSt+yB9FwGhFwGYdJjj1zFfz df/GiuFUQxUU3OENa+qjJW6p383H+TIdWdSRg014= From: "dodji at seketeli dot org" To: libabigail@sourceware.org Subject: [Bug default/29650] "Assertion `__abg_cond__' failed." with with libabigail 2.1 Date: Tue, 11 Oct 2022 09:49:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: libabigail X-Bugzilla-Component: default X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dodji at seketeli dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dodji at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29650 --- Comment #12 from dodji at seketeli dot org --- Hello Ben, woodard at redhat dot com via Libabigail a =C3=A9crit: > Dodji can we consider a 2.1.1 fork beginning with this patch. There is always a tag for the latest released version. The last one is libabigail-2.1. >From that tag, if there the need for bugfix branch, I create a branch which name is -branch, and I cherry-pick the bug fixes into that branch. So in this case, the branch name would be libabigail-2.1-branch. I have just created it, with the relevant patches cherry-picked in it. I'll be maintaining that branch for this cycle, until 2.2. I try to avoid doing this because it's a bit more work, but when it's necessary, well, it's necessary. So it's available at https://sourceware.org/git/?p=3Dlibabigail.git;a=3Dshortlog;h=3Drefs/heads/= libabigail-2.1-branch. When I roll out libabigail-2.1-2 Fedora packages, they'll be cut from that branch. [...] Hello Romain, "romain.geissler at amadeus dot com via Libabigail" a =C3=A9crit: [...] > For abigail we don't use any official package, we rebuilt it from source,= so I > will chose the cherry-pick path. [...] Ok, so if you like, you might want to get the content of the branch 'libabigail-2.1-branch', browsable at https://sourceware.org/git/?p=3Dlibabigail.git;a=3Dshortlog;h=3Drefs/heads/= libabigail-2.1-branch, which contains all bugfixes that will be accumulated until 2.2 is released. [...] Cheers. --=20 You are receiving this mail because: You are on the CC list for the bug.=