Hi Dirk, Am 04.02.2016 um 13:57 schrieb Dirk Müller: >> Further I had repeatedly said that if you guys care about a Contrib >> repository, such as RaspberryPi2, then you need to update and clean it >> up yourselves. Guess how many people did since then. > > Well, normally the responsibility of fixing something is with the one > who broke it.. I appreciate all the cleanups that have been done in > JeOS, but I think its unfair to shoot the messenger when things are > broken..
Actually I think it is unfair of users to expect that SUSE engineers must be the ones to fix things if random boards break, especially Contrib ones, given that users don't pay SUSE for that. At least for me, ARM boards are a night-time/weekend hobby and as such I cannot and won't start investigating a black-screen problem in the office. If I'm supposed to comment, I need more info and whomever wants a fix needs to deliver it. It's community work, and that means someone in this community must also investigate and possibly fix things - it seems to me an attitude issue in particular among Raspberry Pi users: It's like the most widely used ARM board and yet no one bothered to work on the mainline kernel for Raspberry Pi 2 until recently, everyone seems to be waiting for someone else rather than taking responsibility - and I feel my private time is better spent on less widespread platforms that are not working for me, unlike Raspberry Pi 1 and Raspberry Pi 2 that I do have working. It's not a general issue either, since Guillaume, Matwey, Misha, Oscar and some other non-SUSE people do understand how they can contribute in OBS. Contributing to A and asking for help with B is also much more motivating for me to help than this oh-I'm-just-a-user-not-a-developer dance; it's not like I was born an ARM/kernel/whatever developer either! At FOSDEM Michal and a visitor indicated the latest downstream kernel for the Raspberry Pi 2 were 4.1 based, whereas we have a 3.14 based kernel - one that apparently no one remembers how it was put together, so no one updates it. If there's issues, e.g., with graphics on that kernel then someone needs to package a new kernel in a home or sub-project, or build an image against Kernel:linux-next or Kernel:HEAD. If someone really badly wants to run openSUSE on a Raspberry Pi 1, the instructions for how to manually partition, cross-compile a kernel and switch to openSUSE packages have all been posted to this list, by me. Mainly the convenience stuff around Kiwi images, that I am not an expert on, "constantly" breaks in one way or another. I made the /boot/dtb symlink change and worked with you on resolving the ln issue during Hackweek after we got two good reports with serial output and later file listings pointing to that. I made the /boot/vc raspberrypi-firmware and u-boot changes, so after realizing how broken Kiwi is after updating our JeOS config scripts, I patched it. I maintain the qemu package, so I investigated the armv6l breakage, finding no QEMU change causing this error. None of us on this list updated/broke systemd however, so that left us with no one responsible reading the armv6l complaints here. If you, Dirk, want to monitor Raspberry Pi issues on this list and reply to future daily/weekly reports from Freek and Jimmy, you are more than welcome to - late last year it felt like I was left alone with replying here at times... Thanks, 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: [email protected] To contact the owner, e-mail: [email protected]
