Hi,
I found a bug late in 11.3RC1/2 Reported it here: https://bugzilla.novell.com/show_bug.cgi?id=617677.
Because it was close to 11.3 GA it needs to be fixed as a patch. There is discussions in this thread about swampids and sr#. The bug is marked as fixed but I don’t think it has reached any repositories yet as the Gnome libraries are not in the update directory.
So my questions are:
- Can someone explain the internals of the opensuse patch process? swampids and sr?
- Is the process open? How can I know that my bug has a fix that has reached the repos?
- Is there a public place where patches go before being released? The fix has been available for some time now but no binaries as I understand it.
I want to understand how my favourite Linux brand works.
Thanks!
Hi, Johan -
I’m not an expert on the process, but let me see if I can answer your
questions (or start a discussion about them). 
On Tue, 27 Jul 2010 22:36:02 +0000, johanferner wrote:
> Hi,
>
> I found a bug late in 11.3RC1/2 Reported it here:
> https://bugzilla.novell.com/show_bug.cgi?id=617677.
>
> Because it was close to 11.3 GA it needs to be fixed as a patch. There
> is discussions in this thread about swampids and sr#. The bug is marked
> as fixed but I don’t think it has reached any repositories yet as the
> Gnome libraries are not in the update directory.
>
> So my questions are:
> * Can someone explain the internals of the opensuse patch process?
> swampids and sr?
I’m not sure what those terms apply to - where are you seeing them?
> * Is the process open? How can I know that my bug has a fix that has
> reached the repos?
As far as I know, the bug would be updated to resolved and/or verified,
those terms generally mean a code fix has been committed and has been
verified to fix the reported bug.
> * Is there a public place where patches go before being released? The
> fix has been available for some time now but no binaries as I understand
> it.
As I understand it, the fix would first go to factory (as a binary -
you’d see this as a repository, but I’d not add that repository unless
you want to test ‘bleeding edge’ full-on, because when you update you’ll
be updated to the ‘factory’ release). From there you might see it move
to the standard repos unless there was a dependency that wasn’t met or
the update was significant enough to bump the version number beyond the
third decimal (ie, from 3.5 to 3.6 generally wouldn’t be udpated, but
3.5.1 to 3.5.2 would be - though there may be exceptions to that).
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C