Scratch build of gtkhash does not appear to pull in libb2-0.98.1. Has the buildroot override expired?
https://koji.fedoraproject.org/koji/taskinfo?taskID=45077601
On 5/26/20 1:49 PM, Antonio T. sagitter wrote:
Mukundan, your package misses. Please, rebuild `gtkhash` against `libb2-0.98.1` or let me commit changes to it.
On 25/05/20 19:18, Elliott Sales de Andrade wrote:
I made builds for R-argon2 last night as well, which you can include in your update.
- R-argon2-0.2.0-7.fc31
Actually, there's no need for a _new_ update; you can just edit the existing one.
On Mon, 25 May 2020 at 08:41, Felix Schwarz fschwarz@fedoraproject.org wrote:
builds for borgbackup done (finally): - borgbackup-1.1.11-3.el7 - borgbackup-1.1.11-5.fc31
Please add these once you submit the final update.
Felix
On Wed, May 27, 2020 at 05:22:04PM -0400, Mukundan Ragavan wrote:
Scratch build of gtkhash does not appear to pull in libb2-0.98.1. Has the buildroot override expired?
https://koji.fedoraproject.org/koji/taskinfo?taskID=45077601
It did not expire:
$ bodhi overrides query --builds libb2-0.98.1-2.fc31 ============================================================ libb2-0.98.1-2.fc31 ============================================================ Submitter: fschwarz Expiration Date: 2020-05-29 00:00:00 Notes: updating borgbackup due to libb2 update Expired: False
Use the following to ensure the override is active:
$ koji wait-repo f31-build --build=libb2-0.98.1-2.fc31
1 overrides found (1 shown)
So what libb2 build is in the build root?
$ koji wait-repo f31-build --build=libb2-0.98.1-2.fc31 Warning: nvr libb2-0.98.1-2.fc31 is not current in tag f31-build latest build in f31-build is libb2-0.98-4.20171225git60ea749.fc31 ^C
How is it possible? What happened with the libb2-0.98.1-2.fc31 build:
$ koji list-history --build libb2-0.98.1-2.fc31 Fri May 22 20:48:12 2020 libb2-0.98.1-2.fc31 tagged into f31-updates-candidate by sagitter Fri May 22 20:54:19 2020 libb2-0.98.1-2.fc31 tagged into f31-signing-pending by bodhi Fri May 22 20:54:36 2020 libb2-0.98.1-2.fc31 untagged from f31-signing-pending by autopen Fri May 22 20:54:36 2020 libb2-0.98.1-2.fc31 tagged into f31-updates-testing-pending by autopen Fri May 22 23:00:35 2020 libb2-0.98.1-2.fc31 tagged into f31-override by bodhi Sat May 23 04:51:56 2020 libb2-0.98.1-2.fc31 untagged from f31-updates-candidate by bodhi Sat May 23 04:51:56 2020 libb2-0.98.1-2.fc31 tagged into f31-updates-testing by bodhi Sat May 23 04:52:04 2020 libb2-0.98.1-2.fc31 untagged from f31-updates-testing-pending by bodhi Tue May 26 15:15:47 2020 libb2-0.98.1-2.fc31 untagged from f31-updates-testing by bodhi Tue May 26 15:15:47 2020 libb2-0.98.1-2.fc31 untagged from f31-override by bodhi Tue May 26 15:15:48 2020 libb2-0.98.1-2.fc31 tagged into f31-updates-candidate by bodhi [still active]
It was untagged from override by bodhi user on 2020-05-26. That's 3 days before the expiration. It looks like a bug in Bodhi service.
You can try to submit it into override again.
-- Petr
On 5/28/20 2:25 AM, Petr Pisar wrote:
How is it possible? What happened with the libb2-0.98.1-2.fc31 build:
$ koji list-history --build libb2-0.98.1-2.fc31 Fri May 22 20:48:12 2020 libb2-0.98.1-2.fc31 tagged into f31-updates-candidate by sagitter Fri May 22 20:54:19 2020 libb2-0.98.1-2.fc31 tagged into f31-signing-pending by bodhi Fri May 22 20:54:36 2020 libb2-0.98.1-2.fc31 untagged from f31-signing-pending by autopen Fri May 22 20:54:36 2020 libb2-0.98.1-2.fc31 tagged into f31-updates-testing-pending by autopen Fri May 22 23:00:35 2020 libb2-0.98.1-2.fc31 tagged into f31-override by bodhi Sat May 23 04:51:56 2020 libb2-0.98.1-2.fc31 untagged from f31-updates-candidate by bodhi Sat May 23 04:51:56 2020 libb2-0.98.1-2.fc31 tagged into f31-updates-testing by bodhi Sat May 23 04:52:04 2020 libb2-0.98.1-2.fc31 untagged from f31-updates-testing-pending by bodhi Tue May 26 15:15:47 2020 libb2-0.98.1-2.fc31 untagged from f31-updates-testing by bodhi Tue May 26 15:15:47 2020 libb2-0.98.1-2.fc31 untagged from f31-override by bodhi Tue May 26 15:15:48 2020 libb2-0.98.1-2.fc31 tagged into f31-updates-candidate by bodhi [still active]
It was untagged from override by bodhi user on 2020-05-26. That's 3 days before the expiration. It looks like a bug in Bodhi service.
You can try to submit it into override again.
-- Petr
I have submitted the BR again but no use so far. I noticed that kojira ran a f31-infra-build task.
$ koji wait-repo f31-infra-build --build=libb2-0.98.1-2.fc31 Successfully waited 0:00 for libb2-0.98.1-2.fc31 to appear in the f31-infra-build repo
$ koji wait-repo f31-build --build=libb2-0.98.1-2.fc31
It has been at least 1 hour since I submitted the BR.
$ koji list-history --build libb2-0.98.1-2.fc31
<snip> Tue May 26 09:15:47 2020 libb2-0.98.1-2.fc31 untagged from f31-updates-testing by bodhi Tue May 26 09:15:47 2020 libb2-0.98.1-2.fc31 untagged from f31-override by bodhi Tue May 26 09:15:48 2020 libb2-0.98.1-2.fc31 tagged into f31-updates-candidate by bodhi [still active] Thu May 28 07:39:43 2020 libb2-0.98.1-2.fc31 tagged into f31-override by bodhi [still active]
Scratch build still does not pull in 0.98.1 [1]. From the build log,
DEBUG util.py:602: intltool noarch 0.51.0-15.fc31 build 55 k DEBUG util.py:602: libappstream-glib aarch64 0.7.17-1.fc31 build 316 k DEBUG util.py:602: libb2-devel aarch64 0.98-4.20171225git60ea749.fc31 build 8.8 k
:(
[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=45100671
epel-devel@lists.fedoraproject.org
-
Mukundan Ragavan -
Petr Pisar