Eugene Teo <[EMAIL PROTECTED]> schrieb:
>
>> > 3. I have a couple of files in debian/ called procps-doc.{docs,files}.
>> >
>> > It gives this error message when i try to do dpkg-buildpackage.
>> >
>> > cp: cannot stat `#DOCS#': No s
Eugene Teo <[EMAIL PROTECTED]> schrieb:
>
>> > 3. I have a couple of files in debian/ called procps-doc.{docs,files}.
>> >
>> > It gives this error message when i try to do dpkg-buildpackage.
>> >
>> > cp: cannot stat `#DOCS#': No s
n it, and keep the list updated.
> > 2. What should I do so that I can copy those man pages in the
> > program's source directory to the respective directory?
> >
> > [~/procps/procps-2.0.18] $ \ls *.1 *.5 *.8
> > free.1 pkill.1 skill.1snice.1 sysctl.conf.
n it, and keep the list updated.
> > 2. What should I do so that I can copy those man pages in the
> > program's source directory to the respective directory?
> >
> > [~/procps/procps-2.0.18] $ \ls *.1 *.5 *.8
> > free.1 pkill.1 skill.1snice.1 sysctl.conf.
Eugene Teo <[EMAIL PROTECTED]> schrieb:
> Hi everyone,
>
> I am trying to create a .deb package for a procps branch[1] by Robert
> Love (different from the official procps deb). In the program's
> source directory, it has a shared library, many binaries, and many
>
Eugene Teo <[EMAIL PROTECTED]> schrieb:
> Hi everyone,
>
> I am trying to create a .deb package for a procps branch[1] by Robert
> Love (different from the official procps deb). In the program's
> source directory, it has a shared library, many binaries, and many
>
Hi everyone,
I am trying to create a .deb package for a procps branch[1] by Robert
Love (different from the official procps deb). In the program's
source directory, it has a shared library, many binaries, and many
man pages for those binaries.
I read, and followed the instructions giv
Hi everyone,
I am trying to create a .deb package for a procps branch[1] by Robert
Love (different from the official procps deb). In the program's
source directory, it has a shared library, many binaries, and many
man pages for those binaries.
I read, and followed the instructions giv
Bob Hilliard <[EMAIL PROTECTED]> writes:
> I have built a sid chroot by installing debootstrap and
> build-essential. The procps package is installed, but the proc
> directory in the chroot is empty. This makes it difficult to install
> and start/stop the daemon.
>
>
On Wednesday 06 November 2002 00:34, Bob Hilliard wrote:
> I have built a sid chroot by installing debootstrap and
> build-essential. The procps package is installed, but the proc
> directory in the chroot is empty. This makes it difficult to install
> and start/sto
I have built a sid chroot by installing debootstrap and
build-essential. The procps package is installed, but the proc
directory in the chroot is empty. This makes it difficult to install
and start/stop the daemon.
Can anyone advise how I can make proc file system work in the
chroot
Bob Hilliard <[EMAIL PROTECTED]> writes:
> I have built a sid chroot by installing debootstrap and
> build-essential. The procps package is installed, but the proc
> directory in the chroot is empty. This makes it difficult to install
> and start/stop the daemon.
>
>
On Wednesday 06 November 2002 00:34, Bob Hilliard wrote:
> I have built a sid chroot by installing debootstrap and
> build-essential. The procps package is installed, but the proc
> directory in the chroot is empty. This makes it difficult to install
> and start/sto
I have built a sid chroot by installing debootstrap and
build-essential. The procps package is installed, but the proc
directory in the chroot is empty. This makes it difficult to install
and start/stop the daemon.
Can anyone advise how I can make proc file system work in the
chroot
14 matches
Mail list logo
