traceback when installing openssh-server
by Alexandre Magaz Graça
Hi,
Since some days ago, livecd-creator is falling with this traceback
(latest git version):
Traceback (most recent call last):
File "/usr/bin/livecd-creator", line 1503, in <module>
sys.exit(main())
File "/usr/bin/livecd-creator", line 1483, in main
target.unmount()
File "/usr/bin/livecd-creator", line 503, in unmount
self.ayum.close()
File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 92, in
close
self._repos.close()
File "/usr/lib/python2.5/site-packages/yum/repos.py", line 76, in close
repo.close()
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 257, in
close
self.sack.close()
File "/usr/lib/python2.5/site-packages/yum/sqlitesack.py", line 233,
in close
del self.pkgobjlist
AttributeError: pkgobjlist
I noticed that it only happened when the base group is installed. After
some tests, I discovered it was caused by the openssh-server package (ks
attached). It worked when I tested in another machine, but failed againg
after a system update which included yum (from 3.2.1-1.fc7 to 3.2.5-1.fc7).
Could someone give some hint about how to find out what is making it fail?
Thanks,
Àlex
lang ca_ES.UTF-8
keyboard es
timezone Europe/Madrid
auth --useshadow --enablemd5
xconfig --startxonboot
services --enabled=NetworkManager,dhcdbd --disabled=network
selinux --disabled
firewall --disabled
repo --name=fedora --baseurl=http://ftp.udl.es/pub/fedora/linux/releases/7/Everything/i386/os
%packages
openssh-server
@core
bash
kernel
passwd
chkconfig
rootfiles
16 years, 6 months
livecd built from git on top of rawhide
by Tim Wood
I've converted a Fedora 8 test 2 system to rawhide, installed livecd-
creator from GIT
* I'm still getting the no repository available to set up error
* I'm also getting a lot of python errors referring to /usr/lib/
python2.5/site-packages/yum/__init__.py.
I'm using /usr/share/livecd-tools/livecd-fedora-minimal.ks as my
config with the selinux flag changed from enforcing to disabled.
Questions that seem relevant that I can find any answers to:
*) I've seen some allusions in my digging that using 'Fedora' as part
of the repo name causes problems because it wasn't disabled in yum.
Does that mean going into /etc/yum... and setting enabled to 0 on all
the repos while running livecd-creator?
Does it mean doing the same thing on just repos with similar naming
Is livecd-creator supposed to grab the repository config from /etc/
yum/something?
*) What constitutes a valid repository?
Should the path end with a slash?
Should it point to the directory holding the repodata dir or
someplace else?
*) Is there a FAQ or other additional documentation? If I was stupid
enough ;-) to voluntee sr, is there a need for someone to maintain
this stuff?
I've found the reasonably obvious stuff:
- appropriate docs in /usr/
- the material on the website that essentially mirrors that
- the LiveCDHowTo in the FedoraLiveCD part of the wiki
*) Does someone have a working config file that uses a public repo
that they'd post?
Tim
16 years, 6 months
Git/Rawhide vs. v009/F7 ?
by Tim Wood
Two different recommendations have been posted on what version of
Fedora to use (F7 presumably with livecd-tools 009 vs. rawhide and
livecd-tools from git). Rawhide and git (seems to me) to be a
formula for a very unstable development environment. But, livecd-
tools 009 and F7 seem to be pretty out of date. BUT... that's my
guessing. Why one combination versus the other from someone in the
livecd development loop?
And how do you modify grub arguments for a livecd (besides doing
weird foo on a created image...)?
On Oct 6, 2007, at 6:47 AM, Chitlesh GOORAH wrote:
> On 9/27/07, Alexandre Magaz Graça wrote:
>> Could someone give some hint about how to find out what is making
>> it fail?
>
> I encountered tracebacks only when creating live images on a F7 box?
> Use a rawhide box instead with the git version of livecd-tools
>
> However my livecd images built on F8 automatically do a media check !!
> Thus wasting about 15 minutes on a 2.7GHZ box.
> Then there's kernel panics.
>
> The only way I could boot these livecd images is to edit the
> arguments on grub:
> * removing "check" ??? <<<<<<<<<<< why is this by default ????????
> * added enforcing=0
>
> regards,
> Chitlesh
>
> --
> http://clunixchit.blogspot.com
>
> --
> Fedora-livecd-list mailing list
> Fedora-livecd-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-livecd-list
>
16 years, 6 months
Bootloader timeout and default kernel checkin to git?
by Elias Hunt
Jeremy,
I noticed that there was a git checking to livecd for supporting new
kickstart use of bootloader timeout and default kernel. Is there
anywhere that tells the proper format for these in the kickstart file?
Generally I'd bug off list, but I know I've seen a number of questions
about this before on list, and figured everyone would like to know.
Thanks.
-Eli
--
Elias Hunt
Systems Engineer
M2S, Inc.
12 Commerce Ave.
W Lebanon, NH 03784
Ph: 603-298-5509 x365
Fax: 603-298-8816
hunt(a)m2s.com
16 years, 6 months
Trimming the size of LiveCD's
by Jeroen van Meeuwen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Here's a thought:
1304 random packages will install 724 MB of data in /usr/share/doc
I'm sure there is /something/ to gain here. If every package on average
installs ~0.5 MB of docs... Would it worth figuring out what docs should
be on the LiveCD in the first place? I guess removing everything RPM
calls docs is too much, as this will include man-pages as well.
Any thoughts?
- --
Kind regards,
Jeroen van Meeuwen
- -kanarip
- --
http://www.kanarip.com/
RHCE, LPIC-2, MCP, CCNA
C6B0 7FB4 43E6 CDDA D258 F70B 28DE 9FDA 9342 BF08
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFG19BDKN6f2pNCvwgRAhhaAJ9UCH9WetRBu6foxAgztqMvg3h6OwCeLZU5
LxWzG5TBxdQOAE3VGFp400w=
=YiuK
-----END PGP SIGNATURE-----
16 years, 6 months
Removing packages
by Jon Steer
Hi,
I'm a little confused about the package removal.
I have attempted to remove "wireless-tools" in my packages section, but it
doesn't get removed. Does this mean it won't remove if there are
dependencies? I thought a --nodeps was being done for this?
I have noticed in other peoples kickstart files, they specify the same
package for removal multiple times? Is there some hidden ordering issue I'm
missing?
thanks,
jon
--
"Don't stand still, if you see me running down the road, 'cause there is
trouble right behind me".
16 years, 6 months
selinux alerts and livecd doesn't boot
by Chitlesh GOORAH
Hello there,
i did a clean installation of the FEL F8T2 livecd.
then did the updates
then yum install livecd-tools (012)
I created a livecd like i used to do.
however during the installation of the packages for the livecd, there
are lots of selinux denial notification popped on the system tray.
it's nice to see the selinux notifier being integrated into the KDE desktop.
however, non of my 7 livecds I recreated was bootable.
during the build i can see restorecon /proc/1xxxx : permission denied.
I'm wondering if the livecd creation procedures have been changed
again that im unaware of or it's a bug.
see attachments.
chitlesh
--
http://clunixchit.blogspot.com
16 years, 6 months
udev selinux problem? "udevd_event selinux_setfilecon failed"
by Douglas McClendon
I may yet file a bug, if I can provide instructions on how to reproduce
this. But since I'm working from an extremely modified environment,
I'll just ask for general advice-
I've spun an selinux-enabled livecd, and upon starting up, and starting
udev, I get a whole bunch of 'errors' (perhaps harmless) that look
vaguely like the following-
udevd_event selinux_setfilecon failed permission denied /dev/usbdev....
I googled for selinux_setfilecon and found basically nothing.
Do these keywords ring a bell to anyone?
the /dev/usbdev... means that I get the same error half a dozen times
(seems relative to how many usb devices are plugged in) with various
non-intuitive incarnations of that filename.
-dmc
16 years, 6 months
Bluetooth Keyboard and Mouse (Mac)
by Peter Hutnick
I tried out the Live CD on my Mac Mini (1.66) with an Apple Bluetooth
keyboard and a 2nd gen Bluetooth Mighty Mouse.
The system booted to the desktop, but neither input device worked. I
saw something on startup about a Bluetooth daemon starting, so I had
some hope, but no dice.
Should this work (automagically)? Can this be made to work through
some manual process?
Thanks,
Peter
16 years, 6 months
