I downloaded the live cd of F10 beta. Booted and added the live_ram
option to the boot params. After copying the image to RAM I get the
following error on two machines, (Apple Mac Book, and Acer 3680).
Done copying live image to RAM.
eject: did not find a device /dev/root in /sys/block
Bug in initramfs /init detected. Dropping to a shell. Good luck!
sbin/real-init: line 7: plymouth: command not found
I know I used that param for F9. Is it depreciated or is this a bug
Nathanael d. Noblet
I'd like to update waf  to version 1.5.0 (which has been released
only recently, and changes apis) for rawhide, and also as an update
for f10. As far as I can see, only midori depends on it (although some
more packages probably should, like kdissert).
Thomas Moschny <thomas.moschny(a)gmail.com>
I am orphaning all my packages. I orphan the devel branch, but I'd
also orphan the stable branches too, so if you are interested don't
hesitate to ask. I am still willing to maintain the EPEL branches, but
here, also, if you want to take over, say so.
I am nco, ncview, glib 1 and gtk+ 1 de-facto main packager, so
somebody else should take care of those packages.
I think that lesstif, perl-File-MimeInfo and fcron are strategic for
Low maintainance but very complicated packages:
The cernlib packages are quite complicated and unusual, this is fortran,
uses imake :-/ and upstream is moribund since 2003, and dead since 2006.
Debian was like a substitution upstream, but the debian maintainer has
also abandonned cernlib. Still it is known that there are users for this
Very low maintainance packages:
Low maintainance packages:
there is an update available for grads, but it has some functionalities
removed, and also upstream is complicated, with a friendly fork at
opengrads and last libgadap can be packaged now. I'll still be working
with upstream, so I could help with chosing which version to package and
things like that.
Recently added packages:
As some of you may know, after more than a month of consultation,
feedback and tweaking new font packaging guidelines have been approved
New font packages in review must now conform to the new templates, and
current packages be converted in rawhide by their maintainers. To track
the conversion progress I will henceforth file tickets in bugzilla.
The following packages have already been converted in rawhide and can
serve as examples if the templates in the fontpackages-devel package are
not clear enough:
Note that the discussed renames and splits have not been submitted for
approval yet (I'm waiting for the rename process to be clarified), so
the current change is purely technical.
Nevertheless the new templates make creation of sub-packages
considerably easier and safer, so I advice packagers to perform a split
by family now if they don't mind. There was a broad consensus for the
splitting in general, and the only thing that remains to be clarified
before submission FPC-side is the wording of the few exceptions.
I want to update libcdio to 0.81. libcdio 0.81 requires a rebuild of all
application linking against it. If I used repoquery correctly following
packages in fedora and rpmfusion need a rebuild:
xmms2: LGPLv2+ and GPLv2+ and BSD
libcdio also changes the license to GPLv3+ which is a problem only for
bmpx which, according to RPM, is GPLv2.
I tried to rebuild all packages against the new libcdio 0.81 and the
following rebuilds where successful:
I was not able to rebuild the following packages, but all of them are
right now not rebuildable at all. Even with the current libcdio.
I can do all the necessary rebuilds of the rebuildable packages.
I will commit libcdio 0.81 in the next few days to rawhide.
the manpage for repoquery says that is is possible to search for
BuildRequires using this command:
repoquery --archlist=src --whatrequires gail-devel
But it gives me a traceback. Is it still supposed to work? There was
also a thread on yum-devel about searching BuildRequires -
-----BEGIN PGP SIGNED MESSAGE-----
nowaday I have read in the german fedora forum, that grub is not able
ext4 file systems. In opposite grub2 should be able to support ext4.
Because Fedora/Red Hat is a leader of development of the ext4 file
system, I want to
ask about the plan for ext4 on F11 or F12.
Because, I'm assume, that you don't want to patch grub for ext4, you
have to migrate
to grub2 if you want to support ext4 on /boot.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----