Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: future-release
    • Component/s: updatetool
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      1,112
    • Status Whiteboard:
      Hide

      mixed-owner-admin

      Show
      mixed-owner-admin
    • Tags:

      Description

      From an email

      Steven Dehandtschutter wrote:
      > When I try to update Java DB via updateTool (2.0) on Mac OS X 10.5.6
      > (after seeing the message that an update was available for Glassfish), I
      > get the following error:
      >
      >
      > Application ID: [Update Tool 2.0.0 (Build 15.1269)]
      > Timestamp : [2009-02-12 21:01:22 CET(+0100)]
      > wx Version : [2.8.8.0]
      > wx Platform : [__WXMAC__]
      > Python Version: [UNKNOWN]
      > Platform : [UNKNOWN]
      >
      > Traceback (innermost last):
      > File
      >
      "/Applications/NetBeans/glassfish-v3-prelude/updatetool/vendor-packages/updatetool/ips.py",

      > line 858, in Run
      > self.iplan.execute()
      > File
      >
      "/Applications/NetBeans/glassfish-v3-prelude/pkg/vendor-packages/pkg/client/imageplan.py",

      > line 453, in execute
      > p.execute_removal(src, dest)
      > File
      >
      "/Applications/NetBeans/glassfish-v3-prelude/pkg/vendor-packages/pkg/client/pkgplan.py",

      > line 303, in execute_removal
      > src.remove(self)
      > File
      >
      "/Applications/NetBeans/glassfish-v3-prelude/pkg/vendor-packages/pkg/actions/file.py",

      > line 271, in remove
      > os.chmod(path, S_IWRITE|S_IREAD)
      > OSError: [Errno 1] Operation not permitted:
      > '/Applications/NetBeans/glassfish-v3-prelude/javadb/CHANGES'
      >
      >
      > Seems to me that the updater should ask for my user/pwd (default Mac
      > dialog), not?
      >
      > hope this helps!
      >
      > Steven

        Activity

        Hide
        Snjezana Sevo-Zenzerovic added a comment -

        Corresponding GlassFish issue:

        https://glassfish.dev.java.net/issues/show_bug.cgi?id=7190

        Please update the issue with UC 2.3 specific status.

        Show
        Snjezana Sevo-Zenzerovic added a comment - Corresponding GlassFish issue: https://glassfish.dev.java.net/issues/show_bug.cgi?id=7190 Please update the issue with UC 2.3 specific status.
        Hide
        Joe Di Pol added a comment -

        Cleared whiteboard as this was not implemented in 2.3

        Show
        Joe Di Pol added a comment - Cleared whiteboard as this was not implemented in 2.3
        Hide
        ckamps added a comment -

        Tracking Issues
        ===============
        In addition to updates having been made to the following GlassFish v3 tracking
        issue:

        https://glassfish.dev.java.net/issues/show_bug.cgi?id=7190

        Tracking issues have been filed for the GlassFish v3 + Eclipse bundle and the
        GlassFish v3 + NetBeans bundles:

        Eclipse bundle:

        https://glassfishplugins.dev.java.net/issues/show_bug.cgi?id=257

        In this bundle, Ludo implemented the code based workaround as described in the
        issue report. Therefore, future builds of the Eclipse + v3 bundle won't have
        this issue.

        NetBeans bundle:

        https://netbeans.org/bugzilla/show_bug.cgi?id=177872

        A similar code-based workaround could be applied by the NetBeans in this case,
        but we will have to wait for the NetBeans team's evaluation of the issue.

        End User Workaround
        ===================
        In the meantime, the end user can apply one of these workarounds when the owning
        user is different from the current user:

        • Preferred: Perform a chown -R to set the ownership of the GlassFish
          installation to the user that will typically manage that installation. For
          example:

        sudo chown -R ckamps:admin /Applications/NetBeans/glassfishv3

        Where in this example "ckamps" is the developer's user ID and "glassfishv3"
        should represent the install location of GlassFish.

        This workaround is a one-time step after which the user can directly execute
        the bin/updatetool and bin/pkg tools directly. It also enables the background
        notifier to periodically inspect the installation for updates and, when updates
        are available, enables the Software Update GUI to operate properly.

        • A partial workaround is to use "sudo bin/updatetool" and "sudo bin/pkg" with
          the existing ownership in place. The shortcoming of this approach is that the
          background notifier which is automatically started as a desktop login task and
          any execution of the Software Update GUI will not work properly.
        Show
        ckamps added a comment - Tracking Issues =============== In addition to updates having been made to the following GlassFish v3 tracking issue: https://glassfish.dev.java.net/issues/show_bug.cgi?id=7190 Tracking issues have been filed for the GlassFish v3 + Eclipse bundle and the GlassFish v3 + NetBeans bundles: Eclipse bundle: https://glassfishplugins.dev.java.net/issues/show_bug.cgi?id=257 In this bundle, Ludo implemented the code based workaround as described in the issue report. Therefore, future builds of the Eclipse + v3 bundle won't have this issue. NetBeans bundle: https://netbeans.org/bugzilla/show_bug.cgi?id=177872 A similar code-based workaround could be applied by the NetBeans in this case, but we will have to wait for the NetBeans team's evaluation of the issue. End User Workaround =================== In the meantime, the end user can apply one of these workarounds when the owning user is different from the current user: Preferred: Perform a chown -R to set the ownership of the GlassFish installation to the user that will typically manage that installation. For example: sudo chown -R ckamps:admin /Applications/NetBeans/glassfishv3 Where in this example "ckamps" is the developer's user ID and "glassfishv3" should represent the install location of GlassFish. This workaround is a one-time step after which the user can directly execute the bin/updatetool and bin/pkg tools directly. It also enables the background notifier to periodically inspect the installation for updates and, when updates are available, enables the Software Update GUI to operate properly. A partial workaround is to use "sudo bin/updatetool" and "sudo bin/pkg" with the existing ownership in place. The shortcoming of this approach is that the background notifier which is automatically started as a desktop login task and any execution of the Software Update GUI will not work properly.
        Hide
        ckamps added a comment -

        sudo doesn't look like a viable workaround when using Update Tool on Mac OS X:

        https://updatecenter2.dev.java.net/issues/show_bug.cgi?id=768

        Show
        ckamps added a comment - sudo doesn't look like a viable workaround when using Update Tool on Mac OS X: https://updatecenter2.dev.java.net/issues/show_bug.cgi?id=768
        Hide
        ckamps added a comment -

        Changing from just Mac OS X to a general feature for Unix platforms. Windows
        Vista and Windows 7 are already being addressed in separate RFEs.

        This feature calls for the toolkit GUI tools to automatically detect situations
        when elevated privileges are required and to enable the user to put those
        privileges into effect without leaving the GUI tools. In some cases, the end
        user's ID must already be capable of reaching such elevation. Without a
        prerequisite in place, the user may still not be able to attain the required
        privileges.

        This feature applies to the Update Tool GUI and notifier balloon and SW Update
        GUI tools.

        The pkg(1) CLI is likely out of scope for this feature.

        As an incremental step in this direction, the following RFE calls for detection
        and notification of the requirement for elevated privileges:

        https://updatecenter2.dev.java.net/issues/show_bug.cgi?id=1925

        This incremental RFE is being evaluated for 2.4.

        Show
        ckamps added a comment - Changing from just Mac OS X to a general feature for Unix platforms. Windows Vista and Windows 7 are already being addressed in separate RFEs. This feature calls for the toolkit GUI tools to automatically detect situations when elevated privileges are required and to enable the user to put those privileges into effect without leaving the GUI tools. In some cases, the end user's ID must already be capable of reaching such elevation. Without a prerequisite in place, the user may still not be able to attain the required privileges. This feature applies to the Update Tool GUI and notifier balloon and SW Update GUI tools. The pkg(1) CLI is likely out of scope for this feature. As an incremental step in this direction, the following RFE calls for detection and notification of the requirement for elevated privileges: https://updatecenter2.dev.java.net/issues/show_bug.cgi?id=1925 This incremental RFE is being evaluated for 2.4.

          People

          • Assignee:
            Joe Di Pol
            Reporter:
            mnsingh
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: