unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Frank Pursel <frank.pursel@gmail.com>
Cc: 32947@debbugs.gnu.org
Subject: [bug#32947] Add java-xalan.
Date: Thu, 14 Apr 2022 10:30:09 +0200	[thread overview]
Message-ID: <c0e41122e15cd3643ec2ffcf0ecd1af8ef831512.camel@telenet.be> (raw)
In-Reply-To: <CANp2FMcxbFARyTOH+7xdLeb+WGPxO1-LvEhaFAU=Le41tDRZMg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2847 bytes --]

Frank Pursel schreef op wo 13-04-2022 om 23:43 [+0000]:
> I think that IntStack.java has almost no economic value and so the
> comparison to a commercial package is not really appropriate.

It is not about the commercial aspect, it is about the potential
proprietariness.

> We are not asking for a bug fix, or for clarification of a
> behaviour.

Violating the (copyright, maybe contract) law seems like a bug to me
(TBC it is not known yet if this is the case, it just seems plausible
to me at this moment).

> We are questioning if they are meeting their own stated
> licensing criteria!

The problem is not if Apacha meets their own license (it seems that
they do, since they explicitly release the source code with their
license headers etc.  The potential problem is Sun's licensing of
JDK1.0, which we (as distribution) might indirectly be in violation of
by including java-xalan.

Also, it's all about how the question is framed -- asking ‘did you
violate the licensing terms’ doesn't seem advisable, but ‘Does IntStack
indeed come from JDK1.0, and if so, can I use it under the ASL license
like the rest?’ would just be asking for confirmation (and somewhat
positive, because it seems to imply we want to use xalan).

> I would feel bad asking this of them because I imagine they
> are no better equipped to answer questions about JDK1.0 than we are.

They are probably not well-equipped to answer questions about JDK1.0. 
However, they _are_ well-equiped to answer questions about theirselves,
presumably they remember what they mean by @since and where their
source code came from.

> Worse, if we believe such impropriety is possible why would be
> believe what they tell us anyway?

FWIW, IMO it would only be impropriety because of the current law (and
somewhat unclear attribution).  Also, by assuming good faith.

> I think to ask for this to be investigated,
> at minimum, you would need to find the actual file from JDK1.0 that
> you feel was appropriated.

JDK1.0 is propietary, why would I look into its sources?  Also,
probably the sources aren't available anyway, given that it is
proprietary.

> I don't think we should be asking upstream
> to work on investigation of a suspicious licensing that cannot
> improve their software in any functional way.

Moving from being in violation in the law to not seems like a
functional improvement to me (assuming it was actually in violation,
which has not been determined).  Illegal software is, for many
practical purposes, not functional.

More generally, ignorance is not an excuse, and I imagine willfull
ignorance to be even less so.

Anyway, I've sent a mail upstream, presumably it will eventually appear
in the archive at
<https://marc.info/?l=xalan-j-users&r=1&b=202204&w=2>.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-04-14  8:31 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 15:18 [bug#32947] [PATCH 0/3] Add java-xalan Danny Milosavljevic
2018-10-05 15:20 ` [bug#32947] [PATCH 1/3] gnu: Add java-cup Danny Milosavljevic
2018-10-05 15:20   ` [bug#32947] [PATCH 2/3] gnu: Add java-jakarta-regexp Danny Milosavljevic
2018-10-05 15:20   ` [bug#32947] [PATCH 3/3] gnu: Add java-xalan Danny Milosavljevic
2018-10-05 15:46     ` Julien Lepiller
2018-10-05 15:28   ` [bug#32947] [PATCH 1/3] gnu: Add java-cup Julien Lepiller
2018-10-05 16:00     ` Danny Milosavljevic
2018-10-05 16:13       ` Julien Lepiller
2018-10-05 15:52   ` Julien Lepiller
2018-12-19 14:05 ` [bug#32947] Add java-xalan Julien Lepiller
2022-03-17 21:08 ` Frank Pursel
2022-03-17 21:50   ` Maxime Devos
2022-03-17 21:53   ` Maxime Devos
2022-03-17 21:57   ` Maxime Devos
2022-03-18 17:40   ` Maxime Devos
2022-03-18 18:15     ` Frank Pursel
2022-03-18 18:22       ` Frank Pursel
2022-03-18 19:19         ` Maxime Devos
2022-03-18 17:29 ` Frank Pursel
2022-03-18 17:59   ` Maxime Devos
2022-03-18 19:16 ` Frank Pursel
2022-03-18 20:07   ` Maxime Devos
2022-03-18 20:42     ` Frank Pursel
2022-03-19 15:58     ` Maxime Devos
2022-03-22 17:45     ` Maxime Devos
2022-03-22 18:18       ` Julien Lepiller
2022-03-30 17:43     ` Maxime Devos
2022-03-30 18:41       ` Maxime Devos
2022-03-30 20:23         ` Frank Pursel
2022-04-03  8:32     ` Maxime Devos
2022-04-05 13:12     ` Maxime Devos
2022-04-05 21:09       ` Frank Pursel
2022-04-09 13:40       ` Maxime Devos
2022-04-11 16:36         ` Frank Pursel
2022-04-12  9:32           ` Maxime Devos
2022-04-13 23:43             ` Frank Pursel
2022-04-14  8:30               ` Maxime Devos [this message]
2022-04-14 16:07                 ` Frank Pursel
2022-04-14 20:33       ` Maxime Devos
2022-04-14 20:49         ` Frank Pursel
2022-04-16 21:02   ` Maxime Devos
2022-04-19 17:13     ` Frank Pursel
2022-04-19 18:44       ` Maxime Devos
2022-04-19 18:55         ` Frank Pursel
2022-03-19 15:41 ` Frank Pursel
2022-03-19 16:38 ` Frank Pursel
2022-03-23  1:32 ` Frank Pursel
2022-03-23 14:14 ` Frank Pursel
2022-08-19 22:05   ` Vagrant Cascadian
2022-06-24 15:23 ` [bug#32947] [PATCH 0/3] Add java-xalan: reverse ping Maxime Devos
2022-07-14 23:46 ` [bug#32947] [PATCH 0/3] Add java-xalan Frank Pursel
2022-08-20  0:57 ` [bug#32947] Add java-xalan-interp Frank Pursel
2022-09-20 21:25 ` [bug#32947] Add java-xalan-interp CVE Frank Pursel

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=c0e41122e15cd3643ec2ffcf0ecd1af8ef831512.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=32947@debbugs.gnu.org \
    --cc=frank.pursel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).