From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@uclibc.org
Subject: [Buildroot] Is there a working version of opkg?
Date: Tue, 1 Apr 2025 19:50:57 -0000 (UTC) [thread overview]
Message-ID: <vshg31$ei0$1@ciao.gmane.io> (raw)
Does anybody know of a working verison of opkg? I've tried 0.6.2 and
0.7.0, and both versions have a file-locking bug. The basic 'opkg'
utility appears to fork off multiple children (WHY?!?!?) which then
collide with each other when trying to lock /var/log/opkg.lock.
It can be plainly seen using strace, but to make it a little more
obvious, I added fprintf() calls to opkg_lock/unlock:
# opkg install --force-reinstall --force-downgrade <foo>.opk
PID 843 PPID 696 opkg_lock()
Installing <foo> on apps.
beginning preinst...
PID 846 PPID 844 opkg_lock()
error: opkg_lock: Could not lock /var/run/opkg.lock: Resource temporarily unavailable.
error: opkg_cmd_exec: Command failed to capture privilege lock: Resource temporarily unavailable.
ending preinst.....
Configuring web-server.
beginning postinst...
starting /apps/webserver...
ending postinst...
PID 843 PPID 696 opkg_unlock()
If found some old threads discussing the addition of waits/retries
when acquiring that lock but that "solution" was apparently rejected
in favor of just leaving it broken.
--
Grant
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2025-04-01 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 19:50 Grant Edwards [this message]
2025-04-01 20:18 ` [Buildroot] Is there a working version of opkg? Grant Edwards
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='vshg31$ei0$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@uclibc.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