openresty / openresty/openresty-packaging

Mark deb packages with security fixes as security updates

Open
#23 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
187
Forks
93
PR merge metrics
No merged PRs in 30d

Description

Hi,

I've noticed you've just released Openresty 1.11.2.4 in order to include the latest security fixes from upstream nginx version.

We only update our Ubuntu systems (automatically) with security fixes, but this new version isn't detected as a security release. In order to detect which security fixes do we have to apply, we use apt-show-versions command:

$ apt-show-versions | grep openresty

openresty:amd64/xenial 1.11.2.3-4~xenial1 upgradeable to 1.11.2.4-1~xenial1
openresty-openssl:amd64/xenial 1.0.2k-2~xenial1 uptodate
openresty-opm:amd64/xenial 1.11.2.3-4~xenial1 upgradeable to 1.11.2.4-1~xenial1
openresty-pcre:amd64/xenial 8.40-1~xenial1 uptodate
openresty-resty:all/xenial 1.11.2.3-4~xenial1 upgradeable to 1.11.2.4-1~xenial1
openresty-zlib:amd64/xenial 1.2.11-2~xenial1 uptodate

As you can see, all openresty packages are from "all/xenial" target. Instead of this, if these packages were marked as xenial-security they would be covered by the following command:

$ apt-show-versions | grep openresty | grep upgradeable | grep $(lsb_release -cs)-security

<no output>

Could you mark them as xenial-security instead of xenial when the new version is released because of a security fix?

Thanks

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the packaging scripts for Ubuntu releases and review how package targets are assigned. Use the apt-show-versions examples in the issue to verify the behavior; done means security-fix releases are marked for the xenial-security target instead of xenial.

Written by the indexing model from the issue text.

Assessment

Tech stack
nginx, ubuntu
Domain
operating-systems, release, security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.