Yes. I would hate to discover a vulnerability and release an advisory
days after we release slink..
Wichert.
--
==
This combination of bytes forms a message written to you by Wichert Akkerman.
E-Mail: [EMAIL PRO
;t believe how many programs have a check like this and still
work perfectly when they are not root..
Wichert.
--
==
This combination of bytes forms a message written to you by Wichert Akkerman.
E-Mail: [EMA
=
This combination of bytes forms a message written to you by Wichert Akkerman.
E-Mail: [EMAIL PROTECTED]
WWW: http://www.wi.leidenuniv.nl/~wichert/
pgpukegWfbLSs.pgp
Description: PGP signature
Previously peter karlsson wrote:
> Something like a file containing a list of alternative bug reorting
> addresses that these tools can use instead of [EMAIL PROTECTED]
We could put a Bugreports-To: field in the control file I guess. I
suggest you propose this on the debian-policy list.
Wichert.
Previously Christian Hammers wrote:
> > 1. strace can't handle more then 256 subprocesses, a limit you can (and
> > will) reach when building packages.
> really? I'll check it.
Trust me, I'm upstream maintainer for strace so I'm reasonably aware
of its features :)
> > 2. strace'ing an application
Previously Christian Hammers wrote:
> Off-Topic: Why does it has this limitation?
Lack of development time, subtle kernel bugs, etc. strace is not
a trivial application.
> Ok, what about this, I make a dpkg-genbuilddeps and a patch to debuild so
> that it *optionally* runs strace only if the user
Previously Christian Hammers wrote:
> Well, I never received a mail froma an autobuilder saying that one of
> my packages (about 10) were examined and found to have the following
> buildtime dependencies.
Probably because it's a recent change.
> Maybe this should be done so that they can be incl
Previously peter karlsson wrote:
> dpkg-gencontrol: error: source package has two conflicting values - turqstat
> and xturqstat
debian/changelog and debian/control have different for the package name.
> My source package "turqstat" generates two binary packages, "turqstat"
> and "xturqstat". They
Previously Stefano Zacchiroli wrote:
> Sorry but, why with 'ls -al' those files wasn't visible?
Probably because they were uploaded between the time you did ls
and the time you did the rm.
Wichert.
--
_
/ Nothing is fool-p
Previously Colin Watson wrote:
> If this is your only rationale, it is spurious, as you're talking about
> Maintainer: in debian/control while I'm talking about Maintainer: in the
> .changes file. The two are *distinct*.
They are not (any more), with the caveat you can override it using
a -m optio
Previously Christian Hammers wrote:
> > 1. strace can't handle more then 256 subprocesses, a limit you can (and
> > will) reach when building packages.
> really? I'll check it.
Trust me, I'm upstream maintainer for strace so I'm reasonably aware
of its features :)
> > 2. strace'ing an applicatio
Previously Christian Hammers wrote:
> Off-Topic: Why does it has this limitation?
Lack of development time, subtle kernel bugs, etc. strace is not
a trivial application.
> Ok, what about this, I make a dpkg-genbuilddeps and a patch to debuild so
> that it *optionally* runs strace only if the use
Previously Christian Hammers wrote:
> Well, I never received a mail froma an autobuilder saying that one of
> my packages (about 10) were examined and found to have the following
> buildtime dependencies.
Probably because it's a recent change.
> Maybe this should be done so that they can be inc
Previously peter karlsson wrote:
> dpkg-gencontrol: error: source package has two conflicting values - turqstat
> and xturqstat
debian/changelog and debian/control have different for the package name.
> My source package "turqstat" generates two binary packages, "turqstat"
> and "xturqstat". The
Previously Stefano Zacchiroli wrote:
> Sorry but, why with 'ls -al' those files wasn't visible?
Probably because they were uploaded between the time you did ls
and the time you did the rm.
Wichert.
--
_
/ Nothing is fool-
Previously Colin Watson wrote:
> If this is your only rationale, it is spurious, as you're talking about
> Maintainer: in debian/control while I'm talking about Maintainer: in the
> .changes file. The two are *distinct*.
They are not (any more), with the caveat you can override it using
a -m opti
16 matches
Mail list logo
