| 17 Apr 2024 |
 Penguinpee | I guess that means the branch will remain empty. It did work, though. Good to know. But the update is just a bugfix release without any downstream bugs filed. It can wait, indeed. | 20:52:47 |
| Penguinpee | jonathanspw: What's your take? I updated QtAwesome on all Fedora branches today. Do you want/need it in next or wait until rhel 9.4? | 20:55:06 |
 jonathanspw | I don't need it that I'm aware of right now, so can wait. | 20:55:31 |
| jonathanspw | should only be a few more weeks anyway | 20:55:34 |
| Penguinpee | ⏳️ | 20:55:51 |
| Penguinpee | Let's wait then. Thanks for all the help and explanation. | 20:56:25 |
| 18 Apr 2024 |
|  Brian Clemens changed their display name from Brian Clemens to brian. | 08:22:57 |
 James Richardson | In reply to @smooge:fedora.im
have a good evening James Richardson . Hug a guitar for me I gave each one a hug, read them a bedtime story, glass of milk, and tucked them in tight....they said "tell Smooge we said goodnight" | 08:24:05 |
| Brian Clemens changed their display name from brian to Brian Clemens. | 08:27:27 |
|  ericg joined the room. | 15:31:20 |
|  Pat Riehecky joined the room. | 18:13:51 |
| Penguinpee | Could someone confirm that the upcoming rhel release (was it 9.4?) will have rpm-4.19.1.1? I queried the eln and c9s repos, which have that version currently. I'm asking since I introduced a Lua macro in a spec file for a package that is also branched for epel9. I believe 4.19 would support that, whereas currently (4.16?) it is unsupported. | 21:23:09 |
 Troy Dawson | Penguinpee No. RHEL 9.4 will NOT have rpm-4.19.1. It will still have 4.16.1. | 21:35:25 |
| Troy Dawson | You must have queried the CentOS Stream 10 repo's, which will have 4.19.1. | 21:36:06 |
| Troy Dawson | ELN nowdays has nothing to do with CentOS Stream 9. | 21:36:26 |
| Penguinpee | Bummer! I had hoped for an easy escape. And you are right, c9s is on 4.16.1.3. I made a mistake there. So, there will be no support still for %{lua: print(foo)} type macros? Then I will have to find another solution. | 21:40:23 |
| 19 Apr 2024 |
| Brian Clemens set a profile picture. | 02:28:19 |
 Michel Lind 🎩 | Troy Dawson: I happen to be on my aarch box when trying to work on docs, so of course the build script does not work. I fixed it in https://pagure.io/epel/pull-request/273 | 02:47:46 |
 Jens Petersen | Any news on epel10? | 02:51:10 |
 Neil Hanlon | my notes say it'll begin in earnest once there are signed c10s composes | 02:56:38 |
 Davide Cavalca | And those should start showing up later next month if all goes well | 02:57:34 |
 arrfab | Hmm you seem to have more info that I do 😁 | 05:10:13 |
| arrfab | I should sync with Stream team about when they want to push things out as it would need sync with them or that would be problematic with mirrors and c8s/c7 eol plan | 05:11:35 |
| Penguinpee | Are there any alternatives for %constrain_build or %{limit_build ...} available in EPEL? For the details, the macros are defined in macros.build-constraints. | 11:13:05 |
| Michel Lind 🎩 | In reply to @gui1ty:fedora.im
Are there any alternatives for %constrain_build or %{limit_build ...} available in EPEL? For the details, the macros are defined in macros.build-constraints. Setting _smp_ncpus_max like here https://src.fedoraproject.org/rpms/rust-nu/blob/rawhide/f/rust-nu.spec I looked into adding the macros to epel-rpm-macros but the Lua code does not work in el9 | 14:32:30 |
 music | If you really need to try to replicate the memory-per-cpu calculation, something like this will probably work as a starting point: %global mem_kb %(awk '$1 == "MemTotal:" && $3 == "kB" { print $2 }' /proc/meminfo). | 15:20:38 |
| music | (Snippet sold as-is. No returns.) | 15:21:01 |
| Penguinpee | That's violating my statutory consumer rights. ;) | 15:47:43 |
| Penguinpee | In reply to @salimma:fedora.im
Setting _smp_ncpus_max like here https://src.fedoraproject.org/rpms/rust-nu/blob/rawhide/f/rust-nu.spec I looked into adding the macros to epel-rpm-macros but the Lua code does not work in el9 The problem is I need to constrain the build based on memory. I know that one thread consumes a little more than 6GiB when building unit tests. And it fails on the smallest of builders running out of memory. I'll look into music's suggestion. It will need to be something dynamic. Or the build will be as fast as rhel9 is old, e.g. limited to one core only. | 15:50:53 |
 Diego Herrera | Troy Dawson: how long does it usually take to run the willit.py scripts? | 16:37:19 |
