Hi Andreas, > Actually I think it is unfair of users to expect that SUSE engineers > must be the ones to fix things if random boards break
I don't think anyone was calling for a "suse engineer". Users were asking for the openSUSE ARM contributors to take a look at the regression. I don't think anyone excluded "non-SUSE" people from looking at the problem and fixing it. And I'm not writing with a SUSE email here on this list... > 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 Thanks for pointing out a completely irrelevant detail, my completely irrelevant correction follows: We have an image with 3.18 (Contrib:RaspberryPi2, working) and 4.1 (Contrib:RaspberryPi2:Staging, not working yet) kernel. > - one that apparently no one remembers how it was created Maybe the person who created the kernel, who is listed as maintainer, and who has a git repo which accepts PRs knows how though. Oh and BTW: The kernel was not the problem of the image. > Mainly the convenience stuff around Kiwi images, that I am not an expert > on, "constantly" breaks in one way or another. Right, which is not a problem per se, because we're all humans and we make mistakes. Common practices like peer reviewing changes or respecting maintainership definitions can help though. > None of us on this list updated/broke systemd however, so that left us > with no one responsible reading the armv6l complaints here. I don't see many people complaining at all. I do see a group of people caring enough to report issues though, and I'm personally very happy to see that they care about something that I care about as well. BTW. systemd was just preventing the image from rebuild, the image was broken by other changes since it still doesn't work, and I'd guess it is reasonable to assume that somebody reading this list would find the motivation to debug and fix the issue and feel motivated since there is somebody else _as_ _well_ interested in getting that done. > If you, Dirk, want to monitor Raspberry Pi issues on this list I don't even own a Raspberry Pi, Andreas, but even then, I'm fixing packages for armv6 because there are people caring about them being working. if there are issues reported that I can fix given time, motivation and knowledge, more often than not I'm fixing them. I don't monitor for them though, and I generally don't reply to emails that don't motivate me or where I don't have something to contribute to that motivates the sender. I also don't read new emails here within two minutes and respond within 10 minutes though, as I have a demanding day job that requires me to focus on other stuff. So it can easily take a day or even a week for me to read the email, and I don't have time every weekend to fix stuff, so it can take even longer until I get around doing something about it. In my opinion we can greatly improve the experience though by not doing major restructurings of the way how our images work without properly staging those changes, testing them through from the beginning until the end and giving others with more knowledge in how things work a chance to peer review them prior them being merged. Please note that I didn't say that I don't appreciate cleanups or long-overdue refactorings. > welcome to - late last year it felt like I was left alone with replying > here at times... I typically don't have a lot of desire to read through email threads that have a stack of replies already from here up to the moon when I take a look at my email folder. I also lost my motivation at some point 10 years ago to correct anyone who is wrong on the internet (https://xkcd.com/386/). Not replying though doesn't mean that I don't read the mailing list, and I would love to continue enjoying that going forward. Greetings, Dirk -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
