Problem with abrt update on F18?

Jakub Filak jfilak at redhat.com
Wed Jul 10 15:49:16 UTC 2013


On Tue, 2013-07-02 at 16:19 -0500, Richard Shaw wrote:
> I saw this during the update:
> 
> 
> Updating   : abrt-libs-2.1.5-1.fc18.x86_64
>    10/76
> cp: cannot create regular file
> â/var/tmp/abrt/ccpp-2013-03-27-09:24:26-2877/environâ: No such file or
> directory
> cp: cannot create regular file
> â/var/tmp/abrt/ccpp-2013-03-27-09:24:26-2877/mapsâ: No such file or
> directory
> cp: cannot create regular file
> â/var/tmp/abrt/ccpp-2013-03-27-09:24:26-2877/countâ: No such file or
> directory
> cp: cannot create regular file
> â/var/tmp/abrt/ccpp-2013-03-27-09:24:26-2877/hostnameâ: No such file
> or directory
> cp: cannot create regular file
> â/var/tmp/abrt/ccpp-2013-03-27-09:24:26-2877/core_backtraceâ: No such
> file or directory
> 
> 
> Is it anything to worry about?
> 
> 
> Richard

Since abrt-2.1.0 detected problems data are stored in /var/tmp/abrt.

We wanted to keep already detected problems visible in abrt-gui. Thus
during upgrading from abrt < 2.1.0 %post scriptlet makes a copy of
already detected problems from the old location (/var/spool/abrt) in the
new location (/var/tmp/abrt). 

So, the error messages are strange but nothing critical has happened.
The old data has not been lost, because abrt makes only a copy and
doesn't delete anything.

Do you have any idea why the following command failed?

cp --recursive -- "/var/spool/abrt/ccpp-2013-03-27-09:24:26-2877"
"/var/tmp/abrt/ccpp-2013-03-27-09:24:26-2877"


Regards,
Jakub



More information about the devel mailing list