/qubes-issues

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fedora 25 has reached EOL #3429

Closed
andrewdavidwong opened this Issue Dec 26, 2017 · 6 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 3.2 updates
2 participants
@andrewdavidwong @kirill9000
@andrewdavidwong
Member

andrewdavidwong commented Dec 26, 2017 •
edited
Edited 3 times
  • @andrewdavidwong andrewdavidwong edited Jan 7, 2018 (most recent)
  • @andrewdavidwong andrewdavidwong edited Jan 6, 2018
  • @marmarek marmarek edited Dec 26, 2017

Fedora 25 reached EOL on 2017-12-12 and is no longer receiving security updates. We need:

@marmarek, do you want to handle the second item, then I'll do the third?

@andrewdavidwong andrewdavidwong added C: Fedora P: critical task labels Dec 26, 2017

@andrewdavidwong andrewdavidwong added this to the Release 3.2 updates milestone Dec 26, 2017

@andrewdavidwong andrewdavidwong referenced this issue Dec 26, 2017

Open

Mechanism to notify users when critical action is required #3430

@marmarek marmarek changed the title from Fedora 26 has reached EOL to Fedora 25 has reached EOL Dec 26, 2017

This was referenced Jan 3, 2018

Closed
Closed

@andrewdavidwong andrewdavidwong referenced this issue in QubesOS/qubes-doc Jan 5, 2018

Merged

Create Fedora 25 to 26 upgrade instructions #505

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 5, 2018

Member

@marmarek: I've submitted F25->F26 upgrade instructions for your review in QubesOS/qubes-doc#505.
Member

andrewdavidwong commented Jan 5, 2018

@marmarek: I've submitted F25->F26 upgrade instructions for your review in QubesOS/qubes-doc#505.
@kirill9000

This comment has been minimized.

Show comment
Hide comment
@kirill9000

kirill9000 Jan 6, 2018

These upgrades are a pain and always late (i.e. significantly after EOL). Seems to me that Fedora's support cycle is way too short for Qubes. Why don't you switch to Debian as default template VM (or at least for sys-VMs)?

kirill9000 commented Jan 6, 2018

These upgrades are a pain and always late (i.e. significantly after EOL). Seems to me that Fedora's support cycle is way too short for Qubes. Why don't you switch to Debian as default template VM (or at least for sys-VMs)?

@andrewdavidwong andrewdavidwong referenced this issue in QubesOS/qubes-doc Jan 6, 2018

Merged

Update fedora-minimal.md #507

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 6, 2018

Member

These upgrades are a pain and always late (i.e. significantly after EOL).

They're a pain, but I think this is the first time we've been late to announce it (at least in a long time). For example, we announce F23->F24 and F24->F25 well before each of those EOLs:

https://www.qubes-os.org/news/2016/11/15/fedora-24-template-available/
https://www.qubes-os.org/news/2017/07/29/fedora-25-upgrade/

Seems to me that Fedora's support cycle is way too short for Qubes. Why don't you switch to Debian as default template VM (or at least for sys-VMs)?

We'll be addressing this point shortly.
Member

andrewdavidwong commented Jan 6, 2018

These upgrades are a pain and always late (i.e. significantly after EOL).

They're a pain, but I think this is the first time we've been late to announce it (at least in a long time). For example, we announce F23->F24 and F24->F25 well before each of those EOLs:

https://www.qubes-os.org/news/2016/11/15/fedora-24-template-available/
https://www.qubes-os.org/news/2017/07/29/fedora-25-upgrade/

Seems to me that Fedora's support cycle is way too short for Qubes. Why don't you switch to Debian as default template VM (or at least for sys-VMs)?

We'll be addressing this point shortly.
@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 7, 2018

Member

Announcement created: QubesOS/qubes-posts@bf09db9
Member

andrewdavidwong commented Jan 7, 2018

Announcement created: QubesOS/qubes-posts@bf09db9

@andrewdavidwong andrewdavidwong closed this Jan 7, 2018

@kirill9000

This comment has been minimized.

Show comment
Hide comment
@kirill9000

kirill9000 Jan 7, 2018

I think this is the first time we've been late to announce it (at least in a long time)

Yeah, I guess I was wrong about that. Sorry. But what about the Debian question?

kirill9000 commented Jan 7, 2018

I think this is the first time we've been late to announce it (at least in a long time)

Yeah, I guess I was wrong about that. Sorry. But what about the Debian question?
@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 7, 2018

Member

Yeah, I guess I was wrong about that. Sorry. But what about the Debian question?

As I said above, we'll be addressing that point shortly.
Member

andrewdavidwong commented Jan 7, 2018

Yeah, I guess I was wrong about that. Sorry. But what about the Debian question?

As I said above, we'll be addressing that point shortly.

andrewdavidwong added a commit to QubesOS/qubes-doc that referenced this issue Jan 7, 2018

@andrewdavidwong
Create minimal template instructions for each version 
The minimal template upgrade instructions still included the
`qvm-trim-template` command, which only works in R3.2. I've moved those
instructions into the R3.2 section and added new instructions using the
`fstrim` command in the R4.0 section.

I've also removed the section on differences between the standard and
minimal upgrade procedures, since the second point is no longer accurate
(e.g., `sudo` is installed by default in the minimal template on R3.2),
and the first point is not significant enough to merit keeping the
section.

#505
QubesOS/qubes-issues#3429
Verified
This commit was signed with a verified signature.
@andrewdavidwong andrewdavidwong Andrew David Wong
GPG key ID: 8CE137352A019A17 Learn about signing commits
81463b8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment