Hi,
In the project:
openSUSE:Tools
the package :
obs-server
Need to be install:
Requires: perl-BSSolv >= 0.18.0
But the package perl-BSSolv provide:
perl-BSSolv-0.17.2-40.1
so we can't install obs-server.
Some body know when perl-BSSolv
--
Ronan Le Martret
Intel Open Source Technology Center
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Can anyone explain to me why
https://build.opensuse.org/package/show?package=bup&project=home%3Aaspiers%…
is showing unresolvable for openSUSE_Factory?
for example:
$ osc r
[snipped]
openSUSE_Factory x86_64 unresolvable: nothing provides ghc(base-4.5.0.0-40b99d05fae6a4eea95ea69e6e0c9702) needed by pandoc
[snipped]
AFAICS the <path> dependency on devel:languages:haskell is correct:
<repository name="openSUSE_Factory">
<path project="devel:languages:haskell" repository="openSUSE_Factory"/>
<arch>x86_64</arch>
<arch>i586</arch>
</repository>
but when I download ghc-base-4.5.0.0-4.13.x86_64.rpm from
http://download.opensuse.org/repositories/devel:/languages:/haskell/openSUS…
it definitely provides the symbol which is supposedly missing.
The only think I can think of is that the build and publish flags in
d:l:h have been disabled, but the 'Use for Build' flag is still
enabled. I emailed one of the project's maintainers (Peter Trommler)
separately asking about this.
Thanks!
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
The current mails about new submit requests from foreman.opensuse.org
have an URL which does not show anything:
https://build.opensuse.org/request/diff/123456
If 'diff' is replaced with 'show' the request is displayed properly.
Olaf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
e.g. from
https://build.opensuse.org/project/monitor?project=home:xtreemfs:testing
Debian5: conflict for all providers of cpio >= 2.4.2-2 needed by dpkg-dev
Debian6: conflict for all providers of libc-bin = 2.11.2-10 needed by libc6,
conflict for all providers of initscripts needed by procps
xUbuntu9.04: conflict for all providers of initscripts needed by upstart-
compat-sysv
xUbuntu9.10: conflict for all providers of libc-bin = 2.10.1-0ubuntu15 needed
by libc6
xUbuntu10.04: conflict for all providers of libc-bin = 2.11.1-0ubuntu7 needed
by libc6, conflict for all providers of initscripts needed by upstart
xUbuntu10.10: conflict for all providers of libc-bin = 2.12.1-0ubuntu6 needed
by libc6, conflict for all providers of initscripts needed by procps, conflict
for all providers of initscripts needed by upstart
xUbuntu11.04: conflict for all providers of libc-bin = 2.13-0ubuntu13 needed
by libc6, conflict for all providers of initscripts needed by procps, conflict
for all providers of initscripts needed by upstart, conflict for all providers
of libnss3 = 3.12.9+ckbi-1.82-0ubuntu2 needed by libnss3-1d
xUbuntu11.10: conflict for all providers of libc-bin = 2.13-20ubuntu5 needed
by libc6, conflict for all providers of initscripts needed by procps, conflict
for all providers of initscripts needed by upstart, conflict for all providers
of initscripts >= 2.88dsf-13.3 needed by ifupdown, conflict for all providers
of libnss3 = 3.12.9+ckbi-1.82-0ubuntu6 needed by libnss3-1d
xUbuntu12.04: conflict for all providers of libc-bin = 2.15-0ubuntu10 needed
by libc6, conflict for all providers of initscripts needed by procps, conflict
for all providers of initscripts needed by upstart, conflict for all providers
of initscripts >= 2.88dsf-13.3 needed by ifupdown, conflict for all providers
of libnss3 = 3.13.1.with.ckbi.1.88-1ubuntu6 needed by libnss3-1d
xUbuntu12.10: conflict for all providers of libc-bin = 2.15-0ubuntu20 needed
by libc6, conflict for all providers of initscripts needed by procps, conflict
for all providers of initscripts needed by upstart, conflict for all providers
of initscripts >= 2.88dsf-13.3 needed by ifupdown, conflict for all providers
of libnss3 >= 3.12.9+ckbi-1.82-0ubuntu3~ needed by ca-certificates-java,
conflict for all providers of libnss3 = 3.13.1.with.ckbi.1.88-1ubuntu7 needed
by libnss3-1d
Nico
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
What do these new unresolvable errors mean?
perl-Pod-Simple did not change, its a _link to devel:languages:perl.
obs/Virtualization/libguestfs $ obs r -v
openSUSE_11.4 i586 unresolvable: conflict for all providers of perl(Pod::Simple::XHTML) >= 3.16
openSUSE_11.4 x86_64 unresolvable: conflict for all providers of perl(Pod::Simple::XHTML) >= 3.16
SLE_11_SP2 i586 unresolvable: conflict for all providers of perl(Pod::Simple::XHTML) >= 3.16
SLE_11_SP2 x86_64 unresolvable: conflict for all providers of perl(Pod::Simple::XHTML) >= 3.16
Olaf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
After updating build.opensuse.org to current OBS code we have
now support for build job constraints now.
This means you can tell OBS to build a certain package, repository
or project to build only on build hosts which grant a certain hardware or
software feature.
Just to name two examples, you can require a certain amount of
memory or storage space. Or you can build on a special kind of
build host which guarantees you that benchmark result can be
compared between the build jobs.
Please note that you limit your package to be dispatched to a subset
of hosts. So it may dispatched way later or in worst case not at all
when we do not have such a build host. This means it stays in "scheduled"
state.
We do _NOT_ have a "dispatchstatus" yet which would tell if a job is dispatchable
at all or not.
Please find details about this feature in our book chapter:
http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.build_…
Just as an example, you may want to require a VM memory size of 2GB.
You need add a "_constraints" file into your package source with
this syntax:
<constraints>
<hardware>
<memory unit=G>2</memory>
</hardware>
</constraints>
Or you want to run on a specific new host, which we have to
have comparable benchmarks. There is only running one build
job on this hardware and it will always have the same
hardware configuration. You need to use the hostlabel "benchmark"
in our build.opensuse.org instance:
<constraints>
<hostlabel>benchmark</hostlabel>
</constraints>
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian(a)suse.de
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
Since the update (OBS 2.4a1), the download page isn't generated
anymore. Here is an example (from the official documentation):
http://software.opensuse.org/download.html?project=openSUSE:Tools&package=o…
Regards,
Cédric.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
OBS will have a downtime of 1-2hours tomorrow (thursday)
during our regular maintenance window.
We will start at
08:00 UTC
to move our servers physically and do also a larger
OBS version update (details will follow on that later).
This will affect the hosts
build.opensuse.orgapi.opensuse.orgSoftware.opensuse.org will not have the package search during
the OBS downtime.
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian(a)suse.de
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
[cross-posted, but let's divide follow-ups: general rpmlint discussion
to opensuse-buildservice, and rubygem rpmlint issues to opensuse-ruby,
thanks :-]
Hi all,
It seems that the newest version of rpmlint-mini in OBS is only 1.3.
Presumably this means we are lagging quite far behind upstream
rpmlint, because 1.4 was released almost a year ago:
http://www.zarb.org/pipermail/rpmlint-discuss/2011-December/001008.html
One issue with 1.3 (and in fact even 1.4) is that we are getting a
bunch of spurious warnings from every rubygem package build, due to ri
documentation files containing percent-encoded characters:
http://rpmlint.zarb.org/cgi-bin/trac.cgi/ticket/569
The fix is simple:
http://sourceforge.net/p/rpmlint/code/ci/ae8a019e53784a45c59f23a7b09ad47ea7…
and could presumably be backported very easily.
So what's the policy on updating rpmlint-mini?
Thanks,
Adam
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
As I also hit the same issue, I looked at the problem:
[ 192s] [191/305] installing x11-common
[ 192s] Selecting previously unselected package x11-common.
[ 194s] Can't exec "insserv": No such file or directory at /usr/sbin/update-rc.d line 417.
[ 194s] update-rc.d: error: insserv rejected the script header
[ 194s] dpkg: error processing x11-common (--install):
[ 194s] subprocess installed post-installation script returned error exit status 255
[ 194s] Errors were encountered while processing:
[ 194s] x11-common
[ 194s] exit ...
x11-common simply manages a initscript via update-rc.d - the bug is inside update-rc.d (part of sysv-rc package).
update-rc.d checks, if /etc/init.d/.legacy-bootordering is present. If yes, it changes the etc directory itself, else it calls
inserv [expecting, that it is in the path - the insserv package ships this exectuable in /usr/lib/insserv].
The postinst of sysv-rc creates /etc/init.d/.legacy-bootordering, if still some init scripts are linked as
/etc/rc0.d/S*
In a Ubunutu 12.04 (as well as Ubuntu 12.10) chroot, update-rc.d is broken, if there is no /etc/init.d/.legacy-bootordering.
Ensuring, that there is a /etc/init.d/.legacy-bootordering after sysv-rc is installed and configured, should solve the problem.
I don't fully understand the OBS bootstrap nor have I tried to reproduce the bootstrap, but in my option the problem
is caused by the fact, that passwd on 12.10 got a depenendency to upstart added. So initscripts/sysv-rc.d are installed
in the first phase (--prepare) - according to the build logs (and the project config), it's postinst are not started.
So in my option, OBS could add a workaround to create a /etc/init.d/.legacy-bootordering after finishing prepare.
Running the initscripts of sysc-rc.d/initscripts could also be an option.
Regards,
Martin
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org