Hello

I tested upgrades from F29 to F30. I use the following images:
https://download.fedoraproject.org/pub/fedora/linux/releases/29/Cloud/x86_64/images/Fedora-Cloud-Base-Vagrant-29-1.2.x86_64.vagrant-virtualbox.box
https://download.fedoraproject.org/pub/fedora/linux/releases/29/Cloud/x86_64/images/Fedora-Cloud-Base-29-1.2.x86_64.qcow2

On the image for Vagrant, I failed upgrades  I usually use this image for rpm packaging.
```
[vagrant@fedora29 ~]$ sudo dnf --releasever=30 --setopt=module_platform_id=platform:f30 --enablerepo=updates-testing distro-sync
Fedora Modular 30 - x86_64                                                                                                                        650 kB/s | 2.3 MB     00:03  
Fedora Modular 30 - x86_64 - Updates                                                                                                              219  B/s | 257  B     00:01  
Fedora 30 - x86_64 - Test Updates                                                                                                                 1.8 MB/s |  14 MB     00:07  
Fedora 30 - x86_64 - Updates                                                                                                                      234  B/s | 257  B     00:01  
Fedora 30 - x86_64                                                                                                                                1.1 MB/s |  54 MB     00:48  
Error:
 Problem 1: problem with installed package gofed-infra-1.0.0-0.21.rc1.fc29.noarch
  - gofed-infra-1.0.0-0.21.rc1.fc29.noarch does not belong to a distupgrade repository
  - nothing provides python2.7dist(git) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
  - nothing provides python2.7dist(hglib) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
  - nothing provides python2.7dist(koji) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
  - nothing provides python2.7dist(python-gitdb) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
  - nothing provides python2.7dist(tarfile) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
  - nothing provides python2.7dist(urllib2) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
 Problem 2: problem with installed package gofed-gofedlib-1.0.0-0.21.rc1.fc29.x86_64
  - gofed-gofedlib-1.0.0-0.21.rc1.fc29.x86_64 does not belong to a distupgrade repository
  - nothing provides python2.7dist(jinja2) = 2.8 needed by gofed-gofedlib-1.0.0-0.22.rc1.fc30.x86_64
  - nothing provides python2.7dist(markupsafe) = 0.23 needed by gofed-gofedlib-1.0.0-0.22.rc1.fc30.x86_64
 Problem 3: problem with installed package gofed-1.0.0-0.21.rc1.fc29.x86_64
  - package gofed-1.0.0-0.22.rc1.fc30.x86_64 requires gofed-infra = 1.0.0-0.22.rc1.fc30, but none of the providers can be installed
  - gofed-1.0.0-0.21.rc1.fc29.x86_64 does not belong to a distupgrade repository
  - nothing provides python2.7dist(git) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
  - nothing provides python2.7dist(hglib) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
  - nothing provides python2.7dist(koji) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
  - nothing provides python2.7dist(python-gitdb) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
  - nothing provides python2.7dist(tarfile) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
  - nothing provides python2.7dist(urllib2) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch
 Problem 4: problem with installed package gofed-resources-1.0.0-0.21.rc1.fc29.noarch
  - package gofed-resources-1.0.0-0.22.rc1.fc30.noarch requires gofed-gofedlib = 1.0.0-0.22.rc1.fc30, but none of the providers can be installed
  - gofed-resources-1.0.0-0.21.rc1.fc29.noarch does not belong to a distupgrade repository
  - nothing provides python2.7dist(jinja2) = 2.8 needed by gofed-gofedlib-1.0.0-0.22.rc1.fc30.x86_64
  - nothing provides python2.7dist(markupsafe) = 0.23 needed by gofed-gofedlib-1.0.0-0.22.rc1.fc30.x86_64
(try to add '--skip-broken' to skip uninstallable packages)
```

On the image for OpenStack, dependencies are successfully resolved.
```
Transaction Summary
==================================================================================================================================================================================
Install   20 Packages
Upgrade  392 Packages

...

Total download size: 282 M
Is this ok [y/N]:
Operation aborted.
```

Upgrades are successfully completed while I found scriptlets in dbus-daemon and systemd are failed
because of "Failed to reload daemon: Access denied".
```
Transaction Summary
==================================================================================================================================================================================
Install   20 Packages
Upgrade  392 Packages

Total download size: 282 M
Is this ok [y/N]: y

...(snip)...

Upgraded: dbus-daemon-1:1.12.10-1.fc29.x86_64
  Running scriptlet: dbus-daemon-1:1.12.10-1.fc29.x86_64                                                                                                                  663/807
Failed to reload daemon: Access denied
warning: %triggerpostun(systemd-239-3.fc29.x86_64) scriptlet failed, exit status 1

Error in <unknown> scriptlet in rpm package dbus-daemon
Upgraded: systemd-pam-239-3.fc29.x86_64

...(snip)...

Upgraded: libgcc-8.2.1-2.fc29.x86_64
  Running scriptlet: libgcc-8.2.1-2.fc29.x86_64                                                                                                                           807/807
  Running scriptlet: filesystem-3.10-1.fc30.x86_64                                                                                                                        807/807
  Running scriptlet: sssd-common-2.1.0-2.fc30.x86_64                                                                                                                      807/807
  Running scriptlet: kernel-core-5.0.7-300.fc30.x86_64                                                                                                                    807/807
  Running scriptlet: rootfiles-8.1-24.fc30.noarch                                                                                                                         807/807
  Running scriptlet: libgcc-8.2.1-2.fc29.x86_64                                                                                                                           807/807
  Running scriptlet: glibc-common-2.29-9.fc30.x86_64                                                                                                                      807/807
  Running scriptlet: shared-mime-info-1.12-2.fc30.x86_64                                                                                                                  807/807
  Running scriptlet: glib2-2.60.0-3.fc30.x86_64                                                                                                                           807/807
  Running scriptlet: systemd-241-6.gita2eaa1c.fc30.x86_64                                                                                                                 807/807
Failed to reload daemon: Access denied
warning: %triggerin(systemd-241-6.gita2eaa1c.fc30.x86_64) scriptlet failed, exit status 1

Error in <unknown> scriptlet in rpm package systemd
  Running scriptlet: systemd-udev-241-6.gita2eaa1c.fc30.x86_64                                                                                                            807/807
  Running scriptlet: man-db-2.8.4-4.fc30.x86_64                                                                                                                           807/807
  Running scriptlet: info-6.6-1.fc30.x86_64 

...(snip)...

Complete!
[fedora@fedora29 ~]$ 
```

Best Regards,
Hirotaka Wakabayashi


On Thursday, February 28, 2019 6:23 PM, Miroslav Suchý <msuchy@redhat.com> wrote:


Do you want to make Fedora 30 better? Please spend 1 minute of your time and try to run:

  sudo dnf --releasever=30 --setopt=module_platform_id=platform:f30 --enablerepo=updates-testing distro-sync

If you get this prompt:

  ...
  Total download size: XXX M
  Is this ok [y/N]:

you can answer N and nothing happens, no need to test the real upgrade. Upgrades will be fine for you.

But very likely you get some dependency problem now. In that case please report it against appropriate package.

Thank you

Miroslav
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org