Apr 19 2013

Evolution Woes and yum magic

I`m an oldschool guy .. I still love pop3(s) to get my mails locally and read them with my fat email client. Evolution.

So when gmail breaks their pop/imap infra I`m screwed for a while. I hate reading mail from a web gui and the collapsed threading model gmail uses makes me nauseus.

So I fiddled with my config .. disabled it.. deleted the account.. created it again. But even after gmail was up again . I couldn't access my mail from my favourite client. Yet from other clients it seemed to work.

This obviously is real fun when you are travelling and trying to keep an eye on a number of different email threads ..

So I`m back home from Paris now and spend some 10 minutes figuring out what could be wrong.

I ran into https://bugzilla.redhat.com/show_bug.cgi?id=949180 which points out that for newly created there is a problem with the keyring prompting

And refers to https://bugzilla.redhat.com/show_bug.cgi?id=953641 accounts Which states that gcr-3.6.2-3 breaks password prompt/keyring unlocks.

And indeed ..

  1. yum shell
  2. Loaded plugins: langpacks, presto, ps, puppetverify, refresh-packagekit
  3. > remove gcr
  4. > install gcr-3.6.2-1.fc18
  5. adobe-linux-x86_64 | 951 B 00:00
  6. fedora/18/x86_64/metalink | 31 kB 00:00
  7. google-chrome | 951 B 00:00
  8. google-earth | 951 B 00:00
  9. google-talkplugin | 951 B 00:00
  10. rpmfusion-free-updates | 3.3 kB 00:00
  11. rpmfusion-nonfree-updates | 3.3 kB 00:00
  12. updates/18/x86_64/metalink | 24 kB 00:00
  13. rpmfusion-free-updates/primary_db | 279 kB 00:01
  14. > run
  15. --> Running transaction check
  16. ---> Package gcr.x86_64 0:3.6.2-1.fc18 will be installed
  17. ---> Package gcr.x86_64 0:3.6.2-3.fc18 will be erased
  18. --> Finished Dependency Resolution
  20. ================================================================================
  21. Package Arch Version Repository Size
  22. ================================================================================
  23. Installing:
  24. gcr x86_64 3.6.2-1.fc18 fedora 627 k
  25. Removing:
  26. gcr x86_64 3.6.2-3.fc18 @updates 2.3 M
  28. Transaction Summary
  29. ================================================================================
  30. Install 1 Package
  31. Remove 1 Package
  33. Total download size: 627 k
  34. Is this ok [y/N]: y
  35. Downloading Packages:
  36. gcr-3.6.2-1.fc18.x86_64.rpm | 627 kB 00:02
  37. Running Transaction Check
  38. Running Transaction Test
  39. Transaction Test Succeeded
  40. Running Transaction
  41. Installing : gcr-3.6.2-1.fc18.x86_64 1/2
  42. Cleanup : gcr-3.6.2-3.fc18.x86_64 2/2
  43. Verifying : gcr-3.6.2-1.fc18.x86_64 1/2
  44. Verifying : gcr-3.6.2-3.fc18.x86_64 2/2
  45. Removed:
  46. gcr.x86_64 0:3.6.2-3.fc18
  47. Installed:
  48. gcr.x86_64 0:3.6.2-1.fc18
  50. Finished Transaction
  51. > quit
  52. > Leaving Shell

Solved the problem

Nov 03 2010

Bug Zapper

Dear Fedoracommunity,

Over the course of the day I recieved 22^H3 mails from your friendly Bug Zapper.

Most of those bugs where bugs I had reported upon crashes using bug-buddy. Bugs on different desktop tools such as .. synergy, evolution, gwibber , gnome-settings and probably some others

I do understand that I development goes on and on .. and your fancy devs don't care anymore about bugs I reported on Fedora 12 as they are all hacking on Fedora 15 and that I should update more frequently ...

But what I don't get is that non of these bugs was ever touched,
they've been automatically created , and automatically closed

Luis already told us ages ago .. every project needs a bugmaster apparently Fedora replaced that bugmaster with a Bug Zapper.

So can someone please explain my why I should continue to try to improve Fedora by reporting bugs ?

Jan 10 2008

Evolution Happens!

Back in 1998 one of the reasons my boss back then used for not doing something on a Linux box was
"We don't have enough people with the skills to support that"

Fast forward 10 years and the opposite is happening,
I had a chat with a coworker the other day and we were wondering how we ended up having a windows box from a 3rd party vendor in our platform since no one in our organization knows how to support it.

I imagine similar conversations in MySQL environments where people wonder who is going to support that one proprietary database that came a long with an oldskool vendor

Evolution and Adoption is happening, change happens !!