Hello,
Long running compilation can now leverage ccache[1] to speed up the
build process. This feature can be enabled per package in the project
config:
BuildFlags: useccahe:<packagename>
example:
https://build.opensuse.org/projects/home:sjamgade:branches:science:machinel…
Once enabled per package, it will be enabled for all architectures and
repositories.
https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.prjconfig.…
(grep ccache)
---
The ccache tar file is collected only on *successful builds with changed
result*. It is extracted for every build at /.ccache/ if enabled.
This build artifact is not versioned and only the latest tar is stored.
It can be downloaded from the webui or osc.
https://build.opensuse.org/package/binaries/home:sjamgade:branches:science:…
osc getbinaries --ccache -M standard
home:sjamgade:branches:science:machinelearning tensorflow
openSUSE_Tumbleweed x86_64 _ccache.tar osc getbinaries --ccache $prj
$pkg $repo $arch _ccache.tar
This archive can be further used for local builds too.
osc build --pkg-ccache /full/path/to/_ccache.
(please use the latest osc)
---
Ccache config file is stored in /.ccache/ccache.conf and is writable by
the build user. So, it could also be disabled (or configured as per
package requirements)
echo "disable = true" >> /.ccache/ccache.conf
For possible build time comparisons:
https://build.opensuse.org/packages/tensorflow:standard/job_history/home:sj…https://w3.nue.suse.com/~sjamgade/ccachereport.html
Thank you,
Sumit Jamgade and OBS Team
[1] - https://ccache.dev/
PS:
Some packages (eg: tensorflow) need extra plumbing in spec file to
enable access to /.ccache and use of ccache cmd:
export CC_PREFIX=ccache;
ln -s /.ccache/ ~/.ccache
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi OBS users,
we need to do a little database maintenance on Saturday at 21:00 UTC.
The buildservice will not be available for about 30 minutes.
The build service will still schedule and finish builds in that time,
but the API and the Web UI will not be available.
Thanks for your understanding and have a nice weekend,
Michael.
--
Michael Schroeder SUSE Software Solutions Germany GmbH
mls(a)suse.de GF: Felix Imendoerffer HRB 36809, AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
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'm struggling to build a package with the ppc64 architecture for
openSUSE:Factory:PowerPC locally for testing purposes. I always get
> osc build --no-verify openSUSE_Factory_PowerPC ppc64
[...]
[ 2s] [32/32] preinstalling rpm...
[ 2s]
[ 2s] initializing rpm db...
[ 2s] chroot: failed to run command No such file or directory
I'd like to build devel:languages:python/python-typed-ast locally
because of https://bugzilla.suse.com/show_bug.cgi?id=1171573 for
debugging purposes. Adding --clean to the command does not make a
difference. Does someone know how I can fix the problem? Any help is
appreciated.
best wishes,
Sebastian
Hi,
I wonder, where the project.repo files are gone in a local OBS instance?
Aren't they generated anymore?
My obs is 2.10.7 on 15.1.
Pete
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
OBS 2.10.7 released
===================
This minor release is fixing a security issue where the application
could be manipulated into processing an insecure or cross-origin request.
* Frontend:
- CVE-2020-8184: Percent-encoded cookies can be used to overwrite
existing prefixed cookie names.
Kind regards,
Your OBS Team
--
Eduardo Navarro <enavarro(a)suse.com>
Open Build Service Frontend Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nürnberg
Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
I am trying to provide a distribution (SLES15) in a local OBS instance without using interconnect.
For this I copied "meta" and "project config" from both SUSE:SLE-15-SP1:GA and SUSE:SLE-15-SP1:Update.
After that I adapted the DoD repositories to use the SUSE Manager as package source.
I also removed some repositories I don't have a subscription for (HPC, Livepatching), and some I don't need.
For everything to work properly I had to mirror the complete repo "SLE-Module-Development-Tools-OBS" with "obs_mirror_project".
Everything works as planned. A Kiwi-Template against GA has all packages from "Install DVD" and a kiwi-template against Update has the newest packages.
But I have some problems with understanding. 😊
- Where does the content of the "SLE-Module-Development-Tools-OBS" repository come from?
- This repo is available in both the :GA project and the :Update project - are they identical?
- Do I have to update this obs repo regularly?
- Furthermore I don't understand the existence of a "pool" or "pool-sp2" repository - what is it for?
- Or also, why does the repo refer to the previous SP project (here SUSE:SLE-15:Update) - do I really need the old packages?
Thanks for the explanations.
Greetings Andre
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
Starting with helm v3, there is a way to publish container charts as
OCI container registry artifacts rather than inside a chart museum.
details about that can be found here:
https://helm.sh/docs/topics/registries/
if there would be support in the build service to 'build' a chart
(submitted as a source package, maybe with a special charts.tar.gz
tarball or the like), which would then produce a container image that
can be published into the OBS connected registry (including signing!),
then that would make life easier for those that want to use the Open
Build Service for cloud native application development.
Is there any plan around that? I wasn't able to find something related
in the issue tracker. From a 500000 foot view this seems small work,
but I'm not very engrained with the details of how much work it is to
add a new build type and make it map to container building using
'helm' as a builder tool.
Also the signing part probably has many more items to consider, but it
would be a key value add for me.
Thanks,
Dirk
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Good Day
Can anyone help with the how-to please.
Kind Regards,
Sean Fabian
Chief Operating Officer
Office +27126585182 | Mobile +27790155514 | Email sean.fabian(a)pfortner.co.za | Web www.pfortner.co.za
Hey all,
So I've started building stuff for Ubuntu 20.04, and I've discovered
that a number of packages depend on a tool called "ucf" that is
written in shell script that requires Bash, but does not have the
dependency declared, so build environments fail with errors like the
following:
[ 136s] [193/242] installing php7.4-common-7.4.3-4ubuntu1
[ 136s] /usr/bin/ucf: line 346: getopt: command not found
[ 136s] dpkg: error processing package php7.4-common (--install):
[ 136s] installed php7.4-common package post-installation script
subprocess returned error exit status 127
[ 136s] Errors were encountered while processing:
[ 136s] php7.4-common
[ 136s] exit ...
To fix this, we need "Preinstall: bash" to be added so that it's
included early and everything works.
Thanks in advance and best regards!
--
真実はいつも一つ!/ 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
I am unable to log into the OBS through the web portal today; it worked yesterday.
The error message I initially get is "The username/password combination you entered is invalid. Please try again, or recover it from here."
I am sure I used the correct username/password (it still works on the wiki, forum, bugzilla, and osc) but I tried the recovery link anyway, and got the following message:
An error occurred
Internal server error: The service is temporarily not available.
Server error message:
The connection to the server could not be established. Please try again later. Error message was: (Could not send request: error(113, 'No route to host'))
--
Rosanne DiMesio <dimesio(a)gmail.com>
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org