Hi,
just recognized that perl-Pod-Simple was removed (perhaps accidently)
from devel:languages:perl.
Why ?
Kind Regards
Chris
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I have just found an update for mkvtoolnix because the package from
multimedia:apps was rebuilt after being submitted to Factory.
Forget the fact that this was an unuseful rebuild that perhaps could
be avoided. My problem is that the package probably shouldn't have
been published.
Before I could look at the build log and see some meaningful output
from build-compare. But nowadays I just find something like:
- obs://build.opensuse.org/multimedia multimedia:apps / openSUSE_11.2
obs://build.opensuse.org/multimedia:apps/openSUSE_11.2/3cc1fd092e992c6b4938…
GPLv2+ GPLv2+
+ obs://build.opensuse.org/multimedia multimedia:apps / openSUSE_11.2
obs://build.opensuse.org/multimedia:apps/openSUSE_11.2/36f0b7d3408de9e659c7…
GPLv2+ GPLv2+
There seems to be some kind of hash in a header that perhaps makes the
comparison more efficient. But doesn't helps me to fix the problem
(ok, probably my problem is the build time being in some binary,
but...).
Could the old behavior be restored?
Thanks.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all,
I'm having trouble running $(build) locally. The error I get is,
>>> build
logging output to /var/tmp/build-root/.build.log...
Memory limit set to 2740424KB
Using BUILD_ROOT=/var/tmp/build-root
Using BUILD_RPMS=/media/dvd/suse
Using BUILD_ARCH=x86_64:i686:i586:i486:i386
oliver started "build sketch-cegis.spec" at Sat Dec 5 00:07:26 PST 2009.
processing specfile /tmp/sketch-cegis-1.5.0SNAPSHOT/sketch-cegis.spec ...
init_buildsystem /tmp/sketch-cegis-1.5.0SNAPSHOT/sketch-cegis.spec ...
It seems that there was an incomplete setup of /var/tmp/build-root.
To be sure, we will build it again completely...
Your build system is broken!! Shall I execute
rm -rf -- /var/tmp/build-root/*
y - yes, cleanup the build root
N - No, abort build (default on enter)
c - Continue anyway with this build root
[y/N/c] y
initializing /var/tmp/build-root/.srcfiles.cache ...
/usr/lib/build/createrpmdeps /media/dvd/suse
expanding package dependencies...
expansion error
nothing provides brp-check-suse
nothing provides post-build-checks
nothing provides rpmlint-Factory
nothing provides build-compare
Thanks in advance,
Nicholas — ntung at ntung — https://ntung.com
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I have three issues with the build service.
First, when I login to my openSUSE account it puts me on some page empty
except for some animated Novell navigation menu :
https://build.opensuse.org/ICSIBroker/?""-T
Second, 'osc status' does not return anything but this warning:
WARNING: SSL certificate checks disabled. Connection is insecure!
I'm using osc-0.123 on Fedora 11. Note I had to add 'sslcertck = 0' to my
~/.oscrc file in order to make osc do anything at all.
Third, and most important, is that my package build fails on openSUSE
11.1/11.2 targets with this message:
+ /usr/lib/rpm/brp-rpath
ERROR: RPATH "/usr/src/packages/BUILD/boron-0.1.0" on /var/tmp/boron-0.1.0-
build/usr/bin/boron is not allowed
ERROR: RPATH "/usr/src/packages/BUILD/boron-0.1.0" on /var/tmp/boron-0.1.0-
build/usr/bin/boron is not allowed
error: Bad exit status from /var/tmp/rpm-tmp.10687 (%install)
I have no idea what this really means or how to fix it. My project does not
use any ld -rpath option, if that is the RPATH being referred to.
-Karl
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I don't want you to bore with 2 pages long emails, so I try to group
the topics a bit. So first the "what we did yesterday":
Adrian and me sit together for roughly 9 hours without big breaks
and "ported" some bigger parts of opensuse svn to git. There is still
a lot left in SVN, we plan to migrate them as the need arises.
On http://www.gitorious.org/opensuse you can see now 9 repos that
weren't there yesterday. Namely
build: what was in buildservice/src/build
build-service: frontend, webclient and backend together (more to this later)
hermes: what was in infrastructure/hermes
openfate: what was in infrastructure/openfate
osc: what was in buildservice/src/clientlib/python/osc
shared-resources: 4 "common" directories grouped
sign: what was in buildservice/src/sign
software-o-o: what was in buildservice/src/software
yabsc: what was in buildservice/src/yabsc
For the build-service we took the opportunity to rename webclient to webui
(as it's not really a client, it's a server that talks to other servers)
and frontend to api (as this is what people refer it to). We did this rename
in the history, so the first commit to them are already named webui. This
is to make it easier to track history without larger renames.
We only imported release branches with one exception: branches/jw ended
up in osc as it's the only active (as in the last month) branch. On how
to handle branches, I'll write a separate mail.
The "shared-resources" are basically things we linked into checkouts using
svn:externals before. Now we have one extra module for that that we link
into a toplevel directory on git repos and add symlinks into it. This is
not as convenient as svn:externals but more clear. We will hopefully collect
some experience with it and eventually change it, but for now it seems the
best approach.
I already deployed webui from the new git repository on
build.opensuse.org/stage and it looks fine.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Questions:
See error below.
1. How can I force the removal from my MyHome Project of openSUSE_Factory
item ?
2. How do I unlink any repos which link against it ?
3. How do I find out the email address from the linkage so I can tell them
to remove the link ?
4. How can i remove the item if the previous steps fail ?
Thanks Glenn
openSUSE Webclient Error:
Error Details:
Errorcode: project_save_error
Message: error saving project: Repository home:doiggl/openSUSE_Factory
cannot be deleted because following repos link against it:
home:elvigia:branches:home:doiggl/openSUSE_Factory
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
as already announced to all people with a commit account the svn on
forge.novell.com will get transfered today (and maybe also still tomorrow).
We will be back on gitorious.org and we will anounce details when we finished.
I am about to remove the svn commit rights on forge now to avoid data loss
during the transfer period.
welcome back in this theater soon :)
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian(a)suse.de
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I've been testing out upgrading our internal copy of osc to 0.123 to get
python-keyring support, but I've hit a snag when calling osc build with
the --prefer-pkgs flag. The flag appears to package the build
description into a cpio file, but obs-server 1.6 gives a parse error
when this happens. What is the latest version of osc that is compatible
with 1.6 when using the --prefer-pkgs flag or is a stable version of the
server available that supports the cpio format?
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I've raised that issue long time ago already but there was no real
outcome IIRC.
As I'm managing a a popular repository which should be kept as stable
and reliable as possible I turning publishing off when I prepare a new
update package. I do that even before upstream released the update
officially to be able to release it at about the same time.
Now as the repo is popular there are people linking to packages from
there but in their repos publishing is not disabled and the packages
might get picked up as if they were final or whatever.
How to avoid that?
Thanks,
Wolfgang
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org