[Bug 203520] Review Request: evolution-brutus

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: evolution-brutus
Alias: evolution-brutus

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203520





------- Additional Comments From mtasaka at ioa.s.u-tokyo.ac.jp  2006-09-05 05:56 EST -------
I just checked if this package (-1.1.6-4) can be rebuilt,
however, it failed in mock.

+ ./configure --build=i686-redhat-linux-gnu --host=i686-redhat-linux-gnu
--target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-pr
efix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc
--datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/
usr/libexec --localstatedir=/var --sharedstatedir=/usr/com
--mandir=/usr/share/man --infodir=/usr/share/info --enable-brutus-dist=yes
--enable-br
utus-debug=no --enable-brutus-devel=yes --enable-brutus-spy=no
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
./configure: line 2122: evolution: command not found
checking Evolution Data Server version... 1.7
configure: error: Unsupported version of Evolution Data Server. Please report
this to <bugs at omesc.com>.
error: Bad exit status from /var/tmp/rpm-tmp.53931 (%build)
RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.53931 (%build)
Error building package from evolution-brutus-1.1.6-4.src.rpm, See build log

Check the BuildRequires. 
Also, as the comment #3 , if
this package cannot be rebuilt with evolution-data-server-1.7.92 ,
this package cannot be released because Fedora Extras packages has to
be rebuilt under devel environment first.

Also, you have to add %{?dist} to release.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.