Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

https-everywhere: xpi timestamp of files is 1/1/1980 #17618

Closed

Description

@apoleon

This is Debian bug

https://bugs.debian.org/925177

The timestamp of files in the distributed xpi version of https-everywhere dates back to January 1980 on Linux systems. Obviously this is not accurate.

Once https-everywhere shipped a script in utils/create_xpi.py that was responsible for creating the xpi file. It just lacked a date_time parameter.

https://salsa.debian.org/webext-team/https-everywhere/blob/99fcc50e0bb5617c64e55457a7b3e502013e0dc8/debian/patches/use-newer-timestamp-date.patch

Debian applied the aforementioned patch to change the timestamp to a recent value. The create_xpi.py script does not exist anymore but maybe you want to correct this anyway. You can easily reproduce this issue by unpacking the xpi file on a Debian GNU/Linux system.

Activity

  1. pipboy96 commented on Mar 21, 2019

    @pipboy96
    Contributor

    @apoleon This is expected, it's needed for reproducible builds.

  2. apoleon commented on Mar 21, 2019

    @apoleon
    Author

    This shouldn't be necessary for reproducible builds because several alternatives are known.

    https://wiki.debian.org/ReproducibleBuilds/Howto

    https://wiki.debian.org/ReproducibleBuilds/TimestampsInTarball

  3. pipboy96 commented on Mar 21, 2019

    @pipboy96
    Contributor

    @apoleon Can you try implementing one of such alternatives?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions