Hi,
once again I found weird behaviour when accepting MR release requests
and I'm not sure if the current state is sane.
I've accepted the following two requests via webui:
https://build.opensuse.org/request/show/242452https://build.opensuse.org/request/show/242453
For both I got an Internal Server Error page :-(
Now it seems both requests were correctly accepted and were put into the
maintenance project.
But still I see both requests as "open" in my task view.
Is this a known issue? Do I need to clean up something?
Thanks,
Wolfgang
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I'm getting unresolveable packages on my first attempt to build something
on the RH7 image, it says it's missing groff and libidn-devel. My own
CentOS 7 VMs appear to include those packages (and they're the same as
what they were called on RH6/CentOS6), so is there something off about the
package list at this point?
It doesn't exactly even spin up the VM at all to do the build, so it seems
to be based on a separately defined list of what's known to be available
to it.
-- Scott
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hey I have tried to build packages on our own OBS Appliance instant.
But they all get to here:
[ 2s] /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_3/root,if=none,id=disk,serial=0,cache=unsafe -device ide-hd,drive=disk -drive file=/var/cache/obs/worker/root_3.swap,if=none,id=swap,serial=1,cache=unsafe -device ide-hd,drive=swap -smp 1
[28806s] qemu: terminating on signal 15 from pid 13820
Job seems to be stuck here, killed. (after 28800 seconds of inactivity)
[28806s] No buildstatus set, either the base system is broken (glibc/bash/perl)
[28806s] or the build host has a kernel or hardware problem...
And then get stuck, what can I/WE do?
- Lars Nielsen
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello All,
I'm linking a number of packages from d:l:python to
server:database:postgresql to fulfill dependencies for SLE_11. One of
these packages, python-nose, is dependent on python-coverage, which is
also a linkpac, is built and published for SLE in the postgresql repo
yet is still listed as unresolvable for python-nose. Typically once a
package is finished building it's immediately available within said
repo but it's been nearly an hour and still unresolvable and it's been
published.
Any thoughts on why this is?
--
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 was an update in KIWI, making it possible to build tar.gz able to
be loaded to docker as image. I have not tested yet, but I think that it
is available in OBS now.
When OBS is used to build RPM, one can add http-repo to his package
manager and use RPMs directly. So, what do you think? Should there be a
way to automatically load images to a registry? But this leads to the
new problem, the build history must be kept. So, sequential builds must
be represented as different tagged image layers.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello again.
We have our own instance of OBS Appliance, where we want to allow access
to github by git
in a waf script (python). We currently get this output:
[ 1s] Resolve dependency sak : Command
['/usr/bin/git', 'clone', 'https://github.com/steinwurf/sak.git',
'/home/abuild/rpmbuild/BUILD/kodo-c-bindings/bundle_dependencies/sak-1bdcea/master']
returned 128
is there anyone to solve this problem and if yes how?
Thanks in advance
Lars Nielsen
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hey.
I am trying to build a package for Debian 6.0 and 7.0 and I get this error:
[ 45s] Python version not supported: (2, 6, 6), required
minimum version: 2.7
My different files are here:
https://build.opensuse.org/package/show/home:looop/kodo-c-bindings
From what I can tell I do require Python3 in all the relevant files and
build dependencies,
are there something I am missing or ?
Thanks in advance
Lars Nielsen
Student programmer Steinwurf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
First of all, I wan't to say thank to the team, it's a very helpfull
tool to create packages and to contribute to the open-source.
I'm currently working a lot with _service with github repository.
It work fine, but I wan't to know 3 thinks about that.
1. Do you have any scan mode for auto-detecting push on git repository ?
It can be an option for reduce builds... Or also can be scan each
day/week something like that.
2. The second, as I using services, I push the file on a github
repository. But I neeed to copy it on my workspace.
Is it possible to give an URL to get _service, and after other files
on source code repository ?
Youo can refers to my tests here:
https://build.opensuse.org/package/show/home:MarcAntoineArnaud/AvTranscoder
3. Is it possible also to select tags on a github repo ?
Looking the libav project tags: https://github.com/libav/libav/releases
It can be great if the stable packages are based on releases presents
on repositories.
We require more on a developer repository for beta testing develop
branch. But also providing stable packages based on releases.
Thanks,
--
Marc-Antoine
| e: arnaud.marcantoine(a)gmail.com
| tel: 06-84-71-84-45
| ohloh: http://bit.ly/1iwtlsU
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org