Bug 473849 - thunderbird fails to update during an F8->F10 transition
thunderbird fails to update during an F8->F10 transition
Product: Fedora
Classification: Fedora
Component: thunderbird (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
Fedora Extras Quality Assurance
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2008-11-30 21:56 EST by Michal Jaegermann
Modified: 2018-04-11 10:25 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 02:03:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2008-11-30 21:56:28 EST
Description of problem:

An upgrade F8 to F10 leaves an "orphaned"  thunderbird-  Trying to repeat that in yum shows why:

  Updating       : thunderbird                                              1/2 
Error unpacking rpm package thunderbird-
error: unpacking of archive failed on file /usr/lib/thunderbird-
aries: cpio: rename

The problem is that /usr/lib/thunderbird- in a directory in an F8 package but a symlink in F10.  After removal of "dictionaries*" (that includes "lefovers" from failed attempts) updating actually works.

A package %pre script could include:

[ -d %{_libdir}/lib/thunderbird- ] && \
  rm -rf %{_libdir}/lib/thunderbird-

and that would do the above "automagically".

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

How reproducible:
Comment 1 Tim Niemueller 2008-12-01 12:09:04 EST
Had the same problem. Removal of the directory indeed fixes this problem.
Comment 2 Matěj Cepl 2008-12-01 18:49:48 EST
This looks like a duplicate of famous bug 433096, but I thought (and bug 433096 comment 20 would support it) that it shouldn't happen to normal users outside of Rawhide.
Comment 3 Michal Jaegermann 2008-12-01 19:04:20 EST
> This looks like a duplicate of famous bug 433096 ...

Hits in another place but yes - the issue is really the same. I already forgot about that other gotcha.

(Bugzilla "wondrously" scrambles longer lines, at least on my screen. Should all reports be really entered as attachments?  At least what is mailed out looks sane.)
Comment 4 Bug Zapper 2009-11-18 04:05:46 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 WONTFIX if it remains open with a Fedora 
'version' of '10'.

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 prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
Comment 5 Bug Zapper 2009-12-18 02:03:49 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.

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.