Package: packer
Version: 0.10.2+dfsg-6
Severity: wishlist
Tags: upstream
Hello,
Packer recently released v1.1.0:
https://github.com/hashicorp/packer/blob/v1.1.0/CHANGELOG.md
One of the really nice things about this version is that it now supports
builds for `lxc` and `lxd`. Is work already
Package: ruby-gdk3
Version: 3.1.0-1
Severity: grave
Justification: renders package unusable
Hello there,
I was attempting to make a small thing with gtk3 (via ruby) this morning
and ran into an error with one of its dependencies:
```
Package: ansible
Version: 2.3.1.0+dfsg-2
Severity: normal
Hello!
Currently ansible doesn't allow for updating roles via forced installs.
This affects all versions packaged by Debian. This is considered a bug
that was fixed upstream:
https://github.com/ansible/galaxy-issues/issues/249
Package: ansible
Version: 2.2.1.0-2
Severity: normal
Hello,
To summarize, my issue is the same as the one here:
https://github.com/ansible/ansible/issues/21026
Fixes have already been merged:
https://github.com/ansible/ansible/pull/21072
https://github.com/ansible/ansible/pull/23904 # mildly
Hi again,
> You are absolutelly right! Thanks for catching this.
> And thanks for fixing it upstream!
You're welcome! I enjoy fixing things.
> I fear it's too late for Stretch 9.0, but I'll see to include that into
> 9.1.
It appears that my endeavors have been foiled. Very well, then. Is there
Package: lxc
Version: 1:2.0.7-2
Hello,
Debian's packaged version of LXC currently is not able to stop systemd-based
containers as they have not responded to SIGPWR as of
https://github.com/lxc/lxc/commit/8eb62c245e9b67b451ba0766f3ecd7c6f2081d73 .
The appropriate way to stop systemd via a
>
> Thanks for your verifacation under qemu.
> So I'm going to release, as the autoremoval dealline is drawing very
> near..
>
> If you meet other issues, please report again.
>
> Cheers,
> --
> Roger Shimizu, GMT +9 Tokyo
> PGP/GPG: 4096R/6C6ACD6417B3ACB1
>
Hi
>
> Thanks for your verifacation under qemu.
> So I'm going to release, as the autoremoval dealline is drawing very
> near..
>
> If you meet other issues, please report again.
>
> Cheers,
> --
> Roger Shimizu, GMT +9 Tokyo
> PGP/GPG: 4096R/6C6ACD6417B3ACB1
>
Hi
>
> Thanks for your info!
> I pushed a commit to new branch fix_861282, that applied:
> ee5d13611fb8aca1f1014f9bcd65c18fffdd1b2b
> a0052fdb687f80ac07e67d7a0f39dcf3a66e32dd
>
> (https://anonscm.debian.org/cgit/pkg-go/packages/packer.git/log/?h=fix_861282)
>
> Please help
Thanks for the patch! I'm having a bit of trouble with the build:
"""
? github.com/mitchellh/packer/version[no test files]
dh_auto_test: go test -v -p 1 -timeout 30m -run
^Test([^M]|M[^u]|Mu[^x]|Mux[^B]|MuxB[^r]|MuxBr[^o]|MuxBro[^k]|MuxBrok[^e]|MuxBroke[^r])
Here are the four patches that are related to this issue:
https://github.com/hashicorp/packer/commit/28ee60d216e49d565d654443b57295ce37197db1
https://github.com/hashicorp/packer/commit/249cb690e04477582aefadf4350a087bf4e33a87
Hello,
Packer is still broken due to the ABI changes. AFAIK the patch that was
supposed to fix this does nothing to address use of the ABI in the builders.
Since then, there have also been some patches upstream (as Matt had mentioned)
to resolve the fallout due to the change:
12 matches
Mail list logo