[opensuse-factory] maintenance question: what if a bugfix needs a new package?
Hi, Ben & listmates, Here's the case I ran into (bnc#821877): Our unzip can't detect CJK charsets, so it unzips them into folders like "口口口", which can't be opened by file managers and impossible to delete by rm command. So most of the users will consider this as a blocker. The cause of this problem is that we use librcc to detect charset in zip formats(librcc use dynamic engines for this task, so it masks other functions like iconv on purpose, which means you can't apply _any_ further chaset patch besides librcc). But our librcc is built without libguess support, which is responsible for CJK charset detection. Well, although libguess has been landed in devel:libraries:c_c++ for a while, it didn't get submitted into Factory, no need to mention released versions. For new version like 13.1, the fix will be easy: submit libguess, fix librcc, done. But for maintenance, I can fix librcc, then it requires libguess. Our maintenance policy doesn't seem to allow brand _new_ packages. Any exceptions? Greetings Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 25 Jun 2013 05:26:37 +0800
Marguerite Su
Hi, Ben & listmates,
Here's the case I ran into (bnc#821877):
Our unzip can't detect CJK charsets, so it unzips them into folders like "口口口", which can't be opened by file managers and impossible to delete by rm command. So most of the users will consider this as a blocker.
The cause of this problem is that we use librcc to detect charset in zip formats(librcc use dynamic engines for this task, so it masks other functions like iconv on purpose, which means you can't apply _any_ further chaset patch besides librcc). But our librcc is built without libguess support, which is responsible for CJK charset detection.
Well, although libguess has been landed in devel:libraries:c_c++ for a while, it didn't get submitted into Factory, no need to mention released versions.
For new version like 13.1, the fix will be easy: submit libguess, fix librcc, done.
But for maintenance, I can fix librcc, then it requires libguess. Our maintenance policy doesn't seem to allow brand _new_ packages. Any exceptions?
Greetings
Marguerite
I'd love to see where this policy is written down, although in general terms it makes sense not adding random packages after release. I'd vote for an exception, with the provision that libguess gets accepted into Factory properly. Then a backported package could be added to the updates channel. Thanks, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Jun 25, 2013 at 05:26:37AM +0800, Marguerite Su wrote:
Hi, Ben & listmates,
Here's the case I ran into (bnc#821877):
Our unzip can't detect CJK charsets, so it unzips them into folders like "口口口", which can't be opened by file managers and impossible to delete by rm command. So most of the users will consider this as a blocker.
The cause of this problem is that we use librcc to detect charset in zip formats(librcc use dynamic engines for this task, so it masks other functions like iconv on purpose, which means you can't apply _any_ further chaset patch besides librcc). But our librcc is built without libguess support, which is responsible for CJK charset detection.
Well, although libguess has been landed in devel:libraries:c_c++ for a while, it didn't get submitted into Factory, no need to mention released versions.
For new version like 13.1, the fix will be easy: submit libguess, fix librcc, done.
But for maintenance, I can fix librcc, then it requires libguess. Our maintenance policy doesn't seem to allow brand _new_ packages. Any exceptions?
We are more flexible these days, so we can ship new packages with maintenance updates. All the new stuff should be in Factory first of course, so we do not do new stuff only in maintainance. CIao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/24/2013 05:26 PM, Marguerite Su wrote:
But for maintenance, I can fix librcc, then it requires libguess. Our maintenance policy doesn't seem to allow brand _new_ packages. Any exceptions?
There is no technical reason to disallow such thing, unless of course the addition of a new package requires invasive changes in more than a handful of selected components in which case I can see why someone might (should?) object. In any case, it has to be tested first ;) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thanks, all, In the end the issue happens because our librcc0 sub-library has no requirements to its engine libs (rcc-runtime). Instead the runtime requirement was added to the main librcc which doesn't exist at all. Of course there'll be regressions if we don't follow what upstream suggests(use special lib for special purpose). But since librcc supports dynamic engines, in this case I can update without introducing a new package. And meanwhile I updated our libguess/librcc with the new mechanism for Factory and further versions. Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Cristian Rodríguez -
Marcus Meissner -
Marguerite Su -
Peter Linnell