Trouble Building Banshee on Linux Mint (Again)

Trouble Building Banshee on Linux Mint (Again)

Thought I'd try building Banshee again almost 18 months after first
effort. First efforts failed primarily because Mint was based on a
dated release fo Ubuntu at the time , but it's up to date now and
has been for a while so I thought to give it a crack. So I followed
the directions here:

under Ubuntu. And all is well until I run autogen.sh which bails
with:

checking for Mono 2.0 GAC for Mono.Posix.dll... not
found
configure: error: missing required Mono 2.0 assembly:
Mono.Posix.dll
Error: There were errors when running './configure', a step that
is required to configure banshee

Go figure! I'd have thought that was well covered by all the
prerequisites listed, and I've installed MonoDevelop and Mono from
the package mono-complete from the Ubuntu repositories (labelled as
Complete mono runtime, development tools and all
libraries) but no luck. If I "locate Mono.Posix"
telling results are:

To wit Mono.Posix.dll is installed, but autogen.sh isn't finding it.
Perhaps some environment variable or other is what it wants, if it's
too blind to find it alone. What is going on and why (again) is
Banshee apparently not so simple to build? After all the clear
effort that's gone into Ubuntu support on that development page and
more?

1) Does banshee really depend on a dated version of Mono? (a version
superceded in 2009!)
2) Can I install a dated version of Mono? And if so, how?
3) Can such a dated version of Mono exist in parallel with the
latest version without causing hassles elsewhere?

We could probably look at updating some of these dependencies as I
think some distributions are dropping Banshee through build
difficulties - Gentoo appears to be anyway so feel free to share a
patch when you get up and running.

> Thought I'd try building Banshee again almost 18 months after first effort.
> First efforts failed primarily because Mint was based on a dated release fo
> Ubuntu at the time , but it's up to date now and has been for a while so I
> thought to give it a crack. So I followed the directions here:
>
> http://banshee.fm/download/development/>
> under Ubuntu. And all is well until I run autogen.sh which bails with:
>
> checking for Mono 2.0 GAC for Mono.Posix.dll... not found
> configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll
> Error: There were errors when running './configure', a step that is required
> to configure banshee
>
> Go figure! I'd have thought that was well covered by all the prerequisites
> listed, and I've installed MonoDevelop and Mono from the package
> mono-complete from the Ubuntu repositories (labelled as Complete mono
> runtime, development tools and all libraries) but no luck. If I "locate
> Mono.Posix" telling results are:
>
> /usr/lib/mono/4.5/Mono.Posix.dll
> /usr/lib/mono/gac/Mono.Posix
> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756
> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756/Mono.Posix.dll
>
> To wit Mono.Posix.dll is installed, but autogen.sh isn't finding it. Perhaps
> some environment variable or other is what it wants, if it's too blind to
> find it alone. What is going on and why (again) is Banshee apparently not so
> simple to build? After all the clear effort that's gone into Ubuntu support
> on that development page and more?
>
> Anyhow:
>
> bash -x autogen.sh
>
> reveals that ./configure is what's bailing. And:
>
> bash -x configure
>
> in turn reveals that this is what's failing:
>
> + test -e /usr/lib/mono/2.0/Mono.Posix.dll -o -e
> /usr/lib/mono/2.0/Mono.Posix.dll
>
> And voila, I have Mono 4.5 not 2.0.
>
> So, that begs the obvious questions:
>
> 1) Does banshee really depend on a dated version of Mono? (a version
> superceded in 2009!)
> 2) Can I install a dated version of Mono? And if so, how?
> 3) Can such a dated version of Mono exist in parallel with the latest
> version without causing hassles elsewhere?
>
> Puzzled, and appreciating any insights.
>
> Kind regards,
>
> Bernd.
>
>
> _______________________________________________
> banshee-list mailing list
> [hidden email]> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)

Re: Trouble Building Banshee on Linux Mint (Again)

Nicholas,

Thanks for the pointer. Have had a quick look (as in 30 mins of
looking and reading) and have a lot to learn about autoconf before
much makes sense to me. What the heck is shamrock?

Leaves me wondering alas if all the Banshee developers and
contributors are old hats at it, have had the dev environments and
build streams set up for long time (pre Mono 2!) and if not, how
noobs since then have actually installed and got running with a
working build? I may hack around as time permits, but time is
scant alas, and the main driver that motivates me perhaps is
learning more about autoconf and its ilk as a general background
skill.

Regards,

Bernd.

Nicholas Little via banshee-list wrote:

Hi Bernd,
That's some nice shell foo. In configure.ac you'll find:
SHAMROCK_CHECK_MONO_2_0_GAC_ASSEMBLIES([
Mono.Posix
ICSharpCode.SharpZipLib
])
You'll probably have to do some hacking around in the build subtree,
which contains all the macros used by autotools, in order to get it to
work - specifically take a look at
https://github.com/GNOME/banshee/blob/master/build/m4/shamrock/mono.m4
We could probably look at updating some of these dependencies as I
think some distributions are dropping Banshee through build
difficulties - Gentoo appears to be anyway so feel free to share a
patch when you get up and running.
Good luck.
Yours,
Nicholas
On 29 May 2017 at 01:53, Bernd Wechner [hidden email] wrote:
> Thought I'd try building Banshee again almost 18 months after first effort.
> First efforts failed primarily because Mint was based on a dated release fo
> Ubuntu at the time , but it's up to date now and has been for a while so I
> thought to give it a crack. So I followed the directions here:
>
> http://banshee.fm/download/development/
>
> under Ubuntu. And all is well until I run autogen.sh which bails with:
>
> checking for Mono 2.0 GAC for Mono.Posix.dll... not found
> configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll
> Error: There were errors when running './configure', a step that is required
> to configure banshee
>
> Go figure! I'd have thought that was well covered by all the prerequisites
> listed, and I've installed MonoDevelop and Mono from the package
> mono-complete from the Ubuntu repositories (labelled as Complete mono
> runtime, development tools and all libraries) but no luck. If I "locate
> Mono.Posix" telling results are:
>
> /usr/lib/mono/4.5/Mono.Posix.dll
> /usr/lib/mono/gac/Mono.Posix
> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756
> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756/Mono.Posix.dll
>
> To wit Mono.Posix.dll is installed, but autogen.sh isn't finding it. Perhaps
> some environment variable or other is what it wants, if it's too blind to
> find it alone. What is going on and why (again) is Banshee apparently not so
> simple to build? After all the clear effort that's gone into Ubuntu support
> on that development page and more?
>
> Anyhow:
>
> bash -x autogen.sh
>
> reveals that ./configure is what's bailing. And:
>
> bash -x configure
>
> in turn reveals that this is what's failing:
>
> + test -e /usr/lib/mono/2.0/Mono.Posix.dll -o -e
> /usr/lib/mono/2.0/Mono.Posix.dll
>
> And voila, I have Mono 4.5 not 2.0.
>
> So, that begs the obvious questions:
>
> 1) Does banshee really depend on a dated version of Mono? (a version
> superceded in 2009!)
> 2) Can I install a dated version of Mono? And if so, how?
> 3) Can such a dated version of Mono exist in parallel with the latest
> version without causing hassles elsewhere?
>
> Puzzled, and appreciating any insights.
>
> Kind regards,
>
> Bernd.
>
>
> _______________________________________________
> banshee-list mailing list
> [hidden email]
> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)

Now I just have to work out how to apply the patch (and find time
to) and then perhaps to post a pull request to the banshee repo
for it (assuming it does the job).

Regards,

Bernd.

Nicholas Little via banshee-list wrote:

