Bug 18154

Summary: mkdir /var/cache/urpmi: Permission denied in urpm::create_var_lib_rpm()
Product: Mageia Reporter: Michel AUTEM <michel.autem>
Component: RPM PackagesAssignee: Thierry Vignaud <thierry.vignaud>
Status: RESOLVED INVALID QA Contact:
Severity: minor    
Priority: Normal    
Version: 5   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: urpmi CVE:
Status comment:

Description Michel AUTEM 2016-04-07 13:01:47 CEST
The "mgaapplet" program crashed. Drakbug-16.104 caught it.

Rien, j'ai simplement rebooté la machine aprés une purge du répertoire /var/cache.

mkdir /var/cache/urpmi: Permission non accordée at /usr/lib/perl5/vendor_perl/5.20.1/urpm.pm line 305.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/perl5/5.20.1/Carp.pm:166
Carp::croak() called from /usr/lib/perl5/5.20.1/File/Path.pm:156
File::Path::_mkpath() called from /usr/lib/perl5/5.20.1/File/Path.pm:133
File::Path::_mkpath() called from /usr/lib/perl5/5.20.1/File/Path.pm:114
File::Path::mkpath() called from /usr/lib/perl5/vendor_perl/5.20.1/urpm.pm:305
urpm::create_var_lib_rpm() called from /usr/lib/perl5/vendor_perl/5.20.1/urpm.pm:293
urpm::set_files() called from /usr/lib/perl5/vendor_perl/5.20.1/urpm.pm:151
urpm::new() called from /usr/lib/perl5/vendor_perl/5.20.1/Rpmdrake/open_db.pm:80
Rpmdrake::open_db::fast_open_urpmi_db() called from /usr/bin/mgaapplet:61

Theme name: Adwaita
Kernel version = 4.1.15-desktop-2.mga5
Distribution=Mageia release 5 (Official) for x86_64
CPU=AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
Comment 1 Rémi Verschelde 2016-04-07 13:08:21 CEST
@Thierry: Is it supported to recreate the urpmi cache from scratch after /var/cache has been wiped out, or did this user unintentionally break his setup?

Assignee: bugsquad => thierry.vignaud
Summary: mgaapplet crashed => mkdir /var/cache/urpmi: Permission denied in urpm::create_var_lib_rpm()
Source RPM: mgaonline-3.15-1.mga5 => urpmi

Comment 2 Thierry Vignaud 2016-04-07 14:00:58 CEST
mgaapplet works as user, it cannot create anything here.
If you take a random package, and randomly kill files/directories, the odds're high the package will break...

just recreate the directory as root, and next time, only nuke the subcontent...

Status: NEW => RESOLVED
Resolution: (none) => INVALID