It is already in cauldron, assigning to maintainer

CC: (none) => marja11
Assignee: bugsquad => oliver.bgr
Summary: Package Request: PUAE Amiga emulator for MGA1 - present in Mandriva 2010.2 => p-uae, PUAE Amiga emulator for MGA1 - present in Mandriva 2010.2
Source RPM: (none) => p-uae
Whiteboard: (none) => Mdv, cauldron
Severity: normal => enhancement

Oliver :)

Thanks Marja.

Will do, but it is a bit buggy.

Status: NEW => ASSIGNED

It's crashing here very often, MrsB, could you test the cauldron package?

Thanks Oliver, I will do when I get the beta installed. 

I compiled it locally from the git and had sound issues with it so I'm not sure it is all that stable but it's still worth adding, there are no alternatives to this at the moment still being maintained.

I just managed to test this Oliver, it seems to be missing kick.rom. It needs kick.rom to be able to start. I think that is why it is crashing.

I'll test on the one I got mostly working and see if it gives the same message.

If not then its maybe just imported from a time when it wasn't working.

This version appears to be quite old Oliver, it dates back to March 22nd 2011 and there was another comit 3 days afterwards.


It's actually on 2.3.3 now.

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

closing as it's available in mga2 onwards

Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD

I imported fs-uae into cauldron, which is actually working (which p-uae is not).

So I had fs-uae obsoleting p-uae.

Since the version of p-uae we are providing doesn't work, I'd say we should backport fs-uae into 3 (and perhaps 2 as well) as a replacement for the not working p-uae.

Do we have a policy for that? Can we add fs-uae to the updates repositories or do we use backports?

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

Strictly speaking, I think, the policy would make importing fs-uae a backport unless there is no way to fix p-uae. A backport shouldn't obsolete an existing package though.

p-uae in mga3 is quite old by the looks of it (2.3.3) it is still maintained upstream though. Currently 2.6.0 beta 19. (We thought we had alot of betas!)

Our current version segfaults when started. Would an update not fix it ?

Failing that an exception would need to be discussed on dev ML.

Setting version to Mageia 3.

CC: (none) => stormi
Version: 1 => 3
Whiteboard: Mdv, cauldron => Mdv, cauldron, MGA2TOO

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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