Bug#833821: txtorcon: Should age() use an old new timestamp?

[Petter Reinholdtsen] > I noticed this issue because the package fail to build reproducably, and > sphinx generate documentation where the now statement below is replaced > with a concrete timestamp. See for the details about this. Gah, forgot to insert the URL to the sphinx bug report. It is

Bug#833821: txtorcon: Should age() use an old new timestamp?

Package: txtorcon Version: 0.15.0-1 Tags: patch I noticed this issue because the package fail to build reproducably, and sphinx generate documentation where the now statement below is replaced with a concrete timestamp. See for the details about this. But while looking at the code, it occured