pacman/pactest/tests/sync044.py

self.description = "A dependency induces a replacement"

lp1 = pmpkg("pkg1")
self.addpkg2db("local", lp1);

sp2 = pmpkg("pkg2")
sp2.depends = ["pkg3"]
self.addpkg2db("sync", sp2);

sp3 = pmpkg("pkg3")
sp3.conflicts = ["pkg1"]
self.addpkg2db("sync", sp3);

self.args = "-S pkg2 --ask=4"

self.addrule("PACMAN_RETCODE=0")
self.addrule("!PKG_EXIST=pkg1")
self.addrule("PKG_EXIST=pkg2")
self.addrule("PKG_EXIST=pkg3")
self.addrule("PKG_REASON=pkg3|1")
Add sync044 pactest : A dependency induces a replacement. That is the problem mentioned by Nagy there (with suggestions for fixing it) : http://www.archlinux.org/pipermail/pacman-dev/2007-August/009082.html If a dependency conflicts with a local package and has to replace it, the PM_SYNC_TYPE_DEPEND information is lost, and the resulting install reason is wrong (the package is marked as explictly installed). Signed-off-by: Chantry Xavier <shiningxc@gmail.com> 2007-09-23 11:07:13 -04:00			`self.description = "A dependency induces a replacement"`

			`lp1 = pmpkg("pkg1")`
			`self.addpkg2db("local", lp1);`

			`sp2 = pmpkg("pkg2")`
			`sp2.depends = ["pkg3"]`
			`self.addpkg2db("sync", sp2);`

			`sp3 = pmpkg("pkg3")`
			`sp3.conflicts = ["pkg1"]`
			`self.addpkg2db("sync", sp3);`

Do not remove conflict by default When a conflict is detected, pacman asks if the user wants to remove the conflicting package. In many cases this is a bad idea. e.g. udev conflicts with initscripts (initscripts<2009.07). Remove initscripts [Y/n] This changes the query to [y/N]. The --noconfirm behavior has been also changed, because it chooses the default answer. Since the yes answer is more interesting in our pactests dealing with conflicts, I inserted '--ask=4' to all of them with one exception: sync042.py tests the no answer. (I also fixed a typo in sync043.py) Original-work-by: Allan McRae <allan@archlinux.org> Signed-off-by: Nagy Gabor <ngaba@bibl.u-szeged.hu> 2009-08-31 17:54:51 -04:00			`self.args = "-S pkg2 --ask=4"`
Add sync044 pactest : A dependency induces a replacement. That is the problem mentioned by Nagy there (with suggestions for fixing it) : http://www.archlinux.org/pipermail/pacman-dev/2007-August/009082.html If a dependency conflicts with a local package and has to replace it, the PM_SYNC_TYPE_DEPEND information is lost, and the resulting install reason is wrong (the package is marked as explictly installed). Signed-off-by: Chantry Xavier <shiningxc@gmail.com> 2007-09-23 11:07:13 -04:00
			`self.addrule("PACMAN_RETCODE=0")`
			`self.addrule("!PKG_EXIST=pkg1")`
			`self.addrule("PKG_EXIST=pkg2")`
			`self.addrule("PKG_EXIST=pkg3")`
			`self.addrule("PKG_REASON=pkg3\|1")`