Important SolydXK news

As of today I’m taking a step back in the production of SolydXK. My family and I have come to the conclusion that some things are going to have to change. This means I cannot continue with SolydXK in the current form.

To answer some of the questions I received, I created a small FAQ:

  • Is SolydXK going to disappear?
    – No, I will continue maintaining SolydK64, SolydX64 based on the upcoming Debian stable and the SolydXK repository.
  • Is there going to be a 32-bit version?
    – I am not going to continue to maintain the 32-bit versions. However, I’d love to see them live on as pure community editions. Frank (grizzler) plans to give maintaining them a try, but can’t guarantee this will work out, so any assistance from the community would be highly appreciated.
  • Are there going to be “Enthusiast Editions”, based on Debian testing?
    – I won’t be able to maintain those either, but again, Frank will see what he can do about it. Any help from the community would be very welcome here as well.
  • Is the Back Office going to be maintained?
    – Unfortunately not. Although I love this edition, it takes a lot of time to create the packages and test them.
  • What about the repositories?
    – I will continue maintaining the SolydXK repository. The Debian and Security repositories will point directly to Debian. The packages of the Community repository will be transferred to the SolydXK repository.

    For the Home Editions the sources.list would look like this:

      deb solydxk main upstream import
      deb jessie main contrib non-free
      deb jessie/updates main contrib non-free
      deb jessie-backports main contrib non-free

    The sources.list for the Business Editions would look like this:

      deb solydxk main upstream import
      deb wheezy main contrib non-free
      deb wheezy/updates main contrib non-free
      deb wheezy-backports main contrib non-free

    The repository is still in development. So, please don’t use it on your working machine just yet.

  • Will my current install of SolydXK (and SoldyXK BE) roll into the new SolydXK when the new SolydXK based on Debian Jessie is released?
    – I have prepared a new version of the solydxk-system package that should rewrite the sources.list automatically. If you’re using the Home Edition, your sources.list will point to Jessie and if you’re using the Buesiness Editions, your sources.list will point to Wheezy.
  • Will there be any more Update Packs?
    – As Jessie is now preparing for stable there will be no need for any more Update Packs. Updates will come as regular updates or security updates.
  • What will be the release cycle of the ISOs?
    – Unfortunately, I cannot make any promises on frequency of releases (software or ISOs).
  • Will the forum still exist?
    – Yes, both the site and the forum will stay. Perhaps some minor changes in the structure, but nothing more.
  • When will this all happen?
    – I’ll start the transition on 31 January 2015.

Would you like to help?

  • Maintain one or more ISOs.
    – I’ve developed solydxk-constructor for that purpose. It comes with a help function to get you started and you can post your questions here:
  • If you find some software needs TLC.
    – If you know Python you can help. All code is available at Github:
    – If you find that one of those applications need to be translated in your language, you will find a “po” directory in each Github project. Choose the right .po file and start translating with poedit. You can either create a pull request or send me the translated .po file directly.
    Jocelyn (Ane champenois) will try to simplify the work of the translators by using an online platform of translation. You’ll have more informations about that if we’ll achieve that point.

I also would like to thank all the people who have helped me during the past two years. Without you I wouldn’t have come this far. I would especially like to thank zerozero who has been with this project since the early start. Thank you for your advice and keeping my feet on the ground when it was most needed.

Kind regards,
Arjen Balfoort