Fedora 19 Final blocker status: fix and karma requests
jreznik at redhat.com
Mon Jun 24 11:22:45 UTC 2013
----- Original Message -----
> On Sat, 2013-06-22 at 22:17 -0700, Adam Williamson wrote:
> > On Sat, 2013-06-22 at 11:00 -0400, Matthias Clasen wrote:
> > > On Fri, 2013-06-21 at 14:14 -0700, Adam Williamson wrote:
> > >
> > > >
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=958426 - "19 Final TC1
> > > > x86_64 Desktop Live is oversized (larger than 1 GB)" - desktop team (I
> > > > know you're working on it)
> > >
> > > I've filed an update with some 20 packages, only removing excess baggage
> > > from /usr/share/doc (duplicate docs, large ChangeLog files, etc). It
> > > touches nothing outside /usr/share/doc, so should be fairly safe to let
> > > in. That will probably only get us part of the way, so I've also cut
> > > some more things from the package set in the .ks file (gnome-system-log,
> > > deja-dup).
> > >
> > > If that is not enough, next step will probably be removing some of the
> > > big font packages.
> > So Matthias forgot to link to his update, but here it is:
> > https://admin.fedoraproject.org/updates/FEDORA-2013-11471/PackageKit-0.8.9-6.fc19,gtk2-2.24.19-2.fc19,evolution-3.8.3-2.fc19,gedit-3.8.2-2.fc19,gnome-session-126.96.36.199-2.fc19,gdm-3.8.3-2.fc19,eog-3.8.2-2.fc19,telepathy-mission-control-5.14.1-2.fc19,yelp-3.8.1-5.fc19,libchamplain-0.12.4-2.fc19,dbus-glib-0.100-4.fc19,libisofs-1.2.8-2.fc19,libxslt-1.1.28-3.fc19,gnome-contacts-3.8.2-2.fc19,gtkmm24-2.24.2-6.fc19,glibmm24-2.36.2-2.fc19,folks-0.9.2-3.fc19,harfbuzz-0.9.18-3.fc19,tracker-0.16.1-3.fc19,libmx-1.4.7-7.fc19
> > It contains changes to some packages not entirely GNOME-y in nature,
> > inc. dbus-glib and gtk2, so other people might want to give it the
> > once-over just to make sure there are no inadvertent errors, and upkarma
> > it assuming it's all good. I am about to test a live compose with the
> > update to see the impact on image size.
> So here's some results.
> f2e707287dd82cccb05a3fef6b75cb356744ca58 (Jun 14), no update: 1019215872
> f2e707287dd82cccb05a3fef6b75cb356744ca58 (Jun 14), update: 1017118720
> 1a0c28fdf638796bda60ed2785f95eac16a85b65 (Jun 22), update: 1005584384
> that is, with the old spin-kickstarts and without the above update,
> we're 19215872 bytes oversize; with the update but old spin-kickstarts,
> we're 17118720 bytes oversize (the update saves ~2.1MB); and with the
> update and latest spin-kickstarts, we're 5584384 bytes oversize (the
> kickstart changes save ~11.5MB). We still need to find another 5.6MB
> from somewhere.
Do we have to be byte strict here? For physical medium sizes, we had to
be, this 1 GB is more "we set it as we think it's a good idea". Or maybe
1 GB sticks (what's the real size one can use + overlay?) but it's not
as strict, as you could pick up bigger one.
> Thanks folks!
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> devel mailing list
> devel at lists.fedoraproject.org
More information about the devel