Hi Bernd,
That's some nice shell foo. In configure.ac you'll find:
SHAMROCK_CHECK_MONO_2_0_GAC_ASSEMBLIES([
Mono.Posix
ICSharpCode.SharpZipLib
])
You'll probably have to do some hacking around in the build subtree,
which contains all the macros used by autotools, in order to get it to
work - specifically take a look at
https://github.com/GNOME/banshee/blob/master/build/m4/shamrock/mono.m4
We could probably look at updating some of these dependencies as I
think some distributions are dropping Banshee through build
difficulties - Gentoo appears to be anyway so feel free to share a
patch when you get up and running.
Good luck.
Yours,
Nicholas
On 29 May 2017 at 01:53, Bernd Wechner [hidden email] wrote:
> Thought I'd try building Banshee again almost 18 months after first effort.
> First efforts failed primarily because Mint was based on a dated release fo
> Ubuntu at the time , but it's up to date now and has been for a while so I
> thought to give it a crack. So I followed the directions here:
>
> http://banshee.fm/download/development/
>
> under Ubuntu. And all is well until I run autogen.sh which bails with:
>
> checking for Mono 2.0 GAC for Mono.Posix.dll... not found
> configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll
> Error: There were errors when running './configure', a step that is required
> to configure banshee
>
> Go figure! I'd have thought that was well covered by all the prerequisites
> listed, and I've installed MonoDevelop and Mono from the package
> mono-complete from the Ubuntu repositories (labelled as Complete mono
> runtime, development tools and all libraries) but no luck. If I "locate
> Mono.Posix" telling results are:
>
> /usr/lib/mono/4.5/Mono.Posix.dll
> /usr/lib/mono/gac/Mono.Posix
> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756
> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756/Mono.Posix.dll
>
> To wit Mono.Posix.dll is installed, but autogen.sh isn't finding it. Perhaps
> some environment variable or other is what it wants, if it's too blind to
> find it alone. What is going on and why (again) is Banshee apparently not so
> simple to build? After all the clear effort that's gone into Ubuntu support
> on that development page and more?
>
> Anyhow:
>
> bash -x autogen.sh
>
> reveals that ./configure is what's bailing. And:
>
> bash -x configure
>
> in turn reveals that this is what's failing:
>
> + test -e /usr/lib/mono/2.0/Mono.Posix.dll -o -e
> /usr/lib/mono/2.0/Mono.Posix.dll
>
> And voila, I have Mono 4.5 not 2.0.
>
> So, that begs the obvious questions:
>
> 1) Does banshee really depend on a dated version of Mono? (a version
> superceded in 2009!)
> 2) Can I install a dated version of Mono? And if so, how?
> 3) Can such a dated version of Mono exist in parallel with the latest
> version without causing hassles elsewhere?
>
> Puzzled, and appreciating any insights.
>
> Kind regards,
>
> Bernd.
>
>
> _______________________________________________
> banshee-list mailing list
> [hidden email]
> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)

Re: Trouble Building Banshee on Linux Mint (Again)

I'm not sure I'd bother with the pull request, last time I checked
they didn't accept them - you're better off commenting on the bugzilla
entry so that the maintainers get a notification.

I've tested that patch and it works for me. As in, I can autoreconf,
configure and make and the program doesn't crash :)

The only thing missing from that patch is the update to the mono.m4
within the Hyena submodule for completeness but that's just
duplication of what's already shown for the main one - I've added that
in the patches I pushed this morning to my forked respositories.

> Actually I just found a fix someone else did:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=753091>
> He posted a patch:
>
> https://bug753091.bugzilla-attachments.gnome.org/attachment.cgi?id=308515>
> Now I just have to work out how to apply the patch (and find time to) and
> then perhaps to post a pull request to the banshee repo for it (assuming it
> does the job).
>
> Regards,
>
> Bernd.
>
> Nicholas Little via banshee-list wrote:
>
> Hi Bernd,
>
> That's some nice shell foo. In configure.ac you'll find:
>
> SHAMROCK_CHECK_MONO_2_0_GAC_ASSEMBLIES([
> Mono.Posix
> ICSharpCode.SharpZipLib
> ])
>
> You'll probably have to do some hacking around in the build subtree,
> which contains all the macros used by autotools, in order to get it to
> work - specifically take a look at
> https://github.com/GNOME/banshee/blob/master/build/m4/shamrock/mono.m4>
> We could probably look at updating some of these dependencies as I
> think some distributions are dropping Banshee through build
> difficulties - Gentoo appears to be anyway so feel free to share a
> patch when you get up and running.
>
> Good luck.
>
> Yours,
> Nicholas
>
> On 29 May 2017 at 01:53, Bernd Wechner <[hidden email]> wrote:
>> Thought I'd try building Banshee again almost 18 months after first
>> effort.
>> First efforts failed primarily because Mint was based on a dated release
>> fo
>> Ubuntu at the time , but it's up to date now and has been for a while so I
>> thought to give it a crack. So I followed the directions here:
>>
>> http://banshee.fm/download/development/>>
>> under Ubuntu. And all is well until I run autogen.sh which bails with:
>>
>> checking for Mono 2.0 GAC for Mono.Posix.dll... not found
>> configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll
>> Error: There were errors when running './configure', a step that is
>> required
>> to configure banshee
>>
>> Go figure! I'd have thought that was well covered by all the prerequisites
>> listed, and I've installed MonoDevelop and Mono from the package
>> mono-complete from the Ubuntu repositories (labelled as Complete mono
>> runtime, development tools and all libraries) but no luck. If I "locate
>> Mono.Posix" telling results are:
>>
>> /usr/lib/mono/4.5/Mono.Posix.dll
>> /usr/lib/mono/gac/Mono.Posix
>> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756
>> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756/Mono.Posix.dll
>>
>> To wit Mono.Posix.dll is installed, but autogen.sh isn't finding it.
>> Perhaps
>> some environment variable or other is what it wants, if it's too blind to
>> find it alone. What is going on and why (again) is Banshee apparently not
>> so
>> simple to build? After all the clear effort that's gone into Ubuntu
>> support
>> on that development page and more?
>>
>> Anyhow:
>>
>> bash -x autogen.sh
>>
>> reveals that ./configure is what's bailing. And:
>>
>> bash -x configure
>>
>> in turn reveals that this is what's failing:
>>
>> + test -e /usr/lib/mono/2.0/Mono.Posix.dll -o -e
>> /usr/lib/mono/2.0/Mono.Posix.dll
>>
>> And voila, I have Mono 4.5 not 2.0.
>>
>> So, that begs the obvious questions:
>>
>> 1) Does banshee really depend on a dated version of Mono? (a version
>> superceded in 2009!)
>> 2) Can I install a dated version of Mono? And if so, how?
>> 3) Can such a dated version of Mono exist in parallel with the latest
>> version without causing hassles elsewhere?
>>
>> Puzzled, and appreciating any insights.
>>
>> Kind regards,
>>
>> Bernd.
>>
>>
>> _______________________________________________
>> banshee-list mailing list
>> [hidden email]>> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>
>
>
>
>
> _______________________________________________
> banshee-list mailing list
> [hidden email]> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)

and sit seems the PR is a standard way of capitalising on
community contribs. Of course triaging and merging them is work
someone has to do, but then PRs aren't PRs, some might be onerous
and others trivial patches like this ... ;-).

Regards,

Bernd.

Nicholas Little via banshee-list wrote:

