[opensuse-arm] Repository for openSUSE Tumbleweed architecture aach64 is not kept up-to-date
I filed a bug report with this subject as: https://bugzilla.opensuse.org/show_bug.cgi?id=1077011 I am using the image for the Raspberry Pi 3, which is available via OBS and which is build using the newest packages also available in OBS. This image should be available in the regular repository, also mentioned in the wiki. Also the newest packages should be available via the repository zypper uses to upgrade Tumbleweed, which is currently not the case. Can I be of any help with this? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 01/22/2018 12:08 PM, Freek de Kruijf wrote:
I filed a bug report with this subject as: https://bugzilla.opensuse.org/show_bug.cgi?id=1077011
I am using the image for the Raspberry Pi 3, which is available via OBS and which is build using the newest packages also available in OBS. This image should be available in the regular repository, also mentioned in the wiki. Also the newest packages should be available via the repository zypper uses to upgrade Tumbleweed, which is currently not the case.
Publishing of images and repositories (for aarch64) happens whenever OpenQA passes successfully: https://openqa.opensuse.org/group_overview/3 I guess the last run wasn't quite happy :) Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op maandag 22 januari 2018 12:34:20 CET schreef Alexander Graf:
On 01/22/2018 12:08 PM, Freek de Kruijf wrote:
I filed a bug report with this subject as: https://bugzilla.opensuse.org/show_bug.cgi?id=1077011
I am using the image for the Raspberry Pi 3, which is available via OBS and which is build using the newest packages also available in OBS. This image should be available in the regular repository, also mentioned in the wiki. Also the newest packages should be available via the repository zypper uses to upgrade Tumbleweed, which is currently not the case.
Publishing of images and repositories (for aarch64) happens whenever OpenQA passes successfully:
https://openqa.opensuse.org/group_overview/3
I guess the last run wasn't quite happy :)
Alex
I am quite happy with the latest image I got from OBS for the Raspberry Pi 3. There is hardly any detailed information on why OpenQA failed or rather the 15 tests were incomplete. BTW: the image I use was build 2018-01-20; latest OpenQA test was 20180113. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op maandag 22 januari 2018 12:34:20 CET schreef Alexander Graf:
On 01/22/2018 12:08 PM, Freek de Kruijf wrote:
I filed a bug report with this subject as: https://bugzilla.opensuse.org/show_bug.cgi?id=1077011
I am using the image for the Raspberry Pi 3, which is available via OBS and which is build using the newest packages also available in OBS. This image should be available in the regular repository, also mentioned in the wiki. Also the newest packages should be available via the repository zypper uses to upgrade Tumbleweed, which is currently not the case.
Publishing of images and repositories (for aarch64) happens whenever OpenQA passes successfully:
There is something strange on this page. It says 7 days ago is 20180113, which should be 16 days ago. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Jan 29 2018, Freek de Kruijf <freek@opensuse.org> wrote:
There is something strange on this page. It says 7 days ago is 20180113, which should be 16 days ago.
No, it says that 2018-01-22 is 8 days ago, which is correct. 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." -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Freek, Am 22.01.2018 um 12:08 schrieb Freek de Kruijf:
I filed a bug report with this subject as: https://bugzilla.opensuse.org/show_bug.cgi?id=1077011
I don't see how that will help, as a Bugzilla ticket is only really useful when it can be assigned to someone to work on it and be closed at some point. "is not kept up-to-date" doesn't quite tick that box for me. That openQA sometimes does not pass happens for x86 too, just not that often, and they get more frequent snapshot builds to test so that they're not blocked as long. We already got a donation of two servers a few months back to help shorten that build cycle.
I am using the image for the Raspberry Pi 3, which is available via OBS and which is build using the newest packages also available in OBS. This image should be available in the regular repository, also mentioned in the wiki. Also the newest packages should be available via the repository zypper uses to upgrade Tumbleweed, which is currently not the case.
Fully agree that that is the ideal case - however note that there's a difference between "snapshot" and "standard" repository on x86, too, with snapshot corresponding to what's published and standard being the very latest.
Can I be of any help with this?
Yes! :) The openQA build results need to be monitored, and if there are failures they need to be looked at and acted upon. It won't help to file 15 bugs for 15 test failures when the problem is really the openQA worker, but occasionally there were package dependency issues, surfacing as warning/error messages in the screenshots before a failure. The builds that were fully reviewed show a grey star next to the date, and if you click on that build it will show a blue bug symbol next to the failing test cases. https://openqa.opensuse.org/group_overview/3 There are no notifications of when a new build has been tested, and Dirk and I have been looking at the test results as time permits. Any help 1) bringing new failing builds to our common attention and 2) investigating what may be going wrong to ultimately 3) get the failures annotated with bugs that either need to be fixed before publishing or can be ignored by ttm for the next build would be appreciated. And obviously where packages are failing to build (113 for aarch64 atm), some may be a generic issue also found in openSUSE:Factory for x86_64, some may be an intermittent worker problem, and some others an actual ARM-specific problem that Dominique and the maintainers are simply not seeing on x86. So if a package you care about has failing dependencies, then Submit Requests in OBS to get those builds fixed properly may be a solution for certain openQA and repo publishing problems. https://build.opensuse.org/project/show/openSUSE:Factory:ARM https://build.opensuse.org/project/monitor/openSUSE:Factory:ARM?arch_aarch64=1&defaults=0&failed=1&repo_standard=1 Cheers, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op maandag 22 januari 2018 21:20:06 CET schreef Andreas Färber: Hallo Andreas,
Hi Freek, https://build.opensuse.org/project/monitor/openSUSE:Factory:ARM?arch_aarch64 =1&defaults=0&failed=1&repo_standard=1
I looked at MyGUI and ShellCheck and have some ideas about what's wrong. MyGUI: the spec file has a conditial for 64 bit architecture which is only for x86_64, but I assume should also be applied for aarch64. ShellCheck: ends with "Out of memory", so it may need building with more memory. I found another ghc packet also with "Out of memory", so there may be more with the same reason. Is this the type of help I should provide? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Jan 23 2018, Freek de Kruijf <freek@opensuse.org> wrote:
ShellCheck: ends with "Out of memory", so it may need building with more memory. I found another ghc packet also with "Out of memory", so there may be more with the same reason.
ghc is notorious for going OOM since it doesn't have a native backend for aarch64. 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." -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 01/23/2018 02:35 PM, Freek de Kruijf wrote:
Op maandag 22 januari 2018 21:20:06 CET schreef Andreas Färber: Hallo Andreas,
Hi Freek, https://build.opensuse.org/project/monitor/openSUSE:Factory:ARM?arch_aarch64 =1&defaults=0&failed=1&repo_standard=1
I looked at MyGUI and ShellCheck and have some ideas about what's wrong. MyGUI: the spec file has a conditial for 64 bit architecture which is only for x86_64, but I assume should also be applied for aarch64.
Feel free to branch the package, change the spec file. If this fixes the build, feel free to create a Submit Request to get the maintainer reviewing (and hopefully accepting) your changes :) Best regards, Matthias
ShellCheck: ends with "Out of memory", so it may need building with more memory. I found another ghc packet also with "Out of memory", so there may be more with the same reason.
Is this the type of help I should provide?
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op dinsdag 23 januari 2018 17:28:31 CET schreef Matthias Brugger:
On 01/23/2018 02:35 PM, Freek de Kruijf wrote: Hallo Mathias,
I looked at MyGUI and ShellCheck and have some ideas about what's wrong. MyGUI: the spec file has a conditial for 64 bit architecture which is only for x86_64, but I assume should also be applied for aarch64.
Feel free to branch the package, change the spec file. If this fixes the build, feel free to create a Submit Request to get the maintainer reviewing (and hopefully accepting) your changes :)
I branched the package and managed to have it build for aarch64, however while building the Buildrequires are not satisfied. How do I get these packages in? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 23/01/2018 à 19:58, Freek de Kruijf a écrit :
Op dinsdag 23 januari 2018 17:28:31 CET schreef Matthias Brugger:
On 01/23/2018 02:35 PM, Freek de Kruijf wrote: Hallo Mathias,
I looked at MyGUI and ShellCheck and have some ideas about what's wrong. MyGUI: the spec file has a conditial for 64 bit architecture which is only for x86_64, but I assume should also be applied for aarch64. Feel free to branch the package, change the spec file. If this fixes the build, feel free to create a Submit Request to get the maintainer reviewing (and hopefully accepting) your changes :) I branched the package and managed to have it build for aarch64, however while building the Buildrequires are not satisfied. How do I get these packages in?
You can keep a single %ifarch line with: %ifarch x86_64 aarch64 To get the Buildrequires, you need to add the "openSUSE Factory ARM" repo from here: https://build.opensuse.org/repositories/home:fdekruijf:branches:games Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op woensdag 24 januari 2018 10:34:57 CET schreef Guillaume Gardet:
Hi,
Le 23/01/2018 à 19:58, Freek de Kruijf a écrit :
Op dinsdag 23 januari 2018 17:28:31 CET schreef Matthias Brugger:
On 01/23/2018 02:35 PM, Freek de Kruijf wrote: Hallo Mathias,
I looked at MyGUI and ShellCheck and have some ideas about what's wrong. MyGUI: the spec file has a conditial for 64 bit architecture which is only for x86_64, but I assume should also be applied for aarch64.
Feel free to branch the package, change the spec file. If this fixes the build, feel free to create a Submit Request to get the maintainer reviewing (and hopefully accepting) your changes :)
I branched the package and managed to have it build for aarch64, however while building the Buildrequires are not satisfied. How do I get these packages in? You can keep a single %ifarch line with: %ifarch x86_64 aarch64
To get the Buildrequires, you need to add the "openSUSE Factory ARM" repo from here: https://build.opensuse.org/repositories/home:fdekruijf:branches:games
Guillaume
Found finally how to do that, but I don't think it is relevant anymore because Kasimir has taken action. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Request for MyGUIis on the way: https://build.opensuse.org/request/show/568731 Am 23.01.2018 um 19:58 schrieb Freek de Kruijf:
Op dinsdag 23 januari 2018 17:28:31 CET schreef Matthias Brugger:
On 01/23/2018 02:35 PM, Freek de Kruijf wrote: Hallo Mathias,
I looked at MyGUI and ShellCheck and have some ideas about what's wrong. MyGUI: the spec file has a conditial for 64 bit architecture which is only for x86_64, but I assume should also be applied for aarch64. Feel free to branch the package, change the spec file. If this fixes the build, feel free to create a Submit Request to get the maintainer reviewing (and hopefully accepting) your changes :) I branched the package and managed to have it build for aarch64, however while building the Buildrequires are not satisfied. How do I get these packages in?
N�����r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0�����Ǩ�
Op maandag 22 januari 2018 21:20:06 CET schreef Andreas Färber:
Hi Freek, Hallo Andeas,
The builds that were fully reviewed show a grey star next to the date, and if you click on that build it will show a blue bug symbol next to the failing test cases.
I looked on this page and revieuwed the failures for OpenQA for Build20180113 and found some simple errors (probably just 2 different ones), for which I filed bug reports. Hope this helps. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op donderdag 25 januari 2018 13:07:03 CET schreef Freek de Kruijf:
Op maandag 22 januari 2018 21:20:06 CET schreef Andreas Färber:
Hi Freek,
Hallo Andeas,
The builds that were fully reviewed show a grey star next to the date, and if you click on that build it will show a blue bug symbol next to the failing test cases.
I looked on this page and revieuwed the failures for OpenQA for Build20180113 and found some simple errors (probably just 2 different ones), for which I filed bug reports. Hope this helps.
Both type of failures are looked upon, but the answer is that they wait for some changes that should appear, and probably have appeared, in a new build of Tumbleweed for aarch64. So waiting for a new OpenQA test for this. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (7)
-
Alexander Graf -
Andreas Färber -
Andreas Schwab -
Freek de Kruijf -
Guillaume Gardet -
Kasimir _ -
Matthias Brugger