Your message dated Sun, 25 Aug 2019 15:26:19 +0000 with message-id <[email protected]> and subject line Bug#935659: Removed package(s) from unstable has caused the Debian Bug report #378184, regarding I wish all my contacts had a different default buddy icon (not a blue head) based on what protocol they used to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 378184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378184 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: kopete Version: 4:3.5.3-1 Severity: wishlist Problem: A dozen of my contacts all have same icon: a diagram of a bald head with blue-colored skin. Feature request: I would prefer if the Jabber-using buddies had a lightbulb icon, the AIM-using buddies had the AIM logo icon, and the MSN-using buddies had a butterfly icon. I, a newbie to Kopete hacking, humbly offer tips on how one could implement this fix below. (I don't know if my tips would work.) I also ask some questions about whether my fix would actually work. I would very much appreciate feedback. . . . . . Tips for implementing the fix: The protocol icons are in /usr/share/apps/kopete/icons/crystalsvg/32x32/apps. I assume they are converted upstream from unlimited-resolution SVG source. The blue head icons are elsewhere. There are actually four slightly different blue head icons: metacontact_{online,away,offline,unknown}.png. However, it's not that important to show online/away/offline status in the buddy icon space because that info is saved by automatic contrast-fading of icons of buddies who are away, and because the same info (plus Extended Away status) is shown in the tiny (16x16) icons to the right of contact names. Therefore, I feel it is fine to ignore the fact that there are four slightly different blue head icons. The code that seems to return the blue head icons seems to be the function MetaContact::statusIcon() in kopete/libkopete/kopetemetacontact.cpp. I assume that if the lines of this sort: return QString::fromUtf8( "metacontact_online" ); were changed to return something like: return QString::fromUtf8( "msn_protocol" ); or return QString::fromUtf8( "aim_protocol" ); or something similar, based on which kind of protocol the contact used, then you would be OK. Question 1 about proposed fix: If I do not implement the above proposed fix, does anyone else here also want this fixed and will implement the fix themselves? :-) I am currently working on another project - ITP bug http://bugs.debian.org/376431 - currently. Question 2 about proposed fix: Most people don't use the subcontact features of Kopete (where, if one friend uses three different protocols, you can show just one icon for that friend). But some people do use that feature. How will my proposed interact with Kopete's metacontact features? Could Kopete show the blue head for supercontacts with subcontacts below, but use my fix the rest of the time? Signing off, and wishing there was a hackers' guide to Kopete :-), Jason
--- End Message ---
--- Begin Message ---Version: 4:17.08.3-2.1+rm Dear submitter, as the package kopete has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/935659 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
