Bug 2041135 - nextcloud-client FTBFS with GCC 12: 'standard attributes in middle of decl-specifiers'
Summary: nextcloud-client FTBFS with GCC 12: 'standard attributes in middle of decl-sp...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nextcloud-client
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-16 04:43 UTC by Michel Lind
Modified: 2022-05-07 04:11 UTC (History)
8 users (show)

Fixed In Version: nextcloud-client-3.4.4-1.fc35 nextcloud-client-3.4.4-3.fc36
Clone Of:
Environment:
Last Closed: 2022-04-11 17:16:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
build.log (55.77 KB, text/plain)
2022-01-16 04:43 UTC, Michel Lind
no flags Details
root.log (214.26 KB, text/plain)
2022-01-16 04:43 UTC, Michel Lind
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github nextcloud desktop issues 4180 0 None open Build failure on GCC 12 because standard attributes are present in the middle of decl-specifiers 2022-01-16 04:43:05 UTC

Description Michel Lind 2022-01-16 04:43:06 UTC
Created attachment 1851081 [details]
build.log

nextcloud-client fails to build with GCC 12 with

/builddir/build/BUILD/desktop-3.4.1/redhat-linux-build/src/csync/nextcloud_csync_autogen/AAGGKE4ILT/../../../../../src/common/vfs.h:171:13: error: standard attributes in middle of decl-specifiers
  171 |     virtual Q_REQUIRED_RESULT Result<void, QString> updateMetadata(const QString &filePath, time_t modtime, qint64 size, const QByteArray &fileId) = 0;
      |             ^~~~~~~~~~~~~~~~~

Comment 1 Michel Lind 2022-01-16 04:43:39 UTC
Created attachment 1851082 [details]
root.log

Comment 2 Ben Cotton 2022-02-08 21:11:19 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 3 Fedora Update System 2022-03-24 13:53:17 UTC
FEDORA-2022-ec5899c99a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ec5899c99a

Comment 4 Fedora Update System 2022-03-24 18:08:54 UTC
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.

Comment 5 Fedora Update System 2022-03-25 23:25:28 UTC
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.

Comment 6 Fedora Update System 2022-04-01 23:22:55 UTC
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.

Comment 7 Fedora Update System 2022-04-11 17:16:45 UTC
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.

Comment 8 Fedora Update System 2022-05-07 04:11:48 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.