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

Bug#670070: marked as done (nmu: dolfin_1.0.0-4)



Your message dated Fri, 27 Apr 2012 19:02:51 +0100
with message-id <1335549771.4844.0.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#670070: nmu: dolfin_1.0.0-4
has caused the Debian Bug report #670070,
regarding nmu: dolfin_1.0.0-4
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.)


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

Dear Release Team,

Subsequent to the upload of armadillo 3, dolfin needs a rebuild.

nmu dolfin_1.0.0-4 . ALL . -m "Rebuild against armadillo (>= 1:3.0.1+dfsg)"

gdal also needs a rebuild, but the version affected is only in
experimental now, so I guess that is not of much concern at the moment?

Thanks.

Kumar

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
Kumar Appaiah



--- End Message ---
--- Begin Message ---
On Sun, 2012-04-22 at 12:44 -0500, Kumar Appaiah wrote:
> Subsequent to the upload of armadillo 3, dolfin needs a rebuild.
> 
> nmu dolfin_1.0.0-4 . ALL . -m "Rebuild against armadillo (>= 1:3.0.1+dfsg)"

Scheduled.

> gdal also needs a rebuild, but the version affected is only in
> experimental now, so I guess that is not of much concern at the moment?

It's not relevant for testing migration, but we can schedule binNMUs in
experimental as well if you'd prefer.

Regards,

Adam



--- End Message ---

Reply to: