Description of problem: We have a development version of Lilypond (2.13.58) in Mageia 1. The stable release of 2.14.2 needs fontforge >= 20100501 to build Version-Release number of selected component (if applicable): The update of lilypond would also take care of bug #3050 How reproducible: Steps to Reproduce: 1. 2. 3.
Bug assigned to the package maintainer.
Assignee: bugsquad => anssi.hannula
Assignee: anssi.hannula => doktor5000
OK, i'll take a look. @Thomas Spuhler: Did you already ask for en exception to our updates policy for fontforge and lilypond?
Status: NEW => ASSIGNED
as we had a development release i find normal to update to a stable release and then do not allow new updates like normal softwares.
CC: (none) => dmorganec
Update commited, waiting for review. Checked that lilypond-2.14.2 builds with it OK. But still those warnings need to be fixed: https://bugs.mageia.org/show_bug.cgi?id=3050 They are still there with fontforge-1.0-0.20100501 and lilypond-2.14.2.
I cannot find fontforge-1.0-0.20100501 in updates_testing. What am I missing?
(In reply to comment #5) > I cannot find fontforge-1.0-0.20100501 in updates_testing. What am I missing? A google search of fontforge 20100501 site:mageia.org shows it's currently only in svn, so it hasn't been sent to updates testing (yet).
CC: (none) => davidwhodgins
Would have posted here if it would have been submitted. @Thomas: Unrelated, but please when you touch other packages next time, please make sure you don't drop patches that are still needed and please make sure you remove old sources after uploading new ones. I'm speaking of fontforge in cauldron. It was built successfully, and old tarballs were still there. Also you forgot to update two of the sources.
There is now fontforge-1.0-0.20100501.1.1.mga1 in core/updates_testing to validate ------------------------------------------------------- Suggested advisory: ------------------- This update addresses the following issue: fontforge >= 20100501 is needed to upgrade the current development version of lilypond (2.13.58) in Mageia to a stable release (2.14.2). ------------------------------------------------------- Steps to reproduce: - install/update to update candidate
Assignee: doktor5000 => qa-bugs
Testing complete on i586 for the srpm fontforge-1.0-0.20100501.1.1.mga1.src.rpm For testing, I copied /usr/share/fonts/vemana2000/Vemana2000.ttf to my home directory, and used fontforge to modify some of the glyphs. Used fontimage Vemana2000.ttf to create Vemana2000.png.
Florian, I am not aware of dropping a patch. I reverted to a pristine mageia 1, dropping all snapshots and did a checkout using an older mgarepo that was installed from earlier days. I got a lot of errors about missing paths and when trying to build it locally, I notice the missing patch. I wonder if the old mgarepo screwed it up, but no logs show anything. If I did it, it wasn't intentionally.
Fontforge tested OK x86_64 Moved some points about on a downloaded font and created a png Update validated Advisory ------------------- This update addresses the following issue: fontforge >= 20100501 is needed to upgrade the current development version of lilypond (2.13.58) in Mageia to a stable release (2.14.2). ------------------- Source RPM: fontforge-1.0-0.20100501.1.1.mga1.src.rpm Could sysadmin please push from core/updates_testing to core/updates. Thankyou!
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugsHardware: i586 => All
Update pushed.
Status: ASSIGNED => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED
(In reply to comment #10) > Florian, I am not aware of dropping a patch. I reverted to a pristine mageia 1, > dropping all snapshots and did a checkout using an older mgarepo that was > installed from earlier days. I got a lot of errors about missing paths and when > trying to build it locally, I notice the missing patch. > I wonder if the old mgarepo screwed it up, but no logs show anything. If I did > it, it wasn't intentionally. Uhhm, please look at this commit, your comment in spec sounds not unintentional, or am i mistaken there? http://svnweb.mageia.org/packages/cauldron/fontforge/current/SPECS/fontforge.spec?r1=91662&r2=109560 This is not pointing fingers, just noticed it and wanted to make you aware. The patch just needed to be rediffed :)
CC: (none) => doktor5000
I forgot about that. I wanted/needed to upgrade it and it didn't build. I then got sidetracked and forgot about it. But I still think I didn't delete the patch. Actually, I was reminded several times to delete files that are not needed anymore. But again, I am not that sure. I think at that time, the package didn't have a maintainer, did it?
No problem :) Since you didn't use mgarepo sync, the patch was only not applied, but not physically deleted ;) Also because you didn't use mgarepo sync, the SVN held tarballs for both versions of fontforge, which is a waste of space. And no, at that time it didn't have a maintainer, you're right there. Maybe this is just a misunderstanding of the workflow. Normally you would checkout package foobar from svn, update it locally and if it builds correctly, use mgarepo sync and then commit. IIRC you told that you normally remove old tarballs only if the package builds correctly. But then i don't know why one would want to manually upload new sources if the package doesn't build sucessfully ...