Re: Live USB iso boot not working since Fedora 37, still broken in 39 Beta

2023-10-05 Thread Leslie Satenstein via devel 
Please look at 

2241955 – Fedora 39 Wayland initialization code has something missing -- my 
system crashes

| 
| 
|  | 
2241955 – Fedora 39 Wayland initialization code has something missing --...


 |

 |

 |





Leslie Satenstein
 

On Thursday, October 5, 2023 at 04:51:35 p.m. EDT, Adam Williamson 
 wrote:  
 
 On Thu, 2023-10-05 at 16:36 -0400, Neal Gompa wrote:
> On Thu, Oct 5, 2023 at 4:03 AM Matthias Saou  wrote:
> > 
> > Hi,
> > 
> > I continued digging some more, and it turns out there is a one liner
> > fix for the issue that has been merged upstream:
> > 
> > https://github.com/dracutdevs/dracut/pull/2196
> > 
> > Would there be any hope to get this backported to be included in Fedora
> > 39? The scope of the change is ridiculously tiny, limited to this
> > single modules.d/90dmsquash-live/iso-scan.sh file which is exclusively
> > used for this broken feature.
> > 
> > It would be really great to get the final Fedora 39 iso working again.
> > 
> 
> An update has been proposed:
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-f71507e281

The bug still needs to be accepted as an FE for this to make final,
though. https://pagure.io/fedora-qa/blocker-review/issue/1382
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



___
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
  ___
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

Re: Live USB iso boot not working since Fedora 37, still broken in 39 Beta

2023-10-05 Thread Adam Williamson 
On Thu, 2023-10-05 at 16:36 -0400, Neal Gompa wrote:
> On Thu, Oct 5, 2023 at 4:03 AM Matthias Saou  wrote:
> > 
> > Hi,
> > 
> > I continued digging some more, and it turns out there is a one liner
> > fix for the issue that has been merged upstream:
> > 
> > https://github.com/dracutdevs/dracut/pull/2196
> > 
> > Would there be any hope to get this backported to be included in Fedora
> > 39? The scope of the change is ridiculously tiny, limited to this
> > single modules.d/90dmsquash-live/iso-scan.sh file which is exclusively
> > used for this broken feature.
> > 
> > It would be really great to get the final Fedora 39 iso working again.
> > 
> 
> An update has been proposed:
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-f71507e281

The bug still needs to be accepted as an FE for this to make final,
though. https://pagure.io/fedora-qa/blocker-review/issue/1382
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



___
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

Re: Live USB iso boot not working since Fedora 37, still broken in 39 Beta

2023-10-05 Thread Neal Gompa 
On Thu, Oct 5, 2023 at 4:03 AM Matthias Saou  wrote:
>
> Hi,
>
> I continued digging some more, and it turns out there is a one liner
> fix for the issue that has been merged upstream:
>
> https://github.com/dracutdevs/dracut/pull/2196
>
> Would there be any hope to get this backported to be included in Fedora
> 39? The scope of the change is ridiculously tiny, limited to this
> single modules.d/90dmsquash-live/iso-scan.sh file which is exclusively
> used for this broken feature.
>
> It would be really great to get the final Fedora 39 iso working again.
>

An update has been proposed:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-f71507e281



-- 
真実はいつも一つ！/ Always, there's only one truth!
___
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

Re: Occasional random Koji build failures only on ppc64le

2023-10-05 Thread Kevin Fenzi 
On Thu, Oct 05, 2023 at 09:23:57PM +0200, Fabio Valentini wrote:
> On Thu, Oct 5, 2023 at 9:12 PM Richard W.M. Jones  wrote:
> >
> > Getting $SUBJECT.  The errors are always of the form:
> >
> > DEBUG util.py:446:: Cannot download, all mirrors were 
> > already tried without success
> >
> > for various s.  Examples:
> >
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=107101090
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=107097695
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=107097917
> >
> > Retrying the builds seems to fix it.
> >
> > Could be a problem with a server or mirror somewhere?
> 
> I see these regularly in koschei failures as well.
> x86_64 and aarch64 builds succeed, but ppc64le fails with network issues.

yeah. Shortly before final freeze I updated the virthosts those builders
are on. Sadly, somehow the newer kernels cause those weird network
hiccups. Builders stop checking in, or don't return when uploading as
well.

I moved one of them back to the previous kernel to confirm it was ok and
it has been. I am downgrading all the rest now, so they should all be
back to hopefully being stable later this afternoon. 

kevin


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

Re: Occasional random Koji build failures only on ppc64le

2023-10-05 Thread Fabio Valentini 
On Thu, Oct 5, 2023 at 9:12 PM Richard W.M. Jones  wrote:
>
> Getting $SUBJECT.  The errors are always of the form:
>
> DEBUG util.py:446:: Cannot download, all mirrors were 
> already tried without success
>
> for various s.  Examples:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=107101090
> https://koji.fedoraproject.org/koji/taskinfo?taskID=107097695
> https://koji.fedoraproject.org/koji/taskinfo?taskID=107097917
>
> Retrying the builds seems to fix it.
>
> Could be a problem with a server or mirror somewhere?

I see these regularly in koschei failures as well.
x86_64 and aarch64 builds succeed, but ppc64le fails with network issues.

Fabio
___
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

Occasional random Koji build failures only on ppc64le

2023-10-05 Thread Richard W.M. Jones 
Getting $SUBJECT.  The errors are always of the form:

DEBUG util.py:446:: Cannot download, all mirrors were already 
tried without success

for various s.  Examples:

https://koji.fedoraproject.org/koji/taskinfo?taskID=107101090
https://koji.fedoraproject.org/koji/taskinfo?taskID=107097695
https://koji.fedoraproject.org/koji/taskinfo?taskID=107097917

Retrying the builds seems to fix it.

Could be a problem with a server or mirror somewhere?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
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

Summary/Minutes from today's FESCo Meeting (2023-10-05)

2023-10-05 Thread Major Hayden 
=
#fedora-meeting-2: FESCO (2023-10-05)
=


Meeting started by mhayden at 17:00:07 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2023-10-05/fesco.2023-10-05-17.00.log.html



Meeting summary
---
* init process  (mhayden, 17:00:23)

* #3080 Retiring 5 packages without a Python 3.12 rebuild from Fedora
  39+40  (mhayden, 17:03:49)
  * AGREED: Proceed with Python package retirements in #3080 except the
mathics packages (+7,0,0)  (mhayden, 17:09:19)

* #3072 Change: Passim Peer-to-Peer Metadata  (mhayden, 17:10:23)
  * AGREED: Proceed with #3072 for F40. APPROVED (+4, 2, -1)  (mhayden,
17:56:37)

* #3078 Consider revising package sponsor policy due to possible race
  condition  (mhayden, 17:57:15)
  * LINK: https://pagure.io/fesco/fesco-docs/pull-request/79   (mhayden,
17:59:13)

* Next week's chair  (mhayden, 18:00:57)
  * ACTION: mhayden to chair again next week on Oct 12  (mhayden,
18:03:27)

* Open Floor  (mhayden, 18:03:38)

Meeting ended at 18:05:12 UTC.




Action Items

* mhayden to chair again next week on Oct 12




Action Items, by person
---
* mhayden
  * mhayden to chair again next week on Oct 12
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* mhayden (81)
* mhroncok_web (48)
* Son_Goku (34)
* zbyszek (27)
* nirik (25)
* zodbot (20)
* decathorpe (16)
* dcantrell (10)
* dcavalca (6)
* michel-slm (5)
* neil (2)
* sgallagh (0)
* mhroncok (0)
* Conan_Kudo (0)
* Pharaoh_Atem (0)
* King_InuYasha (0)
* Sir_Gallantmon (0)
* Eighth_Doctor (0)
* tstellar (0)

-- 
Major Hayden
___
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

Re: [Fedocal] Reminder meeting : ELN SIG

2023-10-05 Thread Stephen Gallagher 
On Thu, Oct 5, 2023 at 8:00 AM  wrote:

> Dear all,
>
> You are kindly invited to the meeting:
>ELN SIG on 2023-10-06 from 12:00:00 to 13:00:00 US/Eastern
>At fedora-meet...@irc.libera.chat
>
> The meeting will be about:



* Should ELN stop carrying enabled Rawhide repos?
https://src.fedoraproject.org/rpms/fedora-release/pull-request/284

>
___
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

Re: time is running: security issue BZ#2241470

2023-10-05 Thread Adam Williamson 
On Thu, 2023-10-05 at 19:01 +0200, Tomasz Torcz wrote:
> On Thu, Oct 05, 2023 at 11:23:35AM -0400, Stephen Smoogen wrote:
> > On Sat, 30 Sept 2023 at 05:13, Marius Schwarz 
> > wrote:
> > 
> > > 
> > > Hi,
> > > 
> > > this is emerg ping for the security team, to take a look at this bz :
> > > 
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2241470
> > > 
> > > The deadline for having a fix shipped is the afternoon of SUN, 1. of Oct
> > > 2023 . On this date, the patches in upstream go public and exploits
> > > will be developed for them. this impacts ALL of redhat based
> > > installations which run as servers and are publically reachable. The
> > > component in question is the default package for rh based installations.
> > > 
> > So does anyone know which of this weeks major security problems this was
> > about? Since it is supposedly past the release date, I figure it is ok to
> > ask. If it isn't due to some other delay.. my apologies.
> 
>   My guess is on glibc's suid local root: https://lwn.net/Articles/946381/

That doesn't seem to really fit, though. You need to be able to at
least set environment variables and execute processes to exploit that,
right? That hardly covers "all publically reachable servers".

I guess it's the closest candidate, but meh. In any case, the updates
for that all went stable yesterday.
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



___
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

Re: time is running: security issue BZ#2241470

2023-10-05 Thread Tomasz Torcz 
On Thu, Oct 05, 2023 at 11:23:35AM -0400, Stephen Smoogen wrote:
> On Sat, 30 Sept 2023 at 05:13, Marius Schwarz 
> wrote:
> 
> >
> > Hi,
> >
> > this is emerg ping for the security team, to take a look at this bz :
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=2241470
> >
> > The deadline for having a fix shipped is the afternoon of SUN, 1. of Oct
> > 2023 . On this date, the patches in upstream go public and exploits
> > will be developed for them. this impacts ALL of redhat based
> > installations which run as servers and are publically reachable. The
> > component in question is the default package for rh based installations.
> >
> So does anyone know which of this weeks major security problems this was
> about? Since it is supposedly past the release date, I figure it is ok to
> ask. If it isn't due to some other delay.. my apologies.

  My guess is on glibc's suid local root: https://lwn.net/Articles/946381/

-- 
Tomasz TorczOnce you've read the dictionary,
@ttorcz:pipebreaker.pl  every other book is just a remix.
___
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

Re: time is running: security issue BZ#2241470

2023-10-05 Thread Stephen Smoogen 
On Sat, 30 Sept 2023 at 05:13, Marius Schwarz 
wrote:

>
> Hi,
>
> this is emerg ping for the security team, to take a look at this bz :
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2241470
>
> excuse me, for bringing this to the list, as a security bz is the way to
> go, but time is running fast and the patched release needs to be build
> and shipped in 36h hours from now.
>
> The deadline for having a fix shipped is the afternoon of SUN, 1. of Oct
> 2023 . On this date, the patches in upstream go public and exploits
> will be developed for them. this impacts ALL of redhat based
> installations which run as servers and are publically reachable. The
> component in question is the default package for rh based installations.
>
> best regards,
> Marius Schwarz
>
>
So does anyone know which of this weeks major security problems this was
about? Since it is supposedly past the release date, I figure it is ok to
ask. If it isn't due to some other delay.. my apologies.

-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
___
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

Schedule for Thursday's FESCo Meeting (2023-10-05)

2023-10-05 Thread Major Hayden 
Following is the list of topics that will be discussed in the
FESCo meeting Thursday at 17:00UTC in #fedora-meeting-2 on
irc.libera.chat.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2023-10-05 17:00 UTC'

Links to all issues to be discussed can be found at: 
https://pagure.io/fesco/report/meeting_agenda

= New business =

#3080 Retiring 5 packages without a Python 3.12 rebuild from Fedora 39+40 (fast 
track)
https://pagure.io/fesco/issue/3080

#3072 Change: Passim Peer-to-Peer Metadata
https://pagure.io/fesco/issue/3072

#3078 Consider revising package sponsor policy due to possible race condition
https://pagure.io/fesco/issue/3078

= Open Floor = 

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting. 

--
Major Hayden
___
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

Fedora 39 compose report: 20231005.n.0 changes

2023-10-05 Thread Fedora Branched Report 
OLD: Fedora-39-20231004.n.0
NEW: Fedora-39-20231005.n.0

= SUMMARY =
Added images:1
Dropped images:  3
Added packages:  0
Dropped packages:0
Upgraded packages:   7
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   567.09 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   1.60 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-39-20231005.n.0.iso

