create a package for amarok 1.4

Bug #368706 reported by Tiago Cogumbreiro
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: amarok

Lots of people are having problems with Amarok 2.0. Having both packages Amarok 1.4 and Amarok 2.0 seems to be safer, since Amarok 2.0 is presenting lots of problems (different UI, regressions, etc.).

Revision history for this message
Tiago Cogumbreiro (cogumbreiro) wrote :

Bogdanb's PPA offers Amarok 1.4 for Jaunty.

https://launchpad.net/~bogdanb/+archive/ppa

Revision history for this message
Steve Stalcup (vorian) wrote : Re: [Bug 368706] [NEW] create a package for amarok 1.4

When will these silly requests stop?

Amarok 1.4 will not be packaged

On Apr 28, 2009, at 12:54 PM, Tiago Cogumbreiro <<email address hidden>
 > wrote:

> Public bug reported:
>
> Binary package hint: amarok
>
> Lots of people are having problems with Amarok 2.0. Having both
> packages
> Amarok 1.4 and Amarok 2.0 seems to be safer, since Amarok 2.0 is
> presenting lots of problems (different UI, regressions, etc.).
>
> ** Affects: amarok (Ubuntu)
> Importance: Undecided
> Status: New
>
> --
> create a package for amarok 1.4
> https://bugs.launchpad.net/bugs/368706
> You received this bug notification because you are subscribed to
> amarok
> in ubuntu.

Revision history for this message
Tiago Cogumbreiro (cogumbreiro) wrote :

@Steve: your comment is impolite.

By "silly" I assume you are saying that asking for two packages of different versions of the same program is a ridiculous or irrational thought. My motivation stemmed from the fact that in Jaunty we have packages for both Firefox 3.1 and Firefox 3.5.

If you are in charge of the package and do not want do it, I can accept that. Just mark it as WONTFIX. Spare me, however, of the "silly" adjective. This does not help fuel contribution.

Revision history for this message
Steve Stalcup (vorian) wrote : Re: [Bug 368706] Re: create a package for amarok 1.4

It is SILLY, and a waste of time, to report a feature request bug
(which was answered several months ago)

Revision history for this message
GreatBunzinni (greatbunzinni) wrote :

Steve, if you don't have any constructive comment to add then consider not posting at all.

Having said that, jaunty desperately needs an Amarok 1 package. Amarok 1 is usable while amarok 2 isn't. It lacks features, it's UI is a mess and it makes everything harder to accomplish while in amarok 1 everything was a breeze. The apt family of tools already support installing specific versions of a certain software tool. Please don't treat (k)ubuntu users as beta testers and make it possible for them to easily use the best software around instead of mindlessly forcing the cutting edge even when it means an absurd amount of steps backwards.

Revision history for this message
Darwin Survivor (darwinsurvivor) wrote :

GreatBunzinni, from what I've read in this and other forums, along with KDE's website, it is not ubuntu that is treating KDE users like beta testers, it is KDE itself.

Ubuntu has, and has had for a long time, a rule that stipulates that they will not add projects to their official repositories that are not currently being developed. KDE developers knew this when they stated that they are ceasing developement of Amarok1.x and only developing Amarok2.

At this point, the only way to get Amarok1.x added back into the repositories (karmic would be the next chance), is to get KDE (or some other group) to continue the regular maintenance of bug and security development of Amarok1.x.

Ubuntu is not saying "You can't have Amarok1.x because we want you to use Amamok2", they are saying "If you want Amarok1.x in the repos, it needs to be currently under development." It really is not very much to ask from Ubuntu and hopefully KDE will either quickly add the missing features to Amarok2 (including the old view) or get some people back on Amarok1.x's dev team.

I love Amarok1.x as much as the next guy, but adding a dead (KDE's words) application to the repositories is not a good idea from a security or support standpoint.

Sorry for the rant, but this has been said (in pieces) many times before, and yet people still don't get it!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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