walters reported a new issue against the project: `atomic-wg` that you are following:
``
https://kojipkgs.fedoraproject.org/compose/rawhide/latest-Fedora-Rawhide/lo…
```
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/pylorax/ltmpl.py", line 56, in parse
textbuf = template.render(**variables)
File "/usr/lib/python3.6/site-packages/mako/template.py", line 462, in render
return runtime._render(self, self.callable_, args, data)
File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 838, in _render
**_kwargs_for_callable(callable_, data))
File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 873, in _render_context
_exec_template(inherit, lclcontext, args=args, kwargs=kwargs)
File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 899, in _exec_template
callable_(context, *args, **kwargs)
TypeError: render_body() missing 1 required positional argument: 'root'
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/252
We decided to cancel the meeting today 2017-05-31 as many
people were absent.
I opened two new tickets that might be of interest:
- talk/workshop proposals for Flock
- https://pagure.io/atomic-wg/issue/279
- Fedora 26 Atomic/Cloud Test Day
- https://pagure.io/atomic-wg/issue/280
See you all at next week's meeting!
Dusty
Hi,
If I understand correctly, in its current state, F26 AH will
be shipping with the atomic package which added the
rpm-build deps. The update that removes it again is blocked
in testing:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-ac1919a04b
Double-checking the current state:
$ ostree remote add fedora-26 --no-gpg-verify https://kojipkgs.fedoraproject.org/atomic/26/
$ ostree pull fedora-26 --subpath=/usr/share/rpm --depth=0 fedora/26/x86_64/atomic-host
$ ostree checkout -U --subpath=/usr/share/rpm fedora-26:fedora/26/x86_64/atomic-host tmp/rpmdb-26
$ rpm -qa --dbpath $PWD/tmp/rpmdb-26 | grep -E '(rpm-build|gdb)'
gdb-headless-7.12.50.20170226-4.fc26.x86_64
rpm-build-libs-4.13.0.1-4.fc26.x86_64
rpm-build-4.13.0.1-4.fc26.x86_64
gdbm-1.13-1.fc26.x86_64
If this is what the F26 AH deliverables will be based on,
then would it be possible to justify a freeze exception out
of this? It's a pretty big wart on a new AH release, esp.
since the motto is that we're a streamlined OS, though it's
obviously not a critical release blocker.
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2017-05-31 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/
rtnpro added a new comment to an issue you are following:
``
@dustymabe did anyone have time to review the above changes?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/160
jorti reported a new issue against the project: `atomic-wg` that you are following:
``
I just launch an unmodified fedora/25-atomic-host box and I get the error that it cannot create the /vagrant synced dir.
```
$ vagrant up
Bringing machine 'default' up with 'libvirt' provider...
==> default: Creating image (snapshot of base box volume).
==> default: Creating domain with the following settings...
==> default: -- Name: mail-server_default
==> default: -- Domain type: kvm
==> default: -- Cpus: 1
==> default: -- Memory: 512M
==> default: -- Management MAC:
==> default: -- Loader:
==> default: -- Base box: fedora/25-atomic-host
==> default: -- Storage pool: default
==> default: -- Image:
/var/lib/libvirt/images/mail-server_default.img (41G)
==> default: -- Volume Cache: default
==> default: -- Kernel:
==> default: -- Initrd:
==> default: -- Graphics Type: vnc
==> default: -- Graphics Port: 5900
==> default: -- Graphics IP: 127.0.0.1
==> default: -- Graphics Password: Not defined
==> default: -- Video Type: cirrus
==> default: -- Video VRAM: 9216
==> default: -- Keymap: en-us
==> default: -- TPM Path:
==> default: -- INPUT: type=mouse, bus=ps2
==> default: -- Command line :
==> default: Creating shared folders metadata...
==> default: Starting domain.
==> default: Waiting for domain to get an IP address...
==> default: Waiting for SSH to become available...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Configuring and enabling network interfaces...
==> default: Rsyncing folder: /home/juan/Vagrant/mail-server/ => /vagrant
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p /vagrant
Stdout from the command:
Stderr from the command:
mkdir: cannot create directory ‘/vagrant’: Operation not permitted
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/181
ausil added a new comment to an issue you are following:
``
I think /pub/fedora/linux/updates/##/CloudImages/ should be fine. but it may be that /pub/alt/updates/##/CloudImages/ is more appropriate due to less usage
``
To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/138
ausil added a new comment to an issue you are following:
``
@mattdm today we blindly build new cloud images every day. if there was no updates in the last day we should not build them. but over a month, I would be shocked if we did not have changes.
``
To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/138