sun-dlj-v1-1 license could not be presented

I wonder if it's because the new java license strictly forbids ubuntu from distributing Java as long as it can install gcj, kaffee, etc..?

The Fine license says:

    Sun also grants you a (...) limited license to reproduce and distribute the Software, (...) provided that you do not combine, configure or distribute the Software to run in conjunction with any additional software that implements the same or similar functionality or APIs as the Software;

Huh... I hadn't read the actual license before. I thought that the whole *point* of the DLJ was to make it possible for distros to include Java!

I also thought that it was developed in collaboration with some of the core Debian people (and you know *they* don't approve of legally encumbering stuff).

So... what's the deal?

Thanks for your bugreport.

What debconf frontend and priority did you set as default ("dpkg-reconfigure debconf" will tell you)

It works here just fine with the dialog fontend

Thanks,
 Michael

This happened to me too.
I was using "non-interactive" debconf frontend.
Switching to "dialog" worked as a workaround.

My recently filed bug #45442 is a dup of this, but has some more info.

Hi,

Unfortunately, that computer is dead (apparently, Dell's BIOS won't let you boot if the RTC goes down/gets corrupted). I might be able to answer anyway, though:

If "dialog" means a GUI dialog, then no, debconf has never opened anything GUI. Still a bug, in my opinion: what if you don't *have* X (e.g. on a server)?

If "dialog" means a "please read this license agreement"-type screen implemented via 'less', then I'm not sure.

Anyway, sorry about the timing. If I'd seen your question just a few hours earlier...

The machine on which I had the problem was configured with the noninteractive frontend. Mine (which worked) was configured with "Dialog".

Jon Anderson: "Dialog" doesn't use X, it seems to use a curses interface.

Well, I can't verify this on my PC (as I mentioned), but a curses dialog (or the message that I saw for non-interactive setups) seems very reasonable.

I guess that I'm satisfied with this package, then... the bug (feature request?) is more applicable to debconf than Java.

Changing package since it's not a Java bug but a debconf behaviour.

Debconf really ought to say something a little more sensical than "[license name] could not be presented"... something like

[license name] could not be shown and accepted since debconf is running non-interactively. Run 'dpkg-reconfigure debconf' to change this behaviour, or [do something else] to accept the license.

This isn't debconf's responsibility; debconf is a generic framework for asking questions, and already provides maintainer scripts all the necessary knowledge to handle this kind of situation themselves. The maintainer script using debconf should catch non-zero return codes from db_input and print a better error message.

(Blaming debconf for this is a little like blaming the C compiler because somebody displayed an unclear error message with printf()!)

It will install properly fron synaptic. I had the same problem installing from command line.

the debconf mode will be set to somethings else than noninteractive; also making the error message more prominent.

fixed in 1.5.0-07

* Give a more verbose error message when the license or the agreement
    question cannot be presented; point to 'dpkg-reconfigure debconf' to
    select a frontend other than noninteractive. Ubuntu #44891, #45292, #46096.