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-dev/2011-August/007321.html | 118 +++++++++++++++++++++++++++++ 1 file changed, 118 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-August/007321.html (limited to 'zarb-ml/mageia-dev/2011-August/007321.html') diff --git a/zarb-ml/mageia-dev/2011-August/007321.html b/zarb-ml/mageia-dev/2011-August/007321.html new file mode 100644 index 000000000..ff749d6d1 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-August/007321.html @@ -0,0 +1,118 @@ + + + + [Mageia-dev] help packaging lilypond + + + + + + + + + +

[Mageia-dev] help packaging lilypond

+ Thomas Spuhler + thomas at btspuhler.com +
+ Thu Aug 11 05:46:13 CEST 2011 +

+
+ +
On Wednesday, August 10, 2011 12:03:17 am Jani Välimaa wrote:
+> 2011/8/10 Jani Välimaa <jani.valimaa at gmail.com>:
+> > 2011/8/10 Thomas Spuhler <thomas at btspuhler.com>:
+> >> Thanks for fixing the spec file and submit the package.
+> >> I have a comment and a few questions. First the comment.
+> >> an experienced packager telling someone like me (and others not so
+> >> experienced packagers)  why the package build failed that built just a
+> >> few month ago would have helped learning how to fix things. Now the
+> >> package is built and I still don't know what the error message meant.
+> > 
+> > The build failed because now there are some checks which prevents
+> > uploading "erroneus" packages. Check for empty %post and %preun is one
+> > of those added checks. There's no such macro as %update_scrollkeeper
+> > (or  %clean_scrollkeeper) so that's why your build failed. See 'rpm
+> > --eval %update_scrollkeeper'
+> > 
+> >> why can the scrollkeepr script be removed as not required when it was
+> >> required not so long ago and other distributions use it too. It
+> >> supposed to be there if you have omf files, and yes lilypond-doc has
+> >> such files
+> > 
+> > It was me who removed the scrollkeeper reqs as I only looked at %files
+> > section and noticed there was no %{_datadir}/omf/ entry. The
+> > filetriggers looks
+> 
+> Oopsie, somehow managed to push the send button.. Anyways, the
+> filetriggers only looks .omf files from /usr/share/omf/ and now after
+> checking I see in lilypond they're hiding in somewhere else and out of
+> filetriggers reach. I think the fix would be moving them to a correct
+> place to be "available" for filetriggers (and add back reqs I
+> removed).
+> 
+> >> Can you please explain this in more details? I would appreciate it.
+> > 
+> > Sure
+
+I guess the current build works. I have been a user for a long time and 
+haven't seen any problems.
+The relase version should have come out on the 8th. as soon as it shows up, 
+will build it.
+
+-- 
+Thomas
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

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