Hello All,
I'm running a private instance and I'd like to enable networking on my
workers so they can build some java apps, via maven, which need to
download pom's/war's from the net. I ask google but he wasn't much
help so I'm hoping someone here can help;-)
How can I go about doing this?
--
Later,
Darin
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi.
There is a ghost package in my OBS home project. I'm using the web interface,
not the command line one. If you go to
https://build.opensuse.org/project/show/home:jcsl:LXDE
you can see the real 10 packages in the Packages box on left side, but if you
look in the Build Results box, on the right side, you see 11 next to the
"succeeded" text. If you then click the succeeded link you find the
pcmanfm-1.2.0-beta1 package, and if you click on its link you get a Package
"pcmanfm-1.2.0-beta1" not found in project "home:jcsl:LXDE", as expected. It
even appears in the scheduled and building states when something I'm building
triggers its build (I don't know how can this be).
Any hints?
Greetings.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hm...
You have inspired me to try this on the coming weekend. :) With obs
rest/xml api, I need a tiny python script to manage all the things
out. It is easy, you're right.
2012/10/18 Jos Poortvliet <jos(a)opensuse.org>:
> On Sunday, October 07, 2012 12:09:43 Matwey V. Kornilov wrote:
>
>> Hi,
>
>>
>
>> Is there a page to see full list of submit requests, ordered by date? This
>
>> statistics is of quite interest.
>
>>
>
>> For instance, there is no reaction for two month: (It is not ok for devel:
>
>> project, I think)
>
>>
>
>>
>> https://build.opensuse.org/project/requests?project=network%3Amessaging%3Aam
>
>> qp
>
>>
>
>> I think, having such a page, such statistics, one would be able to
>
>> redistribute his power.
>
>
>
> Not a bad idea at all - it'd nice to show which projects need some help,
> which are doing very well etcetera. Maybe a top-ten of fastest SR/MR
> solvers, too ;-)
>
>
>
> Crazy idea: Adrian responded to you that it is possible to request this info
> from the API. If you got the skillzz to do that, it'd be nice to publish
> those statistics somewhere - and that part I could help with. Something like
> a weekly overview of the health of the OBS projects and stuff like that.
>
>
>
> Up for it?
>
>
>
> /Jos
--
With best regards,
Matwey V. Kornilov
http://0x2207.blogspot.com
xmpp:0x2207@jabber.ru
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Open Build Service(OBS) 2.3.4 just got released
===============================================
This is a bugfix release in first place. But also the distribuition default
target list has been updated.
This release is most important for cross build support. Building
against openSUSE 12.2 and Factory for ARM architecture works
now out-of-the-box.
OBS 2.3.4 is published in "openSUSE:Tools" project:
http://download.opensuse.org/repositories/openSUSE:Tools/
Appliances can be used as usual:
http://en.opensuse.org/openSUSE:Build_Service_Appliance
Release Notes:
==============
Feature backports:
==================
* Added "Hostarch" in _buildinfo for osc local builds of cross builds
Changes:
========
* package meta creation of package copy command is not copying
relationships and devel definitions anymore.
* Added openSUSE 12.2 to default target list
* Removed openSUSE 11.4 from default target list (EOL soon)
* Fedora 15 is EOL, removed from default list
Bugfixes:
=========
* backend: allow access to access protected project repositories when
users are in both projects.
* backend: increase vrev on package source copy
* webui: fixed underscores in code listings
* webui: Do not expose user email address in anonymous mode
* obsworker: do not fail when no /etc/sysconfig/proxy exists
* build: fixed cross architecture initilisation for chroot builds
--
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,
when I am doing an osc build locally all packages that are specified in
the "BuildRequires" tags are installed in a isolated environment.
Is the same possible for packages (including their versions) needed at
runtime, i.e. specified by the "Requires" tags?
My goal is to run some unit tests of packaged software to ensure the
Requires dependencies are specified correctly without having to test it
on a separate test machine.
Best regards
Gregor
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Good news everyone .... more work for OBS and all of us :)
SLE 12 got imported. Right now only the x86_64 architecture is usable.
ppc64le will come when we have the hardware in place.
SLE 12 got added to the simple default target list in webui or when you want
to add it manually use
SUSE:SLE-12:GA / standard
repository. Please note that the former existing SUSE:SLE-12 project got removed.
--
Adrian Schroeter
email: adrian(a)suse.de
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
hello,
TL;DR: i'd like all obs-service-* tools to have a Makefile, and i'd
prefer if we could colocate all of them in a single git repository.
i want to package obs-service-* for ArchLinux. most of these tools have
no Makefile, and the build/install procedures are spelled out in their
specfiles in b.o.o. i set out to move the build scripts into Makefiles
since a) i don't fancy reproducing them in the prospective PKGBUILD
files and b) it would do zilch for the future Debian packager.
the various obs-service-* have quite simple and similar needs.
if i went with a simple Makefile per service we'd end up with the common
bits interspersed with the tool-specific ones, which i sense as fertile
ground for divergence. instead, i went for a common obs-service.mk file
which is identical among the different tools, and a GNUmakefile file to
provide that with tool-specific bits.
this arrangement makes it a bit easier to keep the common bits identical
in the various tools, even though it obviously does nothing to remove
the duplication itself; i'm not sure what/if i can do with that.
simple:
https://github.com/roman-neuhauser/obs-service-python_sdist/compare/wip-mak…
local extras:
https://github.com/roman-neuhauser/obs-service-download_files/compare/wip-m…https://github.com/roman-neuhauser/obs-service-format_spec_file/compare/wip…https://github.com/roman-neuhauser/obs-service-source_validator/compare/wip…
obs-service-download_files inspired the $(cachedirs)/install-cache code
which, on a closer look, should be local to that tool, AFAICT there's no
other consumer of that feature.
---
while the above solves the issues of packaging the various services for
different packaging formats and removes *some* of the pain of keeping
the machinery in sync, it does not solve the latter completely. even
with the syncing procedure as simple as copying a file around, i fully
expect the various copies of obs-service.mk to diverge over time.
my suggestion here would be to mvoe all the obs-service-* tools into
a single repository to bring the number of obs-service.mk copies down
to one. is there another way?
--
roman
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi folks,
I have already posted this matter in the gtk-sharp mailing list, but
the guys there suspect my issue to be related to the MonoDevelop RPM I
am using:
I am using gtk-sharp2 incl. glib-sharp2-2.12.10-85.13.x86_64 for my
Mono project and for MonoDevelop (5.0.1-110.14) itself. The issue is
that after the recent update, MD crashes a few seconds after opening
whatever project. I get the following error message:
monodevelop: symbol lookup error: /usr/lib64/libglibsharpglue-2.so:
undefined symbol: g_type_check_instance_is_fundamentally_a
The version of glib-sharp2 is the most recent I can get for my
openSuSE 12.3 machine. For MD and the Mono files incl. gtk-sharp2 I am
using Mono/Factory as a repo.
One of the gtk-sharp guys told me the instance checking routine in
libglibsharpglue had been added in May 2014:
https://mail.gnome.org/archives/commits-list/2014-May/msg08836.html
What shall I do? Thank you for any useful hints.
Kind regards
Jacek Rużyczka
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
to whom it may concern: the search page on build.o.o is currently broken
(returning 500, internal server error) and has done so quite frequently
last week.
Also I recall that the search seems to not support string with hyphens,
like "perl-macros" or anything like that. It used to not return any
results for such a search. Unfortunately I cannot test if thats still
true due to the 500 error...
Best regards,
Joschi Brauchle
Adrian Schröter <adrian(a)suse.de> writes:
> Just wanted to do something useful again this morning :)
>
> build.opensuse.org has now a new special merge tool installed,
> which will be used to merge suse style changelog files (<package>.changes).
>
> This is supposed to solve the typical breakage when you branch from some
> package and upstream and you are applying modifications.
>
Fantastic, thank you! For some reason I have one package which seems
especially prone to confuse diff3, this is a very welcome feature.
>
> --
>
> Adrian Schroeter
> email: adrian(a)suse.de
>
> SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
> Maxfeldstraße 5
> 90409 Nürnberg
> Germany
>
>
>
> --
> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
> To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
>
>
--
// Kristoffer Grönlund
// kgronlund(a)suse.com
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org