You are not logged in.
Hi!
We can now apparently build Arch Linux packages in OpenSUSE Build Service!
Open Build Service adds support for Arch Linux
Seems like an easy way to create custom repositories
Offline
How to build Arch Linux packages
All you need to do is to add the Arch:Extra repository to your OBS project and a PKGBUILD description to your package sources and the OBS will build and publish a repository of .pkg.tar.xz packages.
2 questions come to mind :
- do they support using a src.tar.gz pacakge, like it's made by makepkg --source ?
- How current is that OBS Arch:Extra repo , and how often does it gets updated ?
Last edited by Lone_Wolf (2012-10-08 10:19:19)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
who has managed to create a repository or arch linux on https://build.opensuse.org? if so how to share.
Offline
I tried, the package is ' home:andreas_baumann, Wolframe'.
Roughly this is what I did:
a) Added the 'Arch:Extra' repository:
shell> osc meta prj -e
<repository name="ArchLinux">
<path project="Arch:Extra" repository="standard"/>
<arch>i586</arch>
<arch>x86_64</arch>
</repository>
b) Added a PKGBUILD with one source tarball, absolute standard, no problems.
'Arch:Extra' doesn't contain community packages like 'dia' and 'fop' (which I need to build the documentation),
an 'Arch:Community' would be nice.
Arch:Extra itself looks a little bit out-of-date: boost was 1.50 and not 1.52.
Last edited by andreas_baumann (2013-02-21 08:43:36)
Offline
Are there more users using this open build service? I really like it so far, however the fact that there's no community repo is quite disappointing. Any hints on how to build packages which depend on community?
Offline
I'd query the openSUSE people about getting [community] added. I'm sure they would be quite responsive.
Offline
- How current is that OBS Arch:Extra repo , and how often does it gets updated ?
According to this they "do an rsync on the repos every weekend".
Offline
There is a discussion going on here:
http://lists.opensuse.org/opensuse-buil … 00015.html
The issue is that [community] contains some 'forbidden' packages on this blacklist:
http://en.opensuse.org/openSUSE:Build_S … _blacklist
[extra] also contains some of these packages but these have now been deleted from the OBS.
Offline
i'm confusing about this, im trying to build tint2-svn package with this OBS, upload PKGBUILD and patches but somehow it fail to build the reason is because i fetch tint2-svn from google via SVN, but when i fecth tint2-svn in my computer compress it, then upload the compressed tint2-svn, edit little thing in PKGBUILD to build from the source which i already compressed before, then it build and success,,, is this feature or disabled by default?
Offline
i'm confusing about this, im trying to build tint2-svn package with this OBS, upload PKGBUILD and patches but somehow it fail to build the reason is because i fetch tint2-svn from google via SVN, but when i fecth tint2-svn in my computer compress it, then upload the compressed tint2-svn, edit little thing in PKGBUILD to build from the source which i already compressed before, then it build and success,,, is this feature or disabled by default?
That is because the build machines in OBS are not connected to the internet. You can only build packages when you upload the sources as well. AFAIK it is not possible to change this.
Offline
Yes, the connection is really disabled. I've been playing with OBS a little and can confirm this.
Here is a typical log of the error we get with an example PKGBUILD I maintain:
[ 262s] now finalizing build dir...
[ 263s] Preparing sources...
[ 263s] ==> Making package: topcoder-arena 1-2 (Tue Jun 17 02:19:32 UTC 2014)
[ 263s] ==> Checking runtime dependencies...
[ 263s] ==> Checking buildtime dependencies...
[ 263s] ==> Retrieving sources...
[ 263s] -> Downloading ContestAppletProd.jnlp...
[ 263s] % Total % Received % Xferd Average Speed Time Time Time Current
[ 263s] Dload Upload Total Spent Left Speed
[ 263s] 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Transient problem: timeout Will retry in 3 seconds. 3 retries left.
[ 266s] 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Transient problem: timeout Will retry in 3 seconds. 2 retries left.
[ 269s] 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Transient problem: timeout Will retry in 3 seconds. 1 retries left.
[ 272s] 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: www.topcoder.com
[ 272s] ==> ERROR: Failure while downloading ContestAppletProd.jnlp
[ 272s] Aborting...
[ 272s] -----------------------------------------------------------------
[ 272s] ----- building PKGBUILD (user abuild)
[ 272s] -----------------------------------------------------------------
[ 272s] -----------------------------------------------------------------
[ 272s] ==> Making package: topcoder-arena 1-2 (Tue Jun 17 02:19:41 UTC 2014)
[ 272s] ==> Checking runtime dependencies...
[ 272s] ==> Checking buildtime dependencies...
[ 272s] ==> WARNING: Using existing src/ tree
[ 272s] ==> Entering fakeroot environment...
[ 273s] ==> Starting package()...
[ 274s] install: cannot stat 'topcoder-arena': No such file or directory
[ 274s] ==> ERROR: A failure occurred in package().
[ 274s] Aborting...
[ 276s] [ 211.113610] SysRq : Power Off
[ 276s] [ 211.117879] reboot: Power down
Here is a [community] repo project.
It is from (probably) an Arch user, which seems to have cloned the community.git repo and put it directly there. I'm not sure if it is possible to integrate this unnoficial repo with a custom PKGBUILD in OBS, but it would be really nice if it were.
Here is another Arch project repo.
Last edited by thiagowfx (2014-06-17 03:09:31)
Offline
As an update, there is one way of getting packages of [community] recognized in your home: project. For example, with xcb-util-cursor:
osc branch home:roman-neuhauser:arch-community/xcb-util-cursor home:thiagowfx:arch/xcb-util-cursor
Of course, the generic case is:
osc branch home:roman-neuhauser:arch-community/<package_name_here> home:<your_username>:<your_subproject>/<package_name_here>
After a while, workers will build your package, so a package that previously failed because it couldn't met its dependencies, now will probably build. The only caveat of this method is that you must have all the package dependencies (not only its immediate ones) in your subproject. pactree is a good utility to help on that.
Offline