Bug 1012847 - ooRexx shouldn't ship any preset file
ooRexx shouldn't ship any preset file
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Other
Leap 42.2
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: Erico Mendonca
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-30 15:55 UTC by Franck Bui
Modified: 2018-10-26 22:23 UTC (History)
5 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Franck Bui 2016-11-30 15:55:15 UTC
Hi,

Preset files are supposed to be shipped by the branding package so the secteam can review carefully which packages are enabled by default on a given distro.

Could anybody move the content of the preset file to the branding package ?

Thanks.
Comment 1 Erico Mendonca 2016-12-01 16:40:13 UTC
(In reply to Franck Bui from comment #0)
> Hi,
> 
> Preset files are supposed to be shipped by the branding package so the
> secteam can review carefully which packages are enabled by default on a
> given distro.
> 
> Could anybody move the content of the preset file to the branding package ?
> 
> Thanks.

Hi Franck,

Do you mean create a branding subpackage with just this file, or move it to the system branding package?

We could remove it as well, and leave it up to the user to enable the service.
Comment 2 Marcus Meissner 2016-12-01 16:55:51 UTC
we would prefer to leave it to the user to enable it
Comment 3 Franck Bui 2016-12-01 17:01:35 UTC
Hi Erico,

I meant move it to the main branding package.

However I think it's safe to assume that packages are disabled by default (Marcus, please correct me if I'm wrong).

So if this default is fine for you and you want to let the user enable explicitly your service, then you shouldn't ship anything.

However if you think that your service should be enabled by default then you should request to the secteam a new entry in the "system" branding package.

This is described here: https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines#Enabling_systemd_unit_files

Thanks.
Comment 4 Erico Mendonca 2016-12-02 21:57:51 UTC
Done!
I removed the preset file and added a message in the %post informing the user that he/she should enable the service manually.

https://build.opensuse.org/package/show/devel:languages:misc/ooRexx
Comment 5 Franck Bui 2016-12-05 07:27:11 UTC
Thanks Erico !
Comment 6 Erico Mendonca 2017-01-23 13:16:58 UTC
Forgot to change the status :)
Comment 7 Swamp Workflow Management 2018-10-12 11:00:08 UTC
This is an autogenerated message for OBS integration:
This bug (1012847) was mentioned in
https://build.opensuse.org/request/show/641633 15.0+15.0:NonFree+42.3+42.3:NonFree+Backports:SLE-12+Backports:SLE-15 / Regina-REXX+THE+ooRexx
Comment 8 Swamp Workflow Management 2018-10-26 22:17:12 UTC
openSUSE-RU-2018:3507-1: An update that has four recommended fixes can now be installed.

Category: recommended (low)
Bug References: 1012847,1017668,1083875,985384
CVE References: 
Sources used:
openSUSE Leap 42.3:NonFree (src):    THE-3.3~RC4-3.3.1
openSUSE Leap 42.3 (src):    Regina-REXX-3.9.1-4.3.1, ooRexx-4.2.0-6.3.1
openSUSE Leap 15.0:NonFree (src):    THE-3.3~RC4-lp150.2.3.1
openSUSE Leap 15.0 (src):    Regina-REXX-3.9.1-lp150.2.3.1, ooRexx-4.2.0-lp150.3.3.2
openSUSE Backports SLE-15 (src):    Regina-REXX-3.9.1-bp150.3.3.1, ooRexx-4.2.0-bp150.3.3.1
Comment 9 Swamp Workflow Management 2018-10-26 22:23:33 UTC
openSUSE-RU-2018:3518-1: An update that has four recommended fixes can now be installed.

Category: recommended (low)
Bug References: 1012847,1017668,1083875,985384
CVE References: 
Sources used:
SUSE Package Hub for SUSE Linux Enterprise 12 (src):    Regina-REXX-3.9.1-5.1, Regina-REXX-3.9.1-5.2