Bug 32872

It is unclear whether this bug is for Mageia 9 or Cauldron. Hans, please confirm which one.
If it is for Mageia 9, set 'Version' to that.
If it is for Cauldron, please add MGA9TOO to 'Whiteboard'.

BTAIM Both are at version 8.1 which was released about 11m ago. Curiously, v8.2 followed quickly just a month later.

Different packagers have dealt with this pkg, so assigning globally; CC'ing the two packagers who updated it most recently.

Assignee: bugsquad => pkg-bugs
CC: (none) => eatdirt, geiger.david68210

I only have Cauldron. I've put MGA9TOO on whiteboard.

Release note for 8.2:
    May 2023:
        Release of version 8.2 to fix issues with the databases.

Whiteboard: (none) => MGA9TOO

Thanks, I'll update Cauldron for sure, and mga9 is there is breakage triggered!

I've tested the new VirtualMoon in Cauldron. It installs and runs perfectly. I have updated via urpmi. I have uninstalled with urpme. Uninstalled libpasastro with urpme --auto-orphans, which is OK. Had to manually uninstall virtualmoon-data, which seems OK as it is 4,6 G. You might not want to accidentally uninstall that. It installs without problems with urpmi, including libpasastro and virtualmoon-data, which are dependencies.

OK from my side for Cauldron.

Cool, I'll also push an update for mga9, the big data files remain unchanged between both versions!

Here we go, virtualmoon-8.2 landing in core/updates_testing

This is a bug fix release over the version 8.1 currently shipped with mga9.

RPMS:
virtualmoon-8.2-1.mga9

SRPMS:
virtualmoon-8.2-1.mga9.src.rpm

QA Contact: (none) => qa-bugs

(In reply to Chris Denice from comment #6)
> Here we go, virtualmoon-8.2 landing in core/updates_testing
> 
> This is a bug fix release over the version 8.1 currently shipped with mga9.
> 
> RPMS:
> virtualmoon-8.2-1.mga9
> 
> SRPMS:
> virtualmoon-8.2-1.mga9.src.rpm

The package virtualmoon-data (currently 8.0-1.mga9) not need to be in sync with the version of the binary ?

(In reply to katnatek from comment #7)
> (In reply to Chris Denice from comment #6)
> > Here we go, virtualmoon-8.2 landing in core/updates_testing
> > 
> > This is a bug fix release over the version 8.1 currently shipped with mga9.
> > 
> > RPMS:
> > virtualmoon-8.2-1.mga9
> > 
> > SRPMS:
> > virtualmoon-8.2-1.mga9.src.rpm
> 
> The package virtualmoon-data (currently 8.0-1.mga9) not need to be in sync
> with the version of the binary ?

Forget it I search in upstream page and data version is still in 8.0

LC_ALL=C urpmi virtualmoon
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "QA Testing (64-bit)")
  virtualmoon                    8.2          1.mga9        x86_64  
(medium "Core Release")
  libpasastro                    1.4.1        2.mga9        x86_64  
  virtualmoon-data               8.0          1.mga9        noarch  (recommended)
5.6GB of additional disk space will be used.
4.7GB of packages will be retrieved.
Proceed with the installation of the 3 packages? (Y/n) 

The package require the needed libpasastro so not regression respect bug#32871

MGA9-64 Plasma on HP-Pavillion
No installation issues
Launcing at CLI:

$ atlun 
Init OpenGL
Check Acceleration
Check texture size
Texture max: 16384
Check Bumpmap
Driver: INTEL MESA INTEL(R) HD GRAPHICS 405 (BSW)
GL_ARB_texture_env_dot3 OK
GL_ARB_fragment_program OK
SetBumpMethod
Check MultiTexture
InitLabel
InitSprite
Init OpenGL OK
I can use the Find fucntion, zoom in and out
Seems to work OK

CC: (none) => herman.viaene
Whiteboard: (none) => MGA9-64-OK

Validating.

CC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => validated_update

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2024-0070.html

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