According to http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks
I can use different spec files for different platforms. But if I try
that, builds get excluded. Trying the build on the local host, I get:
-- Multiple build description files found: libdbh2-RedHat_RHEL_6.spec,
libdbh2-CentOS_CentOS_6.spec
Is there a correct way to specify multiple spec files for different platforms?
------------------------------------------------------------------------------------
Dr. Edscott Wilson Garcia
Applied Mathematics and Computing
Mexican Petroleum Institute
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
it seems that lots of ARM workers are dead on build.o.o.
Is there someone who could restart them, please? Lots of armv7 build jobs are waiting! ;)
Guillaume
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
2013/11/24 Greg Freemyer <greg.freemyer(a)gmail.com>:
>
>
> Thus oscar ar -r is only meaningful at project level, not the package level.
>
> So, are you using right and there is a bug, or are you attempting to add subdirs to a project and it is appropriately refusing?
Yep. I did not quite grasp the mechanics of the build service. I was
under the impression that the directory structure should be added to
the project (like a svn/git repository). Instead, I've now added a
tarball with an associated specfile and build proceeded.
Thanks
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I'm trying to add a package with "osc addremove -r" to the project
"home:edscott_wilson", but I can only add the top directory. All the
subdirectories are not added and I get a "skipping directory" message
for each. With no directories, package fails to build.
What am I missing here?
--
------------------------------------------------------------------------------------
Dr. Edscott Wilson Garcia
Applied Mathematics and Computing
Mexican Petroleum Institute
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
All,
I saw that the keepassx package was SR'ed from one project to another
and the old project only has 5 packages.
<https://build.opensuse.org/request/show/207887>
Since it was accepted I was going to submit a delete request to the
old project, but when I clicked delete, it felt like is was going to
actually do it, even though I'm not a maintainer of that
project/package:
https://build.opensuse.org/package/show/security:passwordmanagement/keepass…
So either the WebUI is confusing and an SR would have been sent, or it
is broken and it would tried to delete the package.
Greg
--
Greg Freemyer
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi...
Today hermes sent me 14 emails about submit-requests and accept
messages from myself at the same time 6:16pm...while those activities
actually happened two days ago.
I think our experts may have to look at it...actually:
* Since the very beginning of this year, I can't receive any
notifications on time...eg, I do something on OBS, notifications will
arrive one or two days later...even weeks later...And it will always
bomb you by sending lots of...I think they may stuck somewhere...
* I can't receive any notification about SRs against my
repository...eg: someone SRed to M17N:fonts...I can't be aware of it
until I login through web UI...same thing happened to my rejected
requests and accepted requests made by others...well the only type of
SR among such "response needed" types I can receive is the "review
request".
* I always receive two emails telling me about same thing at the same time:
** One is for status change, while the other is just a copy of it.
** One tells me there is a request, while the other tells me I've
already accepted it. (should they arrive at the same time?)
While maybe it's time to invest in new hardware? ...delayed
notification is spam-like right? or hermes has been changed to an
"archiving" system?
Greetings
Marguerite
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
G'day,
Second attempt at sending, this time with no HTML. In the 21st century.
So I've been trying to use OBS source services for my project novaprova
https://build.opensuse.org/project/show/home:gnb:novaprova
to do a development tree (i.e. not a release) build on days when there
are checkins. What I want is a process which does
1. get the latest source from the master branch in the git repo
2. pull the RPM and DEB package control files (.spec etc) out of a
directory in there
3. figure out a version number
4. apply the version number to the .spec file
5. perform build
6. upload build results to repositories
I read this document
http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#Perform_a_nig…
but I didn't want to do an osc commit for every build, or have a
server sitting around whose only purpose was to run a cronjob. So I
thought I could do some clever tricks with source services, resulting
a single _service file which could be used unmodified for every
nightly build. It almost worked. I found the following issues:
1. If the source service runs correctly, there is no visible log. The
build log starts after that.
2. If the source service fails, the error messages only appear in a tooltip.
3. The build log page has a bug where it will repeat large chunks of a log.
4. Source services could be better documented. A lot better. For
example I discovered @PARENT_TAG@ by reading the source.
5. The tar_scm service creates an uncompressed tarball, i.e.
foo-git.1234567.tar. My .spec file was expecting a compressed tarball
and failed.
6. The recompress service could be used to compress the tarball from
tar_scm, but it takes a fixed incoming filename, without wildcards.
This doesn't work when tar_scm is generating a tarball filename which
has a version number encoded in it, which version number is not known
at the time the _service file is written.
7. Likewise, the extract_files service could be used to extract a
spec file from inside the tarball, but it requires a fixed incoming
filename without wildcards. Given that in most projects there will be
exactly one tarball, I would have thought that extract_files could
have guessed correctly, or accepted a wildcard.
8. For the version number, I wanted to use a timestamp in ISO8601
basic format to day precision, i.e. "20131120" for 20 November 2013.
The closest I can get is to use %ci as the versionformat in the
tar_scm service, but this doesn't quite work. Git gives extended
format to second precision
withhttps://help.github.com/articles/post-receive-hooks timezone, e.g.
2013-11-20 10:06:35 -0800. The tar_scm script tries to clean this
up, but the result still has useless information I don't want and
spaces which break the other services.
Also, what's a good way to kick off an OBS build from a GitHub webhook?
https://help.github.com/articles/post-receive-hooks
--
Greg.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello All,
I have a package, perl-jmx4perl, which I need to make available in the
server:monitoring repository. Normally I'd just setup an _aggregate
but it has a number of deps from d:l:p which will need to be available
also. What is the best way to accomplish this?
Thanks!
--
Later,
Darin
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I'm calling osc build Fedora_19 x86_64 for the
network:samba:TESTING/samba project. This is on a openSUSE 13.1 x86_64
host with osc-0.141.0-2.1.2.noarch
It pulls some packages and aborts with:
(Fedora:19) pytalloc-devel-2.0.8-2.fc19.x86_64.rpm 100% |==| 7.4 kB 00:00
Certificate Verification Error: Peer certificate subjectAltName does
not match host, expected ftp.fau.de, got DNS:*.opensuse.org,
DNS:opensuse.org
I can repeate the same command several times and getting by this more
and more of the required 280 packages. One time I get two and the next
ten packages downloaded.
Cheers,
Lars
--
Lars Müller [ˈlaː(r)z ˈmʏlɐ]
Samba Team + SUSE Labs
SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
I have several packages in security that just started failing for the
tumbleweed repo, but they are building fine against 13.1
One example is libpff:
<https://build.opensuse.org/package/show/security/libpff>
The build log concludes with:
====
[ 52s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)'
--nosignature --define '_build_create_debug 1' --define 'disturl
obs://build.opensuse.org/security/openSUSE_Tumbleweed/a69d3b9f16bf88cb09e4f…'
/home/abuild/rpmbuild/SOURCES/libpff.spec
[ 52s] error: Failed build dependencies:
[ 52s] pkgconfig(libcsplit) >= 20130609 is needed by
libpff-0~20130722-6.2.i586
[ 52s] pkgconfig(libcfile) >= 20130609 is needed by libpff-0~20130722-6.2.i586
[ 52s] pkgconfig(libcpath) >= 20130609 is needed by libpff-0~20130722-6.2.i586
[ 52s] pkgconfig(libclocale) >= 20130609 is needed by
libpff-0~20130722-6.2.i586
[ 52s] pkgconfig(libbfio) >= 20130721 is needed by libpff-0~20130722-6.2.i586
[ 54s] /.build/build: line 373: 213 Killed
background_monitor_process
[ 56s] [ 38.418151] SysRq : Power Off
[ 57s] [ 38.564151] Power down.
[ 58s]
===
Those libraries are in 13.1, so they should be in Tumbleweed? Why the failures?
Thanks
Greg
--
Greg Freemyer
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org