Modify ↓
Ticket #723 (closed defect: fixed)
Not sure how to fix: clients need to be part of a magic arch-specific group to work with Packages
| Reported by: | David Strauss <[email protected]…> | Owned by: | desai |
|---|---|---|---|
| Priority: | critical | Milestone: | Bcfg2 1.0.0 Release |
| Component: | bcfg2-client | Version: | 1.0 |
| Keywords: | Cc: |
Description
Currently, a client must be a member of a group with a name matching the architecture in order to have dependencies properly processed by the Packages plugin.
Ideally, such "magic" groups should not exist. In any case, the Packages plugin shouldn't allow any usage of a repository source if the architecture doesn't match; it shouldn't just fail to find dependencies.
Attachments
Change History
Note: See
TracTickets for help on using
tickets.
We struggled with this issue quite a bit during the design of Packages (and the need to use groups with pre-defined semantics was the major factor that made Packages a relatively recent addition to the system)
I've updated the Packages? wiki page to describe this more fully, and added a server error message to make it clear when Packages is not able to provide any information in [fce273a0e8fda3776d917f3f254b566a08c31ceb] (SVN r5424).