Debian tag2upload service writes ("[tag2upload 3342] uploaded hippotat 1.3.2"):

Getting rid of these is likely to be (in some cases, is known to be)
political.

I don't think we want to change the directory name.  Fixing this is
likely to involve battling the notion that 1.0 shouldn't be used.

I experimented, and this seems only to happen in tag2upload.  I
repro'd it locally and have made dgit!459 with an attempt at a fix.

We can probably just change these in the image builder script.
(But we don't have any tests for it.)

Ian.

Ian Jackson writes ("Bug#1131609: many spurious warnigns in tag2upload logs"):
...

This didn't work.  Passing -S to dpkg-genchanges causes it to omit
the .git.tar.zx.

Ian.

Ian Jackson <ijackson@chiark.greenend.org.uk> [22/Mar 10:47pm GMT] wrote:

Yup.  There's as comment about this in build_source in dgit.

Ian Jackson writes ("Bug#1131609: many spurious warnigns in tag2upload logs"):

To fix this, we have two options:

 1. Have dgit conditionally pass these options based on the source
    format.  That risks breakage with new source formats but such
    things are not very likely and would be a big deal anyway.

 2. Refer #1123661 to the Technical Committee.

    (Unless you think it's worth asking Guillem again, but I think
    there are no arguments we could make that I didn't already make
    and were rejected.)

I am still firmly of the opinion that the dpkg-source behaviour here
is wrong.  By referring the bug to the TC we would be doing everyone
who needs to use dpkg-source a service (assuming the TC would agree
with us).

But any such fix would take years to reach deployment so we might want
to do 1 as well.

This is going to be even worse.

Ian.

Ian Jackson writes ("Bug#1131609: many spurious warnigns in tag2upload logs"):

Done in dgit!464.  Will take a while to get deployed since it has
missed this week's upload.

Ian.