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

fedora25->fedora26 following case #3328

Open
boistordu opened this Issue Nov 22, 2017 · 6 comments

Comments

Projects
None yet
3 participants
@boistordu

Qubes OS version:

R3.2

I have done the upgrade yesterday. We still have a problem with pulseaudio but less of the previous one.
Pulseaudio 11.1 is still incompatbile with qubes-gui-vm so we still have a message to add --best --allowerasing at the upgrade command-line. We need to downgrade pulseaudio to 10.0 to still have qubes-vm-gui installed.

Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 dnf-utils                       noarch 2.1.5-1.fc26              updates  40 k
 pulseaudio                      x86_64 11.1-6.fc26               updates 944 k
 pulseaudio-libs                 i686   11.1-6.fc26               updates 672 k
 pulseaudio-libs                 x86_64 11.1-6.fc26               updates 662 k
 pulseaudio-libs-glib2           x86_64 11.1-6.fc26               updates  26 k
 pulseaudio-module-bluetooth     x86_64 11.1-6.fc26               updates  76 k
 pulseaudio-module-x11           x86_64 11.1-6.fc26               updates  37 k
 pulseaudio-utils                x86_64 11.1-6.fc26               updates  75 k

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
Member

andrewdavidwong commented Nov 23, 2017

Will this be fixed by QubesOS/qubes-gui-agent-linux@4cf2d11 as suggested in #3309 (comment)?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Nov 23, 2017

Member

The update with this is already in testing repository: QubesOS/updates-status#296

Member

marmarek commented Nov 23, 2017

The update with this is already in testing repository: QubesOS/updates-status#296

@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Nov 23, 2017

okey then we'll wait for this thing coming to update rep

okey then we'll wait for this thing coming to update rep

@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Dec 9, 2017

16 days and still no update ... I have done all the dnf clean all. How much time do you still need for this to happen ?

16 days and still no update ... I have done all the dnf clean all. How much time do you still need for this to happen ?

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Dec 9, 2017

Member

@boistordu:

16 days and still no update ... I have done all the dnf clean all. How much time do you still need for this to happen ?

You do not have to rely on dnf clean all to check whether the package is available in stable. You can see when the package moves from testing to stable here: QubesOS/updates-status#296. For more information, see Testing New Releases and Updates.

The amount of time it takes for a package to move from testing to stable varies depending on many factors, including feedback from testers and developer workflow priorities. If you don't want to wait, you can enable the current-testing repo.

Member

andrewdavidwong commented Dec 9, 2017

@boistordu:

16 days and still no update ... I have done all the dnf clean all. How much time do you still need for this to happen ?

You do not have to rely on dnf clean all to check whether the package is available in stable. You can see when the package moves from testing to stable here: QubesOS/updates-status#296. For more information, see Testing New Releases and Updates.

The amount of time it takes for a package to move from testing to stable varies depending on many factors, including feedback from testers and developer workflow priorities. If you don't want to wait, you can enable the current-testing repo.

@boistordu

This comment has been minimized.

Show comment
Hide comment
@boistordu

boistordu Dec 9, 2017

I know sorry but you can know that's frustrating since fedora version are in my own opinion, very fast to be out of busines, so one month from a 10-12 month timetable is actually a lot. But yeah of course I will wait, but still. Thanks for the answer anyway

I know sorry but you can know that's frustrating since fedora version are in my own opinion, very fast to be out of busines, so one month from a 10-12 month timetable is actually a lot. But yeah of course I will wait, but still. Thanks for the answer anyway

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment