On Mon, 2017-02-06 at 12:54 +0200, Panu Matilainen wrote: > On 02/06/2017 01:21 AM, Zbigniew Jędrzejewski-Szmek wrote: > > On Sun, Feb 05, 2017 at 11:02:16PM +0100, Igor Gnatenko wrote: > > > On Sun, 2017-02-05 at 18:29 +0000, Zbigniew Jędrzejewski-Szmek wrote: > > > > systemd.spec file has > > > > %ifarch %{ix86} x86_64 aarch64 > > > > BuildRequires: gnu-efi gnu-efi-devel > > > > %endif > > > > > > > > ... and this seems to work fine in mock/koji/etc. > > > > > > > > dnf builddep deals file with an srpm built on the architecture: > > > > $ fedpkg clone -a systemd && cd systemd && fedpkg srpm > > > > $ sudo dnf builddep *.src.rpm > > > > (ok) > > > > > > > > But the following command fails on ppc64le: > > > > $ sudo dnf builddep systemd > > > > No matching package to install: 'gnu-efi' > > > > No matching package to install: 'gnu-efi-devel' > > > > Not all dependencies satisfied > > > > Error: Some packages could not be found. > > > > > > > > I'm confused: this seems like an error in dnf, or am I doing something > > > > wrong? > > > > > > SRPMs are distributed only once, so it's matter of luck which one will be > > > distributed. > > > > Hm, OK. I see why it is like this, but this limitation makes the > > command much less useful. Maybe at least the dnf.plugin.builddep man > > page should warn about this? > > I'd say dnf builddep should by default extract the spec out of the > src.rpm and parse the spec locally for build-deps. There needs to be an > option for using the metadata in src.rpm directly though, because using > it IS perfectly sane when you do it like the buildsys does. But it means that you need to have all BuildRequires installed in order to run all scrips which are used from spec. Moreover, it's security hole. > > - Panu - > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- -Igor Gnatenko
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx