| 23 Apr 2024 |
 Jiri Kyjovsky | but thanks for notifying us :) | 12:54:00 |
 Michel Lind 🎩 | weird... I can access kojihub.stream's c9s-build repo from COPR for x86_64, but not for aarch64
https://github.com/fedora-copr/copr/issues/3235 | 21:50:23 |
| 24 Apr 2024 |
|  Triskelion joined the room. | 03:36:45 |
 Stephen J Smoogen | Michel Lind 🎩: can you access aarch64 repo from outside of copr? | 12:18:01 |
 Penguinpee | FrostyX: It seems fedora-review service is borked again. | 19:54:56 |
| Penguinpee | Or maybe you've already fixed it. No action on a commit made at 2024-04-24 12:58:59 UTC, though. | 19:55:56 |
| Penguinpee | s/commit/comment | 19:56:21 |
 FrostyX | nirik: Do you think we can solve this caveman style and set a timer to reboot the Bugzilla2fedmsg service every hour? At this point, it sounds like the least painful solution to me | 20:48:13 |
 nirik | I already restaeted it when Penguinpee said that eariler... I'd like to ask abompard for next steps from the development side before doing anything else. | 20:49:04 |
| nirik | can you ask in that ticket? or I can in a bit, busy with other things right now | 20:50:53 |
| FrostyX | Sure, thank you very much. | 20:52:36 |
| Michel Lind 🎩 | In reply to @smooge:fedora.im
Michel Lind 🎩: can you access aarch64 repo from outside of copr? yes | 21:42:45 |
| Michel Lind 🎩 | I can browse the files just fine | 21:42:56 |
| 25 Apr 2024 |
 praiskup | Stephen J Smoogen: I can confirm the aarch64 repo is not accessible from Copr aarch64 builders (EC2) | 08:28:53 |
| praiskup | * processing: https://kojihub.stream.centos.org/kojifiles/repos/c9s-build/latest/aarch64/
* Trying 66.187.232.100:443...<hang>
| 08:29:16 |
| praiskup | $ curl ifconfig.me
3.81.106.199
| 08:29:49 |
| praiskup | Works fine on an x86 builders ```
curl ifconfig.me
18.205.113.8 | 08:31:06 |
| praiskup | * Works fine on an x86 builders
curl ifconfig.me
18.205.113.8
| 08:31:18 |
| praiskup | Nah, works fine on a different aarch box 35.153.142.216 | 08:36:33 |
|  Siteshwar Vashisht joined the room. | 15:45:41 |
|  Mab879 (Matthew Burket) joined the room. | 16:38:37 |
|  Matthew Burket joined the room. | 16:42:27 |
| Michel Lind 🎩 | ah interesting. I tried several times but I might have gotten unlucky and kept getting a bad box | 19:15:44 |
| 26 Apr 2024 |
|  Fabio Valentini (AFK until April 28) changed their display name from Fabio Valentini to Fabio Valentini (AFK until April 28). | 12:59:59 |
| Penguinpee | Why is Copr not using the newer build from the Copr repo? I build python-superqt-0.6.4-2 in Copr today. I chained the build of spyder-6.0.0~a5-1 to after the build of superqt and I was expecting it to use the newer version of superqt. Instead the log tells me
Handling superqt <1.0.0,>=0.6.1 from hook generated metadata: Requires-Dist (spyder)
Requirement satisfied: superqt <1.0.0,>=0.6.1
(installed: superqt 0.6.3)
Shouldn't the Copr repo take precedence over the Fedora repo? If not, how can I ensure it does?
| 21:23:47 |
| Penguinpee | * Why is Copr not using the newer build from the Copr repo? I build python-superqt-0.6.4-2 in Copr today. I chained the build of spyder-6.0.0~a5-1 to start after the build of superqt and I was expecting it to use the newer version of superqt. Instead the log tells me
Handling superqt <1.0.0,>=0.6.1 from hook generated metadata: Requires-Dist (spyder)
Requirement satisfied: superqt <1.0.0,>=0.6.1
(installed: superqt 0.6.3)
Shouldn't the Copr repo take precedence over the Fedora repo? If not, how can I ensure it does?
| 21:24:20 |
| Penguinpee | I guess setting the repo priority is one way of achieving what I want. But it feels strangely unnecessary since the package in the Copr repo has a higher version. | 22:22:13 |
| Penguinpee | It seems the repo hasn't been refreshed after the latest builds. I set the repo priority to 42 and rebuild spyder again. It took the package from the Copr repo, BUT
Handling superqt <1.0.0,>=0.6.1 from hook generated metadata: Requires-Dist (spyder)
Requirement satisfied: superqt <1.0.0,>=0.6.1
(installed: superqt 0.6.2)
that's coming from
python3-superqt noarch 0.6.2-1.fc41 copr_base 642.6 KiB
The page view hasn't registered the [latest build[(https://copr.fedorainfracloud.org/coprs/gui1ty/Spyder6/package/python-superqt/) either.
| 22:39:30 |
| Penguinpee | * It seems the repo hasn't been refreshed after the latest builds. I set the repo priority to 42 and rebuild spyder again. It took the package from the Copr repo, BUT
Handling superqt <1.0.0,>=0.6.1 from hook generated metadata: Requires-Dist (spyder)
Requirement satisfied: superqt <1.0.0,>=0.6.1
(installed: superqt 0.6.2)
that's coming from
python3-superqt noarch 0.6.2-1.fc41 copr_base 642.6 KiB
The page view hasn't registered the latest build either.
| 22:40:08 |
| Penguinpee | Mystery solved. I'm off to bed. Have a great weekend! | 22:40:43 |
