After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 790251 - non-ISO-C and non-deprecated-API warnings.
non-ISO-C and non-deprecated-API warnings.
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: Nautilus
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2017-11-12 13:56 UTC by Clement Hermann (nodens)
Modified: 2018-08-03 19:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Fix non-ISO-C and non-deprecated-API warnings. (3.85 KB, patch)
2017-11-12 13:56 UTC, Clement Hermann (nodens) 		needs-work Details | Review

Description Clement Hermann (nodens) 2017-11-12 13:56:27 UTC 
Created attachment 363444 [details] [review]
Fix non-ISO-C and non-deprecated-API warnings.

Hi,

while giving some love to seahorse-nautilus in Debian (it was removed from testing, and it would affect Tails), we fixed some building issues.

Some non-ISO-C and non-deprecated-API warnings are triggered while building with current Debian gcc version.

Please find a patch attached.

Cheers,

--
Debian Privacy Tools maintainers
Comment 1 Niels De Graef 2017-11-13 18:35:50 UTC 
Review of attachment 363444 [details] [review]:

Hey Clement,

Thanks for patch again! However, when i try to apply it, I get the following error:

> error: corrupt patch at line 36

Looking at the raw patch, it seems like you're missing some leading whitespace
(maybe due to some rogue editor setting?). Anyway, would you mind re-submitting the patch with the necessary fixups?

Cheers,
Niels
Comment 2 GNOME Infrastructure Team 2018-08-03 19:55:23 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/seahorse/issues/169.