From: David Sterba <dsterba@suse.cz>
To: David Sterba <dsterba@suse.cz>
Cc: "Swâmi Petaramesh" <swami@petaramesh.org>,
"David Sterba" <dsterba@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 5.3.1
Date: Tue, 29 Oct 2019 15:47:23 +0100 [thread overview]
Message-ID: <20191029144723.GW3001@twin.jikos.cz> (raw)
In-Reply-To: <20191029141904.GV3001@twin.jikos.cz>
On Tue, Oct 29, 2019 at 03:19:04PM +0100, David Sterba wrote:
> On Fri, Oct 25, 2019 at 11:10:24PM +0200, Swâmi Petaramesh wrote:
> > Hi,
> >
> > Le 25/10/2019 à 14:15, David Sterba a écrit :
> > > btrfs-progs version 5.3.1 have been released.
> > >
> > > This fixes (only) linking against libbtrfs (reported by snapper users).
> > > I did houpefully enough testing, the CI is green, builds on various arches, and
> > > snapper running with the library from 5.3.1 works.
> >
> > Now it looks unhappy on my #Arch...
> >
> >
> > root@zafu:/# inxi -S
> > System: Host: zafu Kernel: 5.3.7-arch1-1-ARCH x86_64 bits: 64
> > Desktop: Cinnamon 4.2.4 Distro: Arch Linux
> >
> > root@zafu:/# pacman -Qs btrfs-progs
> > local/btrfs-progs 5.3-1
> > Btrfs filesystem utilities
> >
> > root@zafu:/# pacman -Qs snapper
> > local/snap-pac 2.3.1-1
> > Pacman hooks that use snapper to create pre/post btrfs snapshots
> > like openSUSE's YaST
> >
> > root@zafu:/# snapper list
> > snapper: symbol lookup error: /usr/lib/libbtrfs.so.0: undefined symbol:
> > write_raid56_with_parity
>
> write_raid56_with_parity should be considered internal symbol and
> snapper does not use it. I'll have a look how Arch builds snapper.
I've grabbed built packages from
https://www.archlinux.org/packages/staging/x86_64/btrfs-progs/download/
(v5.3.1)
and https://www.archlinux.org/packages/core/x86_64/btrfs-progs/download/
(v5.3)
and the files /usr/lib/libbtrfs.so.0.1 are exactly the same:
$ md5sum progs-5.3*/usr/lib/libbtrfs.so.0.1
34a5ae4d38c5831e620b5ece52c04340 progs-5.3.1/usr/lib/libbtrfs.so.0.1
34a5ae4d38c5831e620b5ece52c04340 progs-5.3/usr/lib/libbtrfs.so.0.1
The file size is 371000 but this should be, because 5.3.1 added several
.o files and on openSUSE the file size grew from ~400KB to ~2MB.
As the PKGBUILD probably only bumps version, I verified that the
kernel.org tarballs indeed contain the right sources and buid with
defaults produces the right library.
So this seems to be something fishy on Arch side, like stale build or I
don't know.
prev parent reply other threads:[~2019-10-29 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 12:15 Btrfs progs release 5.3.1 David Sterba
2019-10-25 21:10 ` Swâmi Petaramesh
2019-10-29 14:19 ` David Sterba
2019-10-29 14:47 ` David Sterba [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=20191029144723.GW3001@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.org \
/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;
as well as URLs for NNTP newsgroup(s).