tileradotorg/synapse
1
0
Fork 0
forked from MirrorHub/synapse
Code Pull requests Activity
synapse/debian/control

45 lines
1.1 KiB
Text
Raw Normal View History

Debian packaging via dh_virtualenv (#4285)
2018-12-20 12:33:29 +01:00
Source: matrix-synapse-py3
Section: contrib/python
Priority: extra
Maintainer: Synapse Packaging team <packages@matrix.org>
Improve `Depends` specs in debian package. (#5675) This is basically a contrived way of adding a `Recommends` on `libpq5`, to fix #5653. The way this is supposed to happen in debhelper is to run `dh_shlibdeps`, which in turn runs `dpkg-shlibdeps`, which spits things out into `debian/<package>.substvars` whence they can later be included by `control`. Previously, we had disabled `dh_shlibdeps`, mostly because `dpkg-shlibdeps` gets confused about PIL's interdependent objects, but that's not really the right thing to do and there is another way to work around that. Since we don't always use postgres, we don't necessarily want a hard Depends on libpq5, so I've actually ended up adding an explicit invocation of `dpkg-shlibdeps` for `psycopg2`. I've also updated the build-depends list for the package, which was missing a couple of entries.
2019-07-17 18:47:07 +02:00
# keep this list in sync with the build dependencies in docker/Dockerfile-dhvirtualenv.
import from package-debian-synapse
2018-12-10 18:14:34 +01:00
Build-Depends:
Drop xenial-support hacks (#10429)
2021-07-21 22:25:28 +02:00
debhelper (>= 10),
Install the optional dependencies into the debian package (#4325) since #4298, the optional dependencies are no longer installed with a simple `pip install .`, which meant that they were not being included in the debian package. The easy fix to that is dh_virtualenv --extras, but that needs dh_virtualenv 1.1...
2019-01-02 08:17:39 +01:00
dh-virtualenv (>= 1.1),
Improve `Depends` specs in debian package. (#5675) This is basically a contrived way of adding a `Recommends` on `libpq5`, to fix #5653. The way this is supposed to happen in debhelper is to run `dh_shlibdeps`, which in turn runs `dpkg-shlibdeps`, which spits things out into `debian/<package>.substvars` whence they can later be included by `control`. Previously, we had disabled `dh_shlibdeps`, mostly because `dpkg-shlibdeps` gets confused about PIL's interdependent objects, but that's not really the right thing to do and there is another way to work around that. Since we don't always use postgres, we don't necessarily want a hard Depends on libpq5, so I've actually ended up adding an explicit invocation of `dpkg-shlibdeps` for `psycopg2`. I've also updated the build-depends list for the package, which was missing a couple of entries.
2019-07-17 18:47:07 +02:00
libsystemd-dev,
libpq-dev,
Debian packaging via dh_virtualenv (#4285)
2018-12-20 12:33:29 +01:00
lsb-release,
python3-dev,
python3,
python3-setuptools,
python3-pip,
python3-venv,
tar,
Update debian Conflicts specifications (#4349) ... to allow installation alongside our matrix-synapse transitional package.
2019-01-04 18:24:13 +01:00
Standards-Version: 3.9.8
Debian packaging via dh_virtualenv (#4285)
2018-12-20 12:33:29 +01:00
Homepage: https://github.com/matrix-org/synapse
import from package-debian-synapse
2018-12-10 18:14:34 +01:00
Debian packaging via dh_virtualenv (#4285)
2018-12-20 12:33:29 +01:00
Package: matrix-synapse-py3
Minor cleanup to Debian packaging (#11269) * Remove unused Vagrant scripts * Change package Architecture to any * Preinstall the wheel package when building venvs. Addresses the following warnings during Debian builds: Using legacy 'setup.py install' for jaeger-client, since package 'wheel' is not installed. Using legacy 'setup.py install' for matrix-synapse-ldap3, since package 'wheel' is not installed. Using legacy 'setup.py install' for opentracing, since package 'wheel' is not installed. Using legacy 'setup.py install' for psycopg2, since package 'wheel' is not installed. Using legacy 'setup.py install' for systemd-python, since package 'wheel' is not installed. Using legacy 'setup.py install' for pympler, since package 'wheel' is not installed. Using legacy 'setup.py install' for threadloop, since package 'wheel' is not installed. Using legacy 'setup.py install' for thrift, since package 'wheel' is not installed. * Allow /etc/default/matrix-synapse to be missing Per the systemd.exec manpage, prefixing an EnvironmentFile with "-": > indicates that if the file does not exist, it will not be read and no > error or warning message is logged. Signed-off-by: Dan Callahan <danc@element.io>
2021-11-07 22:18:33 +01:00
Architecture: any
Update debian Conflicts specifications (#4349) ... to allow installation alongside our matrix-synapse transitional package.
2019-01-04 18:24:13 +01:00
Provides: matrix-synapse
s/Breaks/Conflicts/ in debian/control Otherwise people can't upgrade from matrix-synapse without removing it first
2019-01-11 18:05:45 +01:00
Conflicts:
matrix-synapse (<< 0.34.0.1-0matrix2),
matrix-synapse (>= 0.34.0.1-1),
Debian packaging via dh_virtualenv (#4285)
2018-12-20 12:33:29 +01:00
Pre-Depends: dpkg (>= 1.16.1)
import from package-debian-synapse
2018-12-10 18:14:34 +01:00
Depends:
adduser,
debconf,
Debian packaging via dh_virtualenv (#4285)
2018-12-20 12:33:29 +01:00
${misc:Depends},
Improve `Depends` specs in debian package. (#5675) This is basically a contrived way of adding a `Recommends` on `libpq5`, to fix #5653. The way this is supposed to happen in debhelper is to run `dh_shlibdeps`, which in turn runs `dpkg-shlibdeps`, which spits things out into `debian/<package>.substvars` whence they can later be included by `control`. Previously, we had disabled `dh_shlibdeps`, mostly because `dpkg-shlibdeps` gets confused about PIL's interdependent objects, but that's not really the right thing to do and there is another way to work around that. Since we don't always use postgres, we don't necessarily want a hard Depends on libpq5, so I've actually ended up adding an explicit invocation of `dpkg-shlibdeps` for `psycopg2`. I've also updated the build-depends list for the package, which was missing a couple of entries.
2019-07-17 18:47:07 +02:00
${shlibs:Depends},
debian package: symlink to python-3.X (#4433) In the debian package, make the virtualenv symlink python to /usr/bin/python3.X rather than /usr/bin/python3. Also make sure we depend on the right python3.x package. This might help a bit with subtle failures when people install a package from the wrong distro (https://github.com/matrix-org/synapse/issues/4431).
2019-01-23 12:43:04 +01:00
${synapse:pydepends},
Debian packaging via dh_virtualenv (#4285)
2018-12-20 12:33:29 +01:00
# some of our scripts use perl, but none of them are important,
# so we put perl:Depends in Suggests rather than Depends.
Improve `Depends` specs in debian package. (#5675) This is basically a contrived way of adding a `Recommends` on `libpq5`, to fix #5653. The way this is supposed to happen in debhelper is to run `dh_shlibdeps`, which in turn runs `dpkg-shlibdeps`, which spits things out into `debian/<package>.substvars` whence they can later be included by `control`. Previously, we had disabled `dh_shlibdeps`, mostly because `dpkg-shlibdeps` gets confused about PIL's interdependent objects, but that's not really the right thing to do and there is another way to work around that. Since we don't always use postgres, we don't necessarily want a hard Depends on libpq5, so I've actually ended up adding an explicit invocation of `dpkg-shlibdeps` for `psycopg2`. I've also updated the build-depends list for the package, which was missing a couple of entries.
2019-07-17 18:47:07 +02:00
Recommends:
${shlibs1:Recommends},
import from package-debian-synapse
2018-12-10 18:14:34 +01:00
Suggests:
Debian packaging via dh_virtualenv (#4285)
2018-12-20 12:33:29 +01:00
sqlite3,
${perl:Depends},
import from package-debian-synapse
2018-12-10 18:14:34 +01:00
Description: Open federated Instant Messaging and VoIP server
Matrix is an ambitious new ecosystem for open federated Instant
Messaging and VoIP. Synapse is a reference Matrix server
implementation.
Copy permalink