[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#829027: [jwilk@debian.org: Re: Bug#829027: libstroke: missing/obsolete coypright information]



Dear Hamish,

I'm sorry to bother you about a package you have orphaned, but do you
recall where you downloaded the original sources for libstroke?

In the copyright file you said that you got them from etla.org, but per
the below e-mail, they weren't available from etla.org at the time you
uploaded the package to Debian.  Did you download them in 1999 and then
just not get around to uploading until 2002?

Hopefully we don't have an unfixable RC bug here.

Thanks!

----- Forwarded message from Jakub Wilk <jwilk@debian.org> -----

Date: Fri, 1 Jul 2016 01:19:23 +0200
From: Jakub Wilk <jwilk@debian.org>
To: Vincent Lefevre <vincent@vinc17.net>, 829027@bugs.debian.org
Cc: Sean Whitton <spwhitton@spwhitton.name>
Subject: Re: Bug#829027: libstroke: missing/obsolete coypright information
User-Agent: Mutt/1.5.23.1 (2014-03-12)
Message-ID: <[🔎] 20160630231923.GA2260@jwilk.net>

* Vincent Lefevre <vincent@vinc17.net>, 2016-06-30, 14:34:
>>> The Debian policy manual says:
>>> 
>>> "In addition, the copyright file must say where the upstream sources
>>> (if any) were obtained, and should name the original authors."
>> 
>> This clause is made up of two requirements:
>> 
>> 1. "the copyright file must say where the upstream sources ... were
>> obtained"
>> 
>> 2. "the copyright file ... should name the original authors"
>> 
>> libstroke does not violate the first requirement: the copyright file
>> does say where the upstream sources /were/ obtained, even though they
>> can no longer be obtained there.

According to archive.org, http://www.etla.net/ stopped mentioning libstroke
somewhere between February and March 1999. The current upstream release was
first uploaded in 2002, when the link was already invalid.

> I thought that it would still be needed as long as the package is in
> Debian (so that users could check too) so that the location should
> implicitly still be valid.

No, there's no such requirement.

-- 
Jakub Wilk

----- End forwarded message -----

-- 
Sean Whitton


Reply to: