Bug 960719 - No upstream
Summary: No upstream
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rdate
Version: rawhide
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Honza Horak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 967517
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-07 18:41 UTC by Adam Williamson
Modified: 2013-06-12 03:31 UTC (History)
1 user (show)

Fixed In Version: openrdate-1.2-2.fc19
Clone Of:
Environment:
Last Closed: 2013-06-12 03:31:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2013-05-07 18:41:24 UTC
So, from the spec file, it looks like our 'rdate' implementation was written years ago by someone who no longer works for Red Hat, Elliot Lee.

The given URL for the app and for the source tarball no longer works - ftp://people.redhat.com/sopwith/ does not exist. As there is no functional upstream, we are carrying multiple patches in the Fedora package, even though 'we' (RH) wrote the damn thing in the first place!

This seems kinda silly. 'thrice' on IRC points out that there is an implementation called openrdate:

http://sourceforge.net/projects/openrdate/

which is a standalone packaging of the OpenBSD implementation. It's an active upstream that is currently maintained, and various other distros use it. If we really still need an rdate implementation, perhaps we should use that one?

Comment 1 Honza Horak 2013-05-27 10:40:06 UTC
Thanks for this tip. I've just sent a package review for openrdate:
bug #967517

Comment 2 Fedora Update System 2013-06-03 12:32:32 UTC
openrdate-1.2-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/openrdate-1.2-2.fc19

Comment 3 Fedora Update System 2013-06-05 02:35:18 UTC
openrdate-1.2-2.fc19 has been pushed to the Fedora 19 testing repository.

Comment 4 Fedora Update System 2013-06-12 03:31:48 UTC
openrdate-1.2-2.fc19 has been pushed to the Fedora 19 stable repository.


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