Please backport newer rhythmbox to dapper-backports

Bug #50477 reported by Baptiste
34
Affects Status Importance Assigned to Milestone
Dapper Backports
Invalid
Wishlist
Unassigned
rhythmbox (Ubuntu)
Invalid
Wishlist
Unassigned

Bug Description

It would be great to have the new version of rhythmbox, that corrects bugs and adds new functions.

Revision history for this message
Baptiste (baptiste2050-deactivatedaccount) wrote :

A part of the changelog may be find here : http://www.gnomefiles.org/app.php?soft_id=423

Revision history for this message
John Dong (jdong) wrote :

The version requested is currently not in Edgy.

 rhythmbox | 0.9.4.1-6 | unstable | source
 rhythmbox | 0.9.4.1-6+b1 | unstable | i386
 rhythmbox | 0.9.4.90-1 | experimental | source, i386
 rhythmbox | 0.9.3.1-0ubuntu9 | dapper | source, i386
 rhythmbox | 0.9.3.1-0ubuntu9 | edgy | source, i386

Changed in dapper-backports:
status: Unconfirmed → Rejected
Revision history for this message
Daniel T Chen (crimsun) wrote :

Not a bug in rhythmbox.

Changed in rhythmbox:
importance: Untriaged → Wishlist
status: Unconfirmed → Rejected
Revision history for this message
Daniel T Chen (crimsun) wrote :

Reopening (this source package makes no sense, however...). Legitimate backport request. The package is in Debian Sid now, so it will probably be merged when the Edgy build system stabilizes.

Changed in dapper-backports:
importance: Untriaged → Wishlist
status: Rejected → Confirmed
Revision history for this message
John Dong (jdong) wrote :

Marking as Needs Info until the new package is synced to Edgy.

Daniel, I typically use "Needs Info" in dapper-backports to represent a package that's a good request but awaiting a newer package in Ubuntu repositories.

I also set a bug on the Ubuntu source package as a way to say that a sync/upload/whatever-you-call-it has been requested by a user. I'm not sure how else to let developers know that...

I do continue to keep an eye out on madison-lite for the new uploads, and when I notice one, I'll close the ubuntu source package bug ticket if it hasn't been closed already.

If this is not an acceptable way of communicating with Ubuntu developers, please let me know and perhaps we can work out a better method.

Changed in dapper-backports:
status: Confirmed → Needs Info
Revision history for this message
John Dong (jdong) wrote :

0.9.5 uploaded to Edgy

Changed in dapper-backports:
status: Needs Info → Confirmed
Revision history for this message
John Dong (jdong) wrote : rhythmbox test backport

Built in a clean pbuilder, no source changes from Edgy.

Revision history for this message
John Dong (jdong) wrote : rhythmbox-dbg test backport

Built in a clean Dapper pbuilder, no source changes from Edgy.

Revision history for this message
John Dong (jdong) wrote :

I have built some testing debs from Edgy for Dapper. Please try them out and see if they work well.

If no problems are discovered, I'll send this off for inclusion in dapper-backports.

Revision history for this message
Mike Basinger (mike.basinger) wrote :

Working great for me. The only thing I have noticed is that the notificatiion bubble don't always show.

Revision history for this message
Pablo (pabloa) wrote :

Works fine for me.

The notification bubble only shows when Rhythmbox is hidden on the tray or on another workspace. I believe that it's expected behaviour.

Revision history for this message
Pablo (pabloa) wrote :

Whoops, just one thing.
The trayicon of Rhythmbox is not transparent. This was already fixed in the official Dapper's package (See #32173)

Revision history for this message
Ankit Jain (luckyankit) wrote :

Using it for last few days and its working fine.

Revision history for this message
Onkar Shinde (onkarshinde) wrote :

When will this package make to backports repository?

Revision history for this message
John Dong (jdong) wrote :

Alright, I'll have to check up on the regression of 32173 on Edgy's package, and we'll see from there.

