Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 14 Feb 2020 16:37:08 -0800
Source: cloud-init
Architecture: source
Version: 19.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cloud Team
Changed-By: Noah Meyerhans
Closes: 866613
Changes:
cloud-init_19.4-1_source.changes uploaded successfully to localhost
along with the files:
cloud-init_19.4-1.dsc
cloud-init_19.4.orig.tar.gz
cloud-init_19.4-1.debian.tar.xz
cloud-init_19.4-1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Sat, 15 Feb 2020 01:04:14 +
with message-id
and subject line Bug#866613: fixed in cloud-init 19.4-1
has caused the Debian Bug report #866613,
regarding cloud-init: Adding Apache v2 license to debian/copyright
to be marked as done.
This means that you claim that the problem
On Fri, Jun 30, 2017 at 02:14:00PM +, Joonas Kylmälä wrote:
> We need to also take care of asking permission from the authors of
> Debian patches if they can be used under Apache v2 license.
I don't think there's anything copyrightable in any of those
contributions. Note that none of the
Processing commands for cont...@bugs.debian.org:
> fixed 929388 18.3-4
Bug #929388 {Done: Noah Meyerhans } [cloud-init] cloud-init:
Incorrect datasource name
There is no source info for the package 'cloud-init' at version '18.3-4' with
architecture ''
Unable to make a source version for version
Processing commands for cont...@bugs.debian.org:
> close 929388
Bug #929388 [cloud-init] cloud-init: Incorrect datasource name
Marked Bug as done
> fixed 929388 debian/18.3-4
Bug #929388 {Done: Noah Meyerhans } [cloud-init] cloud-init:
Incorrect datasource name
The source debian and version
Processing commands for cont...@bugs.debian.org:
> close 926527
Bug #926527 [cloud-init] cloud-init: new upstream version 18.5 available
Marked Bug as done
> fixed 926527 19.2-1
Bug #926527 {Done: Noah Meyerhans } [cloud-init] cloud-init:
new upstream version 18.5 available
Marked as fixed in
Package: cloud.debian.org
Severity: normal
Dear Maintainer,
I cannot start a vagrant LXC-box for 'debian/buster64', but succeed to
start the 'debian/stretch64' box. The error message leads me to believe
there is something wrong in the LXC config of the buster box.
Vagrant box: debian/buster64
On 2/13/20 12:44 PM, Christian Tramnitz wrote:
> Is there any progress in getting 19.3 into stable? I can see it was not
> part of the Buster 10.3 release.
> If this takes any longer I'd suggest to backport the initially mentioned
> patch.
>
>
> BR,
> Christian
We currently don't have any
