Bug 624246 - purple-sipe package wrong group
Summary: purple-sipe package wrong group
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin-sipe
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Konstantin Ryabitsev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-15 07:11 UTC by raffamaiden
Modified: 2013-01-10 06:09 UTC (History)
2 users (show)

Fixed In Version: pidgin-sipe-1.11.2-1.fc14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-26 01:13:05 UTC
Type: ---


Attachments (Terms of Use)

Description raffamaiden 2010-08-15 07:11:00 UTC
I think that in the purple-sipe package the group field is wrong: Synaptic report it under %{pkg-group} and this is the only package under this group

Comment 1 Fedora Update System 2010-10-07 17:45:40 UTC
pidgin-sipe-1.11.0-1.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/pidgin-sipe-1.11.0-1.fc13

Comment 2 Fedora Update System 2010-10-07 17:46:35 UTC
pidgin-sipe-1.11.0-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/pidgin-sipe-1.11.0-1.fc14

Comment 3 Fedora Update System 2010-10-07 19:54:05 UTC
pidgin-sipe-1.11.0-1.fc14 has been pushed to the Fedora 14 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 pidgin-sipe'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/pidgin-sipe-1.11.0-1.fc14

Comment 4 Fedora Update System 2010-11-26 01:13:01 UTC
pidgin-sipe-1.11.2-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2010-11-26 01:13:13 UTC
pidgin-sipe-1.11.2-1.fc14 has been pushed to the Fedora 14 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.