= DROPPED IMAGES =
Image: Workstation live aarch64
Path: 
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-39-20231004.n.0.iso
Image: LXQt live aarch64
Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-39-20231004.n.0.iso
Image: KDE live aarch64
Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-39-20231004.n.0.iso

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  glibc-2.38-6.fc39
Old package:  glibc-2.38-4.fc39
Summary:  The GNU libc libraries
RPMs: compat-libpthread-nonshared glibc glibc-all-langpacks 
glibc-benchtests glibc-common glibc-devel glibc-doc glibc-gconv-extra 
glibc-headers-s390 glibc-headers-x86 glibc-langpack-aa glibc-langpack-af 
glibc-langpack-agr glibc-langpack-ak glibc-langpack-am glibc-langpack-an 
glibc-langpack-anp glibc-langpack-ar glibc-langpack-as glibc-langpack-ast 
glibc-langpack-ayc glibc-langpack-az glibc-langpack-be glibc-langpack-bem 
glibc-langpack-ber glibc-langpack-bg glibc-langpack-bhb glibc-langpack-bho 
glibc-langpack-bi glibc-langpack-bn glibc-langpack-bo glibc-langpack-br 
glibc-langpack-brx glibc-langpack-bs glibc-langpack-byn glibc-langpack-ca 
glibc-langpack-ce glibc-langpack-chr glibc-langpack-ckb glibc-langpack-cmn 
glibc-langpack-crh glibc-langpack-cs glibc-langpack-csb glibc-langpack-cv 
glibc-langpack-cy glibc-langpack-da glibc-langpack-de glibc-langpack-doi 
glibc-langpack-dsb glibc-langpack-dv glibc-langpack-dz glibc-langpack-el 
glibc-langpack-en glibc-langpack-eo glibc-langpack-es glibc-langpack-et 
glibc-langpack-eu glibc-langpack-fa glibc-langpack-ff glibc-langpack-fi 
glibc-langpack-fil glibc-langpack-fo glibc-langpack-fr glibc-langpack-fur 
glibc-langpack-fy glibc-langpack-ga glibc-langpack-gd glibc-langpack-gez 
glibc-langpack-gl glibc-langpack-gu glibc-langpack-gv glibc-langpack-ha 
glibc-langpack-hak glibc-langpack-he glibc-langpack-hi glibc-langpack-hif 
glibc-langpack-hne glibc-langpack-hr glibc-langpack-hsb glibc-langpack-ht 
glibc-langpack-hu glibc-langpack-hy glibc-langpack-ia glibc-langpack-id 
glibc-langpack-ig glibc-langpack-ik glibc-langpack-is glibc-langpack-it 
glibc-langpack-iu glibc-langpack-ja glibc-langpack-ka glibc-langpack-kab 
glibc-langpack-kk glibc-langpack-kl glibc-langpack-km glibc-langpack-kn 
glibc-langpack-ko glibc-langpack-kok glibc-langpack-ks glibc-langpack-ku 
glibc-langpack-kw glibc-langpack-ky glibc-langpack-lb glibc-langpack-lg 
glibc-langpack-li glibc-langpack-lij glibc-langpack-ln glibc-langpack-lo 
glibc-langpack-lt glibc-langpack-lv glibc-langpack-lzh glibc-langpack-mag 
glibc-langpack-mai glibc-langpack-mfe glibc-langpack-mg glibc-langpack-mhr 
glibc-langpack-mi glibc-langpack-miq glibc-langpack-mjw glibc-langpack-mk 
glibc-langpack-ml glibc-langpack-mn glibc-langpack-mni glibc-langpack-mnw 
glibc-langpack-mr glibc-langpack-ms glibc-langpack-mt glibc-langpack-my 
glibc-langpack-nan glibc-langpack-nb glibc-langpack-nds glibc-langpack-ne 
glibc-langpack-nhn glibc-langpack-niu glibc-langpack-nl glibc-langpack-nn 
glibc-langpack-nr glibc-langpack-nso glibc-langpack-oc glibc-langpack-om 
glibc-langpack-or glibc-langpack-os glibc-langpack-pa glibc-langpack-pap 
glibc-langpack-pl glibc-langpack-ps glibc-langpack-pt glibc-langpack-quz 
glibc-langpack-raj glibc-langpack-rif glibc-langpack-ro glibc-langpack-ru 
glibc-langpack-rw glibc-langpack-sa glibc-langpack-sah glibc-langpack-sat 
glibc-langpack-sc glibc-langpack-sd glibc-langpack-se glibc-langpack-sgs 
glibc-langpack-shn glibc-langpack-shs glibc-langpack-si glibc-langpack-sid 
glibc-langpack-sk glibc-langpack-sl glibc-langpack-sm glibc-langpack-so 
glibc-langpack-sq glibc-langpack-sr glibc-langpack-ss glibc-langpack-st 
glibc-langpack-sv glibc-langpack-sw glibc-langpack-syr glibc-langpack-szl 
glibc-langpack-ta glibc-langpack-tcy glibc-langpack-te glibc-langpack-tg 
glibc-langpack-th glibc-langpack-the glibc-langpack-ti glibc-langpack-tig 
glibc-langpack-tk glibc-langpack-tl glibc-langpack-tn glibc-langpack-to 
glibc-langpack-tpi glibc-langpack-tr glibc-langpack-ts glibc-langpack-tt 
glibc-langpack-ug glibc-langpack-uk glibc-langpack-unm glibc-langpack-ur 
glibc-langpack-uz glibc-langpack-ve glibc-langpack-vi glibc-langpack-wa 
glibc-langpack-wae glibc-langpack-wal glibc-langpack-wo glibc-langpack-xh 
glibc-langpack-yi glibc-langpack-yo glibc-langpack-yue glibc-langpack-yuw 
glibc-langpack-zh glibc-langpack-zu glibc-locale

Re: Specify koji build machine mem req via. spec file

2023-10-05 Thread Kalev Lember 
On Thu, Oct 5, 2023 at 2:04 PM Julian Sikorski  wrote:

> Does a hammer smaller than -g1 also exist for issues like:
>
> relocation truncated to fit: R_X86_64_32 against `.debug_info'
> https://kojipkgs.fedoraproject.org//work/tasks/1615/107091615/build.log
>
> Thanks for the info in advance.
>

Sorry, I don't know, that's something slightly different. Maybe open a
ticket against gcc and ask the tools team?

-- 
Kalev
___
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

[Test-Announce] Fedora 39 Upgrade Test Day is underway!

2023-10-05 Thread Sumantro Mukherjee 
Hey All,

As we come closer to Fedora 39 release dates, it's time to test upgrades.
Fedora 39 has a lot of changesets and it becomes essential that we
test the graphical upgrade methods as well as the command line.
As a part of this test day[0], we will test upgrading from a full
updated, F37 and F38 to the F39 for all architectures(x86_64,ARM,aarch
64) and variants(WS,cloud,server,silverblue,IoT).

We understand that upgrade takes time and testing if things work as
expected, takes more.
We will be accepting results throughout the weekend!

The results can be submitted here[1]

As usual, we hang out on the #fedora-test-day, should you have questions.

[0] http://fedoraproject.org/wiki/Test_Day:2023-10-05_F39_Upgrade_Test_Day
[1] https://testdays.fedoraproject.org/events/158


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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/test-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
___
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

Re: Specify koji build machine mem req via. spec file

2023-10-05 Thread Julian Sikorski 

Am 04.10.23 um 12:19 schrieb Kalev Lember:
On Wed, Oct 4, 2023 at 11:44 AM Martin Stransky > wrote:


Hello guys,

Is there's a way how to set requested amount of ram for koji builders?

I'd like to use it as Firefox builds fail recently due low memory, like
https://bugzilla.redhat.com/show_bug.cgi?id=2241690



I looked at the first linked build log in the ticket and it looks like 
the build failed in the debuginfo extraction step. In that log, 
find-debuginfo is called with -j3, and it could be that it ran out of 
memory because it was trying to do 3 debuginfo extractions in parallel. 
You could try to stick something like this in the spec file to tune it down:


# Require 32 GB of RAM per CPU core for debuginfo processing
%global _find_debuginfo_opts %limit_build -m 32768

... and see if it helps. With this, it should pass -j1 to find-debuginfo 
when the builder has 32 GB RAM, -j2 when it has 64 GB etc.


If that doesn't work, then there's also the option of using -g1 to 
reduce the binary sizes so they take less memory to process (but that 
makes backtraces much worse so I'd only leave it for emergencies if you 
can't get an important build out otherwise).



Does a hammer smaller than -g1 also exist for issues like:

relocation truncated to fit: R_X86_64_32 against `.debug_info'
https://kojipkgs.fedoraproject.org//work/tasks/1615/107091615/build.log

Thanks for the info in advance.

Best regards,
Julian
___
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

[Fedocal] Reminder meeting : ELN SIG

2023-10-05 Thread sgallagh 
Dear all,

You are kindly invited to the meeting:
   ELN SIG on 2023-10-06 from 12:00:00 to 13:00:00 US/Eastern
   At fedora-meet...@irc.libera.chat

The meeting will be about:



Source: https://calendar.fedoraproject.org//meeting/10568/

___
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

Fedora rawhide compose report: 20231005.n.0 changes

2023-10-05 Thread Fedora Rawhide Report 
OLD: Fedora-Rawhide-20231004.n.0
NEW: Fedora-Rawhide-20231005.n.0

= SUMMARY =
Added images:4
Dropped images:  1
Added packages:  10
Dropped packages:1
Upgraded packages:   107
Downgraded packages: 0

Size of added packages:  32.37 MiB
Size of dropped packages:995.83 KiB
Size of upgraded packages:   1.92 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -12.54 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20231005.n.0.iso
Image: Onyx dvd-ostree x86_64
Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20231005.n.0.iso
Image: Silverblue dvd-ostree aarch64
Path: 
Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20231005.n.0.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20231005.n.0.iso

= DROPPED IMAGES =
Image: LXQt live aarch64
Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-Rawhide-20231004.n.0.iso

= ADDED PACKAGES =
Package: golang-github-microsoft-dev-tunnels-0.0.21-1.fc40
Summary: Dev Tunnels SDK
RPMs:golang-github-microsoft-dev-tunnels-devel
Size:69.28 KiB

Package: golang-github-rodaine-table-1.1.0-1.fc40
Summary: Go CLI Table Generator
RPMs:golang-github-rodaine-table-devel
Size:14.34 KiB

Package: golang-modernc-sqlite-1.25.0-2.fc40
Summary: A port of SQLite/SQLite3 to Go without cgo
RPMs:golang-modernc-sqlite golang-modernc-sqlite-devel
Size:6.78 MiB

Package: libtexprintf-1.25-1.fc40
Summary: Formatted Output with tex-like syntax support
RPMs:libtexprintf libtexprintf-devel libtexprintf-static libtexprintf-tools
Size:1.10 MiB

Package: perl-File-KDBX-0.906-6.fc40
Summary: Encrypted database to store secret text and files
RPMs:perl-File-KDBX
Size:243.79 KiB

Package: python-pycatch22-0.4.3-1.fc40
Summary: CAnonical Time-series CHaracteristics in Python
RPMs:python3-pycatch22
Size:122.50 KiB

Package: python-pygmtools-0.4.0-1.fc40
Summary: A library of Python graph matching solvers
RPMs:python-pygmtools-doc python3-pygmtools
Size:23.79 MiB

Package: python-trio-websocket-0.11.1-2.fc40
Summary: WebSocket implementation focused on safety and correctness
RPMs:python-trio-websocket-doc python3-trio-websocket
Size:158.25 KiB

Package: rust-gix-archive-0.4.0-1.fc40
Summary: Archive generation from of a worktree stream
RPMs:rust-gix-archive+default-devel 
rust-gix-archive+document-features-devel rust-gix-archive+tar-devel 
rust-gix-archive+tar_gz-devel rust-gix-archive+zip-devel rust-gix-archive-devel
Size:58.71 KiB

Package: rust-relative-path-1.9.0-1.fc40
Summary: Portable, relative paths for Rust
RPMs:rust-relative-path+default-devel rust-relative-path+serde-devel 
rust-relative-path-devel
Size:49.41 KiB


= DROPPED PACKAGES =
Package: perl-Marpa-XS-1.008000-40.fc40
Summary: Language grammar parser module for Perl
RPMs:perl-Marpa-XS
Size:995.83 KiB


= UPGRADED PACKAGES =
Package:  HepMC3-3.2.7-1.fc40
Old package:  HepMC3-3.2.6-3.fc39
Summary:  C++ Event Record for Monte Carlo Generators
RPMs: HepMC3 HepMC3-devel HepMC3-doc HepMC3-interfaces-devel 
HepMC3-protobufIO HepMC3-protobufIO-devel HepMC3-rootIO HepMC3-rootIO-devel 
HepMC3-search HepMC3-search-devel python3-HepMC3 python3-HepMC3-protobufIO 
python3-HepMC3-rootIO python3-HepMC3-search
Size: 8.12 MiB
Size change:  -427 B
Changelog:
  * Wed Oct 04 2023 Mattias Ellert  - 3.2.7-1
  - Update to version 3.2.7


Package:  anaconda-40.7-1.fc40
Old package:  anaconda-40.6-1.fc40
Summary:  Graphical system installer
RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui 
anaconda-install-env-deps anaconda-install-img-deps anaconda-live anaconda-tui 
anaconda-webui anaconda-widgets anaconda-widgets-devel
Size: 24.14 MiB
Size change:  3.83 KiB
Changelog:
  * Tue Oct 03 2023 Packit  - 40.7-1
  - webui: tests: ignore the logo image selector in the pixel tests (kkoukiou)
  - webui: do not hardcode the required mount points in the getInitialRequests
(kkoukiou)
  - webui: helpers: Document storage helper methods (kkoukiou)
  - webui: reimplement checkDeviceInSubTree by re-using existing helper method
(kkoukiou)
  - webui: port dropdown to new PF5 implementation (akankovs)
  - Revert "tests: Run pytest in parallel on available cpu cores" (vslavik)
  - webui: add a logo to the header (akankovs)
  - install-{env,img}-deps: recommend/require kdump-anaconda-addon (awilliam)
  - Fix crash because of missing import statement (kkoukiou)
  - webui: prevent re-defining required mount points from the UI (kkoukiou)
  - Simplify keyboard layout handling, rely on localed more (awilliam)
  - tests: Run pytest in parallel on available cpu cores (vslavik)
  - tests: Don't hardcode file handle number (vslavik)
  - live: Repo

Re: Specify koji build machine mem req via. spec file

2023-10-05 Thread Panu Matilainen 

On 10/5/23 12:41, Kalev Lember wrote:
On Thu, Oct 5, 2023 at 10:07 AM Miroslav Suchý > wrote:


Dne 04. 10. 23 v 11:43 Martin Stransky napsal(a):
 > Hello guys,
 >
 > Is there's a way how to set requested amount of ram for koji
builders?
 >
 > I'd like to use it as Firefox builds fail recently due low
memory, like
 > https://bugzilla.redhat.com/show_bug.cgi?id=2241690

 >
 > Thanks,
 > Martin
 >
Related - rpm has tunables that allows you to tune the build
according the available resources. However memory is not there:

https://github.com/rpm-software-management/rpm/pull/2418


