Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running

2015-05-15 Thread Martin Steigerwald 
Am Freitag, 15. Mai 2015, 00:25:45 schrieb Thomas Liske:
 Re,
 
 On 05/14/2015 10:29 AM, Martin Steigerwald wrote:
  Ah, okay, I see that change is not yet in. Will remove it again until an
  update appears, unless its possible to disable the kernel check.
 
 the kernel check could be disabled in /etc/needrestart/needrestart.conf
 using:
 
 # Disable hints on pending kernel upgrades.
 $nrconf{kernelhints} = 0

Thanks, this appears to work. Will enable hints again after fix is in.

Have a nice weekend,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running

2015-05-14 Thread Thomas Liske 
Re,

On 05/14/2015 10:29 AM, Martin Steigerwald wrote:

 Ah, okay, I see that change is not yet in. Will remove it again until an 
 update appears, unless its possible to disable the kernel check.

the kernel check could be disabled in /etc/needrestart/needrestart.conf
using:

# Disable hints on pending kernel upgrades.
$nrconf{kernelhints} = 0


HTH,
Thomas

-- 

::  WWW: http://fiasko-nw.net/~thomas/  ::
   :::  Jabber:   xmpp:tho...@jabber.fiasko-nw.net  :::
::  flickr:  http://www.flickr.com/photos/laugufe/  ::


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running

2015-05-14 Thread Martin Steigerwald 
Am Freitag, 3. April 2015, 12:26:05 schrieb Thomas Liske:
 Re,

Re,

 On 04/03/2015 10:24 AM, Martin Steigerwald wrote:
  (4.20.0-rc6 wins against 4.20.0 which is expected since -rc6 could also
  be a usual CONFIG_LOCALVERSION string)
  
  Hmmm, but when I have a 4.20.0 final release compiled needrestart would
  treat it as older? That doesn´t make much sense for me.
  
  I think ideally it would use the same ordering as the boot manager. And
  grub2 definately puts 4.20.0 about 4.20.0-rc6.
 
 thanks for pointing me on grub's regex-hack in
 /usr/share/grub/grub-mkconfig_lib. I've ported the regex to needrestart
 and the kernel ordering should now be the same:
 
 $VAR1 = [
   '4.20.0',
   '4.20.0-rc6-tp520-btrfs-trim+',
   '4.19.0-foo-tp540-btrfs-trim+',
   '4.19.0-foo-rc6-tp544-btrfs-trim+',
   '4.19.0',
   '4.19.0-rc6-tp520-btrfs-trim+',
   '4.10',
   '4.9',
   '4.4.0-foo',
   '4.4.0',
   '4.0.0',
   '4.0.0-rc6-tp520-btrfs-trim+',
   '4.0',
   '3.19.3-a7-tp521-btrfs-trim+',
   '3.19.3',
   '3.19.3-rc6-tp521-btrfs-trim+',
   '3.19.3-rc6-tp520-btrfs-trim+',
   '3.19.0-rc7-tp520+',
   '3.10',
   '3.9',
   '3.3',
   '2.6',
   ''
 ];
 
 
 Thanks  HTH

I tested needrestart again and I still get:

Newer kernel available  
 

The currently running kernel version is 4.0.1-tp520-btrfs-trim-norace+ which 
is not the expected kernel version 3.18.0-tp520.  

Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.

needrestart 2.0-2

Ah, okay, I see that change is not yet in. Will remove it again until an 
update appears, unless its possible to disable the kernel check.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running

2015-05-13 Thread Aaron M. Ucko 
Package: needrestart
Version: 2.0-2
Followup-For: Bug #781657

I've run into this bug as well.  It looks like line 115 of
.../NeedRestart/Kernel/Linux.pm inappropriately removes the first
kernel version component.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781657: Processed (with 4 errors): Re: Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running - Bug in libsort-naturally-perl

2015-04-27 Thread Axel Beckert 
Hi again,

Debian Bug Tracking System wrote:
 Processing control commands:
 
  clone -1 -2
 Bug #781657 [needrestart] needrestart: pending kernel upgrade warning when 
 new kernel is already running
 Bug #783238 [needrestart] needrestart: Recognizes kernel 3.19.0-trunk-amd64 
 as newer than 4.0.0-trunk-amd64
 Failed to clone 781657: Bug is marked as being merged with others. Use an 
 existing clone.

