[ 
https://issues.apache.org/jira/browse/PROTON-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated PROTON-1792:
-----------------------------------
    Description: 
The Python bindings for proton-c are published at PyPi, and in order to allow a 
seemless install there, a system was added such that if the relevant proton-c 
version couldn't be located on the system already then the setup
would implicitly compile and install a local version for use.

Unfortunately, when this functionality was added in earlier releases, around 
0.9, reference was made to apache.org/dist/qpid/proton/ to download the 
matching release archive for installation.

The 0.15.0 package at PyPi instead got the files via the GitHub mirror for the 
source repo, and so wasn't affected.

The issue was addressed in proton-0.16.0 via PROTON-1330, to distribute the 
needed proton-c files within the generated python binding source bundle.

As a result of the issue older releases have been left at 
apache.org/dist/qpid/proton/ longer than they should, and also on the mirrors 
as a side effect of this, to avoid breaking things for actually relying on the 
bindings implicit proton-c install functionality.

Now that significant time has passed since a release was last affected by the 
issue, and from chatting with [~kgiusti] and [~jr...@redhat.com] we aren't 
aware of significant remaining usage of these older versions by other projects, 
it seems a reasonable time to now clear them out.

Anyone affected can still use the older python binding versions by grabbing the 
appropriate proton release from the 
[archives|https://archive.apache.org/dist/qpid/proton/] and installing from 
source, if there is a reason they cant simply upgrade to a newer version.

  was:
The Python bindings for proton-c are published at PyPi, and in order to allow a 
seemless install there, a system was added such that if the relevant proton-c 
version couldn't be located on the system already then the setup
would implicitly compile and install a local version for use.

Unfortunately, when this functionality was added in earlier releases, around 
0.9, reference was made to apache.org/dist/qpid/proton/ to download the 
matching release archive for installation.

The 0.15.0 package at PyPi instead got the files via the GitHub mirror for the 
source repo, and so wasn't affected.

The issue was addressed in proton-0.16.0 via PROTON-1330, to distribute the 
needed proton-c files within the generated python binding source bundle.

As a result of the issue older releases have been left at 
apache.org/dist/qpid/proton/ longer than they should, and also on the mirrors 
as a side effect of this, to avoid breaking things for actually relying on the 
bindings implicit proton-c install functionality.

Now that significant time has passed since a release was last affected by the 
issue, and from chatting with [~kgiusti] and [~jr...@redhat.com] we aren't 
aware of significant remaining usage of these older versions by other projects, 
it seems a reasonable time to now clear them out.

Anyone affected can still use the older python binding versions by grabbing the 
appropriate proton release from the archives and installing from source, if 
there is a reason they cant simply upgrade to a newer version.


> clean out older releases from the dist repo
> -------------------------------------------
>
>                 Key: PROTON-1792
>                 URL: https://issues.apache.org/jira/browse/PROTON-1792
>             Project: Qpid Proton
>          Issue Type: Task
>          Components: release
>            Reporter: Robbie Gemmell
>            Priority: Major
>
> The Python bindings for proton-c are published at PyPi, and in order to allow 
> a seemless install there, a system was added such that if the relevant 
> proton-c version couldn't be located on the system already then the setup
> would implicitly compile and install a local version for use.
> Unfortunately, when this functionality was added in earlier releases, around 
> 0.9, reference was made to apache.org/dist/qpid/proton/ to download the 
> matching release archive for installation.
> The 0.15.0 package at PyPi instead got the files via the GitHub mirror for 
> the source repo, and so wasn't affected.
> The issue was addressed in proton-0.16.0 via PROTON-1330, to distribute the 
> needed proton-c files within the generated python binding source bundle.
> As a result of the issue older releases have been left at 
> apache.org/dist/qpid/proton/ longer than they should, and also on the mirrors 
> as a side effect of this, to avoid breaking things for actually relying on 
> the bindings implicit proton-c install functionality.
> Now that significant time has passed since a release was last affected by the 
> issue, and from chatting with [~kgiusti] and [~jr...@redhat.com] we aren't 
> aware of significant remaining usage of these older versions by other 
> projects, it seems a reasonable time to now clear them out.
> Anyone affected can still use the older python binding versions by grabbing 
> the appropriate proton release from the 
> [archives|https://archive.apache.org/dist/qpid/proton/] and installing from 
> source, if there is a reason they cant simply upgrade to a newer version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to