Trying stuff in the testing repository
by Alan Cox
I have an FC1 box that tracks the testing repository. With the latest updates
it got part way through updating, failed on cpp (unpacking failed) - disk
was mostly empty. This set of updates applied so far also broke up2date
entirely
Traceback (most recent call last):
File "/usr/sbin/up2date", line 1198, in ?
sys.exit(main() or 0)
File "/usr/sbin/up2date", line 316, in main
sources = sourcesConfig.getSources()
File "sourcesConfig.py", line 169, in getSources
File "sourcesConfig.py", line 32, in __init__
File "sourcesConfig.py", line 61, in load
File "sourcesConfig.py", line 128, in parseYum
NameError: global name 'up2dateUtils' is not defined
20 years, 2 months
/sbin not in path
by Sean Earp
Hello all-
I did not see an answer to this in the archives, so if it is a stupid
question, I apologize in advance.
I just did a clean install of FC2 Test 1, formatting my drive in
advance. I chose all the default options during the install. Once I
booted up to the desktop, I did not have any network connectivity
(although the internet/network worked fine with FC1). I popped open a
terminal window and typed
ifconfig
To check if I was obtaining an IP address. I received a message that
the command "ifconfig" could not be found. After doing some
troubleshooting, I found that /sbin was not part of my
default path. If I manually move to the /sbin directory and run
./ifconfig, it works fine. If export the /sbin directory to my path,
it works fine.
My question is... Is the omission of the /sbin directory in the
default path an error, or is something messed up with my installation?
As far as I recall, ifconfig worked just fine in FC1
Any information would be much appreciated. Thanks a million,
-Sean
20 years, 2 months
question regarding mount.cifs, samba, kernel 2.6.3
by Bart Kalita
I'm still trying to mount remote WIN shares on FC2 after finding
"sharity" and realising that in "free" mode it allows only for 1
share to be mounted and that $: mount.cifs comes up with "command
not found" I'm at a loss as to what to do next.
Now, for the question, or rather questions:
1. am I just simply thick as a brick and the whole thing is simple but
I'm doing something wrong?
2. Is samba offered in devel tree for FC2 never than samba 3.0.2a
offeverd by samba for FC1?
3. Is there a posibility to have mntsmb "turned on" in the kernels form
the devel tree?
4. Or is there an rpm or anything else that I can download to make this
whole problem go away?
TIA
--
____________________________________________________
Bart Kalita MCP
www.bart-domain.com
www.astradine.no-ip.org
20 years, 2 months
openh323 build breaks at speexcodec
by sean darcy
I'm rebuilding openh323-1.13.2-0.pre1.1.src.rpm. It fails here:
g++ -DP_USE_PRAGMA -fno-rtti -ffunction-sections -fdata-sections
-D_REENTRANT - Wall -march=athlon-xp -m3dnow -msse -mmmx -mfpmath=sse -Os
-fPIC -DPTRACING -I /usr/src/redhat/BUILD/openh323-1.13.2pre1/include
-DHAS_OSS -DPTRACING -I/usr/sh are/pwlib//include -march=athlon-xp -m3dnow
-msse -mmmx -mfpmath=sse -Os -x c+ + -c speexcodec.cxx -o
/usr/src/redhat/BUILD/openh323-1.13.2pre1/lib/obj_linux_x 86_r/speexcodec.o
speexcodec.cxx: In member function `virtual BOOL
SpeexCodec::EncodeFrame(BYTE*,
unsigned int&)':
speexcodec.cxx:404: error: cannot convert `float*' to `short int*' for
argument
`2' to `int speex_encode(void*, short int*, SpeexBits*)'
speexcodec.cxx: In member function `virtual BOOL
SpeexCodec::DecodeFrame(const
BYTE*, unsigned int, unsigned int&)':
speexcodec.cxx:418: error: cannot convert `float*' to `short int*' for
argument
`3' to `int speex_decode(void*, SpeexBits*, short int*)'
make[2]: ***
[/usr/src/redhat/BUILD/openh323-1.13.2pre1/lib/obj_linux_x86_r/spee
xcodec.o] Error 1
I upgraded to gcc-3.3.3-2. Same result.
Anybody got an idea?
sean
_________________________________________________________________
Find and compare great deals on Broadband access at the MSN High-Speed
Marketplace. http://click.atdmt.com/AVE/go/onm00200360ave/direct/01/
20 years, 2 months
RE: turnover wait push
by Fred New
It sounds like you are looking in the original FC2T1
(test/1.90/i386/os/Fedora/RPMS) directory since that is the kernel that
was shipped with the release of FC2T1.
The latest kernels are in the "rawhide" (development/i386/Fedora/RPMS)
directory.
Fred
-----Original Message-----
From: fedora-test-list-admin(a)redhat.com
[mailto:fedora-test-list-admin@redhat.com] On Behalf Of Harry Putnam
Sent: 26. veebruar 2004. a. 6:57
To: fedora-test-list(a)redhat.com
Subject: Re: turnover wait push
Harry Putnam <reader(a)newsguy.com> writes:
>> rsync://carroll.cac.psu.edu/ seems to be updated, as that is what I
>> mirror.
>
> Oh, thanks... that one isn't on the list at
> http://fedora.redhat.com/download/mirrors.html
But they are at kernel-2.6.1-1.65.i686.rpm too.
--
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
Add/Remove Programs
by Sean Earp
Hello all-
I decided to fire up the Add/Remove Programs (control panel?) and make
a few changes to my installed programs configuration. First of all,
the interface looks GREAT!
That having been said, the program itself does not appear to work. I
have tried to install several different packages (ABI Office, GNU Cash,
OpenSSL) which happen to be located on different CDs. After checking
dependencies, the program asks me to insert the appropriate CD (which I
do), and after scanning the CD, the error message:
----------
Error installing packages
There was an error installing packages.
Exiting
----------
Pops up... After hitting "OK", the entire program exits. This happens
with every program I try to add. Is there an error log that I can look
at to troubleshoot/post to bugzilla, relating to the usage of
Add/Remove programs?
Thanks,
-Sean
GPG public key: <http://homepage.mac.com/smearp/seanpgp.asc>
20 years, 2 months
Oddity with "w"
by Warren Togami
[root@test32 root]# w
23:41:32 up 14 min, 3 users, load average: 0.49, 0.87, 0.49
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root tty1 - 23:27 3days 0.05s 0.05s -bash
root tty2 - 23:40 34.00s 0.02s 0.02s -bash
root pts/0 192.168.1.100 23:41 0.00s 0.02s 0.00s w
[root@test32 root]# uptime
23:44:20 up 17 min, 3 users, load average: 0.03, 0.49, 0.40
Does something look odd here? Anyone else experience this on pure rawhide?
Warren
20 years, 2 months
perl + spamassasin dependency redux
by Robert G. (Doc) Savage
The latest perl and perl-suidperl 5.8.3-9 packages just posted to
updates-testing trigger a familiar dependency problem:
Unresolvable chain of dependencies:
spamassassin 2.63-0.2 requires /usr/lib/perl5/site_perl/5.8.1
Please modify your package selections and try again.
The -0.2 spamassassin package fixed a similar problem on Feb 11.
Warren? Michael? Shrek-m? Gentlemen, start your engines...
--Doc Savage
Fairview Heights, IL
20 years, 2 months
Re: where to announce and discuss test updates (Re: Fedora Core 1 Test Update)
by Jef Spaleta
Let me sum up the debate about this:
group A wants the test update notices to be more widely distributed
via other mediums beyond just the test-list. fedora-list was suggested
as an example medium to use for wider notification.
group B thinks fedora-list is pretty much /dev/null, and posting
notices there will only encourage people to discuss things in
fedora-list instead of moving over to fedora-test. Or god
forbid..crosspost.
Both groups are right.
Might I suggest that someone approach the community sites like
fedoranews or fedorazine to shepherd something like an rss feed
for the test update notices...or a summary webpage or just the test
update notices. The key idea is to find secondary communication mediums
that are solely informative and not open for feedback. So that all
potential discussion is driven to the fedora-test-list... instead of
falling into secondary feedback forums, where it does no good.
fedora-list, being purely noisy discussion, is probably the best worst
example of the type of secondary feedback forum...no wait...slashdot
would be the best worst example. But wider distribution of the testing
notice texts isn't a completely horrible idea, you just have to avoid
communication channels that encourage feedback anywhere but in the
fedora-test-list or bugzilla.
-jef
20 years, 2 months