Re: F33 install minimum memory requirements?

On 2020-08-26 02:27, Chris Murphy wrote: > It's getting clobbered by earlyoom. It really doesn't have enough > memory if it's swapping out 892M. If that were on disk, it'd be kindof > a dreadful experience performance wise, but yeah it would eventually > succeed if big enough. I'm not concerned

Fedora-33-20200825.n.1 compose check report

No missing expected images. Failed openQA tests: 8/181 (x86_64) Old failures (same test failed in Fedora-33-20200824.n.0): ID: 647962 Test: x86_64 KDE-live-iso desktop_background URL: https://openqa.fedoraproject.org/tests/647962 ID: 647968 Test: x86_64 KDE-live-iso

Fedora 33 compose report: 20200825.n.1 changes

OLD: Fedora-33-20200824.n.0 NEW: Fedora-33-20200825.n.1 = SUMMARY = Added images:7 Dropped images: 0 Added packages: 6 Dropped packages:135 Upgraded packages: 251 Downgraded packages: 0 Size of added packages: 4.27 MiB Size of dropped packages:412.50 MiB

Re: Release criteria proposal: networking requirements

On Tue, 2020-08-25 at 16:11 -0700, Adam Williamson wrote: > On Tue, 2020-08-25 at 15:50 -0700, Michel Alexandre Salim wrote: > > On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote: > > > VPN connections > > > > > > > > > > > > Using the default network configuration tools for

Re: Release criteria proposal: networking requirements

On Tue, 2020-08-25 at 15:50 -0700, Michel Alexandre Salim wrote: > On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote: > > VPN connections > > > > > > > > Using the default network configuration tools for the console and for > > > > release-blocking desktops, it must be

Re: Release criteria proposal: networking requirements

On Fri, 2020-08-21 at 17:11 -0700, Adam Williamson wrote: > VPN connections > > > > Using the default network configuration tools for the console and for > > release-blocking desktops, it must be possible to establish a working > > connection to common OpenVPN, openconnect-supported

Re: F33 install minimum memory requirements?

On Tue, Aug 25, 2020 at 12:32 AM Ed Greshko wrote: > > On 2020-08-25 13:58, Chris Murphy wrote: > > On Mon, Aug 24, 2020 at 11:30 PM Ed Greshko wrote: > >> With F32 and previous versions I've been able to install Workstation and > >> other spins in a QEMU VM > >> with about 1200MB~1248MB of

Re: F33 install minimum memory requirements?

On Tue, 2020-08-25 at 13:30 +0800, Ed Greshko wrote: > With F32 and previous versions I've been able to install Workstation and > other spins in a QEMU VM > with about 1200MB~1248MB of memory.  With F33 the install process crashes > during the "installing software" > phase. > > Is this

Re: F33 install minimum memory requirements?

On 2020-08-25 22:35, Kamil Paral wrote: > On Tue, Aug 25, 2020 at 8:33 AM Ed Greshko > wrote: > > Aug 25 02:27:15 localhost-live anaconda[2042]: program: stderr: > Aug 25 02:27:14 localhost-live anaconda[2042]: program: Running... umount >

Re: F33 install minimum memory requirements?

On 2020-08-25 22:38, Kamil Paral wrote: > On Tue, Aug 25, 2020 at 9:08 AM Ed Greshko > wrote: > > On reflection, I don't think that previous installs without zram used any > swap. > > > That seems hardly possible, according to your logs. Anything is possible,

Re: F33 install minimum memory requirements?

On Tue, Aug 25, 2020 at 9:08 AM Ed Greshko wrote: > On reflection, I don't think that previous installs without zram used any > swap. > That seems hardly possible, according to your logs. Anything is possible, but it is very improbable that previously you'd be able to finish the installation

Re: F33 install minimum memory requirements?

On Tue, Aug 25, 2020 at 8:33 AM Ed Greshko wrote: > Aug 25 02:27:15 localhost-live anaconda[2042]: program: stderr: > Aug 25 02:27:14 localhost-live anaconda[2042]: program: Running... umount > /run/install/source > Aug 25 02:27:13 localhost-live earlyoom[1015]: sending SIGTERM to process > 2042

[Test-Announce] Bodhi Activation point

Hi all, Today's an important day on the Fedora 33 schedule[1], with several significant cut-offs. First of all, today is the Bodhi activation point [2]. That means that from now on all Fedora 33 packages must be submitted to updates-testing and pass the relevant requirements[3] before they will

Fedora-Cloud-31-20200825.0 compose check report

No missing expected images. Passed openQA tests: 7/7 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to

Fedora-Cloud-32-20200825.0 compose check report

No missing expected images. Soft failed openQA tests: 1/7 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-32-20200824.0): ID: 647295 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL:

Re: Preserving the home on btrfs

On Mon, 2020-08-24 at 13:12 -0600, Chris Murphy wrote: > 1. Create /boot/efi or BIOS Boot mount point (can be reused or > reformatted) > 2. Create /boot mount point (can be reused or reformatted) > 3. Create / mount point (this is required to be a new subvolume) Ah. Ok, this is the point. I was

Re: F33 install minimum memory requirements?

On 2020-08-25 14:32, Ed Greshko wrote: > So, it would seem, zram based swap is less forgiving than disk based swap. That may have been silly statement.  On reflection, I don't think that previous installs without zram used any swap. -- The key to getting good answers is to ask good questions.

Re: F33 install minimum memory requirements?

On 2020-08-25 13:58, Chris Murphy wrote: > On Mon, Aug 24, 2020 at 11:30 PM Ed Greshko wrote: >> With F32 and previous versions I've been able to install Workstation and >> other spins in a QEMU VM >> with about 1200MB~1248MB of memory. With F33 the install process crashes >> during the