On Fri, Apr 1, 2011 at 1:38 PM, kachelaqa <[email protected]> wrote: > hello > > i have used swig to create some python bindings for libalpm. > > with pacman-3.4 it was possible to use alpm_pkg_changelog_open with packages > from both the local and sync databases. > > with pacman-3.5, however, packages from sync databases now produce a > segfault (local packages still work fine). > > here is a sample of some code which is currently segfaulting for me: > > int test_changelog(pmpkg_t *pkg) { > void *fp = NULL; > > if (pkg != NULL) { > if ((fp = alpm_pkg_changelog_open(pkg)) != NULL) { > alpm_pkg_changelog_close(pkg, fp); > return 1; > } > } > return 0; > } > > am i doing something wrong, or should i post a bug report?
It is definitely a bug in the sense that it segfaults- we provide no changelog_* functions in the sync (or default) pkg_operations callback. Where have you actually seen changelogs in sync databases? -Dan
