FS#9349 - etracer force flag missing in the database

Attached to Project: Community Packages
Opened by Xavier (shining) - Saturday, 26 January 2008, 22:02 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 27 January 2008, 22:23 GMT
Task Type Bug Report
Category
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
As we can see here :
http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/*checkout*/games/etracer/PKGBUILD?rev=1.2&cvsroot=AUR&only_with_tag=HEAD
the PKGBUILD of etracer 0.4-1 does have the force option set :
options=('force')

However, the force flag doesn't appear in the sync database.
$ grep FORCE /var/lib/pacman/sync/community/etracer-0.4-1/desc
<nothing>

Any ideas how community packages are added to the community database ?
Is repo-add used directly, or updatesync, or what?
updatesync is apparently just a wrapper to repo-add which handles the force flag in PKGBUILD.
If it finds that flag in the PKGBUILD, it calls repo-add with the --force option.

So either using updatesync or repo-add --force should work as far as I can tell.
That situation still looks confusing, but that should probably belong to another bug report.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Sunday, 27 January 2008, 22:23 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#9347 

Loading...