Bug 27875 - java3d package "have to be removed for others to be upgraded" when upgrading from Mageia 7 to Mageia 8.
Summary: java3d package "have to be removed for others to be upgraded" when upgrading...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA8-64-OK
Keywords: IN_RELEASENOTES8, advisory, validated_update
Depends on:
Blocks: 28393
  Show dependency treegraph
 
Reported: 2020-12-19 12:29 CET by PC LX
Modified: 2022-02-05 21:24 CET (History)
6 users (show)

See Also:
Source RPM: task-obsolete
CVE:
Status comment: move of task-obsolete forgotten


Attachments

Description PC LX 2020-12-19 12:29:30 CET
Description of problem:

When upgrading an up-to-date Mageia 7 system to Mageia 8/cauldron the following message is shown:

"""
The following packages have to be removed for others to be upgraded:
java3d-1.5.2-15.mga7.x86_64
 (due to missing libjawt.so(SUNWprivate_1.1)(64bit))
"""

System: Mageia 7, x86_64, Intel CPU, nVidia GPU using nvidia-current proprietary driver.

The Mageia 8 repositories contain mga7 packages. Don't know if that is relevant for this issue.

$ urpmf -f -m --name  java3d-
Core Release:java3d-javadoc-1.5.2-15.mga7.x86_64
Core Release:java3d-1.5.2-15.mga7.x86_64
Core Release:java3d-examples-1.5.2-15.mga7.x86_64
Core 32bit Release:java3d-1.5.2-15.mga7.i586
Core 32bit Release:java3d-javadoc-1.5.2-15.mga7.i586
Core 32bit Release:java3d-examples-1.5.2-15.mga7.i586



Version-Release number of selected component (if applicable):

java3d-1.5.2-15.mga7.src.rpm



How reproducible:

Always.



Steps to Reproduce:
1. Start with a fully up-to-date Mageia 7 system with the package wireshark-libvirt installed.
2. Remove all the Mageia 7 repositories (urpmi.removemedia -a).
3. Add the Mageia 8/cauldron repositories (urpmi.addmedia --distrib "http://ftp.free.fr/mirrors/mageia.org/distrib/cauldron/x86_64/").
4. Do an update (urpmi --split-length 0 --auto-update).
5. See the error message indicated above.
Aurelien Oudelet 2020-12-19 16:52:36 CET

Assignee: bugsquad => java
CC: (none) => ouaurelien

Comment 1 Aurelien Oudelet 2020-12-19 16:52:58 CET
Assigning this one to Java devs.
David Walser 2020-12-19 16:57:48 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=27524

David Walser 2020-12-19 16:58:07 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=16280

Comment 2 Nicolas Lécureuil 2020-12-19 20:58:49 CET
this is because we have not yet fixed jogl2, java3d, etc build against java11

CC: (none) => mageia

Comment 3 Aurelien Oudelet 2021-02-27 20:29:46 CET
Status?

Blocks: (none) => 28393

Morgan Leijström 2021-02-27 20:52:04 CET

CC: (none) => fri

Morgan Leijström 2021-03-05 17:24:37 CET

Priority: Normal => High

Comment 4 Morgan Leijström 2021-03-11 22:58:30 CET
From QA Meeting today:
20:28:44 <DavidWHodgins> The java3d packages should be dropped from mga8 if they can not be fixed soon.
20:29:14 <neoclust> it has been removed from mageia 8 already
20:29:21 <DavidWHodgins> Ah. Ok. Good.
20:29:23 <neoclust> the problem is when it is installed from mga7
20:29:36 <neoclust> it tells "hey man, where is my java3d?"
20:29:38 <neoclust> :)
20:29:49 <DavidWHodgins> The error message is correct, not a bug in my opinion
20:30:26 <DavidWHodgins> It should be listed in the errata if it isn't already, but otherwise is not a bug
20:30:27 <neoclust> not a bug but not good neither :-)
20:30:44 <neoclust> DavidWHodgins: yes in the ERRATA is good
20:30:58 <DavidWHodgins> Might be a good idea to suggest it's removal in the preparations too
20:31:14 <DavidWHodgins> To avoid having the upgrade interrupted
20:31:51 <neoclust> DavidWHodgins: should be added in task-obsolete ?
20:32:12 <DavidWHodgins> That would work too
20:32:44 <neoclust> ok i add on my todo :-)
20:32:44 <DavidWHodgins> Probably a better idea since it can not work on mga8
20:32:47 <neoclust> first the conflicts
20:33:35 <neoclust> yes and we will reintroduce it "IF" it gets fixed to work with java11 or we build it with java 1.8.0 as we still have it mageia 8
20:33:39 <neoclust> i will try to see what is best

