[opensuse-arm] Status of Raspberry Pi for openSUSE
Hallo, for half a year we're trying now to get openSUSE working on Raspberry Pi and still no success. The normal images don't build and the replacement image from http://en.opensuse.org/HCL:Raspberry_Pi works, but is ARM5 and thus does not work together with any project in the OBS, as these are all ARM6. On OBS it seems impossible to build anything from ARM5 anymore. So in my eyes the state is: - a non-standard image can be installed and works, but it is impossible to build packages for it. - all packages build in OBS are for ARM6, but can't be used, as I have no image to start from. Is there anything I overlook? How do I use Raspberry Pi with openSUSE and especially with the chance to build own packages for it? Ciao -- http://www.dstoecker.eu/ (PGP key available) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Its a bit sad that a board that already has sold 1.5 million pieces is not fully supported. My raspberry group here in Singapore is a lot bigger then my openSUSE group.. And I can not use OpenSUSE on my raspberries... :/ What really frustrates me On Tuesday 30 July 2013 12:19:35 Dirk Stöcker wrote:
Hallo,
for half a year we're trying now to get openSUSE working on Raspberry Pi and still no success.
The normal images don't build and the replacement image from http://en.opensuse.org/HCL:Raspberry_Pi works, but is ARM5 and thus does not work together with any project in the OBS, as these are all ARM6. On OBS it seems impossible to build anything from ARM5 anymore.
So in my eyes the state is: - a non-standard image can be installed and works, but it is impossible to build packages for it. - all packages build in OBS are for ARM6, but can't be used, as I have no image to start from.
Is there anything I overlook?
How do I use Raspberry Pi with openSUSE and especially with the chance to build own packages for it?
Ciao
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 31-07-2013 02:45, Mike Veltman wrote:
Its a bit sad that a board that already has sold 1.5 million pieces is not fully supported.
My raspberry group here in Singapore is a lot bigger then my openSUSE group.. And I can not use OpenSUSE on my raspberries... :/
What really frustrates me
Feel free to join in and help get it all working if it frustrates you that much. As we've explained several times, the Pi uses the old ARMv6 architecture and is almost the sole user nowadays (from a general compute perspective). openSUSE is looking forward, and when we re-started the ARM porting effort we made it crystal clear that our focus is on ARMv7 and above (including ARMv8). Creating and maintaining a port takes a heck of a lot of work, so there is only so much we can do. This does not stop you from getting ARMv6 up and running etc, and we know there are a lot of people with devices. This is what Berhhard help start and I know he would love some help.
On Tuesday 30 July 2013 12:19:35 Dirk Stöcker wrote:
Hallo,
for half a year we're trying now to get openSUSE working on Raspberry Pi and still no success.
The normal images don't build and the replacement image from http://en.opensuse.org/HCL:Raspberry_Pi works, but is ARM5 and thus does not work together with any project in the OBS, as these are all ARM6. On OBS it seems impossible to build anything from ARM5 anymore.
So in my eyes the state is: - a non-standard image can be installed and works, but it is impossible to build packages for it. - all packages build in OBS are for ARM6, but can't be used, as I have no image to start from.
Is there anything I overlook?
How do I use Raspberry Pi with openSUSE and especially with the chance to build own packages for it?
IIRC you need to wait a little bit longer as the ARMv6 target hasn't finished bootstarpping, I could be wrong and it is something more fundamental that's broken. Regards, Andy -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Andrew Wafaa wrote:
On 31-07-2013 02:45, Mike Veltman wrote:
Its a bit sad that a board that already has sold 1.5 million pieces is not fully supported.
My raspberry group here in Singapore is a lot bigger then my openSUSE group.. And I can not use OpenSUSE on my raspberries... :/
What really frustrates me
Feel free to join in and help get it all working if it frustrates you that much.
As we've explained several times, the Pi uses the old ARMv6 architecture and is almost the sole user nowadays (from a general compute perspective). openSUSE is looking forward, and when we re-started the ARM porting effort we made it crystal clear that our focus is on ARMv7 and above (including ARMv8).
Hmm, I'm quite sure that most people lurking on this list like me are interested in an openSUSE ARM port simply for getting it on the Raspberry Pi. The better ARM-based boards are too expensive to compete with fan-less x86-compatible hardware. Ciao, Michael.
Hi Michael. From your statement. that OpenSuse is no more interested to port OS for the AMRV6 boards such as Raspüberry Pi, as as OpenLinux since Version 4.1, I will now have to switch to the Debian Repos. Sri Edgar, DJ3PU, from Munich. Am 01.08.2013 10:34, schrieb Michael Ströder:
Andrew Wafaa wrote:
On 31-07-2013 02:45, Mike Veltman wrote:
Its a bit sad that a board that already has sold 1.5 million pieces is not fully supported.
My raspberry group here in Singapore is a lot bigger then my openSUSE group.. And I can not use OpenSUSE on my raspberries... :/
What really frustrates me
Feel free to join in and help get it all working if it frustrates you that much.
As we've explained several times, the Pi uses the old ARMv6 architecture and is almost the sole user nowadays (from a general compute perspective). openSUSE is looking forward, and when we re-started the ARM porting effort we made it crystal clear that our focus is on ARMv7 and above (including ARMv8). Hmm, I'm quite sure that most people lurking on this list like me are interested in an openSUSE ARM port simply for getting it on the Raspberry Pi.
The better ARM-based boards are too expensive to compete with fan-less x86-compatible hardware.
Ciao, Michael.
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Edgar, On 1 August 2013 10:50, Edgar Dombrowski <dj3pu@t-online.de> wrote:
Hi Michael.
From your statement. that OpenSuse is no more interested to port OS for the AMRV6 boards such as Raspüberry Pi, as as OpenLinux since Version 4.1, I will now have to switch to the Debian Repos.
Michael made no such statement. What I had said was openSUSE's focus is on ARMv7 and above. There is nothing stopping people from helping get support for v6 up and running, just that it won't be done as part of the core port. I would love to see openSUSE on every device out there, but there are only a small number of people doing the work so the work needs to be prioritised.
Sri
Edgar, DJ3PU, from Munich.
Am 01.08.2013 10:34, schrieb Michael Ströder:
Andrew Wafaa wrote:
On 31-07-2013 02:45, Mike Veltman wrote:
Its a bit sad that a board that already has sold 1.5 million pieces is not fully supported.
My raspberry group here in Singapore is a lot bigger then my openSUSE group.. And I can not use OpenSUSE on my raspberries... :/
What really frustrates me
Feel free to join in and help get it all working if it frustrates you that much.
As we've explained several times, the Pi uses the old ARMv6 architecture and is almost the sole user nowadays (from a general compute perspective). openSUSE is looking forward, and when we re-started the ARM porting effort we made it crystal clear that our focus is on ARMv7 and above (including ARMv8).
Hmm, I'm quite sure that most people lurking on this list like me are interested in an openSUSE ARM port simply for getting it on the Raspberry Pi.
The better ARM-based boards are too expensive to compete with fan-less x86-compatible hardware.
Ciao, Michael.
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Andrew Wafaa wrote:
What I had said was openSUSE's focus is on ARMv7 and above. There is nothing stopping people from helping get support for v6 up and running, just that it won't be done as part of the core port. I would love to see openSUSE on every device out there, but there are only a small number of people doing the work so the work needs to be prioritised.
I can understand very well that resources are limited. But I'd like to know why Raspberry Pi is low-priority despite its big community? What was the reason for openSUSE to focus on ARMv7? Regarding help I'd be willing to help in details or with certain packages. But only very few people can do something about the OBS infrastructure. As said I'm lurking on this in the hope to get some directions how to use the Raspberry Pi with a repo which receives updates. But I'm totally confused about all the ARM-related repos popping up. Ciao, Michael.
Am Donnerstag, 1. August 2013, 18:33:18 schrieb Michael Ströder:
Andrew Wafaa wrote:
What I had said was openSUSE's focus is on ARMv7 and above. There is nothing stopping people from helping get support for v6 up and running, just that it won't be done as part of the core port. I would love to see openSUSE on every device out there, but there are only a small number of people doing the work so the work needs to be prioritised.
I can understand very well that resources are limited.
But I'd like to know why Raspberry Pi is low-priority despite its big community? What was the reason for openSUSE to focus on ARMv7?
Regarding help I'd be willing to help in details or with certain packages. But only very few people can do something about the OBS infrastructure.
What is missing in the OBS infrastructure?
As said I'm lurking on this in the hope to get some directions how to use the Raspberry Pi with a repo which receives updates. But I'm totally confused about all the ARM-related repos popping up.
Ciao, Michael. --
Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 01-08-2013 17:33, Michael Ströder wrote:
Andrew Wafaa wrote:
What I had said was openSUSE's focus is on ARMv7 and above. There is nothing stopping people from helping get support for v6 up and running, just that it won't be done as part of the core port. I would love to see openSUSE on every device out there, but there are only a small number of people doing the work so the work needs to be prioritised.
I can understand very well that resources are limited.
But I'd like to know why Raspberry Pi is low-priority despite its big community? What was the reason for openSUSE to focus on ARMv7?
The main reason is that both physical and human resources are limited. ARMv6 is used almost solely by the Pi, ARMv5 has numerous devices, but both are old. ARMv7 is the current architecture and with a new port it made sense to look at current and next release of the architecture. So this means ARMv7 and ARMv8. Most new devices, whether they be development boards, servers or PCs and especially mobile devices like tablets are all v7. The market dictates where we focus. We are not saying openSUSE will not support ARMv6, just that it is not being done as part of the core ARM porting effort as we are struggling with what we have targeted let alone anything new. This message has been clear from the outset of the porting effort that was started over 2 years ago.
Regarding help I'd be willing to help in details or with certain packages. But only very few people can do something about the OBS infrastructure.
As said I'm lurking on this in the hope to get some directions how to use the Raspberry Pi with a repo which receives updates. But I'm totally confused about all the ARM-related repos popping up.
Ciao, Michael. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Mon, Aug 05, 2013 at 03:11:46PM +0100, Andrew Wafaa wrote: [...]
The main reason is that both physical and human resources are limited. ARMv6 is used almost solely by the Pi, ARMv5 has numerous devices, but both are old. ARMv7 is the current architecture and with a new port it made sense to look at current and next release of the architecture. So this means ARMv7 and ARMv8.
[...] This is understood, but I think maybe from a marketing / mind-share point of view we have missed a trick here. Many Raspberry Pi owners are actually new to Linux, and I think it's a pity that openSUSE is not put in front of them as one of the alternatives. -- ======================== Roger Whittaker roger@disruptive.org.uk http://disruptive.org.uk ======================== -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 05-08-2013 15:55, Roger Whittaker wrote:
On Mon, Aug 05, 2013 at 03:11:46PM +0100, Andrew Wafaa wrote:
[...]
The main reason is that both physical and human resources are limited. ARMv6 is used almost solely by the Pi, ARMv5 has numerous devices, but both are old. ARMv7 is the current architecture and with a new port it made sense to look at current and next release of the architecture. So this means ARMv7 and ARMv8.
[...]
This is understood, but I think maybe from a marketing / mind-share point of view we have missed a trick here.
Many Raspberry Pi owners are actually new to Linux, and I think it's a pity that openSUSE is not put in front of them as one of the alternatives.
I completely understand people's complaints of this decision and it is a valid concern. Problem is we only have a limited pool of resource, openSUSE operates a roll your sleeve up methodology - if you want it bad enough, roll your sleeves up and just do it. There is work already started in supporting the Raspberry Pi, and I'm 100% sure that those involved would be more than happy for all the help they get, and would be willing to help those trying to move the effort forward. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Tue, 6 Aug 2013, Andrew Wafaa wrote:
I completely understand people's complaints of this decision and it is a valid concern. Problem is we only have a limited pool of resource, openSUSE operates a roll your sleeve up methodology - if you want it bad enough, roll your sleeves up and just do it. There is work already started in supporting the Raspberry Pi, and I'm 100% sure that those involved would be more than happy for all the help they get, and would be willing to help those trying to move the effort forward.
I now started a bit for Raspberry Pi: https://build.opensuse.org/project/monitor/devel:ARM:Factory:Contrib:Raspber... I reduced the error messages a bit. Now the JeOS-raspberrypi image says following: ---------------------------------------------- 1) I have no idea what these errors mean and how they can be solved: nothing provides ERROR_NO_BOOT_CONFIG_FILE_FOUND needed by kiwi-desc-oemboot-requires, nothing provides ERROR_NO_DEPENDENCIES_FOUND needed by kiwi-desc-oemboot-requires, 2) These I don't understand. Even if the packages are blocked for build, there are old packages which should be taken! nothing provides kernel-raspberrypi, nothing provides raspberrypi-firmware, 3) Following probably due to rebuild issues in main repo and will be resolved when build proceeds (2.37.3 mismatches 2.37.4). nothing provides libgio-2_0-0 = 2.37.3 needed by gio-branding-openSUSE, nothing provides qemu-tools needed by virt-utils, conflict for provider of gio-branding = 2.37.4 needed by libgio-2_0-0, (provider gio-branding-upstream is conflicted by installed gio-branding-openSUSE) Ciao -- http://www.dstoecker.eu/ (PGP key available) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Dienstag, 6. August 2013, 15:46:59 schrieb Dirk Stöcker:
On Tue, 6 Aug 2013, Andrew Wafaa wrote:
I completely understand people's complaints of this decision and it is a valid concern. Problem is we only have a limited pool of resource, openSUSE operates a roll your sleeve up methodology - if you want it bad enough, roll your sleeves up and just do it. There is work already started in supporting the Raspberry Pi, and I'm 100% sure that those involved would be more than happy for all the help they get, and would be willing to help those trying to move the effort forward.
I now started a bit for Raspberry Pi:
https://build.opensuse.org/project/monitor/devel:ARM:Factory:Contrib:Raspber ryPi
I reduced the error messages a bit.
Now the JeOS-raspberrypi image says following: ----------------------------------------------
1) I have no idea what these errors mean and how they can be solved:
nothing provides ERROR_NO_BOOT_CONFIG_FILE_FOUND needed by kiwi-desc-oemboot-requires, nothing provides ERROR_NO_DEPENDENCIES_FOUND needed by kiwi-desc-oemboot-requires,
that basically says that kiwi has no support yet for armv6. It is not able to create bootable medias. I can have a look at it, but given that I have no clue how PI is booting, it would be better if someone else is doing it.
2) These I don't understand. Even if the packages are blocked for build, there are old packages which should be taken!
nothing provides kernel-raspberrypi, nothing provides raspberrypi-firmware,
if they exist, the repository is not used. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 07/08/2013 12:09, Adrian Schröter a écrit :
On Tue, 6 Aug 2013, Andrew Wafaa wrote:
I completely understand people's complaints of this decision and it is a valid concern. Problem is we only have a limited pool of resource, openSUSE operates a roll your sleeve up methodology - if you want it bad enough, roll your sleeves up and just do it. There is work already started in supporting the Raspberry Pi, and I'm 100% sure that those involved would be more than happy for all the help they get, and would be willing to help those trying to move the effort forward. I now started a bit for Raspberry Pi:
https://build.opensuse.org/project/monitor/devel:ARM:Factory:Contrib:Raspber ryPi
I reduced the error messages a bit.
Now the JeOS-raspberrypi image says following: ----------------------------------------------
1) I have no idea what these errors mean and how they can be solved:
nothing provides ERROR_NO_BOOT_CONFIG_FILE_FOUND needed by kiwi-desc-oemboot-requires, nothing provides ERROR_NO_DEPENDENCIES_FOUND needed by kiwi-desc-oemboot-requires,
Am Dienstag, 6. August 2013, 15:46:59 schrieb Dirk Stöcker: that basically says that kiwi has no support yet for armv6. It is not able to create bootable medias. I can have a look at it, but given that I have no clue how PI is booting, it would be better if someone else is doing it.
If I remember for armv5 we simply used armv7 support in kiwi. Could we do the same for armv6?
2) These I don't understand. Even if the packages are blocked for build, there are old packages which should be taken!
nothing provides kernel-raspberrypi, nothing provides raspberrypi-firmware, if they exist, the repository is not used.
It is a stange error I noticed with my home repo. Maybe a bug somewhere? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Wed, 7 Aug 2013, Adrian Schröter wrote:
2) These I don't understand. Even if the packages are blocked for build, there are old packages which should be taken!
nothing provides kernel-raspberrypi, nothing provides raspberrypi-firmware,
if they exist, the repository is not used.
That's not really possible, as images has the normal repo as target and that again has openSUSE:Factory:ARM/armv6hl which has openSUSE:Factory/ports. So if factory packages are found, the repo must work at all, so why not for the files in the repo itself? The files are even exported to download: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... Ciao -- http://www.dstoecker.eu/ (PGP key available)
Hi Adrian,
that basically says that kiwi has no support yet for armv6. It is not able to create bootable medias. I can have a look at it, but given that I have no clue how PI is booting, it would be better if someone else is doing it.
Thats not really true. the generic ARM support in kiwi allows anything to be set up via the uboot-setup hooks that have been implemented, including RaspberryPi support.
2) These I don't understand. Even if the packages are blocked for build, there are old packages which should be taken!
The repository which contains those packages needs to be added as a source to the kiwi config. I've fixed that now. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hello, I fixed the files for recent repo changes, now only one error remains.
nothing provides qemu-tools needed by virt-utils,
Probably qemu needs to be enabled for standard/armv6l here? https://build.opensuse.org/package/show/openSUSE:Factory:ARM/qemu Ciao -- http://www.dstoecker.eu/ (PGP key available) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Mittwoch, 14. August 2013, 09:12:52 schrieb Dirk Stöcker:
Hello,
I fixed the files for recent repo changes, now only one error remains.
nothing provides qemu-tools needed by virt-utils,
Probably qemu needs to be enabled for standard/armv6l here?
probably, did so now.
https://build.opensuse.org/package/show/openSUSE:Factory:ARM/qemu
Ciao
-- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Thu, 1 Aug 2013, Andrew Wafaa wrote:
Feel free to join in and help get it all working if it frustrates you that much.
As we've explained several times, the Pi uses the old ARMv6 architecture and is almost the sole user nowadays (from a general compute perspective). openSUSE is looking forward, and when we re-started the ARM porting effort we made it crystal clear that our focus is on ARMv7 and above (including ARMv8).
Creating and maintaining a port takes a heck of a lot of work, so there is only so much we can do. This does not stop you from getting ARMv6 up and running etc, and we know there are a lot of people with devices. This is what Berhhard help start and I know he would love some help.
I plan to plan helping for half a year now, but the basic requirements are missing. Since we have our raspberries there was no time, when an initial boot image and the the obs service repositories could be used together. I do a lot for openSUSE for many years now, but I have no time to learn a completely new topic how to create a installation system from scratch. So if we can get a state, where an installation medium is available which matches current OBS, then I'll help to port some of the stuff and fix problems. Also the OBS build stuff actually should be exported to the download directories. Currently all the stuff available for download has nothing to do with the stuff in the build setup. Everything is totally mangled. I requested maintainer role for devel:ARM:12.3:Contrib:RaspberryPi already, so that I at least can fix some of the obvious errors like broken links in the build environment. Ciao -- http://www.dstoecker.eu/ (PGP key available) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Dirk,
I plan to plan helping for half a year now, but the basic requirements are missing. Since we have our raspberries there was no time, when an initial boot image and the the obs service repositories could be used together.
plan to plan helping is not helping. Thanks for stepping up as a maintainer of the RaspberryPi port, I've approved your request a few days ago. Getting to a state where you can actually build a ARMv6 based image is ongoing work done by me (and others) for 4 months already, but given that there are many fronts to fight on (various armv7 breakages and AArch64 also being a pita sometimes), there is only that much you can do when you're working on something alone. Note that building an image is only perhaps 50% of the work, getting a repository with enough (and current) packages to build an image from is at least half of the other work, and that work is ongoing, a tedious, timeconsuming and often very frustrating job because packages get sometimes broken to build quicker than it took you to fix them to get to build again in the first place.
I do a lot for openSUSE for many years now, but I have no time to learn a completely new topic how to create a installation system from scratch. So if we can get a state, where an installation medium is available which matches current OBS, then I'll help to port some of the stuff and fix problems.
Thats when all the work would be done. without additional helping hands to get there, we have little chance to succeed.
the OBS build stuff actually should be exported to the download directories. Currently all the stuff available for download has nothing to do with the stuff in the build setup. Everything is totally mangled.
Well, it is hidden behind (sometimes not really well documented) APIs or AHIs (Application Human interfaces). In many cases one has to ask somebody who wrote the code on what is going on. Thats just how it is, unfortunately.
I requested maintainer role for devel:ARM:12.3:Contrib:RaspberryPi already, so that I at least can fix some of the obvious errors like broken links in the build environment.
the 12.3:Contrib project turned out to be a dead end, since it was armv5 and the miscompilations there were just too much effort to get fixed in a stable code tree. Thats why we decided a few weeks ago to focus on ARMv6 and Factory only, where things look a lot more promising. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sat, 10 Aug 2013, Dirk Müller wrote:
I plan to plan helping for half a year now, but the basic requirements are missing. Since we have our raspberries there was no time, when an initial boot image and the the obs service repositories could be used together.
plan to plan helping is not helping. Thanks for stepping up as a
Each and everbody has only a limited amount of time. I can't do everything, so I have a clear mark what I can and will do and what not. I care for packages, not for whole distributions.
I do a lot for openSUSE for many years now, but I have no time to learn a completely new topic how to create a installation system from scratch. So if we can get a state, where an installation medium is available which matches current OBS, then I'll help to port some of the stuff and fix problems.
Thats when all the work would be done. without additional helping hands to get there, we have little chance to succeed.
Huh. I'm pretty sure that there is lots of work to be done when an initial image is available which links to OBS. An bootable image probably needs only 5% of all the software in factory and that's only a small part of OBS at all. I don't expect a fancy powerful system, but only a WORKING one, where I can install additional stuff when available.
the OBS build stuff actually should be exported to the download directories. Currently all the stuff available for download has nothing to do with the stuff in the build setup. Everything is totally mangled.
Well, it is hidden behind (sometimes not really well documented) APIs or AHIs (Application Human interfaces). In many cases one has to ask somebody who wrote the code on what is going on. Thats just how it is, unfortunately.
I don't want to learn any of these details. I want one image downloadable and installable, where I can add OBS repos like for normal x86. From there on it is fixing packages and installing. Currently I can neither do that for our Raspberry Pi, nor for the ARM7 Beagle board we bought recently. ARM for openSUSE seems completely unusable ATM. And download.opensuse.org contains too much stuff which is unusable and/or does not match the OBS stuff (thus seems outdated :-). Ciao -- http://www.dstoecker.eu/ (PGP key available)
participants (10)
-
Adrian Schröter -
Andrew Wafaa -
Andrew Wafaa -
Dirk Müller -
Dirk Stöcker -
Edgar Dombrowski -
Guillaume Gardet -
Michael Ströder -
Mike Veltman -
Roger Whittaker