Nice find, cheers.
I'm not sure I'd bother with the pull request, last time I checked
they didn't accept them - you're better off commenting on the bugzilla
entry so that the maintainers get a notification.
I've tested that patch and it works for me. As in, I can autoreconf,
configure and make and the program doesn't crash :)
The only thing missing from that patch is the update to the mono.m4
within the Hyena submodule for completeness but that's just
duplication of what's already shown for the main one - I've added that
in the patches I pushed this morning to my forked respositories.
FYI use 'git apply' for patches that look like that.
On 5 June 2017 at 08:23, Bernd Wechner [hidden email] wrote:
> Actually I just found a fix someone else did:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=753091
>
> He posted a patch:
>
> https://bug753091.bugzilla-attachments.gnome.org/attachment.cgi?id=308515
>
> Now I just have to work out how to apply the patch (and find time to) and
> then perhaps to post a pull request to the banshee repo for it (assuming it
> does the job).
>
> Regards,
>
> Bernd.
>
> Nicholas Little via banshee-list wrote:
>
> Hi Bernd,
>
> That's some nice shell foo. In configure.ac you'll find:
>
> SHAMROCK_CHECK_MONO_2_0_GAC_ASSEMBLIES([
> Mono.Posix
> ICSharpCode.SharpZipLib
> ])
>
> You'll probably have to do some hacking around in the build subtree,
> which contains all the macros used by autotools, in order to get it to
> work - specifically take a look at
> https://github.com/GNOME/banshee/blob/master/build/m4/shamrock/mono.m4
>
> We could probably look at updating some of these dependencies as I
> think some distributions are dropping Banshee through build
> difficulties - Gentoo appears to be anyway so feel free to share a
> patch when you get up and running.
>
> Good luck.
>
> Yours,
> Nicholas
>
> On 29 May 2017 at 01:53, Bernd Wechner [hidden email] wrote:
>> Thought I'd try building Banshee again almost 18 months after first
>> effort.
>> First efforts failed primarily because Mint was based on a dated release
>> fo
>> Ubuntu at the time , but it's up to date now and has been for a while so I
>> thought to give it a crack. So I followed the directions here:
>>
>> http://banshee.fm/download/development/
>>
>> under Ubuntu. And all is well until I run autogen.sh which bails with:
>>
>> checking for Mono 2.0 GAC for Mono.Posix.dll... not found
>> configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll
>> Error: There were errors when running './configure', a step that is
>> required
>> to configure banshee
>>
>> Go figure! I'd have thought that was well covered by all the prerequisites
>> listed, and I've installed MonoDevelop and Mono from the package
>> mono-complete from the Ubuntu repositories (labelled as Complete mono
>> runtime, development tools and all libraries) but no luck. If I "locate
>> Mono.Posix" telling results are:
>>
>> /usr/lib/mono/4.5/Mono.Posix.dll
>> /usr/lib/mono/gac/Mono.Posix
>> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756
>> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756/Mono.Posix.dll
>>
>> To wit Mono.Posix.dll is installed, but autogen.sh isn't finding it.
>> Perhaps
>> some environment variable or other is what it wants, if it's too blind to
>> find it alone. What is going on and why (again) is Banshee apparently not
>> so
>> simple to build? After all the clear effort that's gone into Ubuntu
>> support
>> on that development page and more?
>>
>> Anyhow:
>>
>> bash -x autogen.sh
>>
>> reveals that ./configure is what's bailing. And:
>>
>> bash -x configure
>>
>> in turn reveals that this is what's failing:
>>
>> + test -e /usr/lib/mono/2.0/Mono.Posix.dll -o -e
>> /usr/lib/mono/2.0/Mono.Posix.dll
>>
>> And voila, I have Mono 4.5 not 2.0.
>>
>> So, that begs the obvious questions:
>>
>> 1) Does banshee really depend on a dated version of Mono? (a version
>> superceded in 2009!)
>> 2) Can I install a dated version of Mono? And if so, how?
>> 3) Can such a dated version of Mono exist in parallel with the latest
>> version without causing hassles elsewhere?
>>
>> Puzzled, and appreciating any insights.
>>
>> Kind regards,
>>
>> Bernd.
>>
>>
>> _______________________________________________
>> banshee-list mailing list
>> [hidden email]
>> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>
>
>
>
>
> _______________________________________________
> banshee-list mailing list
> [hidden email]
> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)

Re: Trouble Building Banshee on Linux Mint (Again)

It might make more sense to just fork the whole project and host it
elsewhere. The existing Banshee maintainers seem to have flown the coop,
and the GNOME folks have their own music players (GNOME Music and
Rhythmbox) that they are understandably more interested in.

Nate

On 06/10/2017 06:33 PM, Bernd Wechner wrote:

> Nicholas,
>
> Can you point me to your forked repo? I just forked one here:
>
> https://github.com/bernd-wechner/banshee>
> perhaps you can send me a pull request for the patched files and I'll
> get rolling ...
>
> I wonder who "they" is that don't accept PRs and if banshee is a
> community driven project? Just curious. Because you're right the GNOME repo:
>
> https://github.com/GNOME/banshee/pulls?q=is%3Apr+is%3Aclosed>
> has only 4 PRs ever and the history suggests it's been on Github since 2006:
>
> https://github.com/GNOME/banshee/graphs/code-frequency>
> and sit seems the PR is a standard way of capitalising on community
> contribs. Of course triaging and merging them is work someone has to do,
> but then PRs aren't PRs, some might be onerous and others trivial
> patches like this ... ;-).
>
> Regards,
>
> Bernd.
>
> Nicholas Little via banshee-list wrote:
>> Nice find, cheers.
>>
>> I'm not sure I'd bother with the pull request, last time I checked
>> they didn't accept them - you're better off commenting on the bugzilla
>> entry so that the maintainers get a notification.
>>
>> I've tested that patch and it works for me. As in, I can autoreconf,
>> configure and make and the program doesn't crash :)
>>
>> The only thing missing from that patch is the update to the mono.m4
>> within the Hyena submodule for completeness but that's just
>> duplication of what's already shown for the main one - I've added that
>> in the patches I pushed this morning to my forked respositories.
>>
>> FYI use 'git apply' for patches that look like that.
>>
>> On 5 June 2017 at 08:23, Bernd Wechner<[hidden email]> wrote:
>> > Actually I just found a fix someone else did:
>> >
>> > https://bugzilla.gnome.org/show_bug.cgi?id=753091>> >
>> > He posted a patch:
>> >
>> > https://bug753091.bugzilla-attachments.gnome.org/attachment.cgi?id=308515>> >
>> > Now I just have to work out how to apply the patch (and find time to) and
>> > then perhaps to post a pull request to the banshee repo for it (assuming it
>> > does the job).
>> >
>> > Regards,
>> >
>> > Bernd.
>> >
>> > Nicholas Little via banshee-list wrote:
>> >
>> > Hi Bernd,
>> >
>> > That's some nice shell foo. In configure.ac you'll find:
>> >
>> > SHAMROCK_CHECK_MONO_2_0_GAC_ASSEMBLIES([
>> > Mono.Posix
>> > ICSharpCode.SharpZipLib
>> > ])
>> >
>> > You'll probably have to do some hacking around in the build subtree,
>> > which contains all the macros used by autotools, in order to get it to
>> > work - specifically take a look at
>> > https://github.com/GNOME/banshee/blob/master/build/m4/shamrock/mono.m4>> >
>> > We could probably look at updating some of these dependencies as I
>> > think some distributions are dropping Banshee through build
>> > difficulties - Gentoo appears to be anyway so feel free to share a
>> > patch when you get up and running.
>> >
>> > Good luck.
>> >
>> > Yours,
>> > Nicholas
>> >
>> > On 29 May 2017 at 01:53, Bernd Wechner <[hidden email]> wrote:
>> >> Thought I'd try building Banshee again almost 18 months after first
>> >> effort.
>> >> First efforts failed primarily because Mint was based on a dated release
>> >> fo
>> >> Ubuntu at the time , but it's up to date now and has been for a while so I
>> >> thought to give it a crack. So I followed the directions here:
>> >>
>> >> http://banshee.fm/download/development/>> >>
>> >> under Ubuntu. And all is well until I run autogen.sh which bails with:
>> >>
>> >> checking for Mono 2.0 GAC for Mono.Posix.dll... not found
>> >> configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll
>> >> Error: There were errors when running './configure', a step that is
>> >> required
>> >> to configure banshee
>> >>
>> >> Go figure! I'd have thought that was well covered by all the prerequisites
>> >> listed, and I've installed MonoDevelop and Mono from the package
>> >> mono-complete from the Ubuntu repositories (labelled as Complete mono
>> >> runtime, development tools and all libraries) but no luck. If I "locate
>> >> Mono.Posix" telling results are:
>> >>
>> >> /usr/lib/mono/4.5/Mono.Posix.dll
>> >> /usr/lib/mono/gac/Mono.Posix
>> >> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756
>> >> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756/Mono.Posix.dll
>> >>
>> >> To wit Mono.Posix.dll is installed, but autogen.sh isn't finding it.
>> >> Perhaps
>> >> some environment variable or other is what it wants, if it's too blind to
>> >> find it alone. What is going on and why (again) is Banshee apparently not
>> >> so
>> >> simple to build? After all the clear effort that's gone into Ubuntu
>> >> support
>> >> on that development page and more?
>> >>
>> >> Anyhow:
>> >>
>> >> bash -x autogen.sh
>> >>
>> >> reveals that ./configure is what's bailing. And:
>> >>
>> >> bash -x configure
>> >>
>> >> in turn reveals that this is what's failing:
>> >>
>> >> + test -e /usr/lib/mono/2.0/Mono.Posix.dll -o -e
>> >> /usr/lib/mono/2.0/Mono.Posix.dll
>> >>
>> >> And voila, I have Mono 4.5 not 2.0.
>> >>
>> >> So, that begs the obvious questions:
>> >>
>> >> 1) Does banshee really depend on a dated version of Mono? (a version
>> >> superceded in 2009!)
>> >> 2) Can I install a dated version of Mono? And if so, how?
>> >> 3) Can such a dated version of Mono exist in parallel with the latest
>> >> version without causing hassles elsewhere?
>> >>
>> >> Puzzled, and appreciating any insights.
>> >>
>> >> Kind regards,
>> >>
>> >> Bernd.
>> >>
>> >>
>> >> _______________________________________________
>> >> banshee-list mailing list
>> >> [hidden email]>> >> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > banshee-list mailing list
>> > [hidden email]>> > https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>>
>>
>>
>
>
>
> _______________________________________________
> banshee-list mailing list
> [hidden email]> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>

