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

Bug#859108: marked as done (unblock: mapdamage/2.0.6+dfsg-2)

Your message dated Thu, 30 Mar 2017 19:03:00 +0000
with message-id <dc2ce2c5-8d45-3a57-bb49-ce792b07ce8f@thykier.net>
and subject line Re: Bug#859108: unblock: mapdamage/2.0.6+dfsg-2
has caused the Debian Bug report #859108,
regarding unblock: mapdamage/2.0.6+dfsg-2
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.)


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

Please unblock package mapdamage

When the potential Outreachy student Nadiya Sitdykova started to work on
an autopkgtest she detected some issues in the packaging which are
described in bug #859090 and #859091.  Both describe that mapdamage is
not fully functional as is.  Nadiya worked hard to fix those issues
including fixing an upstream issue which was reported.

The attached debdiff includes the fixes and additionally the autopkgtest
proving the functionality of the package.

I did not reverted a spelling patch that was in Git before the
investigation started (debhelper 10 was reverted to match freeze
policy - so I hope this additional change not really addressing the
RC bugs is acceptable).

Kind regards and thanks for your release team work

       Andreas.

unblock mapdamage/2.0.6+dfsg-2

-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Andreas Tille:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Please unblock package mapdamage
> 
> When the potential Outreachy student Nadiya Sitdykova started to work on
> an autopkgtest she detected some issues in the packaging which are
> described in bug #859090 and #859091.  Both describe that mapdamage is
> not fully functional as is.  Nadiya worked hard to fix those issues
> including fixing an upstream issue which was reported.
> 
> The attached debdiff includes the fixes and additionally the autopkgtest
> proving the functionality of the package.
> 
> I did not reverted a spelling patch that was in Git before the
> investigation started (debhelper 10 was reverted to match freeze
> policy - so I hope this additional change not really addressing the
> RC bugs is acceptable).
> 
> Kind regards and thanks for your release team work
> 
>        Andreas.
> 
> unblock mapdamage/2.0.6+dfsg-2
> 
> [...]
> 

Hi,

@Nadiya: Many thanks for your work! :)

@Andreas: Thanks for reverting the dh 10 change.

I have unblocked the package; it is clearly in a much better state than
previously and I only had a minor remark.

In d/control, I noticed the following Recommends:

+         libopenblas-dev | [...] | libblas.so,
+         libopenblas-dev | [...] | liblapack.so
                                    ^^^^^^^^^^^^

There are no packages names like this (the lib*.so) AFAICT, so these are
redundant.  Please remove them in a future upload.

Thanks,
~Niels

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: