We still have pbuilder version 0.231 for current Debian OS 12 (Bookworm)
and warning message about not using cgroups is still shown.
It is in shell script file "/usr/lib/pbuilder/pbuilder-checkparams":
1) The check in line 398 "systemctl is-system-running --quiet >/dev/null
2>&1" returns with
Hello Gabriel,
> If I try to complete the second word, then it doesn't work, but that's
> because I don't have the configuration file under /etc and I believe
> that this is unrelated to your problem:
> $ fsmtool2 showconfig
> grep: /etc/fsmd2/fsmd2.conf: No such file or directory
Yes, that's
Hello Gabriel,
I found the cause. It is the wrapper function have() of the obviously newer
function _have() in the shell script
/usr/share/bash-completion/bash_completion
As shown there, have() is still kept for backwards compatibility reasons:
--8<-
Hello Axel,
the OpenVZ/container maintainer went into this and fixed it with the
installation of the libpam-systemd:
apt-get install libpam-systemd
After the question from my side how he came to this conclusion, this is all I
got out of him:
"I think the cause is not easily identified n
Hello Axel,
first, thank you for the quick response, I am not used to it from the Debian
community.
> * Which init system do you use?
To me it looks like a "pseudo-hybrid" of SysV and systemd:
$ ps axfwu
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root 1
Package: screen
Version: 4.5.0-6
Severity: important
Steps to Reproduce on Debian Stretch OS
---
1) invoke: screen
2) start a program e.g. top (or none)
3) detach from screen session by pressing keys CRTL+A+D
4) process listing looks as usual, SCREEN process ha
> "pyversions" is part of package "python2-minimal". Why python2-minimal if I
> build a Python3 project?
"p3versions" is part of package "python3-minimal".
But "/usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm" calls
the external script explicitly (`pyversions`) in line 124.
--
cd /build/ehbackup-api-3.3.2+3+g6939d93~ui10/ && env
PATH="/usr/lib/ccache:/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent"
dpkg-buildpackage -us -uc -d
dpkg-buildpackage: info: source packag
On Sun, 31 May 2020 15:00:46 -0300 "Gabriel F. T. Gomes"
wrote:
> On the other, you are saying that the completions do not work from this
> location, and that's puzzling me. Could you provide more details about
> the problem you are actually getting? Bash-completion is supposed to
> work with fil
Package: bash-completion
Version: 1:2.8-6
Severity: normal
I have a project for which I build Debian installation packages with the help
of pbuilder. The packages are built for Debian OS
* Jessie
* Stretch
* Buster
I have two different bash-completion scripts for two di
Package: openssh-server
Severity: normal
Tags: stretch
Steps to Reproduce:
1) Have a Debian Stretch amd64 in place
2) Have the packages openssh-* of previous release 1:7.4p1-10+deb9u6 installed:
apt install openssh-server=1:7.4p1-10+deb9u6
openssh-sftp-server=1:7.4p1-10+deb9u6 openssh-clie
Hello Niels,
thanks for quick help.
> To be honest, I am surprised that worked in the past. My advice is to
> stop using absolute paths in the debhelper config files[1].
It worked since December 2012! Since then code wasn't changed and it built
For Debian Squeeze, Wheezy, Jessie, Stretch so far
If you create a smylink "ln -s /tmp ." in build directory (same dir level where
"debian/" exists) it works with dh_installman from Buster distribution.
--
Jürgen Kuri
s impeccably with Debian Stretch or Jessie but
not with Buster.
If I copy /usr/bin/dh_installman Perl script from Debian Stretch distribution
to my Buster build environment it works.
--
Jürgen Kuri
14 matches
Mail list logo
