correction...  the four backgrounds in desktop-backgrounds are just symlinks
into the theme packages.  this makes things simpler and more complicated at the
same time.  problem remains, though.  my temporary solution was to produce
empty equivs-generated packages to replace and conflict out the theme and
theme-config packages.

Re-assigned to correct person.

Comment 3 Roope Rainisto 2007-08-21 12:29:24 UTC

Reassign to Tuomas.

Comment 4 Tuomas Kuosmanen 2007-09-11 10:07:04 UTC

Assigning to Michael as I don't know that much about debian packaging to be of
much help here.

Comment 5 Eero Tamminen 2007-10-11 18:43:16 UTC

IMHO there should be a virtual package provided by the theme packages and
the other packages depend from this virtual package.

https://garage.maemo.org/tracker/index.php?func=detail&aid=1456&group_id=164&atid=681

Comment 7 Andre Klapper 2008-05-30 18:25:03 UTC

hmm, this doesn't sound too hard to fix to me.

Comment 8 Andre Klapper 2008-06-06 17:17:09 UTC

reassigning MDK's bugs to Rodrigo.

Comment 9 Andre Klapper 2008-11-03 20:57:59 UTC

Can neither find osso-theme-theme2 nor desktop-backgrounds.
Have these packages been renamed? Is this still valid?

Comment 10 Andre Klapper 2008-11-17 15:55:19 UTC

(In reply to comment #9)
> Can neither find osso-theme-theme2 nor desktop-backgrounds.
> Have these packages been renamed? Is this still valid?

Anybody able to answer my questions?
Clarence, Tuomas? :-/

(In reply to comment #9)
> Can neither find osso-theme-theme2 nor desktop-backgrounds.
> Have these packages been renamed? Is this still valid?
> 

They have been renamed to hildon-theme-XXXX, for example hildon-theme-echo.

Now they depend on osso-software-version-rx44 (package known by everyone) and
hildon-application-framework-rx34-rx44 (really I don't know what does this
package, it only has changelog and copyright files that are deleted by docpurge
in the installation).

The background images are in every theme package, now they aren't in a separate
package.

So, I would say this bug has been half fixed, because now it suffers the same
problem as bug 3602.

Comment 12 Andre Klapper 2009-01-20 17:28:52 UTC

(reflect the reality and set correct assignee)

Comment 13 Quim Gil 2009-02-01 01:21:59 UTC

CCing Ville. 

Themes are also content and therefore they should be probably untied to package
dependencies (apart from the default one, that would assure that in the worst
case scenario you have always at least one theme available in the system).

Comment 14 Eero Tamminen 2009-02-02 10:35:28 UTC

(In reply to comment #13)
> Themes are also content and therefore they should be probably untied to package
> dependencies (apart from the default one, that would assure that in the worst
> case scenario you have always at least one theme available in the system). 

This should be handled through a virtual package which all real theme packages
provide and from which things needing a theme depend from.

Comment 15 Quim Gil 2009-05-21 14:32:02 UTC

Soumya, can you help explaining how are the package dependencies in Fremantle
and whether this is still an issue? Thanks!

Comment 16 Soumya 2009-05-22 14:00:51 UTC

In Fremantle, I see that the theme dependency in packages is set as 
'hildon-theme|hildon-theme-devel'

While hildon-theme-devel is actually valid a package name and the development
theme (used in the beta SDK), hildon-theme is a virtual package provided by
other themes.

So, all extra themes (other than hildon-theme-devel) that provide  for
'hildon-theme' and can be removed without affecting any other packages. 

In  my opinion, the original bug here should no longer be occuring in
Fremantle.

Comment 17 Quim Gil 2009-05-22 14:11:01 UTC

So I guess in an ideal world there should be 1 theme really tied to the system
(to fallback to it just in case you delete all the themes removable) and then
the rest of themes should be removable via the application manager. Is that
right?

Comment 18 Eero Tamminen 2009-05-25 19:19:16 UTC

(In reply to comment #17)
> So I guess in an ideal world there should be 1 theme really tied to the system
> (to fallback to it just in case you delete all the themes removable)
> and then the rest of themes should be removable via the application manager.
> Is that right?

The system should require any one theme to be present by depending on a virtual
theme package which is provided by all real theme packages.  I.e. user can
decide which theme to leave in to the device.

Comment 19 Andre Klapper 2009-07-02 15:03:39 UTC

A hildon-theme-* package in Diablo says
"Required by application packages:
 hildon-application-framework-rx-34-rx44
 OS2008 Feature upgrade"
A hildon-theme-* package in Fremantle does not list anything under
"Required by application packages:".

But of course I don't have a OS2009/Maemo5 Feature upgrade handy to test. ;-)

Comment 20 Andre Klapper 2009-12-30 15:44:05 UTC

This report was filed against Maemo4 ("Diablo").
The N900 and Maemo5 ("Fremantle") have been available for some time now.

If you own an N900, we kindly ask you to retest this with Maemo5 if possible,
and update this report by describing whether this still happens and which exact
Maemo5 version you use (Settings > General > About product).

This is unfortunately a WONTFIX for Maemo4 as Maemo4 is in maintenance mode and
Nokia will only provide bugfixes for critical issues if at all, as Nokia
currently seems to concentrate on Maemo5 and future Maemo releases.

Sorry that your issue could not be fixed for Maemo4. For your interest the Mer
project aims to provide a community backport of Maemo5 for 770/N8x0 devices.
See http://wiki.maemo.org/Mer for more information.

Comment 21 Quim Gil 2010-01-11 23:56:16 UTC

Now Maemo 5 comes with only 2 pre-installed themes that (I would say) it is
safe to keep just in case. Relying entirely on 3rd party themes might be
problematic when doing an update, for instance.

I don't know exactly the situation on dependencies currently but the current
situation looks fair from an end user point of view and therefore this looks as
a WONTFIX (or FIXED, if you find the situation has improved enough since Maemo
4).