Steve Langasek:
> Do you ever intend to release this software as a tarball for use outside
> of Debian?
Yes, the tarball that I create for Debian is also distributed from my
homepage (together with Debian packages compiled for potato, for those that
do not use unstable), along with a RAR package
Peter,
On Fri, 20 Jul 2001, peter karlsson wrote:
> > Since this is the Debian changelog rather than an upstream changelog, the
> > majority of changes noted are specific to the shared debian directory, of
> > which there is precisely one for any set of binary packages that are built
> > from a s
Steve Langasek:
> Do you ever intend to release this software as a tarball for use outside
> of Debian?
Yes, the tarball that I create for Debian is also distributed from my
homepage (together with Debian packages compiled for potato, for those that
do not use unstable), along with a RAR package
Peter,
On Fri, 20 Jul 2001, peter karlsson wrote:
> > Since this is the Debian changelog rather than an upstream changelog, the
> > majority of changes noted are specific to the shared debian directory, of
> > which there is precisely one for any set of binary packages that are built
> > from a
On Fri, Jul 20, 2001 at 11:24:31AM -0400, Richard A Nelson wrote:
> > > install: install-stamp
> > > install-stamp: build-stamp
> > > install stuff
> > > chown someuser stuff
> > >
> > > binary-arch: install-stamp
> > > build package
> > >
> > BTW install-stamp is evil
Nicolas SABOURET wrote:
> I may be wrong, but as far as I understood, dh_fixperms is responsible
> for changing the owner of the files :
>
> $man dh_fixperms
> [...]It makes all files be owned by
>root, and it removes group and other write permission from
>
On Fri, Jul 20, 2001 at 10:21:37AM +0200, Robert Bihlmeyer wrote:
> It should be noted that this requirement is broken when your rules
> have something like:
>
> install: install-stamp
> install-stamp: build-stamp
> install stuff
> chown someuser stuff
>
> binary-arch: insta
On Fri, Jul 20, 2001 at 11:24:31AM -0400, Richard A Nelson wrote:
> > > install: install-stamp
> > > install-stamp: build-stamp
> > > install stuff
> > > chown someuser stuff
> > >
> > > binary-arch: install-stamp
> > > build package
> > >
> > BTW install-stamp is evi
Hi,
Is there any way I can find out who all are within my web of trust, given
a particular max-cert-depth ?
Thanks in Advance,
viral
--
Every year is getting shorter, never seem to find the time.
Plans that either come to naught or half a page of scribbled lines.
pgp2dK0eZN2di.pgp
Descripti
Nicolas SABOURET wrote:
> I may be wrong, but as far as I understood, dh_fixperms is responsible
> for changing the owner of the files :
>
> $man dh_fixperms
> [...]It makes all files be owned by
>root, and it removes group and other write permission from
>
On Fri, Jul 20, 2001 at 10:21:37AM +0200, Robert Bihlmeyer wrote:
> It should be noted that this requirement is broken when your rules
> have something like:
>
> install: install-stamp
> install-stamp: build-stamp
> install stuff
> chown someuser stuff
>
> binary-arch: inst
Hi,
Is there any way I can find out who all are within my web of trust, given
a particular max-cert-depth ?
Thanks in Advance,
viral
--
Every year is getting shorter, never seem to find the time.
Plans that either come to naught or half a page of scribbled lines.
PGP signature
Adam C Powell IV <[EMAIL PROTECTED]> writes:
> So, I think I want:
>
> Build-Depends: atlas-dev [!powerpc !m68k !sparc !hppa], lapack-dev
> [powerpc m68k sparc hppa]
>
>
> But I don't see the proper syntax for doing this properly. Is that
> correct as is above?
Yes.
> The potato packaging man
[EMAIL PROTECTED] writes:
> > >because it forces everything to look like it's owned by root. Use
> > >sudo.
> >
> > That's not true:
>
> You're right, as long as you haven't exited fakeroot and started it up
> again in the meantime; I didn't realize that.
It should be noted that this require
Adam C Powell IV <[EMAIL PROTECTED]> writes:
> So, I think I want:
>
> Build-Depends: atlas-dev [!powerpc !m68k !sparc !hppa], lapack-dev
> [powerpc m68k sparc hppa]
>
>
> But I don't see the proper syntax for doing this properly. Is that
> correct as is above?
Yes.
> The potato packaging ma
[EMAIL PROTECTED] writes:
> > >because it forces everything to look like it's owned by root. Use
> > >sudo.
> >
> > That's not true:
>
> You're right, as long as you haven't exited fakeroot and started it up
> again in the meantime; I didn't realize that.
It should be noted that this requir
Steve Langasek:
> Since this is the Debian changelog rather than an upstream changelog, the
> majority of changes noted are specific to the shared debian directory, of
> which there is precisely one for any set of binary packages that are built
> from a single source package.
Well, first of all,
I may be wrong, but as far as I understood, dh_fixperms is responsible
for changing the owner of the files :
$man dh_fixperms
[...]It makes all files be owned by
root, and it removes group and other write permission from
all files. [...]
Nicolas.
S
18 matches
Mail list logo
