packaging June 2008

packaging@lists.fedoraproject.org

45 participants
35 discussions

No build ID note found - how to resolve this?
by Mohd Izhar Firdaus Ismail 09 Jun '08

09 Jun '08

+ /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

3 3

clarification about the DraftsTodo table to edit
by Patrice Dumas 09 Jun '08

09 Jun '08

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

1 0

file-not-utf8 complaints
by Jason L Tibbitts III 02 Jun '08

02 Jun '08

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<

5 12

eclipse plugin without feature.xml
by Sergio Pascual 02 Jun '08

02 Jun '08

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

2 1

CMake link to upstream documentation added
by Toshio Kuratomi 01 Jun '08

01 Jun '08

I at the request of liquidat and cmake upstream I added some links to upstream's documentation to our cmake page: https://fedoraproject.org/wiki/Packaging/cmake This seemed straightforward. If anyone has issues with it, holler and we can discuss it at the Packaging Meeting. -Toshio

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

packaging June 2008