tags 609932 + fixed-upstream pending
thanks
On Sun, Jan 16, 2011 at 02:48:35PM +, Roger Leigh wrote:
> > Also, = 0 seems to be the default, in sbuild.conf, which is also
> > misleading.
>
> Quite a number of the sbuild.conf defaults need re-synching with the
> current defaults. Ideally, I'd
On Fri, Jan 14, 2011 at 01:54:46AM +0100, Cyril Brulebois wrote:
> Roger Leigh (14/01/2011):
> > The latter should also be coupled with an upgrade to ensure that the
> > baseline state is up-to-date prior to any installations and
> > removals. This is why the default is also to do an upgrade.
>
Roger Leigh (14/01/2011):
> The latter should also be coupled with an upgrade to ensure that the
> baseline state is up-to-date prior to any installations and
> removals. This is why the default is also to do an upgrade.
So by default I get a chroot which gets upgraded behind my back? Great!
>
On Thu, Jan 13, 2011 at 11:29:39PM +0100, Cyril Brulebois wrote:
> Package: sbuild
> Version: 0.60.8-1
> Severity: important
>
> sbuild now runs apt-get update while building, why?
The reason for updating prior to a build is to ensure that:
• Needed packages are actually available on the mirror,
Package: sbuild
Version: 0.60.8-1
Severity: important
sbuild now runs apt-get update while building, why?
| $ sbuild -As -d unstable xbitmaps_1.1.1-1.dsc
| sbuild (Debian sbuild) 0.60.8 (12 Dec 2010) on talisker
|
|
╔══
5 matches
Mail list logo
