Improve AUR quality - automated testing of all packages

Spider.007 · 2008-11-30 20:42:11

As the subject states, I think the quality of the AUR-packages could be improved; and automated testing is probably an idea that might work. Which is why I have spend some days creating a script and website.

http://archlinux.spider007.net/AurBuild/index

The next step is to improve the AUR and fix the unmaintained packages. Do you guys like the idea of testing the AUR packages automatically?

Xyne · 2008-11-30 20:45:18

Interesting idea, but how could you possibly handle the load of downloading and compiling everything?

Spider.007 · 2008-11-30 20:52:42

The number of packages that are updated aren't that enormous. As you can see I have already compiled quite a few packages. I do however agree that the load might be too big of an issue for this to be a near-realtime view. Maybe updating only once a month would be a solution

Army · 2008-11-30 21:12:18

This is really cool! What about running namcap over them and checking, if dependencies are okay? And what about makedeps, do you have the ability to check them too?

fwojciec · 2008-11-30 21:17:16

Spider.007 wrote:

As the subject states, I think the quality of the AUR-packages could be improved; and automated testing is probably an idea that might work. Which is why I have spend some days creating a script and website.
http://archlinux.spider007.net/AurBuild/index
The next step is to improve the AUR and fix the unmaintained packages. Do you guys like the idea of testing the AUR packages automatically?

Very cool. Bu the system that builds/checks AUR packages doesn't seem to have [community] repo enabled, both of my packages that I checked failed because they couldn't resolve a dependency that's in community repo.

Spider.007 · 2008-11-30 21:41:01

fwojciec wrote:

Spider.007 wrote:
As the subject states, I think the quality of the AUR-packages could be improved; and automated testing is probably an idea that might work. Which is why I have spend some days creating a script and website.
http://archlinux.spider007.net/AurBuild/index
The next step is to improve the AUR and fix the unmaintained packages. Do you guys like the idea of testing the AUR packages automatically?
Very cool. Bu the system that builds/checks AUR packages doesn't seem to have [community] repo enabled, both of my packages that I checked failed because they couldn't resolve a dependency that's in community repo.

Good point, I will add it soon; so the next run we'll see if it works

Army wrote:

This is really cool! What about running namcap over them and checking, if dependencies are okay? And what about makedeps, do you have the ability to check them too?

Well; that's what the 'package validation' button does; but I haven't decided yet on how to interpret the results. About the makedepends; they are checked as well (if everything is working like it should )

Last edited by Spider.007 (2008-11-30 21:42:46)

haxit · 2008-11-30 22:32:11

Very cool idea.

godane · 2008-11-30 23:14:05

This is a very good idea.

BTW, I was checking my old kernel26livecd package and there was a error that shouldn't be there.

PKGBUILD: line 56: patch: command not found

i think you need to add patch package into the build system your using. This bug could make a lot package not compile when it just needs to patch something to work build right.

Just my 2 cents.

EDIT1: I think you save on bandwidth if you just delete the pkg and src folder. But you will need a lot of diskspace and make sure that when you version comes out you delete the older source code. That could make it possible to do this every week instead of every month.

Again Just my 2 cents.

EDIT2: I look up my italc package thats at 1.0.9. The build error is for 1.0.7 on june 17th. I just thinking its odd since i thought you site was new. (At least in the last month new if anything else.)

