On 04/25/2013 08:54 PM, Lars Vogdt wrote:
On Tue, 23 Apr 2013 09:48:17 +0200, Marcus Meissner <meissner@suse.de> wrote :
On Tuesday, April 23, 2013 09:06:38 Sascha Peilicke wrote: So it's that time of the year again. But it is still the same thing as was when we pushed Essex to Factory. These packages come from different (git, but doesn't matter) branches which by nature don't necessarily share a common history. They do share a common ancestor though:
----+----- master branch
\----- stable branch with bugfixes
It's the same thing with every project following that model by the way, so _yes_ deleted lines in changes files are expected. So what exactly is new here? [...] You are violating your own set rules... And it is sad that you think that they do not apply to you.
This sets bad precedence.
The same discussion process should be done this way. http://en.opensuse.org/openSUSE:Creating_a_changes_file_%28RPM%29
Just as a warning: you might change this policy for openSUSE without problems. But at least for SLE we have exactly this as a strict policy covered for our EAL certification:
No changes of released/accepted *.changes files!
Which is a clear indication the the EAL certification is absolute nonsense and pure bureaucracy. Which is totally fine with me as long as we are able to sell more.
So your package might end up in openSUSE, but you should think about a solution for SLE in your case. Otherwise your packages will be rejected there if there is an older package with a different changes file - and there is no way other than changing our EAL certification to change this. I'm fine if you start doing this - but please be aware that it might need much money and some time to do so.
Thankfully, it's unlikely that the OpenStack packages will become part of core SLE any time soon. We're a separate product and I don't see PM willing to change this. As long as the packages aren't rejected in openSUSE for SLE reasons anymore, we're totally ignorant to that :-) On the other hand, this happens all the time. Packages moving from pacman or vice versa don't always share history. And during the last two years of my Factory reviews I haven't come across a single Yast update (spanning across multiple packages), that didn't had changes files modified.
Other projects btw. have either different packages (think about the <packname><version>-<version-<release> schema) or add the changes of their new branch on top of the old changes file. This works for SLE since years...
Thinks that work for SLE since years aren't necessarily the right things. So we could argue about the usefullness of this practice forever, but I'm not gonna do this. I prefer to concentrate on more important matters. -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org