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

Bug#765950: marked as done (nmu: sflphone_1.4.1-0.1)



Your message dated Sun, 19 Oct 2014 15:40:33 +0100
with message-id <825a492be78c6b9ee204edfdb70fe157@hogwarts.powdarrmonkey.net>
and subject line Re: Bug#765950: nmu: sflphone_1.4.1-0.1
has caused the Debian Bug report #765950,
regarding nmu: sflphone_1.4.1-0.1
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.)


-- 
765950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765950
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: binnmu

Hi,

please rebuild sflphone/amd64, as the latest upload has been built on
a non-clean environment (with deb-multimedia packages, in particular).

nmu sflphone_1.4.1-0.1 . amd64 . -m "Rebuild in a clean environment."

Thanks,
-- 
Pino

--- End Message ---
--- Begin Message ---
On 2014-10-19 14:58, Pino Toscano wrote:
please rebuild sflphone/amd64, as the latest upload has been built on
a non-clean environment (with deb-multimedia packages, in particular).

nmu sflphone_1.4.1-0.1 . amd64 . -m "Rebuild in a clean environment."

Scheduled.

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

<directhex> i have six years of solaris sysadmin experience, from
            8->10. i am well qualified to say it is made from bonghits
			layered on top of bonghits

--- End Message ---

Reply to: