9:10 a.m.
Hi everyone,
I want to rebuild some of the fedora 33 packages for EL8 (vagrant, for
example), but I'm having trouble getting all of the build dependencies
right. I ran dnf to download the SRPMS with the --resolve option, but I'm
still missing dependencies when I submit the builds to copr.
My current workflow is to download an RPM from Fedora 33, then submit it to
copr to build on the EPEL8 image in my personal COPR projects, waiting for
any library errors, then download those and build, repeat as needed.
That workflow is tedious and I feel like there must be a better way, but I
don't know what that is. How can I recursively find all of the builddeps
for packages?
Ideally, I would like some type of (semi-)automated way to track packages
on Fedora and automatically build them on EL8, but I'm at a loss for how to
do so.
Thanks,
Jason
4:03 p.m.
On Sunday, November 15, 2020 3:10:03 PM WET Jason Edgecombe wrote:
Hi everyone,
I want to rebuild some of the fedora 33 packages for EL8 (vagrant, for
example), but I'm having trouble getting all of the build dependencies
right. I ran dnf to download the SRPMS with the --resolve option, but I'm
still missing dependencies when I submit the builds to copr.
My current workflow is to download an RPM from Fedora 33, then submit it to
copr to build on the EPEL8 image in my personal COPR projects, waiting for
any library errors, then download those and build, repeat as needed.
That workflow is tedious and I feel like there must be a better way, but I
don't know what that is. How can I recursively find all of the builddeps
for packages?
Ideally, I would like some type of (semi-)automated way to track packages
on Fedora and automatically build them on EL8, but I'm at a loss for how to
do so.
Thanks,
Jason
IIRC to deal with dependencies Jens Petersen's fbrnch should help you do that:
https://github.com/juhp/fbrnch
The package is available in copr:
https://copr.fedorainfracloud.org/coprs/petersen/fbrnch/
--
José Abílio
6:02 p.m.
Thanks José!
This looks promising, but I must admit that I don't understand enough of
the Fedora packaging process to really understand it. Can I use this for
personal projects without pushing it to the main Fedora packaging process?
I'm not totally opposed to becoming a full-blown package maintainer, but I
need to know a lot more before being willing to commit.
Thanks,
Jason
On Sun, Nov 15, 2020 at 5:04 PM José Abílio Matos <jamatos(a)fc.up.pt> wrote:
On Sunday, November 15, 2020 3:10:03 PM WET Jason Edgecombe wrote:
> Hi everyone,
>
> I want to rebuild some of the fedora 33 packages for EL8 (vagrant, for
> example), but I'm having trouble getting all of the build dependencies
> right. I ran dnf to download the SRPMS with the --resolve option, but I'm
> still missing dependencies when I submit the builds to copr.
>
> My current workflow is to download an RPM from Fedora 33, then submit it
to
> copr to build on the EPEL8 image in my personal COPR projects, waiting
for
> any library errors, then download those and build, repeat as needed.
>
> That workflow is tedious and I feel like there must be a better way, but
I
> don't know what that is. How can I recursively find all of the builddeps
> for packages?
>
> Ideally, I would like some type of (semi-)automated way to track
packages
> on Fedora and automatically build them on EL8, but I'm at a loss for how
to
> do so.
>
> Thanks,
> Jason
IIRC to deal with dependencies Jens Petersen's fbrnch should help you do
that:
https://github.com/juhp/fbrnch
The package is available in copr:
https://copr.fedorainfracloud.org/coprs/petersen/fbrnch/
--
José Abílio
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
8:23 p.m.
dnf builddep fedora-review.spec ? after reading what fbrnch does, I
remembered that
On Sun, 2020-11-15 at 10:10 -0500, Jason Edgecombe wrote:
Hi everyone,
I want to rebuild some of the fedora 33 packages for EL8 (vagrant,
for example), but I'm having trouble getting all of the build
dependencies right. I ran dnf to download the SRPMS with the --
resolve option, but I'm still missing dependencies when I submit the
builds to copr.
My current workflow is to download an RPM from Fedora 33, then submit
it to copr to build on the EPEL8 image in my personal COPR projects,
waiting for any library errors, then download those and build, repeat
as needed.
That workflow is tedious and I feel like there must be a better way,
but I don't know what that is. How can I recursively find all of the
builddeps for packages?
Ideally, I would like some type of (semi-)automated way to track
packages on Fedora and automatically build them on EL8, but I'm at a
loss for how to do so.
Thanks,
Jason
_______________________________________________devel mailing list --
devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
--
Sérgio M. B.
9:28 p.m.
On 2020-11-16 02:23 UTC, Sérgio Basto wrote:
dnf builddep fedora-review.spec ? after reading what fbrnch does, I remembered that
Unfortunately "dnf builddep" has a DESIGN error: it does not separate the task
"find the names of the missing packages" from the task "install
packages".
"find the names" should be performed without sudo, but dnf does not.
As a result, "sudo dnf builddep" can fail mysteriously:
https://bugzilla.redhat.com/show_bug.cgi?id=1663619
noon
On Sunday, November 15, 2020 4:10:03 PM CET Jason Edgecombe wrote:
Hi everyone,
I want to rebuild some of the fedora 33 packages for EL8 (vagrant, for
example), but I'm having trouble getting all of the build dependencies
right. I ran dnf to download the SRPMS with the --resolve option, but I'm
still missing dependencies when I submit the builds to copr.
My current workflow is to download an RPM from Fedora 33, then submit it to
copr to build on the EPEL8 image in my personal COPR projects, waiting for
any library errors, then download those and build, repeat as needed.
That workflow is tedious and I feel like there must be a better way, but I
don't know what that is. How can I recursively find all of the builddeps
for packages?
If you already have it built in copr, there's package-build-order script
in copr-cli that could help you to reconstruct the order from the
repository. It was created exactly for this purpose, but has not yet been
widely tested.
Pavel
Ideally, I would like some type of (semi-)automated way to track
packages
on Fedora and automatically build them on EL8, but I'm at a loss for how to
do so.
Thanks,
Jason
6:55 p.m.
On Sun, Nov 15, 2020 at 4:13 PM Jason Edgecombe <jason(a)rampaginggeek.com> wrote:
Hi everyone,
I want to rebuild some of the fedora 33 packages for EL8 (vagrant, for example), but
I'm having trouble getting all of the build dependencies right. I ran dnf to download
the SRPMS with the --resolve option, but I'm still missing dependencies when I submit
the builds to copr.
My current workflow is to download an RPM from Fedora 33, then submit it to copr to build
on the EPEL8 image in my personal COPR projects, waiting for any library errors, then
download those and build, repeat as needed.
That workflow is tedious and I feel like there must be a better way, but I don't know
what that is. How can I recursively find all of the builddeps for packages?
Ideally, I would like some type of (semi-)automated way to track packages on Fedora and
automatically build them on EL8, but I'm at a loss for how to do so.
Thanks,
Jason
That is a common [bootstrapping] problem, yes.
In short, you need to query the SRPM & RPM dependencies and their
runtime and build time dependencies, recursively. You also need to do
that on every architecture (due to the potential use of conditional
build deps), so your process should involve SRPM rebuilds as the ones
you download from Fedora repos have only been built on one; and it's
random -- there's a chance you won't be able to resolve your tree if
you use those. Binary RPMs are already available for all arches so you
just need to fetch the repodata.
You can do all this on a single host and arch, don't worry. No uploads
and actual RPM builds are necessary.
Once you have your package list, just compare it to your target
distribution's package list and you have your set.
It's no longer maintained and it was rather quirky buy could try
depchase; it did exactly this when we were experimenting with fully
modular distributions:
https://github.com/fedora-modularity/depchase
P
1251
days inactive
1260
days old
6 comments
6 participants
participants (6)
-
Jason Edgecombe -
John Reiser -
José Abílio Matos -
Pavel Raiskup -
Petr Šabata -
Sérgio Basto