Debian Jessie freezing and stuff

On November 5, Debian's testing branch (with the name Jessie) was frozen, after long months of development and correcting more than 400 bugs. They also have ready the official art for the distro, by Cyril Brulebois.

Incidentally, they announced that Debian 9 (due out in 2017), will be called Stretch. And that Debian 10 (due out in 2019), will be called Buster. It was also announced that the kfreebsd port will no longer be an official port, and the ports for the arm64 and ppc64el architectures will be.

Among the packages that will come by default are: kernel 3.16, Iceweasel and Icedove 31, GNOME 3.14, KDE 4.14, LibreOffice 4.3.3, GCC 4.9, MySQL 5.5.39 (there will be no migration to MariaDB, they will only include it within the repos and nothing else), OpenJDK 7u71, Perl 5.20, Python 2.7.8 and 3.4.2, Xfce 4.10, Apache 2.4.10, Tomcat 6.0.41 and 7.0.56 and, of course , systemd 215

Another important thing is Joey Hess's departure, who since 1996 has held various roles in Debian, including maintaining the debhelper, alien, dpkg-repack, and debmirror packages. He cites as a reason for his departure the fact that the Debian constitution led the project in the wrong direction. I don't know if it's a wink to the February championship, but it can be.


26 comments, leave yours

Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   nobody said

    according to I read the output of joe hess has to do with the adoption of systemd ...

  2.   Rolo said

    how strange that the guy moves away from debian by systemd and in his blog write a post on how to use the systemd cron module https://joeyh.name/blog/entry/a_programmable_alarm_clock_using_systemd/

    I don't think it's the behavior of someone who is against systemd

    by the way the official art looks like the trisquel but in a bland version

    1.    elav said

      I do not think that one thing has to do with the other. The fact that one does not use (for example) Windows does not mean that if you can teach someone to use it, say: NO, because I do not use it. On the contrary, it shows you how to use it and let the other see for himself if it suits him or not.

      1.    Rolo said

        From what I have been seeing with the issue of systemd, there are no middle terms and those who are against hate it as if it were an invention of Satan himself (not turpial but ajoba: P)
        as they say to show this a button http://igurublog.wordpress.com/2014/04/28/ignorantgurus-hiatus/ this is the developer of SpaceFM the fork of PCmanFM stops using debian because of the systemd issue

        and as I said, since with systemd there are no middle terms you are not going to write a post-tutorial on systemd and then leave because debian implements systemd.

        That is if I know that there was an attempt to vote to get the option to use sysv in the debian installer, although the issue was that there are not enough people to keep the package compatible with both managers

  3.   orange said

    I registered yesterday and apparently it did not pass the moderation?

    1.    elav said

      I doubt it!

      1.    orange said

        I never got the confirmation email, how do you know if someone is a bot or not, seeing only the nickname and the email?

  4.   yukiteru said

    The Joey Hess thing is very clear, not only is systemd, it is the way in which certain things are being handled in the distro, and you have left a good example here, MariaDB is not the default version for databases and instead MySQL is still being used, something that years ago would have been quite crazy.

    1.    elav said

      Well that's what I'm trying to say in my comment .. +1

      1.    yukiteru said

        Exactly @elav Debian has changed a lot compared to previous years and it is this situation that has made many developers and collaborators decide to abandon the project. IgnorantGuru also said it on his blog with his hiatus, not only is systemd the way things are done, now it is Joey Hess, and many more will join the group depending on what is decided on November 18 when the vote about the free choice of init se de.

  5.   elav said

    It is not for less that Joey Hess has left the project, and what is more, I share the supposed cause that you comment on in the Diazepan post. I wonder why Debian does not just move to MariaDB when other distributions have already done it without any problem and are not so philosophical? Cof .. cough .. Archlinux .. cough .. They stop supporting KFreeBSD why? What is the excuse if they maintain other architectures that only a few use? Anyway .. every day I get further away from Debian and that hurts .. 🙁

    1.    peterczech said

      They stop supporting KFreeBSD since their kernel is not Linux but BSD ... You know that systemd does not get along with BSD systems: D.

      1.    peterczech said

        As for mysql or mariadb ... Does it matter a bit, right? And it's still being debated about it: D.

      2.    peterczech said

        I also think that Debian leaves mysql by default for the moment for a very important reason: MySQL Cluster CGE.

        Please note that Debian is used on servers and should remain neutral for everyone. You cannot pass to MySQL Cluster CGE from MariaDB and if they remove MySQL from Debian this could lead to the rejection of not a few users.

      3.    eliotime3000 said

        In other words: there is quite a bit of pressure related to the MySQL CGE cluster. Besides, if Andamiro releases a successor version of Pump It Up Infinity, you probably no longer use Debian as the default OS due to its initial reliance on SystemD in environments like GNOME and components like NetworkManager.

  6.   linuXgirl said

    I agree with Joey Hess: «… the Debian Project is no longer the same…» 😉

    1.    eliotime3000 said

      In that he is right, since Debian now makes decisions like Ubuntu did when it released 12.04.

  7.   xarlieb said

    but they say that MariaDB will be in the official repos "just in case". So I don't see much of a problem for now.

  8.   Xipe said

    It is sad what is happening in the last year on Debian. I can understand the fed up of some developers - like Joey Hess - with the climate of tension that is often experienced in debates over the Debian 8 "Jessie" startup system.

    It has been a difficult decision and it is proving painful. Even some users (who are not developers, at the moment), are considering creating a fork of the distribution that does not incorporate systemd by default.

    Systemd - and this is one opinion - is problematic, opaque, and potentially insecure. It fiddles with too many dependencies and forces us to make changes that some users do not agree with. Many system administrators are warning of the serious technical conflicts that its implementation entails (for not using the thick words with which they usually refer when they speak of systemd). This is not a debate about "evolution-conservatism," "progressivism-immobility," or "modernity-antiquity" as some commentators have wanted to simplify it. Nor is it a Manichean dichotomy between "cool" desktop users and "troglodyte" system administrators. It's about security, modularity, flexibility, and most importantly, trust.

    If I want to remove systemd in Debian and put sysyinit I find that the following packages will be uninstalled:

    1) colord
    2) gvfs
    3) gvfs-backends
    4) gvfs-daemons
    5) hplip
    6) libpam-systemd
    7) policykit-1
    8) policykit-1-gnome
    9) printer-driver-postscript-hp
    10) steadyflow
    11) systemd-sysv
    12) udisks2

    Leave the following dependencies unresolved:
    14) libcolord2 retrieves colord
    15) cups recomana colord
    16) cups-daemon reclaims colord
    17) cups-filters retrieve colord
    18) gvfs-common accepts gvfs
    19) gvfs-daemons takes over policykit-1-gnome
    20) libsane-hpaio recomana hplip (= 3.14.6-1 + b2)
    21) liferea recomana steadyflow | kget
    22) printer-driver-all requires printer-driver-postscript-hp
    23) task-print-server receives hplip
    24) udisks2 recomana policykit-1

    They are important dependencies. For some I will find a substitute but for others I will not and my system will limp somewhere. I can always install "systemd-shim" (which is what Lucas Nussbaum, the current project leader, recommends) but it will still be a bit of a fix. A patch that, in particular, does not convince me.

    A distribution like Debian (and this is an opinion again) should have opted to partner with Gentoo and strengthen OpenRC or develop its own boot system. Your inability to do so can be interpreted as a sign of neglect. Debian loses initiative and somehow independence, and that's unfortunate. Although of course, this is my opinion and I have no right to demand anything from anyone, much less the Debian community.

    It is not about removing systemd from the repositories (which may be useful to many users) it is about that this system does not contaminate everything and limits the possibilities of users.

    Those who use Gnome are tied to systemd, but the rest of us don't have to be if we don't want to, and therein lies the voting proposal (General Resolution: init system coupling), presented by Ian Jackson, which has sparked all the bitter debates that they have surely led Hess and other developers to abandon the project. The problem has been in the tricks used, the lack of respect in the mailing lists and some completely inadmissible attitudes in a discussion environment that is intended to be constructive.

    There is a lot of talk about the Unix philosophy (do one thing and do it well) or the blissful Linux standards (as if these were to make Linux the ultimate desktop system that wipes Windows and Mac OS X off the map), but the truth is that this is dead paper if there is no minimum consensus. And systemd doesn't bring it. In sight it is. Linux is not entirely planned (like BSD or Windows and Mac), standards are welcome but must meet the requirements of a free, critical, and in some cases scholarly community.

    And of course, it's not about the system booting up 20 seconds faster either. That is staying on the surface of a much more complex problem.

    If the situation in Debian continues like this, on a personal level I consider migrating to Gentoo or, if necessary, giving the happy fork of Debian a chance, as long as I am convinced by its social contract and the developers behind it (there is a lot of anti troll -systemd that I don't like them at all, really). So far, I'll stay on Wheezy.

    Greetings and sorry for the length of the comment,

    1.    Rolo said

      but to use sysv you don't need to uninstall systemd http://www.esdebian.org/wiki/systemd#3.2 editing / etc / default / grub and setting GRUB_CMDLINE_LINUX_DEFAULT = »quiet init = / sbin / init.sysvinit» + update grub or else uninstalling the systemd-sysv package (you probably have sysvinit installed).

      PS: asking you to uninstall those packages would not be a problem. what you could do is: first put sysv to manage the startup, then remove systemd and reinstall the packages (except for gnome because it will ask for systemd)

      you have to read and not be judgmental

      regards

      1.    eliotime3000 said

        That's right, since the first thing I did was install SysVinit and then uninstall SystemD so as not to run out of INIT.

  9.   xiep said

    In the previous comment I misspelled my nickname, it is Xiep.

    That said, yes, to be able to use sysvinit it is not necessary to uninstall systemd, but precisely what I want is to uninstall it.

    That is, if I do not trust systemd and want to remove it from my system, I run into uncomfortable setbacks, such as automatically mounting removable media or suspending and hibernating the system without being root. I can do it manually, it would be more, but you will agree with me that this is a fix. Almost anything that depends on "dbus" will install systemd. So far one of the "official" solutions of the project has been to install "systemd-shim" (http://www.itwire.com/business-it-news/open-source/65684-debian-leader-says-users-can-continue-with-sysvinit), a package that emulates systemd and allows you to use all the programs that depend on it. But this solution is not quite convincing.

    Of course I can survive without systemd (everything can be fixed in this life), it is about under what conditions I do it and what and who favors Debian with this decision. You have to be juggling so that everything works and that is precisely what has led the community to confront the RG that is raising so many blisters and causing some casualties (https://www.debian.org/vote/2014/vote_003.en.html). The problem is that the result tends to be binary: either you win or you lose. It seems that the climate is so radicalized that the discussion is ending in an "all or nothing." Bad business, really. On November 19 we will leave doubts.

    You are very attentive to worrying about my behavior, Rolo, but I read a lot and trust me, I am not judgmental. Precisely, what has seemed hasty to me is the adoption of systemd by default in some of the most important distributions, when it is a system that is not very mature, let's say. Anyway, such a rush seems suspicious.

    Health!

    1.    Rolo said

      Xiep about "... That is, if I don't trust systemd and want to remove it from my system I run into uncomfortable setbacks, such as automatically mounting removable media or suspending and hibernating the system without being root ...." You are confusing systemd with PolicyKit (you have to read !!!) and some bug in debian related to desktops like lxde or xfce4.

      How much would you have to create your own Polkit rules

      You have to stop messing around with the systemd issue, at the end of the day it is a software that if it works well, jewel and if not, it will be changed for something else and a hint. but please let us leave politics for important things in life,

      vast of prejudices based on ignorance let us stop repeating like parrots what others repeat

      1.    xiep said

        Rolo, it's going to be difficult to uninstall systemd on Debian Jessie, I mean that. Replacing the default boot system is tricky and can break the system.

        It's not fucking anyone. Many Debian users don't trust systemd, that's all. And we view with concern the decisions that are being adopted lately, that's why there is debate. In fact, the final decision of the Technical Committee was very tight. It is normal that I still got the controversy because only one vote decided the final decision. And that's not exactly a clear majority.

        Debian has always considered political and social aspects. Perhaps that is what has made the project what it is, otherwise it would not be Debian.

        I don't know how to take your last paragraph… As a disqualification? You come to imply that I am ignorant and a parrot without my own criteria ... A bit exaggerated, right?

        In short,

        Health!

  10.   Nonamed said

    lovely Jessie's art work

  11.   eliotime3000 said

    What surprises me is that the Debian developers have not taken into account UselessD, which is better than systemd-shim and is seen as a better alternative to what Debian offers. The bad thing is that it is already too late to propose it, since the repos have already been frozen and it seems that this version will be the equivalent of Debian's Ubuntu 12.04.

    Regarding SystemD, I don't see RHEL / CentOS currently being enthusiastic about rolling out version 7 on a massive scale (you know, SystemD).