[SOLVED] sudoedit: /usr/bin/sudoedit must be owned by uid 0

I tried to mount /usr from a different location in read-only mode and moved /usr from the root ext4 partition to another disk with btrfs filesystem. After I mounted it with 'ro' flag, 'sudo' and 'sudoedit' have ceased to work and return error messages when called:
sudoedit: /usr/bin/sudoedit must be owned by uid 0 and have the setuid bit set
What can be the cause of this problem?
Last edited by nbd (2015-05-14 22:32:26)

That's the problem, you're going to be missing a lot of file attributes and likely several sym links as cp does not copy these without additional flags. Read `man cp' - it's short. Also rsync would probably be a better way of copying a system.

Similar Messages

Odd /usr/bin/kill behavior

I have a Solaris 10 container that I have installed some of the blastwave programs in. Today, I installed and then attempted to stop the milter-greylist daemon which still uses the legacy rc style of initialization.
Running the shutdown script produced the following results:
bash-3.00# /etc/init.d/cswmiltergreylist stop
Shutting down milter-greylist: ... initial gids (should be 0/0): r/egid=0/0
SETUP ERROR: re-run set-group-ID guest
Use chgrp(1) and chmod(1)
For example, do this as root (nobody is the name of a group in this example):
# chgrp nobody /usr/bin/kill
# chmod g+s nobody /usr/bin/kill
done
and running /usr/bin/kill on its own resulted in this:
bash-3.00# /usr/bin/kill
initial gids (should be 0/0): r/egid=0/0
SETUP ERROR: re-run set-group-ID guest
Use chgrp(1) and chmod(1)
For example, do this as root (nobody is the name of a group in this example):
# chgrp nobody /usr/bin/kill
# chmod g+s nobody /usr/bin/kill
The size of /usr/bin/kill on this computer's global zone is different from my other Solaris 10 servers.
This host:
bash-3.00# ls -l /usr/bin/kill
-r-xr-xr-x 1 root root 7772 Feb 26 12:23 /usr/bin/kill
Another Solaris 10 host:
bash-3.00# ls -l /usr/bin/kill
-r-xr-xr-x 17 root bin 134 Jan 21 2005 /usr/bin/kill
I tried checking the md5 sum of /usr/bin/kill in the Solaris fingerprint database, but don't believe that it covers Solaris 10.
Has anyone else seen this behavior and what did you do about it?
TIA

"it seems that I accidentally installed something"... so you can't recall installing any such thing?
I can't even imagine which tool or package might replace /bin/kill..
If core system utilities suddenly change behaviour or file size, you might have a rootkit on that box. Better run a thorough check.. or reinstall.
Especially if the new file version is about fifty times as big.. that smells like it contains unexpected additional "features" now. At least compare file sizes of the other core system binaries to your other host..

[SOLVED] Freezing while executing /usr/bin/openbox from Openbox menu

I'm following the instructions in this webpage to create a dynamic menu. I have successfully achieved this on my laptop by installing the openbox-menu package and typing the following lines in menu.xml:
<menu id="desktop-app-menu" label="Applications" execute="/usr/bin/openbox-menu lxde-applications.menu" />
For some reason, the same doesn't work on my desktop PC. After editing and saving the menu.xml file, I restart Openbox and when I right click the desktop and hover the "Applications" menu item the desktop freezes. However, I can still move the mouse and switch to other ttys with Ctrl+Alt+Fx, therefore I believe it's reasonable to suggest that the problem lies in the permissions.
What should I do about it?
Last edited by Martificiam (2013-02-03 11:29:21)

Umm, that's not "some random" webpage at all... It worked on all of my Arch Linux installations. The "lxde-applications.menu" is just an argument. But thanks for the link, I'll look into it.
It's just that it's more of a workaround, not a solution, really... since it has ALWAYS worked for me.
Furthermore, while setting up Arch on my laptop I remember experiencing similar problems (running a particular program from the openbox menu and resulting in a desktop freeze). This must have something to do with permissions.
Edit: the xdg_menu worked perfectly, but I would still prefer to use the openbox-menu. I'm marking this as solved anyway.
Last edited by Martificiam (2013-02-03 11:29:06)

Make: execvp: /usr/bin: Permission denied[SOLVED]

hey, I'm trying to install an app called jconv.
I get this error:
make: execvp: /usr/bin: Permission denied
here is the make file..(don't have the first clue on making a PKGBUILD)
# Copyright (C) 2005-2007 Fons Adriaensen <[email protected]>
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
PREFIX = /usr
SUFFIX := $(shell uname -m | sed -e 's/^unknown/$//' -e 's/^i.86/$//' -e 's/^x86_64/$/64/')
LIBDIR = lib$(SUFFIX)
DISTDIR = jconv-$(VERSION)
VERSION = 0.2.0
LDFLAGS += -L$(PREFIX)/$(LIBDIR)
CPPFLAGS += -O3 -Wall -MMD -MP -DVERSION=\"$(VERSION)\"
#CPPFLAGS += -march=i686 -mtune=pentium4 -msse -msse2 -m3dnow -O3 -ffast-math
# Uncomment if you use a libsndfile version without support for setting/getting the Ambisonic flags.
CPPFLAGS += -DNOAMBIS=1
all: jconv fconv mkwavex
JCONV_O = jconv.o config.o jconfig.o jclient.o
jconv: LDLIBS += -lzita-convolver -lfftw3f -lsndfile -lclthreads -ljack -lpthread -lrt
jconv: $(JCONV_O)
g++ $(LDFLAGS) -o $@ $(JCONV_O) $(LDLIBS)
$(JCONV_O):
-include $(JCONV_O:%.o=%.d)
FCONV_O = fconv.o config.o fconfig.o
fconv: LDLIBS += -lzita-convolver -lfftw3f -lsndfile -lpthread -lrt
fconv: $(FCONV_O)
g++ $(LDFLAGS) -o $@ $(FCONV_O) $(LDLIBS)
$(FCONV_O):
-include $(FCONV_O:%.o=%.d)
MKWAVEX_O = mkwavex.o impdata.o
mkwavex : LDLIBS += -lsndfile -lrt
mkwavex: $(MKWAVEX_O)
g++ $(LDFLAGS) -o $@ $(MKWAVEX_O) $(LDLIBS)
install: jconv fconv mkwavex
/usr/bin/install -m 755 jconv $(PREFIX)/bin
/usr/bin/install -m 755 fconv $(PREFIX)/bin
/usr/bin/install -m 755 mkwavex $(PREFIX)/bin
clean:
/bin/rm -f *~ *.o *.a *.d *.so jconv fconv
Last edited by funkmuscle (2008-10-23 21:51:15)

Thanx Chok. I know that. That's why I'm posting this. This app was make for debian so it's something to do with:
install: jconv fconv mkwavex
/usr/bin/install -m 755 jconv $(PREFIX)/bin
/usr/bin/install -m 755 fconv $(PREFIX)/bin
/usr/bin/install -m 755 mkwavex $(PREFIX)/bin
solved...I removed [/usr/bin/install -m 755] and replaced with [install]
so it looked like this:
install $(PREFIX)/bin
Last edited by funkmuscle (2008-10-23 21:50:26)

Is /bin/sh must link to /usr/bin/bash?

I'm building Arch Linux on embedded system which CPU is sh4.
I found there is a problem of bash package.
It creates /bin/sh as a symbolic link to /usr/bin/bash.
But my /bin/sh is busybox.
1. I'm wonder how could I keep /bin/sh to busybox's /bin/sh? Or, it could set on pacman.conf?
2. Could my root account still use 'sh' as its shell? I wish busybox could still exist as the basement.
3. Is makepkg or yaourt based on root's shell must be bash?

Thank you Allan,
I have this question is because /usr/bin/bash require many dynamic library and I just failed login my embedded system after upgrade bash with pacman -Udd option.
Am I right of the following assumption (Sorry, I can not 100% understand your meaning, require double confirm.).
1. I can keep my root's shell as /bin/sh (it's busybox version).
2. I can config pacman to use /bin/bash for install (I've compiled brand new pacman)
3. makepkg have forced to use /bin/bash for install
BTW, I found it is required bash 4.0 (declare function) My embedded system's original linux only provide bash 3.0. So, it took me a while to prepare bash 4.0.
Last edited by dlin (2013-01-31 06:42:22)

What does this error message mean and how do I solve it? "Sorry, one or more of the following command-line tools was not found: /usr/bin/lsbom, /bin/pax, /bin/mkdir, /bin/chmod, or /usr/bin/update_prebinding."

When I try to open up this program, Pacifist, I receive this error message. Here's a screenshot. http://i.imgur.com/v717w.jpg What does this error message mean and how do I solve it?

It sounds like some of the Unix Executable commands were removed (or the permissions to those were modified) out of the /usr/bin/ folder. You can try opening disk utility and repairing permissions on Macintosh HD or you can reboot your computer and holding down option-r when it comes back up to reinstall Lion again. This will not delete your personal information or applications you have installed but it would be best to back it up to Time Machine before you do. The article on how to do this is here. (http://www.apple.com/macosx/recovery/) I have had to do this before and it works like a charm. It should fix your issue but grab a cup of coffee because its going to take about 35 - 40 minutes depending on how fast your computer is.

[solved] build failing: /usr/bin/ld: cannot find -lgd

I'm trying to satisfy crossover dependencies and recommendations. Found lib32-libgphoto2 on AUR with a few dependencies of its own, all of which I installed succesfully.
When doing a makepkg for lib32-libgphoto2 I get the following error:
libtool: link: gcc -m32 -shared -fPIC -DPIC ax203/.libs/ax203_la-library.o ax203/.libs/ax203_la-ax203.o ax203/.libs/ax203_la-ax203_decode_yuv.o ax203/.libs/ax203_la-ax203_decode_yuv_delta.o ax203/.libs/ax203_la-ax203_compress_jpeg.o ax203/.libs/ax203_la-jpeg_memsrcdest.o ax203/.libs/ax203_la-tinyjpeg.o ax203/.libs/ax203_la-jidctflt.o -Wl,-rpath -Wl,/home/someuser/Downloads/aur/lib32-libgphoto2/src/build/libgphoto2/.libs -Wl,-rpath -Wl,/home/someuser/Downloads/aur/lib32-libgphoto2/src/build/libgphoto2_port/libgphoto2_port/.libs -L/home/someuser/Downloads/aur/lib32-libgphoto2/src/build/libgphoto2_port/libgphoto2_port/.libs ../libgphoto2/.libs/libgphoto2.so -L/usr/lib32 /home/someuser/Downloads/aur/lib32-libgphoto2/src/build/libgphoto2_port/libgphoto2_port/.libs/libgphoto2_port.so -lexif ../libgphoto2_port/libgphoto2_port/.libs/libgphoto2_port.so -lltdl -lpthread -lgd -lz -lm -lpng16 -lfreetype -lfontconfig -ljpeg -m32 -march=x86-64 -mtune=generic -O2 -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-soname -Wl,ax203.so -Wl,-version-script -Wl,.libs/ax203.ver -o .libs/ax203.so
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.2/../../../libgd.so when searching for -lgd
/usr/bin/ld: skipping incompatible /usr/lib/libgd.so when searching for -lgd
/usr/bin/ld: cannot find -lgd
collect2: error: ld returned 1 exit status
Makefile:1659: recipe for target 'ax203.la' failed
make[3]: *** [ax203.la] Error 1
make[3]: Leaving directory '/home/someuser/Downloads/aur/lib32-libgphoto2/src/build/camlibs'
Makefile:3347: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/someuser/Downloads/aur/lib32-libgphoto2/src/build/camlibs'
Makefile:622: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/someuser/Downloads/aur/lib32-libgphoto2/src/build'
Makefile:444: recipe for target 'all' failed
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
In that blob of text it says 'skipping incompatible' so it found something but I don't know to fix that or find out what it needs. A search on the internet I found that the message (in title) means I'm missing 32-bit library for gd, so I pulled that from AUR and installed it, but its still giving me this message.
Any ideas what I need to do to get this to build?
Thanks in advance.
Last edited by mouseman (2014-05-05 05:24:27)

The linker tries to find libgd. so. If you build lib32-libgphoto2, I guess from the name that you are building a 32 bit package on a 64 bits installation. You should have the 32 bit version of libgd. so and you only have the 64 bit version (hence skipping incompatible /usr/lib/libgd.so). Note that I have not found this version in the multilib repository (nor on AUR), I think you will have to build it yourself.

[SOLVED]pacman: libusb-compat: /usr/bin/libusb-config exists ...

Hi,
I just installed the arch base system and did a 'pacman -S kernel26' and got some errors
error: failed to commit transaction (conflicting files)
libusb-compat: /usr/bin/libusb-config exists in filesystem
libusb-compat: /usr/include/usb.h exists in filesystem
libusb-compat: /usr/lib/libusb-0.1.so.4 exists in filesystem
libusb-compat: /usr/lib/libusb-0.1.so.4.4.4 exists in filesystem
libusb-compat: /usr/lib/libusb.a exists in filesystem
libusb-compat: /usr/lib/libusb.so exists in filesystem
libusb-compat: /usr/lib/pkgconfig/libusb.pc exists in filesystem
Errors occurred, no packages were upgraded.
this page I found on google contains error messages very similar to mine: http://pastebin.com/twGU7Yy3
any ideas?
Last edited by tgoossens (2011-08-11 17:12:32)

[SOLVED] I believe this is a related topic: https://bbs.archlinux.org/viewtopic.php?id=23774
Last edited by tgoossens (2011-08-11 17:11:52)

[SOLVED] .. error: coreutils: /usr/bin/install exists in filesystem

Hi All,
Getting the following error:
(85/85) checking for file conflicts [###########################] 100%
error: failed to commit transaction (conflicting files)
coreutils: /usr/bin/install exists in filesystem
I am reluctant to delete/move /usr/bin/install for fear of breaking the system ..
Anyone help here?
Last edited by bmentink (2012-04-05 02:26:42)

I just ran into this same issue today while performing a full system upgrade. After some investigation, I came to agree with the OP that manually removing "/usr/bin/install" is the correct action to take.
Prior to successfully executing the full system upgrade, I found that /usr/bin/install was a symlink to /bin/install. Using "pacman -Qo /bin/install", I found that the file /bin/install was owned by the coreutils 8.15-1 package. The symlink /usr/bin/install, however, was not owned by any package. The conflict arises because coreutils 8.16-2 wants to put the new install program in /usr/bin instead of its previous location under /bin.
My memory is a bit fuzzy, but I seem to recall running into a problem installing some third party library that had /usr/bin/install hard-coded into its build script and claimed the file didn't exist. I may have manually created the symlink /usr/bin/install to /bin/install as a quick-fix, then forgot to remove it. In retrospect, I could have confirmed/refuted this hypothesis by comparing the time stamp on the symlink /usr/bin/install to /bin/install. If the symlink was created well after /bin/install, then I'm probably to blaim; on the other hand, if the symlink was created essentially at the time /bin/install was created, then most likely the creators of the coreutils package forgot to claim ownership of the symlink.

[Solved] Virtualbox-source missing /usr/bin/vboxbuild

New virtualbox source missing /usr/bin/vboxbuild
i cant load my vboxdrv module & i also cant build vboxdrv module
new vbox-source 4.1.18-3 (2012-07-24) dont have vboxbuild script
anyone also have problem with this issue?
btw i use ck-kernel
Last edited by dhiika (2012-07-25 01:19:27)

xzy3186 wrote:
gbc921 wrote:
I'm also using the linux-ck from AUR and I could not load vboxdrv even after the "# dkms setup vboxhost/4.1.18"
It has compiled fine, but when I do "$ sudo rc.d start dkms" it gives me this:
:: Starting Dynamic Kernel Module System [BUSY] Error! Could not locate dkms.conf file.
File: does not exist.
ERROR: could not insert 'vboxdrv': Exec format error
ERROR: could not insert 'vboxnetadp': Exec format error
ERROR: could not insert 'vboxnetflt': Exec format error
ERROR: could not insert 'vboxpci': Exec format error
If I try to compile it again then:
$ sudo dkms install vboxhost/4.1.18
Module vboxhost/4.1.18 already installed on kernel 3.4.6-2-ck/x86_64
I have installed these packages:
community/virtualbox 4.1.18-4
community/virtualbox-additions 4.1.18-1
community/virtualbox-modules 4.1.18-4
community/virtualbox-source 4.1.18-4
aur/virtualbox-hook 1.0-3
Sincerely,
The same problem here. I compiled virtualbox-source 4.1.18-4 with "dkms install" under linux-ck-3.4.6-2 but had "ERROR: could not insert 'vboxdrv': Exec format error" whilie trying to modprobe.
Solved：According to https://bbs.archlinux.org/viewtopic.php?id=145925, I should delete "old" vboxdrv generated by vboxbuild.
Yeah! Removing the modules from /usr/lib/extramodules... and doing a depmod worked fine!
Thanks!

[SOLVED]Symlinking /bin, /sbin to /usr/bin for system update

Hello everyone,
Reading this has exposed a basic gap in my knowledge of linux ownership:
https://www.archlinux.org/news/binaries … ervention/
How is it that a directory /bin can be owned by a package contained within it, as is implied by the query option "-o" to pacman in step 1 of the above linked page?:
$ pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -
Incidentally, I get no output from this command or the others in steps 1 and 3, so it seems from reading the following that there are no packages causing problems (I'm pretty sure I don't have any packages from unofficial repositories):
https://bbs.archlinux.org/viewtopic.php?id=164505
Secondly, (and I may be completely wrong here), is it really as simple as this to move all the binaries from /bin and /sbin into /usr/bin, then create symbolic links in the root directory pointing to this new location?:
cd /
rsync -a /bin/ /usr/bin/
rsync -a /sbin/ /usr/bin/
ln -s /bin /usr/bin
ln -s /sbin /usr/bin
rm -R /bin /sbin
I use rsync -a here to preserve permissions, although I've heard that I could use tar. Is there a safer/more succinct way of doing this? And finally, I delete the original directories and their
contents last. If I were to delete them AFTER copying their contents to /usr/bin but BEFORE creating the symlinks, I would be in serious trouble, wouldn't I?
Last edited by Amp (2013-06-04 20:10:26)

If you dont have any packages that is in the wrong place you just have to follow the instructions from the front page to upgrade your system.
# pacman -Syu --ignore filesystem,bash
# pacman -S bash
# pacman -Su
No need for manual moving, deleting and symlinking.

[Solved] How to save a file in /usr/bin/local using gedit as an admin?

In my attempt to run these two programs:
https://github.com/kerchen/export_gr2evernote
https://github.com/spiermar/bookmarks2evernote
I noticed they assumed the default python is python 2. I have python 3.3.1 and 2.6.8. I'm following the instructions at: https://wiki.archlinux.org/index.php/Py … ld_scripts
Created a file with this:
#!/bin/bash
script=`readlink -f -- "$1"`
case "$script" in
/home/Dropbox/export_gr2evernote-master1/*|/home/Dropbox/bookmarks2evernote2/*)
exec python2 "$@"
esac
exec python3 "$@"
I then, tried to save it as p2 under /usr/local/bin/ where the only thing that's there is meteor, node, and npm, and it throws me an error saying I don't have enough permissions.
How do I save p2 as an admin in /usr/bin/local using gedit?
I've searched on the forums 'create a file in /usr/' and I haven't found anything. Can someone please help me?
Last edited by jjshinobi (2013-04-23 05:20:47)

jjshinobi wrote:
sidneyk wrote:
jjshinobi wrote:
I moved p2 to bin, edited my projects path with the username in front of home, saved it as python, made it executable (#sudo chmod +x /usr/local/bin/python), removed p2. Ran:
#python evernote2enex.py -m 10
It's still referencing python 3...
"python3: can't open file 'evernote2enex.py': [Errno 2] No such file or directory"
My python file contains this:
#!/bin/bash
script=`readlink -f -- "$1"`
case "$script" in
/home/<user>/Dropbox/export_gr2evernote-master1/*|/home/<user>/Dropbox/bookmarks2evernote2/*)
exec python2 "$@"
esac
exec python3 "$@"
I did everything exactly like the wiki said, what seems to be the problem?
OK. Looking at the 2 scripts you quoted, neither one is using a shbang line to set a python version to call. Without that, the python intercept doesn't even come into play. The problem that I see is the way you are starting it:
sudo nano /usr/local/bin/python
Is root really necessary for these if they are in your /home/<user>/Dropbox/ directory. And it appears that you are assuming python3 when you start them that way. If you are going to use that method and they are indeed python2 scripts, then change your command to this:
#python evernote2enex.py -m 10
You might try it as your normal user too in case root isn't really required.
I tested out the first ten with:
#python2 export2enex.py -m 10
it worked!
then proceded with
#python2 export2enex.py GStarred -n exported.enex
The script is fully functional. Thanks man!
Actually, you're not even using the script when starting your python scripts that way. You are explicitly calling either python3 (python) or python2 (python2) to run the indicated python script and not even touching the work around /usr/local/bin/python script. If your python script started with a line like either :
#!/usr/bin/env python
or:
#!/usr/bin/python
And was executable, such that you called it by it's name, i.e. "someprogram.py", then the python script in /usr/local/bin/ would take precedence and effectively intercept the python call and choose the appropriate version of python as long as the path to the directory where "someprogram.py" resides is specified in that /usr/local/bin/python script.
Last edited by sidneyk (2013-04-25 15:40:19)

[SOLVED]pacman fails to upgrade... /usr/bin/vercmp: cannot execute bin

Proceed with installation? [Y/n] y
:: Retrieving packages from core...
pacman-3.2.1-1-x86_64 491.3K 1850.7K/s 00:00:00 [########################################################################################################] 100%
checking package integrity...
(1/1) checking for file conflicts [########################################################################################################] 100%
(1/1) upgrading pacman [########################################################################################################] 100%
warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
/tmp/alpm_eT02H1/.INSTALL: line 5: /usr/bin/vercmp: cannot execute binary file
/tmp/alpm_eT02H1/.INSTALL: line 5: [: : integer expression expected
Here is more info on my system and the file vermcp is installed and permissions seem correct.
http://rafb.net/p/MYk3pO21.html
HELP?
Last edited by rooloo (2008-09-09 00:07:09)

Ok, this was my dumb mistake again. I was testing out powerpill on my server which is a 32 bit machine. I tried copying my 64 bit mirrorlist to my 32 bit server because I have it ranked and slimmed down to only the essential servers.

[SOLVED]PKGBUILD change to install to /usr/bin

I have this package installed and it needs to be changed to install to /usr/bin, now it installs to usr/sbin. I really dont know much about this so if someone could point out what i need to change i would appreciate it.
https://aur.archlinux.org/packages/?O=0 … fsarchiver
# qt4-fsarchiver by Francois Dupoux, Hihin Ruslan and Dieter Baum
# PKGBUILD by hasufell, updated by DaarkWel
pkgname=qt4-fsarchiver
pkgver=0.6.17_3
pkgrel=1
pkgdesc='GUI for fsarchiver'
arch=('i686' 'x86_64')
url='http://sourceforge.net/projects/qt4-fsarchiver/'
license=('GPL')
depends=('fsarchiver' 'gksu')
makedepends=('qt4')
source=("http://sourceforge.net/projects/${pkgname}/files/source/${pkgname}-${pkgver//_/-}.tar.gz")
sha1sums=('8b474af6fd81d604f357348567608f450dbe83e7')
build() {
cd "${srcdir}/${pkgname}"
qmake-qt4
package() {
cd "${srcdir}/${pkgname}"
make
make INSTALL_ROOT="${pkgdir}" install
mkdir -p ${pkgdir}/usr/share/qt/translations
rm -R ${pkgdir}/usr/share/qt4
install -D -m644 ${srcdir}/${pkgname}/translations/*.qm ${pkgdir}/usr/share/qt/translations
sed s/Terminal=true/Terminal=false/ -i ${pkgdir}/usr/share/applications/qt4-fsarchiver.desktop
sed s/sudo/gksu/ -i ${pkgdir}/usr/share/applications/qt4-fsarchiver.desktop
Last edited by cecar (2013-06-04 13:22:28)

There is a problem in that PKGBUILD. The make shouldn't be in the package function. It should be in the build function, just after qmake-qt4.
And the qmake project hard codes the destination to /usr/sbin. In that case, the correct PKGBUILD should be:
# qt4-fsarchiver by Francois Dupoux, Hihin Ruslan and Dieter Baum
# PKGBUILD by hasufell, updated by DaarkWel
pkgname=qt4-fsarchiver
pkgver=0.6.17_3
pkgrel=1
pkgdesc='GUI for fsarchiver'
arch=('i686' 'x86_64')
url='http://sourceforge.net/projects/qt4-fsarchiver/'
license=('GPL')
depends=('fsarchiver' 'gksu')
makedepends=('qt4')
source=("http://sourceforge.net/projects/${pkgname}/files/source/${pkgname}-${pkgver//_/-}.tar.gz")
sha1sums=('8b474af6fd81d604f357348567608f450dbe83e7')
build() {
cd "${srcdir}/${pkgname}"
qmake-qt4
make
package() {
cd "${srcdir}/${pkgname}"
make INSTALL_ROOT="${pkgdir}" install
mkdir -p ${pkgdir}/usr/share/qt/translations
rm -R ${pkgdir}/usr/share/qt4
install -D -m644 ${srcdir}/${pkgname}/translations/*.qm ${pkgdir}/usr/share/qt/translations
# workaround for fixed destination path in qmake project
mkdir -p ${pkgdir}/usr/bin
mv ${pkgdir}/usr/sbin/qt4-fsarchiver ${pkgdir}/usr/bin/
rmdir ${pkgdir}/usr/sbin
sed s/Terminal=true/Terminal=false/ -i ${pkgdir}/usr/share/applications/qt4-fsarchiver.desktop
sed s/sudo/gksu/ -i ${pkgdir}/usr/share/applications/qt4-fsarchiver.desktop

[SOLVED] /usr/bin/env: No such file or directory

Hi,
I've tried to install a couple packages from the AUR, but when I run "makepkg -s", I get this error:
/usr/bin/env: No such file or directory
make: *** [install] Error 127
==> ERROR: A failure occurred in package().
Aborting...
I'm sorry if this is something terribly simple, but I can't find any mention of /usr/bin/env anywhere.
I have coreutils installed, which I believe env is part of.
Thank you for any help!
Last edited by dluco (2013-09-24 01:37:11)

The /usr/bin/env is provided by the coreutils package.
You didn't run into issues when there was the move from /bin, /sbin, /usr/sbin → /usr/bin ? This happened back in the beginning of June! You need to read the front page news.
If this is the case, I am venturing to guess that your system is probably not actually up to date, and even that you might have been doing partial updates for some time now…
Edit: Check /bin, /sbin, and /usr/sbin and see if they are symlinks pointing to /usr/bin. If they are, you apparently made it through that update unscathed. If they are not, well…
Last edited by WonderWoofy (2013-09-23 16:25:19)

[SOLVED] sudoedit: /usr/bin/sudoedit must be owned by uid 0

Similar Messages

Maybe you are looking for