I added it to the existing list of removed packages with removal on upgrade, at end of Release Notes, with link to this bug.
That section is already linked from Errata.

Keywords: (none) => IN_RELEASENOTES8

Comment 5 Nicolas Lécureuil 2021-03-12 20:56:46 CET
Please try with new task-obsolete ( i pushed it right now )
Comment 6 Nicolas Lécureuil 2021-03-12 20:57:12 CET
Please try with new task-obsolete ( i pushed it r

Assignee: java => qa-bugs

Aurelien Oudelet 2021-03-14 16:36:27 CET

Version: Cauldron => 8

Comment 7 Aurelien Oudelet 2021-03-19 10:30:45 CET
Status of this bug @PC LX?

Status: NEW => NEEDINFO

Comment 8 PC LX 2021-03-19 12:23:26 CET
Tested upgrading from Mageia 7 to Mageia 8 and this issue is resolved.
Will mark this bug appropriately.

Whiteboard: (none) => MGA8-64-OK
Resolution: (none) => FIXED
Status: NEEDINFO => RESOLVED

Comment 9 Morgan Leijström 2022-01-27 15:54:00 CET
Prematurely marked fixed:

task-obsolete-8-295.mga8.noarch.rpm did not get moved to updates!

Still in updates_testing for both i586 and x86_64

Version 294 is in release media.


BUT we can as well do next change to it now:
It should not obsolete PlayOnLinux  (does it?)
https://bugs.mageia.org/show_bug.cgi?id=28717#c38

Status: RESOLVED => REOPENED
CC: ouaurelien => davidwhodgins, lewyssmith
Resolution: FIXED => (none)

Morgan Leijström 2022-01-27 17:37:29 CET

Status comment: (none) => 1) move forgotten. 2) do not obsolete PlayOnLinux
Severity: major => normal
Priority: High => Normal

Comment 10 Thomas Andrews 2022-01-28 17:38:19 CET
Removing the OK until Comment 9 is addressed.

CC: (none) => andrewsfarm
Whiteboard: MGA8-64-OK => (none)

Comment 11 Dave Hodgins 2022-01-28 17:53:46 CET
It should be ok. The task-obsolete package has
Obsoletes: playonlinux < 4.3.4-4
https://svnweb.mageia.org/packages/updates/8/task-obsolete/current/SPECS/task-obsolete.spec?revision=1701859&view=markup

The new playonlinux update is playonlinux-4.4-1.1.mga8
Comment 12 Morgan Leijström 2022-01-28 18:40:58 CET
Great then.

So should we hand this over to sysadmins in order to move task-obsolete-8-295 ?


---


Thank you for showing how to check :)

I see there are a lot more we could add to
https://wiki.mageia.org/en/Mageia_8_Release_Notes#With_removal_on_upgrade

- Of course not all!

But some typical home user things like childsplay, sweethome3d, ... ?
Comment 13 Morgan Leijström 2022-02-01 02:32:55 CET
Hi!

Please move task-obsolete-8-295.mga8.noarch.rpm from testing to updates, all arch.

It was forgotten due to prematurely marking the bug fixed.

CC: (none) => sysadmin-bugs
Status comment: 1) move forgotten. 2) do not obsolete PlayOnLinux => move of task-obsolete forgotten
Whiteboard: (none) => MGA8-64-OK
Assignee: qa-bugs => sysadmin-bugs
Source RPM: java3d-1.5.2-15.mga7.src.rpm => (none)
Keywords: (none) => validated_update

Comment 14 Morgan Leijström 2022-02-05 17:19:23 CET
What is missing to get this moved?
Comment 15 Dave Hodgins 2022-02-05 19:15:23 CET
For java3d to be moved the bug has to be re-assigned back to qa, and an
advisory included indicating what has actually been changed in the package.
Comment 16 Morgan Leijström 2022-02-05 19:56:05 CET
There is no java3d to move, but the updated task-obsolete to obsolete it.

Seed for advisory:
Java3d is not in Mageia 8, and must be removed on upgrade from Mageia 7.


Its removal is already described in Mageia 8 Errata since Mars 2021.

Source RPM: (none) => task-obsolete
Assignee: sysadmin-bugs => qa-bugs

Comment 17 Dave Hodgins 2022-02-05 20:18:27 CET
Advisory added to svn as ...
$ cat 27875.adv 
type: bugfix
subject: Updated task-obsolete packages drop java3d
src:
  8:
   core:
     - task-obsolete-8-295.mga8
description: |
  Add java3d to list of obsolete packages to facilitate Mageia 7 to 8 upgrades.
references:
 - https://bugs.mageia.org/show_bug.cgi?id=27875

Keywords: (none) => advisory

Comment 18 Mageia Robot 2022-02-05 21:24:08 CET
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2022-0021.html

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.