> On Aug 30, 2016, at 12:34 PM, Elan Ruusamäe <[email protected]> wrote: > > just reminder, that old bug never got resolved. >
I am reminded. Fix the following flaws in your bug report (sic). 0) You refuse to report through recommended rpm5.org bug reporting, either at http://launchpad.net/rpm, or discussing on <[email protected]>. > and i'm certain it happens if you upgrade packages %config %verify with > multiple package names > i.e in the command below there were multiple matches for poldek, poldek-libs > packages > > > 19:31:40 root[load: 0.05]@jenkins-vm /vagrant# rpm -Fhv *.rpm 1) Add -vv so I have some prayer of being able to follow the logic path. 2) Don’t use -F —freshen; instead use -U —update. 3) Don’t use *.rpm because I have no idea what operation is being performed. > warning: poldek-0.32.1-2.i686.rpm: Header V4 DSA signature: NOKEY, key ID > c0708994 4) Remove extraneous warning messages. In addition to having no idea to what operation is being performed, there is no indication of what is installed, other than that you have _NOT_ imported some pubkey. You also have not reported the version of rpm in use, nor what patches are applied. > warning: package poldek = 0:0.30.1-10 was already added, replacing with > poldek >= 0.32.1-2 > warning: package poldek = 0.32.1-2 was already added, replacing with poldek > >= 0:0.32.1-3 > warning: package poldek-libs = 0:0.30.1-10 was already added, replacing with > poldek-libs >= 0.32.1-2 > warning: package poldek-libs = 0.32.1-2 was already added, replacing with > poldek-libs >= 0:0.32.1-3 5) Stop throwing multip[le instances of identical packages at rpm and expecting the right thing to happen. > Preparing... ########################################### [100%] > 1:poldek-libs ########################################### [ 50%] > warning: /etc/poldek/repos.d/pld.conf saved as > /etc/poldek/repos.d/pld.conf.rpmsave > warning: /etc/poldek/poldek.conf saved as /etc/poldek/poldek.conf.rpmsave > 2:poldek warning: /etc/poldek/poldek.conf created as > /etc/poldek/poldek.conf.rpmnew > ########################################### [100%] 6) These warnings are explicit confirmation that %config is saving your files, contrary to your claims. > cp: cannot stat ‘/etc/poldek/poldek.conf’: No such file or directory > /bin/sed: can't read /etc/poldek/poldek.conf: No such file or directory > cp: cannot stat ‘/etc/poldek/repos.d/pld.conf’: No such file or directory > /bin/sed: can't read /etc/poldek/repos.d/pld.conf: No such file or directory > /bin/sed: can't read /etc/poldek/repos.d/pld.conf: No such file or directory 7) In addition to _NOT_ reporting a) the packages that are being installed b) the debugging output with -vv c) the packages installed add to your list d) what scripts are being run in what packages > 19:31:47 root[load: 0.12]@jenkins-vm /vagrant# poldek --up -u icedtea7-jre > error: /etc/poldek/poldek.conf: No such file or directory > error: /etc/poldek/poldek.conf: No such file or directory 8) Instead of cut-n-pasting some random command, try a simple statement like polled is broken afterwards. Your bug report will be shorter and more succinct. > 19:31:54 root[load: 0.11]@jenkins-vm /vagrant# cd /etc/poldek/ > 19:31:59 root[load: 0.10]@jenkins-vm /etc/poldek# l > total 36K > drwxr-xr-x 2 root root 19 aug 30 19:31 post-install.d/ > drwxr-xr-x 2 root root 19 aug 30 19:31 pre-install.d/ > drwxr-xr-x 2 root root 4,0K aug 30 19:31 repos.d/ > -rw-r--r-- 1 root root 568 mai 3 10:21 cli.conf > -rw-r--r-- 1 root root 1,9K mai 3 10:34 fetch.conf > -rw-r--r-- 1 root root 6,2K mai 3 10:34 poldek.conf.rpmnew > -rw-r--r-- 1 root root 6,1K aug 27 2013 poldek.conf.rpmsave > -rw-r--r-- 1 root root 2,5K mai 3 10:34 source.conf > -rw-rw---- 1 root root 1,3K juuli 20 2010 witch.conf > 19:31:59 root[load: 0.10]@jenkins-vm /etc/poldek# mv poldek.conf.rpmsave > poldek.conf > 19:32:06 root[load: 0.09]@jenkins-vm /etc/poldek# > 7) Describe in words, not examples, what you are trying to show. > > 19:33:37 root[load: 0.02]@jenkins-vm /vagrant# l *.rpm > -rw-r--r-- 1 vagrant vagrant 336K nov 13 2015 poldek-0.30.1-10.i686.rpm > -rw-r--r-- 1 vagrant vagrant 339K apr 26 16:04 poldek-0.32.1-2.i686.rpm > -rw-r--r-- 1 vagrant vagrant 339K mai 3 10:34 poldek-0.32.1-3.i686.rpm > -rw-r--r-- 1 vagrant vagrant 1,4M nov 13 2015 > poldek-debuginfo-0.30.1-10.i686.rpm > -rw-r--r-- 1 vagrant vagrant 1,4M apr 26 16:04 > poldek-debuginfo-0.32.1-2.i686.rpm > -rw-r--r-- 1 vagrant vagrant 1,4M mai 3 10:34 > poldek-debuginfo-0.32.1-3.i686.rpm > -rw-r--r-- 1 vagrant vagrant 41K nov 13 2015 > poldek-devel-0.30.1-10.i686.rpm > -rw-r--r-- 1 vagrant vagrant 42K apr 26 16:04 > poldek-devel-0.32.1-2.i686.rpm > -rw-r--r-- 1 vagrant vagrant 41K mai 3 10:34 > poldek-devel-0.32.1-3.i686.rpm > -rw-r--r-- 1 vagrant vagrant 282K nov 13 2015 > poldek-libs-0.30.1-10.i686.rpm > -rw-r--r-- 1 vagrant vagrant 310K apr 26 16:04 poldek-libs-0.32.1-2.i686.rpm > -rw-r--r-- 1 vagrant vagrant 284K mai 3 10:34 poldek-libs-0.32.1-3.i686.rpm > -rw-r--r-- 1 vagrant vagrant 33K nov 13 2015 > poldek-static-0.30.1-10.i686.rpm > -rw-r--r-- 1 vagrant vagrant 36K apr 26 16:04 > poldek-static-0.32.1-2.i686.rpm > -rw-r--r-- 1 vagrant vagrant 33K mai 3 10:34 > poldek-static-0.32.1-3.i686.rpm > -rw-r--r-- 1 vagrant vagrant 75K nov 13 2015 > python-poldek-0.30.1-10.i686.rpm > -rw-r--r-- 1 vagrant vagrant 85K apr 26 16:04 > python-poldek-0.32.1-2.i686.rpm > -rw-r--r-- 1 vagrant vagrant 83K mai 3 10:34 > python-poldek-0.32.1-3.i686.rpm > I again suggest <[email protected]> as discussion forum, because I will not change %config without discussion. And I again suggest http://launchpad.net/rpm as a bug reporting system, so that we do not have to repeat these exchanges every 3 months. hth 73 de Jeff > > -- > glen > > _______________________________________________ > pld-devel-en mailing list > [email protected] > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
