From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-discuss/2013-February/009171.html | 77 ++++++++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 zarb-ml/mageia-discuss/2013-February/009171.html (limited to 'zarb-ml/mageia-discuss/2013-February/009171.html') diff --git a/zarb-ml/mageia-discuss/2013-February/009171.html b/zarb-ml/mageia-discuss/2013-February/009171.html new file mode 100644 index 000000000..88851ab5a --- /dev/null +++ b/zarb-ml/mageia-discuss/2013-February/009171.html @@ -0,0 +1,77 @@ + + + + [Mageia-discuss] Local custom repo - "Advisory/Upgrade notice" question + + + + + + + + + +

[Mageia-discuss] Local custom repo - "Advisory/Upgrade notice" question

+ Johnny A. Solbu + cooker at solbu.net +
+ Sun Feb 10 03:49:39 CET 2013 +

+
+ +
For some time now I've maintained a few local packages in a custom repo for me and my friends. But there is one feature I have yet to figure out how to do.
+
+When Mageia ship an update, an update notice and/or advisory is sometimes added to the package somehow, detailing why the update is required.
+How can I add such a notice on the updates I ship with my own packages?
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 190 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-discuss/attachments/20130210/a6956299/attachment.asc>
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-discuss +mailing list
+ -- cgit v1.2.1