after upgrade makepkg aborts. How to debug it ?

warped · 2010-10-12 07:37:47

Hi,
After 6 months of operation I decided to upgrade whole system (pacman -Syu).

All went OK, but after upgrade I started to have issues with building my packages:
running makepkg on some packages start to give me "==>Aborting" without any error code or hint what is wrong.

Place where makepkg aborts is constant but changes when I'm commenting lines in BUILDPKG file.

How can I enable debugging in makepkg for finding what is wrong ?

BTW: pacman.conf is marged. --nocolour not helping.

br

Allan · 2010-10-12 08:24:03

Your PKGBUILD is probably wrong and not makepkg... Something in your PKGBUILD is returning non-zero. Build with MAKEFLAGS="-j1" and it should hopefully become clearer what the error is. Otherwise, post output or the PKGBUILD here.

tomk · 2010-10-12 08:41:16

warped wrote:

After 6 months of operation I decided to upgrade whole system (pacman -Syu).

Off-topic advice: Arch is designed to be updated regularly and frequently.

karol · 2010-10-12 10:15:56

Have you taken care of any .pacnew files after the update? Are you using BUILDPKG or PKGBUILD files? ;P

warped · 2010-10-12 11:17:49

Allan wrote:

Your PKGBUILD is probably wrong and not makepkg... Something in your PKGBUILD is returning non-zero. Build with MAKEFLAGS="-j1" and it should hopefully become clearer what the error is. Otherwise, post output or the PKGBUILD here.

Allan,

Thx. I'll do that when return to home.
I'm curious: why before upgrade all was OK ?

br

BTW: Having You here - I want to ask question related to compatibility between Arch and other distros ?

I'm using app which has its own kernel module.
App uses buffers for data communication and has hardcoded limit for buffers declaration at 20M.
Many people using 16M buffers without problems on Fedora, Ubuntu, etc.
With Arch - at 2.6.33 kernel times I was able to declare max 9M (above that app crashes during operation).
With Arch on 2.6.35 level - I can declare only 6M.
May You hint me where should I tweak Arch build options for achieve better compability ?

thx and sorry for forking dicussion !

Last edited by warped (2010-10-12 11:26:24)

wonder · 2010-10-12 11:20:12

because of : http://projects.archlinux.org/pacman.git/tree/NEWS#n43

- automatically aborts on any errors during packaging

warped · 2010-10-12 11:39:08

wonder wrote:

because of : http://projects.archlinux.org/pacman.git/tree/NEWS#n43
- automatically aborts on any errors during packaging

Thx for replay.

I'm little wonder how You define "errors".
My building script was working OK for months before upgrade. There is clear correlation between upgrade and issue.
I'll do what Allan suggests and we will see.
Thx for You help.

warped · 2010-10-12 11:42:56

tomk wrote:

warped wrote:
After 6 months of operation I decided to upgrade whole system (pacman -Syu).
Off-topic advice: Arch is designed to be updated regularly and frequently.

Thx for replay.

Pls see my question to Allan in this thread - this probably little explains why I'm so conservative.
System in question is home 24/7 server doing MANY things, so stability is important for me.
br

flamelab · 2010-10-12 11:45:11

Can you please post one of these PKGBUILDs here in order to test them as well ?

Stebalien · 2010-10-12 11:48:28

warped wrote:

I'm little wonder how You define "errors".
My building script was working OK for months before upgrade. There is clear correlation between upgrade and issue.
I'll do what Allan suggests and we will see.
Thx for You help.

Anything that returns a non-zero exit status is considered an error. If you want to ignore an error, append "|| return 0" to the end of the offending line.

warped · 2010-10-12 18:53:14

Allan wrote:

Your PKGBUILD is probably wrong and not makepkg... Something in your PKGBUILD is returning non-zero. Build with MAKEFLAGS="-j1" and it should hopefully become clearer what the error is. Otherwise, post output or the PKGBUILD here.

Allan,

It looks like now makepkg is aborting on any non-zero ret code for interpreted lines with shell commands.
I modify my PKGBUILD for any non-important shell command line it will return 0 and it works again.
Modifying makepkg tool in a way where for any non-zero ret code it will print interpreted line and ret code for that line might be really helpful in writing PKGBUILD scripts.

thx for Your help

anonymous_user · 2010-10-13 06:52:18

warped wrote:

System in question is home 24/7 server doing MANY things, so stability is important for me.

*cough*Debian*cough*

warped · 2010-10-13 08:41:04

anonymous_user wrote:

warped wrote:
System in question is home 24/7 server doing MANY things, so stability is important for me.
*cough*Debian*cough*

Well. I was 4 years with Debian. Indeed - stability is king. But with price of long long delay between upstreamers and OS. At some point of time I was forced to add app which requires v.latest kernel. It was pain due big mismatch between newest kernel and 2-years old surrounding OS parts. I decided to give try for Arch. Surprisingly results were better than expected: Currently I have 1 year 24/7 operation WITHOUT single trap or other issue derived from fact that Arch is rolling release and Debian is v.conservative milestoned distro. Right - I'm walking on thin ice. But once You receive stable packages combination - if You will carefully do upgrades - You can have stability almost comparable with Debian - but without Debian's lag in time....

Arch Linux

#1 2010-10-12 07:37:47

after upgrade makepkg aborts. How to debug it ?

#2 2010-10-12 08:24:03

Re: after upgrade makepkg aborts. How to debug it ?

#3 2010-10-12 08:41:16

Re: after upgrade makepkg aborts. How to debug it ?

#4 2010-10-12 10:15:56

Re: after upgrade makepkg aborts. How to debug it ?

#5 2010-10-12 11:17:49

Re: after upgrade makepkg aborts. How to debug it ?

#6 2010-10-12 11:20:12

Re: after upgrade makepkg aborts. How to debug it ?

#7 2010-10-12 11:39:08

Re: after upgrade makepkg aborts. How to debug it ?

#8 2010-10-12 11:42:56

Re: after upgrade makepkg aborts. How to debug it ?

#9 2010-10-12 11:45:11

Re: after upgrade makepkg aborts. How to debug it ?

#10 2010-10-12 11:48:28

Re: after upgrade makepkg aborts. How to debug it ?

#11 2010-10-12 18:53:14

Re: after upgrade makepkg aborts. How to debug it ?

#12 2010-10-13 06:52:18

Re: after upgrade makepkg aborts. How to debug it ?

#13 2010-10-13 08:41:04

Re: after upgrade makepkg aborts. How to debug it ?

Board footer