| Summary: | Package and install mageia-app-db | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | Nicolas Vigier <boklm> |
| Component: | BuildSystem | Assignee: | Sysadmin Team <sysadmin-bugs> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | dan, marja11, stormi-mageia |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Nicolas Vigier
2011-04-14 19:14:18 CEST
Nicolas Vigier
2011-04-14 19:15:45 CEST
CC:
(none) =>
stormi Not yet, it has been decided to wait for version 0.3 of madb (which has LDAP integration) before installing it on the servers. And version 0.3 kind of was delayed by the need there was for more time of mine spent on QA team organization and various other Mageia-related duties :) In parallel, we are working on the packaging of madb. Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED. Since you're working on it, do you mind setting the status to ASSIGNED? Do you want "package madb" and "install madb" to stay in this bug report together, or do you want it to be cloned?
Nicolas Vigier
2012-01-13 23:03:25 CET
Status:
NEW =>
ASSIGNED The madb.mageia.org server was migrated to Mageia.Org in September 2023. This bug seems to be about packaging the software and (streamlining?) installation. Has anything happened on that front? CC:
(none) =>
dan No, we haven't done anything regarding its packaging, which is a bit tricky and not necessarily mandatory. Let's close this and open a new one if we give it new traction. Resolution:
(none) =>
OLD Is the code in a Mageia git repository? That would be a good start. |