The heartbeat-2 package we use is based on version 2.1.3-7,
dating back to 2008 in Debian.
In Debian wheezy the heartbeat package has version 1:3.0.5-3,
and in jessie it's currently sitting at 1:3.0.5+hg12629-1.
We should investigate whether the heartbeat package from
Debian/jessie might work for us, so accept it as an alternative
to our heartbeat-2 package dependency-wise. We then can try
building a ngcp system based on Debian/jessie and if the
heartbeat 3.* package doesn't work for us we can still use our
own package (and optionally also revert this commit).
If the ngcp-services-pro package depends on
linux-headers-3.2.0-4-all it pulls in the
linux-headers-3.2.0-4-common-rt and
linux-headers-3.2.0-4-rt-amd64 packages, which then are
considered as valid target kernels for mediaprox/virtualbox
installation on our PRO systems. Avoid this by depending on the
according linux-headers-3.2.0-4-amd64 package instead.
This fixes the failing daily builds, where ngcp-config-{ce,pro}
depends on ngcp-db-schema >= 3.0.0, but ngcp-db-schema is provided
only as 3.0.0~1368026494... currently.
This is a tricky problem related to apt-pinning,
let's see whether we can get apt-get's resolver
to choose percona package on Debian/squeeze and
mysql packages on Debian/wheezy.
From: Michael Prokop <mprokop@sipwise.com>
Since our current Jenkins trigger default to builds against
squeeze currently we get packages that are meant for Debian/wheezy
also built against squeeze and therefore ending up in Debian/squeeze.
To address that until we made the full switch over to Debian/wheezy
as default build target we need to support squeeze + wheezy at
the same time.
Addressing:
| The following packages have unmet dependencies:
| mysql-client-5.1 : Depends: libmysqlclient16 (>= 5.1.66-0+squeeze1) but 5.1.57-rel12.8-233.squeeze is to be installed
from http://paste.mgm.sipwise.com/show/333/
From: Michael Prokop <mprokop@sipwise.com>
We're hardcoding the backports version already, let's
try to keep the current trunk deployable for squeeze + wheezy
at the same time.
Might not be the best approach for the long run, but it should
get us started towards a working sip:provider PRO installation
on Debian/wheezy.
From: Michael Prokop <mprokop@sipwise.com>
Let's try mysql from Debian/wheezy as replacement for
the percona packages, there are no percona packages
available for Debian/wheezy yet anyway.
Do *NOT* merge this into any maintenance branch!
From: Michael Prokop <mprokop@sipwise.com>
Update linux-image-3.2.0-0.bpo.3-amd64 -> linux-image-3.2.0-0.bpo.4-amd64
and linux-headers-3.2.0-0.bpo.3-amd64 -> linux-headers-3.2.0-0.bpo.4-amd64
to fix http://paste.mgm.sipwise.com/show/280/
From: Michael Prokop <mprokop@sipwise.com>
We want to ship 3.2 kernel as part of the upcoming release.
Add linux-headers-3.2.0-0.bpo.3-amd64 + linux-image-3.2.0-0.bpo.3-amd64
as dependencies therefore.
Acked-by: Jon Bonilla
Closes: https://bugtracker.sipwise.com/view.php?id=2233
From: Michael Prokop <mprokop@sipwise.com>
As noted by Andreas in release-trunk installations we get
ngcp-ossbss-common-ce installed by default on PRO installations,
being the result of weak dependencies. Let's try to solve that.
From: Michael Prokop <mprokop@sipwise.com>
This makes reviews and diffs easier and helps in avoiding duplicate entries.
devscripts's wrap-and-sort ftw.
Closes: https://bugtracker.sipwise.com/view.php?id=1845
From: Michael Prokop <mprokop@sipwise.com>
ngcp-ossbss-clients-perl is slim and small and we want to
have it on all our >=2.6 systems available ootb.
This implements the last missing part to finally close
https://bugtracker.sipwise.com/view.php?id=1835
Acked-by: Daniel Tiefnig
From: Michael Prokop <mprokop@sipwise.com>
templates-pro-config and templates-ce-config are
no longer provided as packages.
change update packages to be ngcp-config
dependencies and not ngcp-ngcp ones
As discussed today we shouldn't use a specific Maintainer in
debian/control field but instead just use a team entry since
there might be multiple persons involved per package and
iff we want to track this kind of information outside of
svn [log|blame|,...] we shouldn't make that visible to the
outside per se
From: Michael Prokop <mprokop@sipwise.com>
In today's dev meeting we noticed that telnet is missing on our
pro installation which is annoying. We already have a depency on
telnet in current trunk but it's not in the 2.3 repository yet,
that's why it was missing in today's pro installation. While at
it replace dependency on telnet with telnet-ssl since Daniel
suggested that.
From: Michael Prokop <mprokop@sipwise.com>
While at it do some lintian cleanups (like providing
debian/source/format and line-wrapping long description)
and raise copyright year information from 2010 to 2011.
From: Michael Prokop <mprokop@sipwise.com>
Alexander Lutay
Victor Seva
Michael Prokop
Jon Bonilla
Andrew Pogrebennyk
Andreas Granig
Victor Seva
Richard Fuchs