openssh
by bastard operater
Openssh 3.8 is now available. Openssh 3.7.1 was available for the FC1 test
1 release, but it was not included. Will openssh 3.8 be included in the
test2 release?
BOFH1234
_________________________________________________________________
Get business advice and resources to improve your work life, from bCentral.
http://special.msn.com/bcentral/loudclear.armx
20 years, 2 months
Re: Pb with fedora distrib and compaq NC4000 laptop
by Erich Hoover
I don't know about ACPI, but sound and USB should be fixable.
For Sound:
Run the tool in "System Settings" called "Soundcard Detection", it should be able to find your soundcard and configure it.
For USB:
If you can't use ANY USB devices then the host controller isn't getting loaded properly, try adding the line:
alias usb-controller uhci-hcd
to the file '/etc/modprobe.conf' in order to have the system load the host controller.
Hope that helps!
>Hello, i am quite a newbie on linux and i try to install linux (fedora
>core V1) on my compaq NC4000 laptop with kernel 2.4.
>
>It was quite perfect except that the network card did'nt work and froze
>the laptop. So i decide to upgrade the kernel to 2.6 (a friend of mine
>said it could fix my problem). He was right, my netword card is ok, but
>now neither sound, acpi and usb cdrom or key work.
>
>I need help, i try to execute some how to to install my sound card
>manually but without success.
>
>Thanks in advance.
>
>
>
>
>
>
>
>Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout !
>Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/
>
>Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez Yahoo! Messenger sur http://fr.messenger.yahoo.com
<http://fr.messenger.yahoo.com>
20 years, 2 months
Re: yum 2.0.5.20040229-1 problem
by sangu
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=117290
2004-03-02 (화) 14:47 -0500에 Marcus Schuetz 쓰기를:
> After upgrading to the latest yum in rawhide (2.0.5.20040229-1) I am
> getting the following error when doing a yum list updates / yum update:
>
> Unable to find pid
> Gathering header information file(s) from server(s)
> Server: Fedora Core 1.90 - Development Tree
> Server: Fedora.us Extras (Stable)
> Server: Fedora.us Extras (Testing)
> Server: Fedora.us Extras (Unstable)
> Server: Livna.org Fedora Compatible Packages (stable)
> Server: Livna.org Fedora Compatible Packages (testing)
> Server: Livna.org Fedora Compatible Packages (unstable)
> Finding updated packages
> Downloading needed headers
> rpmdb: Program version 4.2 doesn't match environment version
> error: db4 error(22) from dbenv->open: Invalid argument
> error: cannot open Packages index using db3 - Invalid argument (22)
> error: cannot open Packages database in
> /usr/lib/rpmdb/i386-redhat-linux/redhat
> Traceback (most recent call last):
> File "/usr/bin/yum", line 30, in ?
> yummain.main(sys.argv[1:])
> File "/usr/share/yum/yummain.py", line 253, in main
> clientStuff.download_headers(HeaderInfo, nulist)
> File "/usr/share/yum/clientStuff.py", line 919, in download_headers
> cachedbdict = returnCacheDBHeaders(nulist)
> File "/usr/share/yum/clientStuff.py", line 901, in returnCacheDBHeaders
> mi = cachedb.dbMatch()
> TypeError: rpmdb open failed
> Exit 1
>
> :: Marcus
>
>
> --
> fedora-test-list mailing list
> fedora-test-list(a)redhat.com
> To unsubscribe:
> http://www.redhat.com/mailman/listinfo/fedora-test-list
>
20 years, 2 months
Fedora Bug Day Tomorrow: March 3rd 2004: Don't Bug Mark Day
by Jef Spaleta
What: Fedora Bug Day: Learn to be a package shepherd
Help us out with Fedora Core triage by picking your favorite
Fedora Core package and acting as its community shepherd, by helping
the package maintainer keep up with bug reports and submitted patches
and so on and so forth.
Alan Cox I think said it best:
"Track the bugs in your favorite package/component:
* try to make a few minutes everyday to look through the new bugs filed
in the last day for the package you want to watch.
* Sign up for the upstream mailing lists and bug tracking system, so you
can more effectively be able to move bugs reported to Fedora upstream
where they are more likely to be fixed."
And to put a finer point on it Warren Togami adds:
"Most projects don't have anything like an effective bug tracker of
their own. Because of that, what we need are volunteers to serve as
liaison to upstream projects. They should be members of those upstream
mailing lists and pay attention to news/patches/security alerts there.
Such helpers if they are diligent would be like assistants to the
package maintainers, and learn things as they go as well as gain trust
in the process"
When: March 3rd, starting at 14:00 UTC (09:00 EST)
Where: #fedora-bugs channel on freenode irc network
How:
Come to the #fedora-bugs channel on the freenode irc network tomorrow
and be a part of the discussion. Instead of writing a very long drawn
out explanation of what you should be doing as a package shepherd. I'll
just point you to an example.
http://www.ottolander.nl/gnome-panel/
I think leonardjo created a very useful shepherding tool with this
simple static table. I think people might be able to do a lot of good
taking this static table summary example and reusing it for other
packages in Fedora Core. Poor Mark, he had to be the guinea pig package
maintainer for leonardjo's proactive shepherding experiment. So instead
of just picking on Mark, maybe its time to pick on..err i mean help...a
few more package maintainers as well. So come on over to the
#fedora-bugs channel tomorrow, pick a fedora core package you would like
to start shepherding and start digging into the steaming pile of bugs
waiting for you in bugzilla.
What else:
And if you can't be a package shepherd just yet, you're you can still be
useful for general Fedora Core Triage, and help clean out
the cobwebs in bugzilla so developers can find the bugreports that need
attention.
Huh: No Clue What I'm talking about when I say the phrase Fedora
Triage?
Take a quick look at the fedora-triage-list archives:
https://lists.dulug.duke.edu/pipermail/fedora-triage-list/
These messages should hopefully tell you what its all about in more
detail:
http://tinyurl.com/ywma3 - Summary of my vision for Fedora Triage
http://tinyurl.com/23alw - My short term goals and long term plan
-jef"black belt cat herder"spaleta
20 years, 2 months
Evolution broken deps
by Pedro Fernandes Macedo
I'm trying to install evolution 1.4.5-7 on a FC2t1 machine and I'm getting these messages:
[root@tirael headers]# yum install evolution
Gathering header information file(s) from server(s)
Server: Fedora Core 1.90 - i386 - Development Tree
Finding updated packages
Downloading needed headers
Resolving dependencies
....Unable to satisfy dependencies
Package evolution needs libgal-2.0.so.5, this is not available.
Package evolution needs libgal-a11y-2.0.so.5, this is not available.
Package evolution needs libgtkhtml-3.0.so.2, this is not available.
Package evolution needs libgtkhtml-a11y-3.0.so.2, this is not available.
Package evolution needs libsoup-2.0.so.0, this is not available.
[root@tirael headers]#
I did use yum provides filename , but it only finds these libs in the libname-debuginfo packages , so it's
not what evolution wants.. (it matches /usr/lib/debug/usr/lib/libgal-2.0.so.5.0.1.debug when I look for libgal-2.0.so.5 , for example)
Is this really broken or am I doing something stupid?
--------------------
Pedro Fernandes Macedo
20 years, 2 months
Pb with fedora distrib and compaq NC4000 laptop
by christophe BONNEL
Hello, i am quite a newbie on linux and i try to install linux (fedora
core V1) on my compaq NC4000 laptop with kernel 2.4.
It was quite perfect except that the network card did'nt work and froze
the laptop. So i decide to upgrade the kernel to 2.6 (a friend of mine
said it could fix my problem). He was right, my netword card is ok, but
now neither sound, acpi and usb cdrom or key work.
I need help, i try to execute some how to to install my sound card
manually but without success.
Thanks in advance.
Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout !
Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/
Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez Yahoo! Messenger sur http://fr.messenger.yahoo.com
20 years, 2 months
Graphic Interface for ACLs
by Erich Hoover
Will there be a graphic interface for ACLs? I saw a few threads about
turning them on, but I think it would be much more useful to be able to
set ACLs with GNOME or KDE. Is there actually a graphic interface for
this and I'm just blind?
20 years, 2 months
FC2-t1 exhibits long delay on LVM setup
by Ben Steeves
I just installed a FC2 Test 1 system and applied all of the days
patches. When the machine boots, it sits at teh "Setting up Logical
Volume Management" phase for a very long time (about 5 minutes). After
this delay, the message "setlocale failed" is printed and boot continues
normally. The filesystems all appear to work correctly.
Is anyone else seeing odd LVM behaviour?
--
Ben Steeves _ bcs(a)metacon.ca
The ASCII ribbon campaign ( ) ben.steeves(a)unb.ca
against HTML e-mail X GPG ID: 0xB3EBF1D9
http://www.metacon.ca/ascii / \ Yahoo Messenger: ben_steeves
20 years, 2 months
version/release identification for packages
by Gene C.
There seems to be this desire to put oddball version/release identifiers for
packages. First, in FC2-T1 there was util-linux 2.12pre-3 being updated with
2.12-4 but rpm and up2date consider the older package to be newer. Now, for
FC1 the recent update for tcpdump has 3.7.2-7.1 being updated by
3/7/2-7.fc1.1 but (again) the older packages is considered newer (and the
same is true for libpcap 0.7.2-7.1 being updated by 0.7.2-7.fc1.1).
For folks just letting up2date figure out what needs to be updated, this is a
major problem. Please stop doing this.
--
Gene
20 years, 2 months
Testing procedures
by shmuel siegel
If testers are expected to stay synced with rawhide then the schedule
page on the fedora site needs to be modified. The following quote
implies that a tester is expected to test the test release.
"Releases during the test phase will be three weeks apart. Longer means
testers are testing software that is too old; shorter means that testers
abort testing too soon to start downloading the newer test release."
20 years, 2 months
