Bug#774274: fontforge: please use SOURCE_DATE_EPOCH for reproducible font modification time

2019-09-20 Thread Theppitak Karoonboonyanan
Package: fontforge Version: 1:20170731~dfsg-1+b2 Followup-For: Bug #774274 Hi, Just seen Vasudev's comment from the bug log. There are three relevant commits: 1. Add GetTime function: override time(2) in case SOURCE_DATE_EPOCH is set https://github.com/fontforge/fontforge/commit/4e850c13420

Bug#774274: fontforge: please use SOURCE_DATE_EPOCH for reproducible font modification time

2019-02-02 Thread Vasudev Kamath
Theppitak Karoonboonyanan writes: > Package: fontforge > Version: 1:20170731~dfsg-1 > Followup-For: Bug #774274 > > Dear Maintainer, > > This bug still exists for Type 1 font generation, which causes my package > fonts-sipa-arundina to be unreproducible. > > https://tests.reproducible-builds.org/

Bug#774274: fontforge: please use SOURCE_DATE_EPOCH for reproducible font modification time

2019-01-11 Thread Theppitak Karoonboonyanan
Package: fontforge Version: 1:20170731~dfsg-1 Followup-For: Bug #774274 Dear Maintainer, This bug still exists for Type 1 font generation, which causes my package fonts-sipa-arundina to be unreproducible. https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/fonts

Bug#774274: [Pkg-fonts-devel] Bug#774274: fontforge: please use SOURCE_DATE_EPOCH for reproducible font modification time

2017-05-06 Thread Vasudev Kamath
Justin Cappos writes: > found 774274 > forwarded 774274 https://github.com/fontforge/fontforge/issues/2490 > done > > The changelog doesn't seem to indicate that the upstream patch was > applied. This seems to be fixed in upstream master on November 16th, 2016 > as per ( https://github.com/fontf

Bug#774274: fontforge: please use SOURCE_DATE_EPOCH for reproducible font modification time

2017-05-05 Thread Justin Cappos
found 774274 forwarded 774274 https://github.com/fontforge/fontforge/issues/2490 done The changelog doesn't seem to indicate that the upstream patch was applied. This seems to be fixed in upstream master on November 16th, 2016 as per ( https://github.com/fontforge/fontforge/issues/2490 ). This m