Skip to content

[BUG] Building DMS fails with DOVECOT_COMMUNITY_REPO=1 #2935

@casperklein

Description

@casperklein

Miscellaneous first checks

  • I checked that all ports are open and not blocked by my ISP / hosting provider.
  • I know that SSL errors are likely the result of a wrong setup on the user side and not caused by DMS itself. I'm confident my setup is correct.

Affected Component(s)

Building DMS

What happened and when does this occur?

#18 31.67 [  TRACE  ]  Using Dovecot community repository
#18 31.67 gpg: directory '/root/.gnupg' created
#18 31.67 gpg: keybox '/root/.gnupg/pubring.kbx' created
#18 31.68   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
#18 31.68                                  Dload  Upload   Total   Spent    Left  Speed
100  3129  100  3129    0     0  41171      0 --:--:-- --:--:-- --:--:-- 41720
#18 31.75 gpg: /root/.gnupg/trustdb.gpg: trustdb created
#18 31.75 gpg: key 18A348AEED409DA1: public key "Dovecot Community Edition <[email protected]>" imported
#18 31.76 gpg: Total number processed: 1
#18 31.76 gpg:               imported: 1
#18 31.76 [  TRACE  ]  Updating Dovecot package signatures
#18 31.84 Hit:1 http://deb.debian.org/debian bullseye InRelease
#18 31.85 Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease
#18 31.86 Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
#18 31.91 Get:4 https://repo.dovecot.org/ce-2.3-latest/debian/bullseye bullseye InRelease [1747 B]
#18 32.17 Get:5 https://repo.dovecot.org/ce-2.3-latest/debian/bullseye bullseye/main amd64 Packages [6759 B]
#18 32.18 Fetched 8506 B in 0s (21.2 kB/s)
#18 32.18 Reading package lists...
#18 32.48 [  DEBUG  ]  Installing Dovecot
#18 32.49 Reading package lists...
#18 32.77 Building dependency tree...
#18 32.87 Reading state information...
#18 32.90 Some packages could not be installed. This may mean that you have
#18 32.90 requested an impossible situation or if you are using the unstable
#18 32.90 distribution that some required packages have not yet been created
#18 32.90 or been moved out of Incoming.
#18 32.90 The following information may help to resolve the situation:
#18 32.90
#18 32.90 The following packages have unmet dependencies:
#18 32.94  dovecot-fts-xapian : Depends: dovecot-abi-2.3.abiv13
#18 32.94 E: Unable to correct problems, you have held broken packages.
#18 ERROR: executor failed running [/bin/bash -e -o pipefail -c /bin/bash /build/packages.sh]: exit code: 100

What did you expect to happen?

Build should succeed.

How do we replicate the issue?

docker build -t test --build-arg DOVECOT_COMMUNITY_REPO=1 .

DMS version

edge

What operating system is DMS running on?

Linux

Which operating system version?

Debian 11

What instruction set architecture is DMS running on?

x86_64 / AMD64

What container orchestration tool are you using?

Docker

docker-compose.yml

No response

Relevant log output

No response

Other relevant information

dovecot-fts-xapian changelog:

  * Generate dependency on dovecot ABI in use during build.
    Technique stolen from dovecot-antispam packaging.
    Thanks to Ron Lee <[email protected]> (Closes: #1009794)

This adds a dependency for the package dovecot-abi-2.3.abiv13. dovecot-abi-2.3.abiv13 is a virtual package provided by dovecot-core (1:2.3.13+dfsg1-2+deb11u1).

However, the dovecot community repo provides dovecot-core: 2:2.3.19.1-2+debian11, so the dependency is not met.

Possible solution: Creating and installing an empty dummy package dovecot-abi-2.3.abiv13, before installing dovecot.

What level of experience do you have with Docker and mail servers?

  • I am inexperienced with docker
  • I am rather experienced with docker
  • I am inexperienced with mail servers
  • I am rather experienced with mail servers
  • I am uncomfortable with the CLI
  • I am rather comfortable with the CLI

Code of conduct

Improvements to this form?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions