Fedora 8 and 9 updates re-enabled
by Jesse Keating
In a few hours, updates for Fedora 8 and Fedora 9 will start hitting
mirrors. These updates are designed to transition users from our old
repo locations to new locations that have all our updates re-signed with
a new set of keys.
Most users will simply need to apply the offered updates, and later
apply any further updates, and verify/import the new GPG key.
The process to getting new updates is two stage.
Stage 1) Users configured to get updates from existing repos will see a
small set of updates available in the next few hours/days. These
updates include fedora-release, PackageKit, gnome-packagekit, and unique
(for Fedora 8, only fedora-release is offered). These updates should be
applied as soon as possible.
Stage 2) Once the above updates have been applied, your update tools
(yum, PackageKit, pirut) will see a new repository and a larger set of
updates available. This is your new standard flow of updates, that will
continue to see new updates as the lifetime of Fedora 8 and 9 progress.
There will be further milestones in the future that involve redirection
of release package repos to match that of updates, and removing of old
gpg key from rpm trust.
For more details and an FAQ, please see
https://fedoraproject.org/w/index.php?title=Enabling_new_signing_key
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
_______________________________________________
Fedora-devel-announce mailing list
Fedora-devel-announce(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-announce
15 years, 4 months
kernel-devel in "Fedora" spin?
by Jesse Keating
Back in December, I had made a change that blocked kernel-devel packages
from winding up in the install media for the Fedora spin. I don't
recall getting any push back at the time, but I've gotten at least one
angry comment since then. So I'm putting it out for more discussion.
Do we feel that the kernel-devel (5~megs) should be in the install
media?
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
15 years, 4 months
Fedora Security Tools spin
by Huzaifa Sidhpurwala
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All,
I just came across a knoppix security tool live CD and thought it would
be a good idea for a security tool fedora spin too.
The tools are freely available at:
http://knoppix-std.org/index.html
and are all GPLed?
Do you guys think this is a good idea, I am sure such a spin does not
exists in Fedora yet.
Thanks for your inputs in advance.
- --
Regards,
Huzaifa Sidhpurwala, RHCE, CCNA (IRC: huzaifas)
GnuPG Fingerprint:
3A0F DAFB 9279 02ED 273B FFE9 CC70 DCF2 DA5B DAE5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org
iD8DBQFIvgI6zHDc8tpb2uURAmrzAJ4tx7cMrCd4LNczHZ6pRS2TQ60bGQCfVhYm
aXLofMTIoK89NuDOQXjQmGI=
=Ai3F
-----END PGP SIGNATURE-----
15 years, 5 months
Off Topic: where I can see how I translate old gdm conf files to new ones?
by casimiro barreto
Hello,
After upgrading to Fedora Rel 9 I've had trouble to drop the
-nolisten in the Xserver (old defaults.conf is not working anymore)
and I need to set the command=/usr/bin/X ...
Gdm was shipped without proper documentation (no man pages, nothing
for the missing gdmsetup and other programs...
Best regards and sorry for the inconvenience...
Casimiro Barreto
15 years, 6 months
No more MAKEDEV?
by Bill Nottingham
Looking at some of the inefficiencies in bootup (in regards to the 5
second Fedora boot), we came across MAKEDEV. To be short - it's a pig.
The only user of it in Fedora is udev, which uses it for entries in
/etc/udev/makedev.d. However, there's an already-upstream solution
of putting device nodes in /lib/udev/devices. Why not just use this,
remove MAKEDEV, simplify start_udev, and boot faster?
Bill
15 years, 6 months
Help! XFCE event sounds in Rawhide -- make it stop!
by Matthew Miller
My rawhide system has always had some sound oddities ever since the
pulseaudio switch -- it really needs a reinstall. But in the last couple of
days, something has been driving me crazy: there are suddenly loud,
obnoxious sound effects when I open or close windows. There doesn't seem to
be an XFCE control panel that has anything to do with this, and changing the
gnome one has no effect. Help! Help!
--
Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>
15 years, 6 months
NetworkManager-pptp
by Mat Booth
I was pleased to see this package hanging out in Koji today. Thanks
Dan for packaging it, I've been looking forward to seeing this in
Fedora.
I've installed the x86_64 package from Koji to try it out on my F9
machine. Am I being too eager? :-)
Anyway, I've configured up my VPN connection but I can't get it to
work. Whatever I try, I always get the following:
Aug 30 16:05:40 sd NetworkManager: <info> Starting VPN service
'org.freedesktop.NetworkManager.pptp'...
Aug 30 16:05:40 sd NetworkManager: <info> VPN service
'org.freedesktop.NetworkManager.pptp' started
(org.freedesktop.NetworkManager.pptp), PID 6587
Aug 30 16:05:40 sd NetworkManager: <WARN> vpn_service_watch_cb(): VPN
service 'org.freedesktop.NetworkManager.pptp' exited with error: 1
Aug 30 16:05:45 sd NetworkManager: <info> VPN service
'org.freedesktop.NetworkManager.pptp' did not start in time,
cancelling connections
Currently, I connect to the VPN with this script (login details
censored, obviously):
http://www.matbooth.co.uk/lwd/start-vpn
Which works reasonably well. How can I make NetworkManager-pptp
connect using the settings I use in that script? What's the best way
to go about debugging this?
Regards,
Mat
--
Mat Booth
www.matbooth.co.uk
15 years, 6 months
xen kernel with dom0 in Fedora 10?
by David Hláčik
Hi , guys, I have found in Fedora 10 Features , that there is still a
lot of work to provide xen kernel with dom0 support to Fedora 10 GA.
For my future project, which at 90 percent depends on virtualization
technology I am deciding between XEN or KVM virtualization. I am
experienced XEN user, KVM is new for me. But as I am aware of,
Qumranet was bought by RedHat which predicts something ...
Thanks in advance!
David
15 years, 6 months
How important is comps.xml to us these days? Which packages should be in comps.xml and which not?
by Thorsten Leemhuis
Hi all!
I recently created comps.xml files for RPM Fusion. During that a few
things around comps.xml got discussed on the RPM Fusion lists(¹).
That and a recent change (²) to
https://fedoraproject.org/wiki/PackageMaintainers/CompsXml
made me wonder:
How important is comps.xml to us these days?
(Note that I mean Fedora and RPM Fusion with "us" here, as RPM Fusion
for things like this just follows the Fedora guidelines)
Comps.xml is afaics mainly used in anaconda (and thus indirectly in
tools like pungi that rely on anaconda) and yum (if you know what to do)
these days; PackageKit afaics doesn't use it much (or does it use
comps.xml at all? Will that change?); it just lists everything it finds
afaics (correct me if I'm wrong, I'm not using PackageKit much and just
use yum directly).
Thus for most packages it doesn't matter much if they are missing in
comps.xml -- if they are missing there they will not be able to select
in anaconda during install, but that's all. Which brings me to the
second question:
Which packages should be in comps.xml and which not?
Round about two years ago (e.g. before the merge) we IIRC for a short
while mainly said and acted like this: round about everything that is
not a lib (those normally get tracked in by deps when needed) or a devel
package should be mentioned in comps.xml; that of course included
command line apps(³). Note sure if it ever made it to the guidelines
with these or similar words; likely not. These days the wiki says:
> If you maintain an application which makes sense for a user to select
> during installation, [...] make sure that your package is listed in a
> reasonable group in the comps-fn.xml.in files.
I consider the "during installation" part not much helpful because a
package that seems unimportant during installation for 99% of the users
might be something a few other users will look out for. Heck, some new
Fedora users might even abort the Fedora install at this point if they
miss a package they really plan to use with Fedora.
But that is only one of the problems afaics; according to
http://fedoraproject.org/wiki/PackageMaintainers/PackageStatus/CompsF10Mi...
there are 2866 packages in comps-f10 and 1711 packages missing (seems
the SRPMS are used as a base here; I'm wondering if using RPMs might be
more wise, but that is just one more thing to discuss); some of
those 1711 really are in fedora for quite a while and really look to me
like worthwhile mentioning in comps.xml (see above), to make sure people
can find and select them right during install with anaconda. Do we care?
Cu
knurd
(¹) doesn't matter much for this discussion, but for the curious see
this thread
http://lists.rpmfusion.org/pipermail/rpmfusion-developers/2008-September/...
(²)
https://fedoraproject.org/w/index.php?title=PackageMaintainers%2FCompsXml...
(³) see also
http://lists.rpmfusion.org/pipermail/rpmfusion-developers/2008-September/...
15 years, 6 months