Bug 998382 - Conflicts with libotr
Summary: Conflicts with libotr
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libotr3
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-19 08:09 UTC by Michael Schwendt
Modified: 2015-06-29 12:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 12:17:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michael Schwendt 2013-08-19 08:09:26 UTC
If it has been like that already during review, it should not have been approved. Note that typically we try to avoid conflicts also in -devel packages. 

=> libotr3-3.2.1-6.fc20.src.rpm
=> libotr3-devel-3.2.1-6.fc20.i686 in fedora-development-i386
  File conflict with: libotr-devel-4.0.0-1.fc20.i686
     /usr/include/libotr/auth.h
     /usr/include/libotr/b64.h
     /usr/include/libotr/context.h
     /usr/include/libotr/dh.h
     /usr/include/libotr/mem.h
     /usr/include/libotr/message.h
     /usr/include/libotr/privkey-t.h
     /usr/include/libotr/privkey.h
     /usr/include/libotr/proto.h
     /usr/include/libotr/serial.h
     /usr/include/libotr/sm.h
     /usr/include/libotr/tlv.h
     /usr/include/libotr/userstate.h
     /usr/include/libotr/version.h
     /usr/lib/pkgconfig/libotr.pc

Comment 1 Fedora End Of Life 2013-09-16 16:35:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 2 Mike McLean 2014-08-18 18:30:22 UTC
This appears to be fixed in the F19 version, but not the F20 version.

[mike@localhost ~]$ koji latest-build --quiet f19-updates libotr
libotr-4.0.0-3.fc19                       f19-updates           pwouters
[mike@localhost ~]$ koji latest-build --quiet f20-updates libotr
libotr-4.0.0-1.fc20                       f20                   ausil
[mike@localhost ~]$ 

f19: http://koji.fedoraproject.org/koji/buildinfo?buildID=504516
f20: http://koji.fedoraproject.org/koji/buildinfo?buildID=438331

otoh, the f21/f22 builds appear to have it (based on the changelog).

Comment 3 Fedora End Of Life 2015-05-29 09:20:03 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-29 12:17:31 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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