*sigh*

I've created that bug report now manually. It's at 
https://bugs.debian.org/783457

Regards, Axel
-- 
 ,''`.  |  Axel Beckert a...@debian.org, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running - Bug in libsort-naturally-perl

2015-04-27 Thread Axel Beckert 
Control: clone -1 -2
Control: reassign -2 libsort-naturally-perl 1.02-1
Control: retitle -2 libsort-naturally-perl: Doesn't sort properly with numbers 
at the beginning of a string
Control: tag -2 = upstream

Hi,

Thomas Liske wrote:
 On 04/01/2015 02:14 PM, Thomas Liske wrote:
  The expected kernel version reported by needrestart is the first one...
  I need to review why i.e. 4.9 looses against 3.10.
 
 the kernel version sorting was based on Sort::Naturally which does not
 work since the rightmost integer found in the version string is used as
 the primary sorting index. Therefore 4.0 will loose against any 3.x
 (x0) kernels :-/

Thomas Liske wrote earlier:
 $VAR1 = [
   '4.20.0-rc6-tp520-btrfs-trim+',
   '4.20.0',
   '4.19.0-rc6-tp520-btrfs-trim+',
   '4.19.0',
   '4.10',
   '3.19.3-rc6-tp520-btrfs-trim+',
   '3.19.3',
   '3.19.0-rc7-tp520+',
   '3.10',
   '4.9',
   '4.4.0-foo',
   '4.4.0',
   '4.0.0-rc6-tp520-btrfs-trim+',
   '4.0.0',
   '4.0',
   '3.9',
   '3.3',
   '2.6'
 ];

 The expected kernel version reported by needrestart is the first one...
 I need to review why i.e. 4.9 looses against 3.10.

This looks like a bug in Sort::Naturally upstream:

$ perl -MSort::Naturally -E 'say join(\n, nsort(qw(1.fnord 3.bar 1-foo 
2.gnarz 3.19-foo 4.0-bla 3-19-foo 4-0-foo)))'
1.fnord
1-foo
2.gnarz
3.bar
4.0-bla
4-0-foo
3-19-foo
3.19-foo
$

Cloning this bug report accordingly.

 Upstream has been fixed by porting the version comparing stuff from
 Dpkg::Version into a simplified implementation in needrestart.

Hrm, why copying and causing code duplication instead of just simply
using use Dpkg:Version;?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert a...@debian.org, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running - Bug in libsort-naturally-perl

2015-04-27 Thread Thomas Liske 
Re,

On 04/27/2015 09:54 AM, Axel Beckert wrote:
 
 This looks like a bug in Sort::Naturally upstream:
 
 $ perl -MSort::Naturally -E 'say join(\n, nsort(qw(1.fnord 3.bar 1-foo 
 2.gnarz 3.19-foo 4.0-bla 3-19-foo 4-0-foo)))'
 1.fnord
 1-foo
 2.gnarz
 3.bar
 4.0-bla
 4-0-foo
 3-19-foo
 3.19-foo
 $
 
 Cloning this bug report accordingly.

it should result in something like:

 $ perl -MSort::Naturally -E 'say join(\n, nsort(qw(1.fnord 3.bar
1-foo 2.gnarz 3.19-foo 4.0-bla 3-19-foo 4-0-foo)))'
 4.0-bla
 4-0-foo
 1.fnord
 1-foo
 2.gnarz
 3.bar
 3-19-foo
 3.19-foo
 $

(primary sort by the right-most int). But it would not solve the problem
in needrestart... (kernel) 4.0 always looses against 3.19 since 0 is
less than 19. Using nsort was

 Upstream has been fixed by porting the version comparing stuff from
 Dpkg::Version into a simplified implementation in needrestart.
 
 Hrm, why copying and causing code duplication instead of just simply
 using use Dpkg:Version;?

1) needrestart should work on non dpkg-based distros, too. I don't
expect that libdpkg-version is available on non-debian-based Distros.

2) Using Dpkg::Version directly gives a different sorting than
update-grub would use to build the grub.cfg (i.e. sort -rc kernels
before the final version).

Therefore I did some cherry picking from Dpkg::Version and
grub-mkconfig_lib.


Cheers,
Thomas

-- 

::  WWW: http://fiasko-nw.net/~thomas/  ::
   :::  Jabber:   xmpp:tho...@jabber.fiasko-nw.net  :::
::  flickr:  http://www.flickr.com/photos/laugufe/  ::


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running

2015-04-03 Thread Martin Steigerwald 
Am Freitag, 3. April 2015, 01:54:24 schrieb Thomas Liske:
[…]
 Re,

Re Thomas,

 On 04/01/2015 02:14 PM, Thomas Liske wrote:
  The expected kernel version reported by needrestart is the first
  one...
  I need to review why i.e. 4.9 looses against 3.10.
 
 the kernel version sorting was based on Sort::Naturally which does not
 work since the rightmost integer found in the version string is used as
 the primary sorting index. Therefore 4.0 will loose against any 3.x
 (x0) kernels :-/
 
 Upstream has been fixed by porting the version comparing stuff from
 Dpkg::Version into a simplified implementation in needrestart. This
 results in the expected kernel version sorting order:
 
 $VAR1 = [
   '4.20.0-rc6-tp520-btrfs-trim+',
   '4.20.0',
   '4.19.0-rc6-tp520-btrfs-trim+',
   '4.19.0',
   '4.10',
   '4.9',
   '4.4.0-foo',
   '4.4.0',
   '4.0.0-rc6-tp520-btrfs-trim+',
   '4.0.0',
   '4.0',
   '3.19.3-rc6-tp521-btrfs-trim+',
   '3.19.3-rc6-tp520-btrfs-trim+',
   '3.19.3-a7-tp521-btrfs-trim+',
   '3.19.3',
   '3.19.0-rc7-tp520+',
   '3.10',
   '3.9',
   '3.3',
   '2.6',
   ''
 ];
 
 (4.20.0-rc6 wins against 4.20.0 which is expected since -rc6 could also
 be a usual CONFIG_LOCALVERSION string)

Hmmm, but when I have a 4.20.0 final release compiled needrestart would 
treat it as older? That doesn´t make much sense for me.

I think ideally it would use the same ordering as the boot manager. And 
grub2 definately puts 4.20.0 about 4.20.0-rc6.

Thank you,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running

2015-04-03 Thread Thomas Liske 
Re,


On 04/03/2015 10:24 AM, Martin Steigerwald wrote:
 (4.20.0-rc6 wins against 4.20.0 which is expected since -rc6 could also
 be a usual CONFIG_LOCALVERSION string)
 
 Hmmm, but when I have a 4.20.0 final release compiled needrestart would 
 treat it as older? That doesn´t make much sense for me.
 
 I think ideally it would use the same ordering as the boot manager. And 
 grub2 definately puts 4.20.0 about 4.20.0-rc6.

thanks for pointing me on grub's regex-hack in
/usr/share/grub/grub-mkconfig_lib. I've ported the regex to needrestart
and the kernel ordering should now be the same:

$VAR1 = [
  '4.20.0',
  '4.20.0-rc6-tp520-btrfs-trim+',
  '4.19.0-foo-tp540-btrfs-trim+',
  '4.19.0-foo-rc6-tp544-btrfs-trim+',
  '4.19.0',
  '4.19.0-rc6-tp520-btrfs-trim+',
  '4.10',
  '4.9',
  '4.4.0-foo',
  '4.4.0',
  '4.0.0',
  '4.0.0-rc6-tp520-btrfs-trim+',
  '4.0',
  '3.19.3-a7-tp521-btrfs-trim+',
  '3.19.3',
  '3.19.3-rc6-tp521-btrfs-trim+',
  '3.19.3-rc6-tp520-btrfs-trim+',
  '3.19.0-rc7-tp520+',
  '3.10',
  '3.9',
  '3.3',
  '2.6',
  ''
];


Thanks  HTH
Thomas

-- 

::  WWW: http://fiasko-nw.net/~thomas/  ::
   :::  Jabber:   xmpp:tho...@jabber.fiasko-nw.net  :::
::  flickr:  http://www.flickr.com/photos/laugufe/  ::


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running

2015-04-02 Thread Thomas Liske 
found 781657 1.2-7
tags 781657 + fixed-upstream
thanks


Re,


On 04/01/2015 02:14 PM, Thomas Liske wrote:
 The expected kernel version reported by needrestart is the first one...
 I need to review why i.e. 4.9 looses against 3.10.

the kernel version sorting was based on Sort::Naturally which does not
work since the rightmost integer found in the version string is used as
the primary sorting index. Therefore 4.0 will loose against any 3.x
(x0) kernels :-/

Upstream has been fixed by porting the version comparing stuff from
Dpkg::Version into a simplified implementation in needrestart. This
results in the expected kernel version sorting order:

$VAR1 = [
  '4.20.0-rc6-tp520-btrfs-trim+',
  '4.20.0',
  '4.19.0-rc6-tp520-btrfs-trim+',
  '4.19.0',
  '4.10',
  '4.9',
  '4.4.0-foo',
  '4.4.0',
  '4.0.0-rc6-tp520-btrfs-trim+',
  '4.0.0',
  '4.0',
  '3.19.3-rc6-tp521-btrfs-trim+',
  '3.19.3-rc6-tp520-btrfs-trim+',
  '3.19.3-a7-tp521-btrfs-trim+',
  '3.19.3',
  '3.19.0-rc7-tp520+',
  '3.10',
  '3.9',
  '3.3',
  '2.6',
  ''
];

(4.20.0-rc6 wins against 4.20.0 which is expected since -rc6 could also
be a usual CONFIG_LOCALVERSION string)


HTH,
Thomas


 Thanks for reporting,
 Thomas
 
 
 Thanks,
 Martin




 -- Package-specific info:
 needrestart output:
 Your outdated processes:
 akonadi_agent_l[2501, 2532, 2502, 2515], yeah I know…

 checkrestart output:


 -- System Information:
 Debian Release: 8.0
   APT prefers unstable
   APT policy: (500, 'unstable'), (200, 'experimental')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386

 Kernel: Linux 4.0.0-rc6-tp520-btrfs-trim+ (SMP w/4 CPU cores; PREEMPT)
 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: sysvinit (via /sbin/init)

 Versions of packages needrestart depends on:
 ii  dpkg   1.17.24
 ii  libmodule-find-perl0.12-1
 ii  libmodule-scandeps-perl1.16-1
 ii  libproc-processtable-perl  0.51-1
 ii  libsort-naturally-perl 1.03-1
 ii  libterm-readkey-perl   2.32-1+b1
 ii  perl   5.20.2-3

 needrestart recommends no packages.

 Versions of packages needrestart suggests:
 pn  libnotify-bin  none

 -- no debconf information

 


-- 

::  WWW: http://fiasko-nw.net/~thomas/  ::
   :::  Jabber:   xmpp:tho...@jabber.fiasko-nw.net  :::
::  flickr:  http://www.flickr.com/photos/laugufe/  ::


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running

2015-04-01 Thread Martin Steigerwald 
Package: needrestart
Version: 2.0-1
Severity: normal

Dear Maintainer,

needrestart warns me:

 ┌─┤ Pending kernel upgrade ├─┐
 ││
 │ Newer kernel available │
 ││
 │ The currently running kernel version is│
 │ 4.0.0-rc6-tp520-btrfs-trim+ which is not the expected kernel   │
 │ version 3.19.0-rc7-tp520+. │
 ││
 │ Restarting the system to load the new kernel will not be handled   │
 │ automatically, so you should consider rebooting.   │
 ││
 │   Ok │
 ││
 └┘

Yet, I have:

martin@merkaba:~ cat /proc/version
Linux version 4.0.0-rc6-tp520-btrfs-trim+ (martin@merkaba) (gcc version 4.9.2 
(Debian 4.9.2-10) ) #23 SMP PREEMPT Mon Mar 30 10:47:01 CEST 2015

martin@merkaba:~ dpkg -l | grep linux-image | cut -c1-70
ii  linux-image-3.16-2-amd643.16.3-2
ii  linux-image-3.18.0-tp5201
ii  linux-image-3.19.0-rc7-tp520+   1
ii  linux-image-4.0.0-rc6-tp520-btrfs-trim+ 1


Expected results:
No warning when installed kernel is already up and running.



Idea:

Maybe it gets confused by the + in kernel version? It may be that it sees
this as part of a regular expression. Don´t remember whether I had the
same issue with the 3.19-rc7 version which also has a +.

Kernels are built by make-kpkg from kernel-package 13.014+nmu1, which seems
to add the + on versions patched manually (so that they diff from the git
checkout).

Thanks,
Martin




-- Package-specific info:
needrestart output:
Your outdated processes:
akonadi_agent_l[2501, 2532, 2502, 2515], yeah I know…

checkrestart output:


-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-rc6-tp520-btrfs-trim+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages needrestart depends on:
ii  dpkg   1.17.24
ii  libmodule-find-perl0.12-1
ii  libmodule-scandeps-perl1.16-1
ii  libproc-processtable-perl  0.51-1
ii  libsort-naturally-perl 1.03-1
ii  libterm-readkey-perl   2.32-1+b1
ii  perl   5.20.2-3

needrestart recommends no packages.

Versions of packages needrestart suggests:
pn  libnotify-bin  none

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running

2015-04-01 Thread Thomas Liske 
severity 781657 important
tags 781657 pending,upstream
thanks


Hi Martin,

On 04/01/2015 12:21 PM, Martin Steigerwald wrote:
 Maybe it gets confused by the + in kernel version? It may be that it sees
 this as part of a regular expression. Don´t remember whether I had the
 same issue with the 3.19-rc7 version which also has a +.
 
 Kernels are built by make-kpkg from kernel-package 13.014+nmu1, which seems
 to add the + on versions patched manually (so that they diff from the git
 checkout).

the + should not be a problem. I've created a small test bed using the
version comparission from needrestart (which is based on Sort::Naturally):

$VAR1 = [
  '4.20.0-rc6-tp520-btrfs-trim+',
  '4.20.0',
  '4.19.0-rc6-tp520-btrfs-trim+',
  '4.19.0',
  '4.10',
  '3.19.3-rc6-tp520-btrfs-trim+',
  '3.19.3',
  '3.19.0-rc7-tp520+',
  '3.10',
  '4.9',
  '4.4.0-foo',
  '4.4.0',
  '4.0.0-rc6-tp520-btrfs-trim+',
  '4.0.0',
  '4.0',
  '3.9',
  '3.3',
  '2.6'
];

The expected kernel version reported by needrestart is the first one...
I need to review why i.e. 4.9 looses against 3.10.


Thanks for reporting,
Thomas


 Thanks,
 Martin
 
 
 
 
 -- Package-specific info:
 needrestart output:
 Your outdated processes:
 akonadi_agent_l[2501, 2532, 2502, 2515], yeah I know…
 
 checkrestart output:
 
 
 -- System Information:
 Debian Release: 8.0
   APT prefers unstable
   APT policy: (500, 'unstable'), (200, 'experimental')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 4.0.0-rc6-tp520-btrfs-trim+ (SMP w/4 CPU cores; PREEMPT)
 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: sysvinit (via /sbin/init)
 
 Versions of packages needrestart depends on:
 ii  dpkg   1.17.24
 ii  libmodule-find-perl0.12-1
 ii  libmodule-scandeps-perl1.16-1
 ii  libproc-processtable-perl  0.51-1
 ii  libsort-naturally-perl 1.03-1
 ii  libterm-readkey-perl   2.32-1+b1
 ii  perl   5.20.2-3
 
 needrestart recommends no packages.
 
 Versions of packages needrestart suggests:
 pn  libnotify-bin  none
 
 -- no debconf information
 

-- 

::  WWW: http://fiasko-nw.net/~thomas/  ::
   :::  Jabber:   xmpp:tho...@jabber.fiasko-nw.net  :::
::  flickr:  http://www.flickr.com/photos/laugufe/  ::
#!/usr/bin/perl

use Data::Dumper;
use Sort::Naturally;

my @v = reverse nsort qw(
3.19.3
3.19.3-rc6-tp520-btrfs-trim+
3.3
2.6
4.0
4.0.0
4.4.0
4.4.0-foo
4.19.0
4.20.0
4.0.0-rc6-tp520-btrfs-trim+
4.20.0-rc6-tp520-btrfs-trim+
4.19.0-rc6-tp520-btrfs-trim+
3.19.0-rc7-tp520+
3.10
3.9
4.10
4.9
);
print Dumper(\@v);