livecd-creator failed

[Danishka Navin]

I was trying to build my livecd but it giving following error
http://fpaste.org/tueY/

[Bruno Wolff III]

On Fri, Feb 26, 2010 at 21:59:41 +0530,
  Danishka Navin  wrote:
> I was trying to build my livecd but it giving following error
> http://fpaste.org/tueY/

It looks like there may have been a corrupted package at the rpmfusion
mirror you pulled from.

[Julian Aloofi]

Am 26.02.2010 17:29, schrieb Danishka Navin:
> I was trying to build my livecd but it giving following error
> http://fpaste.org/tueY/

I have encountered this error myself several times now, and I also know
that others had it as well (at least two reported cases on IRC).
This seems to be some mysterious livecd-creator bug that is floating
around since F11 now (at least as far as I know).

I haven't bothered reporting it yet, because it is in fact almost
impossible to reproduce. Rebooting and a rm -rf / on the tempdir you
chose should generally solve the problem (if you're lucky…)

[Danishka Navin]

On Fri, Feb 26, 2010 at 10:26 PM, Julian Aloofi <
[e-mail]> wrote:
> Am 26.02.2010 17:29, schrieb Danishka Navin:
> > I was trying to build my livecd but it giving following error
> > http://fpaste.org/tueY/
>
> I have encountered this error myself several times now, and I also know
> that others had it as well (at least two reported cases on IRC).
> This seems to be some mysterious livecd-creator bug that is floating
> around since F11 now (at least as far as I know).
>
> I haven't bothered reporting it yet, because it is in fact almost
> impossible to reproduce. Rebooting and a rm -rf / on the tempdir you
> chose should generally solve the problem (if you're lucky…)

no luck with removing the tmp/
> spins mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/spins

[Danishka Navin]

another issue
didn't select soprano, R-core packages...

http://fpaste.org/80tP/

On Sat, Feb 27, 2010 at 2:55 PM, Danishka Navin  wrote:
> On Fri, Feb 26, 2010 at 10:26 PM, Julian Aloofi <
> [e-mail]> wrote:
> > Am 26.02.2010 17:29, schrieb Danishka Navin:
> > > I was trying to build my livecd but it giving following error
> > > http://fpaste.org/tueY/
> >
> > I have encountered this error myself several times now, and I also know
> > that others had it as well (at least two reported cases on IRC).
> > This seems to be some mysterious livecd-creator bug that is floating
> > around since F11 now (at least as far as I know).
> >
> > I haven't bothered reporting it yet, because it is in fact almost
> > impossible to reproduce. Rebooting and a rm -rf / on the tempdir you
> > chose should generally solve the problem (if you're lucky…)
>
> no luck with removing the tmp/
> > spins mailing list
> > [e-mail]
> > https://admin.fedoraproject.org/mailman/listinfo/spins
>
> --
> Danishka Navin
> http://danishkanavin.blogspot.com

[Salvadesswaran P.S.]

This error is in most cases due to rpm files being corrupt. Do you
build against a local repo? Then I'd suggest rsyncing against a nearby
mirror. I had this issue sometime back, and the root of the problem
was that many rpms were zero byte files due to some FS problem. I
rsynced after deleting those corrupt files. All works fine now.

[Danishka Navin]

right now running the build without local repo.
 up to now no issue at all.

On Sat, Feb 27, 2010 at 6:26 PM, Salvadesswaran P.S. <
[e-mail]> wrote:
> This error is in most cases due to rpm files being corrupt. Do you
> build against a local repo? Then I'd suggest rsyncing against a nearby
> mirror. I had this issue sometime back, and the root of the problem
> was that many rpms were zero byte files due to some FS problem. I
> rsynced after deleting those corrupt files. All works fine now.
>
> --
>
> Salvadesswaran Srinivasan
>
> http://www.twitter.com/salva_eswar
> http://queasyquagmire.wordpress.com
> _______________________________________________
> spins mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/spins

[Salvadesswaran P.S.]

On Sat, Feb 27, 2010 at 6:29 PM, Danishka Navin  wrote:
> right now running the build without local repo.
>  up to now no issue at all.

Just check if all files are intact. Trust me, it (hard drive problem)
happens when least expected.