Your message dated Sat, 06 Jun 2015 13:11:11 +0100 with message-id <1433592671.2987.12.camel@adam-barratt.org.uk> and subject line Fix released with 8.1 point release has caused the Debian Bug report #787008, regarding pu: package needrestart/1.2-8+deb8u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 787008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787008 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: pu: package needrestart/1.2-8+deb8u1
- From: Patrick Matthäi <pmatthaei@debian.org>
- Date: Wed, 27 May 2015 19:36:55 +0200
- Message-id: <20150527173655.13384.51922.reportbug@srv1.linux-dev.org>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: pu Hello release team, needrestart=1.2-8+deb8u1 fixes two issues where Perl warnings and errors occur and especially it fixes #781657, where the used Perl module fails to sort the kernel version correctly (3.aa.bb > 4.0).. Upstream decided to adopt the mechanism of Dpkg::Version to keep changes and dependencies in his code as minimal as possible. debdiff attached. -- System Information: Debian Release: 7.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: 781276-done@bugs.debian.org
- Cc: 781284-done@bugs.debian.org, 782900-done@bugs.debian.org, 783256-done@bugs.debian.org, 783404-done@bugs.debian.org, 783488-done@bugs.debian.org, 783489-done@bugs.debian.org, 783526-done@bugs.debian.org, 783722-done@bugs.debian.org, 783750-done@bugs.debian.org, 783811-done@bugs.debian.org, 783884-done@bugs.debian.org, 783973-done@bugs.debian.org, 784101-done@bugs.debian.org, 784178-done@bugs.debian.org, 784342-done@bugs.debian.org, 784383-done@bugs.debian.org, 784644-done@bugs.debian.org, 784714-done@bugs.debian.org, 784800-done@bugs.debian.org, 784801-done@bugs.debian.org, 784815-done@bugs.debian.org, 784816-done@bugs.debian.org, 784905-done@bugs.debian.org, 784943-done@bugs.debian.org, 784946-done@bugs.debian.org, 784962-done@bugs.debian.org, 784963-done@bugs.debian.org, 784964-done@bugs.debian.org, 784998-done@bugs.debian.org, 785154-done@bugs.debian.org, 785184-done@bugs.debian.org, 785201-done@bugs.debian.org, 785240-done@bugs.debian.org, 785254-done@bugs.debian.org, 785298-done@bugs.debian.org, 785301-done@bugs.debian.org, 785386-done@bugs.debian.org, 785478-done@bugs.debian.org, 785510-done@bugs.debian.org, 785523-done@bugs.debian.org, 785713-done@bugs.debian.org, 785718-done@bugs.debian.org, 786388-done@bugs.debian.org, 786389-done@bugs.debian.org, 786431-done@bugs.debian.org, 786513-done@bugs.debian.org, 786647-done@bugs.debian.org, 786720-done@bugs.debian.org, 786744-done@bugs.debian.org, 786811-done@bugs.debian.org, 786812-done@bugs.debian.org, 786856-done@bugs.debian.org, 786860-done@bugs.debian.org, 786863-done@bugs.debian.org, 786870-done@bugs.debian.org, 786912-done@bugs.debian.org, 786918-done@bugs.debian.org, 786922-done@bugs.debian.org, 786924-done@bugs.debian.org, 786982-done@bugs.debian.org, 787008-done@bugs.debian.org, 787014-done@bugs.debian.org, 787255-done@bugs.debian.org, 787260-done@bugs.debian.org, 787626-done@bugs.debian.org, 787636-done@bugs.debian.org
- Subject: Fix released with 8.1 point release
- From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Date: Sat, 06 Jun 2015 13:11:11 +0100
- Message-id: <1433592671.2987.12.camel@adam-barratt.org.uk>
Version: 8.1 Hi, The fix discussed in this bug was released to stable as part of the 8.1 point release earlier today. Regards, Adam
--- End Message ---