search

elastic / logstash

Logstash - transport and process your logs, events, or other data
https://www.elastic.co/products/logstash
Other
114 stars 3.51k forks source link

Debian package filenames don't follow the convention #5981

Open magnusbaeck opened 8 years ago

magnusbaeck commented 8 years ago

As of Logstash 2.4, the filenames of published Debian packages isn't following the Debian convention of an underscore between the package name and the package version. Additionally, the 5.0.0-beta1 filename doesn't include the architecture name. Example URLs currently linked from https://www.elastic.co/downloads/logstash:

These should've been logstash_2.4.0_all.deb and logstash_5.0.0-beta1_all.deb. Quoting §7.3 of the Debian FAQ:

The Debian binary package file names conform to the following convention: -.deb

jordansissel commented 8 years ago

I agree that they are different than upstream Debian package file names. However, I am not seeing this as a problem or a bug. Can you help me understand the negative impact of this? For example, does apt-get install logstash not work because of this?

jordansissel commented 8 years ago

For some background, as part of moving all Elastic products to a synchronized version, we also moved to make our artifacts consistently named. In practice, this will generally mean the projects that are architecture-independent will be product-version.filetype, and arch-dependent will be product-version-arch.filetype

shubb30 commented 5 years ago

My company uses an apt cache that our servers use to download packages. Our cache server has a regex pattern for valid packages that we have had to modify twice in order to use Elastic services. Once for Elasticsearch that uses dashes instead of underscores, and now for Logstash that does not include the arch in the filename.

What is the reasoning for not following the Debian package naming standard?