more TERM breakage [screen, gnome-terminal]
by Tim Waugh
My gnome-terminal window title no longer changes when I ssh to another
Fedora machine. Both machines involved have current rawhide
installed.
Is this more TERM=gnome breakage?
Is it related to the fact that screen no longer updates the window
title and instead puts messages on the bottom row of the terminal?
Tim.
*/
19 years, 9 months
xscale port of fedora core 2
by Lennert Buytenhek
Hi,
Some weeks ago, I started porting Fedora Core 2 to the Intel IXP2400,
which is basically a 600MHz big-endian xscale (ARM) core. Right now
I have ~550 out of ~950 packages building and seemingly in good order.
(I have not yet attempted to build openoffice and such.)
I would like to start submitting the (surprisingly small number of)
needed patches so far back into Fedora, perhaps shifting my efforts
towards FC3. What do people here think about such an effort?
cheers,
Lennert
19 years, 9 months
Re: nfsroot on FC2 x86_64 not functional?
by Gary Molenkamp
>
> Attached is the latest version I have of the script - maybe try that?
I tried the latest diskless-mkinitrd scripts with the latest kernel.org
kernel 2.6.8-rc4:
no root= boot option asks for root=, OK tried:
root=/dev/ram0
and
root=/dev/ram
Then mounts root (ext2 filesystem) read-only. Frees unused memory,
Panics.
no init found for both the above, added init=/linuxrc
Same panic, so init found.
??
--
Gary Molenkamp SHARCNET
Systems Administrator University of Western Ontario
gary(a)sharcnet.ca http://www.sharcnet.ca
(519) 661-2111 x88429 (519) 661-4000
19 years, 9 months
Re: evolution formatting problem.
by Naoki
Haha! :)
I did this and it all worked!
# rpm -q gtkhtml3
gtkhtml3-3.3.0-1
# rpm -Uvh --oldpackage gtkhtml3-3.1.19-1.i386.rpm
error: Failed dependencies:
gtkhtml3 = 3.3.0-1 is needed by (installed) gtkhtml3-devel-3.3.0-1
# rpm -e gtkhtml3-devel
# rpm -Uvh --oldpackage gtkhtml3-3.1.19-1.i386.rpm
Preparing... ########################################### [100%]
1:gtkhtml3 ########################################### [100%]
Excellent thanks!
On Tue, 2004-08-10 at 10:35 +0100, Rui Miguel Seabra wrote:
> On Tue, 2004-08-10 at 18:32 +0900, Naoki wrote:
> > Excellent, could you just email them to me off the list?
>
> If rawhide evolution can't work with this RPMS, tell me and we'll find a
> way to send you the evolution RPM too.
>
> You'll need to rpm -e gtkhtml3 gtkhtml3-devel --nodeps
> before installing these rpms.
>
> Rui
>
19 years, 9 months
packaging pyc files - again
by Zoltan Kota
Hi,
There was a thread in this list about packaging python pyc and pyo files:
http://www.redhat.com/archives/fedora-devel-list/2004-February/msg00115.html
As I see there was no consensus if pyc files should be included
or %ghost-ed.
The spec template of fedora-rpmdevtools mentions only that *.pyo should be
marked as %ghost.
I am submitting a python application to Fedora Extras which contains the
pyc files by default. It is not clear if I should %ghost the pyc files or
not (my srpm was set as NEEDSWORK in fedora.us). As I know having the pyc
files might make the application to load a
bit faster. Since the program is executed normally by normal users, the
pyc files cannot be created automatically by python in /usr/share/app
where the files are installed.
Please help me to clarify what to do.
Zoltan
19 years, 9 months
devhelp, epiphany and mozilla announcemnets
by seth vidal
Hey,
Packagers:
If you issue an update, please issue a notice to SOMEWHERE about it.
updates in final update path that don't have notices:
mozilla
epiphany
devhelp
Thanks
-sv
19 years, 9 months
FC and SATA RAID (dmraid)
by Markus Nicolussi
Can anyone tell me when Fedora will be ready to install on a SATA RAID,
which was set up in the SATA-RAID-chip-BIOS?
There are much postings on the Fedora mailing lists on this topic, but all i
could find out on the mailing lists and in the internet is, that there is a
tool which seems to be important for this problem. (dmraid)
but then i got stuck, because the documentation is so poor. and because i
need install CD's which see my SATA-RAID (SiI chip --> Medley)
ciao, nico.
--
NEU: WLAN-Router f�r 0,- EUR* - auch f�r DSL-Wechsler!
GMX DSL = superg�nstig & kabellos http://www.gmx.net/de/go/dsl
19 years, 9 months
Question about how to announce packages
by Silke Reimer
Hallo list again,
I just did my self-introduction and immediately I have my first
questions:
1.
If I want to announce and provide the packages which I produced, is
it necessary to set up a special directory tree on my server
(something like fedora/2/i386/RPMS.unstable etc.) where the packages
are made available for download?
2.
I am not sure about the right Fedora tree for my packages. Most of
them are stable in my opinion and could placed in testing but since
these are my first Fedora packages I am thinking about to place them
in unstable for the start. What do you think?
3.
I don't know which official group I should use. For the libraries
this is rather easy. But I don't what to do with GIS software
(perhaps Applications/Productivity). It is even more difficult with
geodata. They don't seem to fit to any group of RH (s.
http://www.fedora.us/wiki/RPMGroups). Any idea?
Ciao,
Silke
--
Silke Reimer
Intevation GmbH http://intevation.de/
FreeGIS http://freegis.org/
19 years, 9 months
Integrate dormant fedora-legacy in up2date/yum packages before EOL
by Axel Thimm
Instead of having users manually edit their config files to switch to
fedora legacy updates when the time comes, how about having fedora
legacy activated with an empty set of packages (but valid metadata
nonetheless) from the very start? fedora-legacy could "populate" empty
updates directories for FC1-FCX today and get into up2date's and yum's
config files.
When the distribution reaches EOL and fedora-legacy becomes
authoritative over it, fedora-legacy will only need to put the new
errata packages into the prepared folders and not have to propaganda
the correct usage of yum config lines etc.
If that sounds like a good idea, I suggest to add this to FC3 and also
have update packages for FC1/FC2 before they reach their EOL (in
FC1/FC2 updates, not fedora-legacy's, otherwise this defeats the
purpose of a smooth transition).
There is an immediate drawback for the legacy server of course, every
yum update of every fedora box worldwide will ask for one header.info
file for each operation. While the bandwidth will be low, the number
of accesses per time unit will be quite immense.
Also there might be an educational interest, that users should be
forced to do the switch manually to be aware of changed situation. In
this case at least have the config lines commented in the
resp. configuration files with a comment like:
# Fedora Legacy updates
# When a Fedora distribution reaches its EOL it is taken over by the
# Fedora Legacy project, see http://fedoralegacy.org/some/url/here/
# Uncomment the following to get access to errata packages crafted by
# the Fedora Legacy project.
#[fedoralegacyupdates]
#name=Fedora Core $releasever - $basearch - Released Updates by FedoraLegacy
#baseurl=http://download.fedoralegacy.org/fedora/$releasever/updates/$basearch
--
Axel.Thimm at ATrpms.net
19 years, 9 months
