> On Jun 7, 2016, at 4:35 AM, Elan Ruusamäe <g...@delfi.ee> wrote: > > On 07.06.2016 06:33, Jeffrey Johnson wrote: >> I’m not sure how repackaged rpm’s are involved: that isn’t entirely clear >> from the report. > again, it was included in report that files were installed from repackage > pool: >
Its still not clear to me whether the new package files were installed or not. Yes the original configuration files were renamed to *.rpmsave. > > # ls -l */*pam* > -rw-r--r-- 1 root root 326K 6. juuni 20:17 1465233457/pam-1.1.8-8.x86_64.rpm > -rw-r--r-- 1 root root 35K 6. juuni 20:17 > 1465233457/pam-libs-1.1.8-8.x86_64.rpm > > root@glen spool/repackage# > root@glen spool/repackage# rpm -Uhv */*pam* —d OK, so repackaged *.rpm were used. The repackaged rpm’s are “best effort”: if the files are renamed before the repackaging occurs, then those packages do not contain the config files because the files were not present (on the original path) when the repackaging occurred. Do the repackaged rpm’s contain those files.? When/how were the repackaged packages created? 73 de Jeff > owngrade > > > -- > glen > > _______________________________________________ > pld-devel-en mailing list > pld-devel-en@lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