Re: Trouble Building Banshee on Linux Mint (Again)

Hmmm, so what I'm hearing is Banshee is
effectively dead and it's better to move to Gnome music?

Just checked it briefly. I'm actually rather agnostic. I want a
living project and am proficient in C# and Python and want
something that builds that I can work on and hopefully has a
future a living future and doesn't die or decline into the abyss
of wasted effort ;-).

What puzzles me is how and why devs fly the coop en masse without
succession planning, handing over control of the repo to folk they
identify as willing and able to do that! Would seem a natural
desire to not see the stuff you've been working on, but now
haven't time for anymore, carry on living and growing and not
stagnating!

Regards,

Bernd.

Nate Graham wrote:

I found the same thing with an approved patch I sent in 7 months ago:
https://bugzilla.gnome.org/show_bug.cgi?id=774478
Still just sitting there.
It might make more sense to just fork the whole project and host it
elsewhere. The existing Banshee maintainers seem to have flown the coop,
and the GNOME folks have their own music players (GNOME Music and
Rhythmbox) that they are understandably more interested in.
Nate
On 06/10/2017 06:33 PM, Bernd Wechner wrote:
> Nicholas,
>
> Can you point me to your forked repo? I just forked one here:
>
> https://github.com/bernd-wechner/banshee
>
> perhaps you can send me a pull request for the patched files and I'll
> get rolling ...
>
> I wonder who "they" is that don't accept PRs and if banshee is a
> community driven project? Just curious. Because you're right the GNOME repo:
>
> https://github.com/GNOME/banshee/pulls?q=is%3Apr+is%3Aclosed
>
> has only 4 PRs ever and the history suggests it's been on Github since 2006:
>
> https://github.com/GNOME/banshee/graphs/code-frequency
>
> and sit seems the PR is a standard way of capitalising on community
> contribs. Of course triaging and merging them is work someone has to do,
> but then PRs aren't PRs, some might be onerous and others trivial
> patches like this ... ;-).
>
> Regards,
>
> Bernd.
>
> Nicholas Little via banshee-list wrote:
>> Nice find, cheers.
>>
>> I'm not sure I'd bother with the pull request, last time I checked
>> they didn't accept them - you're better off commenting on the bugzilla
>> entry so that the maintainers get a notification.
>>
>> I've tested that patch and it works for me. As in, I can autoreconf,
>> configure and make and the program doesn't crash :)
>>
>> The only thing missing from that patch is the update to the mono.m4
>> within the Hyena submodule for completeness but that's just
>> duplication of what's already shown for the main one - I've added that
>> in the patches I pushed this morning to my forked respositories.
>>
>> FYI use 'git apply' for patches that look like that.
>>
>> On 5 June 2017 at 08:23, Bernd Wechner[hidden email] wrote:
>> > Actually I just found a fix someone else did:
>> >
>> > https://bugzilla.gnome.org/show_bug.cgi?id=753091
>> >
>> > He posted a patch:
>> >
>> > https://bug753091.bugzilla-attachments.gnome.org/attachment.cgi?id=308515
>> >
>> > Now I just have to work out how to apply the patch (and find time to) and
>> > then perhaps to post a pull request to the banshee repo for it (assuming it
>> > does the job).
>> >
>> > Regards,
>> >
>> > Bernd.
>> >
>> > Nicholas Little via banshee-list wrote:
>> >
>> > Hi Bernd,
>> >
>> > That's some nice shell foo. In configure.ac you'll find:
>> >
>> > SHAMROCK_CHECK_MONO_2_0_GAC_ASSEMBLIES([
>> > Mono.Posix
>> > ICSharpCode.SharpZipLib
>> > ])
>> >
>> > You'll probably have to do some hacking around in the build subtree,
>> > which contains all the macros used by autotools, in order to get it to
>> > work - specifically take a look at
>> > https://github.com/GNOME/banshee/blob/master/build/m4/shamrock/mono.m4
>> >
>> > We could probably look at updating some of these dependencies as I
>> > think some distributions are dropping Banshee through build
>> > difficulties - Gentoo appears to be anyway so feel free to share a
>> > patch when you get up and running.
>> >
>> > Good luck.
>> >
>> > Yours,
>> > Nicholas
>> >
>> > On 29 May 2017 at 01:53, Bernd Wechner [hidden email] wrote:
>> >> Thought I'd try building Banshee again almost 18 months after first
>> >> effort.
>> >> First efforts failed primarily because Mint was based on a dated release
>> >> fo
>> >> Ubuntu at the time , but it's up to date now and has been for a while so I
>> >> thought to give it a crack. So I followed the directions here:
>> >>
>> >> http://banshee.fm/download/development/
>> >>
>> >> under Ubuntu. And all is well until I run autogen.sh which bails with:
>> >>
>> >> checking for Mono 2.0 GAC for Mono.Posix.dll... not found
>> >> configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll
>> >> Error: There were errors when running './configure', a step that is
>> >> required
>> >> to configure banshee
>> >>
>> >> Go figure! I'd have thought that was well covered by all the prerequisites
>> >> listed, and I've installed MonoDevelop and Mono from the package
>> >> mono-complete from the Ubuntu repositories (labelled as Complete mono
>> >> runtime, development tools and all libraries) but no luck. If I "locate
>> >> Mono.Posix" telling results are:
>> >>
>> >> /usr/lib/mono/4.5/Mono.Posix.dll
>> >> /usr/lib/mono/gac/Mono.Posix
>> >> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756
>> >> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756/Mono.Posix.dll
>> >>
>> >> To wit Mono.Posix.dll is installed, but autogen.sh isn't finding it.
>> >> Perhaps
>> >> some environment variable or other is what it wants, if it's too blind to
>> >> find it alone. What is going on and why (again) is Banshee apparently not
>> >> so
>> >> simple to build? After all the clear effort that's gone into Ubuntu
>> >> support
>> >> on that development page and more?
>> >>
>> >> Anyhow:
>> >>
>> >> bash -x autogen.sh
>> >>
>> >> reveals that ./configure is what's bailing. And:
>> >>
>> >> bash -x configure
>> >>
>> >> in turn reveals that this is what's failing:
>> >>
>> >> + test -e /usr/lib/mono/2.0/Mono.Posix.dll -o -e
>> >> /usr/lib/mono/2.0/Mono.Posix.dll
>> >>
>> >> And voila, I have Mono 4.5 not 2.0.
>> >>
>> >> So, that begs the obvious questions:
>> >>
>> >> 1) Does banshee really depend on a dated version of Mono? (a version
>> >> superceded in 2009!)
>> >> 2) Can I install a dated version of Mono? And if so, how?
>> >> 3) Can such a dated version of Mono exist in parallel with the latest
>> >> version without causing hassles elsewhere?
>> >>
>> >> Puzzled, and appreciating any insights.
>> >>
>> >> Kind regards,
>> >>
>> >> Bernd.
>> >>
>> >>
>> >> _______________________________________________
>> >> banshee-list mailing list
>> >> [hidden email]
>> >> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > banshee-list mailing list
>> > [hidden email]
>> > https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>>
>>
>>
>
>
>
> _______________________________________________
> banshee-list mailing list
> [hidden email]
> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>
_______________________________________________
banshee-list mailing list
[hidden email]https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)

Re: Trouble Building Banshee on Linux Mint (Again)

@Bernd, here it is: https://github.com/arfbtwn/banshee, for me to
create a pull request that will work in your fork you'll need to also
fork the Hyena library and repoint your git submodule file to it
(.gitmodules) which is what I've done on my master branch.

'They' are the approved Banshee maintainers, the guys who can push to
the main repository. People move on, it's just something we have to
accept in FOSS development, there could be any number of reasons for
not passing on the mantle to other community members, I don't think
that means it can't be picked up though. Ideally we can get
maintainership for one of us but I think that person would have to be
active on GIMPnet in #banshee too.

@Nate, I'm in the same boat with bugzilla reports, the point of the
Bugs, Features and Forks thread was really to try and pull us all
together and see if we can get some community development going on -
Banshee uses the Cathedral model so I hoped we could add some Bazaar
element since the Priests have moved on. Sadly I don't have a
Macintosh so I can't even comment on that BGO bug.

BTW, in my current feature/lite branch the album browser is available
again when running with the --classic switch even when using the
--enable-treeview build switch, just pushed that yesterday so might be
a little rough around the edges. Since the album browser now works
with treeview the initial intention is to include it in the lighter
interface controlled by a view button - think Nautilus' icon/list
selection popover - but I haven't gotten round to that yet.

I've tried migrating to GNOME music (I already moved from Rhythmbox to
Banshee) but it performs terribly on my system and I can't see a way
of managing my devices, I read somewhere I'm supposed to use a grilo
plugin but Banshee really excels at sync so I'm happy fixing it up and
making improvements where I can.

