Bug 561160 - installing package gzip-1.3.12-14.fc12.x86_64 needs 4MB on the /boot filesystem
Summary: installing package gzip-1.3.12-14.fc12.x86_64 needs 4MB on the /boot filesystem
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 12
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Panu Matilainen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-02 21:33 UTC by Matt Castelein
Modified: 2014-01-21 23:13 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-03 23:25:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matt Castelein 2010-02-02 21:33:09 UTC
Error message produced by yum:

installing package gzip-1.3.12-14.fc12.x86_64 needs 4MB on the /boot filesystem

What is gzip doing messing with the /boot filesystem?  Should it not be confined to /bin, /usr/bin, and /usr/share?

Comment 1 Karel Klíč 2010-02-02 21:55:47 UTC
May be that the gzip update is not the source of the problem. 
Is it possible, that you also updated kernel, which needs some space on /boot, and yum incorrectly complained about gzip?

Please try to update gzip separately from all other updates. Does it still produce the error message?

Comment 2 Matt Castelein 2010-02-03 15:11:37 UTC
(In reply to comment #1)
> Is it possible, that you also updated kernel, which needs some space on /boot,
> and yum incorrectly complained about gzip?

Yes, this is the case.

Comment 3 seth vidal 2010-02-03 15:26:03 UTC
yum doesn't do the disk space check. rpm does.

Comment 4 Panu Matilainen 2010-02-04 06:53:04 UTC
Hmm, this was supposed to be already fixed (bug 517418), guess I need to check again...

Comment 5 Panu Matilainen 2010-02-04 08:29:52 UTC
Reproduced, the fix to bug 517418 doesn't correctly deal with removed packages in the transaction.

Comment 6 Panu Matilainen 2010-02-04 14:00:59 UTC
Fixed upstream now, keeping this open for Fedora status tracking.

Comment 7 Panu Matilainen 2010-02-06 10:37:09 UTC
Also in rawhide now. The issue is mostly cosmetical: when there are real disk space issues with some package, these can "leak" to one unaffected package if erasures are present in the transaction.

Comment 8 Bug Zapper 2010-11-03 23:13:53 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Bug Zapper 2010-12-03 23:25:25 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.