+####################
+#
+# (*) sometimes we have yum issuing errors like 'package does not match intended content'
+# this means that the sha256 checksum of the downloaded pkg does not match
+# the sha256 checksum advertised in filelists.xml
+# if you did run 'yum clean all' on the node,
+# this means that the repodata/ dir. on the server side is out of date
+# forcing a createrepo should solve this
+#
+# (*) also sometimes the node complains that a package is not signed
+#
+# so there quite obviously are some corner cases that are not well handled
+# hopefully the following subforms may be helpful to recover in these cases
+#
+# /etc/plc.d/packages clean
+# performs cleanup of the yum repositories and signed-stamps
+# thus forcing the next 'start' command to re-sign and re-index everything
+# /etc/plc.d/packages superclean
+# like 'clean', plus this will reinstall the noderepo rpms that you have,
+# that is to say restart from unsigned rpms
+# /etc/plc.d/packages start
+# this is the usual form, it should be smart enough to only sign the packages that need to,
+# and to rerun createrepo when useful
+# /etc/plc.d/packages force
+# same as 'start' but createrepo is run unconditionnally
+#
+# PS. I suspect sometimes the signing fails and the script does not notice properly
+####################
+
+
+# helper for hacking yumgroups