Re: [EPEL-devel] Re: %{python3} no defined in epel-7-aarch64?

[Florian Weimer]

* Miro Hrončok:

> Yes. The macro was added to EPEL 7 only after aarch64 was discontinued there:
>
> https://lists.fedoraproject.org/archives/list/epel-annou...@lists.fedoraproject.org/thread/YVLZGTBBW2M3GMXHLIA2QMKENBEGPEJY/
>
> No easy way to solve this except to stop building for aarch64 on EPEL
> 7. You could use the %__python3 macro instead to workaround this
> particular problem, but you will most likely hit another one later.

aarch64 is completely EOL on 7, so you should just stop building it.
There is no Extended Update Support and no Extended life cycle support
for it.



Thanks,
Florian
-- 
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.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.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

Re: faccessat2 support in COPR

[Florian Weimer]

* Jakub Kadlcik:

> Hello Florian,
> I must confess that this is a too system-level topic for me to
> comprehend, but I read the BZ 1869030 you linked and I think your
> question boils down to this?
>
>> In summary:
>> - We need to check with COPR admins to see if their systemd-nspawn is new 
>> enough to drop the patch.
>
> At this moment, Copr builders are F32 instances spawned from our
> snapshot, that was created Sep 18 2020, and therefore contain package
> versions from that date. We have systemd-container installed in
> 245.7-1 version but on that system 245.8-2 is available. We can update
> the snapshot for you, if necessary. In case even newer version is
> required, please let me know where to get it.
>
> I hope I am not misunderstanding the question completely.

Sorry for being unclear.  I'm glad you could figure out what we needed;
the information you provided was very helpful:

Upstream systemd 245.8 lists the faccessat2 commit here:



I don't think this is in 245.7, so you would have to upgrade.  Could you
do that, please, and tell us afterwards, so that we can proceed to
remove the kludge from glibc?

Thanks,
Florian
-- 
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.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.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

faccessat2 support in COPR

[Florian Weimer]

Do the COPR environments either support faccessat2 or fail with ENOSYS?

I've been told that we put in a workaround in glibc for the bogus EPERM
error from systemd-nspawn specifically to support COPR:

  

And we really need to remove that workaround again because EPERM is an
ambiguous error code and applies to situations where we *do not* want to
perform the fallback implementation (because it cannot perform
permission checks accurately).

Thanks,
Florian
-- 
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.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.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org

CI-style package builds from a Git repository

[Florian Weimer]

Is there a way to get Copr to build binary packages directly from a Git 
repository?  I do not need the SRPM, and I don't want to bother with 
revision and %changelog updates.


I tried an SCM-1 style repository (I think), but the generated SRPM only 
had the spec file, which is not what I want.


I used to have a private builder which did exactly that for Debian 
packages, and it was extremely helpful for distributing software.  And 
if Copr isn't the tool for that, what is?


Thanks,
Florian
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org