Bug#858008: [pkg-go] Bug#858008: hugo FTBFS: cannot use (type **jwalterweatherman.Feedback) as type logPrinter in field value

[Dr. Tobias Quathamer]

Am 16.04.2017 um 15:53 schrieb Dr. Tobias Quathamer:

Once the upload has been accepted into unstable, I'll file an unblock
request for jwalterweatherman.


Done: 




signature.asc
Description: OpenPGP digital signature

Bug#858008: [pkg-go] Bug#858008: hugo FTBFS: cannot use (type **jwalterweatherman.Feedback) as type logPrinter in field value

[Dr. Tobias Quathamer]

Am 13.04.2017 um 17:46 schrieb Ivo De Decker:

Can you please revert this change? We want to rebuild hugo, because it has
outdated built-using, but this cannot be done in unstable (because of this
bug), but it also cannot be done in testing, as the archive doesn't allow the
version in testing to be newer than unstable. A revert will allow the build in
unstable (and migration to testing).


Dear all,

I've just uploaded the previous version of the jwalterweatherman 
package, so that hugo can be build again in sid (and therefore migrate 
to testing).


Once the upload has been accepted into unstable, I'll file an unblock 
request for jwalterweatherman.


Regarding the package hugo, I think it should be enough to request 
binNMUs as soon as the CVE in golang-go.crypto has been fixed, right?


See https://bugs.debian.org/859655 for details.

Regards,
Tobias




signature.asc
Description: OpenPGP digital signature

Bug#858008: [pkg-go] Bug#858008: hugo FTBFS: cannot use (type **jwalterweatherman.Feedback) as type logPrinter in field value

[Ivo De Decker]

Hi,

On Fri, Mar 24, 2017 at 10:09:14AM -0600, Anthony Fok wrote:
> On Sun, Mar 19, 2017 at 8:21 AM, Dr. Tobias Quathamer  
> wrote:
> > control: tag -1 sid
> > thanks
> >
> > Hi,
> >
> > thanks for the bug report. However, hugo still builds fine in a stretch
> > chroot, this bug only applies to unstable.
> >
> > It was triggered by the recent upload of a new upstream version of
> > golang-github-spf13-jwalterweatherman.
> >
> > @Anthony, did you have a specific reason to upload the new upstream version?
> > The changelog does not mention anything, and we've been in the freeze for
> > quite some time already.
> 
> My apologies.  It was my attempt at getting Hugo 0.19 into Debian sid,
> but didn't get it done all the way.
> 
> > If there would be a real release critical bug in hugo, now it could not be
> > fixed with a simple upload to unstable, which is very unfortunate.
> 
> You are right.  I should have been more prudent and avoid making such
> uploads, especially an incomplete one, during a freeze.

Can you please revert this change? We want to rebuild hugo, because it has
outdated built-using, but this cannot be done in unstable (because of this
bug), but it also cannot be done in testing, as the archive doesn't allow the
version in testing to be newer than unstable. A revert will allow the build in
unstable (and migration to testing).

Cheers,

Ivo

Bug#858008: [pkg-go] Bug#858008: hugo FTBFS: cannot use (type **jwalterweatherman.Feedback) as type logPrinter in field value

[Anthony Fok]

Thank you Adrian and Dr. Tobias.

On Sun, Mar 19, 2017 at 8:21 AM, Dr. Tobias Quathamer  wrote:
> control: tag -1 sid
> thanks
>
> Hi,
>
> thanks for the bug report. However, hugo still builds fine in a stretch
> chroot, this bug only applies to unstable.
>
> It was triggered by the recent upload of a new upstream version of
> golang-github-spf13-jwalterweatherman.
>
> @Anthony, did you have a specific reason to upload the new upstream version?
> The changelog does not mention anything, and we've been in the freeze for
> quite some time already.

My apologies.  It was my attempt at getting Hugo 0.19 into Debian sid,
but didn't get it done all the way.

> If there would be a real release critical bug in hugo, now it could not be
> fixed with a simple upload to unstable, which is very unfortunate.

You are right.  I should have been more prudent and avoid making such
uploads, especially an incomplete one, during a freeze.

Best regards,
Anthony

Bug#858008: [pkg-go] Bug#858008: hugo FTBFS: cannot use (type **jwalterweatherman.Feedback) as type logPrinter in field value

[Dr. Tobias Quathamer]

control: tag -1 sid
thanks

Am 17.03.2017 um 10:45 schrieb Adrian Bunk:

Source: hugo
Version: 0.18.1-1
Severity: serious

https://buildd.debian.org/status/package.php?p=hugo=sid

...
github.com/spf13/hugo/livereload
github.com/spf13/hugo/hugofs
github.com/spf13/hugo/helpers
# github.com/spf13/hugo/helpers
src/github.com/spf13/hugo/helpers/general.go:250: cannot use 
 (type **jwalterweatherman.Feedback) as type 
logPrinter in field value:
**jwalterweatherman.Feedback does not implement logPrinter (missing 
Println method)
dh_auto_build: go install -v -p 4 github.com/spf13/hugo 
github.com/spf13/hugo/bufferpool github.com/spf13/hugo/commands 
github.com/spf13/hugo/create github.com/spf13/hugo/helpers 
github.com/spf13/hugo/hugofs github.com/spf13/hugo/hugolib 
github.com/spf13/hugo/livereload github.com/spf13/hugo/parser 
github.com/spf13/hugo/source github.com/spf13/hugo/target 
github.com/spf13/hugo/tpl github.com/spf13/hugo/transform 
github.com/spf13/hugo/utils github.com/spf13/hugo/watcher returned exit code 2
debian/rules:13: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2


Hi,

thanks for the bug report. However, hugo still builds fine in a stretch 
chroot, this bug only applies to unstable.


It was triggered by the recent upload of a new upstream version of 
golang-github-spf13-jwalterweatherman.


@Anthony, did you have a specific reason to upload the new upstream 
version? The changelog does not mention anything, and we've been in the 
freeze for quite some time already.


If there would be a real release critical bug in hugo, now it could not 
be fixed with a simple upload to unstable, which is very unfortunate.


Regards,
Tobias




signature.asc
Description: OpenPGP digital signature