Re: libmtp7 -> libmtp8 transition
* Adeodato Simó <dato@net.com.org.es> [2009-02-21 21:56]:
> * Rafael Laboissiere [Sun, 15 Feb 2009 14:22:54 +0100]:
> > * mtpfs
>
> > Version 0.9 currently in experimental builds fine without changes against
> > libmtp-dev 0.3.6.
>
> Good. Chris, is mtpfs 0.9 ready to be uploaded to unstable, or else, is
> the unstable version buildable against libmtp8? Thanks.
Version 0.8+svn11-1 builds file with the debdiff patch attached below. Not
tested.
--
Rafael
diff -u mtpfs-0.8+svn11/debian/changelog mtpfs-0.8+svn11/debian/changelog
--- mtpfs-0.8+svn11/debian/changelog
+++ mtpfs-0.8+svn11/debian/changelog
@@ -1,3 +1,9 @@
+mtpfs (0.8+svn11-1.1) UNRELEASED; urgency=low
+
+ * Build against libmtp8
+
+ -- Rafael Laboissiere <rafael@debian.org> Sun, 22 Feb 2009 01:20:27 +0100
+
mtpfs (0.8+svn11-1) unstable; urgency=low
* Initial release (Closes: #457236)
only in patch2:
unchanged:
--- mtpfs-0.8+svn11.orig/mtpfs.c
+++ mtpfs-0.8+svn11/mtpfs.c
@@ -174,7 +174,7 @@
ret = LIBMTP_Update_Playlist(device,playlist);
} else {
if(DEBUG) g_debug("New playlist");
- ret = LIBMTP_Create_New_Playlist(device,playlist,0);
+ ret = LIBMTP_Create_New_Playlist(device,playlist);
}
playlists_changed=TRUE;
return ret;
@@ -486,8 +486,7 @@
g_mutex_lock(device_lock);
ret =
LIBMTP_Send_Track_From_File_Descriptor (device, fi->fh,
- genfile, NULL, NULL,
- parent_id);
+ genfile, NULL, NULL);
g_mutex_unlock(device_lock);
id3_file_close (id3_fh);
LIBMTP_destroy_track_t (genfile);
@@ -503,8 +502,7 @@
g_mutex_lock(device_lock);
ret =
LIBMTP_Send_File_From_File_Descriptor (device, fi->fh,
- genfile, NULL, NULL,
- parent_id);
+ genfile, NULL, NULL);
g_mutex_unlock(device_lock);
LIBMTP_destroy_file_t (genfile);
if (DEBUG) g_debug ("Sent FILE %s",path);
@@ -982,7 +980,7 @@
}
if (DEBUG) g_debug ("%s:%s:%d", filename, directory, parent_id);
g_mutex_lock(device_lock);
- ret = LIBMTP_Create_Folder (device, filename, parent_id);
+ ret = LIBMTP_Create_Folder (device, filename, parent_id, 0);
g_mutex_unlock(device_lock);
g_strfreev (fields);
g_free (directory);
Reply to: