Possibility of getting openvz problem included in stable?
Thanks for the clarifications. Yes it is true that I have not followed
the GIT tree very well. I got the impression that you were handling
most of the openvz things in the Debian kernel, so that is why I asked
you instead of digging into this myself. I do now understand that you
were not involved into the openvz branch as much as I thought and I
should put in more effort on this myself. Good to know.
Some further comments below.
Quoting "maximilian attems" <email@example.com>:
On Mon, Jun 20, 2011 at 04:52:56PM +0200, Ola Lundqvist wrote:
>we have pretty much allways synced with available openvz git.
>(see 2.6.26 history and 2.6.32 history)
>uploads are not immediate as we have a different schedule.
I understand that this is the case before the release. However after
the release only security updates are there, unless there is a point
release to be planned. That is at least the case for all other
packages in Debian.
openvz linux image do not have stable ABI.
this allows us more easily to update the patchset ones an update
or fix comes up.
If you'd really looked at the past, you'd see that concerning for
2.6.32 we are totally synced with openvz git and for 2.6.26 to 99%,
where the missing 1% were irrelevant for the Debian images.
>also please next time do at least the *effort* of asking the openvz
>guys instead of just forwarding my rants on stupid questions. a little
>effort from your side would really be appreciated.
I do not understand this comment actually. I thought you wanted
better support from openvz project. This is what you wrote in the
email to me. Kir is the project manager for that project and the one
I'm in contact with normally.
This is why I asked him to help with what you complained about.
I get annoyed by the questions you seem to reask and your
assessments. Also the pattern of unedited fwd is just to common.
I can not recall I have asked this question before. If that is the
case, I'm sorry. The reason why I asked is that this one was on my
todo list to ask.
And about stupid question: All I did was to ask a question to you,
and what I got back was a angry email stating that openvz project
behaves badly, and now I get another angry email stating that I have
not put in any effort. I'm sorry if that is the impression you get.
Sorry about that, but I do really not understand what you are so
No angry mail, just a reflection of the current state of affairs.
In that case I misinterpreted you. When people tell that my questions
are stupid I (obviously wrong assumption) that someone is angry or
It seems you never cloned the openvz git tree nor follow it.
This git tree is currently unmaintained and as such risky for any user.
If it is so that you do not have time to look into this yourself, I
have no problem if you simply write that. Just let me know that
(without all the angry tone) and I'll try to help as much as I can.
please do the minimum of research that is a git clone of
If you see no movements there, but lots of stable releases piling up
and you see new 2.6.32 openvz RH release politely ask the openvz guys
I can do that now when it is something that is expected by you.
and not me why the fuck nothing happens.
Well it was really not the intention from me that you should get the
impression that I asked "why the fuck nothing happens". I quote from
my original question to you:
The upstream have solved a kernel crash issue. See
Do you think it would be possible to get 042stab017 stable?
I think it is rather important thing to solve.
Do you want me to report this as a Debian bug report as well
or is it enough to refer to the openvz bug?
As you can see my questions were rather polite. I asked if you thought
it would be possible to include it or not. I even asked if you wanted
me to file a Debian specific bug report about this. Maybe that is the
part you mis-interpreted. It was not my intention to be rude. It was a
polite question actually.
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
Archive: email@example.com ">http://firstname.lastname@example.org