public inbox for gentoo-user-de@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sascha Moeller <sascha@skutcher.de>
To: gentoo-user-de@lists.gentoo.org
Subject: Re: [gentoo-user-de] Problem mit Coreutils und mktemp
Date: Fri, 02 May 2008 14:14:56 +0200	[thread overview]
Message-ID: <481B05C0.2070507@skutcher.de> (raw)
In-Reply-To: <481B03FB.7080409@skutcher.de>

Sascha Moeller schrieb:
> Dirk Heinrichs schrieb:
>> Am Freitag, 2. Mai 2008 schrieb ext Sascha Moeller:
>>  
>>> Justin schrieb:
>>>    
>>>> Sascha Moeller schrieb:
>>>>      
>>>>> Juergen Rose schrieb:
>>>>>        
>>>>>> On Fr, 2008-05-02 at 13:16 +0200, Sascha Moeller wrote:
>>>>>>          
>>>>>>> Hallo Leute,
>>>>>>> wollte mir auf meinem amd64 system grad ne chroot für 32bit
>>>>>>> basteln. Leider gibt es da nen großes Problem beim allerersten
>>>>>>> update des Systems:
>>>>>>> tigerente / # emerge -av coreutils
>>>>>>>
>>>>>>> These are the packages that would be merged, in order:
>>>>>>>
>>>>>>> Calculating dependencies... done!
>>>>>>> [ebuild     U ] sys-apps/coreutils-6.10-r2 [6.4] USE="acl nls
>>>>>>> (-selinux) -static -vanilla% -xattr%" 0 kB
>>>>>>> [blocks B     ] sys-apps/mktemp (is blocking
>>>>>>> sys-apps/coreutils-6.10-r2)
>>>>>>> [blocks B     ] >=sys-apps/coreutils-6.10 (is blocking
>>>>>>> sys-apps/mktemp-1.5)
>>>>>>>
>>>>>>> Wenn ich vorher mktemp deinstallieren fliegt mir coreutils, wie ich
>>>>>>> es mir schon gedacht hatte, um die Ohren.
>>>>>>> Wie kann ich das sinnvoll beheben?
>>>>>>>
>>>>>>> MFG Sascha
>>>>>>>             
>>>>>> Nach dem Loeschen von mktemp (emerge -C mktemp), konnte ich 
>>>>>> coreutils
>>>>>> problemlos installieren.
>>>>>>
>>>>>> MfG Juergen
>>>>>>           
>>>>> Ich leider nicht :( habs nun genauso gemacht wie Justin es im Falle B
>>>>> gesagt hatte. Und jo Justin komme mit dem Englischen klar :)
>>>>>
>>>>> * checking coreutils-6.10.tar.lzma ;-)
>>>>> ...                               [ ok ]
>>>>> * checking coreutils-6.10-patches-1.3.tar.lzma ;-)
>>>>> ...                   [ ok ]
>>>>>
>>>>>        
>>>>>>>> Unpacking source...
>>>>>>>> Unpacking coreutils-6.10.tar.lzma to
>>>>>>>>               
>>>>> /var/tmp/portage/sys-apps/coreutils-6.10-r2/work
>>>>> unpack coreutils-6.10.tar.lzma: file format not recognized. Ignoring.
>>>>>
>>>>>        
>>>>>>>> Unpacking coreutils-6.10-patches-1.3.tar.lzma to
>>>>>>>>               
>>>>> /var/tmp/portage/sys-apps/coreutils-6.10-r2/work
>>>>> unpack coreutils-6.10-patches-1.3.tar.lzma: file format not
>>>>> recognized. Ignoring.
>>>>> /usr/portage/sys-apps/coreutils/coreutils-6.10-r2.ebuild: line 50:
>>>>> cd: /var/tmp/portage/sys-apps/coreutils-6.10-r2/work/coreutils-6.10:
>>>>> No such file or directory
>>>>>
>>>>> * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
>>>>> *
>>>>> *   /var/tmp/portage/sys-apps/coreutils-6.10-r2/work/patch
>>>>> *   ( patch )
>>>>>
>>>>>
>>>>> !!! ERROR: sys-apps/coreutils-6.10-r2 failed.
>>>>> Call stack:
>>>>>  ebuild.sh, line 1614:   Called dyn_unpack
>>>>>  ebuild.sh, line 751:   Called qa_call 'src_unpack'
>>>>>  environment, line 3791:   Called src_unpack
>>>>>  coreutils-6.10-r2.ebuild, line 53:   Called epatch
>>>>>  eutils.eclass, line 181:   Called die
>>>>>
>>>>> !!! Cannot find $EPATCH_SOURCE!
>>>>>         
>>>> Hast du app-arch/lzma-utils installiert?
>>>>       
>>> Jo klar das is installiert, dass dachte ich auch zuerst weil er mit den
>>> Dateien anscheinend nicht recht was anfangen kann und hatte deshalb nun
>>> mktemp vermutet
>>> tigerente / # emerge -av lzma-utils
>>>
>>> These are the packages that would be merged, in order:
>>>
>>> Calculating dependencies... done!
>>> [ebuild   R   ] app-arch/lzma-utils-4.32.5  0 kB
>>>     
>>
>> Sieh' mal nach, ob Deine portage-Version damit schon umgehen kann:
>>
>> $ cd /usr/lib/portage && grep -R lzma *
>>
>> Sollte Treffer in bin/webrsync und bin/ebuild.sh liefern. Wenn nicht: 
>> portage aktualisieren.
>>
>> Bye...
>>
>>     Dirk
>>   
>
> Cool danke, glaub das war das Problem :) da kam gar keine Ausgabe. Ich 
> update grad mal von 2.1.2.2 auf 2.1.4.4, wobei mich dann wundert, 
> wieso das selbe Problem auch im 2008.0 beta2 stage3 noch vorhanden ist.
>
> MFG Sascha
Ok coreutils ging nu durch. Das Problem mit mktemp bleibt aber leider. 
Brauch ich mktemp nicht mehr?
tigerente portage # emerge -av mktemp

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] sys-apps/mktemp-1.5  0 kB
[blocks B     ] sys-apps/mktemp (is blocking sys-apps/coreutils-6.10-r2)
[blocks B     ] >=sys-apps/coreutils-6.10 (is blocking sys-apps/mktemp-1.5)
-- 
gentoo-user-de@lists.gentoo.org mailing list



  reply	other threads:[~2008-05-02 12:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 19:19 [gentoo-user-de] pcmcia und Kernel 2.6.24 Erik Geiger
2008-05-01  6:07 ` Matthias
2008-05-02 11:16 ` [gentoo-user-de] Problem mit Coreutils und mktemp Sascha Moeller
2008-05-02 11:20   ` Justin
2008-05-02 11:21     ` Justin
2008-05-02 11:29     ` Dirk Heinrichs
2008-05-02 11:21   ` Juergen Rose
2008-05-02 11:31     ` Sascha Moeller
2008-05-02 11:39       ` Justin
2008-05-02 11:42         ` Sascha Moeller
2008-05-02 12:01           ` Dirk Heinrichs
2008-05-02 12:07             ` Sascha Moeller
2008-05-02 12:14               ` Sascha Moeller [this message]
2008-05-02 12:20                 ` Sascha Moeller
2008-05-02 12:24                 ` Dirk Heinrichs
2008-05-02 11:44       ` Dirk Heinrichs
2008-05-02 11:41   ` Dirk Heinrichs
2008-05-02 11:53     ` Sascha Moeller

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=481B05C0.2070507@skutcher.de \
    --to=sascha@skutcher.de \
    --cc=gentoo-user-de@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