Hi,
Sorry for being late to the party here..
(Thanks to Myon for pinging me about this today)
So, it seems that my solution to this issue was not understood. It is
*expected* (and wanted!) that tests would start failing as soon as a new
tzdata release is uploaded. The solution is just to
I noticed in the debian/rules that rebuilding the timezone JS data from the
tzdata package is *optional*, and only occurs if the moment-timezone
package has a +x suffix, e.g. +2021e. If not, the timezone JS data from
the upstream moment-timezone source will be used.
I just tried building
This bug is now blocking Prometheus (which I co-maintain) from
transitioning to testing.
In the meantime, I see that there is a new release of moment-timezone.js
upstream (0.5.34) which updates the IANA TZDB to 2021e, and would thus
perhaps resolve the test failures that I see when trying to
Control: tag -1 - pending
On Wed, Oct 27, 2021 at 09:13:11AM +, Yadd wrote:
> Control: tag -1 pending
>
> Hello,
>
> Bug #997736 in moment-timezone.js reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message be
Source: moment-timezone.js
Version: 0.5.32+dfsg1-2+2021a
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
5 matches
Mail list logo
