Bug 128093 - finger-0.17-24 (from FEDORA-2004-181) isn't pushed to development repository
Summary: finger-0.17-24 (from FEDORA-2004-181) isn't pushed to development repository
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: finger
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC3Target
TreeView+ depends on / blocked
 
Reported: 2004-07-17 16:40 UTC by Robert Scheck
Modified: 2015-03-05 01:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-01 17:56:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robert Scheck 2004-07-17 16:40:43 UTC
Description of problem:
finger-0.17-24 (from FEDORA-2004-181) isn't pushed to development 
repository, I only can find finger-0.17-22 there.

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

Actual results:
Well, I think -24 also should be pushed to the development tree, 
because from the changelog of -22:

Finger mishandled stale utmp entries and also entries from remote X 
sessions. This would cause random idle times and spurious users to 
be shown.

Expected results:
-24 or newer in development repository.

Comment 1 Phil Knirsch 2004-07-28 11:52:50 UTC
Update of development was stuck for a couple of days, should all be
set now again. Package should appear in the next few days.

Read ya, Phil

Comment 2 Robert Scheck 2004-08-06 16:29:28 UTC
The package didn't appear the last 10 days after your message 
(including today's update). Maybe something is broken anyway? Could 
you have a look to it, please?

Comment 3 Robert Scheck 2004-08-17 22:53:46 UTC
More than 10 days later, -24 or newer isn't anyway at Rawhide...

Comment 4 Elliot Lee 2004-09-01 17:50:15 UTC
Phil needs to build a new finger for FC3 - release 24 was made
available as an FC2 update only.

Comment 5 Elliot Lee 2004-09-01 17:56:39 UTC
Bah, I've just gone ahead and built it like I should have originally.


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