Bug 20892

Summary:	why ds9 have been move to obsolete?
Product:	Mageia	Reporter:	Chris Denice <eatdirt>
Component:	RPM Packages	Assignee:	Nicolas Lécureuil <mageia>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	ds9	CVE:
Status comment:

Description Chris Denice 2017-05-19 23:39:40 CEST

I don't find ds9 anymore and I am maintaining it, it works and part of task-astronomy that I am maintaining.

It has been moved to obsolete, could we have some explanation?

Cheers.

Comment 1 Rémi Verschelde 2017-05-19 23:57:25 CEST

It seems it was obsoleted by neoclust: http://svnweb.mageia.org/packages?view=revision&revision=1103076

I guess it got caught by mistake in neoclust's work on fixing 300 broken packages after the java stack upgrade: http://pkgsubmit.mageia.org/autobuild/results.php?run=2017-05-17

Assignee: bugsquad => mageia

Comment 2 Chris Denice 2017-05-19 23:59:56 CEST

Indeed, that's most likely a mistake. I moved it back to cauldron, but I don't remember if I have to do something to restore the changelog!? (cannot find anything on the wiki for this), help appreciated :)

Comment 3 Rémi Verschelde 2017-05-20 00:03:03 CEST

The changelog would still be generated from the SVN current branch, so it should be fine: http://svnweb.mageia.org/packages/cauldron/ds9/current/SPECS/ds9.spec?view=log

(you may want to propedit the line about removing the package to make it SILENT though)

The old import log is also still available: http://svnweb.mageia.org/packages/misc/ds9/log?view=log

Comment 4 Chris Denice 2017-05-20 00:10:15 CEST

Ok, thanks. Indeed it did not compile in autobuild, I'll have a look!

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

Comment 5 Chris Denice 2017-05-20 15:02:13 CEST

Weird, it did pass on the BS without any fixing, maybe autobuild is not 100% reliable?