On Mon, Oct 28, 2024 at 09:07:59AM +0100, Florian Weimer wrote:
> * Kevin Fenzi:
> 
> > As a side note, I removed s309x from the noarch_arches when that was
> > going on, but I have readded it a while back. (So noarch builds could
> > also happen on s390x). Also, changes in koji 1.35 meant that srpm build
> > tasks just use noarch_arches, so they too can happen on s390x. I've been
> > watching things and so far this doesn't seem to be a problem.
> 
> I was recently bitten by “fedpkg srpm” (or “fedpkg build --scratch
> --srpm”) not yet using --arch noarch for constructing the source RPM. 8-/

I think the idea is that a src.rpm should be the same constructed on any
arch... ie, 
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_no_arch_specific_sources_or_patches
> 
> > Also, longer term for ppc64le I have put in for budget next year to add
> > memory/faster disks and there is also possibly power10 on the horizon,
> > which I hope will be faster/biggger.
> 
> Historically, Red Hat's POWER systems used desktop-class disks and had
> very poor I/O as a result.  Builds can be quite I/O heavy, and
> minute-long hangs during initial package installation were not uncommon.
> These systems are supposed to be use with a SAN, but I don't think we
> have that.

Yeah, thats another option, we do sort of have. I would have to try and
find space for it and time to setup a iscsi volume and see if it helps
any. The local ssd/nvme is a lot cheaper/less interdependent though.

kevin

Attachment: signature.asc
Description: PGP signature

-- 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to