Continue scanning when an invalid DB entry is found
Fix for FS#7133 - when DB scanning finds an invalid named entry, scanning is currently aborted. Instead we will simply skip it and find the next valid package. Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
This commit is contained in:
parent
9abe99f236
commit
9d9ac66bb2
1 changed files with 3 additions and 1 deletions
|
@ -183,7 +183,9 @@ pmpkg_t *_alpm_db_scan(pmdb_t *db, const char *target)
|
||||||
}
|
}
|
||||||
if(_alpm_pkg_splitname(ent->d_name, pkg->name, pkg->version, 0) == -1) {
|
if(_alpm_pkg_splitname(ent->d_name, pkg->name, pkg->version, 0) == -1) {
|
||||||
_alpm_log(PM_LOG_ERROR, _("invalid name for database entry '%s'"), ent->d_name);
|
_alpm_log(PM_LOG_ERROR, _("invalid name for database entry '%s'"), ent->d_name);
|
||||||
return(NULL);
|
alpm_pkg_free(pkg);
|
||||||
|
pkg = NULL;
|
||||||
|
continue;
|
||||||
}
|
}
|
||||||
|
|
||||||
/* explicitly read with only 'BASE' data, accessors will handle the rest */
|
/* explicitly read with only 'BASE' data, accessors will handle the rest */
|
||||||
|
|
Loading…
Add table
Reference in a new issue