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

Bug#675167: marked as done (pu: package figlet/2.2.2-1+squeeze1)



Your message dated Fri, 10 Aug 2012 00:28:43 +0200
with message-id <20120809222843.GA29788@spike.0x539.de>
and subject line Re: Bug#675167: Bug#674844: Bug#674850: Bug#675167: Bug#674850: RM: figlet -- RoQA; license which "specifically excludes the right to re-distribute"
has caused the Debian Bug report #675167,
regarding pu: package figlet/2.2.2-1+squeeze1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
675167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675167
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

Please remove figlet 2.2.2-1 from unstable, testing, stable and oldstable.

The package contains material that must not be distributed.  One example is
that the file fonts/8859-3.flc contains a license which "specifically excludes
the right to re-distribute".



--- End Message ---
--- Begin Message ---
On Sat, Jul 21, 2012 at 03:49:26PM +0100, Adam D. Barratt wrote:
> Aside from the question of whether the content can actually have
> authorship asserted over it in the first place, we've historically
> treated licensing issues in stable where the situation has subsequently
> been clarified in unstable as documentation updates which don't qualify
> for an update in stable on their own.
> 
> Particularly as the package in stable is in non-free I'm afraid I'm not
> currently convinced that the proposed changes should be applied in
> stable.

I also tend to say that documenting it in unstable is fine, given that
the file didn't really change and that the intention of the copyright
holder is that it's freely disseminated.

Jonathan, thank you for providing us with the update, though!

Kind regards
Philipp Kern

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply to: