> Before forcing the maintainers to make themselfes the work to figure
> these dependencies out we should tell them that such a list already
> exists! (And don't tell me that they should have known it from
> various discussions under strange topics in some lists!)
The central source dependency li
> Before forcing the maintainers to make themselfes the work to figure
> these dependencies out we should tell them that such a list already
> exists! (And don't tell me that they should have known it from
> various discussions under strange topics in some lists!)
The central source dependency l
On Mon, Jul 31, 2000 at 04:49:44PM +0200, Christian Hammers wrote:
>
> Before forcing the maintainers to make themselfes the work to figure these
> dependencies out we should tell them that such a list already exists!
> (And don't tell me that they should have known it from various discussions
> u
On Mon, Jul 31, 2000 at 04:49:44PM +0200, Christian Hammers wrote:
>
> Before forcing the maintainers to make themselfes the work to figure these
> dependencies out we should tell them that such a list already exists!
> (And don't tell me that they should have known it from various discussions
>
Hello
On Mon, 31.07.00 11:22 +0200, Christian T. Steigies wrote:
> See here for some of the source-dependencies the autobuilders use:
> http://buildd.debian.org/andrea/m68k/source-dependencies-unstable.gz
...
> I did not follow the discussion completely, but I think its rather
> pointless, since
Hello
On Mon, 31.07.00 11:22 +0200, Christian T. Steigies wrote:
> See here for some of the source-dependencies the autobuilders use:
> http://buildd.debian.org/andrea/m68k/source-dependencies-unstable.gz
...
> I did not follow the discussion completely, but I think its rather
> pointless, since
Christian Hammers wrote:
> (It's just that I bet that we never get build-depends if maintainers are
> forced to guess them theirselves w/o automatic help)
One source package in 4 has build depends now.
[EMAIL PROTECTED]:/org/ftp.debian.org/ftp/dists/unstable>find . |egrep
'(.diff|.tar.gz)' | grep
Wichert Akkerman wrote:
> Slight bugs in programs used in the build process; I've seen it happen.
> I also have a report of a program hanging if you strace it. Funnily
> enough that was noticed when somebody straced a package build. Could
> be an strace bug, program bug or kernel bug, but definitel
Christian Hammers wrote:
> (It's just that I bet that we never get build-depends if maintainers are
> forced to guess them theirselves w/o automatic help)
One source package in 4 has build depends now.
joeyh@auric:/org/ftp.debian.org/ftp/dists/unstable>find . |egrep
'(.diff|.tar.gz)' | grep -v '
Wichert Akkerman wrote:
> Slight bugs in programs used in the build process; I've seen it happen.
> I also have a report of a program hanging if you strace it. Funnily
> enough that was noticed when somebody straced a package build. Could
> be an strace bug, program bug or kernel bug, but definite
On Sun, Jul 30, 2000 at 10:42:41PM +0200, Wichert Akkerman wrote:
> 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 becau
On Sun, Jul 30, 2000 at 10:42:41PM +0200, Wichert Akkerman wrote:
> 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 beca
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
> > (It's just that I bet that we never get build-depends if maintainers are
> > forced to guess them theirselves w/o automatic help)
> We get build-depends since some of the autobuilders build packages in
> minimal chroots and detect problems automatically.
Well, I never received a mail froma an
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
On Sun, Jul 30, 2000 at 11:35:09AM +0200, Christian Hammers wrote:
> > Previously Christian Hammers wrote:
> > > Attached you find a patch against dpkg-buildpackage which creates a
> > > debian/strace.debhelper file when running "debian/rules build".
There was a suggestion to write a wrapper libra
> > (It's just that I bet that we never get build-depends if maintainers are
> > forced to guess them theirselves w/o automatic help)
> We get build-depends since some of the autobuilders build packages in
> minimal chroots and detect problems automatically.
Well, I never received a mail froma a
On Sun, Jul 30, 2000 at 11:35:09AM +0200, Christian Hammers wrote:
> > Previously Christian Hammers wrote:
> > > Attached you find a patch against dpkg-buildpackage which creates a
> > > debian/strace.debhelper file when running "debian/rules build".
There was a suggestion to write a wrapper libr
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
Hello
> Trust me, I'm upstream maintainer for strace so I'm reasonably aware
> of its features :)
Off-Topic: Why does it has this limitation?
> > And remember that this is only a "suggestive" tool like dpkg-shlibdeps,
> > if your package is so strange that it really does not work you can omit it
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
Hello
[forwarded to debian-mentors as the main discussion was there]
On Sat, 29.07.00 19:20 +0200, Wichert Akkerman wrote:
> Previously Christian Hammers wrote:
> > Attached you find a patch against dpkg-buildpackage which creates a
> > debian/strace.debhelper file when running "debian/rules buil
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
Hello
> Trust me, I'm upstream maintainer for strace so I'm reasonably aware
> of its features :)
Off-Topic: Why does it has this limitation?
> > And remember that this is only a "suggestive" tool like dpkg-shlibdeps,
> > if your package is so strange that it really does not work you can omit it
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
Hello
[forwarded to debian-mentors as the main discussion was there]
On Sat, 29.07.00 19:20 +0200, Wichert Akkerman wrote:
> Previously Christian Hammers wrote:
> > Attached you find a patch against dpkg-buildpackage which creates a
> > debian/strace.debhelper file when running "debian/rules bui
26 matches
Mail list logo
