#33 Doesn't build against nautilus-cd-burner 2.15

closed
nobody
None
5
2006-09-12
2006-07-22
Anonymous
No

0.4.1 is not building against nautilus-cd-burner 2.15.
Has a bunch of errors like:

recorder-selection.c:870: error: 'NautilusBurnDrive'
has no member named
'max_speed_write'
recorder-selection.c: In function
'bonfire_recorder_selection_button_cb':
recorder-selection.c:1100: error: 'NautilusBurnDrive'
has no member named
'type'recorder-selection.c: In function
'bonfire_recorder_selection_get_drive':
recorder-selection.c:1138: error: 'NautilusBurnDrive'
has no member named
'type'recorder-selection.c:1144: error:
'NautilusBurnDrive' has no member named
'display_name'
recorder-selection.c: In function
'bonfire_recorder_selection_select_default_drive':
recorder-selection.c:1180: warning: implicit
declaration of function
'nautilus_burn_drive_get_list'
recorder-selection.c:1180: warning: assignment makes
pointer from integer
without a cast
recorder-selection.c:1184: error: 'NautilusBurnDrive'
has no member named
'type'

Discussion

  • Cyril Jaquier
    Cyril Jaquier
    2006-08-21

    Logged In: YES
    user_id=933467

    +1 for this one

    Thanks

     
  • Logged In: NO

    same error in 0.4.2(stable) :-(

     
  • Logged In: YES
    user_id=351613

    Now that 2.16.0 is out, this should go top-priority.

    +1 from me

     
  • Logged In: YES
    user_id=1402420

    trunk (unstable) has support for ncb-2.15/6 (among other
    things) so if you want to try it out I should make a release
    this afternoon. I might back port the patch.

     
  • Logged In: YES
    user_id=351613

    It's quite a matter of trying it out. I need to repackage it
    for PLD Linux as we are now running Gnome 2.16. Otherwise we
    need to drop bonfire like we did with gnomebaker as some
    users are unable to update the rest of the packages.

    Looking forward to the release (btw, the main page is
    missing the latest stable).

     
    • status: open --> closed
     
  • Logged In: YES
    user_id=1402420

    As you may know this bug is fixed.