pacman/pactest/tests/sync300.py

self.description = "Sync with corrupt database (broken deps)"

sp1 = pmpkg("pkg1")
sp1.depends = ["pkg2=1.1"]
self.addpkg2db("sync", sp1)

sp2 = pmpkg("pkg2", "1.0-1")
self.addpkg2db("sync", sp2)

self.args = "-S %s" % sp1.name

self.addrule("PACMAN_RETCODE=0")
self.addrule("!PKG_EXIST=pkg1")
self.addrule("!PKG_EXIST=pkg2")
Add five new pactest tests where pacman currently fails Most of these new tests deal with provisions upon sync or upgrade being changed by packages, and pacman not being smart enough to deal with it yet. Signed-off-by: Dan McGee <dan@archlinux.org> 2007-06-04 09:37:46 -04:00			`self.description = "Sync with corrupt database (broken deps)"`

			`sp1 = pmpkg("pkg1")`
			`sp1.depends = ["pkg2=1.1"]`
			`self.addpkg2db("sync", sp1)`

			`sp2 = pmpkg("pkg2", "1.0-1")`
			`self.addpkg2db("sync", sp2)`

			`self.args = "-S %s" % sp1.name`

Enabled new interactive prompt and updated some tests Enabled a new prompt to ask the user if they'd like to remove unresolvable packages from the transaction rather than failing it. Many pactest tests that used to fail now return success codes, because pacman now issues a prompt allowing the user to cancel rather than failing many transactions, and the pactest scripts always choose to cancel with no error rather than failing. The only net effect is that the return status of pacman is now 0 in cases where it used to be nonzero. Signed-off-by: Bryan Ischo <bryan@ischo.com> Signed-off-by: Dan McGee <dan@archlinux.org> 2009-02-22 23:25:31 +13:00			`self.addrule("PACMAN_RETCODE=0")`
Add five new pactest tests where pacman currently fails Most of these new tests deal with provisions upon sync or upgrade being changed by packages, and pacman not being smart enough to deal with it yet. Signed-off-by: Dan McGee <dan@archlinux.org> 2007-06-04 09:37:46 -04:00			`self.addrule("!PKG_EXIST=pkg1")`
			`self.addrule("!PKG_EXIST=pkg2")`