Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades

2013-10-14 Thread Matthias Klumpp
Hi! 2013/8/22 Paul Wise p...@debian.org: On Thu, Aug 22, 2013 at 11:17 AM, Matthias Klumpp wrote: PackageKit can do that ;-) It has a plugin to check for shared libraries in use, I just haven't tested in yet. It should show the names of services which need to be restarted after a security

Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades

2013-10-14 Thread Paul Wise
On Tue, Oct 15, 2013 at 12:21 AM, Matthias Klumpp wrote: It just checks that - I wanted it to look for upload-priorities in Debian changelogs some time ago, but doing that was just way too slow. Higher upload priorities doesn't indicate a security fix. It could be an RC bug fix or certain

Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades

2013-10-14 Thread Matthias Klumpp
2013/10/14 Paul Wise p...@debian.org: On Tue, Oct 15, 2013 at 12:21 AM, Matthias Klumpp wrote: It just checks that - I wanted it to look for upload-priorities in Debian changelogs some time ago, but doing that was just way too slow. Higher upload priorities doesn't indicate a security fix.

Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades

2013-08-22 Thread Tollef Fog Heen
]] Patrick Matthäi needrestart checks which daemons need to be restarted after library upgrades. It is inspired by checkrestart(1) from the debian-goodies package. It does not rely on lsof as checkrestart does. Why not just improve checkrestart rather than offering an alternative? --

Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades

2013-08-22 Thread Chow Loong Jin
On Thu, Aug 22, 2013 at 09:20:32AM +0200, Tollef Fog Heen wrote: ]] Patrick Matthäi needrestart checks which daemons need to be restarted after library upgrades. It is inspired by checkrestart(1) from the debian-goodies package. It does not rely on lsof as checkrestart does. Why

Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades

2013-08-22 Thread Konstantin Khomoutov
On Thu, 22 Aug 2013 09:20:32 +0200 Tollef Fog Heen tfh...@err.no wrote: needrestart checks which daemons need to be restarted after library upgrades. It is inspired by checkrestart(1) from the debian-goodies package. It does not rely on lsof as checkrestart does. Why not just improve

Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades

2013-08-22 Thread Paul Wise
On Thu, Aug 22, 2013 at 9:58 AM, Konstantin Khomoutov wrote: By the way, I have always been puzzled with checkrestart being a part of the package containing a set of random tools. I mean, the discoverability of checkrestart is exactly zero, and one have to stumble on a random blog post to

Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades

2013-08-22 Thread Matthias Klumpp
2013/8/22 Paul Wise p...@debian.org: On Thu, Aug 22, 2013 at 9:58 AM, Konstantin Khomoutov wrote: By the way, I have always been puzzled with checkrestart being a part of the package containing a set of random tools. I mean, the discoverability of checkrestart is exactly zero, and one have

Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades

2013-08-22 Thread Sebastian Heinlein
Am 2013-08-22 10:03, schrieb Paul Wise: On Thu, Aug 22, 2013 at 9:58 AM, Konstantin Khomoutov wrote: By the way, I have always been puzzled with checkrestart being a part of the package containing a set of random tools. I mean, the discoverability of checkrestart is exactly zero, and one

Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades

2013-08-22 Thread Paul Wise
On Thu, Aug 22, 2013 at 11:17 AM, Matthias Klumpp wrote: PackageKit can do that ;-) It has a plugin to check for shared libraries in use, I just haven't tested in yet. It should show the names of services which need to be restarted after a security update. Cool. This info is at least shown

Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades

2013-08-14 Thread Patrick Matthäi
Package: wnpp Severity: wishlist Owner: Patrick Matthäi pmatth...@debian.org * Package name: needrestart Version : 0.2 Upstream Author : Thomas Liske tho...@fiasko-nw.net * URL : https://github.com/liske/needrestart * License : GPL2+ Programming Lang: Perl