[Debichem-devel] Conflict between debian/upstream (DEP-12) & debian/upstream/ (uscan)

[Simon Kainz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Am 2014-02-23 09:01, schrieb Andreas Tille:
> Hi Simon,
> 
> I have no idea whether you did follow the discussion but it would
> be great if you could submit a patch to the lintian check you
> recently wrote.  The upstream files will be moved from
> debian/upstream (the file) to debian/upstream/metadata.
> 
Hello,

i didn't follow _this_ discussion but still got aware of this issue.
I'll come up with a patch soon.
Thank you for pointing me to this.

Bye,

> Kind regards
> 
> Andreas.
> 
> On Sat, Feb 22, 2014 at 08:34:31AM +0100, Bastien ROUCARIES wrote:
>> Le 12 févr. 2014 15:41, "Andreas Tille" <andreas at an3as.eu> a
>> écrit :
>>> 
>>> Hi,
>>> 
>>> On Wed, Feb 12, 2014 at 04:11:41PM +0900, Charles Plessy
>>> wrote:
>>>> Le Wed, Feb 12, 2014 at 12:06:42AM -0500, James McCoy a écrit
>>>> :
>>>>> 
>>>>> That being said, I don't have access to most of the
>>>>> packages.  Even
>> if I
>>>>> did, it feels "dirty" to go and commit to a couple hundred
>>>>> packages I have no involvement with instead of adapting two
>>>>> pieces of software to deal with both path names.
>>>> 
>>>> Hi James,
>>>> 
>>>> you already have commit access to the Debian Med packages,
>>>> like all
>> other
>>>> Debian developers.  Please go ahead !
>>> 
>>> I take this "go ahead" for "yes, I accept the move".  While I
>>> would have no problems with this I wonder if it is appropriate
>>> to simply go on here without at least informing Debian Science
>>> and DebiChem who also maintain some d/upstream files.  If I
>>> might have sounded against the move in the past my main problem
>>> was that the affected parties were not included into the
>>> decision making process.
>> 
>> Lintian vive pièce of advice for using debian/upstream file....
>> 
>> I think the problem will more important than you think
>> 
>> Bastien
>>> So I have put the relevant mailing lists in CC to at least give
>>> people lurking there some heads up and a slight chance to
>>> insist.
>>> 
>>> I would say:  If nobody will insist until after the weekend we
>>> might go ahead.  And for the actual action I agree with Charles
>>> that I see no problem if James would simply commit a change to
>>> Debian Med repositories (SVN and Git).  That's fine and would
>>> save us (me or Charles) some work and is perfectly possible
>>> permission-wise.
>>> 
>>> Kind regards
>>> 
>>> Andreas.
>>> 
>>> PS: I think I did not got any answer to my question about
>>> further plans for the debian/upstream/ dir.  I would be really
>>> happy to understand the big picture to make sure we will not
>>> again invent something which needs to be changed later on.
>>> 
>>> -- http://fam-tille.de
>>> 
>>> 
>>> -- To UNSUBSCRIBE, email to
>>> debian-science-request at lists.debian.org with a subject of
>>> "unsubscribe". Trouble? Contact
>> listmaster at lists.debian.org
>>> Archive:
>>> http://lists.debian.org/20140212143924.GA21313@an3as.eu
>>> 
> 


- -- 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJTDGKKAAoJEBy08PeN7K/pUcUQAKcR3fFPosOIe30bOEbs94nt
0S/mQpNt0rg1vdmKngaE2LASGr1YP1DBnicaS2TgHEllH7M15hVBSX4jgGtz4UtV
HtV0VEwdaBO9xCwpDlnWxNJUOtGidp9zoBbFIIE2YRaGJgR6QZq0d30v67M2m8/X
I5l4V4dkla/cTW8+QS94mMJ2KWyP20f+GC99J2ht8JEw/IkDkNi3CObX9Yl0bifv
ucwcUiQTtn9TAspdlpllFvrhjTpxkUfc4UtazHcgbtaFFoaDsfMd/ScTegoplwpc
9T4WxNYijDxvjPpUR2pnJ2WK08asAgBw9bko/Fkp1xsYFfwktwuzE0mzxkUFEvXY
W2Zs+6kDat8mqkl22N2749Hw0HECcbByvmjmSbBgOoy5cjNWKxWvnWwjmsmNuYLR
BXznxu7GWVSQguSTA+ug0h52wChmVKNGhb7VESwtWQfN/6vxXtWZiZQ8CQpShYWe
6bFlIIeKf63ILl6trxjpsUyKZF8SRx2q+83RMkw3khsHW8D6g+dVXxJ8+LXdsEOx
11fmpM5N+SpMof88TseCubVrZAwbO0zhunMtOv5ulOpSA3mkij3no32KfaMxLEa7
PpZiU2D4wuOQRqY02cg5BKjTeRw7hV4372tRjIrt2i4E0i4m6ErttqKWfsywmus3
SvfobREfHz97cYzFRoCz
=bRJI
-----END PGP SIGNATURE-----