Bug#736760: Conflict between debian/upstream (DEP-12) & debian/upstream/ (uscan)

David Prévot taffit at debian.org
Mon Feb 10 19:37:54 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Le 10/02/2014 08:36, Andreas Tille a écrit :

> I wonder in how far it is to late for debian/watch and not for the file
> debian/upstream.  Yey, I'm aware that we have two to three orders of
> magnitude more debian/watch files than debian/upstream files

I’m not sure were you got those numbers, but it seems there are far more
debian/watch files than debian/upstream files in the archive (way more
than three times). Can somebody please enlighten us with factual numbers?

>> That said I also agree that this change is mainly a matter of coherence
>> and esthetics and thus should not break anything and thus everything
>> should support both locations for a long period of time.
> 
> Seems we all agree on the esthetics issue but I for myself would think
> that *if* we go for esthetics than we should make this strict and
> complete or not at all.  Otherwise I see no point in wasting developer
> time for half baken things.

It seems a bit irrelevant to force hard conditions to improvements:
moving the very young debian/upstream file to a more accurate
debian/upstream/$metadata place should not be conditioned to moving the
“very old” and already highly used debian/watch file to the same
directory. If we could first agree on debian/upstream/ being the right
place for upstream related data/files, then it would make sense to
discuss and propose a plan to move the watch file there too (but can we
please have this other discussion if/once we agree on a common directory
first).

If I understood correctly, the DEP-12 metadata file is used by a pair of
tools, and James started to propose patches to support both paths in
order to allow a smooth transition. So the technical issue could be
considered (being) taking care of.
If I understood correctly, the following step would be to move (in the
packages’ VCS) one file to its new path. Considering most of the
concerned packages may be team-maintained, I’d be happy to offer my
hands in order help this transition and (momentarily) join the relevant
teams to (help and) do this not rewarding job.

Regards

David


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJS+SqSAAoJEAWMHPlE9r088j0H/jkVjV+5/lkjH1Vaml7chwof
rJ3qcA8saifU/MuGmR/MWJ5Ct8S9QoKDi1zhyl/JiTmKJw9NRJp0NrPosN5M4F5o
w3ICUQh0QkNsuD8XrNQ0iQ6cFNgAljaRaNjShiBSW0R61OYqPH+jx9rxT62LoFyP
qpbZoBra1Uf9Oz3Qr8839tneLCBr2521TUga+9xCRBzIxOK02lIwwHtVrIvLda6Q
Bg5IGdKrGN6frU2OszQSKXO2IkIUkCD26ahrBx6lPOmnAtOO6ftIRi4luJT7n2NV
Y/TMGOFn73b0WgZwiTD2JPYRVZirxqdiyEBczFrJ0y3ikMoeZ/jYmZOHva435cI=
=aBEs
-----END PGP SIGNATURE-----



More information about the devscripts-devel mailing list