Alien Pastures

My thoughts on Slackware, life and everything

Tag: compatibility

Package updates as a result from the switch to Python 3.10 in Slackware-current

October 22, 2021 / / 29 Comments

When Python3 was updated from 3.9 to 3.10 in Slackware-current two weeks ago, lots of 3rd-party packages (i.e. software packages that are not part of the Slackware distro itself) containing python modules were suddenly broken.
To make things more complex, not all Python software is currently compatible with Python 3.10. Patrick Volkerding opened a poll on LinuxQuestions.org to get feedback from the community about this intrusive update after we already have a Slackware 15.0 Release Candidate since mid-august.
After all, when you tag a Release Candidate, that usually sends a signal that the software set is frozen and only usability issues and software bugs will be addressed.

After giving this some time to sink in and hoping that this update would be reverted because of its impact, I now think we are stuck with Python 3.10 in Slackware. Which means I had to start looking at which of my own packages are now broken.

This will require time I am sure. time which I do not have in large quantities, so I am going to do this incrementally and with a sense of prioritizing. Top-most I am going to work on the packages that are actually reported to me as being broken.

Today’s message for you is that I have fixed the Inkscape package in my repository. Inkscape is a complex program for creating vector graphics (SVG images for instance). Complex in the sense that it has many dependencies and some of these were also broken – due to recent boost, icu4c and python3 upgrades in Slackware. The sum of updated packages is therefore: inkscape, libcdr, python-lxml, python-numpy and scour.

Let me know if there’s other software in my package repository for -current that’s currently broken. I do not use all that software myself so in some cases I will be totally unaware of any ‘broken-ness’ until you tell me.

Cheers! Eric

Google toolbar in Firefox 5

June 26, 2011 / / 6 Comments

Mozilla upgraded its Firefox browser to version 5.0. Slackware followed by packaging it for Slackware -current and offering it as a patch (it fixes some security holes) to the old 4.0.1 version in Slackware 13.37.

Infected by Google Chrome’s release strategy, it seems like the Mozilla developers now think that jumping to new version numbers fast, while abandoning their older release, is a good thing to do. Their rationale, “the web is changing fast and our software should keep the same pace” sounds valid, but I predict that it will negatively affect their usage statistics.

Read this blog entry which voices concern over the deployment of Firefox in enterprise environments and especially Mozilla’s director for the Firefox browser (Asa Dotzler)’s comment… I do not think he did the right thing by downplaying the corporate environment in which most of us have to spend 40 hours every week.

I work in two different “corporate environments”: one is that of my employer (IBM) where we have standardized on Firefox but internal IT keeps tight control over versioning and features… I guess IBM can do that. And then I face the IT landscape of my customer where Internet Explorer is king and open source / open standards adepts are fighting an uphill battle in getting Firefox accepted as a viable alternative.

Leaving alone all the enterprise stuff for a bit, what consequences has this new Mozilla strategy for you and me, Slackware users? Well hum.

It became obvious very soon after running slackpkg and upgrading to the latest slackware-current… I started Firefox and was greeted with the message that my Google Toolbar extension would be disabled because supposedly it is not compatible with Firefox 5.0:

I know, some of you consider that toolbar a piece of legalized spyware, but it keeps my search history available to me and not just Google (what do you think happens with all the search queries you enter in a Google search?) and I like it. So… I wanted it back ASAP.

It is most unfortunate that Google no longer considers the Toolbar as the ultimate weapon to get their Google services onto everybody’s desktop; now they have their own browser, Chrome, and that gets all the attention. This means that updating the Toolbar to the latest Firefox requirements does not have a lot of priority.

There is a way around it, which does not involve waiting for Google, and does not require any other software to be installed. Adding one configuration setting is all:

  • Open the Firefox configuration window by typing “about:config” in the URL entry field
  • Right-click on any of the items displayed and select “New” and then “Boolean“
  • The name of the new entry should be “extensions.checkCompatibility.5.0” and its value should be set to “False“
  • Then, restart your Firefox browser.

If you open your add-on configuration Window now (“Extra > Add-ons“), you will see that the compatibility check has been disabled for Firefox 5.0! And you will also see that the Google Toolbar (and possibly other so-called incompatible add-ons) are enabled again – at your own risk of course:

I hope this helps some of you.

Cheers, Eric

© 2024 Alien Pastures

Theme by Anders Noren — Up ↑