updatecenter2
  1. updatecenter2
  2. UPDATECENTER2-2017

pkgsend man page doesn't say what happens if publish manifest is missing

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Incomplete
    • Affects Version/s: B44
    • Fix Version/s: not determined
    • Component/s: ipsenhancement
    • Labels:
      None
    • Environment:

      Operating System: Linux
      Platform: Sun

    • Issuezilla Id:
      2,017

      Description

      Steps to reproduce :

      • Start a local repo using the URL : <repo1_url> and publish a package pkg1@2.1
        to it
      • using pkgrecv command, copy this package to a directory destination

      pkgrecv -s <repo1_url> -d <pkg1_dir> pkg1

      • Start a second repo using the URL : <repo2_url>
      • Use the following command to publish pkg1 from the directory <pkg1_dir> to the
        repo2

      pkgsend -s <repo2_url> publish -d <pkg1_dir>/pkg1 pkg1@2.1

      This command is wrong because there is a missing argument which is the Manifest
      path : <pkg1_dir>/pkg1/FMRI/Manifest

      Instead of having an error message displayed with what's wrong, the pkgsend
      command does not return

      The user needs to perform Ctrl C in order to stop the process

        Activity

        Hide
        Tom Mueller added a comment -

        When the manifest argument is missing, the publish command reads the manifest
        from standard input. So the command was not hung, it was waiting for the user to
        enter a manifest.

        The manual page properly indicates that the manifest (or list of manifests) is
        an optional argument to the command. However, the description of the publish
        subcommand doesn't state what happens if the manifest is missing, i.e., that the
        manifest is read from standard input.

        Show
        Tom Mueller added a comment - When the manifest argument is missing, the publish command reads the manifest from standard input. So the command was not hung, it was waiting for the user to enter a manifest. The manual page properly indicates that the manifest (or list of manifests) is an optional argument to the command. However, the description of the publish subcommand doesn't state what happens if the manifest is missing, i.e., that the manifest is read from standard input.
        Hide
        Tom Mueller added a comment -

        Looking a bit further, the pkgsend manual page says that the publish subcommand
        combines the open, include, and close subcommands in one step. And the
        documentation for the include subcommand says that if the manifest is provided,
        it is read from standard input.

        So this is covered in the manual page. Closing this bug as invalid.

        Show
        Tom Mueller added a comment - Looking a bit further, the pkgsend manual page says that the publish subcommand combines the open, include, and close subcommands in one step. And the documentation for the include subcommand says that if the manifest is provided, it is read from standard input. So this is covered in the manual page. Closing this bug as invalid.

          People

          • Assignee:
            Tom Mueller
            Reporter:
            faouzia
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: