Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1093 - Povray out of date

Attached to Project: Arch Linux
Opened by Ben Mazer (contrasutra) - Friday, 09 July 2004, 16:51 GMT
Last edited by Dale Blount (dale) - Friday, 09 July 2004, 23:06 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

A new version of Povray has been out for a month. It's a major update and needs packaging.

Thanks,
Ben
This task depends upon

Closed by  Tobias Kieslich (tobias)
Wednesday, 21 July 2004, 20:17 GMT
Reason for closing:  Fixed
Comment by Tobias Kieslich (tobias) - Friday, 09 July 2004, 23:40 GMT
Well, problem is that for month tey display on their webpage, that:
"this is the version 3.5 source code. The version 3.6 source code
will be made available within a few weeks."
Unfortunately the didn't say how many week that exactly does mean.
Building a package form the binaries i not an option, cause the pathes
are all hardcoded to /usr/local. Any approach to relocate it to some
better location will fail as the 3.5 expeirience/pain showed. So this
will have to wait another "few weeks" until they relase the sources
finally. Please add a comment here or mail me directly if I miss the
glory day of release. :)
I will leave it flagged since if I unflag it, it will be flagged tomorrow again :-/
Comment by Ben Mazer (contrasutra) - Saturday, 10 July 2004, 00:16 GMT
I'm sorry, I didn't realize the source wasn't available. You're safe this time Toby. :)
Comment by Tobias Kieslich (tobias) - Tuesday, 20 July 2004, 13:34 GMT
The glory day came and so it's packaged. Although due to that funky crappy
version numbering the update needs to be done manually.
Comment by Aaron Stechesen (sarah31) - Wednesday, 21 July 2004, 19:52 GMT
so close the bug then dammit >:(
Comment by Tobias Kieslich (tobias) - Wednesday, 21 July 2004, 20:17 GMT
Well I was considering to force the update with a 3.6-2 package, but on the other hand, pacman lists perfectly what needs to be done to get the new version.
You win :-)

Loading...