Hi Debian folk and thanks for raising this issue.
By way of background, the logic in debian/GNUmakefile is like this because we
build PCP packages for older debian-based releases where potentially different
debian/control files are needed, based on the availability of dependent
packages (build
Control: reopen 1071103
Control: reopen
Probably should not be marked as Done, until the next PCP upload to Debian.
This was a little messy to implement, as (a) libinih-dev does not have the same
package name on all platforms, and (b) PCP builds for some platforms where there is
no vendor-supplied package to deliver and libinih.so.
However this work is now done and PCP will use the vendor-supplied package i
As of commit
https://github.com/performancecopilot/pcp/commit/1d42dd70a3c28903b7345951cc809cc1006cd012
this issue is fixed upstream in the PCP tree.
As of commit 741ba265c in the PCP tree, this issue is fixed upstream.
Commit
https://github.com/performancecopilot/pcp/commit/f9dfda67acaf7ceac439a5f4870a3314bc3d1f71
resolves this issue in the current PCP source tree.
Validating by installing new PCP 7.0.0 packages in a fresh Debian 12.5 install
(vm23 in the PCP QA Farm).
- /var/run/pcp did not exist before dpk
Commit
https://github.com/performancecopilot/pcp/commit/bf6c6f5ed69eeadfe697958b1c060fd947923058
resolves this issue by moving the PCP pmcheck command out of /usr/bin.
On 17 June 2020 8:45:12 pm Sam Morris wrote:
Package: pcp
Version: 5.1.1-1
Severity: normal
$ systemctl status cron
● cron.service - Regular background program processing daemon
Loaded: loaded (/lib/systemd/system/cron.service; enabled; vendor preset:
enabled)
Active: active (run
On 07-Jan-20 11:18 AM, Nathan Scott wrote:
...
Ken and Andreas, this would mean we set Debian8 (and the equivalent
Ubuntu release) as the minimum required for Makepkgs builds. Would
that be a problem for anyone? It turns out that was the first Debian that
used systemd as the init system, so th
We have incorporated changes based on Daniel's proposed patch into PCP.
As of commit e7406b4 in the github PCP tree on 28 Oct 2017, we're making
arch independent packages for dpkg builds.
$ dpkg-query -W -f '${Package} ${Architecture}\n' pcp\* | grep all
pcp-doc all
pcp-import-ganglia2pcp all
Dariusz,
There is an extensive PCP QA infrastructure included in the PCP source
distribution (it is below the top-level qa directory).
Rather than writing more unit tests in Python, I would recommend using a subset
of the existing QA tests ...
kenj@bozo:~/src/pcp/qa$ cloc .
4233 text files
I expect these commits will be in PCP 3.11.10 which is scheduled for release on
17 May 2017.
Changes committed to git://git.pcp.io/kenj/pcp master
Ken McDonell (4):
debian man page migrations
src/libpcp/doc/README: typo fix
debian/control.*: redo Breaks/Replaces clauses after
Thanks, Andreas.
The html link and your mail both suggest the same approach. But when I do
this and build new 3.11.10 packages and try to upgrade a system with 3.11.9
installed using the same recipe I've been using for decades, namely
# dpkg -i *.deb
in the directory where all the new pac
Package: coreutils
Version: 8.25-2
Severity: normal
Dear Maintainer,
This is related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810295
that has (thankfully) been fixed by reverting the coreutils quoting change.
This is fixed ...
kenj@vm07:/tmp$ touch foo 'foo bar'
kenj@vm07:/tmp$ ls fo
16 matches
Mail list logo
