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

Bug#856069: marked as done (unblock vagrant-libvirt/0.0.37-1)

Your message dated Sat, 25 Feb 2017 07:27:00 +0000
with message-id <da87dc2b-14af-950d-13be-f69931b45f6a@thykier.net>
and subject line Re: Bug#856069: unblock vagrant-libvirt/0.0.37-1
has caused the Debian Bug report #856069,
regarding unblock vagrant-libvirt/0.0.37-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.)


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

0.0.37 is the first upstream release since the git version that is
already included in stretch.  0.0.37 fixes a number of key bugs
including #855700 "vagrant package command fails".  0.0.37 also adds a
new dependency, which can safely be added to Recommends:.  0.0.37-1 is
already in unstable.

The hard part about this update is that the debdiff is large, even
though the actual code changes are quite small.  Between
0.0.36.git20161125.a894dc0 and 0.0.37, upstream ran a ruby linter on the
code which found some of the key bugs that we want fixed.  It also
normalized the code for spacing, uses of quotes, if block structure,
etc.  Even though the diff is long, 0.0.37 is the version that received
lots of testing, and is the version that fixed the specific issues that
we were having.  Also, to fix an earlier bug, a git snapshot was upload,
and that this new version has almost no functional changes with regards
to that git snapshot, according to Antonio Terceiro and I (see #855700).

The first attached debdiff is the full debdiff.  The second removes the
whitespace only changes, making it a quarter smaller.

Attachment: vagrant-libvirt_0.0.37-1.debdiff.bz2
Description: application/bzip

Attachment: vagrant-libvirt_0.0.37-1.ignore-space.debdiff.bz2
Description: application/bzip


--- End Message ---
--- Begin Message --- 
Hans-Christoph Steiner:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Please unblock package vagrant-libvirt
> 
> 0.0.37 is the first upstream release since the git version that is
> already included in stretch.  0.0.37 fixes a number of key bugs
> including #855700 "vagrant package command fails".  0.0.37 also adds a
> new dependency, which can safely be added to Recommends:.  0.0.37-1 is
> already in unstable.
> 
> The hard part about this update is that the debdiff is large, even
> though the actual code changes are quite small.  Between
> 0.0.36.git20161125.a894dc0 and 0.0.37, upstream ran a ruby linter on the
> code which found some of the key bugs that we want fixed.  It also
> normalized the code for spacing, uses of quotes, if block structure,
> etc.  Even though the diff is long, 0.0.37 is the version that received
> lots of testing, and is the version that fixed the specific issues that
> we were having.  Also, to fix an earlier bug, a git snapshot was upload,
> and that this new version has almost no functional changes with regards
> to that git snapshot, according to Antonio Terceiro and I (see #855700).
> 
> The first attached debdiff is the full debdiff.  The second removes the
> whitespace only changes, making it a quarter smaller.
> 

Unblocked, thanks.

~Niels

--- End Message ---
Reply to: