The pimlico suite of apps originally designed for phones but useful
standalone have been dead upstream for quite some time and with the
restructuring of evolution are often breaking. Upstream gnome now has
standalone Contacts and Calendar apps with a Tasks app planned and
there's others that also substitute such as GTG.
So unless anyone explicitly wants to maintain them I'll kill them off
in the next couple of days. If you're interested get in touch.
In Fedora 17, when you install grub2 and generate a fresh config file, that
config is produced by grub2-mkconfig. However, when you install a kernel
update, the kernel's entry is added to the grub2 boot menu by grubby.
This produces messy grub boot menus. The entries added by grubby read
something like "Fedora (%kernel_version)". grub2-mkconfig, on the other
hand, only displays one "Fedora Linux" boot option and places the other
kernels and their recovery mode environments in a submenu called "Advanced
Now, I never really liked seeing three kernels on the main menu to begin
with, and I think the new grub2 approach of hiding the other kernels in a
submenu is nice. But then as soon as I start installing updates the submenu
becomes incomplete (and eventually useless, as the new kernels won't be
listed there) and the grubby options take over the menu.
It seems to me that we should make the boot menu more consistent somehow. I
feel like the simplest solution is just to run grub2-mkconfig at every
kernel update, and stop using grubby for this. Then everything would look
consistent- the "Fedora Linux" boot option would have the latest kernel
and all kernels would always be listed under the submenu. (As far as I
know, this would just be a change to the kernel specfile, right?).
Alternatively, if Fedora does want boot menus that look like the ones
produced by grubby, then the grub2 default configuration should be changed
to reflect that, so the boot menu will always look consistent.
I should add that I did see a reference to possibly replacing grubby with a
"grub-updconf" (though I'm not aware of such a program) on the wiki-
http://fedoraproject.org/wiki/Features/Grub2 - so possibly there are
already plans for this?
Le Jeu 26 juillet 2012 09:32, Akira TAGOH a écrit :
> Well, I see what Nicolas wants to do here. since Japanese characters
> on Unicode's CJK Unified Ideographs is a subset of Chinese characters,
> I think he wanted to avoid picking Droid Sans Japanese up for Chinese
Ideally, I'd like the target="scan" lang-specific rules to generate a form
of simulated locl table. I know the current rules I use don't do that, but
I guess they are a sort of RFE on my part :)
I think Droid is a good showcase of the dead-end
selecting-lang-by-font-name is : if we don't hide the various
lang-specific droid names to the user, it only takes two or three
droid-like families to make font selection totally unusable in most apps.
Before we branch for Fedora 18, as is custom, we will block currently
orphaned packages and packages that have failed to build since Fedora 16.
The following packages are currently orphaned, or fail to build. If
you have a need for one of these packages, please pick them up.
If no one claims any of these packages, they will be blocked before
we branch for Fedora 18. That is currently scheduled to happen on
or around August 7th.
Note that if you're receiving this mail directly, it's because you are
a co-maintainer of one of these packages. Please work with your
comaintainers to take up maintenance.
Package archmage (orphan)
Package boolstuff (orphan)
Package cmucl (orphan)
comaintained by: green
Package drupal6-video (orphan)
Package eclipse-m2m-qvtoml (fails to build)
Package fillmore-lombard (fails to build)
comaintained by: salimma
Package gant (fails to build)
Package genus2reduction (orphan)
Package globalplatform (orphan)
Package gpshell (orphan)
Package gtkmm-utils (orphan)
Package gtkpod (orphan)
Package hamster-applet (orphan)
Package hartke-aurulent-sans-fonts (orphan)
Package healpix (fails to build)
Package json (orphan)
Package k12linux-quick-start-guide (orphan)
Package kadu (fails to build)
comaintained by: gajownik radekl
Package libcrystalhd (fails to build)
comaintained by: kwizart
Package libgtkhotkey (orphan)
Package libhid (fails to build)
Package libqttracker (fails to build)
comaintained by: jreznik
Package libsoup22 (orphan)
Package natus (fails to build)
Package ncpfs (orphan)
Package ntfs-config (fails to build)
Package nvi (orphan)
Package perl-Nagios-Plugin-Beanstalk (orphan)
Package pfqueue (orphan)
Package pino (fails to build)
Package polyester (orphan)
Package polyester3 (orphan)
Package python-batchhttp (orphan)
Package python-chm (orphan)
Package python-pywt (fails to build)
Package python-remoteobjects (orphan)
Package python-typepad (orphan)
Package qtparted (fails to build)
Package selenium-remote-control (fails to build)
Package torque (orphan)
Package typepad-motion (orphan)
Package upstart (orphan)
Package winwrangler (orphan)
List of deps left behind by packages which are orphaned or fail to build:
skyviewer requires chealpix-devel = 2.13a-2.fc14
skyviewer requires libchealpix.so
synapse requires libgtkhotkey.so.1
libopensync-plugin-syncml requires libsoup22-devel = 2.2.105-9.fc15
libsyncml requires libsoup-2.2.so.8
libsyncml requires libsoup22-devel = 2.2.105-9.fc15
hydra requires libncp.so.2.3
hydra requires ncpfs-devel = 2.2.6-17.fc18
hydra requires libncp.so.2.3(NCPFS.220.127.116.11)
hydra requires libncp.so.2.3(NCPFS_18.104.22.168)
hydra requires libncp.so.2.3(NCPFS_2.2.1)
medusa requires libncp.so.2.3
medusa requires ncpfs-devel = 2.2.6-17.fc18
medusa requires libncp.so.2.3(NCPFS.22.214.171.124)
medusa requires libncp.so.2.3(NCPFS_126.96.36.199)
medusa requires libncp.so.2.3(NCPFS_2.2.1)
django-typepad requires python-batchhttp = 1.1-5.fc18
chm2pdf requires python-chm = 0.8.4-12.fc18
django-typepad requires python-remoteobjects = 1.1-5.fc18
django-typepad requires python-typepad = 1.1.2-5.fc18
perl-Alien-SeleniumRC requires selenium-server = 1.0.3-8.20100318svn.fc15
pbstop requires torque-client = 3.0.4-1.fc17
pdsh requires torque-devel = 3.0.4-1.fc17
pdsh-mod-torque requires torque = 3.0.4-1.fc17
pdsh-mod-torque requires libtorque.so.2
perl-PBS requires libtorque.so.2
perl-PBS requires libtorque-devel = 3.0.4-1.fc17
python-pbs requires torque-devel = 3.0.4-1.fc17
python-pbs requires libtorque.so.2
python3-pbs requires libtorque.so.2
clamav-milter-upstart requires /sbin/initctl
clamav-scanner-upstart requires /sbin/initctl
dhcp-forwarder-upstart requires /sbin/initctl
ip-sentinel-upstart requires /sbin/initctl
milter-greylist-upstart requires /sbin/initctl
tor-upstart requires /sbin/initctl
The script that generated this page can be found at
There you can also report bugs and RFEs.
While an anaconda/systemd problem is being worked on (bug #841822),
now my next problem when making new F17 spins including all updates:
anaconda can't display PNG images anymore.
For all images it tries to open (and all these images do exist),
it gives an error like:
17:47:31,122 ERR anaconda: unable to read anaconda_header.png: Couldn't recognize the image file format for file '/usr/share/anaconda/pixmaps/anaconda_header.png'
Looking at the anaconda code, this error seems to be generated by
getPixbuf() in /usr/lib64/python2.7/site-packages/pyanaconda/gui.py,
when it does a gtk.gdk.pixbuf_new_from_file(fn).
Any suggestion on what could be causing this?
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
This morning, I woke up to the news that a group of developers have managed
to successfully make Ubuntu's Unity Desktop work on Fedora 17. What kind
of work would be needed to get these people to be able to bring their work
into the Fedora repository so that everyone can easily choose to use it
without breaking stuff?
Just an informational anecdote. My main dev machine is a vanilla
Lenovo X220 laptop, running an up-to-date F16. At OLPC, we are damned
close to *shipping* a F17-based distro on our XO laptops, so I thought
it'd be good to update.
Worried about /usr move, I decided to DTRT: use preupgrade.
First, preupgrade completely hides grubby errors, and tells you
everthing's peachy. This cannot be a feature. I managed to hit a few
grubby errors, and without the debug output from preupgrade-cli
showing the grubby command it's running, I'd still be scratching my
So grub configs were not being updated, for two reasons
- My machine does not have /boot/grub/grub.cfg, it has grub.conf
instead, so I hit BZ#841976 . Unsure why these conffiles are changing
names, this was a fresh F16 install back when F16 was new.
- Added the missing grub.cfg, grubby segfaults (BZ#841979). Ummpf!
- The preupgrade wikipage helpfully provides instructions to edit
grub.conf by hand. Completely wrong instructions. You don't want the
/boot prefix there. You don't want "savedefault". You probably want to
ensure you see the menu.
I am no expert on what params the preupgrade initrd _really_ needs,
but things did not move forward until I fixed it up and added the
params that preupgrade was giving to the failing grubby.
- And there I hit BZ#813973 - preupgrade (anaconda) garbles the URL
so you only get 404s.
The adventure continues, but at thistime I am under the impression
that preupgrade gets far less testing and polish than yum upgrades.
martin(a)laptop.org -- Software Architect - OLPC
- ask interesting questions
- don't get distracted with shiny stuff - working code first
There will be an outage starting at 2012-07-26 16:00 UTC, which will
last approximately 2 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:
date -d '2012-07-26 16:00 UTC'
Reason for outage:
In order to grow the fedora hosted services we are moving the services
email lists to a new server. This will require an outage of about an
hour as we turn off old services.. sync data.. turn on new services.
Fedora Hosted - https://fedorahosted.org/
Ask Fedora - http://ask.fedoraproject.org/
BFO - http://boot.fedoraproject.org/
Bodhi - https://admin.fedoraproject.org/updates/
Buildsystem - http://koji.fedoraproject.org/
GIT / Source Control
DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
Docs - http://docs.fedoraproject.org/
Fedora Account System - https://admin.fedoraproject.org/accounts/
Fedora Community - https://admin.fedoraproject.org/community/
Fedora Insight - https://insight.fedoraproject.org/
Fedora People - http://fedorapeople.org/
Main Website - http://fedoraproject.org/
Mirror List - https://mirrors.fedoraproject.org/
Mirror Manager - https://admin.fedoraproject.org/mirrormanager/
Package Database - https://admin.fedoraproject.org/pkgdb/
Smolt - http://smolts.org/
Spins - http://spins.fedoraproject.org/
Start - http://start.fedoraproject.org/
Torrent - http://torrent.fedoraproject.org/
Wiki - http://fedoraproject.org/wiki/
Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/3401
Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
comments to the ticket for this outage above.
Stephen J Smoogen.
"Don't derail a useful feature for the 99% because you're not in it."
"Years ago my mother used to say to me,... Elwood, you must be oh
so smart or oh so pleasant. Well, for years I was smart. I
recommend pleasant. You may quote me." —James Stewart as Elwood P. Dowd
Good day all,
This weeks Fedora ARM status meeting will take place today (Wednesday July 25th) in #fedora-meeting-1 on Freenode.
Times in various time zones (please let us know if these do not work):
Current items on the agenda:
1) F18 Mass rebuild status
2) Raspberry Pi Remix update
3) Your topic here
If you have any other items you would like to discuss that are not mentioned, please feel free to send an email to the list or bring it up at the end of the meeting.