Debuginfo broken in rawhide
by Hans de Goede
Hi all,
The debug directory of the devel directory does not contain a repodata
dir, breaking install of -debuginfo packages through yum.
Regards,
Hans
18 years, 1 month
Wild and crazy times for the development tree
by Jeremy Katz
With the release of Fedora Core 5, the development tree is now open for
things to continue forward. So if you've been following it purely to
get updates for the FC5 test releases, you'll probably want to grab the
fedora-release package from the FC5 release instead. If you want to
keep testing and helping to develop things for Fedora Core 6, expect for
some fun to pop up as always.
Jeremy
18 years, 1 month
rawhide report: 20060325 changes
by Build System
Updated Packages:
audiofile-1:0.2.6-3
-------------------
* Fri Mar 24 2006 Matthias Clasen <mclasen(a)redhat.com> - 1:0.2.6-3
- Reduce memory consumption by making data tables const
coreutils-5.94-2
----------------
* Fri Mar 24 2006 Tim Waugh <twaugh(a)redhat.com> 5.94-2
- 5.94.
cups-1:1.2-0.1.b2.6
-------------------
* Fri Mar 24 2006 Tim Waugh <twaugh(a)redhat.com> 1:1.2-0.1.b2.6
- Add KDE compatibility symbols _ipp_add_attr/_ipp_free_attr to ipp.h, with
a comment saying why they shouldn't be used.
* Fri Mar 24 2006 Tim Waugh <twaugh(a)redhat.com> 1:1.2-0.1.b2.5
- Fix KDE compatibility symbols _ipp_add_attr/_ipp_free_attr.
* Fri Mar 24 2006 Tim Waugh <twaugh(a)redhat.com> 1:1.2-0.1.b2.4
- Update to svn snapshot.
db4-4.3.29-4
------------
* Fri Mar 24 2006 Jindrich Novy <jnovy(a)redhat.com> 4.3.29-4
- drop useless java, lfs patches
epiphany-2.14.0-1
-----------------
* Sun Mar 12 2006 Ray Strode <rstrode(a)redhat.com> - 2.14.0-1
- Update to 2.14.0
foomatic-3.0.2-34
-----------------
* Fri Mar 24 2006 Tim Waugh <twaugh(a)redhat.com> 3.0.2-34
- Always use /usr/lib/cups/{backend,filter}.
gedit-1:2.14.1-1
----------------
* Thu Mar 16 2006 Matthias Clasen <mclasen(a)redhat.com> 2.14.1-1
- Update to 2.14.1
gthumb-2.7.5.1-2
----------------
* Fri Mar 24 2006 Matthias Clasen <mclasen(a)redhat.com> - 2.7.5.1-2
- Update to 2.7.5.1
hplip-0.9.9-7
-------------
* Fri Mar 24 2006 Tim Waugh <twaugh(a)redhat.com> 0.9.9-7
- Include hpfax.
- Build requires libusb-devel.
kernel-2.6.16-1.2088_FC6
------------------------
* Fri Mar 24 2006 David Woodhouse <dwmw2(a)redhat.com>
- Fix lockup when someone takes the bcm43xx device down while it's
scanning (#180953)
* Thu Mar 23 2006 Juan Quintela <quintela(a)redhat.com>
- disable sky2 (as it is broken upstream)
* Thu Mar 23 2006 Juan Quintela <quintela(a)redhat.com>
- fix xen to compile with 2.6.16-git6.
libsepol-1.12.2-1
-----------------
* Fri Mar 24 2006 Dan Walsh <dwalsh(a)redhat.com> 1.12.2-1
- Upgrade to latest from NSA
* Fixed avrule_block_write num_decls endian bug.
* Fri Mar 17 2006 Dan Walsh <dwalsh(a)redhat.com> 1.12.1-1
- Upgrade to latest from NSA
* Fixed sepol_module_package_write buffer overflow bug.
* Fri Mar 10 2006 Dan Walsh <dwalsh(a)redhat.com> 1.12-2
- Upgrade to latest from NSA
* Updated version for release.
* Merged cond_evaluate_expr fix from Serge Hallyn (IBM).
* Fixed bug in copy_avrule_list reported by Ivan Gyurdiev.
* Merged sepol_policydb_mls_enabled interface and error handling
changes from Ivan Gyurdiev.
mtr-2:0.71-1
------------
* Fri Mar 24 2006 Miroslav Lichvar <mlichvar(a)redhat.com> - 2:0.71-1
- update to mtr-0.71
selinux-policy-2.2.26-1
-----------------------
* Wed Mar 22 2006 Dan Walsh <dwalsh(a)redhat.com> 2.2.25-3
- Fix policyhelp
smartmontools-1:5.33-7
----------------------
* Fri Mar 24 2006 Tomas Mraz <tmraz(a)redhat.com> - 1:5.33-7
- add missing quotes to /etc/sysconfig/smartmontools
squirrelmail-1.4.6-4.fc6
------------------------
* Fri Mar 24 2006 Warren Togami <wtogami(a)redhat.com> 1.4.6-4
- Fix outgoing Japanese mail to iso-2022-jp for now (#185767)
xinetd-2:2.3.14-2
-----------------
* Fri Mar 24 2006 Jay Fenlason <fenlason(a)redhat.com> 2:2.3.14-2
- Upgrade to new upstream version. This obsoletes the -libwrap,
-rpc, -banner, -bug140084 and -gcc4 patches.
Broken deps for i386
----------------------------------------------------------
GFS-kernel - 2.6.15.1-5.FC5.17.i686 requires /lib/modules/2.6.15-1.2054_FC5
GFS-kernel - 2.6.15.1-5.FC5.17.i686 requires kernel = 0:2.6.15-1.2054_FC5
GFS-kernel-smp - 2.6.15.1-5.FC5.17.i686 requires /lib/modules/2.6.15-1.2054_FC5smp
GFS-kernel-smp - 2.6.15.1-5.FC5.17.i686 requires kernel-smp = 0:2.6.15-1.2054_FC5
GFS-kernel-xen0 - 2.6.15.1-5.FC5.17.i686 requires kernel-xen0 = 0:2.6.15-1.2054_FC5
GFS-kernel-xenU - 2.6.15.1-5.FC5.17.i686 requires /lib/modules/2.6.15-1.2054_FC5xenU
GFS-kernel-xenU - 2.6.15.1-5.FC5.17.i686 requires kernel-xenU = 0:2.6.15-1.2054_FC5
cman-kernel - 2.6.15.1-0.FC5.16.i686 requires /lib/modules/2.6.15-1.2054_FC5
cman-kernel - 2.6.15.1-0.FC5.16.i686 requires kernel = 0:2.6.15-1.2054_FC5
cman-kernel-smp - 2.6.15.1-0.FC5.16.i686 requires /lib/modules/2.6.15-1.2054_FC5smp
cman-kernel-smp - 2.6.15.1-0.FC5.16.i686 requires kernel-smp = 0:2.6.15-1.2054_FC5
cman-kernel-xen0 - 2.6.15.1-0.FC5.16.i686 requires kernel-xen0 = 0:2.6.15-1.2054_FC5
cman-kernel-xenU - 2.6.15.1-0.FC5.16.i686 requires /lib/modules/2.6.15-1.2054_FC5xenU
cman-kernel-xenU - 2.6.15.1-0.FC5.16.i686 requires kernel-xenU = 0:2.6.15-1.2054_FC5
dlm-kernel - 2.6.15.1-0.FC5.14.i686 requires /lib/modules/2.6.15-1.2054_FC5
dlm-kernel - 2.6.15.1-0.FC5.14.i686 requires kernel = 0:2.6.15-1.2054_FC5
dlm-kernel-smp - 2.6.15.1-0.FC5.14.i686 requires /lib/modules/2.6.15-1.2054_FC5smp
dlm-kernel-smp - 2.6.15.1-0.FC5.14.i686 requires kernel-smp = 0:2.6.15-1.2054_FC5
dlm-kernel-xen0 - 2.6.15.1-0.FC5.14.i686 requires kernel-xen0 = 0:2.6.15-1.2054_FC5
dlm-kernel-xenU - 2.6.15.1-0.FC5.14.i686 requires /lib/modules/2.6.15-1.2054_FC5xenU
dlm-kernel-xenU - 2.6.15.1-0.FC5.14.i686 requires kernel-xenU = 0:2.6.15-1.2054_FC5
gnbd-kernel - 2.6.15-5.FC5.23.i686 requires /lib/modules/2.6.15-1.2054_FC5
gnbd-kernel - 2.6.15-5.FC5.23.i686 requires kernel = 0:2.6.15-1.2054_FC5
gnbd-kernel-smp - 2.6.15-5.FC5.23.i686 requires /lib/modules/2.6.15-1.2054_FC5smp
gnbd-kernel-smp - 2.6.15-5.FC5.23.i686 requires kernel-smp = 0:2.6.15-1.2054_FC5
gnbd-kernel-xen0 - 2.6.15-5.FC5.23.i686 requires kernel-xen0 = 0:2.6.15-1.2054_FC5
gnbd-kernel-xenU - 2.6.15-5.FC5.23.i686 requires /lib/modules/2.6.15-1.2054_FC5xenU
gnbd-kernel-xenU - 2.6.15-5.FC5.23.i686 requires kernel-xenU = 0:2.6.15-1.2054_FC5
Broken deps for ia64
----------------------------------------------------------
rgmanager - 1.9.31-3.ia64 requires ccs
Broken deps for ppc64
----------------------------------------------------------
avalon-logkit - 1.2-3jpp_3fc.noarch requires servletapi5
castor-demo - 0.9.5-1jpp_2fc.noarch requires servletapi5
emacs - 21.4-5.ppc64 requires fonts-xorg-75dpi
geronimo-specs - 1.0-0.M2.2jpp_7fc.ppc64 requires servletapi5
hsqldb - 1.80.1-1jpp_8fc.ppc64 requires servletapi5
jakarta-commons-fileupload - 1:1.0-3jpp_5fc.noarch requires servletapi5
jakarta-taglibs-standard - 1.1.1-4jpp_3fc.noarch requires servletapi5 >= 0:5.0.16
struts - 1.2.8-2jpp_9fc.ppc64 requires servletapi5
struts-webapps-tomcat5 - 1.2.8-2jpp_9fc.ppc64 requires tomcat5
velocity - 1.4-3jpp_4fc.noarch requires servletapi5
xalan-j2-demo - 2.6.0-3jpp_9fc.ppc64 requires servletapi5
Broken deps for s390
----------------------------------------------------------
avalon-logkit - 1.2-3jpp_3fc.noarch requires servletapi5
castor-demo - 0.9.5-1jpp_2fc.noarch requires servletapi5
geronimo-specs - 1.0-0.M2.2jpp_7fc.s390 requires servletapi5
hsqldb - 1.80.1-1jpp_8fc.s390 requires servletapi5
jakarta-commons-fileupload - 1:1.0-3jpp_5fc.noarch requires servletapi5
jakarta-taglibs-standard - 1.1.1-4jpp_3fc.noarch requires servletapi5 >= 0:5.0.16
rhythmbox - 0.8.8-2.s390 requires libgstgconf-0.8.so.0
rhythmbox - 0.8.8-2.s390 requires libgstreamer-0.8.so.1
rhythmbox - 0.8.8-2.s390 requires libgstcontrol-0.8.so.1
struts - 1.2.8-2jpp_9fc.s390 requires servletapi5
struts-webapps-tomcat5 - 1.2.8-2jpp_9fc.s390 requires tomcat5
velocity - 1.4-3jpp_4fc.noarch requires servletapi5
xalan-j2-demo - 2.6.0-3jpp_9fc.s390 requires servletapi5
xmlrpc - 2.0.1-1jpp_6fc.s390 requires servletapi5
Broken deps for s390x
----------------------------------------------------------
avalon-logkit - 1.2-3jpp_3fc.noarch requires servletapi5
castor-demo - 0.9.5-1jpp_2fc.noarch requires servletapi5
geronimo-specs - 1.0-0.M2.2jpp_7fc.s390x requires servletapi5
hsqldb - 1.80.1-1jpp_8fc.s390x requires servletapi5
jakarta-commons-fileupload - 1:1.0-3jpp_5fc.noarch requires servletapi5
jakarta-taglibs-standard - 1.1.1-4jpp_3fc.noarch requires servletapi5 >= 0:5.0.16
rhythmbox - 0.8.8-2.s390x requires libgstcontrol-0.8.so.1()(64bit)
rhythmbox - 0.8.8-2.s390x requires libgstgconf-0.8.so.0()(64bit)
rhythmbox - 0.8.8-2.s390x requires libgstreamer-0.8.so.1()(64bit)
struts - 1.2.8-2jpp_9fc.s390x requires servletapi5
struts-webapps-tomcat5 - 1.2.8-2jpp_9fc.s390x requires tomcat5
velocity - 1.4-3jpp_4fc.noarch requires servletapi5
xalan-j2-demo - 2.6.0-3jpp_9fc.s390x requires servletapi5
Broken deps for x86_64
----------------------------------------------------------
GFS-kernel - 2.6.15.1-5.FC5.17.x86_64 requires /lib/modules/2.6.15-1.2054_FC5
GFS-kernel - 2.6.15.1-5.FC5.17.x86_64 requires kernel = 0:2.6.15-1.2054_FC5
cman-kernel - 2.6.15.1-0.FC5.16.x86_64 requires /lib/modules/2.6.15-1.2054_FC5
cman-kernel - 2.6.15.1-0.FC5.16.x86_64 requires kernel = 0:2.6.15-1.2054_FC5
dlm-kernel - 2.6.15.1-0.FC5.14.x86_64 requires /lib/modules/2.6.15-1.2054_FC5
dlm-kernel - 2.6.15.1-0.FC5.14.x86_64 requires kernel = 0:2.6.15-1.2054_FC5
gnbd-kernel - 2.6.15-5.FC5.23.x86_64 requires /lib/modules/2.6.15-1.2054_FC5
gnbd-kernel - 2.6.15-5.FC5.23.x86_64 requires kernel = 0:2.6.15-1.2054_FC5
18 years, 1 month
Support for 3Com 3CRWE737A dissapeared
by Joe Desbonnet
My 3Com 3CRWE737A Airconnect Wireless LAN PC Card (an old card, but
worked fine with every Redhat/Fedora release to date) is not
recognized by FC5 (on a Thinkpad T41p). It has worked with FC4,3,2,1
and Redhat Linux releases. I believe this card is handled by the
orinoco_cs module. I'd appreciate a pointer to some doc on how this
can be fixed: I assume this is a configuration issue rather than
support for the card being dropped from the kernel (?)
On plugging the card I get two lines in /var/log/messages:
Mar 25 04:06:12 localhost kernel: pccard: PCMCIA card inserted into slot 0
Mar 25 04:06:12 localhost kernel: pcmcia: registering new device pcmcia0.0
On unplug:
Mar 25 04:06:41 localhost kernel: pccard: card ejected from slot 0
Should I file this in bugzilla? Thanks,
Joe.
18 years, 1 month
Crashes with via_velocity?
by Chris Adams
Okay, I finally got around to loading FC5 on my Athlon 64 system here.
I first tried the 32 bit install. The install (from local hard drive)
worked fine, but during boot, it got into a cycle of oopses during or
right after network setup. I booted it single user mode and managed to
reproduce the oops.
I then tried a 64 bit install. Again, install worked fine, but it
oopses during network config during boot.
This is an Abit AV8 motherboard with built-in Via gigabit ethernet
(via_velocity). I've also added a Compaq dual 10/100 NIC (two e100
chips behind a DEC PCI bridge). The e100s are eth0 and eth1 and the
via_velocity is eth2. It oopses before configuring eth2 I think, but
the common thing in both 32 and 64 bit oopses is the message "last sysfs
file: /class/net/eth2/address".
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186584
--
Chris Adams <cmadams(a)hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
18 years, 1 month
GUI controls for instrumentation
by Kenneth Porter
I'm tasked to write a front end for an instrumentation application for
"that other operating system" ;) and I'd like to use GUI controls that are
cross-platform portable for an eventual Linux port. What would the list
recommend? I essentially need something that resembles the front panel of
an oscilloscope, along with some dial indicators and knobs. I've also been
thinking about making it web-accessible, so perhaps a Java-based solution
would be suitable.
18 years, 1 month
The Morning After
by Patrick W. Barnes
To start off, congratulations are in order for everyone who was involved in
bringing Fedora Core 5 to fruition. Fedora Core 5 is the most outstanding
Fedora Core release to date, and we've seen a lot of progress since Fedora
Core 4. Thank you and congratulations to everyone!
Overall, I think the Fedora Core 5 release was a great success. We had a few
minor glitches, as will always happen on release day, but things really came
together to deliver this awesome release in an awesome way.
While the excitement is still strong, let's look back over the events leading
up to and immediately following the release, and see what we can do to make
things better both for the lifetime of this release and for future releases.
Over the weekend, we saw quite a few leaked ISOs flying around. This is to be
expected, but we need to try to minimize this to avoid potential problems.
We also saw a large number of users take advantage of BitTorrent, which
greatly reduced demand on the main servers, but, as always, people are always
looking for more bandwidth. We've got plans in the works that will help, but
there's always room for more improvement. It is great that there is so much
interest, so how can we best support that interest without failing our
release goals?
A lot of switches and buttons had to be operated manually for this release.
We could almost certainly add automation and scheduling, and we could
streamline processes to make life easier on ourselves.
We had to update a lot of information on both fedora.redhat.com and
fedoraproject.org. We have some unnecessary duplication, and there are
places where we can get things working a little more smoothly. Jesse, and
anyone else working on these things, what did you notice? How can we improve
the process?
It took a fair chunk of the day to get the latest release notes up on the
website and working properly. Surely, we can automate some of this. I know
a lot of work is going into getting the build tools working better, but what
else can we do to simplify this for a prompt release reaction?
There were a few other technical errors or delays, such as those that prompted
symlinking torrent URLs and the update to the release announcement, the lack
of the planned instructions for CD-burning in the distribution directories,
and a few known flaws in the final release. These kinds of things are bound
to happen, especially when internal issues arise just before the release, but
that's no reason to ignore them. What did we miss, and how can we make sure
we get it right next time?
Finally, there has been a lot of buzz leading up to and following the release.
We saw a refreshing surge even before the release hit. That's great, but the
buzz could still be bigger. We saw a few reviews of the test releases, and
many sites have published new information in the last 24 hours, but how can
we generate more of this? Did anybody notice particular areas that were
undersold?
Now is the time for radical thoughts and ideas that can shape what we do to
support Fedora Core 5 and prepare for Fedora Core 6. Let's hear them!
--
Patrick "The N-Man" Barnes
nman64(a)n-man.com
http://www.n-man.com/
Have I been helpful? Rate my assistance!
http://rate.affero.net/nman64/
--
18 years, 1 month
fyi: vlc
by Neal Becker
I tried FC5 vlc from livna, but it just gave a bunch of errors when started.
Then I tried videolan-client from freshrpms. Better, but gave an error
when trying to open my dvd.
I grabbed the srpm from freshrpms, and (after d/l all the builddeps) it is
rebuilt and working great.
18 years, 1 month