Re: Debian Policy 220.127.116.11 released
- Date: Sun, 08 Apr 2018 10:58:53 +0200
- From: Ole Streicher <olebole@xxxxxxxxxx>
- Subject: Re: Debian Policy 18.104.22.168 released
Andreas Metzler <ametzler@xxxxxxx> writes:
> Ole Streicher <olebole@xxxxxxxxxx> wrote:
>> Sean Whitton <spwhitton@xxxxxxxxxxxxxx> writes:
>>> On Sat, Apr 07 2018, Ole Streicher wrote:
>>>> Sure, but why do we give up a common rule? I think the cases where
>>>> d/watch does not work are not so rare (at least I have quite a number
>>>> of them), and keeping them unified is not the worst thing we can do.
>>> See discussion in #515856.
>> Maybe I didn't read it too carefully, but I didn't find the argument why
>> get-orig-source is not kept for the cases where uscan doesn't do the
>> And when I extrapolate from my packages, this is not an exceptionally
>> rare case.
> Imho Sean's last mail sums it up pretty well
I have read this, but it does not convince me. My rule to get the
upstream packagage was always: use uscan, if d/watch exists, otherwise
use get-orig-source. Sounds pretty simple and straigt-forward. If it
fails, I had a starting point where to debug (usually just a missing
dep). I see no reaso why this should be given up.