Bug 449209 - claws-mail wrongly BR libgnomeprintui22-devel
Summary: claws-mail wrongly BR libgnomeprintui22-devel
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: claws-mail
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-31 11:20 UTC by Tuomo Soini
Modified: 2008-07-23 07:19 UTC (History)
0 users

Fixed In Version: 3.5.0-1.fc9
Clone Of:
Environment:
Last Closed: 2008-07-18 23:08:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tuomo Soini 2008-05-31 11:20:12 UTC
Description of problem:

wrong BR: libgnomeprintui22-devel

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

claws-mail-3.4.0-1

How reproducible:

Always.

Additional info:

When gtk2 is version 2.10+ claws-mail will not use gnomeprint. Bu changing gkt2
version requirement to gtk2 >= 2.10.0 libgnomeprintui22 which is currently
unused can be dropped as build requirement. This can be easily checked from
buildlog, claws-mail is currently not using gnomeprint.

Comment 1 Fedora Update System 2008-06-18 04:49:25 UTC
claws-mail-3.4.0-2.fc9 has been submitted as an update for Fedora 9

Comment 2 Fedora Update System 2008-06-18 04:52:11 UTC
claws-mail-3.4.0-2.fc8 has been submitted as an update for Fedora 8

Comment 3 Fedora Update System 2008-06-20 19:07:48 UTC
claws-mail-3.4.0-2.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update claws-mail'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-5483

Comment 4 Fedora Update System 2008-06-27 19:35:03 UTC
claws-mail-3.4.0-2.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2008-06-27 19:37:04 UTC
claws-mail-3.4.0-2.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Tuomo Soini 2008-06-27 19:53:16 UTC
Only part of this bug was fixed. Now libgnomeprintui22-devel BR is removed but
gtk2-devel version requirement is now wrong. If package is now tried to build on
system with older than 2.10.0 gtk2-devel build still requires
libgnomeprintui22-devel.

-BuildRequires: gtk2-devel >= 2.6.2
+BuildRequires: gtk2-devel >= 2.10.0


Comment 7 Jens Petersen 2008-06-30 02:37:20 UTC
Actually BR libgnomeprintui22-devel still seems to be there?

Comment 8 Tuomo Soini 2008-06-30 06:06:53 UTC
On rawhide, yes. it's removed on f8 and f9. That's why I didn't check changes
earlier because I only follow rawhide.

Rawhide doesn't have partly fixed version yet.

Comment 9 Fedora Update System 2008-07-06 20:40:39 UTC
claws-mail-3.5.0-1.fc8 has been submitted as an update for Fedora 8

Comment 10 Fedora Update System 2008-07-06 20:58:09 UTC
claws-mail-3.5.0-1.fc9 has been submitted as an update for Fedora 9

Comment 11 Fedora Update System 2008-07-09 02:53:30 UTC
claws-mail-plugins-3.5.0-1.fc9, claws-mail-3.5.0-1.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update claws-mail-plugins claws-mail'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-6246

Comment 12 Fedora Update System 2008-07-18 23:08:08 UTC
claws-mail-plugins-3.5.0-1.fc9, claws-mail-3.5.0-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2008-07-23 07:19:48 UTC
claws-mail-plugins-3.5.0-1.fc8, claws-mail-3.5.0-1.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.


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