Bugzilla Bug 205210

media-sound/banshee-0.13.2 released on 8.1.08. 0.13.03 is supposed to be
released in 2 weeks ETA, would be sweet if someone would take this on!

Reproducible: Always

Steps to Reproduce:

Created an attachment (id=141609) [details]
same ebuild as 0.13.1

I've checked dependency, and they are the same as the one in 0.13.1, so I just
copied the ebuild. I test it and it works over here.

Salvo

(In reply to comment #1)

> 
> I've checked dependency, and they are the same as the one in 0.13.1, so I just
> copied the ebuild. I test it and it works over here.
> 

I'm not sure about that.

iPod support has a dependency with dev-dotnet/ipod-sharp-0.8.0 and
podsleuth-0.6.1. Both of them haven't any ebuild yet.

(In reply to comment #2)
> 
> I'm not sure about that.
> 
> iPod support has a dependency with dev-dotnet/ipod-sharp-0.8.0 and
> podsleuth-0.6.1. Both of them haven't any ebuild yet.
> 

True, I didn't test my ipod.
Where should I place the podsleuth ebuild? dev-dotnet?

I think that dev-dotnet is the best place. 

checking for GTKSHARP... yes
checking for SQLITE... yes
checking for IPODSHARP... no
checking for NJBSHARP... no
checking for LIBMTP... no
checking for KARMASHARP... no
checking for MONOZEROCONF... configure: error: Package requirements
(mono-zeroconf >= 0.7.2) were not met:

No package 'mono-zeroconf' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables MONOZEROCONF_CFLAGS
and MONOZEROCONF_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

My avahi version is 0.6.22-r1
Banshee 0.13.1 builds ok in my system (yet another missing dependency)?

dev-dotnet/mono-zeroconf, dev-dotnet/podsleuth and dev-dotnet/ipod-sharp needs
rekeywording.. and banshee itself

keyworded ~x86

The "boo" useflag was removed from the ebuild, so boo is now a required
dependency. But i don't think anything has changed upstream regarding this.

banshee 0.13.2 works alright on my system without boo.

(In reply to comment #8)
> The "boo" useflag was removed from the ebuild, so boo is now a required
> dependency. But i don't think anything has changed upstream regarding this.

True, nothing changed except ebuild. The old ebuild had invalid USE flag to
switch between internal and external boo, it was used anyway.

(In reply to comment #9)
I didn't see the internal boo, and thought the dependency was optional. I was
wrong.

The ebuild works great on my (x86) system. Thanks !

ppc, version 1.0.0 is out..

*** This bug has been marked as a duplicate of bug 233181 ***