glib2 cast failure (Bug #356)


Added by Tommy Boatman about 2 years ago. Updated about 1 year ago.


Status:Closed Start date:02/10/2012
Priority:High Due date:
Assignee:- % Done:

100%

Category:Gnome
Target version:-
Grimoire:Test

Description

glib2 2.30.2 (test grimoire)
xz-utils is installed
This is likely a sorcery issue (1.15.1), but does not occur with other xz packages.

Collating dependencies...
Spells are to be cast:
---------------------------
glib2

Do you want to cast these spells? [y]

Found source file /var/spool/sorcery/glib-2.30.2.tar.xz for spell glib2 in /var/
spool/sorcery
Waiting for any Solo casts to complete...
Waiting for any other casts of glib2 to complete... done.
Staging enabled
castfs: checking sanity of <mnt-dir> and <stage-dir>
castfs: stagedir is okay!
Preparing glib2
GPG checking source file glib-2.30.2.tar.xz...
Algorithm used: sha512
Allowing new hash sha512
Checking spell level WORKS_FOR_ME
Spell level is a new allowed level
gpg signature verified!
Unpacking source file glib-2.30.2.tar.xz for spell glib2.
Building glib2
Building in dir: /usr/src/glib-2.30.2
glib2 2.30.2

/var/lib/sorcery/modules/build_api/api2: line 334: ./configure: No such file or
directory
! Problem Detected !
Creating compile log /var/log/sorcery/compile/glib2-2.30.2.bz2
Creating castfs debug log /var/log/sorcery/compile/glib2-2.30.2.castfs.dbglog.bz
2

Spells that encountered problems:
---------------------------------
glib2 (build)

root@smgl64:~# ls /var/spool/sorcery/glib*
/var/spool/sorcery/glib-2.30.2.tar.xz
/var/spool/sorcery/glibc-2.13.tar.bz2
/var/spool/sorcery/glibc-2.13.tar.bz2.sig
root@smgl64:~# sorcery version
1.15.1
root@smgl64:~# scribe index

Codex Listing
-------------

[0] : z-rejected : /var/lib/sorcery/codex/z-rejected : 4328d68407ac9918
[1] : test : /var/lib/sorcery/codex/test : 0.62-test

Appears to be a failure to extract the files - /usr/src/glib-2.30.2 is empty after this cast.


Related issues

related to Sorcery - Bug #347: sorcery 1.15.1 fails to unpack xz-compressed tarballs Closed 02/03/2012

History

Updated by Vlad Glagolev about 2 years ago

The only quick&good option I see here is switching back to sha512, until we figure out how to handle this properly

Updated by Vlad Glagolev almost 2 years ago

Andra┼ż has found that's a problem about outdated file spell, which returns 'XZ' instead of 'xz' filetype and vice versa.

The recent version of file seems to be fine.

  • % Done changed from 0 to 100
  • Status changed from New to Resolved

Updated by Vlad Glagolev about 1 year ago

Closing the bug.

  • Status changed from Resolved to Closed

Also available in: Atom PDF