After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 672420 - express,fedora: Install latest packages from repo
express,fedora: Install latest packages from repo
Status: RESOLVED FIXED
Product: gnome-boxes
Classification: Applications
Component: installer
3.5.x (unsupported)
Other All
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-03-20 01:26 UTC by Zeeshan Ali
Modified: 2016-03-31 13:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
express,fedora: Install latest packages from repo (1.21 KB, patch)
2012-03-20 01:26 UTC, Zeeshan Ali
reviewed Details | Review
express,fedora: Install from remote repo for <= F16 (3.92 KB, patch)
2012-03-20 21:51 UTC, Zeeshan Ali
committed Details | Review

Comment 1 Zeeshan Ali 2012-03-20 01:26:12 UTC
Created attachment 210133 [details] [review]
express,fedora: Install latest packages from repo

Not sure if this is a good thing in general but this is the quickest
solution to this bug I could come-up with:

https://bugzilla.redhat.com/show_bug.cgi?id=804834

The main issue with this change is that it makes Fedora express
installation to require Internet access.
Comment 2 Marc-Andre Lureau 2012-03-20 02:07:58 UTC
Review of attachment 210133 [details] [review]:

2 remarks:
- we should only require internet connection during install to workaround f16 or broken guests, not f17
- if possible, it would make sense to selectively update what is needed for boxes to work properly (qxl driver in this case, perhaps agent too etc..)
Comment 3 Zeeshan Ali 2012-03-20 18:07:39 UTC
(In reply to comment #2)
> Review of attachment 210133 [details] [review]:
> 
> 2 remarks:
> - we should only require internet connection during install to workaround f16
> or broken guests, not f17

Agreed.

> - if possible, it would make sense to selectively update what is needed for
> boxes to work properly (qxl driver in this case, perhaps agent too etc..)

I wanted to do that but I dont see any straight-forward way to do that :(

http://fedoraproject.org/wiki/Anaconda/Kickstart#repo

We better just use remote repos for <= F16 and install vdagent as well as its going to be available in F17 (and beyond) install medias:

https://bugzilla.redhat.com/show_bug.cgi?id=804739
Comment 4 Zeeshan Ali 2012-03-20 21:51:27 UTC
Created attachment 210203 [details] [review]
express,fedora: Install from remote repo for <= F16

Not sure if this is a good thing in general but this is the quickest
solution to this bug I could come-up with:

https://bugzilla.redhat.com/show_bug.cgi?id=804834

One issue with this change is that it makes Fedora 16 (and older) express
installation to require Internet access. On the bright side, we can now
have spice-vdagent package installed automatically from the start.
Comment 5 Marc-Andre Lureau 2012-03-20 22:31:40 UTC
Review of attachment 210203 [details] [review]:

looks good,
Comment 6 Zeeshan Ali 2012-03-21 00:06:25 UTC
Comment on attachment 210203 [details] [review]
express,fedora: Install from remote repo for <= F16

Committed as d621682 (to 3.5.x branch because of code freeze).
Comment 7 Christophe Fergeau 2012-03-22 07:48:58 UTC
You forgot to fix
+            // FIXME: Mark for translation after string freeze
+            var message = "Internet access required for express installation of Fedora 16 and older";
This should be ok to do since it's in a separate branch that won't be merged before 3.4.0
Comment 8 Zeeshan Ali 2012-03-22 12:29:52 UTC
(In reply to comment #7)
> You forgot to fix
> +            // FIXME: Mark for translation after string freeze
> +            var message = "Internet access required for express installation
> of Fedora 16 and older";
> This should be ok to do since it's in a separate branch that won't be merged
> before 3.4.0

Not entirely true. I will be cherry-picking all essential fixes to master once hard code freeze is over. So far, it seems like I will be cherr-picking everything from this branch..
Comment 9 Christophe Fergeau 2012-03-23 08:31:56 UTC
If master is what you will use for 3.4.x releases, the string should be marked for translation and a string freeze break requested. The string freeze is still in effect after 3.4.0 is released, and adding a new user-visible string is a string freeze break even if you don't mark it for translation for now. The goal of the string freeze is to help translators get an application where all user-visible strings are translated.
Comment 10 Christophe Fergeau 2012-03-23 08:32:37 UTC
(In reply to comment #9)
> If master is what you will use for 3.4.x releases, the string should be marked
> for translation and a string freeze break requested

That is, when/if you merge this patch to master and want to make a 3.4.x release with this in.