Hi,
At the onset, thanks for your wonderful work on OBS!
I have a local OBS instance (using the appliance download) which currently only builds x86_64 binaries. I'm now trying to build a Raspbian armv7l binary, but running into issues -
* The Status Monitor shows both i586 and armv7l as "dead". Do I need to enable these arch in some config file? Or is some OBS service failing at startup that I need to start manually? * The project page shows the arm and i586 repository state as "Unknown", while the package page does not show that distro/arch combinations at all - not even when I click on "show excluded" * I don't have a armv7 worker, but from some googling it looked to me that armv7 can be built on a x86_64 worker using cross-builds. After further googling, I added the following to my project config, but still no luck - %ifarch armv7l Preinstall: qemu-linux-user Runscripts: qemu-linux-user Hostarch: x86_64 Macros: %qemu_user_space_build 1 :Macros %endif
Any help or suggestions is highly appreciated.
Thanks in advance, Srivats
On Okt 29 2019, Srivats P wrote:
- The Status Monitor shows both i586 and armv7l as "dead". Do I need
to enable these arch in some config file? Or is some OBS service failing at startup that I need to start manually?
osc api -e /configuration
Add the architecture to <schedulers>.
Andreas.
Thanks Andreas for the quick reply.
Both i586 and armv7l are already enabled in the architectures.
What else can I check?
Srivats
On Tue, Oct 29, 2019 at 7:00 PM Andreas Schwab schwab@suse.de wrote:
On Okt 29 2019, Srivats P wrote:
- The Status Monitor shows both i586 and armv7l as "dead". Do I need
to enable these arch in some config file? Or is some OBS service failing at startup that I need to start manually?
osc api -e /configuration
Add the architecture to <schedulers>.
Andreas.
-- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
Did you restart the scheduler?
Andreas.
Restarted the scheduler service and now status monitor shows i586 and armv7l are now shown as running - not sure how since these were already enabled even before I started the OBS VM. I did not have to change the configuration file.
But builds are still not happening despite clicking on "Trigger rebuild" in the WebUI.
Srivats
On Tue, Oct 29, 2019 at 7:17 PM Andreas Schwab schwab@suse.de wrote:
Did you restart the scheduler?
Andreas.
-- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
Facing a new problem today -
My local OBS Instance is not able to connect to the public instance. All my packages show "Broken: Interconnect Error: Unknown host: api.opensuse.org".
I am able to ping "api.opensuse.org" successfully from the OBS server command line.
I noticed that https://api.opensuse.org/about shows 2.11 alpha deployed yesterday Oct 29th. I have 2.10 - could that be a possible cause? Are API versions compatible?
Any and all help would be greatly appreciated.
Thanks in advance, Srivats
On Tue, Oct 29, 2019 at 7:35 PM Srivats P srivatsp@gmail.com wrote:
Restarted the scheduler service and now status monitor shows i586 and armv7l are now shown as running - not sure how since these were already enabled even before I started the OBS VM. I did not have to change the configuration file.
But builds are still not happening despite clicking on "Trigger rebuild" in the WebUI.
Srivats
On Tue, Oct 29, 2019 at 7:17 PM Andreas Schwab schwab@suse.de wrote:
Did you restart the scheduler?
Andreas.
-- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
I got help over IRC and was told that the difference in API versions should not cause a problem.
Also, I was able to fix the "Broken: Interconnect Error: Unknown host:api.opensuse.org" by deleting the interconnect, the repos and recreating them.
At least now my armv7 build is starting, but bailing out very early -
I have the following in the project config to crossbuild armv7 on a x86_64 worker %ifarch armv7l Hostarch: x86_64 Macros: %qemu_user_space_build 1 :Macros %endif
This is what the build log shows - [ 21s] chroot: failed to run command '/sbin/ldconfig': No such file or directory [ 21s] [1/343] installing autotools-dev-20180224.1 [ 21s] chroot: failed to run command 'dpkg': No such file or directory [ 21s] exit ...
Should it be using chroot? Or kvm?
Any help or pointer is highly appreciated.
Thanks in advance, Srivats
On Wed, Oct 30, 2019 at 6:46 PM Srivats P srivatsp@gmail.com wrote:
Facing a new problem today -
My local OBS Instance is not able to connect to the public instance. All my packages show "Broken: Interconnect Error: Unknown host: api.opensuse.org".
I am able to ping "api.opensuse.org" successfully from the OBS server command line.
I noticed that https://api.opensuse.org/about shows 2.11 alpha deployed yesterday Oct 29th. I have 2.10 - could that be a possible cause? Are API versions compatible?
Any and all help would be greatly appreciated.
Thanks in advance, Srivats
On Tue, Oct 29, 2019 at 7:35 PM Srivats P srivatsp@gmail.com wrote:
Restarted the scheduler service and now status monitor shows i586 and armv7l are now shown as running - not sure how since these were already enabled even before I started the OBS VM. I did not have to change the configuration file.
But builds are still not happening despite clicking on "Trigger rebuild" in the WebUI.
Srivats
On Tue, Oct 29, 2019 at 7:17 PM Andreas Schwab schwab@suse.de wrote:
Did you restart the scheduler?
Andreas.
-- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
On Nov 04 2019, Srivats P wrote:
I have the following in the project config to crossbuild armv7 on a x86_64 worker %ifarch armv7l Hostarch: x86_64 Macros: %qemu_user_space_build 1 :Macros %endif
Did you Preinstall: qemu-linux-user (or its debian equivalent)?
Andreas.
Did you Preinstall: qemu-linux-user (or its debian equivalent)?
When I add that, I get an "unresolvable, nothing provides qemu-linux-user". I did a zypper install of the package on the obs appliance which acts as both the obs server and worker followed by restart of the appliance, but no luck.
After some googling, I found that you are supposed to provide qemu binary from a project instead of installing directly on the worker, so I create a 'qemu-linux-user' project in my local OBS instance with a `_link` to the official OBS package -
<link project='openSUSE.org:openSUSE:Leap:15.1:Update' package='qemu-linux-user'/>
Still no luck. qemu-linux-user shows 'excluded' under the Raspbian 10 repository for arm7vl
Appreciate any pointers.
Srivats
On Mon, Nov 4, 2019 at 8:58 PM Andreas Schwab schwab@suse.de wrote:
On Nov 04 2019, Srivats P wrote:
I have the following in the project config to crossbuild armv7 on a x86_64 worker %ifarch armv7l Hostarch: x86_64 Macros: %qemu_user_space_build 1 :Macros %endif
Did you Preinstall: qemu-linux-user (or its debian equivalent)?
Andreas.
-- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
You need an aggregate similar to https://build.opensuse.org/package/show/openSUSE:Factory:RISCV/000aggregate and the corresponding ExportFilter similar to the one in https://build.opensuse.org/projects/openSUSE:Factory:RISCV/prjconf.
Andreas.
buildservice@lists.opensuse.org
-
Andreas Schwab -
Srivats P