On 2/11/21 1:40 PM, Miro Hrončok wrote:
> Ad side-tags:
>>
>> IMO the process should work for buildroot overrides too. Side tags look
>> good for big rebuilds, where not all packages belong to one maintainer,
>> but it looks like an overhead for only two packages.
>
> If you want multiple (even two
On 11. 02. 21 13:33, Zdenek Dohnal wrote:
Thanks, Miro!
foomatic-db build is now in testing and I was able to create a override
for it, but when I built foomatic, it got into bodhi automatically and
now I cannot add foomatic build to foomatic-db update to prevent
foomatic landing into stable tha
Thanks, Miro!
foomatic-db build is now in testing and I was able to create a override
for it, but when I built foomatic, it got into bodhi automatically and
now I cannot add foomatic build to foomatic-db update to prevent
foomatic landing into stable than foomatic-db.
I cannot even unpush the foo
On 10. 02. 21 16:24, Miro Hrončok wrote:
You need a buildroot override, but the bodhi CLI will tell you:
"Invalid build. It must be tagged as either candidate or testing."
But the web UI allows it :/
Correction. This part is not true, I had a typo in the build NEVR.
--
Miro Hrončok
--
Phone
On 10. 02. 21 9:09, Zdenek Dohnal wrote:
Hi all,
I have started foomatic-db+foomatic chainbuild this morning for F34 and
it has been opened for 2 hours till now. Is it expected?
IIUC I don't need a buildroot override yet, since F34 hasn't been
enabled in bodhi. So the process should be the same
Hi all,
I have started foomatic-db+foomatic chainbuild this morning for F34 and
it has been opened for 2 hours till now. Is it expected?
IIUC I don't need a buildroot override yet, since F34 hasn't been
enabled in bodhi. So the process should be the same as in rawhide.
Does anyone know what's go
