Bug 2047521

Scratch build failed. Details bellow:

BuilderException: Build started, but failure happened during post build operations:
Command '['git', 'commit', '-a', '-m', 'Update to 3.4.2 (#2047521)']' returned non-zero exit status 1.

StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	SRPMS/

nothing added to commit but untracked files present (use "git add" to track)


Traceback:
  File "/usr/local/lib/python3.9/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 226, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

the-new-hotness/release-monitoring.org's scratch build of nextcloud-client-3.4.1-1.fc34.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=82043111

I will take care of this. along with FTBFS from f36 mass rebuild.

FEDORA-2022-9e56832107 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9e56832107

FEDORA-2022-23aa0e100b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-23aa0e100b

(In reply to Mukundan Ragavan from comment #3)
> I will take care of this. along with FTBFS from f36 mass rebuild.

ah, didn't see this, sorry. I've updated to 3.4.2, but looks like https://github.com/nextcloud/desktop/issues/4141 is still not closed so we probably shouldn't push it to F35/F34 yet anyway.

The FTBFS is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=2041135 - I've reported it upstream, GH issue linked in that bug, but haven't had time to dig down and fix it (annoyingly, the GCC 12 porting guide is still incomplete too, and doesn't cover this issue yet).

FEDORA-2022-9e56832107 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-9e56832107`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9e56832107

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

(In reply to Michel Alexandre Salim from comment #6)
> (In reply to Mukundan Ragavan from comment #3)
> > I will take care of this. along with FTBFS from f36 mass rebuild.
> 
> ah, didn't see this, sorry. I've updated to 3.4.2, but looks like
> https://github.com/nextcloud/desktop/issues/4141 is still not closed so we
> probably shouldn't push it to F35/F34 yet anyway.
> 


Sounds like a good plan. Thanks for updating.



> The FTBFS is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=2041135
> - I've reported it upstream, GH issue linked in that bug, 

Noticed. I believe I am also subscribed to that bug.

>but haven't had
> time to dig down and fix it (annoyingly, the GCC 12 porting guide is still
> incomplete too, and doesn't cover this issue yet).

Ah, that's why I could find no reference on how to fix this. Most unfortunate. Hopefully, the porting guide will be up soon.

FEDORA-2022-23aa0e100b has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-23aa0e100b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-23aa0e100b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-ec5899c99a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ec5899c99a

FEDORA-2022-85f951d527 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-85f951d527

FEDORA-2022-85f951d527 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-85f951d527`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-85f951d527

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-ec5899c99a has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-ec5899c99a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ec5899c99a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-85f951d527 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-85f951d527`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-85f951d527

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-ec5899c99a has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2022-85f951d527 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.