No build ID note found - how to resolve this?
by Mohd Izhar Firdaus Ismail
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id
/builddir/build/BUILD/libitl-0.6.4
extracting debug info from
/var/tmp/libitl-0.6.4-4.fc10-root-mockbuild/usr/lib/libitl.so.0.0.6
*** ERROR: No build ID note found in
/var/tmp/libitl-0.6.4-4.fc10-root-mockbuild/usr/lib/libitl.so.0.0.6
What should I do to resolve that?. FTBFS bug 449622 . This package
previously builds fine on F9.
--
Mohd Izhar Firdaus Bin Ismail
Amano Hikaru
天野晃 「あまの ひかる」
http://fedoraproject.org/wiki/MohdIzharFirdaus
http://blog.kagesenshi.org
92C2 B295 B40B B3DC 6866 5011 5BD2 584A 8A5D 7331
15 years, 10 months
clarification about the DraftsTodo table to edit
by Patrice Dumas
Hello,
I try to follow the
http://fedoraproject.org/wiki/Packaging/Committee#Guideline_Change_Procedure
to resubmit a guideline that didn't pass the vote the first time. But in
the Step One, there is:
Once you're happy with the Draft, add it to the DraftsTodo table.
However there are 3 tables in DraftsTodo table, one with
'Has a Driver', one with 'Queued but Unowned', and one 'Tabled (On
indefinite hold)'. The most logical seems to be 'Has a Driver', but it is
not very clear. In fact it looks less like a page where new guidelines
are proposed than like a page holding the status of current guidelines
under review.
Maybe there could be a new table with the packaging drafts proposed?
--
Pat
15 years, 10 months
file-not-utf8 complaints
by Jason L Tibbitts III
Normally we fix up non-utf8 documentation and such with a quick call
to iconv. It seems that this is problematic for some; see
https://bugzilla.redhat.com/show_bug.cgi?id=226079
Any comments on how much we actually care about this, especially in
the case that it might not actually be as easy as a call to iconv
(such as a changelog file with a pile of random encodings in it).
- J<
15 years, 10 months
eclipse plugin without feature.xml
by Sergio Pascual
Hello, I'm trying to package a eclipse plugin called veditor. I have
followed the guidelines in wiki/Packaging/EclipsePlugins
The zip with the source code contains a file plugin.xmll but doesn't
contain feature.xml. When building,
%{eclipse_base}/buildscripts/pdebuild -f net.sourceforge.veditor
fails, because feature.xml doesn't exist. How do I build with
plugin.xml but without feature.xml?
Regards, Sergio
15 years, 10 months
