On Dienstag, 20. März 2018, 09:39:46 CET wrote Dmitry Ivanov:
> >
> > Arch Core seems to be really not enough anymore to build anything,
> > so I dropped it from our simple repo list.
> >
> > i586 seems to be dropped as well.
> >
> > What do you miss when building against Extra?
>
> One of my packages requires qtkeychain <https://www.archlinux.org/packages/community/x86_64/qtkeychain/> which is a part of Community repo, not Extra. But it’s not really the point of my previous message, the point is that the web interface won’t allow me to enable neither Arch Extra nor Arch Community: there any three checkboxes for Arch in «Add repositories» page and whichever ones I select, I end up with only «Arch:Core» within the list of my project's repositories. It seems to be a bug of the web interface. Is is possible to enable Extra/Community repositories using osc command line tool?
It does not make sense to have them in parallel. Just enable the community one, if it
is okay for you to go with the lowest trust level. It includes all the packages from
Extra and Core as well.
--
Adrian Schroeter
email: adrian(a)suse.de
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, 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,
I'm trying to branch old revisions of a set of packages and can't figure
out how to do that.
An attempt to branch a revision fails:
osc -d branch -r 131 network openvswitch
POST https://api.opensuse.org/source/network/openvswitch?cmd=branch&rev=131
BuildService API error: failed to branch: conflict in file openvswitch.spec
Similar issue happens when I try to see files of the revision in Web UI:
https://build.opensuse.org/package/show/network/openvswitch?rev=131
The error header on the top is:
Files could not be expanded: conflict in file openvswitch.spec
However Web UI lets me to see the revision if I click on show unmerged
sources (which adds expand=0 parameter).
https://build.opensuse.org/package/show/network/openvswitch?expand=0&rev=131
If I then click "Branch package" and tick "Stay on current revision
(#131)", it makes a POST request:
utf8=%E2%9C%93&authenticity_token=<TOKEN>&linked_project=network&linked_package=openvswitch&target_project=home%3Aroolebo%3Abranches%3Anetwork&target_package=openvswitch¤t_revision=false&autocleanup=true&commit=Ok
And then proceeds with branch creation but copies the latest revision of the
files instead of the one I asked it.
I also tried to specify --link=base:
osc -d branch --linkrev=base -r 131 network openvswitch
POST https://api.opensuse.org/source/network/openvswitch?linkrev=base&cmd=branch…
BuildService API error: failed to branch: conflict in file openvswitch.spec
What should I do to branch an old revision?
Thank you,
Roman
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Repositories: Arch Community is really Arch Core!
This is a bug, I think.
If you check all
https://build.opensuse.org/project/add_repository_from_default_list/home:ri…
in:
Arch distributions
check Arch Core check Arch Extra check Arch Community
you only get *two* repositories: Arch and Arch_Extra. Arch_Community
is not there!
Can you fix it???
--
Rick Richardson rickrich(a)gmail.com
Linux printer drivers for JBIG (GDI printers): Konica Minolta magicolor,
HP LaserJet, Samsung, Xerox, Lexmark, and Oki.
http://foo2zjs.rkkda.com/
Linux tools for geocaching http://geo.rkkda.com/
Gnome Manual Duplex http://sourceforge.net/projects/g-manual-duplex/
--
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 think build.opensuse.org has a setup problem.
Previously, my home:seife:testing repo (where I basically test my
factory contributions) had a vendor tag of
"obs://build.opensuse.org/home:seife".
Today I was trying to zypper dup and noticed many packages only
resolvable with vendor changes from obs://...home:seife => openSUSE.
Is there a configuration issue?
If I do "osc buildconfig home:seife:testing openSUSE_Factory",
everything looks as it should.
--
Stefan Seyfried
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi again!
We are happy to announce the first beta release of the upcoming Open
Build Service (OBS) version 2.9.
As a highlight we included the ec2 cloud upload that allows you to
upload images to the Amazon Web Services (AWS).
More infrmation can be found in our recent blog post:
http://openbuildservice.org/2018/03/01/cloud-upload/
Other highlights are the Studio Express features, an
improved workflow for producing appliance images in OBS. A message bus,
supported by RabbitMQ, to help you connect your own tools to what is
happening inside the OBS. And a much improved notifications system to
keep you up to date with OBS.
More information
----------------
For detailed information of the changes we made please have a look into
the 2.9 Release Notes:
https://github.com/openSUSE/open-build-service/blob/2.9/ReleaseNotes-2.9
It is also recommended to read these before updating your OBS instance!
Setting up the ec2 cloud uploader
---------------------------------
You can find information about how to set up the cloud uploader service
in our admin guide:
http://openbuildservice.org/help/manuals/obs-admin-guide/obs.cha.installati…
Try OBS 2.9 RC 2
----------------
Those of you that don't want to install our release (yet) can have a
peek at https://build.opensuse.org, our reference server.
Install 2.9 RC 2
----------------
Please read our setup instructions
https://github.com/openSUSE/open-build-service/blob/2.9/README.md#installat…
or better yet, use our appliance
http://download.opensuse.org/repositories/OBS:/Server:/2.9/images/
Update to 2.9 RC 2
------------------
We do not recommend this for critical production instances but if you
already have a running OBS installation and want to update it to this
beta, please read also the README.UPDATERS
https://github.com/openSUSE/open-build-service/blob/2.9/dist/README.UPDATERS
file about the necessary steps.
OBS Appliance users who have setup their LVM
http://openbuildservice.org/download/#appliance_config
can just replace their appliance image without data loss. The migration
will happen automatically.
OBS 2.9 Final
-------------
We look forward to release the final 2.9 version at the end of this week.
We hope you like this RC and look forward to your feedback, here on this
list, on IRC or by bug reports in GitHub.
Your Open Build Service Team
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hey,
I'm trying to do package builds with my internal OBS 2.8 system
against Ubuntu 18.04.
We have our setup such that we have an "Internal:BuildRoot" project
that provides a few packages that our packages can depend on at
build-time. The project doesn't publish, but it is set up to be usable
for build roots so that useful sets of macros and such are available.
In dependent projects that need packages from here, we do something like this:
<repository name="xUbuntu_18.04">
<path project="Internal:BuildRoot" repository="xUbuntu_18.04"/>
<path project="openSUSE.org:Ubuntu:debbuild" repository="Ubuntu_18.04"/>
<path project="openSUSE.org:Ubuntu:18.04" repository="universe"/>
<arch>x86_64</arch>
</repository>
For every other distribution, this results in when a spec file
requires one of the packages in there, it is able to successfully
resolve it and start the build. However, when we're targeting Ubuntu
18.04, I get the following from the OBS resolver instead: "nothing
provides packager-env". The "packager-env" is a virtual name provided
by a package called "packager-env-obs", and in other distribution
targets, this works.
The failure also affects "osc build", presumably because it relies on
the OBS service to define the build root in the buildinfo...
Anyone have any ideas what's going on here?
--
真実はいつも一つ!/ Always, there's only one truth!
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
(my second mail. my first mail got caught by the Mlmmj program)
I'm new to this so please bear with me. My goal is to build a package
that is stable and up to date, and one package that tracks the git-repo
and build nightly (or at least weekly) versions. And I also configured
the project to build for Ubuntu as it is what I've got in my studio
since Jacklab was discontinued.
I seem to not be able to build a package (muse). Not even the native rpm
for opensuse tumbleweed. I've tried both to branch the package from an
earlier version and also create a new one. I also removed two packages
(ccaudio2) from the spec file when I created a new package.
This is the problem I run into. It can't cd into a the main dir for the
package. Funny enough it built right of the bat when I branched the
package. I don't understand why it can't cd to the directory. If I run
the commands manually it's no problem.
[ 90s] + /usr/bin/gzip -dc /home/abuild/rpmbuild/SOURCES/muse-3.0.2.tar.gz
[ 90s] + /usr/bin/tar -xof -
[ 91s] + STATUS=0
[ 91s] + '[' 0 -ne 0 ']'
[ 91s] + cd muse-3.0.2
[ 91s] /var/tmp/rpm-tmp.9tyBTh: line 34: cd: muse-3.0.2: No such file
or directory
[ 91s] error: Bad exit status from /var/tmp/rpm-tmp.9tyBTh (%prep)
https://build.opensuse.org/package/show/home:aggplanta/muse3_deb.
https://build.opensuse.org/package/live_build_log/home:aggplanta/muse3_deb/…
Cheers,
-- /bengan
--
/bengan
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I have a project that inherits the target repositories. Is it possible
to add an additional repository to a specific project? Ideally it will
still build for the repositories it inherited. But it will also build
for the additional target repositories. I usually work in the web GUI.
But any command that could accomplish this is interesting.
--
Roger Oberholtzer
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
the builtin search function doesn't seem to work in our internal obs 2.8 instance.
It fails with
500: Internal Server Error
It also allows to search within various external systems.
Can search into external systems be disabled?
How to make internal search work?
In the logs I see:
I, [2018-03-01T08:07:30.069322 #1051] INFO -- : [3c5c7815-d750-4e5c-9324-672c2d9df041] [1051:29239.76] Started GET "/search?utf8=%E2%9C%93&search_text=test&commit=Submit+Query&issue_tracker=bnc&issue=&project=0&project=1&package=0&package=1&name=0&name=1&title=0&description=0&attrib_type_id=" for 10.10.10.249 at 2018-03-01 08:07:30 +0100
I, [2018-03-01T08:07:30.080704 #1051] INFO -- : [3c5c7815-d750-4e5c-9324-672c2d9df041] [1051:29239.77] Processing by Webui::SearchController#index as HTML
I, [2018-03-01T08:07:30.080953 #1051] INFO -- : [3c5c7815-d750-4e5c-9324-672c2d9df041] [1051:29239.77] Parameters: {"utf8"=>"✓", "search_text"=>"test", "commit"=>"Submit Query", "issue_tracker"=>"bnc", "issue"=>"", "project"=>"1", "package"=>"1", "name"=>"1", "title"=>"0", "description"=>"0", "attrib_type_id"=>""}
I, [2018-03-01T08:07:30.132015 #1051] INFO -- : [3c5c7815-d750-4e5c-9324-672c2d9df041] [1051:29239.83] Completed 500 Internal Server Error in 51ms (ActiveRecord: 0.0ms | Backend: 0.0ms | XML: 0.0ms)
F, [2018-03-01T08:07:30.147233 #1051] FATAL -- : [3c5c7815-d750-4e5c-9324-672c2d9df041] [1051:29239.84]
F, [2018-03-01T08:07:30.147515 #1051] FATAL -- : [3c5c7815-d750-4e5c-9324-672c2d9df041] [1051:29239.84] ThinkingSphinx::ConnectionError (Error connecting to Sphinx via the MySQL protocol. Error connecting to Sphinx via the MySQL protocol. Can't connect to MySQL server on '127.0.0.1' (111 "Connection refused") - SELECT *, (weight() + 100 * linked_count + -1000 * links_to_other + 1000 * is_devel + 500 * (activity_index * POW( 2.3276, (updated_at - 1519888050) / 10000000))) as adjusted_weight FROM `package_core`, `project_core` WHERE MATCH('@(name) test') AND `sphinx_deleted` = 0 AND `project_id` NOT IN (0) ORDER BY `adjusted_weight` DESC LIMIT 0, 20 OPTION field_weights=(name=10, title=2, description=1), max_matches=15000, ranker=sph04; SHOW META):
F, [2018-03-01T08:07:30.147640 #1051] FATAL -- : [3c5c7815-d750-4e5c-9324-672c2d9df041] [1051:29239.84]
F, [2018-03-01T08:07:30.147747 #1051] FATAL -- : [3c5c7815-d750-4e5c-9324-672c2d9df041] [1051:29239.84] app/controllers/webui/search_controller.rb:82:in `search'
[3c5c7815-d750-4e5c-9324-672c2d9df041] app/controllers/webui/search_controller.rb:7:in `index'
[3c5c7815-d750-4e5c-9324-672c2d9df041] config/initializers/wrap_parameters.rb:38:in `call'
==> /srv/www/obs/api/log/apache_access.log <==
10.10.10.249 - - [01/Mar/2018:08:07:30 +0100] "GET /search?utf8=%E2%9C%93&search_text=test&commit=Submit+Query&issue_tracker=bnc&issue=&project=0&project=1&package=0&package=1&name=0&name=1&title=0&description=0&attrib_type_id= HTTP/1.1" 500 4322
==> /srv/www/obs/api/log/production.log <==
I, [2018-03-01T08:07:30.268687 #1051] INFO -- : [1c81b044-0d0d-4966-b10d-43169b6b070d] [1051:29239.96] Started GET "/favicon.ico" for 10.10.10.249 at 2018-03-01 08:07:30 +0100
F, [2018-03-01T08:07:30.272464 #1051] FATAL -- : [1c81b044-0d0d-4966-b10d-43169b6b070d] [1051:29239.97]
F, [2018-03-01T08:07:30.272791 #1051] FATAL -- : [1c81b044-0d0d-4966-b10d-43169b6b070d] [1051:29239.97] ActionController::RoutingError (No route matches [GET] "/favicon.ico"):
F, [2018-03-01T08:07:30.272886 #1051] FATAL -- : [1c81b044-0d0d-4966-b10d-43169b6b070d] [1051:29239.97]
F, [2018-03-01T08:07:30.273059 #1051] FATAL -- : [1c81b044-0d0d-4966-b10d-43169b6b070d] [1051:29239.97] actionpack (5.0.1) lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] actionpack (5.0.1) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] railties (5.0.1) lib/rails/rack/logger.rb:36:in `call_app'
[1c81b044-0d0d-4966-b10d-43169b6b070d] railties (5.0.1) lib/rails/rack/logger.rb:24:in `block in call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] activesupport (5.0.1) lib/active_support/tagged_logging.rb:69:in `block in tagged'
[1c81b044-0d0d-4966-b10d-43169b6b070d] activesupport (5.0.1) lib/active_support/tagged_logging.rb:26:in `tagged'
[1c81b044-0d0d-4966-b10d-43169b6b070d] activesupport (5.0.1) lib/active_support/tagged_logging.rb:69:in `tagged'
[1c81b044-0d0d-4966-b10d-43169b6b070d] railties (5.0.1) lib/rails/rack/logger.rb:24:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] actionpack (5.0.1) lib/action_dispatch/middleware/request_id.rb:24:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] rack (2.0.1) lib/rack/method_override.rb:22:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] rack (2.0.1) lib/rack/runtime.rb:22:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] activesupport (5.0.1) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] actionpack (5.0.1) lib/action_dispatch/middleware/executor.rb:12:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] rack (2.0.1) lib/rack/lock.rb:15:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] rack (2.0.1) lib/rack/sendfile.rb:111:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] hoptoad_notifier (2.4.11) lib/hoptoad_notifier/user_informer.rb:12:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] railties (5.0.1) lib/rails/engine.rb:522:in `call'
[1c81b044-0d0d-4966-b10d-43169b6b070d] railties (5.0.1) lib/rails/railtie.rb:193:in `public_send'
[1c81b044-0d0d-4966-b10d-43169b6b070d] railties (5.0.1) lib/rails/railtie.rb:193:in `method_missing'
[1c81b044-0d0d-4966-b10d-43169b6b070d] passenger (5.0.30) src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:97:in `process_request'
[1c81b044-0d0d-4966-b10d-43169b6b070d] passenger (5.0.30) src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:152:in `accept_and_process_next_request'
[1c81b044-0d0d-4966-b10d-43169b6b070d] passenger (5.0.30) src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:113:in `main_loop'
[1c81b044-0d0d-4966-b10d-43169b6b070d] passenger (5.0.30) src/ruby_supportlib/phusion_passenger/request_handler.rb:416:in `block (3 levels) in start_threads'
[1c81b044-0d0d-4966-b10d-43169b6b070d] passenger (5.0.30) src/ruby_supportlib/phusion_passenger/utils.rb:113:in `block in create_thread_and_abort_on_exception'
So I searched for "sphinx" and only found this:
http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.admin.…
When I try to start the searchd.service, it fails:
● searchd.service - Sphinx - SQL Full Text Search Engine
Loaded: loaded (/usr/lib/systemd/system/searchd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2018-03-01 08:19:24 CET; 4min 44s ago
Process: 13214 ExecStart=/usr/bin/searchd --nodetach --config /etc/sphinx/sphinx.conf (code=exited, status=1/FAILURE)
Main PID: 13214 (code=exited, status=1/FAILURE)
Mar 01 08:19:24 buildservice searchd[13214]: Copyright (c) 2001-2016, Andrew Aksyonoff
Mar 01 08:19:24 buildservice searchd[13214]: Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com)
Mar 01 08:19:24 buildservice searchd[13214]: precaching index 'test1'
Mar 01 08:19:24 buildservice searchd[13214]: WARNING: index 'test1': preload: failed to open /var/lib/sphinx/data/test1.sph: No such file or directory; NOT SERVING
Mar 01 08:19:24 buildservice searchd[13214]: precaching index 'test1stemmed'
Mar 01 08:19:24 buildservice searchd[13214]: WARNING: index 'test1stemmed': preload: failed to open /var/lib/sphinx/data/test1stemmed.sph: No such file or directory; NOT SERVING
Mar 01 08:19:24 buildservice searchd[13214]: precaching index 'rt'
Mar 01 08:19:24 buildservice systemd[1]: searchd.service: Main process exited, code=exited, status=1/FAILURE
Mar 01 08:19:24 buildservice systemd[1]: searchd.service: Unit entered failed state.
Mar 01 08:19:24 buildservice systemd[1]: searchd.service: Failed with result 'exit-code'.
Is there some documentation about this integration?
Or can I at least disable that in the ui?
--
kind regards,
Carsten Hoeger
Professional Services
Phone: +49 2761 75252 00 Fax: +49 2761 75252 30
Email: carsten.hoeger(a)open-xchange.com
-------------------------------------------------------------------------------------
Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738
Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin
Chairman of the Board: Richard Seibt
European Office:
Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718
Managing Director: Frank Hoberg
US Office:
Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA
-------------------------------------------------------------------------------------