Hey all,
While trying to build packages against a local installation of OBS, I
get the following message from the build log against
OpenSuse_Factory/x86_64:
[ 31s] booting kvm...
[ 31s] /usr/bin/qemu-kvm -no-reboot -nographic -vga none -net none
-cpu host -kernel /boot/vmlinuz -initrd /boot/initrd -append
root=/dev/sda panic=1 quiet no-kvmclock nmi_watchdog=0 rw
rd.driver.pre=binfmt_misc elevator=noop console=ttyS0
init=/.build/build -m 256 -drive
file=/var/cache/obs/worker/root_1/root,if=none,id=disk,serial=0,cache=unsafe
-device ide-hd,drive=disk -drive
file=/var/cache/obs/worker/root_1.swap,if=none,id=swap,serial=1,cache=unsafe
-device ide-hd,drive=swap -smp 1
[ 60s] [ 0.000000] tsc: Fast TSC calibration failed
[ 60s] [ 0.356000] Failed to access perfctr msr (MSR c1 is 0)
<nothing>
Is this a known issue? FWIW, I'm running the instance on an openstack
VM hosted with KVM
Cheers!
Andrew
--
--
Andrew Melo
--
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 have built OBS 2.5.2 in the SUSE 11 SP3 system, and I use the Admin login successful, but there are several problems in the use of OBS.
Could someone can help me?
I according to the http://en.opensuse.org/openSUSE:Build_Service_adding_build_targets step by step, an error occurred when I run "3) Add build config file ".
Error info is:
"
suse-chen:/usr/lib/build/configs # osc -A https://localhost meta SUSE:SLE-11:SP3 -F /usr/lib/build/configs/sles11sp2.conf
Unknown meta type. Choose one of prjconf, attribute, prj, user, pattern, pkg.
"
My /root/.oscrc info is:
[general]
apiurl = https://localhost:81
[https://localhost:81]
user = Admin
pass = opensuse
Question 1:
There is no sles11sp3.conf in the path of "/usr/lib/build/configs", the latest is sles11sp2.conf of SLES.
Is it not supports sles11sp3?
Question 2:
How could I can solve the "osc -A" failed?
Question 3:
In the step "1) Create the build target project." of http://en.opensuse.org/openSUSE:Build_Service_adding_build_targets , I use web create successful,
But failed with cmd.
Error info is:
"
suse-chen:/srv/obs/build # osc meta -e prj chentest
Failed to reach a server:
[Errno 111] Connection refused: 'https://186.100.8.233:81/source/chentest/_meta'
"
In the "1) Create the build target project." it is written:
"
You should also have the following directory structure under /srv/obs/build
my-distro/standard/x86_64/
my-distro/standard/i586/
"
I create project with web, but these is no project named dir in the path "/srv/obs/build", so I use "mkdir" to create it.
Thank you very much.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
At some point osc build --no-checks used to work with sles11sp3 repos.
But right now osc passes --nocheck to rpmbuild, which is an unknown
option in sles11sp3. As a result the local build fails.
Is this a known issue, and is my osc.rpm etc. just outdated?
Olaf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
<status code="maintainance"><summary>Sorry, api.opensuse.org is down at
the moment. If the situation persists, check the
opensuse-buildservice(a)opensuse.org mailinglist.
</summary><details/></status>
--Glenn
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I got this error recently on my OBS appliance exactly 1 year after I installed it!
Turned out the self signed certificates in the Cert direct of OBS had expired. I deleted them (and copies in /etc/pki from memory), restarted, and OBS recreated new certs. Once I copied them back to the /etc/pki directory every thing was back to normal.
Maybe the OBS devs can increase the validity of the self signed certs to 5(?) years?
Sent from my iPhone
> On 5 Jun, 2014, at 3:46 pm, "Adrian Schr?ter" <adrian(a)suse.de> wrote:
>
> On Mittwoch, 4. Juni 2014, 13:54:21 wrote Andrew Melo:
>> On Wed, Jun 4, 2014 at 1:14 PM, Smith, Kenneth
>> <ksmith15(a)jaguarlandrover.com> wrote:
>>> Hello,
>>>
>>> My OBS webui installation has become inoperable. I was logged in and
>>> browsing when I clicked a link on the ui and got "Application error
>>> 500". I restarted the obs services, no change. I rebooted the server.
>>> No change. I get the same error from another user's machine.
>>>
>>> webui production.log shows this:
>>>
>>> [INFO |# 2980] Started GET "/" for 192.168.1.60 at 2014-06-04 17:45:11 +0000
>>> [INFO |# 2980] Processing by MainController#index as HTML
>>> [INFO |# 2980] Anonymous request to /
>>> [INFO |# 2980] Completed 500 Internal Server Error in 6ms
>>>
>>> [FATAL|# 2980] OpenSSL::SSL::SSLError (SSL_connect SYSCALL returned=5
>>> errno=0 state=SSLv3 read server certificate B: certificate verify
>>> failed):
>>> lib/activexml/transport.rb:350:in `http_do'
>>> lib/activexml/transport.rb:227:in `direct_http'
>>> app/controllers/application_controller.rb:361:in `block in
>>> require_configuration'
>>> app/controllers/application_controller.rb:359:in `require_configuration'
>>>
>>> I'm not sure why I'm suddenly getting ssl errors, when I wasn't
>>> before. I'm not sure where to start in fixing this.
>>
>>
>> I'm not sure if it's related, but:
>>
>> I just moved my OBS instance to one hypervisor to another and instead
>> of moving the whole disk image,I started from a scratch hypervisor
>> image from the OBS website and then rsynced over the /srv tree from
>> the old machine. When I try to log in, I get:
>>
>> OpenSSL::SSL::SSLError (SSL_connect returned=1 errno=0 state=SSLv2/v3
>> read server hello A: unknown protocol):
>
> unknown protocol sounds like you do not talk to a SSL connection.
>
> or ruby stack does not accept the certificate and throws wrong error ...
>
>> /usr/lib64/ruby/2.0.0/net/http.rb:918:in `connect'
>> /usr/lib64/ruby/2.0.0/net/http.rb:918:in `block in connect'
>> /usr/lib64/ruby/2.0.0/timeout.rb:52:in `timeout'
>
>
>
> --
>
> Adrian Schroeter
> email: adrian(a)suse.de
>
> SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendrffer, HRB 21284 (AG Nrnberg)
> Maxfeldstrae 5
> 90409 Nrnberg
> Germany
>
>
>
> --
> To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
> To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
>
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
Sometimes I'm a little confused, and today it's because I don't know
some thing...
The questions I ask myself (and google try to answer as best he can) are
probably easy
for a lot of people :
** How can I manage a project with the same package but with 1,2,3...
versions ?
(Same specfile ?...)
** How can I manage the installation of the same package in different
versions ?
(Using /usr/local/package-{xx,xy} ?)
- When I set in a specfile the tags : BuildRequires, Requires,
Recommends,...
BuildRequires : Only useful for building the package
Requires : Dependencies required to use the program (functionalities, ...)
Recommends : Not necessary but recommended ?
Another question arises in me :
- If I use for example a librairy (%{name}-%{version}.rpm)
The building process (if I don't use *Requires: libxx >= %{version}) use
the latest version
available in the OBS repo ? (true?)
But If I had a server where I want to install this package do not has
the latest version
but an older version,
** How can I be sure the installation and use will work properly?
** How to ensure a perfect dependency management ?
Do not hesitate to tell me if I understood nothing.
And possibly if you have references that could more advanced explain how
the operation.
Thank you for your feedback
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
My OBS webui installation has become inoperable. I was logged in and
browsing when I clicked a link on the ui and got "Application error
500". I restarted the obs services, no change. I rebooted the server.
No change. I get the same error from another user's machine.
webui production.log shows this:
[INFO |# 2980] Started GET "/" for 192.168.1.60 at 2014-06-04 17:45:11 +0000
[INFO |# 2980] Processing by MainController#index as HTML
[INFO |# 2980] Anonymous request to /
[INFO |# 2980] Completed 500 Internal Server Error in 6ms
[FATAL|# 2980] OpenSSL::SSL::SSLError (SSL_connect SYSCALL returned=5
errno=0 state=SSLv3 read server certificate B: certificate verify
failed):
lib/activexml/transport.rb:350:in `http_do'
lib/activexml/transport.rb:227:in `direct_http'
app/controllers/application_controller.rb:361:in `block in
require_configuration'
app/controllers/application_controller.rb:359:in `require_configuration'
I'm not sure why I'm suddenly getting ssl errors, when I wasn't
before. I'm not sure where to start in fixing this.
--
Kind Regards
Kenneth F. Smith
-------------------
Infotainment Engineer
MSX on behalf of Jaguar Land Rover
One World Trade Center, 121 Southwest Salmon Street, 11th Floor,
Portland, Oregon, 97204
Email: ksmith15(a)jaguarlandrover.com
PGP: RSA 2048/2048 979C6B958B89909D
-------------------
Business Details:
Jaguar Land Rover Limited
Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
Registered in England No: 1672070
This e-mail and any attachments contain confidential information for a
specific individual and purpose. The information is private and
privileged and intended solely for the use of the individual to whom
it is addressed. If you are not the intended recipient, please e-mail
us immediately. We apologise for any inconvenience caused but you are
hereby notified that any disclosure, copying or distribution or the
taking of any action in reliance on the information contained herein
is strictly prohibited.
This e-mail does not constitute an order for goods or services unless
accompanied by an official purchase order.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I wonder why build-root is a global setting, instead of a per API-URL setting?
With an ~/.oscrc as shown below the build-root defaults to
/var/tmp/build-root/openSUSE_13.1-x86_64, which is not what I want..
Can this be fixed?
Olaf
[general]
packagecachedir = /abuild_disk/olaf/OSbuild-packagecache
su-wrapper = sudo nice -n -13 ionice -c 1 -t
[https://api.opensuse.org]
build-root = /abuild_disk/olaf/oscbuild/obs/%(repo)s-%(arch)s-%(project)s-%(package)s
user=$user
[https://api.suse.de]
build-root = /abuild_disk/olaf/oscbuild/ibs/%(repo)s-%(arch)s-%(project)s-%(package)s
user=$user
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
i have in some package an unresolved error:
have choice for libxml2.so.2(LIBXML2_2.5.2) needed by ???:
libxml2-2-32bit libxml2-2
Please can somebody fix this in obs?
Eric
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
