Re: Scriptlet Failure When Upgrading (F23)
Rex already fixed it, he says :-) Maybe I'll remember some of this next time ;-) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Scriptlet Failure When Upgrading (F23)
I forgot to add the output of: rpm -q --scripts appstream postinstall program: /sbin/ldconfig postuninstall program: /sbin/ldconfig posttrans scriptlet (using /bin/sh): /usr/bin/appstreamcli refresh-index --force >& /dev/null ||: I'm afraid that doesn't tell me a whole lot ;-) I guess it's supposed to run ldconfig both before and after installing? ldconfig was a list of the system libraries? It's been years since I poked around in that stuff, so I don't recall exactly. Then, the posttrans (is that also after running the install?) calls the command line version of the program to update its index and skip the output. I think I got the gist of it :-) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Self Introduction - Luis Riquelme
Hello Folks ! I'm Luis Riquelme, i'm from Chile and I've using Linux since 2006, but i start using Fedora since Laughlin version. Actually i'm finish the career of Software Engineer but my focus is be informatic teacher for children. obviously using Fedora as Distro in the school and Open Sources Tools. Well my skills are Ruby,Javascript and GO (but not to much ). Also i don't have to much knowledge about QA, but testing package will be a good experience for me. I Know that Fedora will be out soon released, so i'm not sure if my help is helpful for the community, but anyway i'm ready for help to the open source !! my best regards :) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Scriptlet Failure When Upgrading (F23)
Adam Williamson wrote: > On Fri, 2015-10-02 at 20:42 -0600, P. Gueckel wrote: >> Adam Williamson wrote: >> >> > In practice, the best thing to do about scriptlet >> fails is to file a >> > bug any time you see one, and try to figure out what >> specifically the >> > scriptlet that failed *was*, and what it was meant >> to do. If it >> > actually needed to do something in your particular >> context, re-do that >> > thing manually. >> >> Thanks for the great and detailed answer :-) It's nice >> to be told what is really going on and not just be >> given a yes/no response that doesn't increase one's >> knowledge or tell much of anything at all. >> >> OK. I guess that's the least I can do, since I am a de >> facto tester of F23, having installed the ß to a spare >> partition :-) >> >> I recall which package it was, pretty much ;-) It was >> almost certainly appstream, but it could have been >> appstream-data or appstream-qt, but I don't think it >> was. > > I think you should be able to retrieve the error message from dnf > history. Try 'dnf history list', identify the transaction (you should > be able to spot it from the number of packages changed, or you can just > go through the last few) and do 'dnf history info (number)'. It should > show the log and you can see the exact message again. > > You can see the actual scriptlets in the package either with 'rpm -q -- > scripts (packagename)' - which will show you the scriptlets as they > exist in the *current installed* version - or in package git, > http://pkgs.fedoraproject.org/cgit/(packagename).git (where you can > obviously go back through earlier versions). scriptlet ordering is > documented here: > > https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Ordering > > Just above it, there's a table of the weird "$1 == n" conditionals you > will find yourself wondering about :) Basically the scriptlets are > passed a value indicating the nature of the transaction: whether the > package is being installed for the first time, updated, or removed. You > will often find that a scriptlet only does anything at all in one of > those cases, or does very different things in different cases. That's pretty cool, but I'm not sure what I should do with it ;-) I guess I could post it to the bug report. Here is what it says: Scriptlet output: 1 disabled 2 disabled 3 disabled 4 disabled 5 /sbin/ldconfig: relative path `1' used to build cache 6 warning: %postun(appstream-0.8.4-1.fc23.x86_64) scriptlet failed, exit status 1 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Scriptlet Failure When Upgrading (F23)
On Fri, 2015-10-02 at 20:42 -0600, P. Gueckel wrote: > Adam Williamson wrote: > > > In practice, the best thing to do about scriptlet > fails is to file a > > bug any time you see one, and try to figure out what > specifically the > > scriptlet that failed *was*, and what it was meant > to do. If it > > actually needed to do something in your particular > context, re-do that > > thing manually. > > Thanks for the great and detailed answer :-) It's nice > to be told what is really going on and not just be > given a yes/no response that doesn't increase one's > knowledge or tell much of anything at all. > > OK. I guess that's the least I can do, since I am a de > facto tester of F23, having installed the ß to a spare > partition :-) > > I recall which package it was, pretty much ;-) It was > almost certainly appstream, but it could have been > appstream-data or appstream-qt, but I don't think it > was. I think you should be able to retrieve the error message from dnf history. Try 'dnf history list', identify the transaction (you should be able to spot it from the number of packages changed, or you can just go through the last few) and do 'dnf history info (number)'. It should show the log and you can see the exact message again. You can see the actual scriptlets in the package either with 'rpm -q -- scripts (packagename)' - which will show you the scriptlets as they exist in the *current installed* version - or in package git, http://pkgs.fedoraproject.org/cgit/(packagename).git (where you can obviously go back through earlier versions). scriptlet ordering is documented here: https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Ordering Just above it, there's a table of the weird "$1 == n" conditionals you will find yourself wondering about :) Basically the scriptlets are passed a value indicating the nature of the transaction: whether the package is being installed for the first time, updated, or removed. You will often find that a scriptlet only does anything at all in one of those cases, or does very different things in different cases. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Self Introduction: Shyam
Hi guys, This is Shyam, and I am here as I am interested and want to contribute to the fedora QA project/team. I have been using linux since early 2014. I enjoy linux. I have found a lot of help from community online whenever I have faced issue in my computer. I want to contribute back now. Although a novice in it, but i like to show few tricks in vim editor to my friends. I am also learning C and Bash. I hope I can make some contribution, and thank you for letting me join. Regards, Shyam -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Scriptlet Failure When Upgrading (F23)
Adam Williamson wrote: > In practice, the best thing to do about scriptlet fails is to file a > bug any time you see one, and try to figure out what specifically the > scriptlet that failed *was*, and what it was meant to do. If it > actually needed to do something in your particular context, re-do that > thing manually. Thanks for the great and detailed answer :-) It's nice to be told what is really going on and not just be given a yes/no response that doesn't increase one's knowledge or tell much of anything at all. OK. I guess that's the least I can do, since I am a de facto tester of F23, having installed the ß to a spare partition :-) I recall which package it was, pretty much ;-) It was almost certainly appstream, but it could have been appstream-data or appstream-qt, but I don't think it was. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Scriptlet Failure When Upgrading (F23)
On Fri, 2015-10-02 at 16:44 -0600, P. Gueckel wrote: > I read somewhere that, when a scriptlet fails during > upgrade, one need only turn off selinux, run the > upgrade, and then turn selinux back on. That's basically woo - someone once hit a scriptlet fail that happened to be SELinux related, and has thus concluded that *all* scriptlet fails *ever* must be SELinux related. This is, of course, not true. scriptlets are generic; practically speaking they can do absolutely anything. It thus follows that they can fail in more or less any way. Sometimes they can fail because of some SELinux problem, sure. They can also fail for just about any other reason. > Fine, but I won't know in advance that a scriptlet is > going to fail and I'm not disabling selinux every time > I upgrade some packages, just in case there are some > pesky failing scriptlets, so... > > 1. Do I even need to worry about those scriptlets that > failed? Will something not be ungraded correctly and, > hence, not work or not be configured as intended? Potentially, yes. scriptlets are there to *do* something, they're not just decoration. If they fail then something which needed to happen may not have happened. > 2. Since the package already got upgraded, but the > scriptlets didn't, can I repeat the upgrade of the > package in question? How? Not...easily. This is one of the icky-ish little secret corners of RPM packaging. scriptlets are often conditional: they do something when you're upgrading the package but not when you're installing it fresh, or vice versa, or when you're removing it but not upgrading it, etc etc. Thus it's not really possible to have a magic button which just says Run The Scriptlets For Package X, because which scriptlets were run and what they actually do depends heavily on what you were *doing* to Package X. There's also this fun: when you upgrade from foo-1.0-1 to foo-2.0-1, some scriptlets that are *part of foo-1.0-1 specifically* get run - but once the process is complete, those precise scriptlets no longer exist anywhere on your system, so you *can't* re-run them. You now have the scriptlets from foo-2.0-1 - but the %postun of foo-2.0-1 (which will get run when it's removed or updated) may not be the same as the %postun of foo-1.0-1 (which got run when you updated from foo-1.0-1 to foo-2.0-1). Yeah, it's a little tricky :/ In practice, the best thing to do about scriptlet fails is to file a bug any time you see one, and try to figure out what specifically the scriptlet that failed *was*, and what it was meant to do. If it actually needed to do something in your particular context, re-do that thing manually. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Scriptlet Failure When Upgrading (F23)
I read somewhere that, when a scriptlet fails during upgrade, one need only turn off selinux, run the upgrade, and then turn selinux back on. Fine, but I won't know in advance that a scriptlet is going to fail and I'm not disabling selinux every time I upgrade some packages, just in case there are some pesky failing scriptlets, so... 1. Do I even need to worry about those scriptlets that failed? Will something not be ungraded correctly and, hence, not work or not be configured as intended? 2. Since the package already got upgraded, but the scriptlets didn't, can I repeat the upgrade of the package in question? How? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: problems with redhat bugzilla?
On 03/10/15 01:23, Sérgio Basto wrote: On Sex, 2015-10-02 at 12:37 +0200, Karel Volný wrote: Maybe my assumption was not totally correct but now bugzilla says: The password must contain at least one: letter special character digit and 8 characters minimum length if Bugzilla enforce 8 characters minimum length , it is a strong password ! if not , it should. Thanks, 8 seems a bit short for an external password, I tend to use 16 characters like: KRTbut I'm aware that most people would not attempt to cope with such passwords! Cheers, Gavin -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Get Latest Kernel To Boot By Default In F23
I messed something up by manually installing the kernel-PAE package (my kernel supports pae and nx). Then, I read that PAE is only useful with more than 4Gb of memory, which my laptop does not have, so I went back to the default kernel. This is easier, anyway, as it requires no extra work for me, in the future. However, now my grub2 menu is messed up. 1. The oldest (third in the list) kernel is always the one that is set to boot, so I have to manually select the newest kernel every time I switch the laptop on. 2. The nice default menu with the extra features for each kernel that drop open when selected is no longer present. I checked the /etc/default/grub file and the contents are exactly the same as the file on my desktop computer, which does default to the newest kernel, so the problem is not with saving. I have selected the newest kernel and booted a number of times, but it never gets saved. There is some other problem afoot here. How can I get the latest kernel selected by default (top of the grub2 menu list) and also have the extra options for each kernel in the drop-down menu restored? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: problems with redhat bugzilla?
On Sex, 2015-10-02 at 17:11 -0400, Felix Miata wrote: > Sérgio Basto composed on 2015-10-02 13:23 (UTC+0100): > > > On Sex, 2015-10-02 at 12:37 +0200, Karel Volný wrote: > > >> > Maybe my assumption was not totally correct but now bugzilla says: > > >> > The password must contain at least one: > > >> > letter > >> > special character > >> > digit > > >> and 8 characters minimum length > > > if Bugzilla enforce 8 characters minimum length , it is a strong > > password ! > > if not , it should. > > Why? Exactly what is the risk that someone could access BZ via password theft > vs. creating an account? What could be lost by keeping the old password > requirement? Stealing a password of a privileged user, can compromised Bugzilla, can be stolen ‘security-sensitive' information etc . We have the recent new with Mozilla: "Mozilla says hacker compromised Bugzilla and used stolen ‘security-sensitive’ info to attack Firefox users" and they did the attack . > -- > "The wise are known for their understanding, and pleasant > words are persuasive." Proverbs 16:21 (New Living Translation) > > Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! > > Felix Miata *** http://fm.no-ip.com/ > -- Sérgio M. B. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: problems with redhat bugzilla?
Sérgio Basto composed on 2015-10-02 13:23 (UTC+0100): > On Sex, 2015-10-02 at 12:37 +0200, Karel Volný wrote: >> > Maybe my assumption was not totally correct but now bugzilla says: >> > The password must contain at least one: >> > letter >> > special character >> > digit >> and 8 characters minimum length > if Bugzilla enforce 8 characters minimum length , it is a strong > password ! > if not , it should. Why? Exactly what is the risk that someone could access BZ via password theft vs. creating an account? What could be lost by keeping the old password requirement? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 21 updates-testing report
The following Fedora 21 Security updates need testing: Age URL 244 https://bodhi.fedoraproject.org/updates/FEDORA-2015-1467 openstack-glance-2014.1.3-4.fc21 125 https://bodhi.fedoraproject.org/updates/FEDORA-2015-9090 fossil-1.33-1.fc21 125 https://bodhi.fedoraproject.org/updates/FEDORA-2015-9141 ceph-deploy-1.5.25-1.fc21 113 https://bodhi.fedoraproject.org/updates/FEDORA-2015-9744 squid-3.4.13-1.fc21 57 https://bodhi.fedoraproject.org/updates/FEDORA-2015-12773 python-kdcproxy-0.3.2-1.fc21 41 https://bodhi.fedoraproject.org/updates/FEDORA-2015-1fed73bab8 conntrack-tools-1.4.2-9.fc21 37 https://bodhi.fedoraproject.org/updates/FEDORA-2015-14179 libreswan-3.15-1.fc21 37 https://bodhi.fedoraproject.org/updates/FEDORA-2015-14200 sblim-sfcb-1.4.8-5.fc21 37 https://bodhi.fedoraproject.org/updates/FEDORA-2015-14211 ntp-4.2.6p5-33.fc21 28 https://bodhi.fedoraproject.org/updates/FEDORA-2015-14849 libvdpau-1.1.1-1.fc21 28 https://bodhi.fedoraproject.org/updates/FEDORA-2015-14852 libwmf-0.2.8.4-46.fc21 27 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15061 bind-9.9.6-11.P1.fc21 25 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15128 389-ds-base-1.3.3.13-1.fc21 23 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15290 ipsilon-1.1.0-1.fc21 17 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15768 bugzilla-4.4.10-1.fc21 16 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15859 unzip-6.0-22.fc21 15 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15935 libvpx-1.3.0-7.fc21 12 https://bodhi.fedoraproject.org/updates/FEDORA-2015-16238 nagios-4.0.8-1.fc21 9 https://bodhi.fedoraproject.org/updates/FEDORA-2015-16368 qemu-2.1.3-11.fc21 5 https://bodhi.fedoraproject.org/updates/FEDORA-2015-015aec3bf2 xen-4.4.3-4.fc21 0 https://bodhi.fedoraproject.org/updates/FEDORA-2015-bf08670f31 firefox-41.0-6.fc21 0 https://bodhi.fedoraproject.org/updates/FEDORA-2015-6999afd53e webkitgtk3-2.4.9-2.fc21 webkitgtk-2.4.9-2.fc21 The following Fedora 21 Critical Path updates have yet to be approved: Age URL 189 https://bodhi.fedoraproject.org/updates/FEDORA-2015-4638 lcms2-2.7-1.fc21 76 https://bodhi.fedoraproject.org/updates/FEDORA-2015-11787 redhat-rpm-config-29-1.fc21 63 https://bodhi.fedoraproject.org/updates/FEDORA-2015-12402 gstreamer1-plugins-good-1.4.5-3.fc21 51 https://bodhi.fedoraproject.org/updates/FEDORA-2015-13233 yum-utils-1.1.31-28.fc21 51 https://bodhi.fedoraproject.org/updates/FEDORA-2015-13239 yum-3.4.3-154.fc21 41 https://bodhi.fedoraproject.org/updates/FEDORA-2015-13877 libteam-1.18-1.fc21 41 https://bodhi.fedoraproject.org/updates/FEDORA-2015-13805 tigervnc-1.5.0-2.fc21 41 https://bodhi.fedoraproject.org/updates/FEDORA-2015-90d3a9ce48 dracut-038-40.git20150819.fc21 41 https://bodhi.fedoraproject.org/updates/FEDORA-2015-37e78bb9af btrfs-progs-4.1.2-1.fc21 40 https://bodhi.fedoraproject.org/updates/FEDORA-2015-14019 nss-3.20.0-1.0.fc21 nss-softokn-3.20.0-1.0.fc21 nss-util-3.20.0-1.0.fc21 38 https://bodhi.fedoraproject.org/updates/FEDORA-2015-14070 selinux-policy-3.13.1-105.21.fc21 34 https://bodhi.fedoraproject.org/updates/FEDORA-2015-14405 abrt-2.3.0-10.fc21 libreport-2.3.0-9.fc21 27 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15061 bind-9.9.6-11.P1.fc21 19 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15683 fedora-repos-21-3 19 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15614 mesa-10.4.7-2.20150323.fc21 17 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15811 attr-2.4.47-10.fc21 17 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15805 gnutls-3.3.18-1.fc21 16 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15882 libassuan-2.3.0-1.fc21 16 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15862 libtalloc-2.1.2-1.fc21 samba-4.1.20-1.fc21 16 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15859 unzip-6.0-22.fc21 15 https://bodhi.fedoraproject.org/updates/FEDORA-2015-15935 libvpx-1.3.0-7.fc21 14 https://bodhi.fedoraproject.org/updates/FEDORA-2015-16099 satyr-0.20-1.fc21 abrt-2.3.0-11.fc21 12 https://bodhi.fedoraproject.org/updates/FEDORA-2015-16193 python-slip-0.6.4-1.fc21 11 https://bodhi.fedoraproject.org/updates/FEDORA-2015-16286 hwdata-0.282-1.fc21 9 https://bodhi.fedoraproject.org/updates/FEDORA-2015-16443 man-db-2.6.7.1-18.fc21 5 https://bodhi.fedoraproject.org/updates/FEDORA-2015-09978b8539 koji-1.10.0-2.fc21 5 https://bodhi.fedoraproject.org/updates/FEDORA-2015-b4c6dd8cd3 perl-5.18.4-310.fc21 5 https://bodhi.fedoraproject.org/updates/FEDORA-2015-5d4e159c10 python-2.7.8-15.fc21 python3-3.4.1-18.fc21 0 https://bodhi.fedoraproject.org/updates/FEDORA-2015-9bcdcdc46b dnf-0.6.4-7.fc21 0 https://bodhi.fedoraproject.org/updates/FEDORA-2015-6999afd53e webki
Fedora Rawhide 20151002 compose check report
No missing expected images. No images in this compose but not Rawhide 20151001 No images in Rawhide 20151001 but not this. Failed openQA tests: 49 of 52 ID: 4522Test: x86_64 universal server_multi_empty@uefi ID: 4521Test: x86_64 universal server_simple_free_space@uefi ID: 4520Test: x86_64 universal server_multi_empty ID: 4517Test: i386 kde_live default_install ID: 4516Test: x86_64 kde_live default_install ID: 4515Test: x86_64 workstation_live default_install@uefi ID: 4514Test: x86_64 workstation_live default_install ID: 4513Test: i386 workstation_live default_install ID: 4512Test: i386 generic_boot default_install ID: 4511Test: x86_64 generic_boot default_install@uefi ID: 4510Test: x86_64 generic_boot default_install ID: 4509Test: i386 universal upgrade_desktop_32bit ID: 4508Test: i386 universal server_lvmthin ID: 4507Test: i386 universal server_ext3 ID: 4506Test: i386 universal server_btrfs ID: 4505Test: i386 universal server_software_raid ID: 4504Test: i386 universal server_simple_encrypted ID: 4503Test: i386 universal server_repository_http_graphical ID: 4501Test: i386 universal package_set_minimal ID: 4500Test: x86_64 universal server_no_swap@uefi ID: 4499Test: x86_64 universal server_lvmthin@uefi ID: 4498Test: x86_64 universal server_ext3@uefi ID: 4497Test: x86_64 universal server_btrfs@uefi ID: 4496Test: x86_64 universal server_software_raid@uefi ID: 4493Test: x86_64 universal server_simple_encrypted@uefi ID: 4492Test: x86_64 universal server_delete_partial@uefi ID: 4491Test: x86_64 universal server_delete_pata@uefi ID: 4490Test: x86_64 universal server_sata_multi@uefi ID: 4489Test: x86_64 universal european_language_install ID: 4488Test: x86_64 universal server_shrink_ntfs ID: 4487Test: x86_64 universal server_shrink_ext4 ID: 4486Test: x86_64 universal server_updates_img_local ID: 4485Test: x86_64 universal upgrade_desktop_64bit ID: 4484Test: x86_64 universal upgrade_minimal_64bit ID: 4483Test: x86_64 universal server_kickstart_hdd ID: 4482Test: x86_64 universal server_no_swap ID: 4481Test: x86_64 universal server_lvmthin ID: 4480Test: x86_64 universal server_ext3 ID: 4479Test: x86_64 universal server_btrfs ID: 4478Test: x86_64 universal server_software_raid ID: 4476Test: x86_64 universal server_simple_free_space ID: 4475Test: x86_64 universal server_simple_encrypted ID: 4474Test: x86_64 universal server_delete_partial ID: 4473Test: x86_64 universal server_repository_http_variation ID: 4472Test: x86_64 universal server_repository_http_graphical ID: 4471Test: x86_64 universal server_mirrorlist_graphical ID: 4470Test: x86_64 universal server_delete_pata ID: 4467Test: x86_64 universal server_sata_multi ID: 4466Test: x86_64 universal package_set_minimal Passed openQA tests: 3 of 52 -- Mail generated by check-compose: https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 23 Branched 20151002 compose check report
No missing expected images. No images in this compose but not 23 Branched 20151001 No images in 23 Branched 20151001 but not this. Failed openQA tests: 10 of 52 ID: 4462Test: i386 kde_live default_install ID: 4461Test: i386 workstation_live default_install ID: 4458Test: x86_64 kde_live default_install ID: 4454Test: i386 universal upgrade_desktop_32bit ID: 4449Test: i386 universal server_simple_encrypted ID: 4439Test: x86_64 universal server_simple_free_space@uefi ID: 4437Test: x86_64 universal server_delete_partial@uefi ID: 4430Test: x86_64 universal upgrade_desktop_64bit ID: 4429Test: x86_64 universal upgrade_minimal_64bit ID: 4417Test: x86_64 universal server_repository_http_graphical Passed openQA tests: 42 of 52 -- Mail generated by check-compose: https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: problems with redhat bugzilla?
On Sex, 2015-10-02 at 12:37 +0200, Karel Volný wrote: > > Maybe my assumption was not totally correct but now bugzilla says: > > > > The password must contain at least one: > > > > letter > > special character > > digit > > and 8 characters minimum length if Bugzilla enforce 8 characters minimum length , it is a strong password ! if not , it should. Thanks, -- Sérgio M. B. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20151002 changes
Compose started at Fri Oct 2 05:15:03 UTC 2015 Broken deps for i386 -- [CableSwig] CableSwig-3.20.0-13.fc23.i686 requires gccxml [IQmol] IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0 IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0 IQmol-2.3.0-9.fc24.i686 requires libOpenMeshCore.so.3.2 [bro] bro-2.3.2-6.fc23.i686 requires libjemalloc.so.1 [bwm-ng] bwm-ng-0.6-18.fc24.i686 requires libstatgrab.so.6 [derelict] derelict-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-AL-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-AL-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-ALURE-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-ALURE-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-ASSIMP3-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-ASSIMP3-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-FI-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-FI-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-FT-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-FT-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-GL3-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-GL3-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-GLFW3-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-GLFW3-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-IL-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-IL-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-LUA-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-LUA-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-ODE-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-ODE-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-Ogg-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-Ogg-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-PHYSFS-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-PHYSFS-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-PQ-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-PQ-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-SDL2-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-SDL2-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-SFML2-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-SFML2-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 derelict-Vorbis-3-32.20141022git7fc1714.fc23.i686 requires libphobos2-ldc-debug.so.66 derelict-Vorbis-3-32.20141022git7fc1714.fc23.i686 requires libdruntime-ldc-debug.so.66 [gnash] 1:gnash-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_serialization.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_date_time.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_serialization.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_date_time.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 require
F-23 Branched report: 20151002 changes
Compose started at Fri Oct 2 07:15:03 UTC 2015 Broken deps for armhfp -- [CableSwig] CableSwig-3.20.0-13.fc23.armv7hl requires gccxml [apache-scout] apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws) apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:juddi-client) [gmsh] gmsh-libs-2.10.1-2.fc23.armv7hl requires libalglib-3.9.0.so gmsh-mpich-libs-2.10.1-2.fc23.armv7hl requires libalglib-3.9.0.so gmsh-openmpi-libs-2.10.1-2.fc23.armv7hl requires libalglib-3.9.0.so [golang-github-goraft-raft] golang-github-goraft-raft-devel-0-0.6.git73f9c44.fc23.noarch requires golang(code.google.com/p/goprotobuf) [hawaii-shell] hawaii-shell-0.3.0-3.fc22.armv7hl requires libqtaccountsservice-qt5.so.0.1.2 [hbase] hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server) hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json) hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json) hbase-tests-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core) [licq] licq-1.8.2-9.fc23.armv7hl requires libboost_regex.so.1.57.0 [mariadb-galera] 1:mariadb-galera-server-10.0.17-5.fc23.armv7hl requires galera >= 0:25.3.3 [moon-buggy] moon-buggy-1.0.51-14.fc23.armv7hl requires libesd.so.0 [netbeans-platform] 1:netbeans-platform-harness-7.0.1-11.fc22.armv7hl requires cobertura >= 0:1.9.3 [nodejs-grunt-contrib-copy] nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(file-sync-cmp) < 0:0.2 nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(file-sync-cmp) >= 0:0.1.0 nodejs-grunt-contrib-copy-0.8.0-2.fc23.noarch requires npm(chalk) >= 0:0.5.1 [nodejs-grunt-saucelabs] nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(sauce-tunnel) >= 0:2.2.3 nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(requestretry) < 0:1.3 nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(lodash) >= 0:3.7.0 nodejs-grunt-saucelabs-8.6.1-2.fc23.noarch requires npm(colors) >= 0:1.0.0 [oat] oat-appraiser-1.6.0-16.fc22.armv7hl requires tomcat-servlet-3.0-api oat-client-1.6.0-16.fc22.armv7hl requires tomcat-servlet-3.0-api [oozie] oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.pig:pig) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-serde) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-metastore) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-exec) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-common) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive:hive-cli) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive.hcatalog:webhcat-java-client) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive.hcatalog:hcatalog-server-extensions) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive.hcatalog:hcatalog-pig-adapter) oozie-4.0.1-5.fc22.noarch requires mvn(org.apache.hive.hcatalog:hcatalog-core) [openstack-heat-gbp] openstack-heat-gbp-2014.2-2.fc23.noarch requires openstack-heat-engine < 0:2014.3 [openstack-neutron-gbp] openstack-neutron-gbp-2014.2-2.fc23.noarch requires openstack-neutron < 0:2014.3 [openstack-swift] openstack-swift-2.3.0-2.fc23.noarch requires python-pyeclib [polymake] polymake-2.13-22.git20141013.fc23.armv7hl requires perl(:MODULE_COMPAT_5.20.2) polymake-2.13-22.git20141013.fc23.armv7hl requires perl = 4:5.20.2 polymake-2.13-22.git20141013.fc23.armv7hl requires libperl.so.5.20 [publican] publican-4.1.3-3.fc22.noarch requires perl(:MODULE_COMPAT_5.20.0) [pyjigdo] pyjigdo-0.4.0.3-9.fc23.noarch requires fuseiso [python-django-horizon-gbp] openstack-dashboard-gbp-2014.2-2.fc23.noarch requires openstack-dashboard < 0:2014.3 python-django-horizon-gbp-2014.2-2.fc23.noarch requires python-django-horizon < 0:2014.3 [python-fiat] python-fiat-1.5.0-2.fc23.noarch requires ScientificPython [python-gbpclient] python-gbpclient-0.9.0-2.fc23.noarch requires python-neutronclient = 0:2.3.9 [rubygem-font-awesome-rails] rubygem-font-awesome-rails-4.4.0.0-1.fc23.noarch requires fontawesome-fonts >= 0:4.4.0 [tortoisehg] tortoisehg-3.4-2.fc23.noarch requires mercurial < 0:3.4 [tritonus] tritonus-esd-0.3.7-0.23.20101108cvs.fc22.armv7hl requires libesd.so.0 [trustedqsl] tqsllib-devel-2.4-9.fc23.1.armv7hl requires tqsllib(armv7hl-32) = 0:2.4-9.fc23 [vdr-live] vdr-live-0.3.0-21.20150213git6ea279a.fc23.armv7hl requires libtntnet.so.12 vdr-live-0.3.0-21.20150213git6ea