> Hmmm, so what I'm hearing is Banshee is effectively dead and it's better to
> move to Gnome music?
>
> Just checked it briefly. I'm actually rather agnostic. I want a living
> project and am proficient in C# and Python and want something that builds
> that I can work on and hopefully has a future a living future and doesn't
> die or decline into the abyss of wasted effort ;-).
>
> What puzzles me is how and why devs fly the coop en masse without succession
> planning, handing over control of the repo to folk they identify as willing
> and able to do that! Would seem a natural desire to not see the stuff you've
> been working on, but now haven't time for anymore, carry on living and
> growing and not stagnating!
>
> Regards,
>
> Bernd.
>
> Nate Graham wrote:
>
> I found the same thing with an approved patch I sent in 7 months ago:
> https://bugzilla.gnome.org/show_bug.cgi?id=774478>
> Still just sitting there.
>
> It might make more sense to just fork the whole project and host it
> elsewhere. The existing Banshee maintainers seem to have flown the coop,
> and the GNOME folks have their own music players (GNOME Music and
> Rhythmbox) that they are understandably more interested in.
>
> Nate
>
>
> On 06/10/2017 06:33 PM, Bernd Wechner wrote:
>> Nicholas,
>>
>> Can you point me to your forked repo? I just forked one here:
>>
>> https://github.com/bernd-wechner/banshee>>
>> perhaps you can send me a pull request for the patched files and I'll
>> get rolling ...
>>
>> I wonder who "they" is that don't accept PRs and if banshee is a
>> community driven project? Just curious. Because you're right the GNOME
>> repo:
>>
>> https://github.com/GNOME/banshee/pulls?q=is%3Apr+is%3Aclosed>>
>> has only 4 PRs ever and the history suggests it's been on Github since
>> 2006:
>>
>> https://github.com/GNOME/banshee/graphs/code-frequency>>
>> and sit seems the PR is a standard way of capitalising on community
>> contribs. Of course triaging and merging them is work someone has to do,
>> but then PRs aren't PRs, some might be onerous and others trivial
>> patches like this ... ;-).
>>
>> Regards,
>>
>> Bernd.
>>
>> Nicholas Little via banshee-list wrote:
>>> Nice find, cheers.
>>>
>>> I'm not sure I'd bother with the pull request, last time I checked
>>> they didn't accept them - you're better off commenting on the bugzilla
>>> entry so that the maintainers get a notification.
>>>
>>> I've tested that patch and it works for me. As in, I can autoreconf,
>>> configure and make and the program doesn't crash :)
>>>
>>> The only thing missing from that patch is the update to the mono.m4
>>> within the Hyena submodule for completeness but that's just
>>> duplication of what's already shown for the main one - I've added that
>>> in the patches I pushed this morning to my forked respositories.
>>>
>>> FYI use 'git apply' for patches that look like that.
>>>
>>> On 5 June 2017 at 08:23, Bernd Wechner<[hidden email]> wrote:
>>> > Actually I just found a fix someone else did:
>>> >
>>> > https://bugzilla.gnome.org/show_bug.cgi?id=753091>>> >
>>> > He posted a patch:
>>> >
>>> >
>>> > https://bug753091.bugzilla-attachments.gnome.org/attachment.cgi?id=308515>>> >
>>> > Now I just have to work out how to apply the patch (and find time to)
>>> > and
>>> > then perhaps to post a pull request to the banshee repo for it
>>> > (assuming it
>>> > does the job).
>>> >
>>> > Regards,
>>> >
>>> > Bernd.
>>> >
>>> > Nicholas Little via banshee-list wrote:
>>> >
>>> > Hi Bernd,
>>> >
>>> > That's some nice shell foo. In configure.ac you'll find:
>>> >
>>> > SHAMROCK_CHECK_MONO_2_0_GAC_ASSEMBLIES([
>>> > Mono.Posix
>>> > ICSharpCode.SharpZipLib
>>> > ])
>>> >
>>> > You'll probably have to do some hacking around in the build subtree,
>>> > which contains all the macros used by autotools, in order to get it to
>>> > work - specifically take a look at
>>> > https://github.com/GNOME/banshee/blob/master/build/m4/shamrock/mono.m4>>> >
>>> > We could probably look at updating some of these dependencies as I
>>> > think some distributions are dropping Banshee through build
>>> > difficulties - Gentoo appears to be anyway so feel free to share a
>>> > patch when you get up and running.
>>> >
>>> > Good luck.
>>> >
>>> > Yours,
>>> > Nicholas
>>> >
>>> > On 29 May 2017 at 01:53, Bernd Wechner <[hidden email]>
>>> > wrote:
>>> >> Thought I'd try building Banshee again almost 18 months after first
>>> >> effort.
>>> >> First efforts failed primarily because Mint was based on a dated
>>> >> release
>>> >> fo
>>> >> Ubuntu at the time , but it's up to date now and has been for a while
>>> >> so I
>>> >> thought to give it a crack. So I followed the directions here:
>>> >>
>>> >> http://banshee.fm/download/development/>>> >>
>>> >> under Ubuntu. And all is well until I run autogen.sh which bails with:
>>> >>
>>> >> checking for Mono 2.0 GAC for Mono.Posix.dll... not found
>>> >> configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll
>>> >> Error: There were errors when running './configure', a step that is
>>> >> required
>>> >> to configure banshee
>>> >>
>>> >> Go figure! I'd have thought that was well covered by all the
>>> >> prerequisites
>>> >> listed, and I've installed MonoDevelop and Mono from the package
>>> >> mono-complete from the Ubuntu repositories (labelled as Complete mono
>>> >> runtime, development tools and all libraries) but no luck. If I
>>> >> "locate
>>> >> Mono.Posix" telling results are:
>>> >>
>>> >> /usr/lib/mono/4.5/Mono.Posix.dll
>>> >> /usr/lib/mono/gac/Mono.Posix
>>> >> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756
>>> >> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756/Mono.Posix.dll
>>> >>
>>> >> To wit Mono.Posix.dll is installed, but autogen.sh isn't finding it.
>>> >> Perhaps
>>> >> some environment variable or other is what it wants, if it's too blind
>>> >> to
>>> >> find it alone. What is going on and why (again) is Banshee apparently
>>> >> not
>>> >> so
>>> >> simple to build? After all the clear effort that's gone into Ubuntu
>>> >> support
>>> >> on that development page and more?
>>> >>
>>> >> Anyhow:
>>> >>
>>> >> bash -x autogen.sh
>>> >>
>>> >> reveals that ./configure is what's bailing. And:
>>> >>
>>> >> bash -x configure
>>> >>
>>> >> in turn reveals that this is what's failing:
>>> >>
>>> >> + test -e /usr/lib/mono/2.0/Mono.Posix.dll -o -e
>>> >> /usr/lib/mono/2.0/Mono.Posix.dll
>>> >>
>>> >> And voila, I have Mono 4.5 not 2.0.
>>> >>
>>> >> So, that begs the obvious questions:
>>> >>
>>> >> 1) Does banshee really depend on a dated version of Mono? (a version
>>> >> superceded in 2009!)
>>> >> 2) Can I install a dated version of Mono? And if so, how?
>>> >> 3) Can such a dated version of Mono exist in parallel with the latest
>>> >> version without causing hassles elsewhere?
>>> >>
>>> >> Puzzled, and appreciating any insights.
>>> >>
>>> >> Kind regards,
>>> >>
>>> >> Bernd.
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> banshee-list mailing list
>>> >> [hidden email]>>> >> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe
>>> >> here)
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > banshee-list mailing list
>>> > [hidden email]>>> > https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe
>>> > here)
>>>
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> banshee-list mailing list
>> [hidden email]>> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>>
>
> _______________________________________________
> banshee-list mailing list
> [hidden email]> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>
>
>
> _______________________________________________
> banshee-list mailing list
> [hidden email]> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)

> @Bernd, here it is: https://github.com/arfbtwn/banshee, for me to
> create a pull request that will work in your fork you'll need to also
> fork the Hyena library and repoint your git submodule file to it
> (.gitmodules) which is what I've done on my master branch.
>
> In the meantime I've created clean versions that apply to
> gnome/banshee's master branch though, those are here
> https://github.com/arfbtwn/banshee/commit/cb40308dd9fed4956fa96ce803a3e390a7e0d6dd> and for Hyena here
> https://github.com/arfbtwn/hyena/commit/52f635cfdd5f9e7f4a5a1f1b54977126f1c70378,
> if you add my banshee repository to your remotes and my hyena
> repository to the submodule remotes then you'll be able to fetch and
> merge them straight into whatever branch you're working on.
>
> 'They' are the approved Banshee maintainers, the guys who can push to
> the main repository. People move on, it's just something we have to
> accept in FOSS development, there could be any number of reasons for
> not passing on the mantle to other community members, I don't think
> that means it can't be picked up though. Ideally we can get
> maintainership for one of us but I think that person would have to be
> active on GIMPnet in #banshee too.
>
> @Nate, I'm in the same boat with bugzilla reports, the point of the
> Bugs, Features and Forks thread was really to try and pull us all
> together and see if we can get some community development going on -
> Banshee uses the Cathedral model so I hoped we could add some Bazaar
> element since the Priests have moved on. Sadly I don't have a
> Macintosh so I can't even comment on that BGO bug.
>
> BTW, in my current feature/lite branch the album browser is available
> again when running with the --classic switch even when using the
> --enable-treeview build switch, just pushed that yesterday so might be
> a little rough around the edges. Since the album browser now works
> with treeview the initial intention is to include it in the lighter
> interface controlled by a view button - think Nautilus' icon/list
> selection popover - but I haven't gotten round to that yet.
>
> I've tried migrating to GNOME music (I already moved from Rhythmbox to
> Banshee) but it performs terribly on my system and I can't see a way
> of managing my devices, I read somewhere I'm supposed to use a grilo
> plugin but Banshee really excels at sync so I'm happy fixing it up and
> making improvements where I can.
>
> On 11 June 2017 at 03:30, Bernd Wechner <[hidden email]> wrote:
>> Hmmm, so what I'm hearing is Banshee is effectively dead and it's better to
>> move to Gnome music?
>>
>> Just checked it briefly. I'm actually rather agnostic. I want a living
>> project and am proficient in C# and Python and want something that builds
>> that I can work on and hopefully has a future a living future and doesn't
>> die or decline into the abyss of wasted effort ;-).
>>
>> What puzzles me is how and why devs fly the coop en masse without succession
>> planning, handing over control of the repo to folk they identify as willing
>> and able to do that! Would seem a natural desire to not see the stuff you've
>> been working on, but now haven't time for anymore, carry on living and
>> growing and not stagnating!
>>
>> Regards,
>>
>> Bernd.
>>
>> Nate Graham wrote:
>>
>> I found the same thing with an approved patch I sent in 7 months ago:
>> https://bugzilla.gnome.org/show_bug.cgi?id=774478>>
>> Still just sitting there.
>>
>> It might make more sense to just fork the whole project and host it
>> elsewhere. The existing Banshee maintainers seem to have flown the coop,
>> and the GNOME folks have their own music players (GNOME Music and
>> Rhythmbox) that they are understandably more interested in.
>>
>> Nate
>>
>>
>> On 06/10/2017 06:33 PM, Bernd Wechner wrote:
>>> Nicholas,
>>>
>>> Can you point me to your forked repo? I just forked one here:
>>>
>>> https://github.com/bernd-wechner/banshee>>>
>>> perhaps you can send me a pull request for the patched files and I'll
>>> get rolling ...
>>>
>>> I wonder who "they" is that don't accept PRs and if banshee is a
>>> community driven project? Just curious. Because you're right the GNOME
>>> repo:
>>>
>>> https://github.com/GNOME/banshee/pulls?q=is%3Apr+is%3Aclosed>>>
>>> has only 4 PRs ever and the history suggests it's been on Github since
>>> 2006:
>>>
>>> https://github.com/GNOME/banshee/graphs/code-frequency>>>
>>> and sit seems the PR is a standard way of capitalising on community
>>> contribs. Of course triaging and merging them is work someone has to do,
>>> but then PRs aren't PRs, some might be onerous and others trivial
>>> patches like this ... ;-).
>>>
>>> Regards,
>>>
>>> Bernd.
>>>
>>> Nicholas Little via banshee-list wrote:
>>>> Nice find, cheers.
>>>>
>>>> I'm not sure I'd bother with the pull request, last time I checked
>>>> they didn't accept them - you're better off commenting on the bugzilla
>>>> entry so that the maintainers get a notification.
>>>>
>>>> I've tested that patch and it works for me. As in, I can autoreconf,
>>>> configure and make and the program doesn't crash :)
>>>>
>>>> The only thing missing from that patch is the update to the mono.m4
>>>> within the Hyena submodule for completeness but that's just
>>>> duplication of what's already shown for the main one - I've added that
>>>> in the patches I pushed this morning to my forked respositories.
>>>>
>>>> FYI use 'git apply' for patches that look like that.
>>>>
>>>> On 5 June 2017 at 08:23, Bernd Wechner<[hidden email]> wrote:
>>>> > Actually I just found a fix someone else did:
>>>> >
>>>> > https://bugzilla.gnome.org/show_bug.cgi?id=753091>>>> >
>>>> > He posted a patch:
>>>> >
>>>> >
>>>> > https://bug753091.bugzilla-attachments.gnome.org/attachment.cgi?id=308515>>>> >
>>>> > Now I just have to work out how to apply the patch (and find time to)
>>>> > and
>>>> > then perhaps to post a pull request to the banshee repo for it
>>>> > (assuming it
>>>> > does the job).
>>>> >
>>>> > Regards,
>>>> >
>>>> > Bernd.
>>>> >
>>>> > Nicholas Little via banshee-list wrote:
>>>> >
>>>> > Hi Bernd,
>>>> >
>>>> > That's some nice shell foo. In configure.ac you'll find:
>>>> >
>>>> > SHAMROCK_CHECK_MONO_2_0_GAC_ASSEMBLIES([
>>>> > Mono.Posix
>>>> > ICSharpCode.SharpZipLib
>>>> > ])
>>>> >
>>>> > You'll probably have to do some hacking around in the build subtree,
>>>> > which contains all the macros used by autotools, in order to get it to
>>>> > work - specifically take a look at
>>>> > https://github.com/GNOME/banshee/blob/master/build/m4/shamrock/mono.m4>>>> >
>>>> > We could probably look at updating some of these dependencies as I
>>>> > think some distributions are dropping Banshee through build
>>>> > difficulties - Gentoo appears to be anyway so feel free to share a
>>>> > patch when you get up and running.
>>>> >
>>>> > Good luck.
>>>> >
>>>> > Yours,
>>>> > Nicholas
>>>> >
>>>> > On 29 May 2017 at 01:53, Bernd Wechner <[hidden email]>
>>>> > wrote:
>>>> >> Thought I'd try building Banshee again almost 18 months after first
>>>> >> effort.
>>>> >> First efforts failed primarily because Mint was based on a dated
>>>> >> release
>>>> >> fo
>>>> >> Ubuntu at the time , but it's up to date now and has been for a while
>>>> >> so I
>>>> >> thought to give it a crack. So I followed the directions here:
>>>> >>
>>>> >> http://banshee.fm/download/development/>>>> >>
>>>> >> under Ubuntu. And all is well until I run autogen.sh which bails with:
>>>> >>
>>>> >> checking for Mono 2.0 GAC for Mono.Posix.dll... not found
>>>> >> configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll
>>>> >> Error: There were errors when running './configure', a step that is
>>>> >> required
>>>> >> to configure banshee
>>>> >>
>>>> >> Go figure! I'd have thought that was well covered by all the
>>>> >> prerequisites
>>>> >> listed, and I've installed MonoDevelop and Mono from the package
>>>> >> mono-complete from the Ubuntu repositories (labelled as Complete mono
>>>> >> runtime, development tools and all libraries) but no luck. If I
>>>> >> "locate
>>>> >> Mono.Posix" telling results are:
>>>> >>
>>>> >> /usr/lib/mono/4.5/Mono.Posix.dll
>>>> >> /usr/lib/mono/gac/Mono.Posix
>>>> >> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756
>>>> >> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756/Mono.Posix.dll
>>>> >>
>>>> >> To wit Mono.Posix.dll is installed, but autogen.sh isn't finding it.
>>>> >> Perhaps
>>>> >> some environment variable or other is what it wants, if it's too blind
>>>> >> to
>>>> >> find it alone. What is going on and why (again) is Banshee apparently
>>>> >> not
>>>> >> so
>>>> >> simple to build? After all the clear effort that's gone into Ubuntu
>>>> >> support
>>>> >> on that development page and more?
>>>> >>
>>>> >> Anyhow:
>>>> >>
>>>> >> bash -x autogen.sh
>>>> >>
>>>> >> reveals that ./configure is what's bailing. And:
>>>> >>
>>>> >> bash -x configure
>>>> >>
>>>> >> in turn reveals that this is what's failing:
>>>> >>
>>>> >> + test -e /usr/lib/mono/2.0/Mono.Posix.dll -o -e
>>>> >> /usr/lib/mono/2.0/Mono.Posix.dll
>>>> >>
>>>> >> And voila, I have Mono 4.5 not 2.0.
>>>> >>
>>>> >> So, that begs the obvious questions:
>>>> >>
>>>> >> 1) Does banshee really depend on a dated version of Mono? (a version
>>>> >> superceded in 2009!)
>>>> >> 2) Can I install a dated version of Mono? And if so, how?
>>>> >> 3) Can such a dated version of Mono exist in parallel with the latest
>>>> >> version without causing hassles elsewhere?
>>>> >>
>>>> >> Puzzled, and appreciating any insights.
>>>> >>
>>>> >> Kind regards,
>>>> >>
>>>> >> Bernd.
>>>> >>
>>>> >>
>>>> >> _______________________________________________
>>>> >> banshee-list mailing list
>>>> >> [hidden email]>>>> >> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe
>>>> >> here)
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > banshee-list mailing list
>>>> > [hidden email]>>>> > https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe
>>>> > here)
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> banshee-list mailing list
>>> [hidden email]>>> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>>>
>>
>> _______________________________________________
>> banshee-list mailing list
>> [hidden email]>> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>>
>>
>>
>> _______________________________________________
>> banshee-list mailing list
>> [hidden email]>> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>
>
>
> --
> Registered Linux User #392373

Re: Trouble Building Banshee on Linux Mint (Again)

It 's odd, isn't it? Personally, I strongly prefer Banshee to GNOME
Music and wouldn't switch. But I have switched to Lollypop, which is
excellent and actively developed (in Python!) by a very enthusiastic and
responsive developer.

Re: Trouble Building Banshee on Linux Mint (Again)

