I am changing the recipient bug to the reproducible issue and the 2014 issues as this is unrelated to the FTCBFS issue. (So many bugs!)
In the absense of better solutions for these bugs, please apply my patch anyway. On Mon, Jul 20, 2015 at 09:08:10PM +0200, Michael Meskes wrote: > On Sun, Jul 19, 2015 at 03:54:55PM +0200, Helmut Grohne wrote: > > As an aside note, I question the use of python-hdate to compute the > > Jewish calendar: > > * Since the build date is used to select the year of the calendar file, > > the package is not reproducible. (Ccing the reproducible people) > > * The last build happened in 2014, so the installed calendar is no > > longer useful for day to day use (neither in stable nor in unstable). > > Absolutely agreed. Any idea how to fix this? So for the reproducible issue the canonical fix is to use the year of the most recent entry in debian/changelog. The reproducible people have recipes for this and generally help with such issues. I suggest asking reproducible-bui...@lists.alioth.debian.org or #debian-reproducible at OFTC for help. The usefulness issue is harder. I have little clue about the file format, but since Debian stable releases are valid for multiple years (5 when considering LTS), the only way seems to be to store the dates for multiple years (ideally 10 or more) in that calendar file. When doing that, using the most recent debian/changelog entry becomes a useful reference point. It still means that you want to upload bsdmainutils at least once per Debian release, but that seems like a given anyway. Hope this helps Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
