239070 – sys-apps/portage-2.2_rc11 does not store PROPERTIES in sqlite database

Bug 239070 - sys-apps/portage-2.2_rc11 does not store PROPERTIES in sqlite database

Summary: sys-apps/portage-2.2_rc11 does not store PROPERTIES in sqlite database

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	InVCS

Depends on:
Blocks:	210077
	Show dependency tree

Reported:	2008-09-29 18:51 UTC by Martin Väth
Modified:	2008-10-09 21:49 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Martin Väth 2008-09-29 18:51:24 UTC

I observed the problem when I implemented support for PROPERTIES in eix:
Although there is some azColName "PROPERTIES" stored in the sqlite database,
the corresponding entry is always empty (after emerge --metadata with
  portdbapi.auxdbmodule = cache.sqlite.database
  eclass_cache.dbmodule = cache.sqlite.database
in /etc/portage/modules) even for those packages for which it is nonempty in
the /usr/portage/metadata/cache database.

Other metadata like azColName "RESTRICT" does not have such a problem.
For the case that it is important: pysqlite-2.3.5 and sqlite-3.5.9 are used.

Comment 1 Zac Medico gentoo-dev

2008-09-29 19:32:38 UTC

This is fixed in svn r11560.

Comment 2 Zac Medico gentoo-dev

2008-10-09 21:49:56 UTC

This is fixed in 2.2_rc12.

If you run emerge --metadata then it should update the PROPERTIES values.