openSUSE 11.1 support and Lightning

As with the release of openSUSE 11.1rc1 I’ve enabled openSUSE_11.1 for the mozilla repository. So feel free to add it to your local repositories.

Another news is that I’ve added the package MozillaThunderbird-lightning which contains Mozilla’s calendar extension for Thunderbird. I’ve planned this years ago but for different reasons (including gcc bugs that didn’t happen until Duncan asked me to add his Lightning package to the mozilla repo just yesterday). The reason for adding that extension was simply that you can’t get it as x86-64 version from upstream.

And as of today openSUSE 10.2 was removed from the buildservice which means that there are no more mozilla updates for that platform. I’m wondering how many people out there still rely on those since it’s possible to reenable support for that again but I’ll only consider that if there is real demand for it. So let me know and speak up 😉


8 thoughts on “openSUSE 11.1 support and Lightning

  1. I still rely on the Mozilla updates for openSUSE 10.2, so I would like to see the support reenabled again.

  2. I’m still using 10.2, but after this, I’m considering switching away from suse. Being unceremoniously dumped after slightly more than a year of use not acceptable. It’s one thing to make it end-of-life and stop updating the packages, I can do that myself to at least get by until I’m ready to update. But to REMOVE the repositories and all related files preventing me from even installing a previous version of anything is absolutely ridiculous.

    This is going to cost me a LOT of time. I had everything set up the way I wanted and everything working very well. Now it’s all GONE. I practically have to start from scratch, building new versions of my custom rpm files that I’d created for dozens of utilities, fix all the little scripts I’d written to automate different things, reinstall a myriad of perl modules, I finally got the smart package manager perfectly tuned and working. All for naught. Now I can’t even download a src.rpm file to use its spec as a model to update something myself.

    This is an inconsiderate, poorly conceived, ham-fisted maneuver by suse. Since I now know I can count on them to leave me high and dry, why should I invest the the time in a new suse distribution when I know I’m going to have to do it all over again in a year. For shame, suse.

  3. I’ve enabled openSUSE 10.2 again.
    @AHinMaine: I’m not really the person to complain to. The 10.2 repos were removed globally from the repositories.

  4. Thanks for re-enabling the openSUSE 10.2 repos again. I also rely on other 10.2 buildservice repos, besides just Mozilla, e.g., Education for the Netbeans packages (version 6.5 was just put out there last week, and then the 10.2 repo disappeared), OpenOffice Stable, various home:xxx repos, like home:wrosenaouer:playground for the gtk2 fix for Firefox 3, and other home:xxx repos for things like hplip, etc.. Will all the 10.2 buildservice repos be re-enabled again, or just Mozilla?

  5. @David: Thanks for remembering me about my playground repo which was solely for 10.2 and is also enabled again. I can only control “my” repositories to enable “DISCONTINUED” 10.2 again. For the others you would have to ask the admins of them.

  6. How long does it take for the Mozilla 10.2 repo to show up again? I checked on, but don’t see an openSUSE_10.2 directory. It seems like I did yesterday? I also checked on, and also don’t see an openSUSE_10.2 directory. However, I do see the home:wrosenaouer:playground on these servers, so that one looks like it has been re-enabled, thank you!

Comments are closed.