Hi,
I am rebuilding centos7 using a local openbuild service server,
which version is 2.6.2. Both server and worker are sles11 sp3.
First, I create a project names CentOS7, then put the content
below to Meta sheet through web page.
<repository name="standard">
<arch>x86_64</arch>
<arch>i586</arch>
</repository>
Second, I connect the server, find the project repos, then create
":full" directory under x86_64 and i686 folder. After that, I copy
all x86_64 and noarch rpm packages to x86_64/:full, i686 and noarch
rpm packages to i686/:full. These rpm packages are from
CentOS-7-x86_64-Everything-1503-01.iso
Third, create another project names test, in its Meta I add below
<repository name="standard">
<path project="CentOS7" repository="standard"/>
<arch>x86_64</arch>
<arch>i586</arch>
</repository>
Here comes my questions.
1. I uploaded gcc's source, but it can't be built.
In x86_64 architecture the status is unresolvable with hint
"nothing provides /usr/bin/pod2man, nothing provides /lib/libc.so.6,
nothing provides /usr/lib/libc.so, nothing provides /lib64/libc.so.6,
nothing provides /usr/lib64/libc.so"
gcc.spec has BuildRequires that directly point to file like below
BuildRequires: /lib/libc.so.6 /usr/lib/libc.so /lib64/libc.so.6 /usr/lib64/libc.so
but openbuild service looks like can't analysis this kind BuildRequires, so I
changed gcc.spec into
BuildRequires: glibc(x86-64) glibc(x86-32)
then hint changed into "nothing provides /usr/bin/pod2man, nothing provides glibc(x86-32)"
looks like it can't find glibc-2.17-55.el7.i686.rpm which provides glibc(x86-32)
Question:
How can I find 32bit BuildRequires while build x86_64 rpm packages?
2. I uploaded glibc's source, x86_64 architecture was ok but can't build i686 package
The status was also unresolvable, the hint is
"nothing provides gcc>=3.2 ………………"
seems build glibc.i686 rpm need gcc.i686, but actually, use gcc.x86_64 with option -m32
can build 32bit program, also "rpmbuild --target i686 glibc.spec" can generate glibc's
i686 rpm on centos.
Question:
How can I cross build i686 package using x86_64 enviroment?
Anyone can help?
Thank you
hui.wang
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
http://download.opensuse.org/ports/update/13.2/ repo is outdated. Last update is from 25th of june.
Anything wrong on OBS side?
Guillaume
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
What version of mercurial is used to process the _service files?
'osc service lr' works, but 'rr' fails and home:olh/mutt enters state
'broken'.
Files could not be expanded: Cleaning: /lxc.tmp.18755/out/tmpdsZgGd
Unfortunately obs-service-tar_scm lacks a shortcut to construct an
usable version string, so I tried to emulate it like that:
<services>
<service name="tar_scm">
<param name="url">http://dev.mutt.org/hg/mutt</param>
<param name="scm">hg</param>
<param name="versionformat">{date(date, '%Y%m%dT%H%M%S')}.r{rev}</param>
<param name="revision">default</param>
<param name="filename">mutt</param>
</service>
<service name="recompress">
<param name="file">*.tar</param>
<param name="compression">xz</param>
</service>
<service name="set_version"/>
</services>
Olaf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello everyone,
Here's another release of Qactus; v0.7.0 comes with many new features
and improvements, such as:
New features:
* you can now add packages by dropping OBS package URLs
on the packages' tab (thanks for the idea, Adrian)
* proxy support
* self-signed certificate support
* using any OBS instance is now supported
Improvements and bug fixes:
* Async getBuildStatus() requests
* Code refactoring: OBS façade created, some code cleanup
* Error handling: it's more verbose about HTTP and SSL errors
* Fixed getting description from OBSRequest
* Fixed parsing empty tags (ie: <description/>)
* Minor improvements
Any feedback is welcome. More features, so more bugs ;)
Packages are on their way to KDE:Extra and openSUSE:Factory (soon).
https://github.com/javierllorente/qactus/
Greetings,
- --
Javier Llorente
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlXQ6rkACgkQdV3zWWOPFxROpQCfbfR12iXTgmylEhx0YKdyF1DB
sf8AmgPDTadr6lT2+NkGly69uuETNS3L
=SS6W
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi guys,
It seems that Ipv4 connectivity to the OBS infrastructure is down: traceroutes
via IPv4 stop at the inbound gateway, traceroutes via IPv6 get through...
Problem is, not all services have Ipv6 addresses in the public DNS, and I
don't know if osc is even IPv6 capable...
Here's a traceroute:
traceroute to login.opensuse.org (195.135.221.133), 64 hops max, 52 byte
packets
1 static.161.185.76.144.clients.your-server.de (144.76.185.161) 0.784 ms
3.282 ms 0.434 ms
2 hos-tr5.juniper1.rz20.hetzner.de (213.239.233.129) 5.296 ms
hos-tr6.juniper2.rz20.hetzner.de (213.239.233.161) 0.152 ms
hos-tr5.juniper1.rz20.hetzner.de (213.239.233.129) 0.146 ms
3 core22.hetzner.de (213.239.245.157) 0.190 ms
core22.hetzner.de (213.239.245.169) 0.304 ms
core21.hetzner.de (213.239.245.165) 0.212 ms
4 core11.hetzner.de (213.239.245.225) 2.750 ms
core11.hetzner.de (213.239.245.221) 4.471 ms
core12.hetzner.de (213.239.245.214) 11.721 ms
5 juniper4.rz2.hetzner.de (213.239.245.26) 2.825 ms 2.762 ms 2.755 ms
6 GigE-0.SuSE.DHK.N-IX.net (195.85.217.20) 3.205 ms 3.221 ms 4.946 ms
7 * * *
8 *
Cheers
MH
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
OBS 2.6.3, 2.5.7 and 2.4.8 released
===================================
These releases are fixing in first place a security issue which
allows to modify package sources without the sufficient permissions.
This leak exists in almost all OBS releases so far, esp. when
using "patch" command version 2.7 or later, which introduced
the git format patch handling.
This issue is tracked as CVE-2015-0796.
It was found by Marcus Hüwe. Thanks a lot for his work and
the way he reported it, allowing us to fix this fast and properly.
In case you want to see an exemplary good security leak analyses,
read bugzilla issue #941099 :)
Updaters from any OBS 2.6 release can just ugrade the packages
and restart all services. Updaters from former releases should
read the README.UPDATERS file.
OBS update are available from the following projects:
https://build.opensuse.org/project/show/OBS:Server:2.6https://build.opensuse.org/project/show/OBS:Server:2.5https://build.opensuse.org/project/show/OBS:Server:2.4
The appliance can be downloaded from
http://openbuildservice.org/download
Details from the Release Notes:
===============================
Feature backports:
==================
* backend: support using docker as build environment (not secure)
Changes:
========
* none
Bugfixes:
=========
* backend: validate results of external patch command. could be used
to modify packages without sufficiant permissions (bnc#941099, CVE-2015-0796)
* backend: fixing create pattern call in publisher
* backend: fix handling of host specific bsconfig.* files
--
Adrian Schroeter
email: adrian(a)suse.de
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello there,
Is it possible to have a 1 MB size fixed name file on the http://download.opensuse.org/
I would like to use it to monitor server access with smokeping (1)
(1) http://software.opensuse.org/package/smokeping
--
Michel Normand
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello everybody.
There is a GitHub service for triggering OBS build. It's easy to use
(if not primitive) and nice. But to me, there was a drawback with it:
it didn't allow user to trigger build *selectively*, for example, for
master branch only, in order to save OBS servers from unnecessary
work.
So I've added this feature. See the following pull request for more
information. I've also changed documentation for OBS service to
explain new feature as detailed as possible.
— https://github.com/github/github-services/pull/1058
I would be glad if this feature is useful for somebody else too.
——— Pavel Kretov.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi:
I created an OBS project in Base:System called target-isns several
months ago, imported from a public project of the same name.
It has been building fine for all targets (SLE_11_SP3, openSUSE_13.2,
and openSUSE_Factory) for a while now.
But recently the Factory builds are failing, and it looks like the
errors have to do with changes in the gcc library, particularly netdb.h.
For example, this code uses gai_strerror(3), which the man page on my
Factory system says is defined in netdb.h. This code includes netdb.h.
But this function is showing up as undefined, cause several problems.
What's the best way to fix this? It looks like the netdb.h file is part
of glibc-devel.
On my factory system, I have glibc-devel version 2.21, but it looks like
the build of my Factory RPM used version 2.22. I can see that the latest
glibc-devel version in OBS in 2.22, but how did the Factory system where
my RPM is being built end up with the wrong (too new) version? And how
to I ensure my build gets the right (older) version?
I tried setting "BuildRequires: glibc-devel = 2.21", but that did not work.
A Side Question: If I wanted to test on a local system using this newer
glibc-devel package, how would I go about it? I assume that there are
more than just one package that has to be updated to switch versions.
--
Lee Duncan
SUSE Labs
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello guys,
I have customized a Linux distribution from Centos 6.5.
I hope OBS can build rpm packages for it. Is that possible? Howto? Any
suggestions
Thanks
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org