Latest upstream release: 3.4.0-rc1 Current version/release in rawhide: 3.3.6-1.fc36 URL: https://nextcloud.com/install/#install-clients Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/18381/
Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-ammktjsc/nextcloud-client.spec'] returned 1: b'error: Bad source: ./desktop-3.4.0.tar.gz: No such file or directory\n'
Latest upstream release: 3.4.0-rc2 Current version/release in rawhide: 3.3.6-1.fc36 URL: https://nextcloud.com/install/#install-clients Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/18381/
Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-4qe201qk/nextcloud-client.spec'] returned 1: b'error: Bad source: ./desktop-3.4.0.tar.gz: No such file or directory\n'
Latest upstream release: 3.4.0 Current version/release in rawhide: 3.3.6-1.fc36 URL: https://nextcloud.com/install/#install-clients Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/18381/
Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-0rj1649x/nextcloud-client.spec'] returned 1: b'error: Bad source: ./xcb_3.4.0.patch: No such file or directory\n'
I will update this soon.
Hi Mukundan, I recently found this remark: https://github.com/nextcloud/desktop/issues/1977#issuecomment-892113790 Maybe you could patch the Fedora Nextcloud Desktop config file to show the main dialog as a normal window? I tested this just today with the current 3.3.6 release, and it seems to work well. Having a normal window is more in line with the normal Linux GNOME (and maybe also KDE) desktop. Another remark: Nextcloud Desktop really seems to need the status indicator to be able to use it normally. Therefore you might consider having the nextcloud-client package to require gnome-shell-extension-appindicator.noarch.
Thanks for the comment I will take a look at both items prior to updating.
Latest upstream release: 3.4.0-do-not-use Current version/release in rawhide: 3.3.6-1.fc36 URL: https://nextcloud.com/install/#install-clients Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/18381/
Skipping the scratch build because an SRPM could not be built: ['fedpkg', '--user', 'hotness', 'sources'] returned 1: b''
There appears to be a major issue with 3.4.0 https://github.com/nextcloud/desktop/issues/4016 Will update only when new minor release is available.
Latest upstream release: 3.4.1 Current version/release in rawhide: 3.3.6-1.fc36 URL: https://nextcloud.com/install/#install-clients Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/18381/
Scratch build failed. Details bellow: BuilderException: Build started, but failure happened during post build operations: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-emjsqa_r/nextcloud-client.spec']' returned non-zero exit status 1. StdOut: error: Bad source: ./xcb_3.4.1.patch: No such file or directory 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 188, 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
Any updates now that the patch version has been updated and the issue is marked resolved?
Not sure what server version you are running. Please see this - https://github.com/nextcloud/desktop/issues/4141 Bugs are unavoidable, of course. But, this seems to break basic functionality of a sync client. :(
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
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-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 Mukundan Ragavan from comment #15) > Not sure what server version you are running. Please see this - > https://github.com/nextcloud/desktop/issues/4141 > > Bugs are unavoidable, of course. But, this seems to break basic > functionality of a sync client. :( @nonamedotc The issue with the sync engine seem to have been disabled in the recent server builds. Are there other crucial standing issues? Because these releases contain some important bug fixes to the exlude-files behavior.
I am going to update to 3.4.4 directly.
Can you try this and provide feedback? F36 - https://koji.fedoraproject.org/koji/taskinfo?taskID=84531183 rawhide - https://koji.fedoraproject.org/koji/taskinfo?taskID=84531180
Actually I am on F35, so I can't try them easily
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.
(In reply to Mukundan Ragavan from comment #24) > Can you try this and provide feedback? > > F36 - https://koji.fedoraproject.org/koji/taskinfo?taskID=84531183 > rawhide - https://koji.fedoraproject.org/koji/taskinfo?taskID=84531180 Ok, I've checked out https://koji.fedoraproject.org/koji/buildinfo?buildID=1938332 which seems to be for F35. I don't think there are critical bugs, but the ones I was able to catch: - The pop-up screen is in the middle of the screen and cannot be moved. Should check if this is not a build issue. - If you delete some files on the server UI (`.sync-exclude.lst`) the sync process errors out `Could not read system exclude file`. After some resets, this gets back to normal, and I do not notice it resulting in unwanted behaviour. This is most likely an upstream issue Are there any other specific issues to look out for?
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-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.