Getting to work on i18n?
by Hugo Cisneiros
Hi,
6 days ago I subscribed to this list and tried to subscribe on the i18n
project to help Fedora Linux translating something to my language
(Brazilian Portuguese).
I received an e-mail telling me that my status was pending... I have to
wait or can I work on something right now? I need some advice :) Thanks.
[]'s
Hugo
20 years, 4 months
redhat-config-network bug(and a small ethernet problem of my own)
by Karlan Kayne
////////////////////////////////////////////////////////////////
Notes from Karlan:
This happens when ever I try to activate my eth0 device(SiS 900-Based PCI
Fast Ethernet Adapter), then press cancel after given this error:
+------------------------------------------------+
| Determining IP information for eth0...
| SIOCSIFFLAGS: Device or resource busy
| SIOCSIFFLAGS: Device or resource busy
+------------------------------------------------+
(Any help with this problem would be great, I can't get on the internet
because it says this
device is [always] busy. I used to be able to connect in RH9, but now RH9
install doesn't recognize it, mandrakes does(but can't use because of the
same problem),
NOTE: Device works just fine in Windows, so it is not a hardware failure(I
believe)
YET ANOTHER NOTE: Linux(any recent verion I believe) since this point(my
troubles started) has always said it can't find OHCI drivers...blah)
////////////////////////////////////////////////////////////////
Component: redhat-config-network
Version: 1.3.10
Summary: TB3fbf821d GUI_functions.py:524:gui_run_dialog:OSError: [Errno 1]
Operation not permitted
Traceback (most recent call last):
File "/usr/bin/redhat-control-network", line 184, in
on_activateButton_clicked
(ret, msg) = dev.activate()
File
"/usr/src/build/320592-noarch/install/usr/share/redhat-config-network/netconfpkg/NCDevice.py",
line 385, in activate
dialog = dialog)
File
"/usr/src/build/320592-noarch/install/usr/share/redhat-config-network/netconfpkg/NC_functions.py",
line 512, in generic_run_dialog
dialog = dialog)
File
"/usr/src/build/320592-noarch/install/usr/share/redhat-config-network/netconfpkg/gui/GUI_functions.py",
line 524, in gui_run_dialog
OSError: [Errno 1] Operation not permitted
Local variables in innermost frame:
fdin: []
swindow: <gtk.ScrolledWindow object (GtkScrolledWindow) at 0x9490ab4>
string: <module 'string' from '/usr/lib/python2.2/string.pyc'>
okbutton: <gtk.Button object (GtkButton) at 0x94d2984>
buffer: <gtk.TextBuffer object (GtkTextBuffer) at 0x94cd524>
cancelbutton: <gtk.Button object (GtkButton) at 0x94c13b4>
command: /sbin/ifup
argv: ['/sbin/ifup', 'eth0', 'up']
searchPath: 0
CancelException: netconfpkg.gui.GUI_functions.CancelException
root: /
label: Activating network device eth0, please wait...
lbl: <gtk.Label object (GtkLabel) at 0x9490a8c>
select: <module 'select' from
'/usr/lib/python2.2/lib-dynload/selectmodule.so'>
stdin: 0
xml: <gtk.glade.XML object (GladeXML) at 0x949ed0c>
catchfd: (1, 2)
fderr: []
dlg: <gtk.Dialog object (GtkDialog) at 0x942d6ec>
errlabel: Cannot activate network device eth0!
fdout: []
vadj: <gtk.Adjustment object (GtkAdjustment) at 0x9394604>
gtk: <module 'gtk' from
'/usr/lib/python2.2/site-packages/gtk-2.0/gtk/__init__.pyc'>
iter: <GtkTextIter at 0x94cdb78>
mark: <gtk.TextMark object (GtkTextMark) at 0x94d2cbc>
write: 4
read: 3
s: SIOCSIFFLAGS: Device or resource busy
childpid: 24657
closefd: -1
dialog: None
rc:
Determining IP information for eth0...SIOCSIFFLAGS: Device or resource busy
SIOCSIFFLAGS: Device or resource busy
title: redhat-config-network:
Network device activating...
os: <module 'os' from '/usr/lib/python2.2/os.pyc'>
textview: <gtk.TextView object (GtkTextView) at 0x94d1e5c>
_________________________________________________________________
Great deals on high-speed Internet access as low as $26.95.
https://broadband.msn.com (Prices may vary by service area.)
20 years, 4 months
RE: Fedora Core 1: X86-64 Failed compile package list
by Mohammed_Khan@Dell.com
Thanks for the tips Justin.
I will keep you posted if I run across anything else.
Thanks,
MFK
-----Original Message-----
From: Justin M. Forbes [mailto:64bit_fedora@comcast.net]
Sent: Wednesday, November 12, 2003 4:51 PM
To: fedora-devel-list(a)redhat.com
Subject: Re: Fedora Core 1: X86-64 Failed compile package list
On Wed, 12 Nov 2003 Mohammed_Khan(a)Dell.com wrote:
> Folks,
>
> I tried to cross-compile all the Fedora Core 1 (yarrow) SRPMS on an
> amd64 machine running the i386 version of Fedora Core 1 (yarrow).
>
While certainly an interesting way to get to know the systems, cross
compile environments are not always the cleanest. All of these packages
except for kernel (and some hardware pieces not needed for AMD64 systems)
are already built and available for x86_64. Kernel is an interesting
beast, and currently being worked on. Target for AMD64 packages is
generally recognized as x86_64
>
> 2. How would one go about fixing packages exhibiting the first issue
> (unknown target: amd64)? Is it a matter of:
> 1. tweaking spec files
> 2. tweaking make files
> 3. tweaking source-code
> 4. combination of 1, 2, and 3?
> 5. ask/beg respective pacakage maintainers to fix?
>
> Thanks,
>
> MFK
>
6. use --target=x86_64, or download existing builds if you would rather
not eat up the CPU time.
If there are any other issued you run across, please feel free to ping me
on them, and I will look into them.
Thanks,
Justin
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-devel-list
20 years, 4 months
Fedora Core 1: X86-64 Failed compile package list
by Mohammed_Khan@Dell.com
Folks,
I tried to cross-compile all the Fedora Core 1 (yarrow) SRPMS on an amd64
machine running the i386 version of Fedora Core 1 (yarrow).
Out of 847 packages, a total of 89 packages failed to build (list attached
as a.txt)
1. 77 packages failed because the "amd64-redhat" target was not recognized.
2. Another 12 failed for other reasons (list attached as b.txt).
<<a.txt>> <<b.txt>>
I have stdout,stderr logs on each SRPM rpmbuild... (should any of this be
logged in bugzilla?)
I have a couple ?s at this point:
1. Am I doing this right? or should I try to compile the SRPMS on a box
running an amd64 linux environment....?
But this is sort of a chicken and an egg problem with Fedora, either
that or a rather painful one to solve as you would have to incrementally
build your amd64 environment while building packages. I tried to
workaround this by compiling using amd64 versions of other linux
distributions but lots of packages fail to build w/o using the --nodeps
flag... and lots more packages fail regardless...
2. How would one go about fixing packages exhibiting the first issue
(unknown target: amd64)? Is it a matter of:
1. tweaking spec files
2. tweaking make files
3. tweaking source-code
4. combination of 1, 2, and 3?
5. ask/beg respective pacakage maintainers to fix?
Thanks,
MFK
20 years, 4 months
ACPI IN KERNEL 2.4.22 INCOMPATIBLE WITH KDE???
by Giuseppe Cavallo
Hi All,
RedHat 9.0 I installed the Linus' kernel (downloaded in kernel.org), after I
recompilt it, when I wanted shoutdown my Laptop (Asus L8416K {L8400L serie})
the system don't shoutdown completely but on the monitor I watch the string
"Power down" and I shutdown the computer with the power off button. This same
problem I have had in Fedora Core 1 Kernel
2.4.22-1.2115.nptl. The thing curious is, that, if I don't login in KDE and I
shoutdown my system by KDM or Terminal the system shoutdown normaly
otherwhise when I login KDE I have that problem.
I don't understand what I can resolve the problem.
--
[--Saluti Giuseppe Cavallo--]
20 years, 4 months
Getting to work on i18n?
by Hugo Cisneiros
Hi,
6 days ago I subscribed to this list and tried to subscribe on the i18n
project to help Fedora Linux translating something to my language
(Brazilian Portuguese).
I received an e-mail telling me that my status was pending... I have to
wait or can I work on something right now? I need some advice :) Thanks.
[]'s
Hugo
20 years, 4 months
Participe
by Miguel Vazquez Gocobachi
Hello.
I'm Miguel Vazquez from Mexico, I interestering in a Fedora Project,
so I can translate language the site and others documents to Spanish.
What I need?
.-.
/v\
// \\
^^-^^
Fundador
ANCrae, Inc
GNU/Linux & FreeBSD
http://www.ancrae.org/
_____________________________________________________________
Create tu cuenta de email en www.esdebian.org
20 years, 4 months
Self Introduction: Paul Nasrat
by Paul Nasrat
Name: Paul Nasrat
Location: London, UK
Profession: Package monkey/sysadmin/developer
Company: undisclosed
Goals:
Working with Fedora to ensure quality packages, timely updates, etc. I'm
intrested in build systems and automation.
Packages I want to see published - synaptics driver which I will submit
one of these days. Happy and have done some QA and also bug triaging at
f.r.c
Historical Qualifications:
Developer on ELKS (particularly the SIBO port)
JPackage Project member
fedora ppc interests
I potter with python, C and java.
Why trust me - hopefully my track record helps, and I'm pretty
enthusiastic and helpful, occasionally I have clue too.
Ob GPG stuff:
pub 1024D/831FFBCA 2003-02-21 Paul Nasrat <pauln(a)truemesh.com>
Key fingerprint = 9693 1E2A 30A0 9E24 708E DC98 E618 76E8 831F FBCA
sub 1024g/0653AAB4 2003-02-21
Paul
20 years, 4 months
Fedora Triage: where things are at.
by Jef Spaleta
On a completely different topic...the full (but tiny, and I'm going to
start targeting people to create some useful information for the triage
effort..soon) universe of Fedora Triage knowledge awaits you at:
http://www.fedora.us/wiki/FedoraTriage
To recap where things stand:
There are about 56 'make cambridge not suck blockers' left
https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=100643
We are experimenting with building public tracking bugs as a way the
community can classify bugs so developers can run simple searches
instead of trolling through open bugs. My current example is the
EasyFix tracking bug. Which is an attempt to group the bug reports that
have trivial fixes or have attached community provided patches.
The hope is that when developers have a few minutes to work on low
priority bugs...they have a way to quickly find the easily fixable ones
so they don't waste their spare time trolling through the 'zilla.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=109188
Another community tool we are experimenting with is the use of
'triage->reason' as a formatted comment string. Examples you can
search for now are:
triage->easyfix
triage->close
triage->duplicate #bugnumber
triage->crack
There are of course more variants on the 'triage->' theme but I'd like
to come up with a reasonably short and more importantly consistantly
used list, if developers find querying against 'triage->reason' useful.
-jef"coffee it is"spaleta
20 years, 4 months
Bug Day Volume 5 - The day the mailinglists stood still
by Jef Spaleta
I encourage everyone to stop reading email today.
And instead do some valuable and needed bugzilla diving.
Oh crap, I mean stop reading email right after you read this entire
post. Err wait, you can read emails from bugzilla all day long too.
Here's today's (Un)Official Fedora Bug Day Mystery Theme:
Become involved in the fedora.us QA process and help QA packages that
are waiting to be published in the fedora.us addon repo:
http://www.fedora.us/QA
Remember, until the full merge is completed and Fedora Extras and
Alternatives is up and running...community packagers are being advised
to use fedora.us's process:
http://www.redhat.com/archives/fedora-devel-list/2003-November/msg00649.html
How do you become involved in the fedora.us QA process?
Easy, read: http://www.fedora.us/wiki/PackageSubmissionQAPolicy
I think there are enough people in the freenode irc network's
#fedora-bugs channel who are already part of the fedora.us QA wagon
train to provide some guidance if you are new to the process (hint hint
hint, that means if you ARE part of the fedora.us QA process right now,
it might be in your best interests to sit in the channel and gingerly
help new people getting started in this process as part of the bug day
call to arms)
-jef"do i need tequila or coffee right now..."spaleta
20 years, 4 months