[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#928965: marked as done (unblock: lsb/10.2019051400)

Your message dated Sun, 26 May 2019 13:58:26 +0100
with message-id <20190526125826.GA13805@powdarrmonkey.net>
and subject line Re: Bug#928965: unblock: lsb/10.2019051400
has caused the Debian Bug report #928965,
regarding unblock: lsb/10.2019051400
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.)


-- 
928965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928965
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

I hereby request an upload authorization towards an unblock for package lsb
10.2019051400, which was not uploaded yet.

lsb (10.2019051400) unstable; urgency=medium

  [ Harald Dunkel ]
  * pidofproc: use "pidof -c" to avoid pidofproc results from containers or chroots
    (Closes: #888743)

 -- Didier Raboud <odyx@debian.org>  Tue, 14 May 2019 08:50:39 +0200

It would be exactly identical as 10.2019032400 from experimental, uploaded on
March 24, and for which no regressions have been reported. It would fix
src:lsb important bug #888743 for buster.

The full debdiff is attached.

Thanks for your consideration, cheers,
        OdyX

unblock lsb/10.2019051400

diff -Nru lsb-10.2019031300/debian/changelog lsb-10.2019051400/debian/changelog
--- lsb-10.2019031300/debian/changelog	2019-03-13 21:42:26.000000000 +0100
+++ lsb-10.2019051400/debian/changelog	2019-05-14 08:50:39.000000000 +0200
@@ -1,3 +1,11 @@
+lsb (10.2019051400) unstable; urgency=medium
+
+  [ Harald Dunkel ]
+  * pidofproc: use "pidof -c" to avoid pidofproc results from containers or chroots
+    (Closes: #888743)
+
+ -- Didier Raboud <odyx@debian.org>  Tue, 14 May 2019 08:50:39 +0200
+
 lsb (10.2019031300) unstable; urgency=low
 
   [ Dmitry Bogatov ]
diff -Nru lsb-10.2019031300/init-functions lsb-10.2019051400/init-functions
--- lsb-10.2019031300/init-functions	2019-03-13 21:42:26.000000000 +0100
+++ lsb-10.2019051400/init-functions	2019-05-14 08:50:39.000000000 +0200
@@ -107,7 +107,7 @@
        # pid file doesn't exist, try to find the pid nevertheless
        if [ -x /bin/pidof ] && [ ! "$specified" ]; then
          status="0"
-         /bin/pidof -o %PPID -x $1 || status="$?"
+         /bin/pidof -c -o %PPID -x $1 || status="$?"
          if [ "$status" = 1 ]; then
              return 3 # program is not running
          fi

--- End Message ---
--- Begin Message --- 
On Fri, May 17, 2019 at 08:59:51AM +0200, Didier 'OdyX' Raboud wrote:
> Control: tags -1 -moreinfo
> 
> Le mardi, 14 mai 2019, 19.42:42 h CEST Jonathan Wiltshire a écrit :
> > Please go ahead and remove the moreinfo tag from this bug when it is ready
> > to be unblocked.
> 
> Uploaded, built, piuparts ran; removing the moreinfo tag.
> 
> (Autopackage tests in progress for _many_ packages).
> 
> Cheers, and thanks for your consideration,
> 
>     OdyX

Unblocked; thanks.

-- 
Jonathan Wiltshire                                      jmw@debian.org
Debian Developer                         http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

--- End Message ---
Reply to: