Bug 189405 - rpmbuild --rebuild evolution-2.2.3-4.fc4.src.rpm fails
Summary: rpmbuild --rebuild evolution-2.2.3-4.fc4.src.rpm fails
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-19 19:17 UTC by G. Roderick Singleton
Modified: 2018-04-11 19:00 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-10-02 17:36:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description G. Roderick Singleton 2006-04-19 19:17:34 UTC 
evolution-2.2.3-4.fc4.src.rpm fails to rebuild with the following error under FC4
2.6.16-1.2069_FC4 i386 with fhe following messages:

address-conduit.c:841: warning: passing argument 4 of 'dlp_ReadRecordById' from
incompatible pointer type
address-conduit.c:841: error: too many arguments to function 'dlp_ReadRecordById'
address-conduit.c:844: warning: passing argument 2 of 'unpack_Address' from
incompatible pointer type
Comment 1 Christian Iseli 2007-01-22 10:44:13 UTC 
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.
Comment 2 Matěj Cepl 2007-08-31 15:20:32 UTC 
The distribution against which this bug was reported is no longer supported,
could you please reproduce this with the updated version of the currently
supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue
turns out to still be reproducible, please let us know in this bug report.  If
after a month's time we have not heard back from you, we will have to close this
bug as INSUFFICIENT_DATA.

Setting status to NEEDINFO, and awaiting information from the reporter.

Thanks in advance.
Comment 3 Matthew Barnes 2007-10-02 17:36:17 UTC 
Closing as INSUFFICIENT_DATA.
Note You need to log in before you can comment on or make changes to this bug.