recover from broken yum transaction
by Ahmed Kamal
Hi,
I had my computer hang during a major yum upgrade. Now, package-cleanup
mentions like 50 duplicate packages installed. I had it clean them up. But
now my system does not feel "clean". I am afraid if I reboot it won't come
up. Is there a smart way to verify all system files are intact. rpm -Va
outputs lots of crappy changes that are "normal". Any way to only get a
warning, when something really important has changed ?
Thanks
15 years, 8 months
Heads up: packages with Patch:/%patch0 or Patch0:/%patch issues in Rawhide
by Ville Skyttä
Hi,
There's a number of packages that have problems with the new rpm's behavior of
not applying Patch0: with plain %patch or not applying Patch: with %patch0.
I just discovered that for some reason, the rpmbuild process does not
terminate because of this error, so unless people read their build logs
carefully, some patches may go unapplied. https://bugzilla.redhat.com/461347
Below is a list of packages that most likely need packager action. One way to
fix them is to convert all unnumbered Patch: lines to Patch0: and all
unnumbered %patch lines to %patch0 or %patch -P 0.
---
Patch: in specfile, applied with %patch0:
alsa-oss
perl-JSON-Any
rcs
starfighter
tailor
time
Patch0: in specfile, applied with %patch (without -P 0):
abe
bit
bontmia
cjet
classpathx-jaf
conexus
cpan2rpm
dosbox
dwdiff
eclipse-subclipse
environment-modules
extrema
freetennis
gai-pal
hdf
hspell
ifplugd
ipcalculator
kompose
ksynaptics
liblqr-1
libnetfilter_conntrack
libnetfilter_queue
libnfnetlink
lvm2
mboxgrep
nec2c
nethogs
osiv
papyrus
pards
perl-BSD-Resource
perl-XML-Smart
plexus-runtime-builder
qemu-launcher
ruby-postgres
shapelib
speech-dispatcher
sundials
svnmailer
symlinks
sysstat
tclparser
tremulous
uisp
unix2dos
weechat
wgrib2
windowlab
worminator
xbae
xmlroff
xpdf
zvbi
15 years, 8 months
Orphaning my packages
by Alain PORTAL
Hi,
As said some days ago, I want to release ownership of my packages:
fcron -- A task scheduler
kbackup -- Back up your data in a simple, user friendly way
kicad -- Electronic schematic diagrams and printed circuit board artwork
man-pages-fr -- French version of the Linux man-pages
pikdev -- IDE for development of PICmicro based application (under Linux/KDE)
piklab -- Development environment for applications based on PIC & dsPIC
microcontrollers
pikloops -- Code generator for PIC delays
tetex-eurofont -- Provides a command that prints a euro symbol
utrac -- Universal Text Recognizer and Converter
Any takers?
Regards,
Alain
--
Les pages de manuel Linux en français
http://manpagesfr.free.fr/
15 years, 8 months
where does pulseaudio store session information?
by Christoph Höger
Hi,
I encounter the following behaviour: When I mute my notebook, after a
reboot the sound is enabled at full volume level. That's annoying.
I figured out that pulseaudio runs a rather small app named
gconf-helper. The source code indicates that this app gets some gconf
values from /system/pulseaudio/ but that key seems not to exist.
So where (if at all) does pulseaudio store its data?
regards
christoph
15 years, 8 months
Orange Sombrero 9 Released - based on Fedora
by Jeroen van Meeuwen
One more Software Freedom Day well spent ;-)
I'm proud to announce a new minor player in the world of insignificant
clones of major, important Free and Open Source Linux Distributions,
*bling* Orange Sombrero - /based on Fedora/ *bling*
Orange Sombrero starts with releasing version number 9 - the same
version number as the upstream distribution, Fedora, to avoid confusion.
Has anything been changed?
Yeah, a patch to anaconda[1,2] that didn't make it in in time for the
Fedora 10 Beta freeze has been applied to compose this release -which is
sort of the entire use case behind the patch anyway. Also, a different
branch of Revisor has been used that uses the patch to anaconda[3].
Since I've got limited bandwidth and disk space, this is a 1 CD
distribution. If I had bandwidth and disk space, I might have thrown in
a mid-release Everything Spin but I couldn't. Also, given that this is a
1 CD distribution, I've added an install class to anaconda so that it
selects the correct groups of packages. Who needs "Office &
Productivity" if there's only @core and @base, right? "Base System" FTW!
It was fun, it took me 4 koji scratch builds of anaconda and another
number of composes to get it "right".
Note that despite these changes the installed system will behave just
the same as Fedora. In fact, if you look really hard, there's the
occasional "Fedora" in there, still -maybe that's because I used
fedora-release, which I should be able to do without trademark
violations, even though /etc/fedora-release still says "Fedora" ;-)
Why bother?
Trademark guidelines right now say a derivative distribution cannot use
"based on Fedora" -which is bad, and Orange Sombrero is now raising some
red flags about it. Work is well on it's way to improve that
situation[4] though, for which I thank everyone involved. I hope soon,
very soon, derivative's of Fedora pop up everywhere, like mushrooms in
autumn.
Where is it?
http://orangesombrero.org (torrents)
On behalf of the entire Orange Sombrero Community (e.g. ~1 person),
Kind regards,
Jeroen van Meeuwen
-kanarip
[1] http://tinyurl.com/49eq5n
[2] http://tinyurl.com/47v38s
[3] http://tinyurl.com/4le262
[4] http://tinyurl.com/6d3ykf
15 years, 8 months
Further recommended slip of Beta, and Fedora 10 schedule
by Jesse Keating
After a week(end) of hacking, we're just not there yet for Beta. There
are a few more anaconda issues that we're tracking down:
* Network installs where network needs to be brought up in stage2
* Installs via Media
* Doing something with tracebacks
We're fairly confident that we've got fixes for these issues, but given
the current timeline we'd rather have a few more days of testing rather
than rush something out that doesn't work.
The Release Engineering team is recommending a slip of the Beta release
date to Tuesday Sept 30th. To go along with this slip, we recommend
that all further points of the Fedora 10 schedule slip out a week as
well, which would put the Fedora 10 release date at November 25th.
While we realize that this is a Holiday week for the vast majority of
people in the United States of America, the work for Fedora 10 would
have to have been completed by Nov 20th in order to release on the 25th
so there should not be (many) schedule conflicts. Any further slipping
of the schedule will slip around this holiday week.
FESCo will need to ACK this schedule change, and we are also making sure
this schedule doesn't conflict with (m)any thing(s) at Red Hat, and
other distributions. An announcement of the schedule change will be
made when it is fully approved.
--
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, 8 months
rawhide report: 20080921 changes
by Fedora compose checker
Updated Packages:
anaconda-11.4.1.38-1
--------------------
* Sat Sep 20 18:00:00 2008 David Cantrell <dcantrell(a)redhat.com> - 11.4.1.38-1
- Restore old lang-names generation method (dcantrell)
- Remount /mnt/sysimage/dev after migrating filesystems. (clumens)
- Use the instroot parameter like we should be doing. (clumens)
Summary:
Added Packages: 0
Removed Packages: 0
Modified Packages: 1
Broken deps for i386
----------------------------------------------------------
bodhi-server-0.5.0-7.fc9.noarch requires python-turboflot
evolution-brutus-1.2.17-1.fc10.i386 requires libBrutusKeyringd-1.0.so.1
evolution-brutus-1.2.17-1.fc10.i386 requires libcamel-1.2.so.12
gscan2pdf-0.9.24-1.fc10.noarch requires perl(Gtk2::ImageView)
pyclutter-0.6.2-2.fc9.i386 requires libclutter-glx-0.6.so.0
pyclutter-cairo-0.6.2-2.fc9.i386 requires libclutter-cairo-0.6.so.0
pyclutter-cairo-0.6.2-2.fc9.i386 requires libclutter-glx-0.6.so.0
pyclutter-gst-0.6.2-2.fc9.i386 requires libclutter-gst-0.6.so.0
pyclutter-gst-0.6.2-2.fc9.i386 requires libclutter-glx-0.6.so.0
pyclutter-gtk-0.6.2-2.fc9.i386 requires libclutter-glx-0.6.so.0
pyclutter-gtk-0.6.2-2.fc9.i386 requires libclutter-gtk-0.6.so.0
python-gammu-0.26-1.fc10.i386 requires libGammu.so.3
ruby-rpm-1.2.3-4.fc9.i386 requires librpmdb-4.4.so
ruby-rpm-1.2.3-4.fc9.i386 requires librpm-4.4.so
ruby-rpm-1.2.3-4.fc9.i386 requires librpmio-4.4.so
ruby-rpm-1.2.3-4.fc9.i386 requires librpmbuild-4.4.so
smolt-server-1.1.1.1-6.fc10.noarch requires python-turboflot
Broken deps for x86_64
----------------------------------------------------------
evolution-brutus-1.2.17-1.fc10.i386 requires libBrutusKeyringd-1.0.so.1
evolution-brutus-1.2.17-1.fc10.i386 requires libcamel-1.2.so.12
evolution-brutus-1.2.17-1.fc10.x86_64 requires libBrutusKeyringd-1.0.so.1()(64bit)
evolution-brutus-1.2.17-1.fc10.x86_64 requires libcamel-1.2.so.12()(64bit)
gscan2pdf-0.9.24-1.fc10.noarch requires perl(Gtk2::ImageView)
pyclutter-0.6.2-2.fc9.x86_64 requires libclutter-glx-0.6.so.0()(64bit)
pyclutter-cairo-0.6.2-2.fc9.x86_64 requires libclutter-glx-0.6.so.0()(64bit)
pyclutter-cairo-0.6.2-2.fc9.x86_64 requires libclutter-cairo-0.6.so.0()(64bit)
pyclutter-gst-0.6.2-2.fc9.x86_64 requires libclutter-glx-0.6.so.0()(64bit)
pyclutter-gst-0.6.2-2.fc9.x86_64 requires libclutter-gst-0.6.so.0()(64bit)
pyclutter-gtk-0.6.2-2.fc9.x86_64 requires libclutter-glx-0.6.so.0()(64bit)
pyclutter-gtk-0.6.2-2.fc9.x86_64 requires libclutter-gtk-0.6.so.0()(64bit)
python-gammu-0.26-1.fc10.x86_64 requires libGammu.so.3()(64bit)
ruby-rpm-1.2.3-4.fc9.x86_64 requires librpmio-4.4.so()(64bit)
ruby-rpm-1.2.3-4.fc9.x86_64 requires librpm-4.4.so()(64bit)
ruby-rpm-1.2.3-4.fc9.x86_64 requires librpmdb-4.4.so()(64bit)
ruby-rpm-1.2.3-4.fc9.x86_64 requires librpmbuild-4.4.so()(64bit)
Broken deps for ppc
----------------------------------------------------------
evolution-brutus-1.2.17-1.fc10.ppc requires libBrutusKeyringd-1.0.so.1
evolution-brutus-1.2.17-1.fc10.ppc requires libcamel-1.2.so.12
evolution-brutus-1.2.17-1.fc10.ppc64 requires libBrutusKeyringd-1.0.so.1()(64bit)
evolution-brutus-1.2.17-1.fc10.ppc64 requires libcamel-1.2.so.12()(64bit)
gscan2pdf-0.9.24-1.fc10.noarch requires perl(Gtk2::ImageView)
pyclutter-0.6.2-2.fc9.ppc requires libclutter-glx-0.6.so.0
pyclutter-cairo-0.6.2-2.fc9.ppc requires libclutter-cairo-0.6.so.0
pyclutter-cairo-0.6.2-2.fc9.ppc requires libclutter-glx-0.6.so.0
pyclutter-gst-0.6.2-2.fc9.ppc requires libclutter-gst-0.6.so.0
pyclutter-gst-0.6.2-2.fc9.ppc requires libclutter-glx-0.6.so.0
pyclutter-gtk-0.6.2-2.fc9.ppc requires libclutter-glx-0.6.so.0
pyclutter-gtk-0.6.2-2.fc9.ppc requires libclutter-gtk-0.6.so.0
python-gammu-0.26-1.fc10.ppc requires libGammu.so.3
ruby-rpm-1.2.3-4.fc9.ppc requires librpmdb-4.4.so
ruby-rpm-1.2.3-4.fc9.ppc requires librpm-4.4.so
ruby-rpm-1.2.3-4.fc9.ppc requires librpmio-4.4.so
ruby-rpm-1.2.3-4.fc9.ppc requires librpmbuild-4.4.so
Broken deps for ppc64
----------------------------------------------------------
eclipse-mylyn-3.0.1-2.fc10.noarch requires ws-commons-util >= 0:1.0.1-5
eclipse-mylyn-3.0.1-2.fc10.noarch requires xmlrpc3-common >= 0:3.0-1jpp.3
eclipse-mylyn-3.0.1-2.fc10.noarch requires xmlrpc3-client >= 0:3.0-1jpp.3
evolution-brutus-1.2.17-1.fc10.ppc64 requires libBrutusKeyringd-1.0.so.1()(64bit)
evolution-brutus-1.2.17-1.fc10.ppc64 requires libcamel-1.2.so.12()(64bit)
gscan2pdf-0.9.24-1.fc10.noarch requires perl(Gtk2::ImageView)
gspiceui-0.9.65-2.fc10.ppc64 requires gwave
livecd-tools-018-1.fc10.ppc64 requires yaboot
perl-Test-AutoBuild-darcs-1.2.2-3.fc9.noarch requires darcs >= 0:1.0.0
pyclutter-0.6.2-2.fc9.ppc64 requires libclutter-glx-0.6.so.0()(64bit)
pyclutter-cairo-0.6.2-2.fc9.ppc64 requires libclutter-glx-0.6.so.0()(64bit)
pyclutter-cairo-0.6.2-2.fc9.ppc64 requires libclutter-cairo-0.6.so.0()(64bit)
pyclutter-gst-0.6.2-2.fc9.ppc64 requires libclutter-glx-0.6.so.0()(64bit)
pyclutter-gst-0.6.2-2.fc9.ppc64 requires libclutter-gst-0.6.so.0()(64bit)
pyclutter-gtk-0.6.2-2.fc9.ppc64 requires libclutter-glx-0.6.so.0()(64bit)
pyclutter-gtk-0.6.2-2.fc9.ppc64 requires libclutter-gtk-0.6.so.0()(64bit)
python-gammu-0.26-1.fc10.ppc64 requires libGammu.so.3()(64bit)
ruby-rpm-1.2.3-4.fc9.ppc64 requires librpmio-4.4.so()(64bit)
ruby-rpm-1.2.3-4.fc9.ppc64 requires librpm-4.4.so()(64bit)
ruby-rpm-1.2.3-4.fc9.ppc64 requires librpmdb-4.4.so()(64bit)
ruby-rpm-1.2.3-4.fc9.ppc64 requires librpmbuild-4.4.so()(64bit)
15 years, 8 months
Mono 2.0 in F10
by Paul F. Johnson
Hi,
I've been informed that Mono 2.0 RC3 is due out next week (RC3 is going
to be the actual release from what I've been told).
If it is out next week, can we get it pushed for inclusion into F10 (it
is mostly bug fixes over the version currently in rawhide, so testing
will need to be minimal)? It will mean that when F10 is released, it
will have something that not even OpenSuSE will have, the proper Mono
2.0 in - a big bonus for us!
A knock on is that the mono packagers should be able to get the full
1.9.x stack into F9, so there should be less problems than we're
currently finding with pushing into core.
TTFN
Paul
--
Sie können mich aufreizen und wirklich heiß machen!
15 years, 8 months
modesetting feature status
by David Airlie
Hi,
So one of the features we've been trying to land for F10 that is a major
change in how we deal with graphics hardware in the Linux world.
https://fedoraproject.org/wiki/Features/KernelModesetting
This is going to be a slightly bumpy ride as it involves re-doing all we
know about GPU drivers from the ground up. From the kernel to X.org to
3D pieces.
So first off how to disable modesetting:
add nommodeset to the kernel command line in grub
grub can be accessed by holding down the Ctrl key.
We are targeting for F10 support for radeon GPUs from r300 to r500 (and
possibly r600/r700), and Intel GPUs from i830 to GM45 (though it may end
up i915 and up only)
For the beta we are only going to enable Radeon support for the r300 to
r500 class of hardware, while we await upstream changes to the Intel
driver. The intel mode code is more mature, however Intel are currently
trying to push the memory manager feature to the kernel first, so are
working on stabilising that before finishing the mode setting code. We
are including the current Intel code but not enabling it at all until
further work is completed. We will switch the code on depending on how
things play out and how much testing we think it has had.
So why are we doing this:
1. Way better startup sequence.
2. Faster X startup.
3. Better fast-user-switching support
4. Better suspend/resume support
5. Oops/panic messages can appear when X is running.
Caveats for Beta release:
1. Performance
You will probably notice performance is below what you are used to on
the same hardware with the older drivers. This is due to a lack of
performance optimization so far and also now that we do more stuff in
the kernel, the kernel debugging overheads have a lot more influence on
the desktop.
2. 3D.
3D support is not as good. We are currently working with a beta 3D
driver on these cards. Compiz might not work for the beta release, we
will get it working for F10 final of course.
3. suspend/resume.
Suspend/resume may corrupt the graphics.
Thanks to everyone who has been involved in this so far and testing all
that they have so far.
Dave.
15 years, 8 months