FAQ
Edit report at http://pear.php.net/bugs/bug.php?id=18278&edit=1

ID: 18278
Updated by: helgith@gmail.com
Reported By: jan at horde dot org
Summary: channel-update updating from wrong server
Status: Assigned
Type: Bug
Package: PEAR
Package Version: 1.9.1
PHP Version: Irrelevant
Assigned To: dufuz
Roadmap Versions:
New Comment:

The issue with making this work is in theory (as stupid as it may be),
you could have
different REST endpoints depending on the REST version, thus making it
mostly
unreliable to use for a base.

I could take the first endpoint but ideally I would have to add a new
tag (hostname)
or similar. The name has always been used as a hostname; Any reason why
you can't
change the name part in pear.local?


Previous Comments:
------------------------------------------------------------------------

[2011-02-27 16:23:00] dufuz

-Assigned To:
+Assigned To: dufuz


------------------------------------------------------------------------

[2011-02-15 15:59:36] yunosh

Description:
------------
If running the "channel-update" command, this works as if you run
"channel-discover <channelname>".

This is wrong, because the channel name might not match the server name.
The updated channel configuration should be fetched from the server
configured in the channel information instead.

Some example:
I have a local installation of the Horde PEAR server for testing
purposes. To install this channel, I run:
$ pear channel-discover pear.local
I then have a channel named pear.horde.org, alias horde, with REST
endpoint pointing to http://pear.local/.
Everything works fine with this setup. Until I run:
$ pear channel-update horde
or
$ pear update-channels
At this point, instead of retreiving http://pear.local/channel.xml, PEAR
downloads http://pear.horde.org/channel.xml, overwriting the correct
channel information.
There is no way to revert to the old channel configuration either. I can
only uninstall all horde packages, channel-delete horde, and the start
from scratch.

------------------------------------------------------------------------

