BuildRequires: redhat-rpm-config
I had a bug filed that a Python package I'm maintaining cannot be
rebuilt using 'rpmbuild --rebuild'. The failure was that the *.pyc
and *.pyo files are missing.
After a lot of head-scratching and debugging it turns out that
brp-python-bytecompile was not running, and that happens because the
RPM macro %{__os_install_post} didn't contain a call to
brp-python-bytecompile. This macro exists in base RPM, but is
overridden/extended when redhat-rpm-config is installed.
Installing redhat-rpm-config fixes the problem for the bug reporter.
However this raises some questions:
- Should this package explicitly BR redhat-rpm-config?
- Should all Python packages explicitly BuildRequire redhat-rpm-config?
- Should this package not be packaging up the *.py[co] files?
- Is this a bug in redhat-rpm-config/Python/RPM/Fedora?
- Should I just ignore this because it builds fine in Koji?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On Thu, 14 Nov 2013 08:56:22 +
Richard W.M. Jones rjo...@redhat.com wrote:
I had a bug filed that a Python package I'm maintaining cannot be
rebuilt using 'rpmbuild --rebuild'. The failure was that the *.pyc
and *.pyo files are missing.
After a lot of head-scratching and debugging it turns out that
brp-python-bytecompile was not running, and that happens because the
RPM macro %{__os_install_post} didn't contain a call to
brp-python-bytecompile. This macro exists in base RPM, but is
overridden/extended when redhat-rpm-config is installed.
Installing redhat-rpm-config fixes the problem for the bug reporter.
However this raises some questions:
- Should this package explicitly BR redhat-rpm-config?
- Should all Python packages explicitly BuildRequire
redhat-rpm-config?
- Should this package not be packaging up the *.py[co] files?
- Is this a bug in redhat-rpm-config/Python/RPM/Fedora?
- Should I just ignore this because it builds fine in Koji?
I think ignoring is fine, we should rather recommend to do yum install
@buildsys-build before starting to work on Fedora packages
Dan
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On Thu, 2013-11-14 at 10:27 +0100, Dan Horák wrote:
On Thu, 14 Nov 2013 08:56:22 +
Richard W.M. Jones rjo...@redhat.com wrote:
However this raises some questions:
- Should this package explicitly BR redhat-rpm-config?
- Should all Python packages explicitly BuildRequire
redhat-rpm-config?
- Should this package not be packaging up the *.py[co] files?
- Is this a bug in redhat-rpm-config/Python/RPM/Fedora?
- Should I just ignore this because it builds fine in Koji?
Or maybe the other way around, do you have to explictly list the .pyc
and .pyo files in the %files manifest?
Could a slightly larger glob work around the problem?
For example, if right now you have:
%dir %{python_sitelib}/mymodule
%{python_sitelib}/mymodule/*.py
%{python_sitelib}/mymodule/*.pyc
%{python_sitelib}/mymodule/*.pyo
You could replace that by:
%{python_sitelib}/mymodule
The above would include the folder, the .py files, and (if they have
been built) the .py[co] files as well.
Is something like this not possible in your case?
I think ignoring is fine, we should rather recommend to do yum install
@buildsys-build before starting to work on Fedora packages
Or even fedora-packager, which has even more important stuff than
@buildsys-build.
--
Mathieu
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
How to escape question mark / equality sign in spec's source URI to get proper source name
Hello guys, I have one source which has the form of (in the last part of it's URI): checklist-cce-feed?id=295 (the source doesn't seem to be available otherwise than via aforementioned query string - or at least I wasn't able to obtain it's final location past the query = if you known there's a way how to find out the final file location past the query string would be expanded, let me know). For now I present that source URI in the particular spec in it's original form (including the query string to avoid rpmlint to complain about non-existing source, and later in the %install moving that source to some more meaningful name). This works on RHEL5 (maybe question mark / equality sign not having special meaning there yet?), but not for example at Fedora-19. At Fedora 19 rpmbuild strips off the part till equality sign, iow checklist-cce-feed?id= from the source and searches only for '295' = rpmbuild fails with a complain not being able to find rpmbuild/SOURCES/295 file. Have tried to provide source URI in (simple, double) quotes, or escape both of ?, and = characters with backslash, but without any luck (it's visible it won't work in the spec already, since having highlighted the syntax the last source URI part isn't taken / understood as a whole - being in same color already). Wondering if someone needed to solve something like the above already, and what the workaround has been (somehow define the last part of the source URI via %global variable to avoid this?) Thank you Regards, Jan. -- Jan iankko Lieskovsky / Red Hat Security Technologies Team -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Test-Announce] Power Management Test Day today (2013-11-14)
Forwarding an invite from Jan Scotka: Hi, There is planned Power Management testday today. If you are interested to see capabilities of your machine or measure power consumption please join us, you will see what your HW know. Everybody with various HW configuration welcomed (Old New Obscure virt guests) info: https://fedoraproject.org/wiki/Test_Day:2013-11-14_Power_management when: today (Thursday) 14. 11. 2013 where: online: please connect mentioned IRC channels at wiki #fedora-test-day, #fedora-power, #fedora-devel at freenode how: You can install Fedora 20, or use liveCDs mentioned at wiki You are very welcome ThanksRegards Your Power Management team -- Jan Scotka jsco...@redhat.com ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: How to escape question mark / equality sign in spec's source URI to get proper source name
On 11/14/2013 11:12 AM, Mathieu Bridon wrote: On Thu, 2013-11-14 at 05:01 -0500, Jan Lieskovsky wrote: Hello guys, I have one source which has the form of (in the last part of it's URI): checklist-cce-feed?id=295 (the source doesn't seem to be available otherwise than via aforementioned query string - or at least I wasn't able to obtain it's final location past the query = if you known there's a way how to find out the final file location past the query string would be expanded, let me know). For now I present that source URI in the particular spec in it's original form (including the query string to avoid rpmlint to complain about non-existing source, and later in the %install moving that source to some more meaningful name). This works on RHEL5 (maybe question mark / equality sign not having special meaning there yet?), but not for example at Fedora-19. At Fedora 19 rpmbuild strips off the part till equality sign, iow checklist-cce-feed?id= from the source and searches only for '295' = rpmbuild fails with a complain not being able to find rpmbuild/SOURCES/295 file. Maybe use only the name of the source file, and add a comment above explaining that it comes from that URL? Or maybe use an url shortener out there, keeping the real url in a comment ? --alec -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: How to escape question mark / equality sign in spec's source URI to get proper source name
- Original Message - From: Mathieu Bridon boche...@fedoraproject.org To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Thursday, November 14, 2013 11:12:21 AM Subject: Re: How to escape question mark / equality sign in spec's source URI to get proper source name On Thu, 2013-11-14 at 05:01 -0500, Jan Lieskovsky wrote: Hello guys, I have one source which has the form of (in the last part of it's URI): checklist-cce-feed?id=295 (the source doesn't seem to be available otherwise than via aforementioned query string - or at least I wasn't able to obtain it's final location past the query = if you known there's a way how to find out the final file location past the query string would be expanded, let me know). For now I present that source URI in the particular spec in it's original form (including the query string to avoid rpmlint to complain about non-existing source, and later in the %install moving that source to some more meaningful name). This works on RHEL5 (maybe question mark / equality sign not having special meaning there yet?), but not for example at Fedora-19. At Fedora 19 rpmbuild strips off the part till equality sign, iow checklist-cce-feed?id= from the source and searches only for '295' = rpmbuild fails with a complain not being able to find rpmbuild/SOURCES/295 file. Maybe use only the name of the source file, and add a comment above explaining that it comes from that URL? You can use checklist-cce-feed?id=295#nameofthesource.tar.bz2, but I'd say ^ is the best idea. Matt -- Mathieu -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [Fedora-packaging] Schedule for Thursday's FPC Meeting (2013-11-14 17:00 UTC)
Hi Christopher, On Thursday, 14 November 2013 at 08:58, Christopher Meng wrote: On Thu, Nov 14, 2013 at 2:11 PM, Toshio Kuratomi a.bad...@gmail.com wrote: On Thu, Nov 14, 2013 at 06:39:25AM +0800, Christopher Meng wrote: Ticket #350 needs 2 votes on final decision. Please consider. What would help is if you could add to the ticket what makes this different from the situation of rsync bundling zlib or similar. In order to be fair to packagers, we try to either follow precedent in these cases or change the guidelines so that old rejections would know that they could re-apply for an exception if needed. Quoted: Currently haven't voted: Rathann, tibbs So please let the rest part of committee to finish voting first. 4:3 with 2 not available, I'm not sure what I could do here. I added my vote and comments to the ticket. To me about this package, well, I think the comment 5 from the author is very clear. It needs antlr but the orginial sources doesn't work in the way he wants, and will be, never, so he modified the sources. The only thing that it's clear is that current antlr3 doesn't work the way they want. Apparently, however, upstream was never told about those issues. I'd be happy to be proven wrong here, but it looks to me as if codimension parser upstream is doing bundling out of convenience only. Regards, Dominik -- Fedora http://fedoraproject.org/wiki/User:Rathann RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu Faith manages. -- Delenn to Lennier in Babylon 5:Confessions and Lamentations -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
What is support status of PowerVR GPUs in Fedora? (Intel D2500 and gma500_gfx)
Friend of mine just showed me his cheap 13 laptop running Intel D2500 and first thing he said that he had issue installing linux on it. When I asked about GPU and answer was Intel I assured him that for last 10 years I only used Intel GPU based laptops and had great experience. I tried Fedora 19 Live - failed to boot, then Linux Mint 15 - got to screen but with terrible artifacts on screen, check them out - http://youtu.be/mha7fZU1xFg, then tried latest Fedora 20 Live Beta 5 - boot starts with artefacts but fails to boot into desktop. Few hours later after reading up on this issue I managed to get laptop working with Linux Mint 15 (updated kernel to 3.11) but had to blacklist gma500_gfx driver, only then I get somewhat usable laptop (but with lower resolution and no video acceleration). I'm really interested what is the state of gma500_gfx driver in latest kernel, is it reasonable to expect that this driver will get updated and have better support or should I just say to my friend to grab version of Windows 7 and to run with it... any suggestions? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [RFC] mesa 10.0 stack in F20
Hey Igor. Am Donnerstag, den 14.11.2013, 11:45 +0400 schrieb Igor Gnatenko: Actually 9.2.3 doesn't built on armv7 (FDO #71573) and I think more better for new release to get updated mesa stack. Probably mesa 9.2.4 will also has this bug. What do you say about this idea? +1 on preparing for mesa 10.0. With my OpenCL hat on I can tel that we probably need to add some subpackages (gbm for gallium and opencl), so doing and testing this might be good. OTOH I don't know if there are major drawbacks we have from migrating to 10, or if features were dropped which we rely on. As a note: A couple of days back I tried to do a build based on a git snapshot on x86_64, there were some llvm path related problems wich stopped me from further trying. - fabian -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: What is support status of PowerVR GPUs in Fedora? (Intel D2500 and gma500_gfx)
On 11/14/2013 01:05 PM, valent.turko...@gmail.com wrote: Friend of mine just showed me his cheap 13 laptop running Intel D2500 and first thing he said that he had issue installing linux on it. Have you captured dmesg and lspci -v output? That could help us to identify what precise hardware components are involved. -- Florian Weimer / Red Hat Product Security Team -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Base] Base Design WG agenda meeting 15. Nov 2013 15:00 UTC on #fedora-meeting
Agenda for tomorrows meeting: - QE representation - Liaison for FESCO? Volunteers? - Mission statement - PRD (https://fedoraproject.org/wiki/User:Johannbg/FOSSP as an example) - Release Schedule and alignment with other WGs (https://fedorahosted.org/fesco/ticket/1202) - Open floor Thanks regards, Phil -- Philipp Knirsch | Tel.: +49-711-96437-470 Manager Core Services| Fax.: +49-711-96437-111 Red Hat GmbH | Email: Phil Knirsch pknir...@redhat.com Wankelstrasse 5 | Web: http://www.redhat.com/ D-70563 Stuttgart, Germany -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
F-20 Branched report: 20131114 changes
Compose started at Thu Nov 14 09:15:02 UTC 2013 Broken deps for armhfp -- [avro] avro-mapred-1.7.5-1.fc20.noarch requires hadoop-mapreduce avro-mapred-1.7.5-1.fc20.noarch requires hadoop-client [blueman] blueman-1.23-7.fc20.armv7hl requires obex-data-server = 0:0.4.3 blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp [cloud-init] cloud-init-0.7.2-7.fc20.noarch requires dmidecode [cobbler] cobbler-2.4.0-2.fc20.noarch requires syslinux [condor-wallaby] condor-wallaby-client-5.0.3-5.fc20.noarch requires python-qpid-qmf = 0:0.9.1073306 [fence-agents] fence-agents-common-4.0.4-3.fc20.armv7hl requires pexpect [fts] fts-server-3.1.1-1.fc20.armv7hl requires libactivemq-cpp.so.14 [glite-lb-common] glite-lb-common-9.0.7-2.fc20.armv7hl requires libclassad.so.5 [glpi] glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Version glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Stdlib glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-ServiceManager glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Loader glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-I18n glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Cache-apc glpi-0.84.3-1.fc20.noarch requires php-ZendFramework2-Cache [gnome-do-plugins] gnome-do-plugins-thunderbird-0.8.4-14.fc20.armv7hl requires thunderbird [gofer] ruby-gofer-0.75-4.fc20.noarch requires rubygem(qpid) = 0:0.16.0 [gtkd] gtkd-geany-tags-2.0.0-29.20120815git9ae9181.fc18.noarch requires gtkd = 0:2.0.0-29.20120815git9ae9181.fc18 [ipython] python-ipython-console-0.13.2-2.fc20.noarch requires pexpect python3-ipython-console-0.13.2-2.fc20.noarch requires python3-pexpect [kawa] 1:kawa-1.11-5.fc19.armv7hl requires servlet25 [koji] koji-vm-1.8.0-2.fc20.noarch requires python-virtinst [kyua-cli] kyua-cli-0.5-3.fc19.armv7hl requires liblutok.so.0 kyua-cli-tests-0.5-3.fc19.armv7hl requires liblutok.so.0 [mozilla-firetray] mozilla-firetray-thunderbird-0.3.6-0.5.143svn.fc18.1.armv7hl requires thunderbird = 0:11 [msp430-libc] msp430-libc-20120224-2.fc19.noarch requires msp430-gcc = 0:4.6.3 [nifti2dicom] nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtksys.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkWidgets.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkVolumeRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkViews.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkTextAnalysis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkParallel.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkInfovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkImaging.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkIO.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkHybrid.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGraphics.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGeovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGenericFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCommon.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCharts.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libQVTK.so.5.10 [nocpulse-common] nocpulse-common-2.2.7-2.fc20.noarch requires perl(RHN::DBI) [openbox] gdm-control-3.5.2-2.fc20.armv7hl requires gnome-panel gnome-panel-control-3.5.2-2.fc20.armv7hl requires gnome-panel [openlmi-providers] openlmi-0.4.0-1.fc20.noarch requires openlmi-power [openpts] openpts-0.2.6-7.fc20.armv7hl requires tboot [perl-Language-Expr] perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [pure] pure-doc-0.57-4.fc20.noarch requires pure = 0:0.57-4.fc20 [python-tag] python-tag-2013.1-1.fc20.armv7hl requires libboost_python.so.1.53.0 [qpid-cpp] qpid-cpp-server-ha-0.24-6.fc20.armv7hl requires qpid-qmf(armv7hl-32) qpid-tools-0.24-6.fc20.noarch requires python-qpid-qmf [rootplot] rootplot-2.2.1-7.fc19.noarch requires root-python [ruby-spqr] ruby-spqr-0.3.6-7.fc20.noarch requires ruby-qpid-qmf [rubygem-audited-activerecord] rubygem-audited-activerecord-3.0.0-3.fc19.noarch requires rubygem(activerecord) 0:4 [scilab] scilab-doc-5.4.1-4.fc20.noarch requires scilab = 0:5.4.1-4.fc20 scilab-tests-5.4.1-4.fc20.noarch requires scilab = 0:5.4.1-4.fc20 [sigul] sigul-0.100-3.fc20.noarch requires pexpect [spacewalk-admin] spacewalk-admin-2.0.1-2.fc20.noarch requires spacewalk-base
Re: [Base] Base Design WG agenda meeting 15. Nov 2013 15:00 UTC on #fedora-meeting
On Thu, Nov 14, 2013 at 7:49 AM, Phil Knirsch pknir...@redhat.com wrote: Agenda for tomorrows meeting: I'll be away from computers all day tomorrow, so I'll have to send my regrets. I'll follow up in the evening and reply to the minutes with any comments/questions I have. - Liaison for FESCO? Volunteers? Er... that's you Phil. It's who FESCo picked at least until Jan. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [Base] Base Design WG agenda meeting 15. Nov 2013 15:00 UTC on #fedora-meeting
On 11/14/2013 12:49 PM, Phil Knirsch wrote: - PRD (https://fedoraproject.org/wiki/User:Johannbg/FOSSP as an example) Note this is not an PRD by PRD's definition ( which you can clearly see once you start looking those up and those are supposed to be accommodated by MRD's ) This is just an draft in process for the FOSSP I'll need to write one up another page for FOS ( FedoraOS) which will be tailored to core/baseOS. JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: How to escape question mark / equality sign in spec's source URI to get proper source name
On Thu, Nov 14, 2013 at 05:21:04AM -0500, Matej Stuchlik wrote: - Original Message - From: Mathieu Bridon boche...@fedoraproject.org To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Thursday, November 14, 2013 11:12:21 AM Subject: Re: How to escape question mark / equality sign in spec's source URI to get proper source name On Thu, 2013-11-14 at 05:01 -0500, Jan Lieskovsky wrote: Hello guys, I have one source which has the form of (in the last part of it's URI): checklist-cce-feed?id=295 (the source doesn't seem to be available otherwise than via aforementioned query string - or at least I wasn't able to obtain it's final location past the query = if you known there's a way how to find out the final file location past the query string would be expanded, let me know). For now I present that source URI in the particular spec in it's original form (including the query string to avoid rpmlint to complain about non-existing source, and later in the %install moving that source to some more meaningful name). This works on RHEL5 (maybe question mark / equality sign not having special meaning there yet?), but not for example at Fedora-19. At Fedora 19 rpmbuild strips off the part till equality sign, iow checklist-cce-feed?id= from the source and searches only for '295' = rpmbuild fails with a complain not being able to find rpmbuild/SOURCES/295 file. Maybe use only the name of the source file, and add a comment above explaining that it comes from that URL? You can use checklist-cce-feed?id=295#nameofthesource.tar.bz2, but I'd say ^ is the best idea. Or Use checklist-cce-feed?id=295ignorethispart=nameofthesource.tar.bz2. I actually think using a live URL is important so that it can be automatically verified to match and can be easily updated to a new version. Zbyszek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Broken dependencies: perl-Language-Expr
perl-Language-Expr has broken dependencies in the rawhide tree: On x86_64: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: F20 Beta upgrade issues - network status gone
On Wed, 13 Nov 2013 17:58:27 -0800 Adam Williamson awill...@redhat.com wrote: On Wed, 2013-11-13 at 18:44 -0600, Michael Ekstrand wrote: I just upgraded my laptop from F19 to F20 Beta, using fedup, and encountered 2 noticeable problems with the upgrade process that I'm not sure where/how to correctly report: - Upon update, nm-applet was gone and my gnome-shell status area had no network status or control. Installing network-manager-applet brought it back. I had a working network status display prior to upgrade. Assuming you have a straightforward wired connection, this is not a bug. See the discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1005719 starting around comment #13. It's a wireless connection; before re-installing network-manager-applet, the integrated status menu didn't have anything to say about networking, so I couldn't check or make sure I was connected to the wireless. It seems like this is an issue in packaging somehow, that fedup didn't know to install network-manager-applet. Or maybe that fix was not the way it's supposed to be fixed - I just did that because I had remembered from previous versions of gnome-shell that the network controls operated by controlling nm-applet. - I don't have any Bluetooth status or display in gnome-shell now. I did previously. I do not know what I need to install or tweak to get it back, or where to report it. I'm not as sure about this one, but it's probably the same thing: no 'status' will be displayed unless there's something useful to display (like a paired device). Yep, pairing a device makes it show up. -- Michael Ekstrand — http://elehack.net/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Broken dependencies: perl-POE-Component-Server-XMLRPC
perl-POE-Component-Server-XMLRPC has broken dependencies in the rawhide tree: On x86_64: perl-POE-Component-Server-XMLRPC-0.05-17.fc20.noarch requires perl(XMLRPC::Lite) On i386: perl-POE-Component-Server-XMLRPC-0.05-17.fc20.noarch requires perl(XMLRPC::Lite) On armhfp: perl-POE-Component-Server-XMLRPC-0.05-17.fc20.noarch requires perl(XMLRPC::Lite) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: Copr
I wanted to try out the copr-cli, but unfortunately without great success. I added my API key to ~/.config/api but copr-cli create always results in an error, without an error message. Is it known that the cli does not work yet, or did I miss something to configure? Manuel On Thu, 7 Nov 2013 13:54:40 +0100 Miroslav Suchý msu...@redhat.com wrote: Dear developers and Fedora contributors, let me introduce Copr: http://copr-fe.cloud.fedoraproject.org/ Copr is a build system for third party repositories. It is intended for: * upstream teams - to make nightly and test builds * layered applications - if you build on top of Fedora, but you are not part of Fedora * packages not yet ready to be included in official Fedora repositories How it works? You provide src.rpm, we will provide resulting yum repo for RHEL 5,6 and Fedora 18, 19, 20... But see WARNING on bottom of this mail. I prepared quick tutorial for you: https://fedorahosted.org/copr/wiki/ScreenshotsTutorial and FAQ: https://fedorahosted.org/copr/wiki/UserDocs#FAQ Everybody with FAS account can build there. If you want to use command line client, you should install copr-cli from updates-testing. If you have ideas, questions, comments feel free to use one of our communication channels https://fedorahosted.org/copr/#Communications (mailing list is prefered) WARNING: Please do not rely on this service in production. This is very early release (following release early, release often). First of all, this service works in simple set-up, where resulting yum repos are *not* backed up. Yet. This is not yet officially part of Fedora infrastructure, so when Copr fails, it can take several hours to be restored. And yes, our WebUI is not perfect. It's work in progress. And since Copr can build packages already, I decided to publicly announce it, so you can experiment with it. We are working on Copr on full steam and in upcoming days you can expect: * improvements in WebUI * ability to build Software Collections there -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 Beta upgrade issues - network status gone
On Thu, 14 Nov 2013 07:41:20 -0600 Michael Ekstrand mich...@elehack.net wrote: On Wed, 13 Nov 2013 17:58:27 -0800 Adam Williamson awill...@redhat.com wrote: On Wed, 2013-11-13 at 18:44 -0600, Michael Ekstrand wrote: I just upgraded my laptop from F19 to F20 Beta, using fedup, and encountered 2 noticeable problems with the upgrade process that I'm not sure where/how to correctly report: - Upon update, nm-applet was gone and my gnome-shell status area had no network status or control. Installing network-manager-applet brought it back. I had a working network status display prior to upgrade. Assuming you have a straightforward wired connection, this is not a bug. See the discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1005719 starting around comment #13. It's a wireless connection; before re-installing network-manager-applet, the integrated status menu didn't have anything to say about networking, so I couldn't check or make sure I was connected to the wireless. It seems like this is an issue in packaging somehow, that fedup didn't know to install network-manager-applet. Or maybe that fix was not the way it's supposed to be fixed - I just did that because I had remembered from previous versions of gnome-shell that the network controls operated by controlling nm-applet. I just uninstalled network-manager-applet, restarted my session, and I do have network controls now. So it looks like things do work, although I do not know why I did not have network controls when I first logged in after the upgrade. -- Michael Ekstrand — http://elehack.net/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 Beta upgrade issues - network status gone
On Wed, 2013-11-13 at 17:58 -0800, Adam Williamson wrote: - I don't have any Bluetooth status or display in gnome-shell now. I did previously. I do not know what I need to install or tweak to get it back, or where to report it. I'm not as sure about this one, but it's probably the same thing: no 'status' will be displayed unless there's something useful to display (like a paired device). Yes, the bluetooth icon shows up on the top bar when you've paired a device. In that case you also get a bluetooth submenu in the system status. I just tried with my phone. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On Thu, Nov 14, 2013 at 05:36:34PM +0800, Mathieu Bridon wrote:
For example, if right now you have:
%dir %{python_sitelib}/mymodule
%{python_sitelib}/mymodule/*.py
%{python_sitelib}/mymodule/*.pyc
%{python_sitelib}/mymodule/*.pyo
You could replace that by:
%{python_sitelib}/mymodule
Unfortunately the Python files are placed directly in
%{python_sitelib} (not in a module subdirectory). ie: the spec file
has:
%files -n python-%{name}
%doc python/examples/*.py
%{python_sitearch}/*
%{python_sitelib}/*.py
%{python_sitelib}/*.pyc
%{python_sitelib}/*.pyo
I have no idea if this packaging is correct or not.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 Beta upgrade issues - network status gone
- I don't have any Bluetooth status or display in gnome-shell now. I did previously. I do not know what I need to install or tweak to get it back, or where to report it. I'm not as sure about this one, but it's probably the same thing: no 'status' will be displayed unless there's something useful to display (like a paired device). Yes, the bluetooth icon shows up on the top bar when you've paired a device. In that case you also get a bluetooth submenu in the system status. I just tried with my phone. Strangely I always have a bluetooth network menu even though i don't have any bluetooth networks configured but I do have a number of bluetooth devices (mouse, speakers, headset) that I use to be able to connect with a couple of clicks once paired but now every time I want to use them I have to go into the control panel which is a good dozen or more clicks. Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[389-devel] Please review: ticket 47591: entries with empty objectclass attribute can be hidden
https://fedorahosted.org/389/ticket/47591 I have two versions of a fix, one correcting the calls to PL_strncasecmp, one replacing them by PL_strcasecmp, which I think is safe in str2entry_fast. https://fedorahosted.org/389/attachment/ticket/47591/0001-Ticket-47591-v1-entries-with-empty-objectclass-attri.patch https://fedorahosted.org/389/attachment/ticket/47591/0001-Ticket-47591-v2-entries-with-empty-objectclass-attri.patch -- 389-devel mailing list 389-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
rawhide report: 20131114 changes
- New release
Size change: 9712 bytes
nwsclient-1.6.4-8.fc21
--
* Wed Nov 13 2013 Ville Skyttä ville.sky...@iki.fi - 1.6.4-8
- Install docs to %{_pkgdocdir} where available (#994010).
Size change: -909 bytes
objectweb-asm4-4.2-1.fc21
-
* Thu Nov 14 2013 gil cattaneo punto...@libero.it 4.2-1
- 4.2 (rhbz#1020136)
Size change: -350 bytes
openssl-1.0.1e-32.fc21
--
* Wed Nov 13 2013 Tomáš Mráz tm...@redhat.com 1.0.1e-32
- disable verification of certificate, CRL, and OCSP signatures
using MD5 if OPENSSL_ENABLE_MD5_VERIFY environment variable
is not set
Size change: 692 bytes
pam_shield-0.9.5-14.fc21
* Wed Nov 13 2013 Ville Skyttä ville.sky...@iki.fi - 0.9.5-14
- Install docs with special %doc (#994019).
Size change: -1005 bytes
perl-IO-Socket-SSL-1.960-1.fc21
---
* Wed Nov 13 2013 Paul Howarth p...@city-fan.org - 1.960-1
- Update to 1.960
- Only documentation enhancements:
- Clarify with text and example code, that within event loops not only
select/poll should be used, but also pending has to be called
- Better introduction into SSL; at least mention anonymous authentication as
something you don't want and should take care with the right cipher
- Make it more clear that it's better not to change the cipher list unless
you really know what you're doing
- Adopt upstream's versioning scheme
Size change: 2346 bytes
perl-SOAP-Lite-1.06-3.fc21
--
* Thu Nov 14 2013 Petr Šabata con...@redhat.com - 1.06-3
- Properly obsolete/provide SOAP-Transport-TCP
Size change: 179 bytes
perl-Sub-Install-0.927-1.fc21
-
* Wed Nov 13 2013 Robin Lee cheese...@fedoraproject.org - 0.927-1
- Update to 0.927
Size change: 1338 bytes
perl-Twiggy-0.1024-1.fc21
-
* Wed Nov 13 2013 Robin Lee cheese...@fedoraproject.org - 0.1024-1
- Update to 0.1024
Size change: -528 bytes
perl-threads-shared-1.45-1.fc21
---
* Thu Nov 14 2013 Petr Pisar ppi...@redhat.com - 1.45-1
- 1.45 bump
Size change: -536 bytes
php-5.5.6-1.fc21
* Wed Nov 13 2013 Remi Collet r...@fedoraproject.org 5.5.6-1
- update to 5.5.6
Size change: 568118 bytes
python-django-horizon-2013.2-3.fc21
---
* Wed Nov 13 2013 Matthias Runge mru...@redhat.com - 2013.2-3
- add requirement python-pbr
Size change: 93 bytes
python-nss-0.14.0-3.fc21
* Wed Nov 13 2013 Ville Skyttä ville.sky...@iki.fi - 0.14.0-3
- Install docs to %{_pkgdocdir} where available (#994060).
Size change: -922 bytes
python-pudb-2013.4-1.fc21
-
* Wed Nov 13 2013 Dhiru Kholia dh...@openwall.com - 2013.4-1
- update to pudb-2013.4
Size change: 1155 bytes
python-webassets-0.9-1.fc21
---
* Thu Nov 14 2013 Praveen Kumar kumarpraveen.nit...@gmail.com 0.9-1
- Updated to new source and added python3 support
Size change: 8345 bytes
q4wine-1.1-1.fc21
-
* Thu Nov 14 2013 Dmitrij S. Kryzhevich kr...@land.ru - 1.1-2
- Fix setup macros parameters.
* Thu Nov 14 2013 Dmitrij S. Kryzhevich kr...@land.ru - 1.1-2
- Update to 1.1 release.
Size change: -1873 bytes
rubygems-2.1.11-113.fc21
* Thu Nov 14 2013 Mamoru TASAKA mtas...@fedoraproject.org - 2.1.11-113
- Update to 2.1.11
Size change: 1565 bytes
selinux-policy-3.13.1-1.fc21
* Wed Nov 13 2013 Miroslav Grepl mgr...@redhat.com 3.13.1-1
- Update to upstream
Size change: 11357 bytes
sisu-0.1.0-1.fc21
-
* Wed Nov 13 2013 Mikolaj Izdebski mizde...@redhat.com - 1:0.1.0-1
- Update to upstream version 0.1.0
Size change: 16044 bytes
skkdic-20131114-7.T1121.fc21
* Thu Nov 14 2013 Mamoru TASAKA mtas...@fedoraproject.org - 20131114-7.T1121
- Update to the latest data
Size change: 7236 bytes
spock-0.7-0.3.groovy.1.8.fc21
-
* Thu Nov 14 2013 gil cattaneo punto...@libero.it 0.7-0.3.groovy.1.8
- use objectweb-asm3
Size change: -1038 bytes
tuned-2.3.0-2.fc21
--
* Fri Nov 08 2013 Jaroslav Škarvada jskar...@redhat.com - 2.3.0-2
- fixed race condition in the start/stop code
resolves: rhbz#1028119
- improved tuned responsiveness
resolves: rhbz#1028122
Size change: 3113 bytes
vips-7.36.3-1.fc21
--
* Wed Nov 13 2013 Benjamin Gilbert bgilb...@backtick.net - 7.36.3-1
- New release
- BuildRequire libwebp
Size change: 48969 bytes
wireshark-1.10.3-4.fc21
---
* Wed Nov 13 2013 Peter Lemenkov lemen...@gmail.com - 1.10.3-4
- Updated RTPproxy dissector
Size change: 643 bytes
xmvn-1.3.0-3.fc21
-
* Thu Nov 14 2013 Michal Srb m...@redhat.com - 1.3.0-3
- Add dep org.sonatype.sisu:sisu-guice::no_aop:
* Fri Nov 08 2013 Mikolaj Izdebski mizde...@redhat.com - 1.3.0-2
- Add wagon
[Bug 1019661] perl-Sub-Install-0.927 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1019661 Robin Lee robinlee.s...@gmail.com changed: What|Removed |Added Status|MODIFIED|CLOSED Fixed In Version||perl-Sub-Install-0.927-1.fc ||21 Resolution|--- |RAWHIDE Last Closed||2013-11-14 10:11:36 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=BLV8Fr1d1ra=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: [RFC] mesa 10.0 stack in F20
Igor Gnatenko (i.gnatenko.br...@gmail.com) said: Hey, folks! Actually 9.2.3 doesn't built on armv7 (FDO #71573) and I think more better for new release to get updated mesa stack. Probably mesa 9.2.4 will also has this bug. What do you say about this idea? It's post-beta, post-GFX-test-week. While I'd defer to the driver team, I'm not sure that a mesa rebase at this point in the schedule makes sense. Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [Fedora QA] #433: blocker proposal form forgets everything after login timeout
#433: blocker proposal form forgets everything after login timeout ---+ Reporter: kvolny| Owner: tflink Type: defect| Status: new Priority: major | Milestone: Component: Blocker bug tracker page |Version: Resolution:| Keywords: Blocked By:| Blocking: ---+ Comment (by tflink): I suspect that this is going to improve with OpenID logins, which are coming in the next version (should be deployed in the next several days). Due to the differences between OpenID and straight FAS, there really isn't so much of a timeout anymore. I'll keep this open for now, if you end up hitting it again after the new version is deployed, please update the ticket and we'll look into the possibility of a different fix. -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/433#comment:1 Fedora QA http://fedorahosted.org/fedora-qa Fedora Quality Assurance ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: What is support status of PowerVR GPUs in Fedora? (Intel D2500 and gma500_gfx)
Have you captured dmesg and lspci -v output? That could help us to identify what precise hardware components are involved. Here are all logs I captured: cpuinfo: http://pastebin.com/raw.php?i=7M7uKBA5 lspci: http://pastebin.com/raw.php?i=2JFb3EnQ dmesg: http://pastebin.com/raw.php?i=8pQ5C8wJ Xorg.0.log.gma500: http://pastebin.com/raw.php?i=7L6n7QAc These are from Linux Mint because Fedora doesn't even boot, but this is probably enough info. If you need some specific Fedora info I can send logs from Fedora 20 boot if I can grab them when live image fails... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Review Request 45: Improve asset management
--- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/45/ --- (Updated Nov. 14, 2013, 3:20 p.m.) Status -- This change has been marked as submitted. Review request for blockerbugs. Bugs: 357 https://fedorahosted.org/fedora-qa/ticket/357 Repository: blockerbugs Description --- commit d86f88d7f9da899ffef44ad617a8a831327b7d80 Author: Martin Krizek mkri...@redhat.com Date: Mon Aug 12 16:40:16 2013 +0200 Improve asset management Fixes: #357 I have not minified two js files in milestone_stats.html template as I am not sure it's worth it, any objections? Diffs - requirements.txt 98eab5da9306a101a41dd13708df1900e9fd1018 blockerbugs/templates/layout.html 49cdbd70ef8347965dfca93971449688f9cd6cb0 blockerbugs/__init__.py b9d7a40e4e9b47624795958212025428e7788b0f blockerbugs.spec cda6d4e4c56cce5b3ab37665b4f1988fc62f29ce Diff: http://reviewboard-tflink.rhcloud.com/r/45/diff/ Testing --- Loaded pages, seems like css and js work as expected after being minified. Thanks, Martin Krizek ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: [Fedora QA] #357: Improve asset management
#357: Improve asset management ---+--- Reporter: tflink| Owner: mkrizek Type: enhancement | Status: closed Priority: minor | Milestone: Fedora 20 Component: Blocker bug tracker page |Version: Resolution: fixed | Keywords: Blocked By:| Blocking: ---+--- Changes (by mkrizek): * resolution: = fixed * status: new = closed * milestone: Undetermined Future = Fedora 20 Comment: Replying to [comment:5 dcallagh]: uglifyjs is a good alternative for JS minification. In Beaker we're using uglifyjs and ycssmin (with webassets), that setup works well. Thanks for the suggestion! Fixed in [https://git.fedorahosted.org/cgit/blockerbugs.git/commit/?h=developid=4c8905932d1511e88febb8e0faa2af1d4d20db17 4c8905932d1511e88febb8e0faa2af1d4d20db17] and [https://git.fedorahosted.org/cgit/blockerbugs.git/commit/?h=developid=dd6baff75945a69d77be7ef690c5ab97f5da5757 dd6baff75945a69d77be7ef690c5ab97f5da5757] -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/357#comment:6 Fedora QA http://fedorahosted.org/fedora-qa Fedora Quality Assurance ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: What is support status of PowerVR GPUs in Fedora? (Intel D2500 and gma500_gfx)
On 14 November 2013 16:19, valent.turko...@gmail.com valent.turko...@gmail.com wrote: Here are all logs I captured: cpuinfo: http://pastebin.com/raw.php?i=7M7uKBA5 lspci: http://pastebin.com/raw.php?i=2JFb3EnQ dmesg: http://pastebin.com/raw.php?i=8pQ5C8wJ Xorg.0.log.gma500: http://pastebin.com/raw.php?i=7L6n7QAc Intel PowerVR poulsbo devices do not have a free driver; their functionality is really limited and there's no DDX driver. They're totalling different than normal Intel chips driven by the intel driver; you have to use VESA for it in X. Regards, --Simone -- You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson). http://xkcd.com/229/ http://negativo17.org/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On Thu, 2013-11-14 at 08:56 +, Richard W.M. Jones wrote:
I had a bug filed that a Python package I'm maintaining cannot be
rebuilt using 'rpmbuild --rebuild'. The failure was that the *.pyc
and *.pyo files are missing.
After a lot of head-scratching and debugging it turns out that
brp-python-bytecompile was not running, and that happens because the
RPM macro %{__os_install_post} didn't contain a call to
brp-python-bytecompile. This macro exists in base RPM, but is
overridden/extended when redhat-rpm-config is installed.
Installing redhat-rpm-config fixes the problem for the bug reporter.
However this raises some questions:
- Should this package explicitly BR redhat-rpm-config?
No.
- Should all Python packages explicitly BuildRequire redhat-rpm-config?
No.
- Should this package not be packaging up the *.py[co] files?
No.
- Is this a bug in redhat-rpm-config/Python/RPM/Fedora?
Yes. People hit this _constantly_ in a lot of ways. Like why am I not
getting debuginfo packages. The theory is that you might want to build
with some other set of macros, which is why rpmbuild doesn't just
require r-r-c.
I think this is foolish, and that we should just fix rpmbuild: if you
wanted some other set of macros, start by rebuilding rpm to require
something other than r-r-c. The counter-argument is - and I find this
completely baffling - that it's easier to replace packages than rebuild
them, so that instead rpmbuild should Require: system-rpm-config and
then r-r-c happens to be what provides that by default. Which, sure,
that's also a thing we could do.
Either solution would be better than what we have.
- Should I just ignore this because it builds fine in Koji?
Yes.
- ajax
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Rawhide and branched nightly compose changes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I have just changed the starting times of the nightly branched composes. Rawhide now kicks off 3 hours earlier at 05:15 UTC. Branched now starts 2 hours earlier at 07:15 UTC. Releng is working to integrate the nightly livecd composes into the automated compose process, as well as adding nightly arm and cloud image creation. as we stabilise the compose processes we will add a separate email with a notification of the nightly image composition completion. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJShPFIAAoJEH7ltONmPFDRbxEQAKI1oFfh7BIMXLHP5xVMUb14 jJVMGRAgJkZxWa0a3BzXXg6aK7OdW7Q7JQTslYSrS64Vf85Ze9Fb4CdX6rhQX4yG oBAzuJkenVhValaG/nQ5fcP9hDBIyIdbP0eJFDx5/2MZXdzDoThuIIWvgxBgXlpX qFdBPtDDypZXjS3wiMTGa4ZnLjLnagSXmi0KLzUiWGlo4oFfi6YUsXj5lDosnj/X LpAxc5YhFpBMwpivBc6Tq+nJqTY+1ML40Nmp15EibDnFgIPn6cto2s19iv+Svf1o LbDltJfs/4VTpq/MSJqiYV56wYrVSMEb52ijbgXHJhR1SnxfnF3fBf31KkAtcIAr X+XT3TU+jO9wzRPE8Pu9NsxQerZGBqKPGAXDeGzo0cpF8zCnow13wKIeHkv0PtnC LQOlf2vDEL7f7zlA04+nxbbvRdrF2O2KNxoCP7pIEXdyKOP32ILmgcTIfY9PjmkX Ftd8oPoccefb0NG3mJ2I/EGkmGRXU4X7iJskYkV7Kcuhg1LerltPqkdIpluQThp+ s/if2V+0AYGDVWX9kB2d4NmPW0uFKrV7NTWjvxClyGjeQgsRu8yjEtFRzkEbQZ5P X3vfTWtEmvjPj5naVTa9lWHIzTCpO1fzwi1MBej5P5yrvjhMZFTmyEsZRDzmywZA GvpoK1wIbzsOPfvn2olN =L+9x -END PGP SIGNATURE- ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 Beta upgrade issues - network status gone
- Original Message - - I don't have any Bluetooth status or display in gnome-shell now. I did previously. I do not know what I need to install or tweak to get it back, or where to report it. I'm not as sure about this one, but it's probably the same thing: no 'status' will be displayed unless there's something useful to display (like a paired device). Yes, the bluetooth icon shows up on the top bar when you've paired a device. In that case you also get a bluetooth submenu in the system Not paired, but connected to the device. status. I just tried with my phone. Strangely I always have a bluetooth network menu even though i don't have any bluetooth networks configured NM configures them automatically now. So you probably paired your phone in this particular case. but I do have a number of bluetooth devices (mouse, speakers, headset) that I use to be able to connect with a couple of clicks once paired but now every time I want to use them I have to go into the control panel which is a good dozen or more clicks. Mice, speakers and headsets should all try to connect to the computer without you having to do anything. If that's not working (and I had some problems with a mouse recently), that's probably what we should be looking at rather than re-adding things to the menu. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Copr
On 11/14/2013 02:43 PM, Manuel Faux wrote: I wanted to try out the copr-cli, but unfortunately without great success. I added my API key to ~/.config/api but copr-cli create always results in an error, without an error message. Is it known that the cli does not work yet, or did I miss something to configure? You *must* use at least one --chroot option. E.g.: copr-cli create --chroot fedora-19-x86_64 --chroot fedora-rawhide-x86_64 test I fixed copr-cli to give you better suggestion instead of that ugly traceback. -- Miroslav Suchy, RHCE, RHCDS Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: What is support status of PowerVR GPUs in Fedora? (Intel D2500 and gma500_gfx)
On Thu, 2013-11-14 at 13:05 +0100, valent.turko...@gmail.com wrote: I'm really interested what is the state of gma500_gfx driver in latest kernel, is it reasonable to expect that this driver will get updated and have better support or should I just say to my friend to grab version of Windows 7 and to run with it... any suggestions? Intel's PowerVR-based graphics have _terrible_ support in Linux. They've been promising for years to either a) provide a competent free driver and/or b) stop producing pvr-based chipsets, and they have repeatedly failed at both. There is no OSS 3D driver for these chips, which is unfortunate, since 3D is the only thing these chips do even remotely well, and they're inevitably attached to underpowered CPUs where llvmpipe isn't going to help much. There's a KMS driver that vaguely works kinda sometimes, as you've found, but that just lights up the display, it doesn't provide any acceleration. I do not expect support for these chips to get materially better any time soon. Honestly at this point I don't even want to reverse engineer the things, it would essentially be rewarding Intel for bad behaviour. - ajax -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On Thu, Nov 14, 2013 at 02:18:05PM +, Richard W.M. Jones wrote:
On Thu, Nov 14, 2013 at 05:36:34PM +0800, Mathieu Bridon wrote:
For example, if right now you have:
%dir %{python_sitelib}/mymodule
%{python_sitelib}/mymodule/*.py
%{python_sitelib}/mymodule/*.pyc
%{python_sitelib}/mymodule/*.pyo
You could replace that by:
%{python_sitelib}/mymodule
Unfortunately the Python files are placed directly in
%{python_sitelib} (not in a module subdirectory). ie: the spec file
has:
%files -n python-%{name}
%doc python/examples/*.py
%{python_sitearch}/*
%{python_sitelib}/*.py
%{python_sitelib}/*.pyc
%{python_sitelib}/*.pyo
I have no idea if this packaging is correct or not.
That is a somewhat odd split (somethings in sitearch and some things in
sitelib)
If there's nothing else in python_sitelib besides this module, you can
change the glob there:
%{python_sitearch}/*
%{python_sitelib}/*
I'd have to look at the actual package to know whether that would cause
problems.
-Toshio
pgprVcRMt2Iwt.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: What is support status of PowerVR GPUs in Fedora? (Intel D2500 and gma500_gfx)
On 14/11/13 15:59, Adam Jackson wrote: On Thu, 2013-11-14 at 13:05 +0100, valent.turko...@gmail.com wrote: I'm really interested what is the state of gma500_gfx driver in latest kernel, is it reasonable to expect that this driver will get updated and have better support or should I just say to my friend to grab version of Windows 7 and to run with it... any suggestions? Intel's PowerVR-based graphics have _terrible_ support in Linux. They've been promising for years to either a) provide a competent free driver and/or b) stop producing pvr-based chipsets, and they have repeatedly failed at both. There is no OSS 3D driver for these chips, which is unfortunate, since 3D is the only thing these chips do even remotely well, and they're inevitably attached to underpowered CPUs where llvmpipe isn't going to help much. There's a KMS driver that vaguely works kinda sometimes, as you've found, but that just lights up the display, it doesn't provide any acceleration. I do not expect support for these chips to get materially better any time soon. Honestly at this point I don't even want to reverse engineer the things, it would essentially be rewarding Intel for bad behaviour. On the one hand, you're absolutely right. On the other hand, I own a Samsung NC110 netbook which has one of these PowerVR suckers in it so I deeply appreciate the excruciatingly laborious work that these folks are doing: http://powervr.gnu.org.ve/doku.php (site seems broken at the moment :( ) http://libreplanet.org/wiki/Group:PowerVR_drivers (decent summary) Andy -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 Beta upgrade issues - network status gone
but I do have a number of bluetooth devices (mouse, speakers, headset) that I use to be able to connect with a couple of clicks once paired but now every time I want to use them I have to go into the control panel which is a good dozen or more clicks. Mice, speakers and headsets should all try to connect to the computer without you having to do anything. If that's not working (and I had some problems with a mouse recently), that's probably what we should be looking at rather than re-adding things to the menu. None of them do, and I've never had any luck with that going back sometime, I've always had to manually pair. Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On Thu, 14 Nov 2013, Adam Jackson wrote: Yes. People hit this _constantly_ in a lot of ways. Like why am I not getting debuginfo packages. The theory is that you might want to build with some other set of macros, which is why rpmbuild doesn't just require r-r-c. I think this is foolish, and that we should just fix rpmbuild: if you wanted some other set of macros, start by rebuilding rpm to require something other than r-r-c. The counter-argument is - and I find this completely baffling - that it's easier to replace packages than rebuild them, so that instead rpmbuild should Require: system-rpm-config and then r-r-c happens to be what provides that by default. Which, sure, that's also a thing we could do. Either solution would be better than what we have. Agreed, and said so in the past. I had to add it as buildrequires: to libreswan. Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F20 Beta upgrade issues - network status gone
- Original Message - but I do have a number of bluetooth devices (mouse, speakers, headset) that I use to be able to connect with a couple of clicks once paired but now every time I want to use them I have to go into the control panel which is a good dozen or more clicks. Mice, speakers and headsets should all try to connect to the computer without you having to do anything. If that's not working (and I had some problems with a mouse recently), that's probably what we should be looking at rather than re-adding things to the menu. None of them do, and I've never had any luck with that going back sometime, I've always had to manually pair. Well, you pair once, that's supposed to keep. Unless you use your device for another computer, or phone, in which case you'll keep needing to do that. The good thing is that we should be reworking for GNOME 3.12 that so you don't need a separate interface from the settings panel to pair it. But that's still pretty deep inside the interface... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On 11/14/2013 05:45 PM, Adam Jackson wrote: On Thu, 2013-11-14 at 08:56 +, Richard W.M. Jones wrote: - Is this a bug in redhat-rpm-config/Python/RPM/Fedora? Yes. People hit this _constantly_ in a lot of ways. Like why am I not getting debuginfo packages. The theory is that you might want to build with some other set of macros, which is why rpmbuild doesn't just require r-r-c. I think this is foolish, and that we should just fix rpmbuild: if you wanted some other set of macros, start by rebuilding rpm to require something other than r-r-c. The counter-argument is - and I find this completely baffling - that it's easier to replace packages than rebuild them, so that instead rpmbuild should Require: system-rpm-config and then r-r-c happens to be what provides that by default. Which, sure, that's also a thing we could do. Well, technically rpmbuild does NOT require redhat-rpm-config to function, building Fedora compliant packages does. Anyway, I got tired of this argument in March, so Fedora = 20 has this: http://pkgs.fedoraproject.org/cgit/rpm.git/commit/?id=6fb2566e2d6d8b2e29e9f671bf9f157de25e9908 - Panu - -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On Thu, 2013-11-14 at 19:13 +0200, Panu Matilainen wrote: On 11/14/2013 05:45 PM, Adam Jackson wrote: On Thu, 2013-11-14 at 08:56 +, Richard W.M. Jones wrote: - Is this a bug in redhat-rpm-config/Python/RPM/Fedora? Yes. People hit this _constantly_ in a lot of ways. Like why am I not getting debuginfo packages. The theory is that you might want to build with some other set of macros, which is why rpmbuild doesn't just require r-r-c. I think this is foolish, and that we should just fix rpmbuild: if you wanted some other set of macros, start by rebuilding rpm to require something other than r-r-c. The counter-argument is - and I find this completely baffling - that it's easier to replace packages than rebuild them, so that instead rpmbuild should Require: system-rpm-config and then r-r-c happens to be what provides that by default. Which, sure, that's also a thing we could do. Well, technically rpmbuild does NOT require redhat-rpm-config to function, building Fedora compliant packages does. Anyway, I got tired of this argument in March, so Fedora = 20 has this: http://pkgs.fedoraproject.org/cgit/rpm.git/commit/?id=6fb2566e2d6d8b2e29e9f671bf9f157de25e9908 Awesome, thanks! - ajax -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Koji / Bodhi tagging spam
On Wed, Nov 13, 2013 at 11:50 PM, Kevin Fenzi ke...@scrye.com wrote: On Wed, 13 Nov 2013 18:30:28 +0100 drago01 drag...@gmail.com wrote: Hi, iw-3.11-1.fc20 successfully untagged from f20-updates-testing-pending by bodhi ... Messages like this has been annoying like forever ... why do I care about such messages? I mean as long as nothing went wrong I don't really care (any I am pretty sure many others don't either). Can we make it a bit less chatty? Or are people really have a use for such messages? It's used by autoqa. I don't know off hand if we can exclude emails from just this tag or if koji always sends email action on a package you are owner for. ;( Apperently not see Tim's mail. So any other reason for them or can we just stop sending them out? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Koji / Bodhi tagging spam
On Thu, 14 Nov 2013 19:19:00 +0100 drago01 drag...@gmail.com wrote: On Wed, Nov 13, 2013 at 11:50 PM, Kevin Fenzi ke...@scrye.com wrote: On Wed, 13 Nov 2013 18:30:28 +0100 drago01 drag...@gmail.com wrote: Hi, iw-3.11-1.fc20 successfully untagged from f20-updates-testing-pending by bodhi ... Messages like this has been annoying like forever ... why do I care about such messages? I mean as long as nothing went wrong I don't really care (any I am pretty sure many others don't either). Can we make it a bit less chatty? Or are people really have a use for such messages? It's used by autoqa. I don't know off hand if we can exclude emails from just this tag or if koji always sends email action on a package you are owner for. ;( Apperently not see Tim's mail. So any other reason for them or can we just stop sending them out? You misunderstand me. The _tag_ is used by autoqa. I don't personally know if we can disable email notifications on a per tag basis or it's global. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Koji / Bodhi tagging spam
On Thu, Nov 14, 2013 at 7:37 PM, Kevin Fenzi ke...@scrye.com wrote: On Thu, 14 Nov 2013 19:19:00 +0100 drago01 drag...@gmail.com wrote: On Wed, Nov 13, 2013 at 11:50 PM, Kevin Fenzi ke...@scrye.com wrote: On Wed, 13 Nov 2013 18:30:28 +0100 drago01 drag...@gmail.com wrote: Hi, iw-3.11-1.fc20 successfully untagged from f20-updates-testing-pending by bodhi ... Messages like this has been annoying like forever ... why do I care about such messages? I mean as long as nothing went wrong I don't really care (any I am pretty sure many others don't either). Can we make it a bit less chatty? Or are people really have a use for such messages? It's used by autoqa. I don't know off hand if we can exclude emails from just this tag or if koji always sends email action on a package you are owner for. ;( Apperently not see Tim's mail. So any other reason for them or can we just stop sending them out? You misunderstand me. The _tag_ is used by autoqa. Well my mail was about the notification mails not about the tag itself. I don't personally know if we can disable email notifications on a per tag basis or it's global. OK. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Copr
On Thu, 14 Nov 2013 16:58:30 +0100 Miroslav Suchý msu...@redhat.com wrote: On 11/14/2013 02:43 PM, Manuel Faux wrote: I wanted to try out the copr-cli, but unfortunately without great success. I added my API key to ~/.config/api but copr-cli create always results in an error, without an error message. Is it known that the cli does not work yet, or did I miss something to configure? You *must* use at least one --chroot option. E.g.: copr-cli create --chroot fedora-19-x86_64 --chroot fedora-rawhide-x86_64 test Sounds logically for me now, as also the web UI requires you to check at least on chroot. In this case the help page of copr-cli seems quite confusing to me, since all the arguments except name are in square brackets, which normally is used for optional arguments. I fixed copr-cli to give you better suggestion instead of that ugly traceback. Manuel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: What is support status of PowerVR GPUs in Fedora? (Intel D2500 and gma500_gfx)
On Nov 14, 2013 5:05 AM, valent.turko...@gmail.com valent.turko...@gmail.com wrote: Friend of mine just showed me his cheap 13 laptop running Intel D2500 and first thing he said that he had issue installing linux on it. When I asked about GPU and answer was Intel I assured him that for last 10 years I only used Intel GPU based laptops and had great experience. I tried Fedora 19 Live - failed to boot, then Linux Mint 15 - got to screen but with terrible artifacts on screen, check them out - http://youtu.be/mha7fZU1xFg, then tried latest Fedora 20 Live Beta 5 - boot starts with artefacts but fails to boot into desktop. Few hours later after reading up on this issue I managed to get laptop working with Linux Mint 15 (updated kernel to 3.11) but had to blacklist gma500_gfx driver, only then I get somewhat usable laptop (but with lower resolution and no video acceleration). I'm really interested what is the state of gma500_gfx driver in latest kernel, is it reasonable to expect that this driver will get updated and have better support or should I just say to my friend to grab version of Windows 7 and to run with it... any suggestions? -- I have a box with the same generation of Atom/PowerVR (Cedar Trail? Cedar View? No access at the moment). I can't get *any* display manager to work reliably, but I can `xinit gnome-session` with reasonable results. Once X stops, whether from killing the process or switching targets, the GPU is locked until reboot. I gave the thing to a friend to use as an HTPC, and he gave it back saying he couldn't find Windows drivers for it, and neither could I. I'm using it as a disposable rawhide playground now. If anyone really wants to hack out support for this I'd be happy to ship it to them. --Pete -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: What is support status of PowerVR GPUs in Fedora? (Intel D2500 and gma500_gfx)
On Thu, 2013-11-14 at 10:59 -0500, Adam Jackson wrote: On Thu, 2013-11-14 at 13:05 +0100, valent.turko...@gmail.com wrote: I'm really interested what is the state of gma500_gfx driver in latest kernel, is it reasonable to expect that this driver will get updated and have better support or should I just say to my friend to grab version of Windows 7 and to run with it... any suggestions? Intel's PowerVR-based graphics have _terrible_ support in Linux. They've been promising for years to either a) provide a competent free driver and/or b) stop producing pvr-based chipsets, and they have repeatedly failed at both. There is no OSS 3D driver for these chips, which is unfortunate, since 3D is the only thing these chips do even remotely well, and they're inevitably attached to underpowered CPUs where llvmpipe isn't going to help much. There's a KMS driver that vaguely works kinda sometimes, as you've found, but that just lights up the display, it doesn't provide any acceleration. I do not expect support for these chips to get materially better any time soon. Honestly at this point I don't even want to reverse engineer the things, it would essentially be rewarding Intel for bad behaviour. I would never usually suggest any of the things in this post, but if you're really stuck with Poulsbo hardware, you essentially have zero good choices, so it's just a case of which bad choice you want to make. Note that several years ago there was a proprietary driver which, while in many ways being a pile of crap, more or less worked and gave 2D, 3D and video playback acceleration. Whoever was maintaining it gave up years ago, and you have 0 chance of getting it to work on any modern distro, but you may be able to use it if you run an old LTS build of Ubuntu. Ubuntu 10.04 should be old enough for the proprietary driver to work, and still has support until mid-2015 according to https://wiki.ubuntu.com/LTS . Of course, the rest of the environment will be from the middle of 2010. You could run an equally old build of any other distribution too, of course, but few will have any support at this point, and you'll likely be able to find old guide/howto threads for running the GMA500 proprietary drivers on Ubuntu more easily than any other distro. If you want to go this route, the best thing to do is probably to start Googling or searching the Ubuntu forums (where Poulsbo-proprietary-driver-folk-wisdom tends to reside) with the magic string 'emgd'. AFAIK none of the two or three different proprietary drivers put out by different groups at Intel (yes...really) for the Poulsbo has been maintained at all since 2011 or so, and you have no effective chance of getting any of them working on distros with Xorg 1.10 or newer and/or kernel 3.0 or newer. For anything modern you're stuck with vesa or the gma500_gfx kernel driver and xorg-x11-drv-modesetting, which will be barely any better than vesa, and both of which will be extremely sluggish. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
EPEL Fedora 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 571 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5620/bugzilla-3.4.14-2.el6 86 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11274/ssmtp-2.61-21.el6 47 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11703/chicken-4.8.0.4-4.el6 28 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11865/quassel-0.9.1-1.el6 11 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12025/seamonkey-2.22-1.el6 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12064/drupal7-context-3.1-1.el6 1 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12079/bip-0.8.9-1.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12040/python-djblets-0.7.23-1.el6,ReviewBoard-1.7.18-1.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12102/moodle-2.4.7-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing ReviewBoard-1.7.18-1.el6 amiri-fonts-0.106-9.el6 engauge-digitizer-5.2-3.el6 fedmsg-0.7.2-1.el6 lcmaps-1.6.1-6.el6 lz4-r108-1.el6 moodle-2.4.7-1.el6 open-vm-tools-9.4.0-1.el6 php-bartlett-PHP-CompatInfo-2.25.0-1.el6 python-djblets-0.7.23-1.el6 simarrange-0.0-1.20131019gitd52382f.el6 skeinforge-12.03.14-16.el6 tcpcopy-0.9.6-1.el6 youtube-dl-2013.11.13-1.el6 Details about builds: ReviewBoard-1.7.18-1.el6 (FEDORA-EPEL-2013-12040) Web-based code review tool Update Information: - Fix JavaScript errors - New upstream security release 1.7.17 - http://www.reviewboard.org/docs/releasenotes/reviewboard/1.7.17/ - Resolves: CVE-2013-4519 - Security Fixes: * Fixed XSS vulnerabilities for the 'Branch' field and uploaded file captions. * Added a 'X-Frame-Options' header to prevent clickjacking. - New Features: * Remove the need for SSH keys for GitHub repositories. * Improved validation for GitHub repositories. * Added support for permissions on Local Sites. - Performance Improvements: * Reduced query counts on all pages. * Reduced query counts in the web API when returning empty lists. - Extensibility: * Extensions using the ``configure_extension`` view an now pass in a custom ``template_name`` pointing to a template for the configuration page, if it needs additional customization. * Enabling, disabling or reconfiguring extensions will now invalidate the caches for pages, ensuring that hooks will take affect. * Extension configuration now works properly on subdirectory installs. - Bug Fixes: * Fixed showing private review requests on a submitter page. * The description for submitted or discarded review requests is now shown on the diff viewer. * Discarding, reopening and then closing a review request no longer makes the review request private. * Fixed a naming conflict with older PyCrypto packages, such as the default package on CentOS 6.4. * Users with the 'can_change_status' permission no longer need the 'can_edit_reviewrequest' permission in order to close or reopen review requests. * Switching a repository from using a hosting service to Custom no longer reverts back to the hosting service. * Fixed editing a repository if its associated hosting service can't be loaded (such as if an extension providing that hosting service is disabled). * Many diff validation errors weren't being shown on the New Review Request page, generating 500 errors instead. * Fixed caching issues with the Blocks field on review requests. * Editing JSON text fields in the administration UI now works, validates, and won't result in warnings in the log. * Fixed breakages with looking up URLs internally with Local Sites. ChangeLog: * Wed Nov 13 2013 Stephen Gallagher sgall...@redhat.com - 1.7.18-1 - New upstream bugfix release 1.7.18 - http://www.reviewboard.org/docs/releasenotes/reviewboard/1.7.18/ - Convert to using UglifyJS2 for javascript minification * Wed Nov 6 2013 Stephen Gallagher sgall...@redhat.com - 1.7.17-1.1 - Drop upstreamed patch for pytz requirement * Tue Nov 5 2013 Stephen Gallagher sgall...@redhat.com - 1.7.17-1 - New upstream security release 1.7.17 - http://www.reviewboard.org/docs/releasenotes/reviewboard/1.7.17/ - Resolves: CVE-2013-4519 - Security Fixes: * Fixed XSS vulnerabilities for the 'Branch' field and uploaded file captions. * Added a 'X-Frame-Options' header to prevent clickjacking. - New Features: * Remove the need for SSH keys for GitHub repositories. * Improved validation for GitHub repositories. * Added support for permissions on Local Sites. - Performance Improvements: * Reduced query counts on all pages. * Reduced query counts in the web API when returning empty
EPEL Fedora 5 updates-testing report
The following Fedora EPEL 5 Security updates need testing: Age URL 571 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5630/bugzilla-3.2.10-5.el5 86 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11276/ssmtp-2.61-21.el5 62 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11560/fail2ban-0.8.10-4.el5 26 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11893/libguestfs-1.20.12-1.el5 12 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12004/GraphicsMagick-1.3.18-2.el5 6 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12067/drupal7-context-3.1-1.el5 1 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12091/bip-0.8.9-1.el5 The following builds have been pushed to Fedora EPEL 5 updates-testing lcmaps-1.6.1-6.el5 lz4-r108-1.el5 Details about builds: lcmaps-1.6.1-6.el5 (FEDORA-EPEL-2013-12106) Grid (X.509) and VOMS credentials to local account mapping service Update Information: Grid (X.509) and VOMS credentials to local account mapping service References: [ 1 ] Bug #736717 - Review Request: lcmaps - Grid (X.509) and VOMS credentials to local account mapping https://bugzilla.redhat.com/show_bug.cgi?id=736717 lz4-r108-1.el5 (FEDORA-EPEL-2013-12105) Extremely fast compression algorithm Update Information: lz4-r108 release. ChangeLog: * Sun Nov 10 2013 pjp p...@fedoraproject.org - r108-1 - new release r108 ___ epel-devel mailing list epel-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: What is support status of PowerVR GPUs in Fedora? (Intel D2500 and gma500_gfx)
On Thu, Nov 14, 2013 at 7:50 PM, Pete Travis li...@petetravis.com wrote: On Nov 14, 2013 5:05 AM, valent.turko...@gmail.com valent.turko...@gmail.com wrote: Friend of mine just showed me his cheap 13 laptop running Intel D2500 and first thing he said that he had issue installing linux on it. When I asked about GPU and answer was Intel I assured him that for last 10 years I only used Intel GPU based laptops and had great experience. I tried Fedora 19 Live - failed to boot, then Linux Mint 15 - got to screen but with terrible artifacts on screen, check them out - http://youtu.be/mha7fZU1xFg, then tried latest Fedora 20 Live Beta 5 - boot starts with artefacts but fails to boot into desktop. Few hours later after reading up on this issue I managed to get laptop working with Linux Mint 15 (updated kernel to 3.11) but had to blacklist gma500_gfx driver, only then I get somewhat usable laptop (but with lower resolution and no video acceleration). I'm really interested what is the state of gma500_gfx driver in latest kernel, is it reasonable to expect that this driver will get updated and have better support or should I just say to my friend to grab version of Windows 7 and to run with it... any suggestions? -- I have a box with the same generation of Atom/PowerVR (Cedar Trail? Cedar View? No access at the moment). I can't get *any* display manager to work reliably, but I can `xinit gnome-session` with reasonable results. Once X stops, whether from killing the process or switching targets, the GPU is locked until reboot. I gave the thing to a friend to use as an HTPC, and he gave it back saying he couldn't find Windows drivers for it, and neither could I. I'm using it as a disposable rawhide playground now. If anyone really wants to hack out support for this I'd be happy to ship it to them. Just sell it on ebay or something and buy something sane instead. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Planned Outage: Server Maintenance - 2013-11-20 22:00 UTC
Planned Outage: Server Maintenance - 2013-11-20 22:00 UTC There will be an outage starting at 2013-11-20 22:00 UTC, which will last approximately 3 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2013-11-20 22:00 UTC' Reason for outage: We will be updating servers and rebooting them. In addition we will be resizing a primary database server to increase it's storage. During the outage window specific services may be up or down as systems that affect them are rebooted. Affected Services: Ask Fedora - http://ask.fedoraproject.org/ Badges - https://badges.fedoraproject.org/ BFO - http://boot.fedoraproject.org/ Blockerbugs - https://qa.fedoraproject.org/blockerbugs/ Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ GIT / Source Control - pkgs.fedoraproject.org Darkserver - https://darkserver.fedoraproject.org/ DNS - ns-sb01.fedoraproject.org, ns02.fedoraproject.org, ns04.fedoraproject.org, ns05.fedoraproject.org Docs - http://docs.fedoraproject.org/ Elections - https://admin.fedoraproject.org/voting Email system Fedmsg busmon - http://apps.fedoraproject.org/busmon Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Calendar - https://apps.fedoraproject.org/calendar/ Fedora Hosted - https://fedorahosted.org/ Fedora OpenID - https://id.fedoraproject.org/ Fedora People - http://fedorapeople.org/ Main Website - http://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ QA Services Secondary Architectures Spins - http://spins.fedoraproject.org/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Wiki - http://fedoraproject.org/wiki/ Contact Information: Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/4120 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. signature.asc Description: PGP signature ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On 11/14/2013 03:56 AM, Richard W.M. Jones wrote:
I had a bug filed that a Python package I'm maintaining cannot be
rebuilt using 'rpmbuild --rebuild'. The failure was that the *.pyc
and *.pyo files are missing.
After a lot of head-scratching and debugging it turns out that
brp-python-bytecompile was not running, and that happens because the
RPM macro %{__os_install_post} didn't contain a call to
brp-python-bytecompile. This macro exists in base RPM, but is
overridden/extended when redhat-rpm-config is installed.
Installing redhat-rpm-config fixes the problem for the bug reporter
I noticed some odd things about the whole brp-python* setup : for
instance, there are two very similar versions of brp-python-hardlink:
one from rpm-build-4.11.1-3.fc19.x86_64 and another from
redhat-rpm-config-9.1.0-46.1.fc19.noarch ; they seem to be doing the
same thing, the only difference is
pyo=${pyc%c}o
---
pyo=$(echo $pyc | sed -e 's/.pyc$/.pyo/')
No big deal but it looks like someone who knows this area should review
and/or clean it up.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Test-Announce] Fedora 20 Final Test Compose 1 (TC1) Available Now!
NOTE: The 64-bit LXDE Live is over its size limit. As per the Fedora 20 schedule [1], Fedora 20 Final Test Compose 1 (TC1) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/5808 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace dl with download-ib01 in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha, Beta, and Final priority test cases for Installation [2], Base [3], and Desktop [4] should pass in order to meet the Final Release Criteria [5]. Help is available on #fedora-qa on irc.freenode.net [6], or on the test list [7]. Create Fedora 20 Final test compose (TC) and release candidate (RC) https://fedorahosted.org/rel-eng/ticket/5808 Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-20/f-20-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Base_validation_testing [4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [5] https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria [6] irc://irc.freenode.net/fedora-qa [7] https://admin.fedoraproject.org/mailman/listinfo/test signature.asc Description: OpenPGP digital signature ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fedora 20 TC1 AMIs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, Final TC1 images have been uploaded to EC2 and are available at ami-fb81a492 : us-east-1 image for i386 ami-6581a40c : us-east-1 image for x86_64 additionally if your looking to the AMI's they have been added to files in the release tree http://dl.fedoraproject.org/pub/alt/stage/20-TC1/Images/i386/Fedora-Images-i386-20-TC1-AMI http://dl.fedoraproject.org/pub/alt/stage/20-TC1/Images/x86_64/Fedora-Images-x86_64-20-TC1-AMI when we get to final Beta and the images are uploaded to all regions they will all be listed and the file will be gpg signed in the final tree Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJShWgdAAoJEH7ltONmPFDRx3IQAIKu/ICtzU20Wt798WaU8wVV OJ+4RXlWl1QS0pi8DHVG0oYrmxyFmQ/+cEExtmL9rq4cPGyPFIF9nHr7fdWjTe6L Ki9uUpS4o2py9sGxDzWZ7nqotdUhuzPUApQCqG+3qkRxIlKNJY6l/oNjrdQYe8L8 aNdKuFXq60DToVK9sO8ALDwFbx2UbRwCOzftHrLd8F2FlqkSVTmt+Tdq72lXYghD rBl/NL51ZfNn2lSN37LrragkNv2KCw9BFuooGnsEjRTxz1KrP5JEYJl+J6AEHAyF 64QE98jssIxJljedh9SnIW8ql6wYRBjs8MX0LDSj1mLtZLVyJU2tPIu1wCLzAq3U axUMIyiuLfsPccJcNCuKg8iom+KF1OzWRR//6uNiMzFccXWYP5zgHHuASHsDupDN eWBSLJadan+00Y7aRvuGrDYdqqj4Mr0ViPx6hFOYwe5Z6htTvVZXkvCnLZHsqzdR njmqwnV0kvQ2Pn/DZU4jQyjW3nDdVTddJauuls6f0sZOKlQICWw7XxN8O+B6mC8K ed1mIAAXa3qZdGWilcqe1ZUtL9Lvegf6sPK+5+8DceorCj8BJh4lTHkQFJPLog7/ hoHXtFSG4Slz8PNtT+i3GlmObo+6HXviC//67NZkQ2cvBYy1Kp9aHouJw//Lz82p 6lsFC3615ewhWpdQ54CF =357Q -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On Thu, 2013-11-14 at 08:12 -0800, Toshio Kuratomi wrote:
If there's nothing else in python_sitelib besides this module, you can
change the glob there:
%{python_sitearch}/*
%{python_sitelib}/*
Or:
%{python_sitearch}/*.py*
%{python_sitelib}/*.py*
Just to be sure not to include undesired stuff.
--
Mathieu
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On 11/14/2013 06:13 PM, Panu Matilainen wrote: On 11/14/2013 05:45 PM, Adam Jackson wrote: On Thu, 2013-11-14 at 08:56 +, Richard W.M. Jones wrote: - Is this a bug in redhat-rpm-config/Python/RPM/Fedora? Yes. People hit this _constantly_ in a lot of ways. Like why am I not getting debuginfo packages. The theory is that you might want to build with some other set of macros, which is why rpmbuild doesn't just require r-r-c. I think this is foolish, and that we should just fix rpmbuild: if you wanted some other set of macros, start by rebuilding rpm to require something other than r-r-c. The counter-argument is - and I find this completely baffling - that it's easier to replace packages than rebuild them, so that instead rpmbuild should Require: system-rpm-config and then r-r-c happens to be what provides that by default. Which, sure, that's also a thing we could do. Well, technically rpmbuild does NOT require redhat-rpm-config to function, building Fedora compliant packages does. Anyway, I got tired of this argument in March, so Fedora = 20 has this: http://pkgs.fedoraproject.org/cgit/rpm.git/commit/?id=6fb2566e2d6d8b2e29e9f671bf9f157de25e9908 I haven't tried, but in my understanding, this change renders it impossible to use Fedora's rpm to build non-Fedora rpms Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Koji / Bodhi tagging spam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 El Wed, 13 Nov 2013 15:50:27 -0700 Kevin Fenzi ke...@scrye.com escribió: On Wed, 13 Nov 2013 18:30:28 +0100 drago01 drag...@gmail.com wrote: Hi, iw-3.11-1.fc20 successfully untagged from f20-updates-testing-pending by bodhi ... Messages like this has been annoying like forever ... why do I care about such messages? I mean as long as nothing went wrong I don't really care (any I am pretty sure many others don't either). Can we make it a bit less chatty? Or are people really have a use for such messages? Not without disabling kojis inbuilt notification service and writing one that works based on fedmsg It's used by autoqa. I don't know off hand if we can exclude emails from just this tag or if koji always sends email action on a package you are owner for. ;( Emails are sent when a package you own of built is tagged. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJShZfIAAoJEH7ltONmPFDRAvoP/3Dql6vwaj1hMqoP0AhXxr3Y kl47YdZ2UTZ8Untyh+NlDQiGiVxQHFesm+hzuHYnFivbjCp7ZvQSDMyd5MiCNI2P YC+3JUWKelTjFIpz9khgND5d0gVh13kzGxA1t8bLsWU1Mii/fnWipCakjKKhepzM Fsk6s0M4cRXQUaaIsP39ABfgkyKIMSgsrktiPYa9w9zyozZTo7uWxpvQ4H+Wr+Z3 B7R26bOIXEHwR2+ZG2MxwvWWatrtHuIBzn75RACOzAEEjxwKpbujw3IL63VIDv/r 1vKrYMNir7jWZEo7VUwVHwtjtRW+w+NPbcb3ZhyLuKdiCqW6iO0jsBI40NrppzA0 7byTINJRUZ3o93ZBRYtDf15OjikxdI0Xi+NYAPAhYWtOf284dCl9qafthBJHH5eJ KMACnfMzgaWSGcgeMxaumVxR8KaTBV36LINF076P0Tw/+u0QA8HDE/whXwS3+lQw pQhnLPsRCpp3T43l6GcrezRW3fpWjea7KvILYJGvCWQGVcYYjzlJepvch3S8ocLG VRPukLSXUr7DjGqR+UyEwcQp2/SYmqHSudnBdE95flccK3bnbGVYUlFS4ZCN9Z5V /bRAo6Zm/Erl27ebmBBvUVQ9EPdZbZy013/TuXPuoZsOVTj5Xm9RCgy9NWTMgNbP jcyYTz542o7qvfHz3hvK =Ztpi -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BuildRequires: redhat-rpm-config
On 11/15/2013 05:25 AM, Ralf Corsepius wrote: On 11/14/2013 06:13 PM, Panu Matilainen wrote: On 11/14/2013 05:45 PM, Adam Jackson wrote: On Thu, 2013-11-14 at 08:56 +, Richard W.M. Jones wrote: - Is this a bug in redhat-rpm-config/Python/RPM/Fedora? Yes. People hit this _constantly_ in a lot of ways. Like why am I not getting debuginfo packages. The theory is that you might want to build with some other set of macros, which is why rpmbuild doesn't just require r-r-c. I think this is foolish, and that we should just fix rpmbuild: if you wanted some other set of macros, start by rebuilding rpm to require something other than r-r-c. The counter-argument is - and I find this completely baffling - that it's easier to replace packages than rebuild them, so that instead rpmbuild should Require: system-rpm-config and then r-r-c happens to be what provides that by default. Which, sure, that's also a thing we could do. Well, technically rpmbuild does NOT require redhat-rpm-config to function, building Fedora compliant packages does. Anyway, I got tired of this argument in March, so Fedora = 20 has this: http://pkgs.fedoraproject.org/cgit/rpm.git/commit/?id=6fb2566e2d6d8b2e29e9f671bf9f157de25e9908 I haven't tried, but in my understanding, this change renders it impossible to use Fedora's rpm to build non-Fedora rpms Not impossible, just a bit harder. Which is the other reason I resisted the change for quite some time. You now need to replace redhat-rpm-config with some other package providing system-rpm-config to get around this. - Panu - -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Broken dependencies: perl-Language-Expr
perl-Language-Expr has broken dependencies in the F-20 tree: On x86_64: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On i386: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) On armhfp: perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) Please resolve this as soon as possible. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File MIME-tools-5.505.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-MIME-tools: 7706e1f592d3f57981a7f7baaf9277a0 MIME-tools-5.505.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-MIME-tools] Update to 5.505
commit 14caaf8d04dc7d44b0149e3e85669f4663514637
Author: Paul Howarth p...@city-fan.org
Date: Thu Nov 14 20:40:22 2013 +
Update to 5.505
- New upstream release 5.505
- Fix documentation typos (CPAN RT#80473, CPAN RT#87783)
- Fix broken test (CPAN RT#84668)
- Don't run Kwalitee tests unless author or release tests are enabled
(CPAN RT#87094)
- Fix bug in header parsing that would fail to parse a header like:
Content-Type: ; name=malware.zip
perl-MIME-tools.spec | 13 +++--
sources |2 +-
2 files changed, 12 insertions(+), 3 deletions(-)
---
diff --git a/perl-MIME-tools.spec b/perl-MIME-tools.spec
index 6bb0416..d88a628 100644
--- a/perl-MIME-tools.spec
+++ b/perl-MIME-tools.spec
@@ -1,7 +1,7 @@
Summary: Modules for parsing and creating MIME entities in Perl
Name: perl-MIME-tools
-Version: 5.504
-Release: 4%{?dist}
+Version: 5.505
+Release: 1%{?dist}
Group: Development/Libraries
License: GPL+ or Artistic
URL: http://search.cpan.org/dist/MIME-tools/
@@ -116,6 +116,15 @@ rm -rf %{buildroot}
%{_mandir}/man3/MIME::Words.3pm*
%changelog
+* Thu Nov 14 2013 Paul Howarth p...@city-fan.org - 5.505-1
+- Update to 5.505
+ - Fix documentation typos (CPAN RT#80473, CPAN RT#87783)
+ - Fix broken test (CPAN RT#84668)
+ - Don't run Kwalitee tests unless author or release tests are enabled
+(CPAN RT#87094)
+ - Fix bug in header parsing that would fail to parse a header like:
+Content-Type: ; name=malware.zip
+
* Fri Jul 26 2013 Petr Pisar ppi...@redhat.com - 5.504-4
- Perl 5.18 rebuild
diff --git a/sources b/sources
index 9658553..cf4ed54 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-8e055aab88552710377b4727b23bfb70 MIME-tools-5.504.tar.gz
+7706e1f592d3f57981a7f7baaf9277a0 MIME-tools-5.505.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-MIME-tools/f20] Update to 5.505
Summary of changes: 14caaf8... Update to 5.505 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-MIME-tools] Created tag perl-MIME-tools-5.505-1.fc21
The lightweight tag 'perl-MIME-tools-5.505-1.fc21' was created pointing to: 14caaf8... Update to 5.505 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-MIME-tools] Created tag perl-MIME-tools-5.505-1.fc20
The lightweight tag 'perl-MIME-tools-5.505-1.fc20' was created pointing to: 14caaf8... Update to 5.505 -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-ElasticSearch] Deprecated in favour of the new official perl-Elasticsearch
commit b48d9367b657fd186f240706ae83a9520ac81153 Author: Emmanuel Seyman emman...@seyman.fr Date: Thu Nov 14 22:50:23 2013 +0100 Deprecated in favour of the new official perl-Elasticsearch .gitignore |3 - dead.package|1 + perl-ElasticSearch.spec | 113 --- sources |1 - 4 files changed, 1 insertions(+), 117 deletions(-) --- diff --git a/dead.package b/dead.package new file mode 100644 index 000..1fdc7cb --- /dev/null +++ b/dead.package @@ -0,0 +1 @@ +Deprecated in favour of the new official perl-Elasticsearch -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-ElasticSearch ownership changed
Package perl-ElasticSearch in Fedora devel was orphaned by eseyman To make changes to this package see: https://admin.fedoraproject.org/pkgdb/acls/name/perl-ElasticSearch -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[pkgdb] perl-ElasticSearch (un)retirement
Package perl-ElasticSearch in Fedora devel has been retired by eseyman To make changes to this package see: https://admin.fedoraproject.org/pkgdb/acls/name/perl-ElasticSearch -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File XMLRPC-Lite-0.717.tar.gz uploaded to lookaside cache by psabata
A file has been added to the lookaside cache for perl-XMLRPC-Lite: 7ae6b541139696fcf8f758d713af9ecd XMLRPC-Lite-0.717.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: [389-devel] Please review ticket 47590: add/split functions around replication
Hi Thierry, my consideration follows (a github-like platform with inline comments would be really welcome)! = method naming and placement = 1- I would use the following convention: if a method setup a functionality adding various entries to the tree, I would name it setup and hopefully should be placed DSAdminTools. 2- methods like _createDefaultReplMgr are not expected to be used in production, so should be placed in the DSAdminTools section 3- the brooker naming convention is based on the function-first so that python interactive users can tab and autocomplete it. initAgreement should be renamed to something like agreement_init or something else. For the return codes, simply use exceptions. = exception handling None return = 1- in case of errors, a method should raise a proper exception and eventually log the error 2- so the assert clauses should be replaced by exception because they mean that something went wrong and an action should be taken 3- about the bindmethod stuff: see http://pastebin.com/w0WnVQuJ There are some other points but the best way to set them is with patches. Let me know + Peace, R. On Wednesday 13 November 2013 17:06:25 thierry bordaz wrote: In order to implement the first CI test with replication instances, I reorganised lib389 functions related to replication setup. https://fedorahosted.org/389/attachment/ticket/47590/0001-Ticket-47590-CI-te sts-add-split-functions-around-rep.patch -- Roberto Polli Community Manager Babel S.r.l. - http://www.babel.it T: +39.06.9826.9651 M: +39.340.652.2736 F: +39.06.9826.9680 P.zza S.Benedetto da Norcia, 33 - 00040 Pomezia (Roma) CONFIDENZIALE: Questo messaggio ed i suoi allegati sono di carattere confidenziale per i destinatari in indirizzo. E' vietato l'inoltro non autorizzato a destinatari diversi da quelli indicati nel messaggio originale. Se ricevuto per errore, l'uso del contenuto e' proibito; si prega di comunicarlo al mittente e cancellarlo immediatamente. -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: [389-devel] Please review: ticket 47591: entries with empty objectclass attribute can be hidden
after discussion with Rich, a new version 1.1 https://fedorahosted.org/389/attachment/ticket/47591/0001-Ticket-47591-v1.1-entries-with-empty-objectclass-att.patch On 11/14/2013 03:49 PM, Ludwig Krispenz wrote: https://fedorahosted.org/389/ticket/47591 I have two versions of a fix, one correcting the calls to PL_strncasecmp, one replacing them by PL_strcasecmp, which I think is safe in str2entry_fast. https://fedorahosted.org/389/attachment/ticket/47591/0001-Ticket-47591-v1-entries-with-empty-objectclass-attri.patch https://fedorahosted.org/389/attachment/ticket/47591/0001-Ticket-47591-v2-entries-with-empty-objectclass-attri.patch -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Re: [389-devel] Please review ticket 47590: add/split functions around replication
On 11/14/2013 12:05 PM, Roberto Polli wrote: Hi Thierry, my consideration follows (a github-like platform with inline comments would be really welcome)! = method naming and placement = 1- I would use the following convention: if a method setup a functionality adding various entries to the tree, I would name it setup and hopefully should be placed DSAdminTools. Hi Roberto, Sorry for this late feedback. I agree that 'setup' is commonly used to prepare/initialize a functionality. Now I would prefer verbs of action/unaction like create/delete, enable/disable, set/get/list. With 'setup' verb we may create entries, enable functionality, set properties. If we have a function setupAgreement (that creates the RA and enables it by default) what is the name for the function that delete the agreement 'deleteAgreement' ? So far DSAdmintools mainly contains offline functions (like start/stop instance). I agree we can put setup functions in it. But I wonder if it would be interesting to keep all offline functions in a separated file. 2- methods like _createDefaultReplMgr are not expected to be used in production, so should be placed in the DSAdminTools section I am not sure. If someone wants to rapidly deploy a replication topology, he would be interested to have a default replication manager. In that case we may offer 'createDefaultReplMgr' (without heading '_'). In your opinion what kind of functions would go into DSAdminTools ? all 'setupxxx' functions ? 3- the brooker naming convention is based on the function-first so that python interactive users can tab and autocomplete it. initAgreement should be renamed to something like agreement_init or something else. For the return codes, simply use exceptions. ok. So do you prefer names like 'replica_create', 'suffix_create', 'agreement_create', rather than 'createReplica', 'createSuffix', 'createAgreement' ? Ok I will change the name. = exception handling None return = 1- in case of errors, a method should raise a proper exception and eventually log the error 2- so the assert clauses should be replaced by exception because they mean that something went wrong and an action should be taken 3- about the bindmethod stuff: see http://pastebin.com/w0WnVQuJ Absolutely, I will change the error handling. In addition, exception makes most of the time the code easier to read. Thanks I will resend a review according to you suggestions. regards thierry There are some other points but the best way to set them is with patches. Let me know + Peace, R. On Wednesday 13 November 2013 17:06:25 thierry bordaz wrote: In order to implement the first CI test with replication instances, I reorganised lib389 functions related to replication setup. https://fedorahosted.org/389/attachment/ticket/47590/0001-Ticket-47590-CI-te sts-add-split-functions-around-rep.patch -- 389-devel mailing list 389-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-devel
Rawhide and branched nightly compose changes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I have just changed the starting times of the nightly branched composes. Rawhide now kicks off 3 hours earlier at 05:15 UTC. Branched now starts 2 hours earlier at 07:15 UTC. Releng is working to integrate the nightly livecd composes into the automated compose process, as well as adding nightly arm and cloud image creation. as we stabilise the compose processes we will add a separate email with a notification of the nightly image composition completion. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJShPFIAAoJEH7ltONmPFDRbxEQAKI1oFfh7BIMXLHP5xVMUb14 jJVMGRAgJkZxWa0a3BzXXg6aK7OdW7Q7JQTslYSrS64Vf85Ze9Fb4CdX6rhQX4yG oBAzuJkenVhValaG/nQ5fcP9hDBIyIdbP0eJFDx5/2MZXdzDoThuIIWvgxBgXlpX qFdBPtDDypZXjS3wiMTGa4ZnLjLnagSXmi0KLzUiWGlo4oFfi6YUsXj5lDosnj/X LpAxc5YhFpBMwpivBc6Tq+nJqTY+1ML40Nmp15EibDnFgIPn6cto2s19iv+Svf1o LbDltJfs/4VTpq/MSJqiYV56wYrVSMEb52ijbgXHJhR1SnxfnF3fBf31KkAtcIAr X+XT3TU+jO9wzRPE8Pu9NsxQerZGBqKPGAXDeGzo0cpF8zCnow13wKIeHkv0PtnC LQOlf2vDEL7f7zlA04+nxbbvRdrF2O2KNxoCP7pIEXdyKOP32ILmgcTIfY9PjmkX Ftd8oPoccefb0NG3mJ2I/EGkmGRXU4X7iJskYkV7Kcuhg1LerltPqkdIpluQThp+ s/if2V+0AYGDVWX9kB2d4NmPW0uFKrV7NTWjvxClyGjeQgsRu8yjEtFRzkEbQZ5P X3vfTWtEmvjPj5naVTa9lWHIzTCpO1fzwi1MBej5P5yrvjhMZFTmyEsZRDzmywZA GvpoK1wIbzsOPfvn2olN =L+9x -END PGP SIGNATURE- ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
