#31033: cannot use macport on a private repository --------------------------------------+------------------------------------- Reporter: Bruno.Guillaume@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.0.1 Keywords: | Port: --------------------------------------+------------------------------------- Description changed by ryandesign@…: Old description:
With our own Macports repository {{{ http://wikilligramme.loria.fr/macport/daily/ }}}
the command {{{ sudo port info frig }}}
returns
{{{ Error: Unable to open port: tar: +CONTENTS: Not found in archive tar: Error exit delayed from previous errors. }}}
It seems that the problem comes from [https://trac.macports.org/browser/tags/release_2_0_1/base/src/macports1.0/ma... this line].
This line is removed in the trunk by the changeset [https://trac.macports.org/changeset/81830/trunk/base/src/macports1.0/macport... 81830].
When version 2.0.2 is planned?
Is there any clean way to avoid the problem until this new version?
New description: With our own Macports repository {{{ http://wikilligramme.loria.fr/macport/daily/ }}} the command {{{ sudo port info frig }}} returns {{{ Error: Unable to open port: tar: +CONTENTS: Not found in archive tar: Error exit delayed from previous errors. }}} It seems that the problem comes from [browser:tags/release_2_0_1/base/src/macports1.0/macports.tcl#L1177 this line]. This line is removed in the trunk by the changeset [changeset:81830/trunk/base/src/macports1.0/macports.tcl 81830]. When version 2.0.2 is planned? Is there any clean way to avoid the problem until this new version? -- -- Ticket URL: <https://trac.macports.org/ticket/31033#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS