Problems with pacbuilder-svn

Yes · 2008-12-13 20:26:24

I'm having some problems getting pacbuilder to work. I ran pacbuilder --core --builddeps --verbose, and every package failed with 'makepkg failed!', because it didn't have the permission to make the temp build directory. Then I tried running sudo pacbuilder --core --builddeps --verbose, and every package failed again with 'makepkg failed!'. This time, it was because makepkg didn't want to be run as root. Am I doing something wrong?

Thanks!

kras1001 · 2008-12-20 17:29:01

After start pacbuilder --clean i can't use pacbuilder?

[kras@DALAVERA pacbuilder-svn]$ sudo pacbuilder --builddeps --keepdeps --verbose --noconfirm gparted
-------------------------------
PacBuilder, by Andrea Cimitan
-------------------------------
[kras@DALAVERA pacbuilder-svn]$

Xyne · 2008-12-20 18:32:48

I'm guessing that "sudo pacbuilder --clean" will remove /tmp/pacbuilder so that you can re-run it without "sudo" to re-create the directory with the proper permissions. If you've run "sudo pacbuilder --clean" followed by "sudo pacbuilder --whatever", you've presumably negated the "--clean", which your post indicates.

Yes · 2008-12-20 19:35:20

Ah, there we go. Most of them installed fine.

A weird problem, though - binutils won't install because it needs a newer version of glibc, glibc won't install because it needs a newer version of gcc, and gcc won't install because it needs a newer version of binutils. How am I supposed to get around this?

methuselah · 2008-12-20 23:06:13

Yes wrote:

Ah, there we go. Most of them installed fine.
A weird problem, though - binutils won't install because it needs a newer version of glibc, glibc won't install because it needs a newer version of gcc, and gcc won't install because it needs a newer version of binutils. How am I supposed to get around this?

What I do is I use the regular "pacman -Sy" to install the packages, and then rebuild them all with "pacbuilder -Sbkv binutils glibc gcc" afterwards. Sometimes I run into some packages that won't build.... If I can't fix the problem with the edit "-e" option then I just use the binary.

For those packages above I was only able to rebuild "binutils".

Sometimes a package will build correctly but won't replace the old version..... or it won't replace and remove the different package it is replacing (esound for esd did this a few weeks back). So I use regular pacman because it will ask if I want to remove the old version/different version and replace it with the new package or version..... then I just re-build the new package/version using pacbuilder and it usually works perfectly that way.

Last edited by methuselah (2008-12-20 23:07:55)

kras1001 · 2008-12-21 06:27:23

Xyne wrote:

I'm guessing that "sudo pacbuilder --clean" will remove /tmp/pacbuilder so that you can re-run it without "sudo" to re-create the directory with the proper permissions. If you've run "sudo pacbuilder --clean" followed by "sudo pacbuilder --whatever", you've presumably negated the "--clean", which your post indicates.

You are right, I "sudo pacbuilder --clean", try to change dir permision from KDE and now:

[kras@DALAVERA pacbuilder-svn]$ pacbuilder --builddeps --keepdeps --verbose --noconfirm --install opera
-------------------------------
PacBuilder, by Andrea Cimitan
-------------------------------
The following packages will be built:
==> opera
==> Building opera [package 1 of 1] ...
==> Making package: opera 9.63-1 i686 (Sun Dec 21 07:59:46 PST 2008)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
mkdir: cannot create directory `/tmp/pacbuilder/build/opera/src': Permission denied
==> ERROR: An unknown error has occured. Exiting...
==> Installing opera-9.63-1-i686.pkg.tar.gz [package 1 of 1] ...makepkg failed!
==> ERROR: I was unable to install these packages: opera

What to do now?

methuselah · 2008-12-21 11:09:31

kras1001 wrote:

Xyne wrote:
I'm guessing that "sudo pacbuilder --clean" will remove /tmp/pacbuilder so that you can re-run it without "sudo" to re-create the directory with the proper permissions. If you've run "sudo pacbuilder --clean" followed by "sudo pacbuilder --whatever", you've presumably negated the "--clean", which your post indicates.
You are right, I "sudo pacbuilder --clean", try to change dir permision from KDE and now:
[kras@DALAVERA pacbuilder-svn]$ pacbuilder --builddeps --keepdeps --verbose --noconfirm --install opera
-------------------------------
PacBuilder, by Andrea Cimitan
-------------------------------
The following packages will be built:
==> opera
==> Building opera [package 1 of 1] ...
==> Making package: opera 9.63-1 i686 (Sun Dec 21 07:59:46 PST 2008)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
mkdir: cannot create directory `/tmp/pacbuilder/build/opera/src': Permission denied
==> ERROR: An unknown error has occured. Exiting...
==> Installing opera-9.63-1-i686.pkg.tar.gz [package 1 of 1] ...makepkg failed!
==> ERROR: I was unable to install these packages: opera
What to do now?

Pacbuilder can not make a directory in the /tmp/pacbuilder/build unless it has root permission.

I know people say that you shouldn't build a package in root...... but I just use "sudo pacbuilder" for everything..... I guess you could make a different directory to build in so that you could build as a non-root user.... check into the /etc/pacbilder.conf file.

Yes · 2008-12-21 21:54:01

Ok, I guess I'll just use pacman then for those packages.

pacbuilder's been working on libmp4v2 for about two hours now, is that normal?

methuselah · 2008-12-21 23:28:51

Yes wrote:

Ok, I guess I'll just use pacman then for those packages.
pacbuilder's been working on libmp4v2 for about two hours now, is that normal?

I'm not an expert with building packages or anything.... but 2 hours seems long. What sort of processor do you have, and have you edited your /etc/makepkg.conf to match: http://wiki.archlinux.org/index.php/Makepkg.conf

For C[XX]FLAGS: http://wiki.archlinux.org/index.php/Mak … chitecture
For MAKEFLAGS: http://wiki.archlinux.org/index.php/Mak … #MAKEFLAGS

Yes · 2008-12-21 23:43:11

It's an Intel E6550. I've just got "-j3" for MAKEFLAGS and "-march=prescott -O2 -pipe -fomit-frame-pointer" for C[XX]FLAGS. I don't think it's a problem with that stuff though because I've already compiled about 300 packages today.

It's been working on libmp4v2 for at least four hours now. According to top, something's using 50% of my CPU, but it only lists configure as using about 6. So I guess it's still doing something

methuselah · 2008-12-22 00:29:21

Yes wrote:

It's an Intel E6550. I've just got "-j3" for MAKEFLAGS and "-march=prescott -O2 -pipe -fomit-frame-pointer" for C[XX]FLAGS. I don't think it's a problem with that stuff though because I've already compiled about 300 packages today.
It's been working on libmp4v2 for at least four hours now. According to top, something's using 50% of my CPU, but it only lists configure as using about 6. So I guess it's still doing something

Yeah, if you have makepkg.conf configured like that then I'm not sure why it would be over 2 hours..... I have has some apps that take a long time.... I never have had 1 package build for 2 hours though. Sorry I can't help.

Yes · 2008-12-22 01:07:49

Ugh, this might be a problem. Is there anyway to exclude it from the list? So I could stop, then try rebuilding extra again without libmp4v2?

Arch Linux

#1 2008-12-13 20:26:24

Problems with pacbuilder-svn

#2 2008-12-20 17:29:01

Re: Problems with pacbuilder-svn

#3 2008-12-20 18:32:48

Re: Problems with pacbuilder-svn

#4 2008-12-20 19:35:20

Re: Problems with pacbuilder-svn

#5 2008-12-20 23:06:13

Re: Problems with pacbuilder-svn

#6 2008-12-21 06:27:23

Re: Problems with pacbuilder-svn

#7 2008-12-21 11:09:31

Re: Problems with pacbuilder-svn

#8 2008-12-21 21:54:01

Re: Problems with pacbuilder-svn

#9 2008-12-21 23:28:51

Re: Problems with pacbuilder-svn

#10 2008-12-21 23:43:11

Re: Problems with pacbuilder-svn

#11 2008-12-22 00:29:21

Re: Problems with pacbuilder-svn

#12 2008-12-22 01:07:49

Re: Problems with pacbuilder-svn

Board footer