On Mon, Feb 16, 2009 at 11:01 AM, ERSEK Laszlo wrote:
> One such thing would be the set of paths I'd to put under an "install:"
> rule. This has clearly no place in Makefile.dev which is my personal
> playground, or Makefile.portable, which is what it is called. (The
> default Makefile, using gcc
Hi Siegfried
> > How can there possibly be this difference between these two tools?
>
> I don't know what could trigger something like this, but it may be
> worth checking that you have the same build dependencies (and version
> of them) installed as pbuilder gets.
I cannot see any difference betwe
On Sun, 2009-02-15 at 20:50 +, Jonathan Wiltshire wrote:
> So take it out of place. A dpatch is two things: the patch file, and its
> entry in debian/patches/00list. Take its entry out, and
> dpatch-edit-patch won't try to apply it.
>
> rm it, and remove its entry in 00list.
Ok, dpatch-edit-
I am a bit swamped and won't be able to see to the many things that
need to be done with mdadm for squeeze:
- synchronise the big Ubuntu patch; Dustin Kirkland from Canonical
has expressed interest to cooperate and could help.
- consider how to support non-dynamic (non-udev) creation of arrays
Paul Wise wrote:
>> It seems awkward to me to generate debugging symbols and then strip
>> them. Is there a reason to include debugging symbols per default? It can
>> eat up a lot of disk space (and thus buffer cache) for huge projects.
>> Also, -O0 is gcc's default, AFAIK.
>>
>> Can you please ex
> Dear mentors,
>
> I am looking for a sponsor for the new version 1.0.0-1
> of my package "clamfs".
>
> It builds these binary packages:
> clamfs - An user-space anti-virus protected file system
>
> The package appears to be lintian clean.
>
> The package can be found on mentors.debian.net
Gudjon I. Gudjonsson wrote:
> Hi
> I do have a problem with the debian packaging tools but I don't know how
> to debug it.
>When I build one of my packages using
> dpkg-buildpackage or ./debian/rules binary
> the library files are installed into
> debian/tmp/usr/lib/tcltk/spice
>But if
Dear mentors,
I am looking for a sponsor for my package "rsplib". RSPLIB is the Open Source
implementation (GPLv3) of the IETF's standard for Reliable Server Pooling
(RSerPool). RSerPool is a framework for server pool management and access. It
is an IETF standard, which has been developed by th
Hi Felipe
On Monday 16 February 2009 13:29:56 Felipe Sateler wrote:
> > I do have a problem with the debian packaging tools but I don't know
> > how to debug it.
> >When I build one of my packages using
> > dpkg-buildpackage or ./debian/rules binary
> > the library files are installed into
Paul Wise wrote:
> The reason is "that's the way we do it in Debian". The policy manual
> probably has a rationale.
[...]
> Hmm, which Debian architectures do you test on?
>
> Perhaps /dev/urandom could be a good source of data.
[...]
> Yeah, always run lintian in sid and build/test your pack
On Mon, 16 Feb 2009, Felipe Sateler wrote:
> Paul Wise wrote:
> > The reason is "that's the way we do it in Debian". The policy manual
> > probably has a rationale.
>
> There is no reason to generate debugging symbols and then strip
> them.
If you plan on being able to debug the binaries that you
2009/2/16 Sandro Tosi :
>
> you'd be welcome to so do :) You can find some documentation at [1]
> [2] [3], and feel free to ask d-pyt...@l.d.o for clarification or, if
> you hang around irc, we're on #debian-python at irc.debian.org.
>
> [1] http://wiki.debian.org/Teams/PythonAppsPackagingTeam
> [2
Don Armstrong wrote:
> If you plan on being able to debug the binaries that you've released,
> you almost certainly need the debbugging symbols that match the
> binaries that you've released.
>
> In Debian we currently aren't collecting all of the debugging symbols,
> so doing the above is diffic
On Monday 16 February 2009 17:11:20 ERSEK Laszlo wrote:
> Don Armstrong wrote:
> > If you plan on being able to debug the binaries that you've released,
> > you almost certainly need the debbugging symbols that match the
> > binaries that you've released.
> >
> > In Debian we currently aren't colle
On Tue, 17 Feb 2009, ERSEK Laszlo wrote:
> Don Armstrong wrote:
> > If you plan on being able to debug the binaries that you've released,
> > you almost certainly need the debbugging symbols that match the
> > binaries that you've released.
> >
> > In Debian we currently aren't collecting all of t
15 matches
Mail list logo
