Hi all.
I'm trying to remove a repo/buildtarget that other users have branched
from, yet doing it the "suggest" way via
bjolie@embla:~> osc meta prj -e Project:FOO -f
Sending meta data...
BuildService API error: 500
Try again? ([y/N]): n
discarding /tmp/osc_metafile.DoNwAp.xml
bjolie@embla:~>
lands me in this lovely errormsg.
Pretty sure this worked fine before latest changes on the obs.
Does anyone have some insight into what might be going wrong?
//Bjørn Lie
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi all,
I wanted a way to quickly compare a project with its "upstream"
project, and a quick hack ended up as a new osc plugin:
https://gist.github.com/616b476a9c592a0a2a89
(Copy to your ~/.osc-plugins or /var/lib/osc-plugins to try it.)
Example usages:
$ osc prdiff --include=client openSUSE:Factory Cloud:OpenStack:Factory
differs: python-glanceclient
identical: python-keystoneclient
differs: python-novaclient
differs: python-quantumclient
identical: python-swiftclient
$ osc prdiff --new-only --exclude='crowbar|rubygem' \
systemsmanagement:chef:10:staging \
systemsmanagement:crowbar:2.0
identical: couchdb
identical: erlang
identical: gecode
identical: js
differs: rabbitmq-server
new only: all-barclamps-good
new only: fakechroot
new only: libyaml
new only: ruby
new only: ruby-common
new only: ruby19
new only: sleshammer
$ cd ~/OBS/home/aspiers/branches/devel/languages/ruby/
$ osc prdiff --diffstat --requests
differs: ruby-common
generate_buildrequires.sh | 31 ++++++++++++++++++++++++++-----
ruby-common.changes | 8 ++++++++
2 files changed, 34 insertions(+), 5 deletions(-)
148023 State:new By:aspiers When:2013-01-11T11:04:14
submit: home:aspiers:branches:devel:languages:ruby/ruby-common -> devel:languages:ruby
Descr: - Fix it to work even if all-good has just been created locally
via mkpac and doesn't exist server-side yet. - Improve support
for running within a branch of the original project. This
allows submitreqs which change all-good.spec.
Feedback welcome. I'd also like to know if it makes sense to include
this in osc core (my vote is yes, but I'm biased ;-)
Cheers,
Adam
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Building a package on openSUSE 12.3 for openSUSE:Factory using
Base:System, the building suddenly stops with this messages:
warning: /var/tmp/osbuild-
packagecache/Base:System/openSUSE_Factory/x86_64/coreutils-8.17-183.1.x86_64.rpm:
Header V3 DSA/SHA1 Signature, key ID 5d053b4f: NOKEY
/var/tmp/osbuild-
packagecache/Base:System/openSUSE_Factory/x86_64/coreutils-8.17-183.1.x86_64.rpm
: public key not available
/var/tmp/osbuild-
packagecache/Base:System/openSUSE_Factory/x86_64/diffutils-3.2-23.1.x86_64.rpm
: public key not available
/var/tmp/osbuild-
packagecache/Base:System/openSUSE_Factory/x86_64/filesystem-12.3-102.1.x86_64.rpm
: public key not available
/var/tmp/osbuild-
packagecache/Base:System/openSUSE_Factory/x86_64/fillup-1.42-283.14.x86_64.rpm
: public key not available
What's wrong here?
Andreas
--
Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
while looking for a recent scratch http://scratch.mit.edu/ in opensuse
I found that there are different versions of squeak running around in
X11:Sugar and devel:languages:smalltalk. The latter project seems not
to have seen any updates for almost three years, so I decided to
submit all of my changes to Education (where scratch lives). Is there
any smalltalker who wants to revive it or is it better to have it all
in Education?
Best regards,
Michael
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Dear All
Now I Encountered a problem about debugging webui.
I follow the steps at the debug website
(http://en.opensuse.org/openSUSE:Build_Service_Webclient_Development#Debuggi…),
when I access 'localhost/project/list_public' or something else after
execute the "script/server", the browser is always showing me that
"Unauthorized access, please login" and so on .
As we know, at this time there is no any user in database. How can I bypass
the problem ? Or I did something wrong ?
--
View this message in context: http://opensuse.14.n6.nabble.com/How-to-Bypass-user-authentication-during-w…
Sent from the opensuse-buildservice mailing list archive at Nabble.com.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Dear All,
in the %build section of an .spec file I'm writing I need to run a
thirds part script that use wget to download some file directly from
internet.
If I try to build the .rpm locally to check any error before to commit
the changes, I'll get the following error:
Resolving www.netlib.org (www.netlib.org)... failed: Connection refused.
wget: unable to resolve host address `www.netlib.org'
It seems that during the build of an rpm there is no internet access.
How can I configure osc in order to have internet access during the
local building of packages ??
Thanks,
Gianluca Massera.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
The 'osc diff' command from osc-0.139.1 complains about missing files if
files from an earlier 'osc ar' were removed.
I think 'osc diff' should be more forgiving and diff just whats (still) there.
# rm release-1.tar.bz2
# wget host/pub/release-2.tar.bz2
# sed -i 's@^Version:.*@Version: 2@g' *.spec
# osc ar
# sleep $((60 * 60 * 24 * $n))
# rm release-2.tar.bz2
# wget host/pub/release-3.tar.bz2
# sed -i 's@^Version:.*@Version: 3@g' *.spec
# osc diff
file 'release-2.tar.bz2' is marked as 'A' but does not exist
(either add the missing file or revert it)
#
Olaf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
We are proud to announce the availability of OBS 2.4.0 RC 1.
Plenty of features and other improvements went into this release.
In short, it supports new packaging formats, new architectures, supports
new virtualization methods, offers new collaboration workflows and
can handle build job distribution better.
As a release candidate, it may get released unmodified, but please
give it a final test before.
One thing which is currently in unclear state is the LDAP support.
While there is a group working on improving it, the current code
is completely untested by SUSE. It would be great if someone could
test it before release.
The release rpms and appliances can be found in OBS:Server:2.4 project:
http://en.opensuse.org/openSUSE:Build_Service_Appliance
Repositories:
http://download.opensuse.org/repositories/OBS:/Server:/2.4/
The version is currently tagged as 2.3.95.
Please find the full release notes below:
=========================================
#
# Open Build Service 2.4
#
Please read the README.SETUP file for initial installation
instructions or use the OBS Appliance from
http://en.opensuse.org/Build_Service/OBS-Appliance
There is also an install medium with installs OBS on hard disc now.
dist/README.UPDATERS file has informations for updaters.
OBS Appliance users who have setup their LVM can just replace
their appliance image without data loss. The migration will
happen automatically.
Regressions:
============
* LDAP support is not tested and in unknown state (not part of test suite)
(A rewrite of it is WIP)
* source service editor in webui is not available anymore
Changes on purpose:
===================
* Migration to Ruby 1.9 and Rails 3.2
* request database got moved from backend to the api. Directly
after update all requests seem to have vanished, but a delayed
job is importing them again. This can take some hours dependening
on the amount of requests.
* package meta of package copy command is not copying
relationships and devel definitions anymore
* Requests do require a description now in any case
* webui configurations got moved from environments/*.rb to config/options.yml.
* Package conflicts and obsoletes are taken into account when resolving
dependencies for build jobs. This improves build consistency but may also lead
to new "unresolvable" errors, since they were ignored so far. The old behaviour
can be restored by adding the following line into the project configuration:
ExpandFlags: ignoreconflicts
* cross architecture build directives in project configuration
CBInstall and CBPreinstall are not supported anymore. Use standard "Install" and
"Preinstall" directives instead.
=> all architectures can be used as host for cross build now.
* The api file/distribution.xml is obsolete, the config gets stored in the SQL database
now. Existing file gets imported during migration.
The list from remote instances can displayed and updated automatically now.
Features
========
* Arch Linux package format support got added.
* Build Job Constraints handling. It can be used to define build
instance requirements for certain build jobs. Either for defined
package sources or for all repositories.
Documentation about this can be found here:
http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.build_…
* Support of preinstall images, which can be used to speed up build
jobs. They need to be build manually, but get automatically used for
creating a build instance base in a faster way than just with installing
packages.
* Static links (without version and release numbers) for binary results
in the published repositories can be configured now. This can be done via
the "staticlinks" keyword in Repotype: definition.
* Build Prerequires can be used also with the FileProvides feature in the
build configuration now.
* Regular users can copy entire projects (without binary results) now.
* Upload of binaries via api is allowed to administrators now.
* Data about used resources of build jobs get collected. However it
gets not yet used for build job assignment
* Requests can be listed also for given groups now.
* Checkout of delete packages does not require a srcmd5 sum anymore.
* Delete Requests can be used to request deletion of repositories from
a project.
* Support of creation of application data xml which can be used for app
stores for application centric browsing versus package browsing.
* Support hugetable memory usage for kvm workers.
* Support building cross build formats, eg. building an rpm with a kiwi
build description or an deb package via a .spec file.
* Efficient transport of product build results from worker to backend.
* aarch64 architecture added (aka armv8 or arm64)
* New generic "emulator" virtualization support. Can be used to build inside
of system emulators (for foreign hardware for example)
* New s390 z/VM virtualization support.
Deprecated:
===========
The following calls have been marked as deprecated, they will get removed in OBS 3.0
* api
- /person/$LOGIN/group -> use /group?login=$LOGIN instead
- /search/project_id -> use /search/project/id instead
- /search/package_id -> use /search/package/id instead
* The deprecated support to copy qemu binaries from external build host into
build environment has been removed. This includes also the CBInstall and CBPreinstall
project configuration directives.
Notes for systems using systemd:
================================
OBS is using init scripts, not systemd style .service files. This will stay until
we will switch from SLES 11 to SLES 12 as default production platform.
openSUSE installations may use systemd (instead of sysvinit) and it should work
in general. Not working are usages like
# rcobssrcserver status
You will only get the systemd status here.
Also stopping services may not kill all processes, which leads to abstract errors
when trying to restart them. We heard also about trashed MySQL databases when using
systemd.
To avoid these problems you need switch directory to avoid the systemd mapper:
# cd /etc/init.d
# ./obssrcserver status|stop|start
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian(a)suse.de
This is on a 12.2 system where I'm attempting to run osc for the first time:
$ osc build
*** certificate verify failed at depth 1
Subject: /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert
High Assurance CA-3
Issuer: /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert
High Assurance EV Root CA
Valid: Apr 2 12:00:00 2008 GMT - Apr 3 00:00:00 2022 GMT
Fingerprint(MD5): C68B9930C8578D416F8C094E6ADB0C90
Fingerprint(SHA1): 42857855FB0EA43F54C9911E30E7791D8CE82705
Reason: unable to get local issuer certificate
Reason: certificate not trusted
A certificate in the chain failed verification
Would you like to
0 - quit (default)
1 - continue anyways
2 - trust the server certificate permanently
9 - review the server certificate
Enter choice [0129]: 9
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
06:c5:3c:43:e4:39:47:ec:d4:7c:66:da:7c:09:b9:1d
Signature Algorithm: sha1WithRSAEncryption
Issuer: C=US, O=DigiCert Inc, OU=www.digicert.com,
CN=DigiCert High Assurance CA-3
Validity
Not Before: Jan 11 00:00:00 2012 GMT
Not After : Mar 20 12:00:00 2015 GMT
Subject: C=US, ST=Utah, L=Provo, O=Novell, Inc., OU=IS&T,
CN=*.opensuse.org
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:e0:55:90:91:8d:0d:7c:a8:37:61:59:78:13:23:
bf:9e:48:29:b0:8c:c7:cf:da:76:1c:48:7c:cd:eb:
49:06:35:85:65:1f:28:dc:b1:f0:78:7b:2d:32:40:
b3:16:22:e0:70:f7:eb:f1:a6:51:ea:48:29:03:60:
ef:87:ea:24:01:79:83:d2:35:e9:5a:e0:12:14:86:
4d:21:02:73:37:8c:da:a9:33:4c:82:94:a7:9d:bf:
79:68:c7:fb:86:81:75:2e:cb:82:5a:53:2c:a9:ed:
9c:d0:92:06:6a:5b:2e:1b:42:08:24:80:02:3d:2f:
ba:30:87:f7:92:f7:62:a2:43:c1:cd:5e:5d:05:6b:
e9:ed:5e:bc:cd:1a:e6:b5:2c:9d:04:80:26:31:c2:
51:0f:aa:2a:21:34:52:0d:c8:d4:63:fe:77:14:fc:
b6:0a:d2:a8:09:99:73:dc:e2:72:57:ba:b6:1c:36:
3f:00:81:ba:40:7b:7d:32:dd:45:23:61:15:ca:4f:
f2:d2:eb:07:7b:6f:e4:e1:a0:bf:c2:01:9b:76:90:
4d:5e:a4:45:4a:d1:7a:3e:07:d4:4d:19:52:fb:d0:
c4:94:3b:62:61:f6:8d:10:0b:22:3c:30:51:4b:ee:
14:94:08:1f:fe:15:69:6d:6d:71:97:d5:cc:f0:60:
e0:19
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Authority Key Identifier:
keyid:50:EA:73:89:DB:29:FB:10:8F:9E:E5:01:20:D4:DE:79:99:48:83:F7
X509v3 Subject Key Identifier:
E2:7C:7C:F8:A8:67:AF:C4:82:C3:9C:75:29:E3:68:CE:52:F2:03:6F
X509v3 Subject Alternative Name:
DNS:*.opensuse.org, DNS:opensuse.org
X509v3 Key Usage: critical
Digital Signature, Key Encipherment
X509v3 Extended Key Usage:
TLS Web Server Authentication, TLS Web Client Authentication
X509v3 CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/ca3-g3.crl
Full Name:
URI:http://crl4.digicert.com/ca3-g3.crl
X509v3 Certificate Policies:
Policy: 2.16.840.1.114412.1.1
CPS: http://www.digicert.com/ssl-cps-repository.htm
User Notice:
Explicit Text:
Authority Information Access:
OCSP - URI:http://ocsp.digicert.com
CA Issuers -
URI:http://cacerts.digicert.com/DigiCertHighAssuranceCA-3.crt
X509v3 Basic Constraints: critical
CA:FALSE
Signature Algorithm: sha1WithRSAEncryption
bd:2f:fd:a7:e3:1e:c2:7e:8c:19:58:cc:2d:c7:fa:b0:60:0b:
81:94:5e:1e:3d:94:96:ae:2d:0f:c3:1c:21:6a:ad:2b:1e:dc:
40:2b:ee:52:8b:0b:f4:83:d5:68:3e:7e:70:05:50:c3:41:ab:
61:ed:4b:2b:f0:a0:32:6e:51:52:53:ae:79:37:46:27:a0:b3:
d9:f6:68:bd:02:df:7a:a2:1d:f9:a9:5e:70:1e:17:d3:1f:69:
a5:3a:95:31:27:e2:aa:f8:94:12:02:3d:d2:93:7e:ae:e8:5b:
94:06:a7:97:49:50:d4:e9:23:52:d6:64:c1:5f:af:ed:d7:9f:
cc:54:db:d9:ce:e9:93:1c:4a:6d:8a:76:ed:32:22:cf:d6:67:
a9:1a:82:5c:2d:ab:44:d4:50:b8:c0:2b:95:24:f6:be:72:b1:
82:5d:b6:2c:fa:42:55:4e:a4:59:a9:74:f0:6c:ed:a2:ab:e3:
47:f3:a4:aa:a3:fa:91:cc:7a:db:80:64:cc:2e:54:2d:9b:53:
ab:74:41:84:3b:d5:2a:1f:86:39:09:7d:5d:b8:40:83:b0:77:
5f:d2:d8:88:ee:9f:64:25:75:5e:ac:2c:50:c3:61:e4:4a:bd:
51:57:57:16:32:e9:cf:a7:54:3f:b8:f2:00:4a:fa:18:5a:2f:
a4:f2:ec:b6
It seems surprising that the cert for opensuse.org is not recognized
on an opensuse.org machine. My .oscrc says:
[general]
apiurl = https://api.opensuse.org
su-wrapper = sudo
extra-pkgs = vim ncurses-utils
build_repository = openSUSE_12.2
Version of ca-certificates is 1.19-1.1.
Any thoughts?
-Archie
--
Archie L. Cobbs
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
Since I am new with obs, I am asking for some directions.
Questions:
* Which is the status of the proposed workflow for git:
http://en.opensuse.org/openSUSE:Build_Service_Concept_GitUpstreamSupport
* In case of using the separated workflow, is there an easy way to
add/delete files using the information of the new tarball? Assuming
the building dependencies are the same, the only difference would be
these changes (adding/deleting files, if I understand correctly). For
adding, I think I could use something extreme like: osc add `find .`.
But for deleting... it may be more complicated.
* Is there an example of a package which use cmake? Particularly, I
would like to have an example for a library.
* For a ubuntu package, for example, will the system generated a
repository with all the dependencies ready and possible to be added as
a repository into /etc/apt/sources.list? Or will the user need to
install all the dependency manually? What about the unnecessary
dependencies (like packages that are already in default repositories)?
Sorry but I couldn't find this information in the wiki. Another option
could be something similar to: "Create Patterns" (but for Ubuntu, and
other distributions).
http://en.opensuse.org/openSUSE:Build_Service_Tutorial#Create_Patterns
Best regards, and thanks in advance!
--
Spe
--
Spe
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org