From: Nicholas D Steeves <sten@debian.org>
To: John Center <jlcenter15@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 5.18
Date: Sat, 28 May 2022 16:18:21 -0400 [thread overview]
Message-ID: <87v8tpe7hu.fsf@DigitalMercury.freeddns.org> (raw)
In-Reply-To: <95422f7b-e0f9-c716-212e-ee1007176d7e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
John Center <jlcenter15@gmail.com> writes:
> Hi,
>
> I usually build the btrfs-progs when it comes out. I've upgraded from
> Ubuntu 20.04 to 22.04 & I'm having a problem with configure looking for
> ext2fs. I have e2fsprogs & libext2fs2 installed, but it fails with "No
> package 'ext2fs' found". What am I missing?
>
> Thanks!
>
> -John
>
You'll need e2fslibs-dev and other -dev packages. The easiest way to
get all of these dependencies in one go is probably to get a copy of the
Debian/Ubuntu source package. To do this create "deb-src" lines based on
the "deb" lines in your /etc/apt/sources.list, and
apt update
apt source btrfs-progs
Then
cd btrfs-progs
and finally
apt build-dep ./
Then build the package as normal. Note that this won't take care of any
new dependencies (if any) added since the version of btrfs-progs
released with 22.04.
I think synaptic might be able to create the "deb-src" lines, and
there's probably a GUI repository manager program that can do this, but
I'm not familiar with these methods. I'm sure you'll figure it out
though! Worst case scenario would be manually installing the -dev
packages for all missing dependencies; there are at least eight or
nine of these.
Cheers,
Nicholas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
prev parent reply other threads:[~2022-05-28 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 14:06 Btrfs progs release 5.18 David Sterba
2022-05-28 0:20 ` John Center
2022-05-28 1:34 ` Qu Wenruo
2022-05-28 1:51 ` John Center
2022-05-28 20:18 ` Nicholas D Steeves [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=87v8tpe7hu.fsf@DigitalMercury.freeddns.org \
--to=sten@debian.org \
--cc=jlcenter15@gmail.com \
--cc=linux-btrfs@vger.kernel.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