2008-06-17 06:17:42 (760 KB/s) - `italc-1.0.7.tar.bz2' saved [2522087/2522087]

  -> Found italc in build dir
  -> Found help.txt in build dir
  -> Found italc.png in build dir
==> Validating source files with md5sums...
    italc-1.0.7.tar.bz2 ... Passed
    italc ... Passed
    help.txt ... Passed
    italc.png ... Passed
==> Extracting Sources...
  -> bsdtar -x -f italc-1.0.7.tar.bz2
==> Entering fakeroot environment...
==> Starting build()...
==> ERROR: Build Failed.
    Aborting...

This was like the end of the log but you see what i mean.

I hope this helps.

Last edited by godane (2008-11-30 23:29:32)

Allan · 2008-12-01 00:20:25

godane wrote:

This is a very good idea.
BTW, I was checking my old kernel26livecd package and there was a error that shouldn't be there.
PKGBUILD: line 56: patch: command not found
i think you need to add patch package into the build system your using. This bug could make a lot package not compile when it just needs to patch something to work build right.

Yeah, you should probably have base and base-devel installed in the build environment.

BTW, Great job!

godane · 2008-12-01 00:40:37

Allan wrote:

Yeah, you should probably have base and base-devel installed in the build environment.
BTW, Great job!

wget is also missing from your build environment too.

==> Making package: arch-bubble-icons 0.3.4-1 i686 (Sun Nov 30 19:54:42 UTC 2008)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
==> ERROR: The download program wget is not installed.
    Aborting...
  -> Downloading arch-bubble-icons-0.3.4.tar.gz...
/usr/bin/makepkg: line 320: http://www.xs4all.nl/~gforce/arch-bubble-icons/arch-bubble-icons-0.3.4.tar.gz: No such file or directory
==> ERROR: Failure while downloading arch-bubble-icons-0.3.4.tar.gz
    Aborting...

So it is not just patch package missing.

EDIT: There is alot of packages in not_build selection that need wget. It not just arch-bubble-icons. So I'm even having trouble how you could get anything to build right without wget in it. Inless the source is in AUR i don't see how you could have 2700+ packages build right without using wget.

Last edited by godane (2008-12-01 00:46:16)

creslin · 2008-12-01 00:53:24

godane wrote:

EDIT2: I look up my italc package thats at 1.0.9. The build error is for 1.0.7 on june 17th.

I noticed this as well. The front page says that it takes daily AUR snapshots, but it seems to have quite a few old pkgver/pkgrel builds. I found several packages on the list of failed builds that I personally adopted and fixed a few weeks back, but it's still showing the old builds.

Maybe it doesn't purge old failed builds even after a newer fixed version/release gets submitted? Cool idea and great work though.

Last edited by creslin (2008-12-01 02:43:24)

Daenyth · 2008-12-01 03:00:27

Not terribly relevent, but you should note that an "aurbuild" thing already exists..

More relevent: How do you keep things secure? I wouldn't even trust a chroot, I'd go with a full virtualized system.

Spider.007 · 2008-12-01 08:53:44

Well, as you might imagine I didn't compile 2500 packages in a single day; this implementation has been lying around for a while; and I only posted it when it was in a bit more workable state.

I also added wget to the chroot, but I am unsure about adding the full base group. Shouldn't every PKGBUILD specify the actual packages they require; even if those packages are in base?

Daenyth wrote:

[...]
More relevent: How do you keep things secure? I wouldn't even trust a chroot, I'd go with a full virtualized system.

Shouldn't users be able to trust packages that exist in the AUR?

Last edited by Spider.007 (2008-12-01 08:56:37)

Allan · 2008-12-01 08:55:11

The general guidlelines are that base and base-devel are assumed while building packages, although there is no harm adding these specifically. My build chroot is created with base, base-devel and sudo.

Dieter@be · 2008-12-01 09:16:58

Spider.007 wrote:

Shouldn't users be able to trust packages that exist in the AUR?

No! It's technically possible that people put infected/malicious code online. It's easy to do. That's why I always check the pkgbuild/.install files and preferably look at the source code before installing a package from AUR

Xyne · 2008-12-01 18:58:55

AUR wrote:

DISCLAIMER: Unsupported PKGBUILDs are user produced content, by downloading them you agree to do so at your own risk.

I also remember reading somewhere that you should check every single PKGBUILD that you download for malicious code.

Army · 2008-12-01 22:52:23

You don't have to read this, it should be enouth to think for a moment

Xyne · 2008-12-02 16:45:16

Sure, but the point was that it's stated several times in different places.

doorknob60 · 2008-12-09 04:49:53

Nice, both my packages build succesfully Fixing the namcap errors in fretsonfire-alarian-mod ATM too.

Arch Linux

#1 2008-11-30 20:42:11

Improve AUR quality - automated testing of all packages

#2 2008-11-30 20:45:18

Re: Improve AUR quality - automated testing of all packages

#3 2008-11-30 20:52:42

Re: Improve AUR quality - automated testing of all packages

#4 2008-11-30 21:12:18

Re: Improve AUR quality - automated testing of all packages

#5 2008-11-30 21:17:16

Re: Improve AUR quality - automated testing of all packages

#6 2008-11-30 21:41:01

Re: Improve AUR quality - automated testing of all packages

#7 2008-11-30 22:32:11

Re: Improve AUR quality - automated testing of all packages

#8 2008-11-30 23:14:05

Re: Improve AUR quality - automated testing of all packages

#9 2008-12-01 00:20:25

Re: Improve AUR quality - automated testing of all packages

#10 2008-12-01 00:40:37

Re: Improve AUR quality - automated testing of all packages

#11 2008-12-01 00:53:24

Re: Improve AUR quality - automated testing of all packages

#12 2008-12-01 03:00:27

Re: Improve AUR quality - automated testing of all packages

#13 2008-12-01 08:53:44

Re: Improve AUR quality - automated testing of all packages

#14 2008-12-01 08:55:11

Re: Improve AUR quality - automated testing of all packages

#15 2008-12-01 09:16:58

Re: Improve AUR quality - automated testing of all packages

#16 2008-12-01 18:58:55

Re: Improve AUR quality - automated testing of all packages

#17 2008-12-01 22:52:23

Re: Improve AUR quality - automated testing of all packages

#18 2008-12-02 16:45:16

Re: Improve AUR quality - automated testing of all packages

#19 2008-12-09 04:49:53

Re: Improve AUR quality - automated testing of all packages

Board footer