Source: gnome-maps
Followup-For: Bug #1066083
X-Debbugs-Cc: la...@debian.org
Control: fixed -1 gnome-maps/47.0-1
Control: close -1
Source: gnome-maps
Followup-For: Bug #1066083
Control: tags -1 fixed-upstream
Source: gnome-maps
Followup-For: Bug #1066083
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/729
Process-wise: I think it makes more sense to set the 'forwarded' property
on this bug to the upstream issue I've reported, instead of the corresponding
merge request. This me
Source: gnome-maps
Followup-For: Bug #1066083
X-Debbugs-Cc: la...@debian.org
Control: forwarded -1
https://gitlab.gnome.org/GNOME/gnome-maps/-/merge_requests/453
Although a SOURCE_DATE_EPOCH-based approach was suggested in this bugreport,
I've independently opened an alternative that removes the
Source: gnome-maps
Followup-For: Bug #1066083
X-Debbugs-Cc: la...@debian.org
Please note: for some other GNOME appdata.xml files, upstream has preferred to
remove dynamic Meson release @date values entirely, which also achieves
reproducibility; that approach might be simpler and perhaps more align
Source: gnome-maps
Version: 46~beta-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed that
gnome-maps could not be bui
6 matches
Mail list logo
