Bug 1008028 - Updates repository isn't used during the installation when custom repository is set
Summary: Updates repository isn't used during the installation when custom repository ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vratislav Podzimek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-13 20:10 UTC by Petr Schindler
Modified: 2015-06-30 01:33 UTC (History)
8 users (show)

Fixed In Version: anaconda-20.20-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 01:33:01 UTC
Type: Bug


Attachments (Terms of Use)
Window with dependency error (113.60 KB, image/png)
2013-09-13 20:10 UTC, Petr Schindler
no flags Details
anaconda.log (14.41 KB, text/x-log)
2013-09-13 20:13 UTC, Petr Schindler
no flags Details
packaging.log (1.43 MB, text/x-log)
2013-09-13 20:13 UTC, Petr Schindler
no flags Details
program.log (35.19 KB, text/x-log)
2013-09-13 20:14 UTC, Petr Schindler
no flags Details
storage.log (129.53 KB, text/x-log)
2013-09-13 20:14 UTC, Petr Schindler
no flags Details

Description Petr Schindler 2013-09-13 20:10:52 UTC
Created attachment 797520 [details]
Window with dependency error

Description of problem:
Well, this bug is quite complicated so I'll start with reproducer (which sadly needs repository with broken dependency and this dep problem has to be fixed by update):

* Boot from netinst
* In anaconda go to installation source, choose http and fill in some repository (for example download.fp.org)
* Go to Software selection and choose something with broken dependency, click on done
* It shows that there are broken dependencies
* Go to Installation source and uncheck 'I don't want updates'
* Go to Software selection and again choose the same option and click 'done'
* Now everything is all right (so updates are probably used? From where? Not sure)
* Set everything else (partitioning at least)
* Begin installation
....
* Profit - you have a window with error message about dependencies (see the attachment)


I tried to do the same thing but with software selection without dependency problems (I turned on updates) and there weren't installed updates on the installed system. And I'm quite sure they should be ('don't install updates' option was unchecked).


Version-Release number of selected component (if applicable):
anaconda-20.15-1.fc20

How reproducible:
Only when dependencies are broken in the repository and they are fixed with update

Actual results:
Installation fails due to problem with dependencies

Expected results:
Updates are installed or shouldn't be used during dependency check

Additional info:
I don't thing that it will be problem with dependencies in repository. But usage of updates is really strange now.

Comment 1 Petr Schindler 2013-09-13 20:13:18 UTC
Created attachment 797521 [details]
anaconda.log

Comment 2 Petr Schindler 2013-09-13 20:13:46 UTC
Created attachment 797522 [details]
packaging.log

Comment 3 Petr Schindler 2013-09-13 20:14:13 UTC
Created attachment 797523 [details]
program.log

Comment 4 Petr Schindler 2013-09-13 20:14:39 UTC
Created attachment 797524 [details]
storage.log

Comment 5 Petr Schindler 2013-09-13 20:16:16 UTC
I forgot to mention that the error shows up after changes on disk are made. So user loses data and doesn't get new installation.

Comment 6 Chris Lumens 2013-09-13 20:43:31 UTC
This is probably what's resulting in your updates repos being tossed out:

19:35:21,909 ERR packaging: repo updates has no baseurl or mirrorlist
19:35:21,910 ERR packaging: repo updates-testing has no baseurl or mirrorlist

Though, I do not know where that would be happening offhand.

Comment 7 Brian Lane 2013-09-13 22:08:20 UTC
I think the real problem here is that we shouldn't be allowing the updates checkbox when not using mirrors. There is no way to figure out a matching updates/updates-testing repo for a custom url.

The ERR is a side-effect because something (I'm not sure if it is yum or anaconda) set the baseurl to [] and mirrorlist to None on those repos.

Comment 8 Fedora Update System 2013-09-25 16:04:05 UTC
anaconda-20.20-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.20-1.fc20

Comment 9 Fedora Update System 2013-09-27 00:32:14 UTC
Package anaconda-20.20-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-20.20-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-17681/anaconda-20.20-1.fc20
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2013-09-28 01:17:05 UTC
anaconda-20.21-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.21-1.fc20

Comment 11 Fedora End Of Life 2015-05-29 09:23:57 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 12 Fedora End Of Life 2015-06-30 01:33:01 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.