GFileInfo Fix Survey 20231017 #4795
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MingcongBai
added
upgrade
|
LGTM on amd64: No error reported. |
OriginCode
approved these changes
Oct 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Topic Description
This topic addresses various
GFilewarnings after our recent GLib update.Refs:
flatpak updateshowsGFileInfo created without standard::sizeflatpak/flatpak#5340Package(s) Affected
appstreamv0.16.0-1gtk-3v3.24.28ostreev2023.1-2Security Update?
No
Build Order
Test Build(s) Done
Primary Architectures
amd64arm64Secondary Architectures
Architectural progress for "secondary," or experimental ports does not impede on merging of this topic.
loongson3mips64r6elppc64elriscv64