Minor highlight: Debian 8 ships with an OpenSSL which has SSLv3 disabled at compile-time.
Do you mean that only TLS is supported now?
Today is Debian 8 release day
111–120 of 152 posts
Re: Today is Debian 8 release day
#112Re: Today is Debian 8 release day
#113Earlier quoted context omitted.
Has there been a significant loss of Debian senior development resources to the https://devuan.org fork, as a result of the systemd debates?
Russ Allbery left https://lwn.net/Articles/620879/ edit: I don't know if he is going Devuan, but is related.
He just left the tech committee, the last paragraph sounds like he'll still be working on debian.
Re: Today is Debian 8 release day
#114Earlier quoted context omitted.
How could any update to the bootloader have been installed properly in that setup? If you did something unorthodox, such as building a boot process dependent on a manual step to clone drive, you surely must be prepared to deal with this in any number of situations that can arise? All non-standard solutions carry a debt where all future admins must understand what you built and how this affects operation.
Given that Debian's standard installers have always been pretty bad at configuring any non-trivial disk set-up without manual intervention, I feel some people here are a little too quick to criticise. As I said in another post, I don't know why the systems where that issue came up were originally set up as they were, but there have certainly been times, particularly before the current generation of bootloaders, when…
No one argues the packaging system can handle every possible situation. It's just that this case seems, on the face of it and without knowing any of the details, have been one where the system was manually placed in a state where the updater was broken.
I'm not a DD and I have no vested interest in it, but that particular data point is an outlier no matter how you look at it.
There are more obvious situations where updates will break your system. Most common probably when you've installed third party packages with dependencies on system software. But that's not generally what's referred to when asked if the update process is stable. Such things will break no matter how stable the process in itself is.
Re: Today is Debian 8 release day
#115Earlier quoted context omitted.
> I can't say why that is, but I've seen it on multiple occasions. Because Ubuntu releases are, well, releases. Early in the release cycle, they sync from Debian, they package their own things, then freeze the versions and release. They don't change versions of most packages in released! releases. Debian unstable on the other hand, has no concept of a release, so maintainers upload new versions of packages into unsta…
What you're saying makes sense, except that I would expect 15.10 to always be more current than it is before 2015-10 arrives. In reality, it's often not more current than the released version. If there is a new version of a package in sid, why isn't it in the "bleeding edge" ubuntu next-release? (I'm sure it's a good reason) In Debian, actually, I am pretty sure there's never really a freeze in unstable as you mentio…
> What you're saying makes sense, except that I would expect 15.10 to always be more current than it is before 2015-10 arrives. In reality, it's often not more current than the released version. If there is a new version of a package in sid, why isn't it in the "bleeding edge" ubuntu next-release? (I'm sure it's a good reason)
I'm not closely following Ubuntu development, but they have 6 month release cycles and they do the "sync from sid" early in the cycle, AFAIK first 3 months or so, so you can expect 15.10 to have what was in sid on August-ish. This may further skew when
1. Debian is on freeze. For example, Debian was on freeze starting from November '14, which means practically sid was also on freeze. Debian import freeze date for Ubuntu 15.04 was February [0], so while normally you would expect 15.04 to have latest versions of february; in reality they were latest versions of october. (there are, of course, exceptions). When you consider import freeze of 14.10 was August '14 [1], you can see why 14.10 and 15.04 have very similar versions.
2. Ubuntu is importing from testing for LTS releases, instead of sid. This shouldn't matter in an ideal world, where the difference between testing and unstable is 5-10 days, but sometimes packages got stuck in sid so bad that it may cause a difference in what lands in Ubuntu release.
3. I'm not so sure on that but if I understand correctly, they do a complete import of Debian in the beginning of the release cycle, and then maintainers can do ad-hoc imports for individual packages until the import freeze date, so the packages that land in the release may also be older than what was on sid near the import freeze date.
I guess you'll see much newer packages on 15.10, though, since sid will be full-speed during the 15.10 cycle, so nothing to worry about for now :)
Re: Today is Debian 8 release day
#116I think maybe it's more accurate to say that today is planned release day? Two relevant links:
(Second) latest post to debian-devel-announce:
https://lists.debian.org/debian-devel-announce/2015/04/msg00...
And latest post to debian-announce (concerning the latest stable point release, 7.8):
https://lists.debian.org/debian-announce/2015/04/msg00000.ht...
Re: Today is Debian 8 release day
#117Just on the side note. This was announced on microsoft website about them celebrating about Debian release. http://openness.microsoft.com/blog/2015/04/21/microsoft-debi...
I wonder why, following their new "openness" motto, Microsoft is still not: 1) porting Visual Studio to Linux. 2) porting Office to Linux, or 3) contributing to Wine, with the goal of solving long-standing issues with their (above) software - but hey they could contribute in other areas too, since Wine is far from complete (a USB driver/stack is much needed IMHO). I won't believe in Microsoft "openness" until I see o…
I dont think either of those are out of the question, but they can't be trivial to port. This stuff takes time.
Re: Today is Debian 8 release day
#118Earlier quoted context omitted.
Any idea how long Debian wheezy will continue to receive security bug fixes?
At least long enough to decide which Linux distro to use in the future. Unfortunately many distros have already jumped on the systemd wagon but I think soon there will be a increasing collection of non-systemd alternatives which will continue to follow the KISS principle which made Unix and Linux so great. There already _are_ alternatives to systemd and systemv -- launchd and upstart (used by ChromeOS) for instance.…
I just installed void on my laptop (x230) and it's quite nice. Very minimal and uses runit for managing services. Not many packages but it's had everything I've needed so far.
It also uses libressl and the packages build against alternative libcs so that's pretty cool. It's also interesting in that it's a new distro rather than a fork.
Re: Today is Debian 8 release day
#119Earlier quoted context omitted.
Any idea how long Debian wheezy will continue to receive security bug fixes?
At least long enough to decide which Linux distro to use in the future. Unfortunately many distros have already jumped on the systemd wagon but I think soon there will be a increasing collection of non-systemd alternatives which will continue to follow the KISS principle which made Unix and Linux so great. There already _are_ alternatives to systemd and systemv -- launchd and upstart (used by ChromeOS) for instance.…
> many distros have already jumped on the systemd wagon
Odd. If systemd is so Objectively Terrible (the general tenor of these posts: systemd is bad, it's obviously bad, with no redeeming features whatsoever), why is that happening? There can't possibly be a financial incentive.
Re: Today is Debian 8 release day
#120And here's the official announcement: https://bits.debian.org/2015/04/jessie-released.html