Can anyone else confirm the transparency bug?

John Dong (jdong)
Changed in dapper-backports:
status: Confirmed → In Progress
Revision history for this message
Onkar Shinde (onkarshinde) wrote :

@John

Check Bug #53126 for transparency regression.

Revision history for this message
Onkar Shinde (onkarshinde) wrote :

Installed the backport yesterday. Working fine.
Search is faster. Haven't checked all the features.

Revision history for this message
Joe Pentland (jpentland) wrote :

umm, how hard will this be to fix, really?

I assume you talking about the border around a single icon not being transparent, yea?

Revision history for this message
Sebastien Bacher (seb128) wrote :

no, he's speaking about the notify area icon, the dapper package was patched for that

Revision history for this message
Alexandre Martani (amartani) wrote :

rhythmbox (0.9.5-1ubuntu3) edgy; urgency=low

  * debian/patches/16_transparency_for_notication_area_icon.patch:
    - make the icon on the notification area be transparent with the panel
      (Ubuntu: #53126)

Can be backported now?

Revision history for this message
Onkar Shinde (onkarshinde) wrote :

I don't know how many of you are facing this issue.
With current test backport, I can not edit tags of Vorbis/Ogg and FLAC files while I can edit tags of MP3 files.

Revision history for this message
Sebastien Bacher (seb128) wrote :

can you edit those tags with the dapper version? That's probably due to gstreamer0.10 not implementing those functions yet (or rhythmbox not using them) and likely to not be a regression of the new version

Revision history for this message
Onkar Shinde (onkarshinde) wrote :

I can not edit tags with dapper version for any type of file.
The backport version can edit tags for MP3.

Someone should check with edgy version.

Funny, isn't it, that the functionality is implemented for restricted format first rather than Free format.

Revision history for this message
Pablo (pabloa) wrote :

From http://www.mikesplanet.net/?p=37
"...Ogg Vorbis tag editing (requires a GStreamer plugin not yet in cvs, see bug 335635)"

Revision history for this message
Jim Braux-Zin (j-brauxzin) wrote :

The debs published here don't work for me on a fresh dapper install... libsoup2.2-8 version should have been >=2.2.93 while the dapper version is 2.2.92. Why haven't you got this problem?

description: updated
Revision history for this message
jim (hesoez) wrote :

I have libsoup2.2.8 version 2.2.93-0ubuntu1 installed, it's in updates i guess. When you install the new rhythmbox through apt it will update the libsoup package as a dependency so i don't think that's a problem. Or maybe (if it's possible) the new rhythmbox has to be compiled on a fresh dapper install. I've tried the .deb and it works very well on my system. Only annoyance that is not fixed is the fact that rhythmbox crashes when using the dvd-drive (formatting dvd-rw or burning a dvd), but that's probably a gstreamer problem.

Revision history for this message
Tom Verdaat (tom-verdaat) wrote :

Tested the deb posted by John Dong and it has been working fine on my dapper environment for weeks now.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Backport team, any reason the new rhythmbox has still no backport for dapper?

Revision history for this message
jim (hesoez) wrote :

Could you backport 0.9.6 to dapper?
It seems to have fixed the unresponsiveness when burning a cd/dvd.
I've tested with the version found on http://www.getdeb.net

Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Just tried with 0.9.6-0ubuntu4 version in an up-to-date dapper-pbuilder:
 -> Considering libnautilus-burn-dev (>= 2.15.3)
      Tried versions: 2.14.3-0ubuntu1 2.14.1-0ubuntu2
   -> Does not satisfy version, not trying
E: Could not satisfy build-dependency.

libnautilus-burn-dev is too old in dapper (and I am not sure it can be backported without breaking gnome).

Revision history for this message
John Dong (jdong) wrote :

Rejected due to unsatisfiable build deps.

Changed in dapper-backports:
status: In Progress → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.