From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] broken catalyst-3.0_rc1 & catalyst-git
Date: Wed, 23 Mar 2016 09:19:05 -0700 [thread overview]
Message-ID: <20160323091905.5dfc6766.dolsen@gentoo.org> (raw)
In-Reply-To: <20160323161059.GK6588@vapier.lan>
[-- Attachment #1: Type: text/plain, Size: 2597 bytes --]
On Wed, 23 Mar 2016 12:10:59 -0400
Mike Frysinger <vapier@gentoo.org> wrote:
> On 23 Mar 2016 15:41, armin76@gentoo.org wrote:
> > 23 Mar 2016 15:41:19 CET: NOTICE : purge(); clearing autoresume ...
> > 23 Mar 2016 15:41:19 CET: NOTICE : Removing AutoResume Points ...
> > 23 Mar 2016 15:41:19 CET: NOTICE : purge(); clearing chroot ...
> > 23 Mar 2016 15:41:19 CET: NOTICE : Clearing the chroot path ...
> > 23 Mar 2016 15:41:19 CET: NOTICE : purge(); clearing package
> > cache ... 23 Mar 2016 15:41:19 CET: NOTICE : purging the
> > pkgcache ... 23 Mar 2016 15:41:19 CET: NOTICE : purge(); clearing
> > kerncache ... 23 Mar 2016 15:41:19 CET: NOTICE : purging the
> > kerncache ... 23 Mar 2016 15:41:19 CET: NOTICE : --- Running
> > action sequence: unpack 23 Mar 2016 15:41:19 CET: ERROR :
> > Exception running action sequence unpack Traceback (most recent
> > call last): File
> > "/usr/lib/python2.7/site-packages/catalyst/base/stagebase.py", line
> > 1413, in run getattr(self, x)() File
> > "/usr/lib/python2.7/site-packages/catalyst/base/stagebase.py", line
> > 734, in unpack unpack_info['source'] =
> > file_check(unpack_info['source']) File
> > "/usr/lib/python2.7/site-packages/catalyst/support.py", line 76, in
> > file_check for ext in extensions: TypeError: 'NoneType' object is
> > not iterable 23 Mar 2016 15:41:19 CET: NOTICE : Cleaning up...
> > Running unbind()
>
> this is the 2nd or 3rd time i've hard catalyst-3.0_rc1 fail for me.
> i just upgraded this to git to try and workaround it, but that failed
> now too:
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site-packages/catalyst/base/stagebase.py",
> line 1418, in run getattr(self, x)()
> File "/usr/lib/python2.7/site-packages/catalyst/base/stagebase.py",
> line 786, in unpack if not self.decompressor.extract(unpack_info):
> File "/usr/lib/python2.7/site-packages/DeComp/compress.py", line
> 168, in _extract return self._run(infodict)
> File "/usr/lib/python2.7/site-packages/DeComp/compress.py", line
> 196, in _run success = func(infodict)
> File "/usr/lib/python2.7/site-packages/DeComp/compress.py", line
> 298, in _common opts = ' '.join(cmdargs) %(cmdinfo)
> KeyError: 'comp_prog'
>
> can we get a newer/fixed version snapshotted out there ?
> -mike
Yeah, I screwed up and deleted that parameter instead of the log
parameter after my testing.
I need to do some additional bsd changes, but looks like I need to edit
the patches Yuta sent. So, it might be a day or two for those.
--
Brian Dolbec <dolsen>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 951 bytes --]
prev parent reply other threads:[~2016-03-23 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1aijyJ-00034h-MV@monolith.freenet-rz.de>
2016-03-23 16:10 ` [gentoo-catalyst] broken catalyst-3.0_rc1 & catalyst-git Mike Frysinger
2016-03-23 16:19 ` Brian Dolbec [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160323091905.5dfc6766.dolsen@gentoo.org \
--to=dolsen@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox