Dan, yes, something clearly needs to be done to prevent similar problems from happening again with future updates. This was discussed in the upstream bug report https://bugzilla.mozilla.org/show_bug.cgi?id=1553554, but no consensus was reached.
I am considering replicating what the Debian maintainers do, i.e. set MOZ_BUILD_DATE to the timestamp of the last debian/changelog entry (https://salsa.debian.org/mozilla-team/firefox/blob/release/master/debian/upstream.mk#L33). This is not foolproof though, as it will still require making sure that the changelog timestamp is exactly the same for all Ubuntu releases.
Dan, yes, something clearly needs to be done to prevent similar problems from happening again with future updates. This was discussed in the upstream bug report https:/ /bugzilla. mozilla. org/show_ bug.cgi? id=1553554, but no consensus was reached.
I am considering replicating what the Debian maintainers do, i.e. set MOZ_BUILD_DATE to the timestamp of the last debian/changelog entry (https:/ /salsa. debian. org/mozilla- team/firefox/ blob/release/ master/ debian/ upstream. mk#L33). This is not foolproof though, as it will still require making sure that the changelog timestamp is exactly the same for all Ubuntu releases.