This release brings new features and bugfixes in the library and the opensync plugin. Brian Edginton has added support for the Time Zone database on newer Blackberries. A naming collision bug has been fixed in the opensync plugin. The file format that btool uses to save parsed data has been changed slightly, and a new tool (bs11nread) is available to read such data without writing it back to the device. Build system fixes for 64 bit systems are also included.
You can rename barry-0.11.ebuild to barry-0.12.ebuild in an local overlay.
Created attachment 149019 [details] barry-0.12.ebuild This the barry-0.11.ebuild renamed to barry-0.12.ebuild. It compiles fine.
Created attachment 152049 [details] Complete ebuild for barry-0.12 with gui, etc. support This ebuild includes use flags and dependencies for boost, gui, and opensync-plugin. Some of the dependencies may be run-time, but I haven't asked the dev and I honestly wouldn't know how to find out. The econf options $(use_with gui libtar=/usr/lib) and $(use_with gui libz=/usr/lib) technically should be applied to "=== configuring in gui..." gui configure inherits from the main so no biggie if ebuilds don't have an explicit way to apply options directly to sub configs. I explicitly list =dev-libs/libtar-1.2.11-r1 because it has been suggested that it is sloppy and the attached patch for barry allows barry to compile against the possibly broken libtar. libtar's emerge spouts the following: * QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures. See also http://www.mail-archive.com/barry-devel@lists.sourceforge.net/msg00266.html
Created attachment 152051 [details, diff] The patch for barry-012.ebuild
Hey Kris, thanks for the ebuild! :D Is it also possible to make an ebuild for the cvs version? (cvs has support for the latest models)
Created attachment 158313 [details, diff] gcc-4.3 patch Patch to make barry compile with GCC 4.3. See http://bugs.gentoo.org/show_bug.cgi?id=228755
Why haven't the new ebuild and patch been added to portage yet? It's been a few months.
Kris, I'm aware about your new bug #233946, but would like to suggest not to file new bugs anymore for each new coming version. Barry dump request is taking long time to submit for whatever reason and I want to propose keep all track changes and new version in one bug, i.e. here. It's simple easier to be involved in the progress.
Created attachment 172179 [details] barry-0.14.ebuild, gcc-4.3 patch is not enabled gcc patch need to be re-applied
Created attachment 172180 [details, diff] tar-int patch
Created attachment 172182 [details, diff] gcc43 corrected patch Not verified
Created attachment 172184 [details] barry-0.14.ebuild gcc patch enabled, typo fixed
Is there no maintainer?
Created attachment 178439 [details] git ebuild git ebuild: note, i renamed the current patches to match the packet version works with my 8220
When I try to emerge the it version in dies like this: I=/usr/include/include -ansi -Wall -g -march=native -O2 -L=/usr/include/lib -Wl,--hash-style=both -o btool btool-btool.o ../src/libbarry.la -lusb -lpthread -lboost_serialization -lpthread mv -f .deps/pppob.Tpo .deps/pppob.Po /bin/sh ../libtool --tag=CXX --mode=link x86_64-pc-linux-gnu-g++ -ansi -Wall -g -march=native -O2 -Wl,--hash-style=both -o bidentify bidentify.o ../src/libbarry.la -lusb -lpthread -lpthread /bin/sh ../libtool --tag=CXX --mode=link x86_64-pc-linux-gnu-g++ -ansi -Wall -g -march=native -O2 -Wl,--hash-style=both -o bjavaloader bjavaloader.o ../src/libbarry.la -lusb -lpthread -lpthread ../libtool: line 4999: cd: =/usr/include/lib: No such file or directory libtool: link: cannot determine absolute directory name of `=/usr/include/lib' make[2]: *** [btool] Error 1 make[2]: *** Waiting for unfinished jobs.... libtool: link: x86_64-pc-linux-gnu-g++ -ansi -Wall -g -march=native -O2 -Wl,--hash-style=both -o .libs/bjavaloader bjavaloader.o ../src/.libs/libbarry.so /usr/lib64/libusb.so -lpthread libtool: link: x86_64-pc-linux-gnu-g++ -ansi -Wall -g -march=native -O2 -Wl,--hash-style=both -o .libs/bidentify bidentify.o ../src/.libs/libbarry.so /usr/lib64/libusb.so -lpthread make[2]: Leaving directory `/var/tmp/paludis/app-pda-barry-9999/work/barry-9999/tools' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/paludis/app-pda-barry-9999/work/barry-9999' make: *** [all] Error 2 /usr/libexec/paludis/utils/emake: emake returned error 2 !!! ERROR in app-pda/barry-9999: !!! In src_compile at line 3603 !!! Error: emake failed! !!! Call stack: !!! * src_compile (/var/tmp/paludis/app-pda-barry-9999/temp/loadsaveenv:3603) !!! * ebuild_f_compile (/usr/libexec/paludis/0/src_compile.bash:49) !!! * ebuild_main (/usr/libexec/paludis/ebuild.bash:482) !!! * main (/usr/libexec/paludis/ebuild.bash:498) diefunc: making ebuild PID 28430 exit with error die trap: exiting with error. Install error: * In program paludis -i barry: * When performing install action from command line: * When executing install task: * When installing 'app-pda/barry-9999:0::local': * When running an ebuild command on 'app-pda/barry-9999:0::local': * Install error: Install failed for 'app-pda/barry-9999:0::local' Summary of failures: * app-pda/barry-9999:0::local: failure
(In reply to comment #15) > * app-pda/barry-9999:0::local: failure That's because 9999 is "live" ebuild and shouldn't be here at all... Try to recompile after couple hours/days again and submit your problem to the upsteam directly. Make sure this is what you want as well. Otherwise just use the latest released version.
(comment #7) > Why haven't the new ebuild and patch been added to portage yet? It's been a few > months. (comment #13) > Is there no maintainer? Can someone comment on this? If barry has no maintainer it should be moved out of the tree. Then we can maintain it in Sunrise. Barry 0.14 has been released 5 months ago.
Patrick might help us as he mentioned it in his blog recently.
Created attachment 183220 [details] New git ebuild Removed an extra '=' from econf, removed gcc patch
*** Bug 233946 has been marked as a duplicate of this bug. ***
Created attachment 191161 [details] ebuild applying GCC-4.4 patch Barry 0.14 ebuild applying GCC-4.4 patch.
Created attachment 191163 [details, diff] GCC-4.4 patch The GCC 4.4 patch. Not sure if the way I've done it is "standard", please comment with any "good practice", this is one of my firsts patches :-)
Created attachment 207502 [details] barry-0.16 ebuild. Renamed barry-0.14.ebuild and removed unnecessary patches.
app-pda/barry-0.16 in portage Big thanks to everybody for their feedback!
