Some problems with preupgrade for f11
by joakim＠verona.se
Hello,
* problem 1
I upgraded a laptop with preupgrade from f10 to f11.
The upgrade was very slow, it took about 15h to upgrade 2092 packages.
The laptop has a ssd disk, maybe thats why its slow.
At the end of the upgrade preupgrade spent several hours in the
"finishing upgrade" step, doing aparently nothing. It seemed like
NetworkManager had crashed, and maybe preupgrade tried to do a network
acess, I dont know. I rebooted the machine and it started fine.
* problem 2
I tried upgrading a server from f9 to f11 with preupgrade. When
rebooting into the upgrade image, I get a "please insert driver disk"
screen. I have a 3ware raid controlled which is supposed to be supported
by the kernel, and I did nothing special when installing f9 once upon a
time. I would very much like to upgrade this machine so any hints here
would be apreciated.
--
Joakim Verona
15 years
From the desk of Jim Whitehurst...
by Paul W. Frields
http://press.redhat.com/2009/06/11/fedora-11-%e2%80%93-wow/
The URL above links to a wonderful note from Jim Whitehurst, President
and CEO of Red Hat, congratulating the community on the release of
Fedora 11. I think it's fantastic that Fedora gets such solid support
from the very top ranks at Red Hat, directly on the company's press
site. One thing that is always in the back of my head, as we work
through all the various release bits, is that I know on release day
Red Hat's CEO -- just like thousands of other people -- is going to
download Fedora and take it for a ride.
Although Jim singled out some specific areas in his blog that
immediately impressed him about Fedora 11, from our phone
conversations I know that he's very proud of the work every team in
Fedora does. He is genuinely passionate about Fedora, and that's due
to *your* superb efforts as part of our large extended family of
contributors.
Thanks to all of you for making this release such an incredible
experience. I hope you enjoy Fedora 11 too, and I'm very excited
about working with all of you on Fedora 12!
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
15 years
Finding file conflicts
by Axel Thimm
Hi,
I ran into a situation where two packages in F10 (pwlib-devel and
ptlib-devel) contained file conflicts, and yum tried to install
both (in this case there seems to be a bug that made yum ignore the
Obsoletes: line of on of the packages).
If I as a packager craft a package for Fedora, how can I check that
this package's contents aren't accidentially conflicting with another
package in Fedora? Is there some magic python script that would check
a package against a whole repo?
Thanks!
--
Axel.Thimm at ATrpms.net
15 years
x86_64 kernel + i586 F11 userspace + yum
by Paul Jakma
Hi,
I run the above system, and everything works fine (except perhaps for
SELinux[1]). I have created a /etc/rpm/platform containing
'i586-redhat-linux'.
Well, everything works except for one thing: yum. Installing with
'yum install name' no longer works, I must now instead explicitly
specify the arch, e.g. 'yum install name.i58'.
Does anyone know a fix for this?
Also, if I explicitely add the x86-64 updates repo, and only include
the 'kernel' package from it, should I be able to expect that yum
update will Do The Right Thing, or will I need to manually 'yum
install kernel.x86_64' whenever kernels are updated (or worse)?
Thanks.
1. Least, I presume this is SELinux related:
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses
genfs_contexts
ioctl32(mount:1503): Unknown cmd fd(3) cmd(80041272){t:12;sz:4}
arg(ffb0eb68) on /home/xguest
ioctl32(mount:1503): Unknown cmd fd(3) cmd(00001260){t:12;sz:0}
arg(ffb0eb70) on /home/xguest
ioctl32(mount:1503): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28}
arg(ffb0eb4c) on /home/xguest
regards,
--
Paul Jakma paul(a)clubi.ie paul(a)jakma.org Key ID: 64A2FF6A
Fortune:
"But officer, I was only trying to gain enough speed so I could coast
to the nearest gas station."
15 years
Pkgdb 0.4 update scheduled for Monday
by Toshio Kuratomi
Hi all,
Assuming all goes well with an account system upgrade this week, we're
going to be updating the PackageDB to 0.4 on Monday, June 10. An outage
notification will go out later that tells the exact times. This is just
a note that anyone who has scripts hitting the package database for
information should check that they still work with the instance we are
running in staging:
https://admin.stg.fedoraproject.org/pkgdb/
The most notable change to the API is that usernames and group names are
now returned everywhere isntead of userids and groupids. For the most
part, this should make scripts simpler as you no longer have to query
FAS if you just need the username.
If you encounter bugs or have any concerns, let me know via email, a
reply to this message, or on irc.freenode.net (I'm abadger1999).
-Toshio
15 years
USB autosuspend in F12
by Matthew Garrett
USB is an irritating protocol that requires USB controllers to remain
active whenever a device is attached, even if that device is doing
nothing. This consumes unnecessary power and can prevent the system
going into deep idle states under some circumstances. The kernel
supports USB autosuspend, which allows idle USB devices to be suspended
and the upstream ports to power down. This is disabled by default
because it breaks various pieces of hardware.
Through F12 I'm going to be slowly enabling autosuspend on various
pieces of USB hardware. The aim is to ensure that it's only enabled on
hardware that supports it. This is going to be a combination of kernel
modifications and packaging changes, and while I'll be testing as many
as possible before uploading anything there's a risk that some hardware
will misbehave. I'll let people know when I think I'm about to upload
anything risky.
The first part of this is an upload of libfprint which enables
autosuspend on fingerprint readers. I'm expecting this to be pretty
safe, but there's always the possibility that a couple of people will
find problems. If your fingerprint reader suddenly stops working after
this change, please file a bug and include the output of lsusb.
--
Matthew Garrett | mjg59(a)srcf.ucam.org
15 years
Live from Raleigh, it's Fedora Activity Day! (A list of proposals regarding Fedora Development Cycle)
by Jesse Keating
We've had a very productive 3 days here at the Fedora Activity Day. Our
wiki page [1] details what we came here to as well as gobby logs of our
work in progress.
Yesterday we identified a number of proposals we could make to resolve
many of the issues we've talked about, and today we created a series of
wiki pages to contain those proposals.
Below you will find a list of the proposals as well as the principle
person responsible for the proposal. Some of these will be ready for
FESCo review now, some will require more work and discussion, and some
will require others to be finished first.
https://fedoraproject.org/wiki/Milestone_Adjustment_Proposal - Bill
Nottingham
https://fedoraproject.org/wiki/Israwhidebroken.com_Proposal - Will Woods
and James Laska
https://fedoraproject.org/wiki/Koji_Build_Autosign_Proposal - Jesse
Keating
https://fedoraproject.org/wiki/Critical_Path_Packages_Proposal - Seth
Vidal
https://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal - Jesse
Keating
I'm sure we'll be seeing more chatter about these in the coming days. I
would request that if you wish to talk about any of these proposals,
please start a new thread, lest this becomes a giant pile-on thread that
would be difficult to follow in the archives, OR use the discussion tab
in the wiki page for the particular proposal.
For those of you that were able to join our Fedora Talk session and IRC
channel, thank you for your valuable input and I hope we made it easy to
participate as the event happened.
Things are winding down here, a few of us are going to start some of the
groundwork for some of these proposals as well as tackling some of the
other issues identified at this FAD which require no proposal for
change, only time and energy to fix.
I hope you all enjoyed Fedora 11!
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
15 years
Re: rpms/polkit-gnome/devel polkit-gnome.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
by Christoph Wickert
Am Montag, den 08.06.2009, 20:47 +0000 schrieb David Zeuthen:
> Author: davidz
[snipped]
> --- NEW FILE polkit-gnome.spec ---
> Summary: PolicyKit integration for the GNOME desktop
> Name: polkit-gnome
> Version: 0.92
> Release: 1%{?dist}
> License: LGPLv2
> URL: http://www.freedesktop.org/wiki/Software/PolicyKit
> Group: Applications/System
> Source0: http://hal.freedesktop.org/releases/%{name}-%{version}.tar.bz2
> BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root
> BuildRequires: gtk2-devel
> BuildRequires: polkit-devel >= 0.92
> BuildRequires: desktop-file-utils
>
> # for /usr/share/gnome/autostart
> Requires: gnome-session
Great! This adds
gnome-session: 1.8 MB
control-center: 7.1 MB
GConf2: 5,5 MB
gnome-keyring: 2,3 MB
gnome-vfs2: 3.1 MB
You added at least ~ 22,8 MB overhead just for directory ownership,
although I asked you to _not_ do this. I think users of alternative
desktops and the maintainers of their spins will not be amused. Last
week you told me, that a one advantage of the new polkit is that no
longer requires GConf2, but now it's dragged in again.
> %description
> polkit-gnome provides an authentication agent for PolicyKit
> that matches the look and feel of the GNOME desktop.
>
> %prep
> %setup -q
>
> %build
> %configure --enable-gtk-doc
> make
Still no parallel build, only one of several problems. I already pointed
that out during the so called "review" [1] and I find it sad to see you
don't give anything about feedback, good advice and not even the
packaging guidelines.
Regards,
Christoph
[1] https://bugzilla.redhat.com/show_bug.cgi?id=502920
15 years
