Bug 220849 - Proj package is not up to date.
Summary: Proj package is not up to date.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: proj
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Shawn McCann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-27 22:47 UTC by Devrim GUNDUZ
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: FC-6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-01-12 15:00:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Devrim GUNDUZ 2006-12-27 22:47:19 UTC
Description of problem:

Proj package is not up to date.

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

4.4.9
  
Actual results:

The Geos in FC 6 and 7 is 4.4.9.

Expected results:

The upstream version is 4.5.0.

Additional info:

I can take the co-ownership of this package if you want.

Comment 1 Devrim GUNDUZ 2007-01-02 23:34:15 UTC
This is my 2nd attempt to contact Shawn McCann.

Comment 2 Toshio Kuratomi 2007-01-03 17:56:04 UTC
Hi Devirm, If you're starting the orphaned packages policy, it's a good idea to
post the URL and a description as well.  That way the maintainer knows that your
intention is to take over his package if he doesn't respond.

http://www.fedoraproject.org/wiki/Extras/Policy/AWOL_Maintainers

Comment 3 Devrim GUNDUZ 2007-01-03 18:42:13 UTC
Thanks Toshio. I also added this info to #220848 .

Regards, Devrim

Comment 4 Shawn McCann 2007-01-04 04:36:57 UTC
Just returned from Xmas vacation and am catching up on emails. I will have a
look at the deltas between 4.5.0 and 4.4.9. If there are no major changes in the
new release then I should be able to submit the new package shortly.

Comment 5 Shawn McCann 2007-01-04 05:55:56 UTC
I have uploaded the new spec file and tarballs for proj-4.5.0 and
proj-datumshift-1.3. The new rpms have been built in devel, FC-6 and FC-5. Let
me know if you see any problems.


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