On Wed, 16 Jan 2013, Christian PERRIER wrote:
> Quoting Jakub Wilk (jw...@debian.org):
> > I would paint the bikeshed the following color:
> > 0.8.51+dfsg1-0.1
>
> Isn't that missing the fact that this is a t-p-u upload, which is
> indeed the start of a "wheezy" branch?
>
> So something we were n
On 01/16/2013 08:56, Neil Williams wrote:
On Wed, 16 Jan 2013 00:26:53 +0100
Jakub Wilk wrote:
Not only dpkg, but also wanna-build, sbuild, lintian, dak, and who knows
what else...
It's about which ones need to change. lintian response rates are not
likely to be a problem - once this gets app
Hi,
On Fri, Jan 11, 2013 at 08:06:43PM +0100, Jonas Smedegaard wrote:
> > On Fri, Jan 11, 2013 at 08:39:41PM +0900, Charles Plessy wrote:
> > > > Not any more (hopefully) since I droped the `find -name` approach
> > > > which turned out as insufficient (even if very attractive in the
> > > > fir
Le Wed, Jan 16, 2013 at 10:45:04AM +0100, Andreas Tille a écrit :
>
> OK. So Fields-Excluded is currently not part of DEP5 anyway and so I
> revert my former answer that it fits the Files format because it may
> contain [] wildcards (and I do not see any problem because of this). I
> agree with
* Nobuhiro Iwamatsu , 2013-01-16, 09:51:
* URL : http://code.google.com/p/lz4/
* License : BSD 2-Clause License
Programming Lang: C
Description : Extremely Fast Compression algorithm library
LZ4 is a very fast lossless compression algorithm.
This uses Dictionary compres
2013/1/15 Andreas Beckmann :
> On 2013-01-15 10:29, Julien Cristau wrote:
>> There's no requirement for md5sums files in the first place AFAIK. How
>> are incomplete md5sums worse than no md5sums? If anything this stuff
>> should be minor IMO.
>
> If a package is shipping no .md5sum at all, it wi
Quoting Andreas Tille (2013-01-16 10:45:04)
> Hi,
>
> On Fri, Jan 11, 2013 at 08:06:43PM +0100, Jonas Smedegaard wrote:
> > > On Fri, Jan 11, 2013 at 08:39:41PM +0900, Charles Plessy wrote:
> > > > > Not any more (hopefully) since I droped the `find -name`
> > > > > approach which turned out as i
On Wed, 16 Jan 2013 10:23:37 +0100
Ansgar Burchardt wrote:
> On 01/16/2013 08:56, Neil Williams wrote:
> > On Wed, 16 Jan 2013 00:26:53 +0100
> > Jakub Wilk wrote:
> >> Not only dpkg, but also wanna-build, sbuild, lintian, dak, and who knows
> >> what else...
> >
> > It's about which ones need t
Package: wnpp
Severity: wishlist
Owner: Gerfried Fuchs
* Package name: nafe
Version : 0.1-1
Upstream Author : Eric Price
* URL : http://nafe.sourceforge.net/
* License : GPLv2
Programming Lang: C
Description : toolset for editing psf format consolefont
On Wed, Jan 16, 2013 at 12:35:27PM +0100, Jonas Smedegaard wrote:
> > OK. So Fields-Excluded is currently not part of DEP5 anyway and so I
> > revert my former answer that it fits the Files format because it may
> > contain [] wildcards (and I do not see any problem because of this).
> > I agr
Quoting Andreas Tille (2013-01-16 14:19:55)
> On Wed, Jan 16, 2013 at 12:35:27PM +0100, Jonas Smedegaard wrote:
> > > OK. So Fields-Excluded is currently not part of DEP5 anyway and so I
> > > revert my former answer that it fits the Files format because it may
> > > contain [] wildcards (and I
Johannes Schauer writes ("Bootstrappable Debian - proposal of needed changes"):
> the following is an email written by Wookey and myself.
Firstly, I want to say thank you! This seems like excellent work to
me.
> 5. Cross-Builds field
> =
>
> For even further automation and a
Am 16.01.2013 13:05, schrieb Neil Williams:
> The main archive only needs to "carry" this extra information without
> needing to act upon it. If dak needs patches to allow-and-ignore the new
> information, that can be done. Most bootstrapping changes are to turn off
> features by not build-dependi
On Wed, Jan 16, 2013 at 02:43:54PM +0100, Jonas Smedegaard wrote:
>
> Sorry if I am dense...
I like you because I know you are dense. ;-)
> You agree that Files and Files-Excluded should ideally use same format,
> but you find it more important that Files-Excluded be flexible - even
> if File
Am 15.01.2013 19:18, schrieb Johannes Schauer:
> This mechanism also covers cross-compiler bootstraping. The eglibc, gcc,
> and kernel packages already have the neceassary staged-build info, but
> the build profiles (1.) part is also needed to specifiy the reduced
> build-deps. The cross-toolchain
Am 16.01.2013 14:50, schrieb Ian Jackson:
> * We initially define one scope "profile", for build profiles.
>
>A build profile is an optional variation that can be applied
>to a particular package, for the purpose of reducing the
>build dependencies and/or avoiding the building of unne
On Wed, 16 Jan 2013 13:50:17 +
Ian Jackson wrote:
> > For even further automation and also for quality assurance, we propose
> > another new field for source packages which indicates whether or not
> > this source package is supposed to be cross compilable.
>
> Is it possible that packages m
Quoting Andreas Tille (2013-01-16 15:11:22)
> On Wed, Jan 16, 2013 at 02:43:54PM +0100, Jonas Smedegaard wrote:
> >
> > Sorry if I am dense...
>
> I like you because I know you are dense. ;-)
>
> > You agree that Files and Files-Excluded should ideally use same
> > format, but you find it more
Hi,
On Wed, Jan 16, 2013 at 01:50:17PM +, Ian Jackson wrote:
> > 5. Cross-Builds field
> > =
> >
> > For even further automation and also for quality assurance, we propose
> > another new field for source packages which indicates whether or not
> > this source package is s
Hi,
On Wed, Jan 16, 2013 at 04:00:15PM +0100, Matthias Klose wrote:
> this only takes care about packages with a reduced package set built,
> or packages with reduced functionality. There are same cases missing:
>
> - extra build dependencies for cross builds, like for gcc-4.7:
>{gobjc++,gcc
+++ Matthias Klose [2013-01-16 15:37 +0100]:
> Am 15.01.2013 19:18, schrieb Johannes Schauer:
> > This mechanism also covers cross-compiler bootstraping. The eglibc, gcc,
> > and kernel packages already have the neceassary staged-build info, but
> > the build profiles (1.) part is also needed to sp
On Tue, Jan 15, 2013 at 07:18:40PM +0100, Johannes Schauer wrote:
> Besides bootstrapping, these build profiles could also be used for
> embedded builds, and to allow for changed buil-deps when cross-building.
On a related point, see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695287
I'v
On Wed, Jan 16, 2013 at 12:26:53AM +0100, Jakub Wilk wrote:
> 2) Support for the :any qualifiers in Build-Depends was added to apt
> in February 2010, and to dpkg in March 2012; AFAIK it's still not
> supported by wanna-build.
I'm working on the buildd/wanna-build side of things at the moment (lat
On Wed, Jan 16, 2013 at 11:52:42AM +0800, Paul Wise wrote:
> That sounds useful, so yes. arm64 is on the way, it would be a nice
> test case but I guess wookey/Sledge are onto that. The SH-5 CPU
> architecture apparently exists but has no port. There are also the
> architectures with open-source CP
On Wed, Jan 16, 2013 at 03:40:52PM +, Neil Williams wrote:
> On Wed, 16 Jan 2013 13:50:17 +
> Ian Jackson wrote:
> > Is it possible that packages might only cross build for certain
> > targets ? Or only for certain hosts ?
In my reply I'm going to use autoconf terminology, so host =>
arc
On Wed, 16 Jan 2013 17:55:00 +
Colin Watson wrote:
> On Wed, Jan 16, 2013 at 03:40:52PM +, Neil Williams wrote:
> > On Wed, 16 Jan 2013 13:50:17 +
> > Ian Jackson wrote:
> In my reply I'm going to use autoconf terminology, so host =>
> architecture built for, and target => only relev
On Wed, Jan 16, 2013 at 05:41:31PM +, Colin Watson wrote:
> > If Debian wants to incorporate the ability to being bootstrappable
> > in its policy, then there *must* be some packages which are cross
> > compiled for a minimal build system. Adding this header to those
> > source packages would m
Quoting Raphael Hertzog (hert...@debian.org):
> On Wed, 16 Jan 2013, Christian PERRIER wrote:
> > Quoting Jakub Wilk (jw...@debian.org):
> > > I would paint the bikeshed the following color:
> > > 0.8.51+dfsg1-0.1
> >
> > Isn't that missing the fact that this is a t-p-u upload, which is
> > indeed
Am 16.01.2013 17:26, schrieb Johannes Schauer:
> Hi,
>
> On Wed, Jan 16, 2013 at 04:00:15PM +0100, Matthias Klose wrote:
>> this only takes care about packages with a reduced package set built,
>> or packages with reduced functionality. There are same cases missing:
>>
>> - extra build dependenci
Am 16.01.2013 17:30, schrieb Wookey:
> +++ Matthias Klose [2013-01-16 15:37 +0100]:
>> Am 15.01.2013 19:18, schrieb Johannes Schauer:
>>> This mechanism also covers cross-compiler bootstraping. The eglibc, gcc,
>>> and kernel packages already have the neceassary staged-build info, but
>>> the build
On Wed, Jan 16, 2013 at 06:47:01PM +, Neil Williams wrote:
> A different - similarly strict - criterion would catch out glib2, gtk
> and others- introspection / marshalling code. This can cause a build
> failure but can also cause more difficult bugs which only show at
> runtime. Skipping the e
I installed Wheezy beta 4 from CD and was surprised that compiz window
manager was removed. Compiz is the best thing about Linux, that's a
shame. I tracked down some explanations, don't want to start a flame
war about that decision.
But, even though Debian is not including compiz, I still love it
Hi!
Why don't you just use the Sid version?
=> http://packages.debian.org/sid/compiz
2013/1/16 Paul Johnson :
> [...]
> The Wheezy repo that was testing during the
> Squeeze time is a different thing from the Wheezy that is Wheezy
> release beta 4? Right?
No. Testing *is* Wheezy at time ;-)
> In
There are some issues when you do have an architecture dependent header file
which needs to be in the multiarch specific include directory. If the header
file is directly located in /usr/include, then moving it to
/usr/include/ usually is not a problem (except for quoting
issues as found in the pa
Hi,
On Wed, Jan 16, 2013 at 7:02 PM, Jakub Wilk wrote:
> * Nobuhiro Iwamatsu , 2013-01-16, 09:51:
>
>> * URL : http://code.google.com/p/lz4/
>> * License : BSD 2-Clause License
>> Programming Lang: C
>> Description : Extremely Fast Compression algorithm library
>>
>> LZ4
On Wed, 16 Jan 2013 19:16:26 +0100, Christian PERRIER
wrote:
> Quoting Raphael Hertzog (hert...@debian.org):
> > On Wed, 16 Jan 2013, Christian PERRIER wrote:
> > > Quoting Jakub Wilk (jw...@debian.org):
> > > > I would paint the bikeshed the following color:
> > > > 0.8.51+dfsg1-0.1
> > >
> > >
Le Wed, Jan 16, 2013 at 10:44:53AM +0800, Paul Wise a écrit :
> The version difference is probably due to symbols stuff, read
> deb-symbols(5), dpkg-shlibdeps(1), dpkg-gensymbols(1) and this wiki
> page:
>
> http://wiki.debian.org/Projects/ImprovedDpkgShlibdeps
Hi all,
note that since version 3.
On Wed, Jan 16, 2013 at 11:32:45PM +0100, Matthias Klose wrote:
> There are some issues when you do have an architecture dependent header file
> which needs to be in the multiarch specific include directory. If the header
> file is directly located in /usr/include, then moving it to
> /usr/include
Matthias Klose writes:
> There are some issues when you do have an architecture dependent header
> file which needs to be in the multiarch specific include directory. If
> the header file is directly located in /usr/include, then moving it to
> /usr/include/ usually is not a problem (except for
On Thu, Jan 17, 2013 at 6:59 AM, Charles Plessy wrote:
> Le Wed, Jan 16, 2013 at 10:44:53AM +0800, Paul Wise a écrit :
>> The version difference is probably due to symbols stuff, read
>> deb-symbols(5), dpkg-shlibdeps(1), dpkg-gensymbols(1) and this wiki
>> page:
>>
>> http://wiki.debian.org/Projec
Would it be possible to use something similar to the bits/ dir in
eglibc? Or would your proposal replace that?
/usr/include/python2.7/bits -> /usr/include/x86_64-linux-gnu/python2.7/bits
And in /usr/include/python2.7/*
#include
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIB
Le Wed, Jan 16, 2013 at 05:26:52PM +0100, Johannes Schauer a écrit :
>
> Whether or not "nocheck" and "nodocs" can/should become build profiles
> is of course still to be debated.
Hi all,
for the packages I maintain, I am now replacing the regression tests that
were ran during the build process
+++ Matthias Klose [2013-01-16 21:09 +0100]:
> Am 16.01.2013 17:26, schrieb Johannes Schauer:
> > On Wed, Jan 16, 2013 at 04:00:15PM +0100, Matthias Klose wrote:
> >>
> >> So it does make sense to build with two profiles like stage1 & check.
Yes. I can think of situations where being able to speci
+++ Ian Jackson [2013-01-16 13:50 +]:
> Johannes Schauer writes ("Bootstrappable Debian - proposal of needed
> changes"):
> > 6. Conclusion
> > =
> ...
>
> > - do the proposals for the needed fields sound convincing? Can they be
> >improved? Do they have fundamental flaws?
>
Package: wnpp
Severity: wishlist
Owner: Adam Stokes
* Package name: sos
Version : 2.3.1
Upstream Author : Adam Stokes
* URL : https://github.com/sosreport/sosreport
* License : GPL2+
Programming Lang: Python
Description : This set of tools is designed
Hi Johannes,
On Tue, Jan 15, 2013 at 07:18:40PM +0100, Johannes Schauer wrote:
[...]
> 2. Build-Profiles (extension 1)
> ===
>
> When a source package is built with fewer build dependencies (cross,
> embedded, stage1, nodocs...), then it often happens that it does not
46 matches
Mail list logo
