owasp-modsecurity / owasp-modsecurity/ModSecurity
Debian package dependencies are broken
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
Hi @airween,
I'm trying to install modsecurity3 latest for nginx from sid.
Apparently there is a minor fix in 3.0.12 leading to a version 3.0.12-1.1 .
However this fix has been added only to libmodsecurity3-dev and not libmodsecurity3.
So I get an error on installing
> [linux/amd64 stage-0 9/35] RUN set -x && apt-get update && apt-get -t sid install -y --no-install-recommends libmodsecurity-dev=3.0.12-1.1 libmodsecurity3=3.0.12-1:
6.700 Reading state information...
6.939 Some packages could not be installed. This may mean that you have
6.939 requested an impossible situation or if you are using the unstable
6.939 distribution that some required packages have not yet been created
6.939 or been moved out of Incoming.
6.939 The following information may help to resolve the situation:
6.939
6.940 The following packages have unmet dependencies:
7.205 libmodsecurity3t64 : Breaks: libmodsecurity3 (< 3.0.12-1.1)
7.211 E: Unable to correct problems, you have held broken packages.
------
IIRC 3.0.12-1.1 was available for some time, but has been removed. Could that be?
For the time being I have removed libmodsecurity-dev and changed my Dockerfile to work around this.
Can you please have a look?
Peter
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported Docker build step with apt-get -t sid and the pinned libmodsecurity-dev and libmodsecurity3 versions. Inspect the Debian package versions and dependency metadata for libmodsecurity3t64; done means the requested packages install together without the reported Breaks or unmet-dependency error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, docker
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100