search for: oldoldst

...and boot with ucode=-1, then the update is working. In both cases dmesg or ?xl dmesg? don?t tell anything about microcode updates (successfull or not). The option ucode=scan doesn?t work with XEN 4.4 either or with 3.6 kernels. -- System Information: Debian Release: stretch/sid APT prefers oldoldstable-updates APT policy: (500, 'oldoldstable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.2-Dom0 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh lin...

...re (and caused a bit of delays and packet loss) for five hours, until I restarted tinc on one (randomly picked) node. The traffic for all hosts went immediately down to idle. Most of the tinc nodes use v1.0.31. Two use v1.0.24 and a single old one is still at v1.0.19. (Debian stable, oldstable and oldoldstable) The tinc daemon I restarted was using v1.0.31. The setup is running unchanged (besides a few nodes being added from time to time) for a few years. The only non-default setting is "ReplayWindow 32". I am quite confident (due to the age and stability of the setup), that this was jus...

...working. In both cases dmesg > or ?xl dmesg? don?t tell anything about microcode updates (successfull or > not). > > The option ucode=scan doesn?t work with XEN 4.4 either or with 3.6 > kernels. > > -- System Information: > Debian Release: stretch/sid > APT prefers oldoldstable-updates > APT policy: (500, 'oldoldstable-updates'), (500, 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.0.2-Dom0 (SMP w/8 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (cha...

...about microcode updates (successfull or > >> not). > >> > >> The option ucode=scan doesn?t work with XEN 4.4 either or with 3.6 > >> kernels. > >> > >> -- System Information: > >> Debian Release: stretch/sid > >> APT prefers oldoldstable-updates > >> APT policy: (500, 'oldoldstable-updates'), (500, 'testing'), (500, 'stable') > >> Architecture: amd64 (x86_64) > >> Foreign Architectures: i386 > >> > >> Kernel: Linux 4.0.2-Dom0 (SMP w/8 CPU cores) > >&g...

This patch proposes to drop support for Python 2 in nbdkit. Rather than abruptly drop it everywhere, my proposal is that we point people to nbdkit 1.14 (the current stable version) if they want to continue with Python 2 plugins, while gently reminding them of the upcoming Python 2.7 end of life announcement. Libnbd never supported Python 2. Libguestfs in theory supports Python 2 but I dropped

Hi Charles, Thanks for your reply. So the Jessie or stretch versions will work then since those are 2.7.2 and 2.7.4... I will have to update my sources.list and follow this? https://backports.debian.org/Instructions/ Will give it a go later and update either way. Thanks, ST Via mobile On 1 Aug 2017 19:44, "Charles Lepple" <clepple at gmail.com> wrote: > On Aug 1, 2017, at

Hi, Xi is broken at the moment. This XenServer version won't boot jessie kernel. Can't fix this myself, so this may take some time. Regards, Stephan.

...ot upgrade XenServer any time soon, we reverted the build systems back to Debian wheezy (oldstable) by re-installing them from scratch. It should all work as normal, with the difference that wheezy is built first. Added Debian stretch (current testing) repository, while the Debian squeeze (current oldoldstable) repository was removed. I also removed repositories for dovecot-2.1 and older. The repositories can now also be used with the release names (e.g. wheezy-auto rather than oldstable-auto). Don't hesitate to notify me if there are any problems. Regards, Stephan.

...20 nodes suffered from a flood of > packages like the following: > IP6 fe80::e4eb:74b6:57e0:c3e1 > ff02::2: ICMP6, router solicitation, length 8 [...] > Most of the tinc nodes use v1.0.31. Two use v1.0.24 and a single old one is > still at v1.0.19. > (Debian stable, oldstable and oldoldstable) The issue looks like a routing loop. In fact, there was a bug in versions before 1.0.24 that might cause routing loops of broadcast packets, and this router sollicitation message is in fact a broadcast packet. If possible, upgrade to a newer version of Debian. If that's not possible, try...

Starting with nbdkit 1.16, Python >= 3.3 will be required. Python 2 reaches end of life on 2020-01-01: https://python3statement.org/ https://pythonclock.org/ Debian oldoldstable and RHEL 7 have Python 3.4 and 3.6 respectively, so it seems pointless to try to support Python < 3.3 which lacked support for PyUnicode_AsUTF8. --- README | 13 +++++++------ configure.ac | 36 ++++++++++++++---------------------- plugins/python/python.c | 31 +-...

...but I mistakenly thought that there was a NUT > package in wheezy-backports. https://packages.debian.org/ > search?suite=wheezy-backports&keywords=nut-server does not list anything. > (Debian only does backports by request, and that could take a while - > especially for something in oldoldstable.) > > Agreed that upgrading to jessie or stretch would work. > > If you can install build-essential and the NUT build-deps, you could build > a newer version from source. > > here is some info on that process: http://lists.alioth.debian. > org/pipermail/nut-upsuser/2016-...