Broken deb source URL

[swaroopkundeti]

Unable to update package manager after adding deb source to source list

Fetched 4,510 kB in 2s (1,589 kB/s)
W: Failed to fetch http://packages.elasticsearch.org/logstashforwarder/debian/dists/stable/main/binary-amd64/Packages  404  Not Found [IP: 23.23.158.216 80]

W: Failed to fetch http://packages.elasticsearch.org/logstashforwarder/debian/dists/stable/main/binary-i386/Packages  404  Not Found [IP: 23.23.158.216 80]

E: Some index files failed to download. They have been ignored, or old ones used instead.

[jbianquetti]

+1

[jordansissel]

The repository you refer to was never intended to be for normal use; it was setup as a test a year ago and forgotten about. I noticed this and removed it last weekend.

We will be putting a supported apt repo online soon with the next release of lsf.

[evanccnyc]

Withdrawing the comment. My mistake.

[evanccnyc]

They all seemed to have disappeared at once.

[jbianquetti]

That's true. If docs point this repos as a trusted source, several of us
prefer a developer trusted build instead source code compilation, and
breaking provision process its a production problem for us.

El miércoles, 11 de febrero de 2015, evanccopengeo notifications@github.com
escribió:

http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-repositories.html
Any idea why this is referenced in this documentation then?

—
Reply to this email directly or view it on GitHub
#370 (comment)
.

[driskell]

@evanccopengeo Those docs only refer to Elasticsearch repository and not this forwarder one. Searching forwarder on the page finds nothing.

[jordansissel]

Hyperbole has taken over, I suppose. I'll address things.

why this is referenced in this documentation then?

Please read this document more carefully. It ONLY refers to the 'elasticsearch' repository. It doesn't mention logstash or logstash forwarder anywhere on the page.

They all seemed to have disappeared at once.

Please provide data. I tested the repos (logstash, elasticsearch) and all are functioning as expected. If you find otherwise, please provide specific data.

If docs point this repos as a trusted source

The docs, again, do not point at logstash forwarder repo.

a developer trusted build

You'll need to define what "developer trusted build" means, for me. I do not believe we have such a phrase anywhere in our documentation in reference to the package repositories.

instead source code compilation

Our packages are built from source. We do not inject any magical power at compilation time that would cause your build to deviate significantly from ours.

breaking provision process its a production problem for us

I understand. Please understand that everyone involved in this situation is human, and as a result, is capable of making mistakes.

I deleted a repository I thought to be unused and abandoned because so many users report that they some how stumbled across it, used it, and found it to have delivered poorly-functioning code. After many months of this, I decided it was worth deleting so that new users would not read some random blog post pointing them at a repository I didn't even know was used (and certainly wasn't documented or supported, best I can tell) and having them receive broken software.

I understand the impact this has had on many of you. Please watch the commits on this repository and see that I am actively working to resolve this problem.

[jordansissel]

I"ll put this in big text to make it more obvious. A summary:

WE ARE AWARE OF THE PROBLEM.

WE ARE WORKING TO FIX IT.

[derdanu]

+1

[kevinprince]

+1

[yeukhon]

+1 this breaks everyone....

[ghost]

+1

[ernetas]

@jordansissel is there an approximate estimate of how fast that will happen (days/weeks/months?) or should we switch to our local repos?

[jordansissel]

this breaks everyone

Please only speak for yourself.

[jordansissel]

I"ll put this in big text, again, to make it more obvious. A summary:

WE ARE AWARE OF THE PROBLEM.

WE ARE WORKING TO FIX IT.

[jordansissel]

I unlocked after thinking about the implications.

Please, folks, understand that we will put up an actually-supported repository of logstash-forwarder soon. I do not have an ETA.

[jordansissel]

There is no need to +1 this ticket. We are aware of the problem. We are working on a solution.

[jordansissel]

#385 tracks the implementation of a package repository. Closing this as duplicate.