Search Discussions

  • Jan at Mar 9, 2011 at 12:22 am
    Edit report at http://pear.php.net/bugs/bug.php?id=18278&edit=1

    ID: 18278
    Updated by: jan@horde.org
    Reported By: jan at horde dot org
    Summary: channel-update updating from wrong server
    Status: Assigned
    Type: Bug
    Package: PEAR
    Package Version: 1.9.1
    PHP Version: Irrelevant
    Assigned To: dufuz
    Roadmap Versions:
    New Comment:

    What have REST endpoints to do with that? Isn't channel-update fetching
    channel.xml from the root directory?


    Previous Comments:
    ------------------------------------------------------------------------

    [2011-03-09 01:07:37] dufuz

    The issue with making this work is in theory (as stupid as it may be),
    you could have
    different REST endpoints depending on the REST version, thus making it
    mostly
    unreliable to use for a base.

    I could take the first endpoint but ideally I would have to add a new
    tag (hostname)
    or similar. The name has always been used as a hostname; Any reason why
    you can't
    change the name part in pear.local?

    ------------------------------------------------------------------------

    [2011-02-27 16:23:00] dufuz

    -Assigned To:
    +Assigned To: dufuz


    ------------------------------------------------------------------------

    [2011-02-15 15:59:36] yunosh

    Description:
    ------------
    If running the "channel-update" command, this works as if you run
    "channel-discover <channelname>".

    This is wrong, because the channel name might not match the server name.
    The updated channel configuration should be fetched from the server
    configured in the channel information instead.

    Some example:
    I have a local installation of the Horde PEAR server for testing
    purposes. To install this channel, I run:
    $ pear channel-discover pear.local
    I then have a channel named pear.horde.org, alias horde, with REST
    endpoint pointing to http://pear.local/.
    Everything works fine with this setup. Until I run:
    $ pear channel-update horde
    or
    $ pear update-channels
    At this point, instead of retreiving http://pear.local/channel.xml, PEAR
    downloads http://pear.horde.org/channel.xml, overwriting the correct
    channel information.
    There is no way to revert to the old channel configuration either. I can
    only uninstall all horde packages, channel-delete horde, and the start
    from scratch.

    ------------------------------------------------------------------------
  • Helgith at Mar 9, 2011 at 12:57 am
    Edit report at http://pear.php.net/bugs/bug.php?id=18278&edit=1

    ID: 18278
    Updated by: helgith@gmail.com
    Reported By: jan at horde dot org
    Summary: channel-update updating from wrong server
    Status: Assigned
    Type: Bug
    Package: PEAR
    Package Version: 1.9.1
    PHP Version: Irrelevant
    Assigned To: dufuz
    Roadmap Versions:
    New Comment:

    Then I don't understand your setup.

    pear.local/channel.xml -> pear.horde.org, horde -> rest points:
    pear.local
    pear.horde.org/channel.xml -> pear.horde.org, horde -> rest points:
    pear.horde.org

    Is it something like that?

    Can I see the pear.local channel.xml to understand what is happening?
    Looking at
    channel-discover and channel-update etc. use the channel->getName() to
    reference
    things throughout.


    Previous Comments:
    ------------------------------------------------------------------------

    [2011-03-09 01:25:46] yunosh

    What have REST endpoints to do with that? Isn't channel-update fetching
    channel.xml from the root directory?

    ------------------------------------------------------------------------

    [2011-03-09 01:07:37] dufuz

    The issue with making this work is in theory (as stupid as it may be),
    you could have
    different REST endpoints depending on the REST version, thus making it
    mostly
    unreliable to use for a base.

    I could take the first endpoint but ideally I would have to add a new
    tag (hostname)
    or similar. The name has always been used as a hostname; Any reason why
    you can't
    change the name part in pear.local?

    ------------------------------------------------------------------------

    [2011-02-27 16:23:00] dufuz

    -Assigned To:
    +Assigned To: dufuz


    ------------------------------------------------------------------------

    [2011-02-15 15:59:36] yunosh

    Description:
    ------------
    If running the "channel-update" command, this works as if you run
    "channel-discover <channelname>".

    This is wrong, because the channel name might not match the server name.
    The updated channel configuration should be fetched from the server
    configured in the channel information instead.

    Some example:
    I have a local installation of the Horde PEAR server for testing
    purposes. To install this channel, I run:
    $ pear channel-discover pear.local
    I then have a channel named pear.horde.org, alias horde, with REST
    endpoint pointing to http://pear.local/.
    Everything works fine with this setup. Until I run:
    $ pear channel-update horde
    or
    $ pear update-channels
    At this point, instead of retreiving http://pear.local/channel.xml, PEAR
    downloads http://pear.horde.org/channel.xml, overwriting the correct
    channel information.
    There is no way to revert to the old channel configuration either. I can
    only uninstall all horde packages, channel-delete horde, and the start
    from scratch.

    ------------------------------------------------------------------------
  • Jan at Mar 9, 2011 at 1:09 am
    Edit report at http://pear.php.net/bugs/bug.php?id=18278&edit=1

    ID: 18278
    Updated by: jan@horde.org
    Reported By: jan at horde dot org
    Summary: channel-update updating from wrong server
    Status: Assigned
    Type: Bug
    Package: PEAR
    Package Version: 1.9.1
    PHP Version: Irrelevant
    Assigned To: dufuz
    Roadmap Versions:
    New Comment:

    <?xml version="1.0" encoding="UTF-8" ?>
    <channel version="1.0" xmlns="http://pear.php.net/channel-1.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://pear.php.net/channel-1.0
    " rel="nofollow">http://pear.php.net/dtd/channel-1.0.xsd">
    <name>pear.horde.org</name>
    <summary>Horde PEAR test server</summary>
    <suggestedalias>horde</suggestedalias>
    <servers>
    <primary>
    <rest>
    <baseurl
    type="REST1.0">http://pear.wg.de/rest/</baseurl>
    <baseurl
    type="REST1.1">http://pear.wg.de/rest/</baseurl>
    <baseurl
    type="REST1.2">http://pear.wg.de/rest/</baseurl>
    <baseurl
    type="REST1.3">http://pear.wg.de/rest/</baseurl>
    </rest>
    </primary>
    </servers>
    </channel>


    Previous Comments:
    ------------------------------------------------------------------------

    [2011-03-09 02:00:31] dufuz

    Then I don't understand your setup.

    pear.local/channel.xml -> pear.horde.org, horde -> rest points:
    pear.local
    pear.horde.org/channel.xml -> pear.horde.org, horde -> rest points:
    pear.horde.org

    Is it something like that?

    Can I see the pear.local channel.xml to understand what is happening?
    Looking at
    channel-discover and channel-update etc. use the channel->getName() to
    reference
    things throughout.

    ------------------------------------------------------------------------

    [2011-03-09 01:25:46] yunosh

    What have REST endpoints to do with that? Isn't channel-update fetching
    channel.xml from the root directory?

    ------------------------------------------------------------------------

    [2011-03-09 01:07:37] dufuz

    The issue with making this work is in theory (as stupid as it may be),
    you could have
    different REST endpoints depending on the REST version, thus making it
    mostly
    unreliable to use for a base.

    I could take the first endpoint but ideally I would have to add a new
    tag (hostname)
    or similar. The name has always been used as a hostname; Any reason why
    you can't
    change the name part in pear.local?

    ------------------------------------------------------------------------

    [2011-02-27 16:23:00] dufuz

    -Assigned To:
    +Assigned To: dufuz


    ------------------------------------------------------------------------

    [2011-02-15 15:59:36] yunosh

    Description:
    ------------
    If running the "channel-update" command, this works as if you run
    "channel-discover <channelname>".

    This is wrong, because the channel name might not match the server name.
    The updated channel configuration should be fetched from the server
    configured in the channel information instead.

    Some example:
    I have a local installation of the Horde PEAR server for testing
    purposes. To install this channel, I run:
    $ pear channel-discover pear.local
    I then have a channel named pear.horde.org, alias horde, with REST
    endpoint pointing to http://pear.local/.
    Everything works fine with this setup. Until I run:
    $ pear channel-update horde
    or
    $ pear update-channels
    At this point, instead of retreiving http://pear.local/channel.xml, PEAR
    downloads http://pear.horde.org/channel.xml, overwriting the correct
    channel information.
    There is no way to revert to the old channel configuration either. I can
    only uninstall all horde packages, channel-delete horde, and the start
    from scratch.

    ------------------------------------------------------------------------
  • Helgith at Mar 9, 2011 at 1:18 am
    Edit report at http://pear.php.net/bugs/bug.php?id=18278&edit=1

    ID: 18278
    Updated by: helgith@gmail.com
    Reported By: jan at horde dot org
    Summary: channel-update updating from wrong server
    Status: Assigned
    Type: Bug
    Package: PEAR
    Package Version: 1.9.1
    PHP Version: Irrelevant
    Assigned To: dufuz
    Roadmap Versions:
    New Comment:

    There is nothing we can do without introducing a new tag to define the
    hostname or
    attempt to track the hostname (via the registry) based on what you
    initially used to
    discover the url.

    The whole point of the name tag has thus far been about using it as a
    hostname.

    I am open to other approaches we could take.


    Previous Comments:
    ------------------------------------------------------------------------

    [2011-03-09 02:12:07] yunosh

    <?xml version="1.0" encoding="UTF-8" ?>
    <channel version="1.0" xmlns="http://pear.php.net/channel-1.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://pear.php.net/channel-1.0
    " rel="nofollow">http://pear.php.net/dtd/channel-1.0.xsd">
    <name>pear.horde.org</name>
    <summary>Horde PEAR test server</summary>
    <suggestedalias>horde</suggestedalias>
    <servers>
    <primary>
    <rest>
    <baseurl
    type="REST1.0">http://pear.wg.de/rest/</baseurl>
    <baseurl
    type="REST1.1">http://pear.wg.de/rest/</baseurl>
    <baseurl
    type="REST1.2">http://pear.wg.de/rest/</baseurl>
    <baseurl
    type="REST1.3">http://pear.wg.de/rest/</baseurl>
    </rest>
    </primary>
    </servers>
    </channel>

    ------------------------------------------------------------------------

    [2011-03-09 02:00:31] dufuz

    Then I don't understand your setup.

    pear.local/channel.xml -> pear.horde.org, horde -> rest points:
    pear.local
    pear.horde.org/channel.xml -> pear.horde.org, horde -> rest points:
    pear.horde.org

    Is it something like that?

    Can I see the pear.local channel.xml to understand what is happening?
    Looking at
    channel-discover and channel-update etc. use the channel->getName() to
    reference
    things throughout.

    ------------------------------------------------------------------------

    [2011-03-09 01:25:46] yunosh

    What have REST endpoints to do with that? Isn't channel-update fetching
    channel.xml from the root directory?

    ------------------------------------------------------------------------

    [2011-03-09 01:07:37] dufuz

    The issue with making this work is in theory (as stupid as it may be),
    you could have
    different REST endpoints depending on the REST version, thus making it
    mostly
    unreliable to use for a base.

    I could take the first endpoint but ideally I would have to add a new
    tag (hostname)
    or similar. The name has always been used as a hostname; Any reason why
    you can't
    change the name part in pear.local?

    ------------------------------------------------------------------------

    [2011-02-27 16:23:00] dufuz

    -Assigned To:
    +Assigned To: dufuz


    ------------------------------------------------------------------------

    The remainder of the comments for this report are too long. To view
    the rest of the comments, please view the bug report online at
    http://pear.php.net/bugs/bug.php?id=18278
  • Jan at Mar 9, 2011 at 1:32 am
    Edit report at http://pear.php.net/bugs/bug.php?id=18278&edit=1

    ID: 18278
    Updated by: jan@horde.org
    Reported By: jan at horde dot org
    Summary: channel-update updating from wrong server
    Status: Assigned
    Type: Bug
    Package: PEAR
    Package Version: 1.9.1
    PHP Version: Irrelevant
    Assigned To: dufuz
    Roadmap Versions:
    New Comment:

    I assumed the host has already been tracked. A hackish approach could be
    to use the host name from the REST endpoints, but that's probably not
    more correct either, since a channel server could propagate endpoints on
    different host.
    I guess this is really just an edge case. I could understand if you
    close it because fixing it properly would be too much work for such a
    rare use case. Maybe consider it for Pyrus.


    Previous Comments:
    ------------------------------------------------------------------------

    [2011-03-09 02:21:44] dufuz

    There is nothing we can do without introducing a new tag to define the
    hostname or
    attempt to track the hostname (via the registry) based on what you
    initially used to
    discover the url.

    The whole point of the name tag has thus far been about using it as a
    hostname.

    I am open to other approaches we could take.

    ------------------------------------------------------------------------

    [2011-03-09 02:12:07] yunosh

    <?xml version="1.0" encoding="UTF-8" ?>
    <channel version="1.0" xmlns="http://pear.php.net/channel-1.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://pear.php.net/channel-1.0
    " rel="nofollow">http://pear.php.net/dtd/channel-1.0.xsd">
    <name>pear.horde.org</name>
    <summary>Horde PEAR test server</summary>
    <suggestedalias>horde</suggestedalias>
    <servers>
    <primary>
    <rest>
    <baseurl
    type="REST1.0">http://pear.wg.de/rest/</baseurl>
    <baseurl
    type="REST1.1">http://pear.wg.de/rest/</baseurl>
    <baseurl
    type="REST1.2">http://pear.wg.de/rest/</baseurl>
    <baseurl
    type="REST1.3">http://pear.wg.de/rest/</baseurl>
    </rest>
    </primary>
    </servers>
    </channel>

    ------------------------------------------------------------------------

    [2011-03-09 02:00:31] dufuz

    Then I don't understand your setup.

    pear.local/channel.xml -> pear.horde.org, horde -> rest points:
    pear.local
    pear.horde.org/channel.xml -> pear.horde.org, horde -> rest points:
    pear.horde.org

    Is it something like that?

    Can I see the pear.local channel.xml to understand what is happening?
    Looking at
    channel-discover and channel-update etc. use the channel->getName() to
    reference
    things throughout.

    ------------------------------------------------------------------------

    [2011-03-09 01:25:46] yunosh

    What have REST endpoints to do with that? Isn't channel-update fetching
    channel.xml from the root directory?

    ------------------------------------------------------------------------

    [2011-03-09 01:07:37] dufuz

    The issue with making this work is in theory (as stupid as it may be),
    you could have
    different REST endpoints depending on the REST version, thus making it
    mostly
    unreliable to use for a base.

    I could take the first endpoint but ideally I would have to add a new
    tag (hostname)
    or similar. The name has always been used as a hostname; Any reason why
    you can't
    change the name part in pear.local?

    ------------------------------------------------------------------------

    The remainder of the comments for this report are too long. To view
    the rest of the comments, please view the bug report online at
    http://pear.php.net/bugs/bug.php?id=18278

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppear-bugs @
categoriesphp
postedMar 9, '11 at 12:04a
activeMar 9, '11 at 1:32a
posts6
users2
websitepear.php.net

2 users in discussion

Jan: 3 posts Helgith: 3 posts

People

Translate

site design / logo © 2022 Grokbase