unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Tommi Höynälänmaa" <tommi.hoynalanmaa@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: A problem with licenses
Date: Sat, 02 Jun 2018 15:21:26 -0400	[thread overview]
Message-ID: <87sh65c7ux.fsf@netris.org> (raw)
In-Reply-To: <bdd4de80-93db-4ec9-1527-4698036f5c53@gmail.com> ("Tommi \=\?utf-8\?B\?SMO2eW7DpGzDpG5tYWEiJ3M\=\?\= message of "Wed, 30 May 2018 13:36:43 +0300")

Tommi Höynälänmaa <tommi.hoynalanmaa@gmail.com> writes:

> I have published some guile-based software under GNU GPL and
> LGPL. However, when I open the Debian packages with Ubuntu Software
> Installation (18.04) the application claims that the software is
> proprietary. How can I fix this?

I don't know, it depends on how that software installing application
determines the licenses of packages.  This sounds like a question for
Ubuntu.  The Debian community might also know.

      Mark



  parent reply	other threads:[~2018-06-02 19:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 10:36 A problem with licenses Tommi Höynälänmaa
2018-05-30 10:42 ` tomas
2018-06-02 19:21 ` Mark H Weaver [this message]
2018-06-02 21:07 ` tomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sh65c7ux.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guile-devel@gnu.org \
    --cc=tommi.hoynalanmaa@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).