Comments on: Some updates on the Banshee repositories… https://lizards.opensuse.org/2011/05/31/some-updates-on-the-banshee-repositories/ Blogs and Ramblings of the openSUSE Members Fri, 06 Mar 2020 17:50:09 +0000 hourly 1 https://wordpress.org/?v=4.7.5 By: nmarques https://lizards.opensuse.org/2011/05/31/some-updates-on-the-banshee-repositories/#comment-5504 Wed, 01 Jun 2011 17:02:16 +0000 http://lizards.opensuse.org/?p=7473#comment-5504 I’m not sure if that’s possible, I think that 11.4 only accepts critical bug fixes and no version updates. Either way, the users can subscribe the banshee repositories and have banshee updated to either 2.1.0 or 2.0.1.

]]> By: Atri https://lizards.opensuse.org/2011/05/31/some-updates-on-the-banshee-repositories/#comment-5503 Wed, 01 Jun 2011 02:27:27 +0000 http://lizards.opensuse.org/?p=7473#comment-5503 Might be worth pushing 2.0.1 as official update to openSUSE 11.4, seeing as it is only a bugfix release. Let me know if I could help out.

]]> By: nmarques https://lizards.opensuse.org/2011/05/31/some-updates-on-the-banshee-repositories/#comment-5501 Tue, 31 May 2011 16:07:43 +0000 http://lizards.opensuse.org/?p=7473#comment-5501 Hi,

We’re pushing 2.1.0 to Factory (in fact 11.4 was released with 1.9.5 if I’m not mistaken). So we’re not breaking anything. On Banshee repositories it’s flagged with ‘Available for build’, so it should really have any issues.

The renaming of the package is being taken care and it should be peaceful. OBS is a bit slow now (I assume it’s because of Factory rebuild).

NP, I think that by the end of the week we’ll have all repositories working ok and properly synched.

NM

]]> By: Andrés G. Aragoneses https://lizards.opensuse.org/2011/05/31/some-updates-on-the-banshee-repositories/#comment-5500 Tue, 31 May 2011 13:24:04 +0000 http://lizards.opensuse.org/?p=7473#comment-5500 Banshee dev here.

Please notice:
– ipod-sharp dependency was removed on version 2.1.0, not 2.0.1.
– rename of the launcher from “banshee-1” to “banshee” should actually have been included in stable (2.0.1) because the changes landed before the 2.0.0 tag.

Thanks for your work.

]]>