binary:python3-awscrt is NEW.
binary:python3-awscrt is NEW.
source:aws-crt-python is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please
aws-crt-python_0.15.3+dfsg-1_amd64.changes uploaded successfully to localhost
along with the files:
aws-crt-python_0.15.3+dfsg-1.dsc
aws-crt-python_0.15.3+dfsg.orig.tar.gz
aws-crt-python_0.15.3+dfsg-1.debian.tar.xz
aws-crt-python_0.15.3+dfsg-1_amd64.buildinfo
Source-only uploads to NEW are not allowed.
binary:python3-awscrt is NEW.
source:aws-crt-python is NEW.
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
aws-crt-python_0.15.3+dfsg-1_source.changes uploaded successfully to localhost
along with the files:
aws-crt-python_0.15.3+dfsg-1.dsc
aws-crt-python_0.15.3+dfsg.orig.tar.gz
aws-crt-python_0.15.3+dfsg-1.debian.tar.xz
aws-crt-python_0.15.3+dfsg-1_source.buildinfo
Greetings,
Your
On Mon, Nov 28, 2022 at 10:24:42AM -0800, Ross Vandegrift wrote:
> > So, some time has passed and I haven't managed to work on this at all.
> > Given the number of packages involved and the dependencies between them,
> > I'm not optimistic that we'll be able to package them all individually
> > as
binary:overlayroot is NEW.
binary:overlayroot is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
Packages are routinely
cloud-initramfs-tools_0.18.debian9_amd64.changes uploaded successfully to
localhost
along with the files:
cloud-initramfs-tools_0.18.debian9.dsc
cloud-initramfs-tools_0.18.debian9.tar.xz
cloud-initramfs-dyn-netconf_0.18.debian9_all.deb
cloud-initramfs-growroot_0.18.debian9_all.deb
Hi,
As you may know, OpenStack has out-of-the-box UEFI secure boot support
(a bit more details: it needs a few tweaks in the image properties, the
ovmf package must be installed in the compute nodes, plus the compute
node must have the correct "trait" in OpenStack placement).
However, our
Hi Ross,
> Should we consider adding "Conflicts: firewalld" to cloud-init before
> the freeze? That's not optimal of course, but it'd prevent a user from
> ending up in this situation for now.
Is there a way to bypass "Conflicts" and install such packages anyway,
in case the user finds a way to
