On Tue, Jan 31, 2023, at 9:10 PM, Major Hayden wrote:
> My team at Red Hat came up with the idea of a locator service that
> would gather data from upstream locations (AWS, Azure, GCP, and
> others), compile the image data into a common schema, and make it
> available for API calls and a web
walters commented on the pull-request: `Make the list of repos empty in the
default inherit chain` that you are following:
``
Yeah it's fine, again I'm not objecting. But I thought what we had with
fedmsg-atomic-composer before was a bit nicer in that it overrode both the
`ref` and the
walters commented on the pull-request: `Make the list of repos empty in the
default inherit chain` that you are following:
``
I'm not *opposed* to this but...again the reason I chose JSON was *precisely*
so that tools like pungi or whatever could easily override the `repos` field
dynamically.
walters commented on the pull-request: `Add secondary treefiles for updates and
update-test (F26)` that you are following:
``
Sure, seems sane to me. (Just to repeat though the reason I chose JSON is
precisely to allow tools to edit the treefile easily)
``
To reply, visit the link below or
walters commented on the pull-request: `manifest: Use 64 bit grub2 EFI` that
you are following:
``
For reference
https://pagure.io/workstation-ostree-config/c/805318e69551876faff5071acbe8d49000434973?branch=master
``
To reply, visit the link below or just reply to this email
walters merged a pull-request against the project: `fedora-atomic` that you are
following.
Merged pull-request:
``
manifest: Use 64 bit grub2 EFI
``
https://pagure.io/fedora-atomic/pull-request/85
___
cloud mailing list --
walters opened a new pull-request against the project: `fedora-atomic` that you
are following:
``
manifest: Use 64 bit grub2 EFI
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/85
___
cloud
walters opened a new pull-request against the project: `fedora-atomic` that you
are following:
``
manifest: Use 64 bit grub2 EFI
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/84
___
cloud
walters merged a pull-request against the project: `fedora-atomic` that you are
following.
Merged pull-request:
``
rawhide: add in dnsmasq since NM dropped the dep
``
https://pagure.io/fedora-atomic/pull-request/80
___
cloud mailing list --
walters commented on the pull-request: `rawhide: add in dnsmasq since NM
dropped the dep` that you are following:
``
LGTM.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/80
___
cloud mailing
walters merged a pull-request against the project: `fedora-atomic` that you are
following.
Merged pull-request:
``
f27: add in dnsmasq since NM dropped the dep
``
https://pagure.io/fedora-atomic/pull-request/81
___
cloud mailing list --
walters commented on the pull-request: `f27: add in dnsmasq since NM dropped
the dep` that you are following:
``
LGTM, thanks!
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/81
___
cloud
walters commented on the pull-request: `post: Re-instate systemd
ProtectHome/ProtectSystem and PrivateTmp` that you are following:
``
I think I got confused since I thought I saw a release but now I can't find it
in my email.I don't see it on
walters commented on the pull-request: `post: Re-instate systemd
ProtectHome/ProtectSystem and PrivateTmp` that you are following:
``
Cherry pick from master. To be merged right after the next F26AH release.
``
To reply, visit the link below or just reply to this email
walters opened a new pull-request against the project: `fedora-atomic` that you
are following:
``
post: Re-instate systemd ProtectHome/ProtectSystem and PrivateTmp
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/79
walters opened a new pull-request against the project: `fedora-atomic` that you
are following:
``
post: Re-instate systemd ProtectHome/ProtectSystem and PrivateTmp
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/78
walters opened a new pull-request against the project: `fedora-atomic` that you
are following:
``
manifest: Add microcode_ctl
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/77
___
cloud
walters opened a new pull-request against the project: `fedora-atomic` that you
are following:
``
manifest: Add microcode_ctl
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/76
___
cloud
walters canceled a pull-request against the project: `fedora-atomic` that you
are following.
Cancelled pull-request:
``
manifest: Add microcode_ctl
``
https://pagure.io/fedora-atomic/pull-request/69
___
cloud mailing list --
walters commented on the pull-request: `manifest: Add microcode_ctl` that you
are following:
``
Pushed, thanks!
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/69
___
cloud mailing list --
walters commented on the pull-request: `Branching f27 from rawhide` that you
are following:
``
It doesn't work for me:
```
rpm-ostree compose tree --repo=repo-build --cachedir=cache
fedora-atomic/fedora-atomic-host.json && ostree --repo=repo pull-local
repo-build && ostree --repo=repo summary
walters commented on the pull-request: `Branching f27 from rawhide` that you
are following:
``
Don't these repos need to be the pre-release version? Or does infra now offer
those repos before the bodhi enablement point?
``
To reply, visit the link below or just reply to this email
walters opened a new pull-request against the project: `fedora-atomic` that you
are following:
``
manifest: Add microcode_ctl
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/69
___
cloud
walters commented on the pull-request: `post: Work around LVM archival
conflicting with ostree` that you are following:
``
Yeah, but the priority for me dropped way way down since for Fedora now we
don't use devicemapper by default for Docker, and that makes LVM make backups
way less often.
``
walters added a new comment to an issue you are following:
``
Not quite - my plan is that anaconda would substitute `${basearch}` for values
passed to `ostreesetup.ref`, i.e. we'd use:
```
ostreesetup --nogpg --osname=fedora-atomic --remote=fedora-atomic
walters reported a new issue against the project: `atomic-wg` that you are
following:
``
In https://fedoramagazine.org/upcoming-fedora-atomic-lifecycle-changes/
and https://pagure.io/atomic-wg/issue/228
we did some handwaving about releases that IMO was very vague :smile:
Now that 26 is out,
walters added a new comment to an issue you are following:
``
Oh right, duh: https://pagure.io/fedora-kickstarts/pull-request/266
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/281
___
cloud mailing list
walters added a new comment to an issue you are following:
``
https://pagure.io/pungi-fedora/pull-request/296
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/301
___
cloud mailing list --
walters added a new comment to an issue you are following:
``
There are some tricky details here...is `$(uname -i`) actually equivalent to
the architecture name we use elsewhere? I *think* it is for ppc64 and aarch64,
but offhand I think one corner case is `i386` (RPM) vs kernel (`i686`).
I
walters merged a pull-request against the project: `fedora-atomic` that you are
following.
Merged pull-request:
``
manifest: Drop updates-testing by default
``
https://pagure.io/fedora-atomic/pull-request/66
___
cloud mailing list --
walters commented on the pull-request: `Rename treefile to match ref` that you
are following:
``
See
https://pagure.io/fedora-atomic-host-continuous/c/b1455b028ac48ff84773d3cf831bc18cfa48f6c8?branch=master
If you're going to delete the symlink, we need to check the Fedora CI work too.
``
To
walters opened a new pull-request against the project: `fedora-atomic` that you
are following:
``
manifest: Drop updates-testing by default
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/66
walters merged a pull-request against the project: `fedora-atomic` that you are
following.
Merged pull-request:
``
Rename treefile to match ref
``
https://pagure.io/fedora-atomic/pull-request/65
___
cloud mailing list --
walters commented on the pull-request: `Rename treefile to match ref` that you
are following:
``
LGTM, thanks.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/65
___
cloud mailing list --
walters added a new comment to an issue you are following:
``
This is
https://www.redhat.com/archives/anaconda-devel-list/2017-February/msg0.html
again.
Changing it to `--url="file:///ostree/repo` should fix it.
``
To reply, visit the link below or just reply to this email
walters added a new comment to an issue you are following:
``
https://koji.fedoraproject.org/koji/taskinfo?taskID=20464792
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/281
___
cloud mailing list --
walters added a new comment to an issue you are following:
``
We already discussed the rationale as an aside in the larger partitioning
discussion earlier. F27 AH defaults to XFS already; that's what Fedora Server
does, which also matches the downstream RHEL Atomic Host. The dynamic inodes
in
walters added a new comment to an issue you are following:
``
I swear we were defaulting to XFS before, but I may have been confused by the
fact that it's hardcoded in the cloud kickstart.
Any objections to backporting this to f26?
```
diff --git a/installclass_atomic.py
On Tue, Jul 11, 2017, at 12:28 PM, Dusty Mabe wrote:
>
> We will try to release blogs and documentation over the next few weeks
> to show you new features and guide how to upgrade your existing hosts.
We have this wiki page for the latter, I've updated it now:
On Sat, Jun 24, 2017, at 09:34 AM, Dusty Mabe wrote:
> happened again last night:
> https://kojipkgs.fedoraproject.org//work/tasks/7733/20127733/root.log
We landed some PRs upstream to help debug this, but they were hard to backport.
I just manually started a build of a git snapshot:
walters added a new comment to an issue you are following:
``
Docker patch
[committed](http://pkgs.fedoraproject.org/cgit/rpms/docker.git/commit/?id=78b777a086500b0fc4780e4bbdb1dec00b5f8a0f)
and [built](https://koji.fedoraproject.org/koji/buildinfo?buildID=910722).
``
To reply, visit the link
walters added a new comment to an issue you are following:
``
Thinking of this change as "3G → 15G by default" indeed is a good and simple
way to phrase it. It's not *entirely* accurate since we also need to factor in
the default size of the cloud images and the vagrant box. But it's a good
walters added a new comment to an issue you are following:
``
@vgoyal: Not quite; the AH storage is the same as Server, we only use up to
15G. For real baremetal machines, they'll have larger disks, and hence there
will be reserved space in the VG.
For cloud images, it's up to the operator;
walters commented on the pull-request: `manifest: Enable tmp-is-dir` that you
are following:
``
This one blocks on https://github.com/projectatomic/rpm-ostree/issues/820
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/62
walters opened a new pull-request against the project: `fedora-atomic` that you
are following:
``
Rename treefile to match ref
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/63
___
cloud
walters added a new comment to an issue you are following:
``
I tested the `20170615.n.0` FAH iso; it looks like we'll need this:
```
diff --git a/docker.spec b/docker.spec
index b654082..b170151 100644
--- a/docker.spec
+++ b/docker.spec
@@ -569,10 +569,14 @@ echo 'STORAGE_DRIVER=overlay2' >>
walters added a new comment to an issue you are following:
``
(It's worth noting here that flatpak which uses ostree as well has logic and
standards for separate `Locale` and `Debug` refs).
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/282
walters added a new comment to an issue you are following:
``
As far as dynamic locale installation: difficult but still doable. I think for
every treecompose we'd need to generate a new second ref like
`fedora/26/x86_64/locales/atomic-host`. And we'd need a new client side
command to
walters added a new comment to an issue you are following:
``
Current tree with locale subset (built locally)
```
/srv/walters/src/github/ostreedev/ostree-releng-scripts/print-commitsize repo
fedora/26/x86_64/atomic-host{^,}
fedora/26/x86_64/atomic-host^ =>
walters added a new comment to an issue you are following:
``
I'm going to do some work on this; though we're blocked a bit in testing by
[rawhide
issues](https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/56YB4HXBT7X2IC6TQUASKYRC22TEGGTZ/).
``
To reply, visit
walters opened a new pull-request against the project: `fedora-atomic` that you
are following:
``
manifest: Enable tmp-is-dir
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/62
___
cloud
walters added a new comment to an issue you are following:
``
Let's try to do rawhide first?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/230
___
cloud mailing list -- cloud@lists.fedoraproject.org
To
walters merged a pull-request against the project: `fedora-atomic` that you are
following.
Merged pull-request:
``
manifest: Remove plymouth
``
https://pagure.io/fedora-atomic/pull-request/61
___
cloud mailing list -- cloud@lists.fedoraproject.org
walters commented on the pull-request: `manifest: Remove plymouth` that you are
following:
``
This originated in https://pagure.io/fedora-kickstarts/pull-request/231
I meant this PR to be for discussion not merge, sorry should have mentioned
that. It's OK though; we can test the LUKS path and
walters opened a new pull-request against the project: `fedora-atomic` that you
are following:
``
manifest: Remove plymouth
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/60
___
cloud mailing
walters commented on the pull-request: `f26: add back in kube/storage clients
for now` that you are following:
``
This is a pretty major change; I'm OK with it but it feels unfortunate. For
people who want to use a different Kube, having to override things is going to
be annoying. It looks
On Fri, Apr 21, 2017, at 10:16 AM, Dusty Mabe wrote:
> NOTE: if you respond to this message please 'reply-all'.
>
> I'd like to discuss firewalld on atomic host.
I think there here are two cases:
AH-as-Kube/OpenShift host: In this I'd turn the conversation around - do
Kube/OpenShift want to
walters merged a pull-request against the project: `fedora-atomic` that you are
following.
Merged pull-request:
``
make the fedora 25 repos pull from mirrors
``
https://pagure.io/fedora-atomic/pull-request/58
___
cloud mailing list --
walters commented on the pull-request: `make the fedora 25 repos pull from
mirrors` that you are following:
``
Yeah.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/58
___
cloud mailing list
walters reported a new issue against the project: `atomic-wg` that you are
following:
``
Related issues:
- https://github.com/ostreedev/ostree/issues/729
- https://github.com/ostreedev/ostree/issues/707
- https://github.com/ostreedev/ostree-releng-scripts/issues/10
Preparatory steps:
1)
To follow up, I think the "not release blocking sidecar" model didn't
really work for Fedora 25, because we had last minute bugs there,
and at least the Fedora websites team refused to link to Fedora 24
content. (I can't find the discussion in a quick search).
https://bugzilla.redhat.com/show_bug.cgi?id=1435310
raised the issue that apparently, Atomic Host isn't "release blocking".
I think we have plenty of resources to match whatever criteria
there are for that for Fedora 27. Thoughts?
___
cloud mailing
walters added a new comment to an issue you are following:
``
We'll try again to do a better job in having Fedora/Project Atomic GSoC ideas
for 2018.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/250
On Fri, Mar 17, 2017, at 11:00 PM, Dusty Mabe wrote:
>
> Yes! we would love a UEFI test
Yes; conceptually most of the important scenarios we run through
for Workstation/Server (e.g. dm-crypt versus not) we should also
do for Atomic Host.
Adam, where is the git containing the input test suite
I can maybe attend this but I already have a lot of meetings today
and I'd like to write some code.
My feelings on this are basically:
1) I wrote on an issue I can't find now, but I was basically suggesting:
ln -s fedora/26/x86_64/atomic-host fedora/stable/x86_64/atomic-host
in the repo
walters added a new comment to an issue you are following:
``
A rebase would only be required one time to track `/stable` - thereafter it'd
be a stream of minor updates, until such time as on the *server* we change the
link to point to the next major.
Basically the client is just going to
walters added a new comment to an issue you are following:
``
I personally didn't like the idea of blogging this on projectatomic.io since
it's kind of advertising an "oops". I can write up something for
ato...@projectatomic.io though.
Ideally someone would be able to find it via Google but
walters commented on the pull-request: `Updates for f26 repos.` that you are
following:
``
rpm-ostree :arrow_right: libdnf :arrow_right: librepo, so it's going to work
the same for every libdnf consumer.
The bug is you need `metalink=` instead of `baseurl=`. In general, we should
have a SOP
walters added a new comment to an issue you are following:
``
https://pagure.io/pungi-fedora/pull-request/167
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/252
___
cloud mailing list --
walters reported a new issue against the project: `atomic-wg` that you are
following:
``
https://kojipkgs.fedoraproject.org/compose/rawhide/latest-Fedora-Rawhide/logs/x86_64/ostree_installer/pylorax.log
```
Traceback (most recent call last):
File
walters added a new comment to an issue you are following:
``
One thing we could do that would be pretty easy is to add a new `/stable` ref
as a *symbolic link*, e.g. we'd do:
`ln -sr repo/refs/heads/fedora/26/x86_64/atomic-host
repo/refs/heads/fedora/stable/x86_64/atomic-host`
Then someone
On Tue, Feb 28, 2017, at 01:37 AM, Dusty Mabe wrote:
> The atomic images are here:
^ Host =)
> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170228.0/compose/CloudImages/x86_64/images/
Autocloud:
https://apps.fedoraproject.org/autocloud/jobs/857
walters added a new comment to an issue you are following:
``
Pungi issue here https://pagure.io/pungi/issue/544
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/229
___
cloud mailing list --
walters added a new comment to an issue you are following:
``
It feels weird to do semi-automatic rebases on the client side. Not saying
it's wrong. But we need to think a bit about how people manage *automated*
systems.
I guess my question here is - who *wouldn't* want a single stream? I
walters added a new comment to an issue you are following:
``
I'd vote for images having a simple serial number - in the case where we have
to respin the cloud image because we changed the kickstart but *not* the tree,
we'd go from `-1` to `-2` or so.
i.e.:
```
walters added a new comment to an issue you are following:
``
For CAHC we use a [major.year.serial
pattern](https://github.com/CentOS/sig-atomic-buildscripts/blob/master/centos-atomic-host-continuous.json#L4).
The rationale is that:
Major is obviously important, and first. Year.serial is
walters added a new comment to an issue you are following:
``
https://www.redhat.com/archives/anaconda-devel-list/2017-February/msg0.html
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/226
___
cloud
walters added a new comment to an issue you are following:
``
Nevermind, this is only when using `virt-install --location` from content
extracted from the ISO. Will investigate.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/227
walters reported a new issue against the project: `atomic-wg` that you are
following:
``
Trying
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170214.0/compose/Atomic/x86_64/iso/
I see nothing in `/run/install/repo`, which causes an interactive installation
failure.
``
On Tue, Feb 14, 2017, at 02:32 PM, Dusty Mabe wrote:
> [1] https://pagure.io/fedora-lorax-templates/pull-request/11
I think this makes sense, though there's a bigger-picture issue here.
We should default to "install from the embedded content" rather
than requiring kickstart users to specify
walters reported a new issue against the project: `atomic-wg` that you are
following:
``
We should to set up the ISO (may need anaconda changes) so that what's in
`interactive-defaults.ks` takes effect for kickstart installs as well. This
would avoid kickstart users having to follow any
walters commented on the pull-request: `post: Work around LVM archival
conflicting with ostree` that you are following:
``
It's still valid. I may get back to it.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/27
walters added a new comment to an issue you are following:
``
The design I had for ostree refspecs is that they go from "general ->
specific". Hence it'd look like this:
```
fedora/25/x86_64/atomic-host
fedora/25/x86_64/workstation
```
The rationale for the `standard` thing was that in
On Fri, Jan 27, 2017, at 12:43 PM, Garrett Holmstrom wrote:
>
> These failures are due to a python-httpretty update that went stable in
> all releases earlier this week.
Ah, nice work tracking that down!
___
cloud mailing list --
On Tue, Jan 24, 2017, at 05:32 AM, Dusty Mabe wrote:
> The vm images are here:
>
> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/CloudImages/x86_64/images/
As a reminder, Atomic Host uses rpm-ostree (which uses ostree) for updates,
and in the future[1]
On Sat, Jan 21, 2017, at 04:53 PM, Dusty Mabe wrote:
> It doesn't use dnf at all. AFAIU rpm-ostree had code to install rpms
> for a while and then that code was broken out and eventually made into
> microdnf. So basically rpm-ostree already doesn't use dnf and uses
> code similar to what
walters reported a new issue against the project: `atomic-wg` that you are
following:
``
walters: so there are two options. One is changing default to
overlay2, which is common across all variants
walters: another new option is specifying where the storage from
overlayfs comes from. Does it
walters added a new comment to an issue you are following:
``
Yeah, merged /boot with ostree doesn't quite work for us yet. See
https://github.com/ostreedev/ostree/pull/215
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
walters added a new comment to an issue you are following:
``
Anaconda PR with updates.img available:
https://github.com/rhinstaller/anaconda/pull/903
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
walters added a new comment to an issue you are following:
``
I'll take this issue.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
___
cloud mailing list -- cloud@lists.fedoraproject.org
To
walters added a new comment to an issue you are following:
``
This might be UEFI vs bios - if you're using default virt-manager you get BIOS.
Some more info here https://fedoraproject.org/wiki/Using_UEFI_with_QEMU
``
To reply, visit the link below or just reply to this email
walters added a new comment to an issue you are following:
``
Oh, sorry, I was reading the git log and missed that we already did back out
the change:
https://pagure.io/fedora-kickstarts/c/6f3661e3a5f2625b73ee8e998087285d7c6e7e63?branch=f25
Nevermind.
``
To reply, visit the link below or just
walters added a new comment to an issue you are following:
``
I think this:
``
this has prevented me from then managing the network (I tried w/ a static ip)
from a cloud-init datasource. I'm pretty sure we don't want that.
```
is independent of the "no networking on boot" problem, which is
walters added a new comment to an issue you are following:
``
Err wait, so can't we revert this now?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/174
___
cloud mailing list --
walters added a new comment to an issue you are following:
``
No, the commands for Fedora (at least 24) and CentOS 7 are different. I linked
the commands for Fedora in https://pagure.io/atomic-wg/issue/178#comment-43101
``
To reply, visit the link below or just reply to this email
walters added a new comment to an issue you are following:
``
From my google searching, the steps have been discovered for CentOS 7, e.g.:
http://serverfault.com/a/694922
We should clearly put this in a document somewhere, but I'm not sure if we have
any for the base image?
``
To reply, visit
walters added a new comment to an issue you are following:
``
We don't document this well, but it is possible to add back in all locales.
The basic step is:
```
rm /etc/rpm/macros.image-language-conf
yum reinstall glibc-all-langpacks
```
However, that only undoes the configuration, any
walters added a new comment to an issue you are following:
``
Are you deploying Origin? See also
https://github.com/openshift/openshift-ansible/issues/1560
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/153
walters added a new comment to an issue you are following:
``
Josh, you need a `-` there.
```
initdb -D /pgdata/data --locale=C.UTF-8
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/178
___
cloud
walters added a new comment to an issue you are following:
``
The workaround is:
export LANG=C.UTF-8
We should probably export this by default in the base image's ENV.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/178
1 - 100 of 240 matches
Mail list logo
