Le mardi 28 juin 2011 16:02:13, nicolas vigier a écrit : > On Tue, 28 Jun 2011, Samuel Verschelde wrote: > > Le mardi 28 juin 2011 15:20:33, nicolas vigier a écrit : > > > Hello, > > > > > > In order to send updates advisories, and have a web page listing all > > > previous advisories, we need to create a database to store them. > > > > > > So I think it should have the following info for each advisory : > > > - advisory ID: something like MGA-[NUMBER] ? > > > - advisory date > > > - affected source packages > > > - affected distribution versions > > > - CVE numbers > > > - list of binary packages with sha1sum > > > - Mageia Bug # > > > - Reference URLs > > > - advisory text > > - bugfix type: normal / security > > > > Anything else ? > > > > Is it for security bugs only or any update ? And will it be the central > > place where update messages are stored ? > > For both security and non-security updates, I forgot to add this info in > the list. > > This database will be used for : > - sending an email to updates-announce mailing list > - generate the descriptions file used by rpmdrake to show infos about > new updates > - a web page to list all updates > > > If possible, I'd like to be able to query such a database containing an > > update message for each update, and more information if needed, to able > > to display them for package updates in Mageia App Db. > > I think we can provide this as json.
That would be great. Samuel
