Custom Query (894 matches)
Results (28 - 30 of 894)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #721 | desai | David Strauss <[email protected]…> | duplicate | Clarify the relationship between managed packages and dependencies |
| Description |
Currently, bcfg2 only considers the explicit, top-level packages to be managed entries. Yet, top-level packages run through the Packages plugin generally have many dependencies. These dependencies should be considered "managed" too, in some way. |
|||
| #722 | desai | David Strauss <[email protected]…> | fixed | Provide a straightforward authentication upgrade path |
| Description |
Currently, users of 1.0pre5 who came from 0.9.6 have to edit /etc/bcfg2.conf to copy the value for the "key =" line to a "certificate =" line. |
|||
| #723 | desai | David Strauss <[email protected]…> | fixed | Not sure how to fix: clients need to be part of a magic arch-specific group to work with Packages |
| 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. |
|||
