Your message dated Sat, 13 Mar 2021 15:30:39 +0100
with message-id <[email protected]>
and subject line Re: Bug#929214: release.debian.org - Add package constraint
for cloud images
has caused the Debian Bug report #929214,
regarding Add key package for cloud images
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 [email protected]
immediately.)
--
929214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929214
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Hi release team
To make your and our work easier, we would like to ask you to add a
package constraint for all the packages included into the official
Debianm cloud images.
>From what I read, the easiest way for you would be to specify a single
package as constraint, a package that depends on all the other binary
package we explicitely include in the images.
I intend to add one binary package per architecture we currently build
images for: amd64, arm64 and ppc64el. The dependencies will be arch
dependent and auto-generated from our own list.
The package would look like this:
| Package: debian-cloud-images-packages
| Architecture: amd64
| Depends: apparmor, awscli, chrony, cloud-init, cloud-initramfs-growroot,
google-compute-engine, grub-cloud-amd64, grub-pc, libpam-systemd,
linux-image-amd64, linux-image-cloud-amd64, openssh-server, python,
python-boto, python3-boto, sudo, unattended-upgrades, waagent
Please acknowledge that such a package would be okay for using as
constraint. After that I'll upload that change.
Regards,
Bastian
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi Bastian,
On Fri, Mar 12, 2021 at 08:14:58AM +0100, Bastian Blank wrote:
> > > Please acknowledge that such a package would be okay for using as
> > > constraint. After that I'll upload that change.
> > If you create such a package, having a binary per architecture as you
> > describe, should do what you want. It can be added to the list as soon as it
> > is in testing.
>
> The binary package is in testing since some time. Please add it to the
> key packages list.
Added.
FYI this currently adds the following packages as key packages:
awscli
chrony
cloud-init
cloud-initramfs-tools
cloud-utils
debian-cloud-images
fai
google-compute-image-packages
grub-cloud
ifenslave
libcloud
libextutils-cchecker-perl
libfile-lchown-perl
liblinux-lvm-perl
python-bcdoc
python-boto
python-httpretty
python-lockfile
python-marshmallow
python-rednose
python-sure
python-termstyle
vlan
Cheers,
Ivo
--- End Message ---
