Where to submit package updates

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Where to submit package updates

Tristan Miller
Dear all,

Certain packages I use from the "official release" repositories of
openSUSE 42.3 and Tumbleweed are out of date.  Some of these packages
are also found (in the same version) in additional repositories such as
"Archiving" or "multimedia:apps".

Until now, when I want to revise a package so that it's using the
latest upstream version, I've been branching it on OBS, making the
necessary updates in my own project space, and then submitting it to
the appropriate "additional" repository.

Will these updates eventually make it into the "official release"
repositories, or do I need to manually submit them to the "official
release" repositories?  I'm not really sure of the workflow here -- I'm
not a SUSE employee but just an external volunteer.

Regards,
Tristan

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                  Tristan Miller
Free Software developer, ferret herder, logologist
             https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

attachment0 (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Where to submit package updates

Axel Braun-2
Hello Tristan

Am Montag, 21. August 2017, 10:32:48 CEST schrieb Tristan Miller:
 
> Certain packages I use from the "official release" repositories of
> openSUSE 42.3 and Tumbleweed are out of date.  Some of these packages
> are also found (in the same version) in additional repositories such as
> "Archiving" or "multimedia:apps".
>
> Until now, when I want to revise a package so that it's using the
> latest upstream version, I've been branching it on OBS, making the
> necessary updates in my own project space, and then submitting it to
> the appropriate "additional" repository.

Thats a good approach - the maintainer of the package can then review it
before accepting into the development repository
 
> Will these updates eventually make it into the "official release"
> repositories, or do I need to manually submit them to the "official
> release" repositories?  

Talk to the maintainer, whether he submits it to Factory, or if he is fine if
you pick this part up.

Into Leap new packages are just submitted in case a bug report exists -
feature releases are not in scope, as Leap should be kept 'stable'.

> I'm not really sure of the workflow here -- I'm
> not a SUSE employee but just an external volunteer.

...as many of us here in the list.

Welcome to the team!
Axel
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Where to submit package updates

Simon Lees-3


On 21/08/17 18:32, Axel Braun wrote:

> Hello Tristan
>
> Am Montag, 21. August 2017, 10:32:48 CEST schrieb Tristan Miller:
>  
>> Certain packages I use from the "official release" repositories of
>> openSUSE 42.3 and Tumbleweed are out of date.  Some of these packages
>> are also found (in the same version) in additional repositories such as
>> "Archiving" or "multimedia:apps".
>>
>> Until now, when I want to revise a package so that it's using the
>> latest upstream version, I've been branching it on OBS, making the
>> necessary updates in my own project space, and then submitting it to
>> the appropriate "additional" repository.
>
> Thats a good approach - the maintainer of the package can then review it
> before accepting into the development repository
>  
>> Will these updates eventually make it into the "official release"
>> repositories, or do I need to manually submit them to the "official
>> release" repositories?  
>
> Talk to the maintainer, whether he submits it to Factory, or if he is fine if
> you pick this part up.
>
> Into Leap new packages are just submitted in case a bug report exists -
> feature releases are not in scope, as Leap should be kept 'stable'.
>
But if there is a new bugfix release and the maintainer is happy for you
to push it as an update to an already released Leap you can do so by
following the process here [1], note that the steps for 42.3 should be
the same as 42.2, I guess know one has got to updating the wiki page
recently.

1. https://en.opensuse.org/openSUSE:Maintenance_update_process

--

Simon Lees (Simotek)                            http://simotek.net

Emergency Update Team                           keybase.io/simotek
SUSE Linux                           Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B


signature.asc (499 bytes) Download Attachment