Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu 14 complaining that the deb package is bad quality #17185

Closed
clintongormley opened this issue Mar 18, 2016 · 8 comments · Fixed by #41561
Closed

Ubuntu 14 complaining that the deb package is bad quality #17185

clintongormley opened this issue Mar 18, 2016 · 8 comments · Fixed by #41561
Labels
:Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts help wanted adoptme >regression Team:Delivery Meta label for Delivery team

Comments

@clintongormley
Copy link

While installing the DEB package downloaded from here on Ubuntu 14.04:
https://www.elastic.co/thank-you?url=https://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/distribution/deb/elasticsearch/2.2.1/elasticsearch-2.2.1.deb

The package is of bad quality

The installation of a package which violates the quality standards
isn't allowed. This could cause serious problems on your computer.
Please contact the person or organisation who provided this package
file and include the details beneath.

Lintian check results for /home/user/Setups/elasticsearch-2.2.1.deb:
E: elasticsearch: dir-or-file-in-var-run var/run/elasticsearch/

This has been reported previously in #2515 and #14532 and was previously resolved in a5f9173

It looks like we need to revisit the lintian overrides

@clintongormley clintongormley added >regression help wanted adoptme :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts labels Mar 18, 2016
@jordansissel
Copy link
Contributor

I think this is due to using the Ubuntu App Center (or something?) to install the package.

dpkg and apt-get do not complain about this:

Example using dpkg:

root@ubuntu-2gb-sfo1-01:~# lsb_release -d
Description:    Ubuntu 14.04.4 LTS

root@ubuntu-2gb-sfo1-01:~# wget https://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/distribution/deb/elasticsearch/2.2.1/elasticsearch-2.2.1.deb

2016-03-18 07:31:28 (8.63 MB/s) - ‘elasticsearch-2.2.1.deb’ saved [29307500/29307500]

root@ubuntu-2gb-sfo1-01:~# dpkg -i elasticsearch-2.2.1.deb
Selecting previously unselected package elasticsearch.
(Reading database ... 86823 files and directories currently installed.)
Preparing to unpack elasticsearch-2.2.1.deb ...
Creating elasticsearch group... OK
Creating elasticsearch user... OK
Unpacking elasticsearch (2.2.1) ...
Setting up elasticsearch (2.2.1) ...
Processing triggers for ureadahead (0.100.0-16) ...

@clintongormley
Copy link
Author

Yes, apparently the App Center does a Lintian check. That said, we added Lintian overrides to work around this previously, but it looks like we need to update them.

@nik9000
Copy link
Member

nik9000 commented Mar 18, 2016

I guess it is just more stuff to add to the bats tests....

@LeeDr
Copy link
Contributor

LeeDr commented Mar 18, 2016

Do we know the steps to reproduce this? I've only used dpkg and apt-get to install. We likely have the same issue across our other products?

@nik9000
Copy link
Member

nik9000 commented Mar 18, 2016

Do we know the steps to reproduce this?

We can likely run the same linting the App Center does. I haven't made sure of it but I'm 99% sure we can reproduce if we want.

@jakommo
Copy link
Contributor

jakommo commented Mar 18, 2016

@jasontedor
Copy link
Member

It looks like we need to revisit the lintian overrides

I don't think that we should override this one; I think that we should move the creation of /var/run/elasticsearch to the init script on service start (instead of when the package is installed), and destroy it when the service stops (instead of when the package is removed).

@nik9000
Copy link
Member

nik9000 commented Mar 18, 2016

I'm ok with that.

rjernst added a commit to rjernst/elasticsearch that referenced this issue Apr 26, 2019
The deb package has been updated several times in the past to contain
overrides in order to pass lintian inspection. However, there have never
been any tests to ensure we do not fallback to failure. This commit
updates the overrides file given things that have changed since 2.x like
adding ML and bundling the jdk.

closes elastic#17185
rjernst added a commit that referenced this issue May 8, 2019
The deb package has been updated several times in the past to contain
overrides in order to pass lintian inspection. However, there have never
been any tests to ensure we do not fallback to failure. This commit
updates the overrides file given things that have changed since 2.x like
adding ML and bundling the jdk.

closes #17185
rjernst added a commit to rjernst/elasticsearch that referenced this issue May 8, 2019
The deb package has been updated several times in the past to contain
overrides in order to pass lintian inspection. However, there have never
been any tests to ensure we do not fallback to failure. This commit
updates the overrides file given things that have changed since 2.x like
adding ML and bundling the jdk.

closes elastic#17185
rjernst added a commit that referenced this issue May 8, 2019
The deb package has been updated several times in the past to contain
overrides in order to pass lintian inspection. However, there have never
been any tests to ensure we do not fallback to failure. This commit
updates the overrides file given things that have changed since 2.x like
adding ML and bundling the jdk.

closes #17185
Megamiun pushed a commit to Megamiun/elasticsearch that referenced this issue May 18, 2019
The deb package has been updated several times in the past to contain
overrides in order to pass lintian inspection. However, there have never
been any tests to ensure we do not fallback to failure. This commit
updates the overrides file given things that have changed since 2.x like
adding ML and bundling the jdk.

closes elastic#17185
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this issue May 27, 2019
The deb package has been updated several times in the past to contain
overrides in order to pass lintian inspection. However, there have never
been any tests to ensure we do not fallback to failure. This commit
updates the overrides file given things that have changed since 2.x like
adding ML and bundling the jdk.

closes elastic#17185
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts help wanted adoptme >regression Team:Delivery Meta label for Delivery team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants