[buildd-tools-devel] Bug#834736: Bug#834736: sbuild: Use basic format for ISO 8601 timestamps (for build logs filenames)

Santiago Vila sanvila at unex.es
Fri Aug 19 12:46:26 UTC 2016


On Fri, Aug 19, 2016 at 01:50:49PM +0200, Johannes Schauer wrote:

> [...]
> I hereby offer you to write a script that converts your collection of existing
> build logs using the old format into the new format. Would that help you?

I already did that two hours ago, but thanks a lot for the offer :-)

(Well, I actually converted everything to the basic format, which I
definitely prefer).

> [...]
> So what I need from you is an argument that shows me that adding this feature
> gives a great enough benefit that outweighs the cost of additional complexity
> in sbuild. As far as I see it (and I might be wrong so please correct me if I
> am), this change only makes a very tiny number of people unhappy and even the
> unhappy people have workarounds (like yours for awk) that are trivial to
> implement. Are your few characters more in your awk script worth such a change
> for sbuild that we will have to keep maintaining for years?
> 
> What do you think?

I think it's soon to measure the "number of unhappy people", because the
change in the filename format is very recent.

It's not for the parsing, really. I find the basic format
aesthetically more pleasant to my eyes when used in filenames.

(Some filenames are already very long, and this change makes them to
be even longer).

Sure, that's not a technical reason, but for me it has been enough
to rename all my build logs to use the basic format.

So my proposal/suggestion about this bug would be: keep it open, do nothing
about it, and wait for someone to write a patch (maybe somebody like
me who thinks that two people renaming their build logs are already
too many people to not have this feature in sbuild itself).

Thanks.



More information about the Buildd-tools-devel mailing list