https://rpm-software-management.github.io/rpm/manual/buildprocess.html 



Oh, nice, I didn't know about that! From a quick look, there are 
actually two memory tunables, %_smp_tasksize_proc and %_smp_tasksize_thread.


Looks like the new thing would replace the constrain_build macro that 
firefox.spec is using:


Instead of current:

# Require 4 GB of RAM per CPU core
%constrain_build -m 4096

It would use:

# Require 4 GB of RAM per CPU core
%global _smp_tasksize_proc 4096

It doesn't look like a huge win from the packager's point of view, but I 
am sure it's better to use the rpm upstream limits instead of external 
macros such as 
constrain_build. 


Yep, memory is certainly considered, it was really the main driver of 
that change.


Compared to %constrain_build the big win is that memory is always 
considered, regardless of whether the packager asked for it or not. It 
would be a useful experiment to drop that tunable from the spec because 
it probably isn't necessary anymore (with rpm >= 4.18 that is).


The other win is that the native version also covers threads, which 
helps on 32bit systems in particular.


- Panu -
___
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

Re: Request for comment- tuned replacing power-profiles-daemon plan

2023-10-05 Thread Yanko Kaneti 
Hello

On Thu, 2023-10-05 at 15:29 +0800, Kate Hsuan wrote:
> Hi Folks,
> 
> We would like to replace power-profiles-daemon with tuned. 

> Moreover, the detailed change proposal can be found here.
> https://fedoraproject.org/wiki/Changes/TunedReplacesPower-profiles-daemon
> 
> If you have any suggestions, please let us know.

Just a quick observation that tuned is python mostly with 10 times the
installed footprint of power-profiles-daemon.

If power management is as fundamental as it seems recently I would
really like to see minimal-footprint-closer-to-core thingie.. , i.e.
something systemd-*... maybe.

- Yanko

___
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

Re: Specify koji build machine mem req via. spec file

2023-10-05 Thread Kalev Lember 
On Thu, Oct 5, 2023 at 10:07 AM Miroslav Suchý  wrote:

> Dne 04. 10. 23 v 11:43 Martin Stransky napsal(a):
> > Hello guys,
> >
> > Is there's a way how to set requested amount of ram for koji builders?
> >
> > I'd like to use it as Firefox builds fail recently due low memory, like
> > https://bugzilla.redhat.com/show_bug.cgi?id=2241690
> >
> > Thanks,
> > Martin
> >
> Related - rpm has tunables that allows you to tune the build according the
> available resources. However memory is not there:
>
> https://github.com/rpm-software-management/rpm/pull/2418
>
> https://rpm-software-management.github.io/rpm/manual/buildprocess.html


Oh, nice, I didn't know about that! From a quick look, there are actually
two memory tunables, %_smp_tasksize_proc and %_smp_tasksize_thread.

Looks like the new thing would replace the constrain_build macro that
firefox.spec is using:

Instead of current:

# Require 4 GB of RAM per CPU core
%constrain_build -m 4096

It would use:

# Require 4 GB of RAM per CPU core
%global _smp_tasksize_proc 4096

It doesn't look like a huge win from the packager's point of view, but I am
sure it's better to use the rpm upstream limits instead of external macros
such as constrain_build. 

-- 
Kalev
___
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

Re: Unretirement: Impallari-Lobster-Fonts

2023-10-05 Thread Michael J Gruber 
Am Do., 5. Okt. 2023 um 07:43 Uhr schrieb Benson Muite
:
>
> Hi,
>
> Would like to unretire Impallari-Lobster-Fonts:
> https://bugzilla.redhat.com/show_bug.cgi?id=2242129

Maybe, somewhere in the bug or here, give a link to upstream (pagure
does not have it either) and spell out whether the reasons leading to
retirement are void now?
Thanks :)

Michael
___
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

OCaml 5.1 rebuild

2023-10-05 Thread Richard W.M. Jones 
Over the next few days I'm going to rebuild all OCaml packages in
Rawhide for OCaml 5.1, plus some non-OCaml packages that have OCaml
bindings.

OCaml 5.1 is basically a small point release, but it does add back
native code support for riscv64 and s390x.  The only remaining
architecture that hasn't been updated for OCaml 5 (and is therefore
still using the bytecode interpreter) is ppc64le.

The side tag will be:
  Side tag 'f40-build-side-75060' (id 75060) created.
  Use 'fedpkg build --target=f40-build-side-75060' to use it.
  Use 'koji wait-repo f40-build-side-75060' to wait for the build repo to be 
generated.

The downstream patched branch is:
  https://pagure.io/fedora-ocaml/commits/fedora-40-5.1.0

The tools used to do the rebuild are:
  http://git.annexia.org/?p=fedora-ocaml-rebuild.git;a=summary

Thanks Jerry James for doing all the hard work here!

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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

Re: libsodium mass rebuild DONE

2023-10-05 Thread Remi Collet 

Le 05/10/2023 à 08:10, Remi Collet a écrit :

Le 04/10/2023 à 15:43, Remi Collet a écrit :

Hi,

I start working on libsodium update from 1.0.18 to 1.0.19


Mass rebuild started in f40-build-side-75054


23 builds in new update
https://bodhi.fedoraproject.org/updates/FEDORA-2023-9190538ec0

2 packages already FTBFS

0ad
et

2 packages reported as FTBFS

warzone2100 
https://bugzilla.redhat.com/show_bug.cgi?id=2242267

folly
https://bugzilla.redhat.com/show_bug.cgi?id=2242256

folly also affects fbthrift, fizz, mcrouter, wangle

3 packages needs a rebuild in RPMfusion

megasync
qtox
ripcord


Regards,
Remi
___
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

Re: Specify koji build machine mem req via. spec file

2023-10-05 Thread Miroslav Suchý 

Dne 04. 10. 23 v 11:43 Martin Stransky napsal(a):

Hello guys,

Is there's a way how to set requested amount of ram for koji builders?

I'd like to use it as Firefox builds fail recently due low memory, like 
https://bugzilla.redhat.com/show_bug.cgi?id=2241690


Thanks,
Martin


Related - rpm has tunables that allows you to tune the build according the 
available resources. However memory is not there:

https://github.com/rpm-software-management/rpm/pull/2418

https://rpm-software-management.github.io/rpm/manual/buildprocess.html

--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
___
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

Re: Live USB iso boot not working since Fedora 37, still broken in 39 Beta

2023-10-05 Thread Matthias Saou 
Hi,

I continued digging some more, and it turns out there is a one liner
fix for the issue that has been merged upstream:

https://github.com/dracutdevs/dracut/pull/2196

Would there be any hope to get this backported to be included in Fedora
39? The scope of the change is ridiculously tiny, limited to this
single modules.d/90dmsquash-live/iso-scan.sh file which is exclusively
used for this broken feature.

It would be really great to get the final Fedora 39 iso working again.

Cheers,
Matthias

On Wed, 4 Oct 2023 22:23:46 +0200
Matthias Saou  wrote:

> Hi,
> 
> I haven't posted here or been active with Fedora development in years
> (sorry!), but I'm running into a blocker and don't know where else to
> get help since the bugzilla ticket is silent and assigned to a struck
> out address.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2181989
> 
> Basically anaconda/dracut's iso-scan/filename= has been broken since
> Fedora 37 included, and is still broken in Fedora 39 Beta, meaning the
> Live iso can't be booted from a USB stick using grub and its loopback
> mount feature (which is super nifty and useful!).
> 
> Would anyone with deep enough knowledge of the installer be able to
> help? It's very easy to reproduce with any "live usb iso boot"
> projects such as my own https://github.com/thias/glim
> All of Debian, Ubuntu, Arch, Mint, Gentoo, etc. work fine, but Fedora
> only works up to 36 and RHEL only up to 8 (RHEL 9 is also similarly
> broken).
> 
> Cheers,
> Matthias
> ___
> 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



-- 
Matthias Saou  ██  ██
 ██  ██
Web: http://matthias.saou.eu/  ██
Mail/XMPP:  matth...@saou.eu   ██  
   ██
GPG: 4096R/E755CC63██  ██  ██
 8D91 7E2E F048 9C9C 46AF  ██  ██  ██  ██
 21A9 7A51 7B82 E755 CC63  
___
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

Request for comment- tuned replacing power-profiles-daemon plan

2023-10-05 Thread Kate Hsuan 
Hi Folks,

We would like to replace power-profiles-daemon with tuned. There are
many power-related software that offer similar functions. Advanced
users may install several power management tools, for example, tuned
and power-profiles-daemon (ppd), and get confused about which tools
manage the system and cause unexpected behaviors for the system. By
integrating power-profiles-daemon with tuned, the user can get extra
features to finetune the system, and the basic feature provided by ppd
can be used according to the user's demand. It also can reduce the
efforts of the maintainer.

The impact of this plan would be gnome-control-center (power panel),
KDE, sysprof, and tuned (or some projects depending on ppd). We should
move the ppd API and features to tuned to provide the same features of
it. From the API aspect, we also can design a new API for the basic
feature, ppd provided but the software dependent on ppd should be
modified to use the new API. Although, for the long-term plan, a set
of new API is a good option. For the short-term plan, moving the
original one to tuned is good for those applications depending on ppd.

Moreover, the detailed change proposal can be found here.
https://fedoraproject.org/wiki/Changes/TunedReplacesPower-profiles-daemon

If you have any suggestions, please let us know.

Thank you. :)
-- 
BR,
Kate
___
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