From: Harald Schioeberg <schioebe@net.in.tum.de>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] unknown problem with portage
Date: Thu, 15 Jun 2006 11:14:25 +0200 [thread overview]
Message-ID: <449124F1.9030107@net.in.tum.de> (raw)
In-Reply-To: <200606151035.51309.ladmanj@volny.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Just an idea:
is ROOT an nfs-mount? linux nfs filelocking is badly broken, the only
thing i can tell you: try different nfs-versions, mount-options et all.
Harald
Jakub Ladman wrote:
> Hello
> I have encountered this problem while emerging anything for my embedded
> system.
> Do you have any recomendation how to fix it?
>
> Thank you
> Jakub Ladman
>
>>>> Original instance of package unmerged safely.
> Traceback (most recent call last):
> File "/usr/bin/emerge", line 3505, in ?
> mydepgraph.merge(pkglist)
> File "/usr/bin/emerge", line 2016, in merge
> retval=portage.pkgmerge(mytbz2,myroot,self.pkgsettings)
> File "/usr/lib/portage/pym/portage.py", line 6824, in pkgmerge
> mylink.merge(pkgloc, infloc, myroot, myebuild, cleanup=1,
> prev_mtimes=prev_mtimes)
> File "/usr/lib/portage/pym/portage.py", line 6693, in merge
> cleanup=cleanup, mydbapi=mydbapi, prev_mtimes=prev_mtimes)
> File "/usr/lib/portage/pym/portage.py", line 6361, in treewalk
> mylock = portage_locks.lockfile(os.path.join(destroot,
> CONFIG_MEMORY_FILE))
> File "/usr/lib/portage/pym/portage_locks.py", line 91, in lockfile
> fcntl.lockf(myfd,fcntl.LOCK_EX|fcntl.LOCK_NB)
> IOError: [Errno 37] No locks available
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
iD8DBQFEkSTxJgyxs71kcx4RArAzAKDjPO1xnsm6JB05EJmae9h4osa4mwCgypkx
8BEArWOX/LRNfb55VHTeVyA=
=Pn3s
-----END PGP SIGNATURE-----
--
gentoo-embedded@gentoo.org mailing list
prev parent reply other threads:[~2006-06-15 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 8:35 [gentoo-embedded] unknown problem with portage Jakub Ladman
2006-06-15 9:14 ` Harald Schioeberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=449124F1.9030107@net.in.tum.de \
--to=schioebe@net.in.tum.de \
--cc=gentoo-embedded@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox