Upstream, this software supports Python 3. Please provide a Python 3\npackage for Fedora.\n\n\nAccording to the Python packaging guidelines [0], software must be\npackaged for Python 3 if upstream supports it.\nThe guidelines give detailed information on how to do this, and even\nprovide an example spec file [1].\n\nThe current best practice is to provide subpackages for the two Python\nversions (called "Common SRPM" in the guidelines). Alternatively, if\nnothing depends on your Python2 package, you can just switch to Python 3\nentirely.\n\nIt's OK to do this in Rawhide only, however, it would be greatly\nappreciated if you could push it to Fedora 24 as well.\n\n\nIf you need more instructions, a guide for porting Python-based RPMs is\navailable at [2].\nIf anything is unclear, or if you need any kind of assistance with the\nporting, you can ask on IRC (#fedora-python on Freenode), or reply here.\nWe'll be happy to help!\n\n\n[0] https://fedoraproject.org/wiki/Packaging:Python\n[1] https://fedoraproject.org/wiki/Packaging:Python#Example_common_spec_file\n[2] http://python-rpm-porting.readthedocs.io/\n\n
Created attachment 1196619[details]\nadd Python 3 & update version\n\nHi Praveen,\nhere is the change needed to add Python 3 support and update the version. Could you please review it and do the update?\n\nKoji scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=15460598\n\nAlso tested in Mock (fedora-23-x86_64, fedora-24-x86_64, fedora-25-x86_64, fedora-rawhide-x86_64, fedora-rawhide-i386).\n\n
python-setuptools_hg-0.4-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.\n\n
python-setuptools_hg-0.4-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.\n\n
\n
\n\n\n \n\n
\n
\n
\n
\n\n
\n\n \n\n \n"
+ },
+ {
+ "url": "https://bugzilla.redhat.com/show_bug.cgi?id=11259",
+ "domain": "bugzilla.redhat.com",
+ "file_source": "part-00626-d9b45f53-efdc-4ae8-a3e4-b1d5d9e13869-c000",
+ "content": "\n\n \n \n\n \n\n\n\n\n 11259 – Unmounting smbfs shares fails when you are in the path of the share\n\n \n\n\n\n\n\n \n\n\n \n\n\n \n\n \n \n \n \n\n \n
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the \"Satellite project\" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status \"CLOSED\", resolution \"MIGRATED\", and set with \"MigratedToJIRA\" in \"Keywords\". The link to the successor Jira issue will be found under \"Links\", have a little \"two-footprint\" icon next to it, and direct you to the \"Satellite project\" in Red Hat Jira (issue links are of type \"https://issues.redhat.com/browse/SAT-XXXX\", where \"X\" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.\n
qemu-kvm is adding support for the new sandy bridge cpu, including features such as TSC Deadline timer, XSAVE/XRSTOR, etc\n\nlibvirt would need to add a new CPU type\n\n
Upstream commit:\n\ncommit b2cb24f48ba568659e47da26078974ab78161df9\nAuthor: Peter Krempa <pkrempa>\nDate: Thu Dec 8 15:11:52 2011 +0100\n\n cpu: Add cpu flags supported by newest qemu\n \n Add support for newly supported Intel cpu features. Newly supported\n flags are: pclmuldq, dtes64, smx, fma, pdcm, movbe, xsave, osxsave and\n avx. This adds support for Intel's Sandy Bridge platform.\n\n\nadds support for feature flags added newly to qemu. QEmu does not yet expose a Sandy Bridge model, so libvirt does not add it yet either.\n\n
I'm setting this bug to ASSIGNED as we should also add the model to the XML. We need to do some research on the minimum set of flags to be supported by the Sandy bridge cpu.\n\n
The upstream support for Sandy Bridge should be ready soon (patches are submitted). The fix in libvirt will be trivial after qemu will support the new model.\n\n
(In reply to comment #7)\n> The upstream support for Sandy Bridge should be ready soon (patches are\n> submitted). The fix in libvirt will be trivial after qemu will support the new\n> model.\n\nUpstream qemu or libvirt or both?\n\n
Those features that are shown by the capabilities command are extra features that are supported by the host CPU (and inquired by the CPUID instruction) and not defined in the SandyBridge model definition.\n\nThe SandyBride model in qemu that is present in rhel6.3 is defined as:\n\n[cpudef]\n name = "SandyBridge"\n level = "0xd"\n vendor = "GenuineIntel"\n family = "6"\n model = "42"\n stepping = "1"\n feature_edx = " sse2 sse fxsr mmx clflush pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc pse de fpu"\n feature_ecx = "avx xsave aes popcnt x2apic sse4.2 sse4.1 cx16 ssse3 pclmulqdq sse3"\n extfeature_edx = "i64 rdtscp nx syscall "\n extfeature_ecx = "lahf_lm"\n xlevel = "0x8000000A"\n model_id = "Intel Xeon E312xx (Sandy Bridge)"\n\n(note that libvirt uses other names for some flags).\n\n
The SandyBridge CPU model on qemu-kvm will be updated due to bug 767944 (TSC-deadline feature), so libvirt will have to be updated as well.\n\nIs it better to reopen this bug so the model can be fixed after qemu-kvm changes, or open a new bug for libvirt?\n\n
After discussing with Dave, please open a new bug. We will need to revert a RHEL-specific patch that disabled the tsc-deadline feature in SandyBridge that was backported completly from upstream.\n\n
\n Technical note added. If any revisions are required, please edit the "Technical Notes" field\n accordingly. All revisions will be proofread by the Engineering Content Services team.\n \n New Contents:\nLibvirt now supports features provided by the most recent Intel processors.\n\n
\n Technical note updated. If any revisions are required, please edit the "Technical Notes" field\n accordingly. All revisions will be proofread by the Engineering Content Services team.\n \n Diffed Contents:\n@@ -1 +1 @@\n-Libvirt now supports features provided by the most recent Intel processors.+In Red Hat Enterprise Linux 6.3, libvirt has been updated to add support for the latest Intel processors and new features these processors include.\n\n
Since the problem described in this bug report should be\nresolved in a recent advisory, it has been closed with a\nresolution of ERRATA.\n\nFor information on the advisory, and where to find the updated\nfiles, follow the link below.\n\nIf the solution does not work for you, open a new bug report.\n\nhttp://rhn.redhat.com/errata/RHSA-2012-0748.html\n\n
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the \"RHEL project\" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses \"NEW\", \"ASSIGNED\", and \"POST\" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components \"kernel\", \"kernel-rt\", and \"kpatch\" are only migrated if still in \"NEW\" or \"ASSIGNED\". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status \"CLOSED\", resolution \"MIGRATED\", and set with \"MigratedToJIRA\" in \"Keywords\". The link to the successor Jira issue will be found under \"Links\", have a little \"two-footprint\" icon next to it, and direct you to the \"RHEL project\" in Red Hat Jira (issue links are of type \"https://issues.redhat.com/browse/RHEL-XXXX\", where \"X\" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.\n
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the \"RHEL project\" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses \"NEW\", \"ASSIGNED\", and \"POST\" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components \"kernel\", \"kernel-rt\", and \"kpatch\" are only migrated if still in \"NEW\" or \"ASSIGNED\". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status \"CLOSED\", resolution \"MIGRATED\", and set with \"MigratedToJIRA\" in \"Keywords\". The link to the successor Jira issue will be found under \"Links\", have a little \"two-footprint\" icon next to it, and direct you to the \"RHEL project\" in Red Hat Jira (issue links are of type \"https://issues.redhat.com/browse/RHEL-XXXX\", where \"X\" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.\n
QMF did not show the auto-delete flag per exchange, though the feature is planned to be implemented later. In the exchange creating process, the flag is already one of parameters. With this update, the visibility of this not yet implemented flag is introduced.
Description of problem:\nEvery exchange (as queue) can be declared as auto-delete.\n\nPython-qpid tools and qmf as well does not show this bit.\n\nIt would be good to show it.\n\n\nVersion-Release number of selected component (if applicable):\n1.1.6 MRG set and earlier.\n\nHow reproducible:\n100%\n\nSteps to Reproduce:\n1. declare exchange as auto-delete\n2. issue qpid-config exchanges or \n qpid-tool<<<"show org.apache.qpid.broker:exchange"\n\n3. No such flag is available\n\n\nActual results:\nNo exchange auto-delete flag exists.\n\nExpected results:\nIt would be great to add such bit.\n\nAdditional info:\n\n
This bug is fixed upstream in revision 807712.\n\nNote that this only fixes the visibility issue by adding the flag. Since the feature is not supported, the flag will always be false.\n\n
I do not see a straightforward way how to create an exchange\nwith auto-delete flag enabled using qpid-config. How did you\ndo it, Frantisek?\n\nOtherwise, there is row for autoDelete property, which as Ted\nwrites above is still not implemented for exchanges, so it should\nbe always False.\n\nIs ensuring this on to-be-built packages and all RHEL releases\nenough to verify this BZ?\n\n
The creation of the auto-delete exchange can be done via qc_exchange clients.\nFor instance:\n./qc_exchange.py -e rere -t direct --exchange-auto-delete\n\nThe autoDelete property should be present in new version (in contrast to MRG 1.2).\n\nWe are not able to validate the feature, because broker does not implement the feature. So existence of that bit is enough.\n\n
Created attachment 390546[details]\nShell script used to reproduce/verify this bug\n\nThe script does not care about repositories,\nthey have to be enabled implicitly with enablerepo=1\nin appropriate file.\n\n
Verified on mrg-candidate\n(RHEL5 i386 and x86_64)\n qpid-cpp-server-0.7.908272-1.el5\n python-qpid-0.5.904641-1.el5\n\nReproduced on mrg-stable\n(RHEL5 i386 and x86_64)\n qpidd-0.5.752581-34.el5\n python-qpid-0.5.752581-4.el5\n(RHEL4 i386 and x86_64)\n qpidd-0.5.752581-34.el4\n python-qpid-0.5.760500-6.el4\n\nI will test RHEL4 packages as soon as they\narrive in -candidate repo.\n\n
Created attachment 397845[details]\nUpdated reproducer/verifier script\n\nVerified as well on RHEL4 (i386, x86_64):\n qpid-cpp-server-0.7.916826-2.el4\n qpid-tools-0.7.917557-4.el4\n\n
\n Technical note added. If any revisions are required, please edit the "Technical Notes" field\n accordingly. All revisions will be proofread by the Engineering Content Services team.\n \n New Contents:\nQMF did not show the auto-delete flag per exchange, though the feature is planned to be implemented later. In the exchange creating process, the flag is already one of parameters. With this update, the visibility of this not yet implemented flag is introduced.\n\n
An advisory has been issued which should help the problem\ndescribed in this bug report. This report is therefore being\nclosed with a resolution of ERRATA. For more information\non therefore solution and/or where to find the updated files,\nplease follow the link below. You may reopen this bug report\nif the solution does not work for you.\n\nhttp://rhn.redhat.com/errata/RHSA-2010-0773.html\n\n
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the \"RHEL project\" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses \"NEW\", \"ASSIGNED\", and \"POST\" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components \"kernel\", \"kernel-rt\", and \"kpatch\" are only migrated if still in \"NEW\" or \"ASSIGNED\". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status \"CLOSED\", resolution \"MIGRATED\", and set with \"MigratedToJIRA\" in \"Keywords\". The link to the successor Jira issue will be found under \"Links\", have a little \"two-footprint\" icon next to it, and direct you to the \"RHEL project\" in Red Hat Jira (issue links are of type \"https://issues.redhat.com/browse/RHEL-XXXX\", where \"X\" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.\n