[389-devel] 389 DS nightly 2018-09-03 - 89% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2018/09/03/report-389-ds-base-1.4.0.16-20180902git78fc627.fc28.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
Fedora Rawhide-20180902.n.0 compose check report
No missing expected images. Failed openQA tests: 37/132 (x86_64), 2/24 (i386), 1/2 (arm) New failures (same test did not fail in Rawhide-20180831.n.0): ID: 273031 Test: i386 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/273031 ID: 273038 Test: x86_64 KDE-live-iso install_no_user URL: https://openqa.fedoraproject.org/tests/273038 ID: 273054 Test: x86_64 universal install_blivet_ext3 URL: https://openqa.fedoraproject.org/tests/273054 ID: 273065 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/273065 ID: 273089 Test: x86_64 universal install_kickstart_firewall_configured URL: https://openqa.fedoraproject.org/tests/273089 ID: 273098 Test: x86_64 universal install_scsi_updates_img URL: https://openqa.fedoraproject.org/tests/273098 ID: 273108 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/273108 Old failures (same test failed in Rawhide-20180831.n.0): ID: 272984 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/272984 ID: 272987 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/272987 ID: 273005 Test: x86_64 Server-dvd-iso server_freeipa_replication_replica URL: https://openqa.fedoraproject.org/tests/273005 ID: 273012 Test: x86_64 Everything-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/273012 ID: 273015 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/273015 ID: 273016 Test: x86_64 Workstation-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/273016 ID: 273028 Test: x86_64 Workstation-boot-iso memory_check@uefi URL: https://openqa.fedoraproject.org/tests/273028 ID: 273029 Test: x86_64 Workstation-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/273029 ID: 273030 Test: i386 Workstation-live-iso install_default URL: https://openqa.fedoraproject.org/tests/273030 ID: 273034 Test: x86_64 KDE-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/273034 ID: 273041 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/273041 ID: 273047 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/273047 ID: 273050 Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/273050 ID: 273060 Test: x86_64 universal install_simple_free_space@uefi URL: https://openqa.fedoraproject.org/tests/273060 ID: 273061 Test: x86_64 universal install_multi_empty@uefi URL: https://openqa.fedoraproject.org/tests/273061 ID: 273068 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/273068 ID: 273070 Test: x86_64 universal install_delete_pata@uefi URL: https://openqa.fedoraproject.org/tests/273070 ID: 273073 Test: x86_64 universal install_blivet_btrfs@uefi URL: https://openqa.fedoraproject.org/tests/273073 ID: 273074 Test: x86_64 universal install_blivet_no_swap@uefi URL: https://openqa.fedoraproject.org/tests/273074 ID: 273075 Test: x86_64 universal install_blivet_xfs@uefi URL: https://openqa.fedoraproject.org/tests/273075 ID: 273077 Test: x86_64 universal install_simple_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/273077 ID: 273080 Test: x86_64 universal install_software_raid@uefi URL: https://openqa.fedoraproject.org/tests/273080 ID: 273081 Test: x86_64 universal install_delete_partial@uefi URL: https://openqa.fedoraproject.org/tests/273081 ID: 273083 Test: x86_64 universal install_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/273083 ID: 273093 Test: x86_64 universal install_btrfs@uefi URL: https://openqa.fedoraproject.org/tests/273093 ID: 273094 Test: x86_64 universal install_blivet_ext3@uefi URL: https://openqa.fedoraproject.org/tests/273094 ID: 273095 Test: x86_64 universal install_blivet_software_raid@uefi URL: https://openqa.fedoraproject.org/tests/273095 ID: 273096 Test: x86_64 universal install_blivet_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/273096 ID: 273099 Test: x86_64 universal install_ext3@uefi URL: https://openqa.fedoraproject.org/tests/273099 ID: 273100 Test: x86_64 universal install_xfs@uefi URL: https://openqa.fedoraproject.org/tests/273100 ID: 273101 Test: x86_64 universal install_no_swap@uefi URL: https://openqa.fedoraproject.org/tests/273101 ID: 273115 Test: x86_64 universal install_sata@uefi URL: https://openqa.fedoraproject.org/tests/273115 ID: 273117 Test: x86_64 universal install_multi@uefi URL: https://openqa.fedoraproject.org/tests/273117 Soft failed openQA tests: 2/132 (x86_64), 3/24 (i386) (Tests completed, but using a workaround for a
Fedora 29-20180902.n.0 compose check report
No missing expected images. Failed openQA tests: 13/132 (x86_64), 2/24 (i386), 1/2 (arm) ID: 273142 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/273142 ID: 273163 Test: x86_64 Server-dvd-iso server_freeipa_replication_replica URL: https://openqa.fedoraproject.org/tests/273163 ID: 273170 Test: x86_64 Everything-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/273170 ID: 273173 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/273173 ID: 273174 Test: x86_64 Workstation-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/273174 ID: 273187 Test: x86_64 Workstation-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/273187 ID: 273188 Test: i386 Workstation-live-iso install_default URL: https://openqa.fedoraproject.org/tests/273188 ID: 273192 Test: x86_64 KDE-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/273192 ID: 273199 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/273199 ID: 273202 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/273202 ID: 273205 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/273205 ID: 273224 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/273224 ID: 273234 Test: x86_64 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/273234 ID: 273235 Test: x86_64 universal install_simple_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/273235 ID: 273279 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/273279 ID: 273298 Test: i386 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/273298 Soft failed openQA tests: 70/132 (x86_64), 17/24 (i386) (Tests completed, but using a workaround for a known bug) ID: 273141 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/273141 ID: 273144 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/273144 ID: 273145 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/273145 ID: 273147 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/273147 ID: 273148 Test: x86_64 Server-dvd-iso server_cockpit_default URL: https://openqa.fedoraproject.org/tests/273148 ID: 273154 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical URL: https://openqa.fedoraproject.org/tests/273154 ID: 273156 Test: x86_64 Server-dvd-iso server_cockpit_basic URL: https://openqa.fedoraproject.org/tests/273156 ID: 273157 Test: x86_64 Server-dvd-iso realmd_join_cockpit URL: https://openqa.fedoraproject.org/tests/273157 ID: 273160 Test: x86_64 Server-dvd-iso install_updates_nfs URL: https://openqa.fedoraproject.org/tests/273160 ID: 273161 Test: x86_64 Server-dvd-iso install_repository_nfs_variation URL: https://openqa.fedoraproject.org/tests/273161 ID: 273167 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/273167 ID: 273168 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/273168 ID: 273169 Test: x86_64 Everything-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/273169 ID: 273171 Test: i386 Everything-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/273171 ID: 273209 Test: x86_64 universal install_xfs URL: https://openqa.fedoraproject.org/tests/273209 ID: 273210 Test: x86_64 universal install_lvmthin URL: https://openqa.fedoraproject.org/tests/273210 ID: 273211 Test: x86_64 universal install_no_swap URL: https://openqa.fedoraproject.org/tests/273211 ID: 273212 Test: x86_64 universal install_blivet_ext3 URL: https://openqa.fedoraproject.org/tests/273212 ID: 273213 Test: x86_64 universal install_blivet_btrfs URL: https://openqa.fedoraproject.org/tests/273213 ID: 273214 Test: x86_64 universal install_blivet_no_swap URL: https://openqa.fedoraproject.org/tests/273214 ID: 273215 Test: x86_64 universal install_blivet_xfs URL: https://openqa.fedoraproject.org/tests/273215 ID: 273216 Test: x86_64 universal install_blivet_software_raid URL: https://openqa.fedoraproject.org/tests/273216 ID: 273217 Test: x86_64 universal install_blivet_lvmthin URL: https://openqa.fedoraproject.org/tests/273217 ID: 273218 Test: x86_64 universal install_simple_free_space@uefi URL: https://openqa.fedoraproject.org/tests/273218 ID: 273219 Test: x86_64 universal install_multi_empty@uefi URL: https://openqa.fedoraproject.org/tests/273219 ID: 273220
Re: Headsup: dbus 1.12.10-1.fc29 is missing systemd dbus.service file, breaking almost everything
Den sön 2 sep. 2018 kl 17:59 skrev stan : > > On Sun, 2 Sep 2018 09:33:39 +0200 > Andreas Tunek wrote: > > > There is no root acoount on a default F29 installation. Also, you > > can't see the boot menu and I haven't been able to trigger it. > > Whoa! I'm not sure what that buys, but I'll change that as soon as > possible when I install it. That's crazy! Maybe someone wants to > imitate a Mac or something. "Don't you trouble your pretty little head > about what is going on behind the scenes, dearie, it is all taken > care of. You just watch the pretty pictures, leave the driving to us." > And that's reasonable for a certain class of users. > > > Is there a guide or something how to do that? > > Alexander gave you one option, here are a couple of others. > > http://www.system-rescue-cd.org/ > > https://www.fossmint.com/linux-rescue-recovery-tools/ > > A Fedora livecd would also work, anything that can boot the system > without using the installed image. The advantage of using a recent > fedora live image is that the kernel and packages will be compatible. > > > Disk is not cheap on my test laptop unfortunately... > > There isn't even 80 GB, maybe less, free to clone the current version > before you update? An rsync makes this easy, though you should > probably do it from a live image so the temporary stuff created during > boot isn't there. > I have a 128 GB ssd in my system. > > I think that install is gone and all I can do is reinstall. Not very > > fun. > > I think you can recover, though it will be some work. In your > situation, I would try to recover, as I think a reinstall will take > more time and effort than a recovery. > > All that is needed is to either downgrade dbus, or update it to the > repaired version. You could just go to koji, grab the fixed dbus rpms, > https://koji.fedoraproject.org/koji/buildinfo?buildID=1140329 > cp them into the installed system from the rescue environment, > chroot into the installed system from the rescue environment, > and then run > dnf -C update [the koji files, space separated] > or > rpm -ivh [the koji files, space separated] > Then leave the chroot with > exit > and shutdown. > > After that, booting into the system should work as dbus will be > repaired. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Headsup: dbus 1.12.10-1.fc29 is missing systemd dbus.service file, breaking almost everything
Den sön 2 sep. 2018 kl 18:18 skrev Adam Williamson : > > On Sun, 2018-09-02 at 08:58 -0700, stan wrote: > > On Sun, 2 Sep 2018 09:33:39 +0200 > > Andreas Tunek wrote: > > > > > There is no root acoount on a default F29 installation. Also, you > > > can't see the boot menu and I haven't been able to trigger it. > > > > Whoa! I'm not sure what that buys, but I'll change that as soon as > > possible when I install it. That's crazy! Maybe someone wants to > > imitate a Mac or something. > > It's a Change that was properly announced and extensively discussed on > this list. (Though it's unfortunate that this situation is apparently > not considered a 'failed' boot by the mechanism that's supposed to make > sure the boot menu *is* shown after a failed boot). > https://fedoraproject.org/wiki/Changes/HiddenGrubMenu > https://bugzilla.redhat.com/show_bug.cgi?id=1592201 > It would be nice if you could get to a command prompt (with networking enabled) even if dbus is broken. > > "Don't you trouble your pretty little head > > about what is going on behind the scenes, dearie, it is all taken > > care of. You just watch the pretty pictures, leave the driving to us." > > And that's reasonable for a certain class of users. > > Please avoid implicitly gendered language like this, that's not cool, > and you don't need it to make your point. > > > > Is there a guide or something how to do that? > > > > Alexander gave you one option, here are a couple of others. > > > > http://www.system-rescue-cd.org/ > > > > https://www.fossmint.com/linux-rescue-recovery-tools/ > > > > A Fedora livecd would also work, anything that can boot the system > > without using the installed image. The advantage of using a recent > > fedora live image is that the kernel and packages will be compatible. > > > > > Disk is not cheap on my test laptop unfortunately... > > > > There isn't even 80 GB, maybe less, free to clone the current version > > before you update? An rsync makes this easy, though you should > > probably do it from a live image so the temporary stuff created during > > boot isn't there. > > > > > I think that install is gone and all I can do is reinstall. Not very > > > fun. > > > > I think you can recover, though it will be some work. In your > > situation, I would try to recover, as I think a reinstall will take > > more time and effort than a recovery. > > > > All that is needed is to either downgrade dbus, or update it to the > > repaired version. You could just go to koji, grab the fixed dbus rpms, > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1140329 > > cp them into the installed system from the rescue environment, > > chroot into the installed system from the rescue environment, > > and then run > > dnf -C update [the koji files, space separated] > > or > > rpm -ivh [the koji files, space separated] > > Then leave the chroot with > > exit > > and shutdown. > > > > After that, booting into the system should work as dbus will be > > repaired. > > Actually, I think the title of this thread is wrong. At least in my > testing, 1.12.10-2.fc29 is the *broken* package. 1.12.10-1.fc29 is > fine. It's when you upgrade to 1.12.10-2.fc29 that things go sideways. > To fix things you need to either enable dbus-daemon.service or > downgrade to -1. > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora > http://www.happyassassin.net > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Heads-up: ImageMagick SONAME bump
ImageMagick 6.9.9 => 6.9.10 introduces a SONAME bump from .so.5 to .so.6. I'll rebuild what I can, but please help out if you have some spare cycles. dnf repoquery --whatrequires libMagickCore-6.Q16.so.5\(\)\(64bit\) --releasever=30: WINGs-libs-0:0.95.8-10.fc29.x86_64 WindowMaker-0:0.95.8-10.fc29.x86_64 autotrace-0:0.31.1-52.fc29.x86_64 chafa-0:0.9.0-1.fc29.x86_64 converseen-0:0.9.6.2-9.fc29.x86_64 dmtx-utils-0:0.7.6-2.fc29.x86_64 drawtiming-0:0.7.1-28.fc29.x86_64 emacs-1:26.1-6.fc29.x86_64 emacs-lucid-1:26.1-6.fc29.x86_64 gtatool-imagemagick-0:2.2.0-11.fc28.x86_64 imageinfo-0:0.05-31.fc29.x86_64 inkscape-0:0.92.3-5.fc29.x86_64 inkscape-view-0:0.92.3-5.fc29.x86_64 kxstitch-0:2.0.0-4.fc28.x86_64 perl-Image-SubImageFind-0:0.03-17.fc29.x86_64 pfstools-0:2.0.6-8.fc29.x86_64 pfstools-imgmagick-0:2.0.6-8.fc29.x86_64 php-pecl-imagick-0:3.4.3-8.fc29.x86_64 psiconv-0:0.9.8-25.fc28.x86_64 python2-vips-0:8.6.5-2.fc29.x86_64 q-magick-0:7.11-33.fc29.x86_64 ripright-0:0.11-10.fc29.x86_64 rss-glx-0:0.9.1.p-35.fc29.x86_64 rubygem-rmagick-0:2.16.0-16.fc29.x86_64 synfig-0:1.2.1-3.fc28.x86_64 synfigstudio-0:1.2.1-3.fc28.x86_64 vdr-scraper2vdr-0:1.0.9-4.20180104gitef448e1.fc29.x86_64 vips-0:8.6.5-2.fc29.x86_64 vips-tools-0:8.6.5-2.fc29.x86_64 Thanks, Michael ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Test-Announce] 2018-09-04 (TUESDAY) @ 16:00 UTC - Fedora 29 Blocker Review Meeting
# F29 Blocker Review meeting # Date: 2018-09-04 (NOTE: TUESDAY)! # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have 7 proposed Beta blockers and 15 proposed Beta freeze exception to review, so let's have a review meeting on Tuesday. Note that Monday is a public holiday in North America, so I expect a lot of folks wouldn't be available; I'm proposing the meeting for Tuesday instead. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F29 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you Tuesday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Test-Announce] 2018-09-04 (TUESDAY) @ 15:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2018-09-04 (NOTE: TUESDAY!) # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! We're getting close to Fedora 29 Beta now, and I think there's some stuff we could usefully discuss at a meeting. However, Monday is a public holiday in the U.S. and Canada, so I suspect quite a few folks wouldn't be available. Given that, I'm proposing we run the meeting on *Tuesday* instead. I'm also gonna propose a blocker meeting for the same day. If this is especially inconvenient for anyone, please do reply and say so. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 29 general status 3. Fedora 29 Change status 4. Test Day update 5. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 29 compose report: 20180902.n.0 changes
OLD: Fedora-29-20180901.n.0 NEW: Fedora-29-20180902.n.0 = SUMMARY = Added images:7 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 1 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 23.53 MiB Size of downgraded packages: 0 B Size change of upgraded packages: -8.46 KiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: AtomicHost qcow2 ppc64le Path: AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20180902.n.0.ppc64le.qcow2 Image: Container_Minimal_Base docker ppc64le Path: Container/ppc64le/images/Fedora-Container-Minimal-Base-29-20180902.n.0.ppc64le.tar.xz Image: Astronomy_KDE live i386 Path: Labs/i386/iso/Fedora-Astronomy_KDE-Live-i386-29-20180902.n.0.iso Image: AtomicHost raw-xz ppc64le Path: AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20180902.n.0.ppc64le.raw.xz Image: Cloud_Base raw-xz ppc64le Path: Cloud/ppc64le/images/Fedora-Cloud-Base-29-20180902.n.0.ppc64le.raw.xz Image: Container_Base docker ppc64le Path: Container/ppc64le/images/Fedora-Container-Base-29-20180902.n.0.ppc64le.tar.xz Image: Cloud_Base qcow2 ppc64le Path: Cloud/ppc64le/images/Fedora-Cloud-Base-29-20180902.n.0.ppc64le.qcow2 = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: sssd-2.0.0-3.fc29 Old package: sssd-2.0.0-1.fc29 Summary: System Security Services Daemon RPMs: libipa_hbac libipa_hbac-devel libsss_autofs libsss_certmap libsss_certmap-devel libsss_idmap libsss_idmap-devel libsss_nss_idmap libsss_nss_idmap-devel libsss_simpleifp libsss_simpleifp-devel libsss_sudo python2-libipa_hbac python2-libsss_nss_idmap python2-sss python2-sss-murmur python2-sssdconfig python3-libipa_hbac python3-libsss_nss_idmap python3-sss python3-sss-murmur python3-sssdconfig sssd sssd-ad sssd-client sssd-common sssd-common-pac sssd-dbus sssd-ipa sssd-kcm sssd-krb5 sssd-krb5-common sssd-ldap sssd-libwbclient sssd-libwbclient-devel sssd-nfs-idmap sssd-proxy sssd-tools sssd-winbind-idmap Size: 23.53 MiB Size change: -8.46 KiB Changelog: * Wed Aug 29 2018 Michal ??idek - 2.0.0-2 - Fix linking issues * Wed Aug 29 2018 Michal ??idek - 2.0.0-3 - Resolves: rhbz#1622760 - Console login as FreeIPA domain user fails in current Fedora Rawhide / 29 = DOWNGRADED PACKAGES =___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Building multiple version of a package from same dist-git repo
On Sun, 2018-09-02 at 17:51 +0200, Igor Gnatenko wrote: > Hello, > > is it possible to build packages like foo0.6 from dist-git repo with name > foo and not foo0.6? > > Since in Rust ecosystem from time to time we need to build multiple > versions of a same package, it is much easier if it would be one repo with > branches 0.6, 0.7 instead of multiple separate git repos. > > If not, what are the limitations? Isn't this exactly what https://fedoraproject.org/wiki/Changes/ArbitraryBranching was supposed to be about? Not that I've seen many (any?) packages actually using it. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Headsup: dbus 1.12.10-1.fc29 is missing systemd dbus.service file, breaking almost everything
On Sun, 2018-09-02 at 08:58 -0700, stan wrote: > On Sun, 2 Sep 2018 09:33:39 +0200 > Andreas Tunek wrote: > > > There is no root acoount on a default F29 installation. Also, you > > can't see the boot menu and I haven't been able to trigger it. > > Whoa! I'm not sure what that buys, but I'll change that as soon as > possible when I install it. That's crazy! Maybe someone wants to > imitate a Mac or something. It's a Change that was properly announced and extensively discussed on this list. (Though it's unfortunate that this situation is apparently not considered a 'failed' boot by the mechanism that's supposed to make sure the boot menu *is* shown after a failed boot). https://fedoraproject.org/wiki/Changes/HiddenGrubMenu https://bugzilla.redhat.com/show_bug.cgi?id=1592201 > "Don't you trouble your pretty little head > about what is going on behind the scenes, dearie, it is all taken > care of. You just watch the pretty pictures, leave the driving to us." > And that's reasonable for a certain class of users. Please avoid implicitly gendered language like this, that's not cool, and you don't need it to make your point. > > Is there a guide or something how to do that? > > Alexander gave you one option, here are a couple of others. > > http://www.system-rescue-cd.org/ > > https://www.fossmint.com/linux-rescue-recovery-tools/ > > A Fedora livecd would also work, anything that can boot the system > without using the installed image. The advantage of using a recent > fedora live image is that the kernel and packages will be compatible. > > > Disk is not cheap on my test laptop unfortunately... > > There isn't even 80 GB, maybe less, free to clone the current version > before you update? An rsync makes this easy, though you should > probably do it from a live image so the temporary stuff created during > boot isn't there. > > > I think that install is gone and all I can do is reinstall. Not very > > fun. > > I think you can recover, though it will be some work. In your > situation, I would try to recover, as I think a reinstall will take > more time and effort than a recovery. > > All that is needed is to either downgrade dbus, or update it to the > repaired version. You could just go to koji, grab the fixed dbus rpms, > https://koji.fedoraproject.org/koji/buildinfo?buildID=1140329 > cp them into the installed system from the rescue environment, > chroot into the installed system from the rescue environment, > and then run > dnf -C update [the koji files, space separated] > or > rpm -ivh [the koji files, space separated] > Then leave the chroot with > exit > and shutdown. > > After that, booting into the system should work as dbus will be > repaired. Actually, I think the title of this thread is wrong. At least in my testing, 1.12.10-2.fc29 is the *broken* package. 1.12.10-1.fc29 is fine. It's when you upgrade to 1.12.10-2.fc29 that things go sideways. To fix things you need to either enable dbus-daemon.service or downgrade to -1. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Headsup: dbus 1.12.10-1.fc29 is missing systemd dbus.service file, breaking almost everything
On Sun, 2 Sep 2018 09:33:39 +0200 Andreas Tunek wrote: > There is no root acoount on a default F29 installation. Also, you > can't see the boot menu and I haven't been able to trigger it. Whoa! I'm not sure what that buys, but I'll change that as soon as possible when I install it. That's crazy! Maybe someone wants to imitate a Mac or something. "Don't you trouble your pretty little head about what is going on behind the scenes, dearie, it is all taken care of. You just watch the pretty pictures, leave the driving to us." And that's reasonable for a certain class of users. > Is there a guide or something how to do that? Alexander gave you one option, here are a couple of others. http://www.system-rescue-cd.org/ https://www.fossmint.com/linux-rescue-recovery-tools/ A Fedora livecd would also work, anything that can boot the system without using the installed image. The advantage of using a recent fedora live image is that the kernel and packages will be compatible. > Disk is not cheap on my test laptop unfortunately... There isn't even 80 GB, maybe less, free to clone the current version before you update? An rsync makes this easy, though you should probably do it from a live image so the temporary stuff created during boot isn't there. > I think that install is gone and all I can do is reinstall. Not very > fun. I think you can recover, though it will be some work. In your situation, I would try to recover, as I think a reinstall will take more time and effort than a recovery. All that is needed is to either downgrade dbus, or update it to the repaired version. You could just go to koji, grab the fixed dbus rpms, https://koji.fedoraproject.org/koji/buildinfo?buildID=1140329 cp them into the installed system from the rescue environment, chroot into the installed system from the rescue environment, and then run dnf -C update [the koji files, space separated] or rpm -ivh [the koji files, space separated] Then leave the chroot with exit and shutdown. After that, booting into the system should work as dbus will be repaired. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Building multiple version of a package from same dist-git repo
Hello, is it possible to build packages like foo0.6 from dist-git repo with name foo and not foo0.6? Since in Rust ecosystem from time to time we need to build multiple versions of a same package, it is much easier if it would be one repo with branches 0.6, 0.7 instead of multiple separate git repos. If not, what are the limitations? -- -Igor Gnatenko ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora rawhide compose report: 20180902.n.0 changes
OLD: Fedora-Rawhide-20180831.n.0 NEW: Fedora-Rawhide-20180902.n.0 = SUMMARY = Added images:6 Dropped images: 0 Added packages: 10 Dropped packages:0 Upgraded packages: 42 Downgraded packages: 0 Size of added packages: 4.79 MiB Size of dropped packages:0 B Size of upgraded packages: 679.91 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 9.20 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: AtomicHost qcow2 ppc64le Path: AtomicHost/ppc64le/images/Fedora-AtomicHost-Rawhide-20180902.n.0.ppc64le.qcow2 Image: Cloud_Base raw-xz ppc64le Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20180902.n.0.ppc64le.raw.xz Image: Container_Base docker ppc64le Path: Container/ppc64le/images/Fedora-Container-Base-Rawhide-20180902.n.0.ppc64le.tar.xz Image: Cloud_Base qcow2 ppc64le Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20180902.n.0.ppc64le.qcow2 Image: AtomicHost raw-xz ppc64le Path: AtomicHost/ppc64le/images/Fedora-AtomicHost-Rawhide-20180902.n.0.ppc64le.raw.xz Image: Container_Minimal_Base docker ppc64le Path: Container/ppc64le/images/Fedora-Container-Minimal-Base-Rawhide-20180902.n.0.ppc64le.tar.xz = DROPPED IMAGES = = ADDED PACKAGES = Package: R-fontBitstreamVera-0.1.1-2.fc30 Summary: Fonts with 'Bitstream Vera Fonts' License RPMs:R-fontBitstreamVera Size:239.91 KiB Package: R-fontLiberation-0.1.0-2.fc30 Summary: Liberation Fonts RPMs:R-fontLiberation Size:1.50 MiB Package: appeditor-1.1.0-1.fc30 Summary: Edit application menu RPMs:appeditor Size:491.61 KiB Package: elementary-print-0.1.3-1.fc30 Summary: Simple shim for printing support via Contractor RPMs:elementary-print Size:81.52 KiB Package: golang-github-git-lfs-gitobj-0-0.1.20180831git5aa0c18.fc30 Summary: Read and write Git objects RPMs:golang-github-git-lfs-gitobj-devel Size:50.83 KiB Package: libmpris-qt5-0.1.0-1.fc30 Summary: Qt and QML MPRIS interface and adaptor RPMs:libmpris-qt5 libmpris-qt5-devel Size:710.79 KiB Package: python-nose-ignore-docstring-0.2-1.fc30 Summary: Ignore docstring to name tests in nose RPMs:python2-nose-ignore-docstring python3-nose-ignore-docstring Size:22.67 KiB Package: python-sphinxtesters-0.2.1-1.fc30 Summary: Utilities for testing Sphinx extensions RPMs:python2-sphinxtesters python3-sphinxtesters Size:69.72 KiB Package: rust-timerfd-1.0.0-1.fc30 Summary: Rust interface to the Linux kernel's timerfd API RPMs:rust-timerfd-devel Size:13.78 KiB Package: termy-server-1.1.0-2.fc30 Summary: TermySequence terminal multiplexer server RPMs:termy-server termy-shell-integration-bash Size:1.65 MiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: R-TH-data-1.0.9-1.fc30 Old package: R-TH-data-1.0.6-7.fc29 Summary: Data for other R packages RPMs: R-TH-data Size: 8.08 MiB Size change: 3.11 MiB Changelog: * Sat Sep 01 2018 Jos?? Matos - 1.0.9-1 - update to 1.0-9 - remove buildroot Package: R-multcomp-1.4.8-1.fc30 Old package: R-multcomp-1.4.5-6.fc29 Summary: Simultaneous inference for general linear hypotheses R Package RPMs: R-multcomp Size: 714.55 KiB Size change: 4.20 KiB Changelog: * Sat Sep 01 2018 Jos?? Matos - 1.4.8-1 - update to 1.4-8 Package: R-systemfit-1.1.22-1.fc30 Old package: R-systemfit-1.1.15-12.fc29 Summary: Simultaneous Equation Estimation R Package RPMs: R-systemfit Size: 813.94 KiB Size change: -12.92 KiB Changelog: * Sat Sep 01 2018 Jos?? Matos - 1.1.22-1 - update to 1.1-22 - update url and source0 to newer versions Package: audit-3.0-0.4.20180831git0047a6c.fc30 Old package: audit-3.0-0.2.20180808git77fbcf3.fc29 Summary: User space tools for 2.6 kernel auditing RPMs: audispd-plugins audispd-plugins-zos audit audit-libs audit-libs-devel audit-libs-static python2-audit python3-audit Size: 4.33 MiB Size change: 14.68 KiB Changelog: * Fri Aug 31 2018 Steve Grubb 3.0-0.4.20180831git0047a6c - New upstream feature prerelease Package: autowrap-0.17.0-4.fc30 Old package: autowrap-0.17.0-3.fc29 Summary: Generates Python Extension modules from [Cython] PXD files RPMs: python3-autowrap Dropped RPMs: python2-autowrap Size: 93.71 KiB Size change: -93.93 KiB Changelog: * Sat Sep 01 2018 Antonio Trande - 0.17.0-4 - Deprecate python2 on fedora 30+ - Prepare SPEC file for python3 migration on epel7 Package: bcm283x-firmware-20180829-2.ec3f856.fc30 Old package: bcm283x-firmware-20180810-1.953a339.fc29 Summary: Broadcom bcm283x firmware for the Raspberry Pi RPMs: bcm283x-firmware Size: 11.34 MiB Size change: 12.51 KiB Changelog: * Fri Aug 31 2018 Peter Robinson 20180829-1.ec3f856 - Latest firmware update - Change locations of firmware - Migration bits for ARMv7 - Prepare
Re: Headsup: dbus 1.12.10-1.fc29 is missing systemd dbus.service file, breaking almost everything
On Sun, Sep 2, 2018 at 9:34 AM Andreas Tunek wrote: > > Den lör 1 sep. 2018 kl 15:50 skrev stan : > > Or, if you can boot a rescue image, you can then use chroot to do a dnf > > update of F29, should be something like > > chroot /mnt/Sysimage dnf update > > where /mnt/Sysimage is the root directory of the F29 installation. > > > > Is there a guide or something how to do that? https://docs.fedoraproject.org/en-US/Fedora/23/html/Multiboot_Guide/common_operations_appendix.html You can chroot into the installed system from a live medium and it doesn't even have to be a Fedora one. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Headsup: dbus 1.12.10-1.fc29 is missing systemd dbus.service file, breaking almost everything
Den lör 1 sep. 2018 kl 15:50 skrev stan : > > On Sat, 1 Sep 2018 13:44:56 +0200 > Andreas Tunek wrote: > > > I can't get a commandline, everything seems stuck in the boot > > process Is there anyway to get a commandline and update the system > > when it is in this state? > > You could try getting to single user mode, putting a 1 after the boot > line during boot by editing the menu entry before booting. That should > put you into the root account, where you can run a dnf update. > There is no root acoount on a default F29 installation. Also, you can't see the boot menu and I haven't been able to trigger it. > Or, if you can boot a rescue image, you can then use chroot to do a dnf > update of F29, should be something like > chroot /mnt/Sysimage dnf update > where /mnt/Sysimage is the root directory of the F29 installation. > Is there a guide or something how to do that? > I've done this successfully in the past from an older version of Fedora > for rawhide update in a situation like you are experiencing, and it has > worked. I always keep an older version of Fedora (the last one I used > before this one) around for just this purpose (disk is cheap). Disk is not cheap on my test laptop unfortunately... I think that install is gone and all I can do is reinstall. Not very fun. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
