Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35451 - [busybox] busybox upgrade errors
Attached to Project:
Community Packages
Opened by Geert Hendrickx (ghen) - Thursday, 23 May 2013, 20:37 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 27 May 2013, 14:21 GMT
Opened by Geert Hendrickx (ghen) - Thursday, 23 May 2013, 20:37 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 27 May 2013, 14:21 GMT
|
DetailsUpgrading community/busybox from 1.20.2-2 to 1.20.2-5 showed:
------------------------------------------------------------------------ stat: can't stat 'usr/bin/busybox': No such file or directory error: command failed to execute correctly (1/3) upgrading busybox [################################################################] 100% BusyBox v1.20.2 (2013-05-23 19:06:47 MSK) multi-call binary. Usage: chmod [-R] MODE[,MODE]... FILE... Each MODE is one or more of the letters ugoa, one of the symbols +-= and one or more of the letters rwxst -R Recurse busybox is un /usr/bin now. Readjust its mode if you modified it. ------------------------------------------------------------------------ The busybox path should probably be hardcoded if you call busybox in pre/post_upgrade with the upgrade that moves it. (do you have to use the busybox version of "chmod" and "stat" anyway?) |
This task depends upon
I don't want to implement smart logic with version checking.