Hi,
I am new and trying local build on s390x with SLE_12_SP3 using the
following command
sudo osc build
but I get the public key not available for many packages. You can see
the output by clicking the following link
https://pastebin.com/YBQk3vGe
I know that I can use --noverify option to bypass this and builds
complete successfully when I use --noverify option but how can I fix
this? What will happen if I don't fix it?
--
Usman
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I try to build qt5.12 in our own OBS instance (running OBS version
2.9.5). When I try to upload the big complete
qt-everywhere-src-5.12.3.tar.xz tarball (~485MB) from the libqt5-qtdoc
package to the server the upload hangs forever regardless if I use osc
commit or file upload via the WEB UI.
The file never hit the /srv/obs/source directory. I did successful
upload files only a little bit smaller (~442MB) some time ago.
Here is enough disk space on the server. Free shows about 2.5 GB free
memory without buffers on the server. No errors on the logs, but also no
entry about this file in the logs. The network shows high traffic for
some tens of seconds to the obs server, then low traffic, so it seems
that the file got transfered, at least a big part oft it.
Any hints howto debug this ?
Is here a place where the file is saved temporary during the API put
operation ?
Do I need to increase some limits ?
Thanks
Karsten
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
A prefer is missing for Ubuntu 19.04:
have choice for fakeroot needed by devscripts: fakeroot pseudo (https://build.opensuse.org/package/show/home:e9925248:grandorgue/grandorgue)
Regards,
Martin
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I use the set_version service in combination with the tar_scm service to replace the version number in my spec file.
Replacing the version in the head of the spec file works, but I use the %{version} macro in the %build section and here I get the original value instead of the replaced value.
I also found out that if I grep the version from the spec file (like grep ^Version: *.spec) I also get the original value instead of the replaced one (and there is only one spec, I listed all files from the %build section).
I did not look at the source RPM but if the file is not properly rewritten, then the srpm probably contains a wrong spec file.
Did I do something wrong or does the service work differently?
Regards,
Mark
____________________________________________________________________
[TestingExpo_Footer]<http://www.testing-expo.com/europe/en/>
Besuchen Sie DSA auf der Automotive Testing Expo 2019 in Stuttgart - wir freuen uns auf Sie!
Stand 8448, 21. - 23. Mai 2019
Für Terminvereinbarungen und kostenlose Besucherausweise wenden Sie sich gerne an Frau Vanessa Sack:
Tel.: +49 2408 9492-794
E-Mail: vanessa.sack(a)dsa.de
Visit DSA at Automotive Testing Expo 2019 in Stuttgart - we look forward to welcoming you!
Booth 8448, May 21 to 23, 2019
For appointments and free visitor badges please get in touch with Ms. Vanessa Sack:
Phone: +49 2408 9492-794
Email: vanessa.sack(a)dsa.de
--
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 home:/ project,
https://build.opensuse.org/project/monitor/home:pgnd:security:netfilter
configured to build/use my own, local gcc8 project,
https://build.opensuse.org/projects/home:pgnd:security:netfilter/meta
...
<repository name="openSUSE_Leap_15.0" rebuild="transitive" block="all" linkedbuild="all">
...
==> <path project="home:pgnd:devel:gcc8" repository="openSUSE_Leap_15.0"/>
...
</repository>
...
where I've set the block="all", per
https://en.opensuse.org/openSUSE:Build_Service_Concept_build_scheduling_str…
Block mode
...
all: The default behaviour, don't start the build if a depending package is currently building.
...
Checking, the gcc8 project _is_ (re)built, in state "succeeded",
https://build.opensuse.org/project/show/home:pgnd:devel:gcc8
but my dependent ...:netfilter project is completely 'blocked',
https://build.opensuse.org/project/monitor/home:pgnd:security:netfilter?arc…
iproute2 blocked
ipset blocked
iptables blocked
libmnl blocked
libnetfilter_acct blocked
libnetfilter_conntrack blocked
libnetfilter_cthelper blocked
libnetfilter_cttimeout blocked
libnetfilter_log blocked
libnetfilter_queue blocked
libnfnetlink blocked
libnftnl blocked
shorewall blocked
xtables-addons blocked
where the blocks include gcc*; e.g., for the 'shorewall' package, the block is reported as:
gcc-PIE, gcc, binutils, libgmp10, gcc8, cpp, libstdc++6, libmpfr6, libmpc3, cpp8, libasan5, libatomic1, libgomp1, libitm1, liblsan0, libmpx2, libmpxwrappers2, libtsan0, libubsan1
checking, e.g., gcc-PIE, it's currently built & directly available as
https://build.opensuse.org/package/binary/home:pgnd:devel:gcc8/gcc/openSUSE…
and in the repos already in the same version
https://download.opensuse.org/repositories/home:/pgnd:/devel:/gcc8/openSUSE…
Same holds true for the other gcc*-built packages I've checked ...
(1) Why do the blocks appear in my ...:netfilter for packages that are available?
(2) Is there additional/different project config I need to avoid these blocks, and keep the projects in sync?
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hey everyone,
I pushed a package to OBS (mongodb) for ArchLinux which is available here:
https://build.opensuse.org/package/show/home:ItachiSan:archlinux/mongodb
but the build fails due to limited disk space.
Is it possible e.g. through package metadata to increase disk space
usage for this specific package?
Thanks in advance
Giovanni Santini
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
On 4/22/19 10:15 PM, Jiri Slaby wrote:
> On 23. 04. 19, 7:14, PGNet Dev wrote:
>> patches.addon/series.conf
>
> Sorry, my bad. Remove the .conf suffix.
>
ugh. I should've looked 1st in kernel-source > apply-patches !
as soon as back-home's back up, I'll put it in place.
thx
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I've added Ubuntu 19.04 to my project, but the build shows as unresolvable. Nothing is being downloaded.
--
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
Hello list,
I'm trying to trigger a rebuild for a package in my home project but I cannot
get it to work.
When I click 'Trigger Rebuild' on [1], I'm redirected to the overview page of
the package and the message
Triggered rebuild for home:cney/pijul successfully.
is shown at the top. Nothing happens after though. I tried from the command
line with osc as well, but no rebuild happens.
% osc -d rebuild home:cney pijul openSUSE_Tumbleweed x86_64
POST
https://api.opensuse.org/build/home:cney?cmd=rebuild&arch=x86_64&repository…
ok
Is manually triggering a rebuild allowed/forbidden for home projects? I
couldn't find anything on the topic with a quick web search.
Thanks and cheers
[1]
https://build.opensuse.org/package/live_build_log/home:cney/pijul/openSUSE_…
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org