Hi all,
looks like obs doesn't rebuild packages when their required dependency
packages are disabled, for easier understanding I created 2 dummy
packages in my home :
https://build.opensuse.org/project/show/home:mseben:dependency_issue
Check the package with name dummy (with BuildRequires vim) it's in
"unresolvable" state :
nothings provides noneexistent-dependency needed by vim
problem is that I already disabled build/publish/useforbuild for this
testing vim package with dependency on "nonexistent-dependency",
however this disable action doesn't trigger rebuilding of package
called dummy
similar real world example is package
devel:languages:ruby:extensions/post-build-checks and its deps on
aaa_base-malloccheck - this deps isn't fulfilled on older distros
(which leads to chain of failing builds for them) and I want to just
disable building of this package only for these older distros in order
to fix builds for them
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
a few weeks ago while I was on vacation I've got dozens of delete
requests like this one
https://build.opensuse.org/request/show/188119
They all were auto accepted only a few days later when I was still on
vacation. Moreover I got no emails about these requests. No chance for
me to take any action. Just noticed them randomly.
Also I don't understand why (almost) nothing seems to be deleted at all
allthough these requests are in state accepted. So this request history
seems to be useless. How can I find out what actually happened to my
projects for real. Or is it still possible that my repos will be
removed somewhen in future?
BTW I also got repeated delete requests which I declined already some
months ago. This is really annoying.
cu,
Rudi
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
First of all, sorry for my english.
Currently, we have an OBS 2.3.0 on SLES11 SP2 x64 with many RPM compiled.
Now, we want to install OBS Server
(http://openbuildservice.org/download/) but before, i have an important
question :
Is it possible to get back our old RPMs from OBS 2.3.0 on SLES11 SP2 to
the new OBS server ?
Do you have any recommendations to upgrade without lose our RPMs ?
Thanks.
Best regards
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
Some time ago I set up my own OBS instance for building YaST installation images.
I noticed that building Kiwi ISO image takes too much time. It turned out that OBS
was downloading all packages inlucluding source packages (src.rpm) and
debuginfo/debug source packages which are not used in the final ISO image at all.
In our case the extra packages are over 7GB in size, which is a lot (and this just
for a small installation DVD, I have selected just "minimal X" packages).
So I decided to look at it during HackWeek. I wanted to get rid of the extra download
which just wastes space and download bandwidth and make ISO builds faster.
And I was successfull, see more details at https://hackweek.suse.com/projects/143
So please, comment on this pull request:
https://github.com/openSUSE/open-build-service/pull/426
I think this will be usefull also for other people building ISO images in OBS and it
could speed up ISO builds also in the public OBS instance as well.
Thank you!
Ladislav
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Tumbleweed hasn't built for days. It seems to have an incredibly low
priority, so it mostly gets one or no build jobs and there's something
changing in Factory that's causing it to require almost a complete
rebuild every couple of days meaning it hasn't really been making much
progress. Could we update it to a higher priority and allow it to use
more build jobs so it has a chance of completing a build before the next
update?
Thanks,
James
--
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 update a number of perl packages in d:l:p so they'll
build in SLE_SP3 and after enabling perl-version for SLE_SP3 I'm
getting unresolvable "provider perl-version is obsoleted by installed
perl". The packages in question are perl-CPAN-Meta and
perl-CPAN-Meta-Requirements, but I'm sure there are more. This was
brought up on this list last year, different package, but not real
solution was provided from what I can tell.
Can someone provide some insight on what needs to be done to move past this.
http://lists.opensuse.org/opensuse-buildservice/2012-11/msg00123.html
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
Hello. It's a known issue of several services types.
______________
Perlow Dmitriy A. via SE Elm
---- Original message ----
From: Michael Schroeder <mls(a)suse.de>
Sent: 08-Oct-2013 11:58
To: Stephan Kulow <coolo(a)suse.de>
Cc: opensuse-buildservice mailing list <opensuse-buildservice(a)opensuse.org>
Subject: Re: [opensuse-buildservice] source server broken
On Tue, Oct 08, 2013 at 08:18:04AM +0200, Stephan Kulow wrote:
> This doesn't look like a problem in my perl package:
>
> Running /usr/lib/obs/service/source_validator --outdir /lxc.tmp.25388/out
> /usr/lib/obs/service/source_validators/20-files-present-and-referenced:
> line 42: /dev/fd/62: No such file or directory
> grep: write error: Broken pipe
> (W) Attention, .old is not mentioned in spec files as source or patch.
> !! .old is a directory !!
> ###ASK -r /lxc.tmp.25388/src/.old
> (W) Attention, .tmp is not mentioned in spec files as source or patch.
> !! .tmp is a directory !!
> ###ASK -r /lxc.tmp.25388/src/.tmp
> /usr/lib/obs/service/source_validators/60-spec-filelist: line 12:
> /dev/fd/62: No such file or directory
> /usr/lib/obs/service/source_validators/60-spec-filelist: line 12: echo:
> write error: Broken pipe
> rm: cannot remove `/var/lib/lxc/obs.service.jail.25388': Is a directory
It also does not look like a bug with the source server. Maybe the
"service server"?
M.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
On 10/07/2013 03:14 PM, Wolfgang Rosenauer wrote:
> Am 07.10.2013 15:07, schrieb Dirk Müller:
>> Hi,
>>
>> increasingly recently I'm seeing constraints added to Factory packages
>> in this form:
>>
>> <constraints>
>> <hardware>
>> <physicalmemory>
>> <size unit="M">2048</size>
>> </physicalmemory>
>> ...
>>
>> This tells OBS to not schedule the job on hosts that can not provide
>> at least 2048 Megabyte (2048 * 1024 * 1024 bytes). With other words,
>> this rules out all 32bit workers without LPAE extension.
>>
>> Unfortunately due to unsolved upstream bugs, the current Guest kernel
>> we use for KVM builds does not have LPAE enabled, which means we can
>> boot VMs with 2000 MB memory maximum (actually a bit lower than that).
>>
>> As a temporary measurement, I've hacked the workers to report 64GB of
>> memory to the scheduler so that those constraints are not effective,
>> but it would be nice to fix this at the source.
>>
>> Please do not add a constraint that rules out any chance of 32bit ARM
>> builds unless you really really really need it (so far I have not seen
>> any package in Factory that cannot be made building with less than 2GB
>> of RAM though).
For devel:languages:python:Factory/pypy I have the following set:
<constraints>
<hardware>
<cpu>
<flag>sse2</flag>
</cpu>
<physicalmemory>
<!-- Actually we only need >4G on x86_64, 2G should be sufficient
on 32-bit machines -->
<size unit="M">5120</size>
</physicalmemory>
</hardware>
</constraints>
As you can read from my comment, I can probably live with half the mem
on 32bit hardware but _constraints currently can't be limited to
architectures. That's a feature I already talked to Adrian about and I
think he's got it on his radar (CC'ing opensuse-buildservice@ therefore).
> Just for clarification. This addresses especially <physicalmemory> and not <memory>?
> I have no idea for ARM but for Firefox & Co. I need usually around 4GB of
> "memory" which can involve swap I guess which is more than suboptimal for speed
> but otherwise I guess we have only very few machines to have real physical 4GB?
According to [1] (and Adrian), <memory> includes swap, whereas
<physicalmemory> does not. I am inclined to always use the latter since
pypy builds still take about 3-5 hours to complete. I don't dare to
imagine how long it would take when using swap :-)
[1]
http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.build_…
--
Sascha Peilicke
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)
This doesn't look like a problem in my perl package:
Running /usr/lib/obs/service/source_validator --outdir /lxc.tmp.25388/out
/usr/lib/obs/service/source_validators/20-files-present-and-referenced:
line 42: /dev/fd/62: No such file or directory
grep: write error: Broken pipe
(W) Attention, .old is not mentioned in spec files as source or patch.
!! .old is a directory !!
###ASK -r /lxc.tmp.25388/src/.old
(W) Attention, .tmp is not mentioned in spec files as source or patch.
!! .tmp is a directory !!
###ASK -r /lxc.tmp.25388/src/.tmp
/usr/lib/obs/service/source_validators/60-spec-filelist: line 12:
/dev/fd/62: No such file or directory
/usr/lib/obs/service/source_validators/60-spec-filelist: line 12: echo:
write error: Broken pipe
rm: cannot remove `/var/lib/lxc/obs.service.jail.25388': Is a directory
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
since building Mozilla Clients does not work with osc build locally since ages
and nobody is looking at the reported bug about it I'm looking for a complete
description how I can build locally using a VM (kvm?) build machine instead of a
chroot build.
I only know some settings from .oscrc but I understood I need more than just
flip a few switches in .oscrc? Can someone please point me to the full
documentation how to set this up?
Thanks,
Wolfgang
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org