The people that took action here - myself, Alex,
Andreas - all are, and
we're less than the users asking.
.. action that you *perceived* to take action. A strong difference!
It could be documented a) in the spec file, b) in the
package or project
description. And some README.txt file in the repository might be a
useful feature for people accessing it directly from the Wiki etc.
it is documented in the maintainer and bugowner roles.. And there is
no way to inject a README.txt file
in the kernel-source build process as far as I know.
The problem is a) people _call_ it an openSUSE image
despite not having
an openSUSE kernel
Sure, because it contains openSUSE :-) Just because it does not *only*
consists of openSUSE it isn't openSUSE anymore.
Then you could start with giving me a chance to review
changes and not changing them behind my back and, without asking me
first, dropping options that I invested time to make consistent!
Usually there is a reason given in the change.. We can go over it in
detail if you want, I'm typically fixing the config for consistency
and don't try to drop options without reasoning (actually I just got a
notification that I added too many options in the last update.. :-) ).
Also we will never get u-boot or dtb-source updated in
Factory if we
keep superseding each other's SRs rather than waiting while an in-flight
one goes through Staging and Factory review.
Those are additional packages so if they get stuck then there is a
reason that needs fixing. Waiting longer isn't gonna fix it.
Missing links is a recurring pain point that some of
can't remedy ourselves.
Thats why the SRs to those packages are configured to add me as a
reviewer, and if you would respect that reviewer setting then I'd have
a chance to fix the link issue and you don't have to "complain" about
And may I remind you that there is no devel project
set for JeOS.
I am painfully aware, thats why I said I would prefer to have those
who maintain an image review changes that affect that image..
that it would help with the armv7l build power
problems with existing
images not getting rebuilt within two weeks.
which is an OBS bug/behaviour change we're trying to fix right now. if
you check the history, you see it was not an issue until the 2nd last
OBS code update.
Part of the official OBS workflow is also using Submit
Requests and not
committing to Contrib projects directly, which then leaves me and other
people without change notifications. Please Don't Do That.
First of all you even get change notifications when direct commits are
done for projects that you care about. But even then, I think Contribs
are allowed to be maintained by those who maintain it, even without
you reviewing the change.
Yes, a lot of things can be done to improve the
Some others are limited by our build power unfortunately.
.. which are partially caused by regressions in our openSUSE kernel.
But thanks for bringing
it up after we have spent a few nights on isolating and fixing it.
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.
at least a handful of people complaining about Raspberry Pi
images specifically, I can't help you if you didn't see that.
I'm specifically annoyed by the word "complaining". People have
mentioned this, yes, and as I
said before, I am reading it. I just don't reply if I have nothing
useful to add.
* Would we stage dtb-source from Kernel:linux-next
to Base:System we could test some additions much earlier (dtb-meson8b).
Downside is such branches would silently break whenever someone changes
Base:System. Similar merge problems exist for Contrib JeOS branches.
That's why there is a common sense to not have downstream
modifications of JeOS branches. we could document
that for a policy if you want.
* Would we have an archive of known working Tumbleweed
temporary image breakages wouldn't be as severe.
yeah, but it requires work to have the archive kept maintained.
creating that would be easy.
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org