[hafqa] [hafqa] [Bug 3764] SSU Update 4.2008.36-5 over-writes /etc/sudoers

[From: bugzilla-daemon at maemo.org]

https://bugs.maemo.org/show_bug.cgi?id=3764


eero.tamminen at nokia.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eero.tamminen at nokia.com,
                   |                            |marius.vollmer at nokia.com




------- Comment #5 from eero.tamminen at nokia.com  2008-10-07 17:42 GMT+3 -------
This finds packages manipulating /etc/sudoers:
  grep sudoers /var/lib/dpkg/info/*inst

The postinst scripts manipulating /etc/sudoers directly seem to be just
appending their information, but there are a few packages calling
/usr/sbin/update-sudoers directly which overwrites /etc/sudoers based on the
files in /etc/sudoers.d/:
- sudo
  - for base stuff
- osso-app-killer
  - to do mount handling (why here?) and stopping services
- osso-af-startup
  - for ke-recv, alarm etc
- hildon-application-manager
  - to do package updates
- hildon-input-method-configurator
  - to configure input method (from CP?)


I think the current mix of some packages updating /etc/sudoers directly and
some packages overwriting it completely with update-sudoers will break if only
the update-sudoers using packages are updated or they are otherwise installed
after the packages that update the /etc/sudoers file directly:
- osso-bluez-compat
  - for backup restore script
- osso-bookmark-ui
  - for bookmark cleaner in resetting to factory settings
- rhapsody-installer
  - to install Rhapsody .desktop file which has already a public bug
(- osso-gwconnect, commented out)

Then the /etc/sudoers modifications by these packages get lost in the SSU
update.  Marius, any comments?


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
Replies to this email are NOT read, instead please add comments at
https://bugs.maemo.org/show_bug.cgi?id=3764
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.