Yeah bit odd but the thing to remember is that They are just users like us and it isn't practical to build and manually test all the patches they review so the system works on a 'squeeky cog' basis, getting other users to test patches and comment on the BGO reports we raise is the best way to get things merged - even just one more person is usually enough, I remember having luck commenting on some of @IBBoard's BGO reports.

Lollipop looks good, shame about the language, although I should probably have learnt Python by now...

It 's odd, isn't it? Personally, I strongly prefer Banshee to GNOME Music and wouldn't switch. But I have switched to Lollypop, which is excellent and actively developed (in Python!) by a very enthusiastic and responsive developer.

Hmmm, so what I'm hearing is Banshee is effectively dead and it's better to move to Gnome music?

Just checked it briefly. I'm actually rather agnostic. I want a living project and am proficient in C# and Python and want something that builds that I can work on and hopefully has a future a living future and doesn't die or decline into the abyss of wasted effort ;-).

What puzzles me is how and why devs fly the coop en masse without succession planning, handing over control of the repo to folk they identify as willing and able to do that! Would seem a natural desire to not see the stuff you've been working on, but now haven't time for anymore, carry on living and growing and not stagnating!

It might make more sense to just fork the whole project and host it
elsewhere. The existing Banshee maintainers seem to have flown the coop,
and the GNOME folks have their own music players (GNOME Music and
Rhythmbox) that they are understandably more interested in.

Nate

On 06/10/2017 06:33 PM, Bernd Wechner wrote:
> Nicholas,
> > Can you point me to your forked repo? I just forked one here:
> > https://github.com/bernd-wechner/banshee
> > perhaps you can send me a pull request for the patched files and I'll > get rolling ...
> > I wonder who "they" is that don't accept PRs and if banshee is a > community driven project? Just curious. Because you're right the GNOME repo:
> > https://github.com/GNOME/banshee/pulls?q=is%3Apr+is%3Aclosed
> > has only 4 PRs ever and the history suggests it's been on Github since 2006:
> > https://github.com/GNOME/banshee/graphs/code-frequency
> > and sit seems the PR is a standard way of capitalising on community > contribs. Of course triaging and merging them is work someone has to do, > but then PRs aren't PRs, some might be onerous and others trivial > patches like this ... ;-).
> > Regards,
> > Bernd.
> > Nicholas Little via banshee-list wrote:
>> Nice find, cheers.
>>
>> I'm not sure I'd bother with the pull request, last time I checked
>> they didn't accept them - you're better off commenting on the bugzilla
>> entry so that the maintainers get a notification.
>>
>> I've tested that patch and it works for me. As in, I can autoreconf,
>> configure and make and the program doesn't crash :)
>>
>> The only thing missing from that patch is the update to the mono.m4
>> within the Hyena submodule for completeness but that's just
>> duplication of what's already shown for the main one - I've added that
>> in the patches I pushed this morning to my forked respositories.
>>
>> FYI use 'git apply' for patches that look like that.
>>
>> On 5 June 2017 at 08:23, Bernd Wechner<[hidden email]> wrote:
>> > Actually I just found a fix someone else did:
>> >
>> > https://bugzilla.gnome.org/show_bug.cgi?id=753091
>> >
>> > He posted a patch:
>> >
>> > https://bug753091.bugzilla-attachments.gnome.org/attachment.cgi?id=308515
>> >
>> > Now I just have to work out how to apply the patch (and find time to) and
>> > then perhaps to post a pull request to the banshee repo for it (assuming it
>> > does the job).
>> >
>> > Regards,
>> >
>> > Bernd.
>> >
>> > Nicholas Little via banshee-list wrote:
>> >
>> > Hi Bernd,
>> >
>> > That's some nice shell foo. In configure.ac you'll find:
>> >
>> > SHAMROCK_CHECK_MONO_2_0_GAC_ASSEMBLIES([
>> > Mono.Posix
>> > ICSharpCode.SharpZipLib
>> > ])
>> >
>> > You'll probably have to do some hacking around in the build subtree,
>> > which contains all the macros used by autotools, in order to get it to
>> > work - specifically take a look at
>> > https://github.com/GNOME/banshee/blob/master/build/m4/shamrock/mono.m4
>> >
>> > We could probably look at updating some of these dependencies as I
>> > think some distributions are dropping Banshee through build
>> > difficulties - Gentoo appears to be anyway so feel free to share a
>> > patch when you get up and running.
>> >
>> > Good luck.
>> >
>> > Yours,
>> > Nicholas
>> >
>> > On 29 May 2017 at 01:53, Bernd Wechner <[hidden email]> wrote:
>> >> Thought I'd try building Banshee again almost 18 months after first
>> >> effort.
>> >> First efforts failed primarily because Mint was based on a dated release
>> >> fo
>> >> Ubuntu at the time , but it's up to date now and has been for a while so I
>> >> thought to give it a crack. So I followed the directions here:
>> >>
>> >> http://banshee.fm/download/development/
>> >>
>> >> under Ubuntu. And all is well until I run autogen.sh which bails with:
>> >>
>> >> checking for Mono 2.0 GAC for Mono.Posix.dll... not found
>> >> configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll
>> >> Error: There were errors when running './configure', a step that is
>> >> required
>> >> to configure banshee
>> >>
>> >> Go figure! I'd have thought that was well covered by all the prerequisites
>> >> listed, and I've installed MonoDevelop and Mono from the package
>> >> mono-complete from the Ubuntu repositories (labelled as Complete mono
>> >> runtime, development tools and all libraries) but no luck. If I "locate
>> >> Mono.Posix" telling results are:
>> >>
>> >> /usr/lib/mono/4.5/Mono.Posix.dll
>> >> /usr/lib/mono/gac/Mono.Posix
>> >> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756
>> >> /usr/lib/mono/gac/Mono.Posix/4.0.0.0__0738eb9f132ed756/Mono.Posix.dll
>> >>
>> >> To wit Mono.Posix.dll is installed, but autogen.sh isn't finding it.
>> >> Perhaps
>> >> some environment variable or other is what it wants, if it's too blind to
>> >> find it alone. What is going on and why (again) is Banshee apparently not
>> >> so
>> >> simple to build? After all the clear effort that's gone into Ubuntu
>> >> support
>> >> on that development page and more?
>> >>
>> >> Anyhow:
>> >>
>> >> bash -x autogen.sh
>> >>
>> >> reveals that ./configure is what's bailing. And:
>> >>
>> >> bash -x configure
>> >>
>> >> in turn reveals that this is what's failing:
>> >>
>> >> + test -e /usr/lib/mono/2.0/Mono.Posix.dll -o -e
>> >> /usr/lib/mono/2.0/Mono.Posix.dll
>> >>
>> >> And voila, I have Mono 4.5 not 2.0.
>> >>
>> >> So, that begs the obvious questions:
>> >>
>> >> 1) Does banshee really depend on a dated version of Mono? (a version
>> >> superceded in 2009!)
>> >> 2) Can I install a dated version of Mono? And if so, how?
>> >> 3) Can such a dated version of Mono exist in parallel with the latest
>> >> version without causing hassles elsewhere?
>> >>
>> >> Puzzled, and appreciating any insights.
>> >>
>> >> Kind regards,
>> >>
>> >> Bernd.
>> >>
>> >>
>> >> _______________________________________________
>> >> banshee-list mailing list
>> >> [hidden email]
>> >> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > banshee-list mailing list
>> > [hidden email]
>> > https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>>
>>
>>
> > > > _______________________________________________
> banshee-list mailing list
> [hidden email]
> https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)
>
_______________________________________________
banshee-list mailing list[hidden email]https://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)