On Sat, Jun 23, 2007 at 09:17:24PM +0100, Raphael Hertzog wrote:
It creates a set of modules in /usr/lib/dpkg/Dpkg/ as I need some shared
code between dpkg-gensymbols and dpkg-shlibdeps.
There's no documentation update yet, but I shall work on that once the
code is integrated. I'll maintain
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.5
tags 383394 pending
Bug#383394: dpkg-source should warn on 0-sized files when creating a source
package
There were no tags set.
Tags added: pending
End of message, stopping
On Sun, Jul 01, 2007 at 12:45:56PM +0200, Frank Lichtenheld wrote:
1) Apply the part of the patch that adds the modules. Since that doesn't
add anything useful to dpkg in its own right, we should probably make
this in a branch
2) Do some code clean-up
3) Add a minimal test suite (no
On Sun, 01 Jul 2007, Frank Lichtenheld wrote:
On Sun, Jul 01, 2007 at 12:45:56PM +0200, Frank Lichtenheld wrote:
1) Apply the part of the patch that adds the modules. Since that doesn't
add anything useful to dpkg in its own right, we should probably make
this in a branch
2) Do some
On Sat, Jun 30, 2007 at 09:40:29AM +0200, Andreas Metzler wrote:
I think that is just wrong. sbuild should not need to know anything
about dpkg-buildpackage's internals and there is no need for change
here. The currently used and proven interface is:
1. install Build-Depends for running
On Sun, 01 Jul 2007, Frank Lichtenheld wrote:
I would give Raphael commit rights to the repository with the
understanding that he limits himself to the branch integrating his work
for now (I really see no need for technical measures enforcing that, we
are all grown-ups, right?)
Sure, I have
Bill Allombert wrote:
On Sat, Jun 30, 2007 at 09:40:29AM +0200, Andreas Metzler wrote:
I think that is just wrong. sbuild should not need to know anything
about dpkg-buildpackage's internals and there is no need for change
here. The currently used and proven interface is:
1. install
7 matches
Mail list logo
