Hi Paul,
Quoting Paul Elliott (2016-08-05 21:28:25)
> OK this time I deleted the recommended files as before, but I noted there
> were no other chroots in use. So I purged both sbuild and schroot with
> apt-get and reinstalled.
note that purging sbuild and schroot will not remove the chroots.
On Fri, Aug 05, 2016 at 10:07:23PM +0200, Jakub Wilk wrote:
> * Wookey , 2016-08-05, 20:56:
> >I think there is a way to stop it putting i the <>
> >substitutions, but I can't find that now.
>
> In /etc/sbuild/sbuild.conf set:
> $log_filter = 0;
>
> (It's beyond me why this
* Jakub Wilk , 2016-08-05, 22:07:
* Wookey , 2016-08-05, 20:56:
I think there is a way to stop it putting i the <>
substitutions, but I can't find that now.
In /etc/sbuild/sbuild.conf set:
$log_filter = 0;
You can also use this tool to (hopefully)
* Wookey , 2016-08-05, 20:56:
I think there is a way to stop it putting i the <>
substitutions, but I can't find that now.
In /etc/sbuild/sbuild.conf set:
$log_filter = 0;
(It's beyond me why this is enabled by default.)
--
Jakub Wilk
On 2016-08-05 14:28 -0500, Paul Elliott wrote:
> dpkg-deb: building package 'sbuild-build-depends-core-dummy' in
> '/<>/
> resolver-aIr7Ri/apt_archive/sbuild-build-depends-core-dummy.deb'.
> dpkg-deb: error: failed to make temporary file (control member): No such file
> or directory
> Is there
OK this time I deleted the recommended files as before, but I noted there
were no other chroots in use. So I purged both sbuild and schroot with
apt-get and reinstalled.
I then recreated th chroot using steps 1-6 of "Create the chroot" from the
wiki page.
I get the same error!
Setup apt archive
Hi,
Quoting Andrey Rahmatullin (2016-08-05 09:49:11)
> On Fri, Aug 05, 2016 at 02:42:27AM -0500, Paul Elliott wrote:
> > Before I was getting a different error complaining
> > that debfoster does not exist under "testing". BTW why does debfoster fail
> > to exist under testing?
> Because it was
On Fri, Aug 05, 2016 at 02:42:27AM -0500, Paul Elliott wrote:
> Before I was getting a different error complaining
> that debfoster does not exist under "testing". BTW why does debfoster fail
> to exist under testing?
Because it was removed from testing and the new version hasn't entered
testing
Ok, I deleted my old sbuild chroot for debian testing.
I then created two sbuild chroot according to the wiki instructions.
For testing, and for unstable.
I have then tried to build 2 different packages, on the different chroots.
I always get the following error:
Setup apt archive
Hello,
On Wed, Aug 03, 2016 at 10:21:46AM +0200, Jonas Meurer wrote:
> Please note that this will delete *all* chroots and their configuration.
> I woud prefer something like:
That's what he said he wanted to do :)
--
Sean Whitton
signature.asc
Description: PGP signature
On 2016-08-03 13:12 +0200, Johannes Schauer wrote:
> Hi,
>
> Quoting Paul Wise (2016-08-03 12:41:28)
> > > As far as I know, schroot still doesn't
> > > document how to delete a chroot.
> >
> > Seems to me like sbuild should have an sbuild-deletechroot command
> > that should call the relevant
Hi,
Quoting Paul Wise (2016-08-03 12:41:28)
> On Wed, Aug 3, 2016 at 1:06 PM, Johannes Schauer wrote:
>
> > The main issue here is, that it is not clear *where* the bug should be
> > filed.
> > Sbuild supports multiple backends. The probably most used one is the schroot
> > backend because that
On Wed, Aug 3, 2016 at 1:06 PM, Johannes Schauer wrote:
> The main issue here is, that it is not clear *where* the bug should be filed.
> Sbuild supports multiple backends. The probably most used one is the schroot
> backend because that is used by sbuild-createchroot and the default of the
>
Am 03.08.2016 um 06:20 schrieb Sean Whitton:
> On Tue, Aug 02, 2016 at 11:06:31PM -0500, Paul Elliott wrote:
>> Sometimes a user gets a sbuild chroot so screwed up that it does not
>> work anymore, and the user has no idea how to fix it, because he does not
>> know what he did wrong.
>>
>> He
Hi Paul,
Quoting Sean Whitton (2016-08-03 06:20:26)
> On Tue, Aug 02, 2016 at 11:06:31PM -0500, Paul Elliott wrote:
> > Sometimes a user gets a sbuild chroot so screwed up that it does not
> > work anymore, and the user has no idea how to fix it, because he does not
> > know what he did wrong.
>
On Tue, Aug 02, 2016 at 11:06:31PM -0500, Paul Elliott wrote:
> Sometimes a user gets a sbuild chroot so screwed up that it does not
> work anymore, and the user has no idea how to fix it, because he does not
> know what he did wrong.
>
> He wants to start over from scratch.
>
> The problem is,
16 matches
Mail list logo