6:30 p.m.
The LiveCDs I've been trying to create today are all failing. In each
case I'm getting what looks like corrupted rpms from official repositories.
I've forced it to use three different repositories with similar
results All of the RPMs in question are either release or update
fedora 8 rpms. The only solutions I can think of vis-a-vis the RPMs is
to some variant of rebuilding, trying all the mirrors or
waaaaiiiitttting. Any other suggestions?
Tim
[snip]
Retrieving
http://linux.nssl.noaa.gov/fedora/linux/releases/8/Everything/i386/os/Pac...
...OK
Retrieving
http://mirror.cc.vt.edu/pub/fedora/linux/updates/8/i386/rarian-0.6.0-3.fc...
...OK
Retrieving
http://mirror.cc.vt.edu/pub/fedora/linux/updates/8/i386/rarian-compat-0.6...
...OK
Retrieving
http://linux.nssl.noaa.gov/fedora/linux/releases/8/Everything/i386/os/Pac...
...OK
Reducing None to included packages only
[snip]
warning: setup-2.6.10-1.fc8: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
Installing: setup ##################### [ 2/800]
[snip]
Installing: bluecurve-icon-theme ##################### [266/800]
/var/tmp/rpm-tmp.74071: line 1: touch: command not found
Installing: fedora-release-notes ##################### [267/800]
[snip]
Installing: rarian-compat ##################### [364/800]
add command failed
could not open /etc/xml/catalog for saving
add command failed
could not open /etc/xml/catalog for saving
error: %post(rarian-compat-0.6.0-3.fc8.i386) scriptlet failed, exit status 2
[snip]
Pass 5: Checking group summary information
tdw-sw-gateway-0: 91674/262144 files (0.3% non-contiguous), 517402/517402 blocks
Traceback (most recent call last):
File "/usr/bin/livecd-creator", line 132, in <module>
sys.exit(main())
File "/usr/bin/livecd-creator", line 122, in main
creator.package()
File "/usr/lib/python2.5/site-packages/imgcreate/creator.py", line 655, in
package
self._stage_final_image()
File "/usr/lib/python2.5/site-packages/imgcreate/live.py", line 295, in
_stage_final_image
self._image, minimal_size)
File "/usr/lib/python2.5/site-packages/imgcreate/fs.py", line 393, in
create_image_minimizer
cowloop.create()
File "/usr/lib/python2.5/site-packages/imgcreate/fs.py", line 193, in create
self.expand(create = True)
File "/usr/lib/python2.5/site-packages/imgcreate/fs.py", line 179, in expand
fd = os.open(self.lofile, flags)
OSError: [Errno 20] Not a directory:
'/var/tmp/imgcreate-zO-jIc/iso-HB_7Wh/LiveOS/osmin'
10:07 p.m.
The LiveCDs I've been trying to create today are all failing.
Pass 5: Checking group summary information
tdw-sw-gateway-0: 91674/262144 files (0.3% non-contiguous), 517402/517402
blocks
I suspect you're running to the problem Warren Togami reported earlier,
and that I've clumsily reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=432521.
If you look closer at the logs you'll probably see that it isn't able to
umount the install_root. This results in the install_root not getting
flushed to disk and so the filesystem is dirty. fsck comes along later
and "cleans up" by removing random stuff.
I'm trying to find out what is keeping the install_root busy...
- Orion
10:12 p.m.
> The LiveCDs I've been trying to create today are all
failing.
>
>
> Pass 5: Checking group summary information
>
> tdw-sw-gateway-0: 91674/262144 files (0.3% non-contiguous),
> 517402/517402
> blocks
I suspect you're running to the problem Warren Togami reported earlier,
and that I've clumsily reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=432521.
Sorry, that should be https://bugzilla.redhat.com/show_bug.cgi?id=430606
- Orion
11:44 p.m.
That matches some other symptoms I'm seeing. I'm encountering this with
kickstarts that worked about 2 weeks ago so it may be something recently
introduced (or uncovered by such). Is there a log file that provides
more info (beyond /var/log/messages)?
I'll have to try some of the standard kickstarts tomorrow to see if they
have the same problem ... because I suspect there's also a corrupt RPM
issue. My suspicion is that the first corrupt RPM (setup) is causing
the problems with the other RPMs.
Tim
orion(a)cora.nwra.com wrote:
>> The LiveCDs I've been trying to create today are all
failing.
>>
>>
>> Pass 5: Checking group summary information
>>
>> tdw-sw-gateway-0: 91674/262144 files (0.3% non-contiguous),
>> 517402/517402
>> blocks
>>
> I suspect you're running to the problem Warren Togami reported earlier,
> and that I've clumsily reported here:
> https://bugzilla.redhat.com/show_bug.cgi?id=432521.
>
>
Sorry, that should be https://bugzilla.redhat.com/show_bug.cgi?id=430606
- Orion
--
Fedora-livecd-list mailing list
Fedora-livecd-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
--
_________________________________
Tim Wood, CLP, RHCT
719.338.7484 (tel)
The Data Wranglers
Web, Database & more since since 1994
www.datawranglers.com
12:17 a.m.
When I say matches other symptoms... sometimes files in the working
directory (in /var/tmp/imgcreate* if I'm reading history right) never
get released. So livecd-creator exits and the directory is still
there. When I try to delete it (even with rm -rf as root), a long list
of files report being tied up. If I reboot the machine, the files are
freed and the directory and contents can be deleted. Tomorrow I'll have
to try and do some weird sys-admin lsof-type checking on those files to
see what's up.
Tim
12:08 p.m.
On Tue, 2008-02-19 at 17:30 -0700, Tim Wood wrote:
The LiveCDs I've been trying to create today are all failing. In
each
case I'm getting what looks like corrupted rpms from official repositories.
I've forced it to use three different repositories with similar
results All of the RPMs in question are either release or update
fedora 8 rpms. The only solutions I can think of vis-a-vis the RPMs is
to some variant of rebuilding, trying all the mirrors or
waaaaiiiitttting. Any other suggestions?
The scriptlet bits you're seeing aren't necessarily errors (well, there
are some that should be filed as package bugs as the packages are likely
missing proper Requires(post) bits)..
Traceback (most recent call last):
..
This is the more interesting piece. It looks very similar to
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=431287 which should
have been fixed with commit ade8a8c33a6e3051ec9bf48d0bacdd1475a2aed5.
Are you using git tip with the current configs? Or git tip with your
own config?
Jeremy
7:27 p.m.
Actually I haven't been using the git version. I just installed the git
version and built a LiveCD. The errors are identical other than the
creator.py error being in line 661 instead of 655.
Knowing not what a git tip is, I suspect the answer is "current config"
although I'm always open to enlightenment on new-to-me terms.
Tim
> Traceback (most recent call last):
>
..
This is the more interesting piece. It looks very similar to
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=431287 which should
have been fixed with commit ade8a8c33a6e3051ec9bf48d0bacdd1475a2aed5.
Are you using git tip with the current configs? Or git tip with your
own config?
Jeremy
7:46 a.m.
On Wed, 2008-02-20 at 18:27 -0700, Tim Wood wrote:
Actually I haven't been using the git version. I just installed
the
git version and built a LiveCD. The errors are identical other than
the creator.py error being in line 661 instead of 655.
Knowing not what a git tip is, I suspect the answer is "current
config" although I'm always open to enlightenment on new-to-me terms.
git tip is the current HEAD of the tree. Which version had you been
using?
Jeremy
9:54 a.m.
The rawhide version. Is it true that when I do a git clone, I'm
grabbing the head of the tree?
Tim
Jeremy Katz wrote:
On Wed, 2008-02-20 at 18:27 -0700, Tim Wood wrote:
> Actually I haven't been using the git version. I just installed the
> git version and built a LiveCD. The errors are identical other than
> the creator.py error being in line 661 instead of 655.
>
> Knowing not what a git tip is, I suspect the answer is "current
> config" although I'm always open to enlightenment on new-to-me terms.
>
git tip is the current HEAD of the tree. Which version had you been
using?
Jeremy
--
Fedora-livecd-list mailing list
Fedora-livecd-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
--
_________________________________
Tim Wood, CLP, RHCT
719.338.7484 (tel)
The Data Wranglers
Web, Database & more since since 1994
www.datawranglers.com
10:08 a.m.
On Thu, 2008-02-21 at 08:54 -0700, Tim Wood wrote:
The rawhide version.
Then I'd definitely check to make sure your config has a change similar
to ade8a8c33a6e3051ec9bf48d0bacdd1475a2aed5 or it will definitely blow
up.
Is it true that when I do a git clone, I'm grabbing the head of
the
tree?
Yep!
Jeremy
10:46 a.m.
I was using the rawhide version. I'm now using one built with git
clone/make install a day or two ago. FWIW... how do I check to see if
I've got that change?
Tim
Jeremy Katz wrote:
On Thu, 2008-02-21 at 08:54 -0700, Tim Wood wrote:
> The rawhide version.
>
Then I'd definitely check to make sure your config has a change similar
to ade8a8c33a6e3051ec9bf48d0bacdd1475a2aed5 or it will definitely blow
up.
> Is it true that when I do a git clone, I'm grabbing the head of the
> tree?
>
Yep!
Jeremy
--
Fedora-livecd-list mailing list
Fedora-livecd-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
--
_________________________________
Tim Wood, CLP, RHCT
719.338.7484 (tel)
The Data Wranglers
Web, Database & more since since 1994
www.datawranglers.com
11:56 a.m.
On Thu, 2008-02-21 at 09:46 -0700, Tim Wood wrote:
I was using the rawhide version. I'm now using one built with
git
clone/make install a day or two ago. FWIW... how do I check to see if
I've got that change?
You can either use 'git show <foo>' (where <foo> is the commit id) or
you can visit the gitweb
(http://git.fedorahosted.org/git/?p=livecd;a=summary) and put the commit
into the search box.
Jeremy
11:46 p.m.
New subject: Corrupted RPM/unbootable LiveCD problem solved
I verified the problems with a fresh install of f8 with updates (not
rawhide) and livecd-tools from git. So, I uninstalled the git version
of LiveCD Tools, disabled the development repo in YUM (LiveCD tools was
the only package enabled) and reinstalled LiveCD tools with GIT. For
some reason it choked on my RPM cache, so I've turned cacheing off for
now. I've just finished creating my second livecd under this setup (2
different kickstarts, fwiw). As an aside, I'm still receiving the same
errors on the same particular RPMs so I'm pretty convince it's not
related to RPMs.
IMVHO (I think I'm going to get blasted for this theory) it's probably
wise not to mix LiveCD tools for a future version of Fedora with a
production release of Fedora. The last time I ran into weird bad juju
with LiveCD Tools was when I mixed a git pre-release of the F8 version
of LiveCD Tools with a F7 dev vm.
Tim
12:05 a.m.
New subject: Suggestions for LiveCD Development LiveCD
I'm starting to work on a LiveCD Development LiveCD designed to create
livecd's and (if desired) burn them onto media (cd, usb, etc) ... and
... keep a light footprint.
So far, I'm working with a fork of the XFCE kickstart. I've added
livecd-tools, emacs, wget, curl, samba-client --for mounting shares with
kickstarts.
If someone has already created such a beast, please scream now ;-)
If not, I'm open to suggestions about packages to include. The obvious
ones are a good GUI text editor, an IDE and a CD/DVD burning package.
I've got favorites in each category, but none are great choices for this
situation (e.g. waaay too bloated).
In the, my bloody to-do-list has too much compost on it, I'm going to
ask people to not make suggestions about all the cool things like
firefox bookmarks that such a beast needs. My brain has definitely
already gone there and I promptly beat it with a beer ;-).
Tim
9:10 a.m.
New subject: Corrupted RPM/unbootable LiveCD problem solved
On Tue, 2008-02-26 at 22:46 -0700, Tim Wood wrote:
IMVHO (I think I'm going to get blasted for this theory) it's
probably
wise not to mix LiveCD tools for a future version of Fedora with a
production release of Fedora. The last time I ran into weird bad juju
with LiveCD Tools was when I mixed a git pre-release of the F8 version
of LiveCD Tools with a F7 dev vm.
As I've said, I really *don't* test running on "stable" releases that
often as all of my main machines run the development tree. I'm very
open to fixes for running on at least the last Fedora release, but at
the same time, it's probably going to require someone helping out and
running more often on the stable release. Because I end up doing one of
those test runs at most probably once a month. And since starting
school, not even that.
Jeremy
11:35 a.m.
New subject: Corrupted RPM/unbootable LiveCD problem solved
I am guinea pig, hear me squeak! ;-)
Tim
Jeremy Katz wrote:
On Tue, 2008-02-26 at 22:46 -0700, Tim Wood wrote:
> IMVHO (I think I'm going to get blasted for this theory) it's probably
> wise not to mix LiveCD tools for a future version of Fedora with a
> production release of Fedora. The last time I ran into weird bad juju
> with LiveCD Tools was when I mixed a git pre-release of the F8 version
> of LiveCD Tools with a F7 dev vm.
>
As I've said, I really *don't* test running on "stable" releases that
often as all of my main machines run the development tree. I'm very
open to fixes for running on at least the last Fedora release, but at
the same time, it's probably going to require someone helping out and
running more often on the stable release. Because I end up doing one of
those test runs at most probably once a month. And since starting
school, not even that.
Jeremy
--
Fedora-livecd-list mailing list
Fedora-livecd-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
--
_________________________________
Tim Wood, CLP, RHCT
719.338.7484 (tel)
The Data Wranglers
Web, Database & more since since 1994
www.datawranglers.com
12:42 p.m.
New subject: Corrupted RPM/unbootable LiveCD problem solved
Patches accepted :-) The problem is that a lot of times, it requires
really seeing the problems and sticking in debugging to fix. Sometimes
I'm psychic enough to be able to fix based on just descriptions of the
problem but sadly not often enough :-)
Jeremy
On Wed, 2008-02-27 at 10:35 -0700, Tim Wood wrote:
I am guinea pig, hear me squeak! ;-)
Tim
Jeremy Katz wrote:
> On Tue, 2008-02-26 at 22:46 -0700, Tim Wood wrote:
>
> > IMVHO (I think I'm going to get blasted for this theory) it's probably
> > wise not to mix LiveCD tools for a future version of Fedora with a
> > production release of Fedora. The last time I ran into weird bad juju
> > with LiveCD Tools was when I mixed a git pre-release of the F8 version
> > of LiveCD Tools with a F7 dev vm.
> >
>
> As I've said, I really *don't* test running on "stable" releases
that
> often as all of my main machines run the development tree. I'm very
> open to fixes for running on at least the last Fedora release, but at
> the same time, it's probably going to require someone helping out and
> running more often on the stable release. Because I end up doing one of
> those test runs at most probably once a month. And since starting
> school, not even that.
>
> Jeremy
>
> --
> Fedora-livecd-list mailing list
> Fedora-livecd-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-livecd-list
>
>
--
_________________________________
Tim Wood, CLP, RHCT
719.338.7484 (tel)
The Data Wranglers
Web, Database & more since since 1994
www.datawranglers.com
--
Fedora-livecd-list mailing list
Fedora-livecd-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
5913
days inactive
5920
days old
livecd@lists.fedoraproject.org
16 comments
3 participants
participants (3)
-
Jeremy Katz -
Orion Poplawski -
Tim Wood