Re: Who uses abi-compliance-checker?
Le mercredi 03 juillet 2013 15:03:53 Richard Shaw a écrit : I initially got abi-compliance-checker into Fedora because one of my packages does not maintain any sort of API/ABI compatibility or even versioning for that matter. That way I could always check a new release to see if any of its dependencies needed to be rebuilt. Since then, I've started using it for all of my libraries in the spirit of Trust but verify, and I've occasionally found issues even though upstream didn't bump the soversion. So out of curiosity, anyone else using this great tool? As the upstream release manager of the CGAL libraries (http://www.cgal.org/), I have started to use it for one year, to check before I publish a beta release. -- Laurent Rineau http://fedoraproject.org/wiki/LaurentRineau -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Compile-time shared library name mismatching base name (SDL)
Petr Pisar ppi...@redhat.com writes: Is the installed libSDL.so symlink a mistage in the SDL-devel package? Is renaming libSDL.so to libSDL-1.2.so wise? The libSDL.so is used in upstream and other distributions. I'm speculating here, but renaming the actual DSO like this would make it possible to install two runtime SDL versions side by side (say, 1.2 and 2.0). However, it's safe to assume that you'll only ever need one SDL-devel, so it's fine to just name the symlink libSDL.so--which allows you to use -lSDL on compiler command line (instead of having to spell out -lSDL-1.2). No idea why it confuses ldconfig like this though. Thanks, PM -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Who uses abi-compliance-checker?
Richard Shaw hobbes1...@gmail.com writes: I initially got abi-compliance-checker into Fedora because one of my packages does not maintain any sort of API/ABI compatibility or even versioning for that matter. That way I could always check a new release to see if any of its dependencies needed to be rebuilt. It would be nice to use this to decide that we don't need to rebuild clients across Boost upgrades. The trouble is that for this, more than static Dwarf inspection is needed. We also need an analysis of all templates that haven't been instantiated, in case another library used them in API. This seems to call for a solution based on a GCC plugin or something similar, where you really get to see and dump the source. Thanks, PM -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: More unhelpful update descriptions
On Tue, Jul 02, 2013 at 09:39:47PM -0700, Adam Williamson wrote: most updates get submitted with the default +3 auto-push, even though it's perhaps not appropriate for all updates. So can we please get a sane default value then that is good for most updates and can be adjusted for special cases (and later per-package)? Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 19 Gnome Desktop Touchscreen Usability
I can operate the full gnome desktop with a mouse, the touchpad, and a digitizer pen. I can operate all applications with fingers. However, I cannot operate the gnome shell using fingers. When I tap on for example Activities, the battery icon or a close button in a window title bar, that item gets highlighted, but nothing else happens. On Fedora 18, I could operate the shell with fingers too. I cannot see any difference in the generated ButtonPress and ButtonRelease events (using xev) with the mouse or the finger. The only difference is that finger motion cannot be tracked without button press, i.e. the MotionNotify events are missing from the finger. What is happening here? How can I get the shell to accept finger input too? Tom -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Circular dependencies in texlive?
Hi, I tried to build texlive-2013-0.1.20130608_r30832.fc19.src.rpm for EPEL, the build failed with the following error: error: Failed build dependencies: harfbuzz-devel is needed by texlive-3:2013-0.1.20130608_r30832.el6.x86_64 graphite2-devel is needed by texlive-3:2013-0.1.20130608_r30832.el6.x86_64 So, I tried to build graphite2-1.2.2-2.fc19.src.rpm, the build failed with the following error: error: Failed build dependencies: texlive-helvetic is needed by graphite2-1.2.2-2.el6.x86_64 texlive-sectsty is needed by graphite2-1.2.2-2.el6.x86_64 texlive-tocloft is needed by graphite2-1.2.2-2.el6.x86_64 texlive-xtab is needed by graphite2-1.2.2-2.el6.x86_64 texlive-multirow is needed by graphite2-1.2.2-2.el6.x86_64 All these dependencies are built in texlive-2013. So, building texlive-2013 requires graphite2-devel, and building graphite2-devel requires texlive2013. How can I do? Does somebody succeed to open texlive.spec? When trying to browse this file, kwrite suddenly stops. Regards, Alain -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: vote for systemd: Nay.
FC18 template is a very standard one (a 939 MBytes tgz file) which (and this is a key factor) was proved to be fully working as is in an openvz container (kernel 2.6.32-042stab076.8). as is means that Template was never taylored to be on openvz container (template is used out of the box in openvz container) and could be used to seed a working HOST too. So, as you mentioned earlier you used this recipe to set up your image: https://gist.github.com/fabaff/5512671 How Many time need I specify I didn't use that solution (it was a bad solution), I sent you this reference to tell you some other must certainly have a problem too and find (which I think is) a none satisfactory solution... Here are exact wording I used in my personal email to you about my trouble 25/06/2013 Via google, I was able to find a way to have fc18 working under LXC. The proposed way was to eviscerate many services unit from systemd (ln -s /dev/null /etc/systemd/system/udev-settle.service, etc..), see https://gist.github.com/fabaff/5512671. Applying such dramatique measure make fc18 container indeed working, but such solution are not good for both systemd and LXC and prove I am not the only one not able to figure out systemd setup needs. Its seems at least we agree it was not a good solution. I want to keep the release as pristine as possible within a container (my kind is an IaaS, see yesterday James Bottomley email about different meaning for the word 'container') Being able to migrate OS images between VMs, bare metal, containers, in all directions without alteration is absolutely a worthy goal, and not far off, if people actually start caring. I fully agree. Problem is not here. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- A bientôt === Jean-Marc PigeonE-Mail: j...@safe.ca SAFE Inc. Phone: (514) 493-4280 Clement, 'a kiss solution' to get rid of SPAM (at last) Clement' Home base http://www.clement.safe.ca; === smime.p7s Description: S/MIME Cryptographic Signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: vote for systemd: Nay (now working but still Voting Nay)
Quoting Lennart Poettering mzerq...@0pointer.de: On Tue, 02.07.13 16:57, Jean-Marc Pigeon (j...@safe.ca) wrote: As expected the problem stand on a very small detail (within /etc/fstab) Note that in a systemd world fstab shouldn't really list any of the virtual file systems like procfs, sysfs, devpts, /dev/shm, unless you have specific mount options that need to override the defaults. Also, the root file system doesn't need to be listed. It is hence a good idea to leave fstab out entirely if you run things in a container. I beg to disagree, As I want to keep the container as close as to a pristine installed distribution and as /etc/fstab is part of it once installed, fstab must be present in the container. The fact that the line just below says, Please see journal but journal is not available (empty) just compound the effect. How did you access the journal? The journal is actually available pretty much all the time. It logs to /run as long as /var is not there, to make this work (very much unlike classic syslog, btw). Just reporting observation. there is condition where you have Please see journal but journal is empty. So, no, sorry, systemd doesn't grade production level (not yet? or never?). Well, as mentioned you altered the most low-level parts of the unit dep tree. So yeah, a setup like that certainly is not production level, but that's hardly our fault. This issue already covered in previous email, May I propose some way to improve it. - journal should be accessible regardless of systemd status or trouble. It is. journalctl directly accesses all journal files and starts very early in the boot process, including in initrd (hint: this is *much* earlier than classic syslog). And for the time even before the journal is around, we log to kmsg (i.e. demsg). - You should have a way to proceed in a 'step by step' boot mode (avoiding in parallel fast scrolling report) systemd.confirm_spawn=yes Didn't notice this. not sure is what I think we need. need to check. But disabling the parallelization doesn't really work. If a service foo triggers starting of a service bar while it is starting up, and needs an answer from bar before it can proceed, how do you want to ever solve this? You need to start both foo and bar at the same time. You need a step by step to sort out problem, instead to flush all data on the console, this give time to sysadmin to see what is happening (very good when problem is ocuuring very early in the process) In step by step I would LOCK in such situation as bar need foo AND foo need bar, seems to me a deadly embrace situation definition, and prone to timing issue subtle problem. Systemd should detect such situation an complain about it. STEP by STEP mode is obviously a debug mode. - On a more philosophical side: * linking PID1 and systemd seems to me a problem (why it is mandatory still escape me), systemd is an init system. init systems run as PID 1. This how Unix works. Yes and I agree, But according my understanding of systemd, many function done by systemd do not need to be PID1. In fact complexity and smart action could be moved away from PID1 process keeping PID1 part, lean and simple. Such way, you could start systemd smart and interesting part from a shell script (which open a lot flexibility an robustness). Bug: - After a very quick check, there is maybe a bug the way systemd is handling 'int reboot(int cmd);', I have the strong feeling systemd is not feeding WTERMSIG(status), but it is very preliminary, I could be wrong Hmm? I cannot parse this. OK... when within the container a reboot is issued by admin, there is a way to advise container superviser (the process above systemd), this is done by reporting a signal status. 'plain init' and 'upstart' are doing that properly, seems to me systemd is not doing it... I didn't double check this, very prelimary report. (hoping this time you can parse my explaination). Many Thanks Lennart. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- A bientôt === Jean-Marc PigeonE-Mail: j...@safe.ca SAFE Inc. Phone: (514) 493-4280 Clement, 'a kiss solution' to get rid of SPAM (at last) Clement' Home base http://www.clement.safe.ca; === smime.p7s Description: S/MIME Cryptographic Signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 960011] Sending large object (many levels deep) throws error Incorrect parameter at line 1993
https://bugzilla.redhat.com/show_bug.cgi?id=960011 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|MODIFIED|CLOSED Resolution|--- |ERRATA Last Closed||2013-07-04 07:48:30 -- 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=YzLgiBA11Ga=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
rawhide report: 20130704 changes
Compose started at Thu Jul 4 08:15:02 UTC 2013 Broken deps for x86_64 -- [avgtime] avgtime-0-0.6.git20130201.fc20.x86_64 requires libphobos-ldc.so.60()(64bit) [derelict] derelict-tcod-3-20.20130626gite70c293.fc20.i686 requires tcod derelict-tcod-3-20.20130626gite70c293.fc20.x86_64 requires tcod derelict-tcod-devel-3-20.20130626gite70c293.fc20.i686 requires tcod derelict-tcod-devel-3-20.20130626gite70c293.fc20.x86_64 requires tcod [ekiga] ekiga-4.0.1-1.fc19.x86_64 requires libedata-book-1.2.so.17()(64bit) [evolution-rss] 1:evolution-rss-0.3.93-3.fc20.x86_64 requires libeutil.so()(64bit) 1:evolution-rss-0.3.93-3.fc20.x86_64 requires libeshell.so()(64bit) [gdb-heap] gdb-heap-0.5-12.fc19.x86_64 requires glibc(x86-64) = 0:2.17 [gooddata-cl] gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java [gr-air-modes] gr-air-modes-0-0.13.20130409gitf25d21f5.fc20.i686 requires libgruel-3.6.5.so.0.0.0 gr-air-modes-0-0.13.20130409gitf25d21f5.fc20.i686 requires libgnuradio-core-3.6.5.so.0.0.0 gr-air-modes-0-0.13.20130409gitf25d21f5.fc20.x86_64 requires libgruel-3.6.5.so.0.0.0()(64bit) gr-air-modes-0-0.13.20130409gitf25d21f5.fc20.x86_64 requires libgnuradio-core-3.6.5.so.0.0.0()(64bit) [gr-osmosdr] gr-osmosdr-0.0.1-3.20130403gite85c68d9.fc20.i686 requires libgruel-3.6.5.so.0.0.0 gr-osmosdr-0.0.1-3.20130403gite85c68d9.fc20.i686 requires libgnuradio-fcd-3.6.5.so.0.0.0 gr-osmosdr-0.0.1-3.20130403gite85c68d9.fc20.i686 requires libgnuradio-core-3.6.5.so.0.0.0 gr-osmosdr-0.0.1-3.20130403gite85c68d9.fc20.x86_64 requires libgruel-3.6.5.so.0.0.0()(64bit) gr-osmosdr-0.0.1-3.20130403gite85c68d9.fc20.x86_64 requires libgnuradio-fcd-3.6.5.so.0.0.0()(64bit) gr-osmosdr-0.0.1-3.20130403gite85c68d9.fc20.x86_64 requires libgnuradio-core-3.6.5.so.0.0.0()(64bit) gr-osmosdr-devel-0.0.1-3.20130403gite85c68d9.fc20.i686 requires pkgconfig(gnuradio-core) gr-osmosdr-devel-0.0.1-3.20130403gite85c68d9.fc20.x86_64 requires pkgconfig(gnuradio-core) [gtkd] gtkd-2.0.0-29.20120815git9ae9181.fc18.i686 requires libphobos-ldc.so.60 gtkd-2.0.0-29.20120815git9ae9181.fc18.x86_64 requires libphobos-ldc.so.60()(64bit) [jboss-as] jboss-as-7.1.1-19.fc20.noarch requires cxf-common = 0:2.6.3 [kawa] 1:kawa-1.11-5.fc19.x86_64 requires servlet25 [koji] koji-vm-1.8.0-1.fc20.noarch requires python-virtinst [kyua-cli] kyua-cli-0.5-3.fc19.x86_64 requires liblutok.so.0()(64bit) kyua-cli-tests-0.5-3.fc19.x86_64 requires liblutok.so.0()(64bit) [lancet] lancet-1.0.1-6.fc19.noarch requires ant-nodeps = 0:1.7.1 [openbox] gdm-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel gnome-panel-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel [openlierox] openlierox-0.59-0.11.beta10.fc20.x86_64 requires libgd.so.2()(64bit) [ovirt-engine] ovirt-engine-notification-service-3.1.0-1.fc19.noarch requires classpathx-mail [ovirt-guest-agent] ovirt-guest-agent-gdm-plugin-1.0.6-6.fc19.x86_64 requires libgdmsimplegreeter.so.1()(64bit) [oyranos] oyranos-libs-0.4.0-7.fc19.i686 requires libraw.so.5 oyranos-libs-0.4.0-7.fc19.x86_64 requires libraw.so.5()(64bit) [perl-Bio-ASN1-EntrezGene] perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) [perl-Bio-SamTools] perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq) [perl-PDL] perl-PDL-2.4.10-6.fc19.x86_64 requires libgd.so.2()(64bit) [perl-qpid] perl-qpid-0.22-2.fc20.x86_64 requires libqpidtypes.so.1.0.0()(64bit) perl-qpid-0.22-2.fc20.x86_64 requires libqpidmessaging.so.2.0.0()(64bit) [python-TraitsBackendQt] python-TraitsBackendQt-3.5.0-5.fc19.noarch requires python-TraitsGUI [ruby-RMagick] ruby-RMagick-2.13.1-11.fc20.2.x86_64 requires ImageMagick = 0:6.8.5.10 [rubygem-openshift-origin-common] rubygem-openshift-origin-common-1.8.10-1.fc20.noarch requires rubygem(safe_yaml) [rubygem-openshift-origin-node] rubygem-openshift-origin-node-1.9.15-1.fc20.noarch requires rubygem(safe_yaml) rubygem-openshift-origin-node-1.9.15-1.fc20.noarch requires openshift-origin-node-proxy [rubygem-qpid] rubygem-qpid-0.16.0-14.fc20.x86_64 requires libqpidmessaging.so.3()(64bit) rubygem-qpid-0.16.0-14.fc20.x86_64 requires libqpidcommon.so.5()(64bit) rubygem-qpid-0.16.0-14.fc20.x86_64 requires libqpidclient.so.5()(64bit) [rubygem-qpid_messaging] rubygem-qpid_messaging-0.22.0-1.fc20.x86_64 requires libqpidtypes.so.1.0.0()(64bit) rubygem-qpid_messaging-0.22.0-1.fc20.x86_64 requires libqpidmessaging.so.2.0.0()(64bit)
Orphaning be and python-storm
Dear all, I'm orphaning the following packages: be, Bugs Everywhere, a DVCS-based issue tracker python-storm, the Canonical-sponsored ORM for Python In both cases, upstream's own test harnesses tend to bring up several different failures, so whoever picks them up should probably invest some time in pushing fixes back upstream. Best regards, -- Michel Alexandre Salim Fedora Project Contributor: http://fedoraproject.org/ Email: sali...@fedoraproject.org | GPG key ID: A36A937A Jabber: hir...@jabber.ccc.de | IRC: hir...@irc.freenode.net () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Who uses abi-compliance-checker?
Sérgio Basto wrote: On Qua, 2013-07-03 at 15:03 -0500, Richard Shaw wrote: I initially got abi-compliance-checker into Fedora because one of my packages does not maintain any sort of API/ABI compatibility or even versioning for that matter. That way I could always check a new release to see if any of its dependencies needed to be rebuilt. Since then, I've started using it for all of my libraries in the spirit of Trust but verify, and I've occasionally found issues even though upstream didn't bump the soversion. So out of curiosity, anyone else using this great tool? If anyone is curious about it, I don't mind typing up the process I go through to make the checks. I think I've found a pretty good path of least resistance method :) could we use this tool on x264/ffmpeg/mplayer packages ? See results of analysis for ffmpeg here: http://upstream-tracker.org/versions/ffmpeg.html -- Andrey Ponomarenko, ROSA Lab. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Who uses abi-compliance-checker?
Xavier Bachelot wrote: On 07/03/2013 10:03 PM, Richard Shaw wrote: I initially got abi-compliance-checker into Fedora because one of my packages does not maintain any sort of API/ABI compatibility or even versioning for that matter. That way I could always check a new release to see if any of its dependencies needed to be rebuilt. Since then, I've started using it for all of my libraries in the spirit of Trust but verify, and I've occasionally found issues even though upstream didn't bump the soversion. So out of curiosity, anyone else using this great tool? I'm not using abi-compliance-checker by itself but through the pkgdiff wrapper. Starting with 1.6 version of pkgdiff if you compare debug packages and add --details option on the command line then the tool will automatically run abi-dumper to dump ABI of old and new shared objects found in the packages and then compare them by the abi-compliance-checker tool. I agree this tool is very helpful. -- Andrey Ponomarenko, ROSA Lab. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Who uses abi-compliance-checker?
Remi Collet wrote: But I also use http://upstream-tracker.org/ Very usefull, except for not yet released version. For some libraries we check unreleased versions from the upstream source control (git, svn, etc.). See example: http://upstream-tracker.org/versions/libssh.html -- Andrey Ponomarenko, ROSA Lab. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Who uses abi-compliance-checker?
Richard Shaw wrote: This is an extreme example, but after removing the offending headers I got this: https://dl.dropboxusercontent.com/u/34775202/compat_reports/ffmpeg/0.10.7_to_1.2.1/compat_report.html Thanks, Richard New approach (by using the abi-dumper tool) avoids such problems with compiling header files. But if you are using basic approach then you can take the input XML descriptor from the appropriate upstream-tracker page (push on the show log button to extend the content of descriptors): http://upstream-tracker.org/versions/ffmpeg.html -- Andrey Ponomarenko, ROSA Lab. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Who uses abi-compliance-checker?
On Wed, Jul 3, 2013 at 9:40 PM, Mathieu Bridon boche...@fedoraproject.orgwrote: On Wed, 2013-07-03 at 15:03 -0500, Richard Shaw wrote: If anyone is curious about it, I don't mind typing up the process I go through to make the checks. I think I've found a pretty good path of least resistance method :) I've never used it, but I'd certainly be interested in reading that if you ever write it up. :) I use a directory, abicompare in the home of my build user followed by the library name then a version folder, i.e.: ~/abicompare/OpenImageIO/1.0.11 and ~/abicompare/OpenImageIO/1.0.13 Then I use a little scripe I wrote[1] to unpack the main library and devel rpms into the version directory of each library because I can never remember how to do it manually: # cd ~/abicompare/OpenImageIO/1.0.11 # rpmunpack /path/to/rpms (repeat for second version) # abi-compliance-cheker -l OpenImageIO -dump 1.0.11/ (repeat for second version, the version as a directory works nicely because it will assume that's the version of the library so no need to specify the version manually) # abi-compliance-checker -l OpenImageIO -old /path/to/abidump-1.0.11 -new /path/to/abidump-1.0.13 Works like a charm as long as there's not any bad headers (like windows only headers) installed. If that happens I usually just have to rm the offending headers till I get a good dump. Audrey, How would this process change using abi-dump instead? Thanks, Richard [1] rpmunpack contents: #!/bin/bash if [ ! -n $1 ] then echo Unpacks an RPM into the current directory. echo echo Usage: `basename $0` package1 [package2]... fi for file in $*; do rpm2cpio $file | cpio -idmv done -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Compile-time shared library name mismatching base name (SDL)
On Mon, Jul 01, 2013 at 09:36:19AM +, Petr Pisar wrote: root@fedora-20:~ # ls -o /usr/lib64/libSDL* lrwxrwxrwx. 1 root 20 Jul 1 10:43 /usr/lib64/libSDL-1.2.so.0 - libSDL-1.2.so.0.11.4 -rwxr-xr-x. 1 root 444176 Jun 19 12:58 /usr/lib64/libSDL-1.2.so.0.11.4 lrwxrwxrwx. 1 root 20 Jul 1 10:55 /usr/lib64/libSDL.so - libSDL-1.2.so.0.11.4 root@fedora-20:~ # ldconfig -v |grep SDL ldconfig: Can't stat /libx32: No such file or directory ldconfig: Path `/usr/lib' given more than once ldconfig: Path `/usr/lib64' given more than once ldconfig: Can't stat /usr/libx32: No such file or directory libSDL-1.2.so.0 - libSDL.so If I remove the libSDL.so, then ldconfig leaves this silly idea and returns to expected value (libSDL-1.2.so.0 - libSDL-1.2.so.0.11.4). Is adding the libSDL-1.2.so symlink (and preserving libSDL.so) for backward compatibility wise? Perhaps the best option would be to rename the symlink and replace it with a linker script containing just INPUT(-lSDL-1.2) to keep ldconfig happy. This is how it's done in the ncurses-devel package for libcurses. -- Miroslav Lichvar -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Who uses abi-compliance-checker?
Richard Shaw wrote: On Wed, Jul 3, 2013 at 9:40 PM, Mathieu Bridon boche...@fedoraproject.org mailto:boche...@fedoraproject.org wrote: On Wed, 2013-07-03 at 15:03 -0500, Richard Shaw wrote: If anyone is curious about it, I don't mind typing up the process I go through to make the checks. I think I've found a pretty good path of least resistance method :) I've never used it, but I'd certainly be interested in reading that if you ever write it up. :) I use a directory, abicompare in the home of my build user followed by the library name then a version folder, i.e.: ~/abicompare/OpenImageIO/1.0.11 and ~/abicompare/OpenImageIO/1.0.13 Then I use a little scripe I wrote[1] to unpack the main library and devel rpms into the version directory of each library because I can never remember how to do it manually: # cd ~/abicompare/OpenImageIO/1.0.11 # rpmunpack /path/to/rpms (repeat for second version) # abi-compliance-cheker -l OpenImageIO -dump 1.0.11/ (repeat for second version, the version as a directory works nicely because it will assume that's the version of the library so no need to specify the version manually) # abi-compliance-checker -l OpenImageIO -old /path/to/abidump-1.0.11 -new /path/to/abidump-1.0.13 Works like a charm as long as there's not any bad headers (like windows only headers) installed. If that happens I usually just have to rm the offending headers till I get a good dump. Audrey, How would this process change using abi-dump instead? The ABI dump should be created in the different way. Use abi-dumper 1.0.11/usr/lib/libopenImageio.so -o /path/to/abidump-1.0.11 -lver 1.0.11 command instead of abi-compliance-cheker -l OpenImageIO -dump 1.0.11/ to create the ABI dump. Note that the library should be compiled with debug info, so you should extract and compare appropriate debug-info rpm packages instead of release ones. Otherwise the tool will report can't find debug info in object(s). All of these steps are automated in the pkgdiff 1.6. Just compare debug-info rpm packages by this tool: pkgdiff --details libA-v1-debuginfo.rpm libA-v2-debuginfo.rpm, and see the output html report. -- Andrey Ponomarenko, ROSA Lab. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Who uses abi-compliance-checker?
Sounds like we need abi-dumper then... Anyone up for a review? https://bugzilla.redhat.com/show_bug.cgi?id=980937 Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Compile-time shared library name mismatching base name (SDL)
On Thu, Jul 04, 2013 at 05:39:02PM +0200, Florian Weimer wrote: On 07/04/2013 03:29 PM, Miroslav Lichvar wrote: Perhaps the best option would be to rename the symlink and replace it with a linker script containing just INPUT(-lSDL-1.2) to keep ldconfig happy. This is how it's done in the ncurses-devel package for libcurses. Unless I'm missing something, this is fairly common (see the attachment). Perhaps changing ldconfig is better? I think there was a reason why ldconfig did it, but I'm not sure what it was. You might want to ask the glibc maintainers. gpsd-libs-3.9-1.fc19.i686,/usr/lib/libgps.so.20.0,libgps.so.20 gpsd-libs-3.9-1.fc19.i686,/usr/lib/libgpsd.so.21.0,libgpsd.so.21 gpsd-libs-3.9-1.fc19.x86_64,/usr/lib64/libgps.so.20.0,libgps.so.20 gpsd-libs-3.9-1.fc19.x86_64,/usr/lib64/libgpsd.so.21.0,libgpsd.so.21 These look good to me. -- Miroslav Lichvar -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Compile-time shared library name mismatching base name (SDL)
On 07/04/2013 06:14 PM, Miroslav Lichvar wrote: gpsd-libs-3.9-1.fc19.i686,/usr/lib/libgps.so.20.0,libgps.so.20 gpsd-libs-3.9-1.fc19.i686,/usr/lib/libgpsd.so.21.0,libgpsd.so.21 gpsd-libs-3.9-1.fc19.x86_64,/usr/lib64/libgps.so.20.0,libgps.so.20 gpsd-libs-3.9-1.fc19.x86_64,/usr/lib64/libgpsd.so.21.0,libgpsd.so.21 These look good to me. True. The attached list (consisting of NEVRA, path of the symlink, and the embedded soname of the library to which it links) only contains *.so symlinks. It's still a substantial number. -- Florian Weimer / Red Hat Product Security Team adplug-devel-2.1-13.fc19.i686,/usr/lib/libadplug.so,libadplug-2.1.so.0 adplug-devel-2.1-13.fc19.x86_64,/usr/lib64/libadplug.so,libadplug-2.1.so.0 aiksaurus-devel-1:1.2.1-27.fc19.i686,/usr/lib/libAiksaurus.so,libAiksaurus-1.2.so.0 aiksaurus-devel-1:1.2.1-27.fc19.x86_64,/usr/lib64/libAiksaurus.so,libAiksaurus-1.2.so.0 aiksaurus-gtk-devel-1:1.2.1-27.fc19.i686,/usr/lib/libAiksaurusGTK.so,libAiksaurusGTK-1.2.so.0 aiksaurus-gtk-devel-1:1.2.1-27.fc19.x86_64,/usr/lib64/libAiksaurusGTK.so,libAiksaurusGTK-1.2.so.0 alsa-plugins-samplerate-1.0.27-1.fc19.i686,/usr/lib/alsa-lib/libasound_module_rate_samplerate_best.so,libasound_module_rate_samplerate.so alsa-plugins-samplerate-1.0.27-1.fc19.i686,/usr/lib/alsa-lib/libasound_module_rate_samplerate_linear.so,libasound_module_rate_samplerate.so alsa-plugins-samplerate-1.0.27-1.fc19.i686,/usr/lib/alsa-lib/libasound_module_rate_samplerate_medium.so,libasound_module_rate_samplerate.so alsa-plugins-samplerate-1.0.27-1.fc19.i686,/usr/lib/alsa-lib/libasound_module_rate_samplerate_order.so,libasound_module_rate_samplerate.so alsa-plugins-samplerate-1.0.27-1.fc19.x86_64,/usr/lib64/alsa-lib/libasound_module_rate_samplerate_best.so,libasound_module_rate_samplerate.so alsa-plugins-samplerate-1.0.27-1.fc19.x86_64,/usr/lib64/alsa-lib/libasound_module_rate_samplerate_linear.so,libasound_module_rate_samplerate.so alsa-plugins-samplerate-1.0.27-1.fc19.x86_64,/usr/lib64/alsa-lib/libasound_module_rate_samplerate_medium.so,libasound_module_rate_samplerate.so alsa-plugins-samplerate-1.0.27-1.fc19.x86_64,/usr/lib64/alsa-lib/libasound_module_rate_samplerate_order.so,libasound_module_rate_samplerate.so alsa-plugins-speex-1.0.27-1.fc19.i686,/usr/lib/alsa-lib/libasound_module_rate_speexrate_best.so,libasound_module_rate_speexrate.so alsa-plugins-speex-1.0.27-1.fc19.i686,/usr/lib/alsa-lib/libasound_module_rate_speexrate_medium.so,libasound_module_rate_speexrate.so alsa-plugins-speex-1.0.27-1.fc19.x86_64,/usr/lib64/alsa-lib/libasound_module_rate_speexrate_best.so,libasound_module_rate_speexrate.so alsa-plugins-speex-1.0.27-1.fc19.x86_64,/usr/lib64/alsa-lib/libasound_module_rate_speexrate_medium.so,libasound_module_rate_speexrate.so amanda-3.3.3-1.fc19.x86_64,/usr/lib64/libamanda.so,libamanda-3.3.3.so amanda-3.3.3-1.fc19.x86_64,/usr/lib64/libamandad.so,libamandad-3.3.3.so amanda-3.3.3-1.fc19.x86_64,/usr/lib64/libamar.so,libamar-3.3.3.so amanda-3.3.3-1.fc19.x86_64,/usr/lib64/libamglue.so,libamglue-3.3.3.so amanda-3.3.3-1.fc19.x86_64,/usr/lib64/libamxfer.so,libamxfer-3.3.3.so amanda-3.3.3-1.fc19.x86_64,/usr/lib64/libndmjob.so,libndmjob-3.3.3.so amanda-3.3.3-1.fc19.x86_64,/usr/lib64/libndmlib.so,libndmlib-3.3.3.so amanda-client-3.3.3-1.fc19.x86_64,/usr/lib64/libamclient.so,libamclient-3.3.3.so amanda-server-3.3.3-1.fc19.x86_64,/usr/lib64/libamdevice.so,libamdevice-3.3.3.so amanda-server-3.3.3-1.fc19.x86_64,/usr/lib64/libamserver.so,libamserver-3.3.3.so apr-util-freetds-1.4.1-8.fc19.x86_64,/usr/lib64/apr-util-1/apr_dbd_freetds.so,apr_dbd_freetds-1.so apr-util-ldap-1.4.1-8.fc19.x86_64,/usr/lib64/apr-util-1/apr_ldap.so,apr_ldap-1.so apr-util-mysql-1.4.1-8.fc19.x86_64,/usr/lib64/apr-util-1/apr_dbd_mysql.so,apr_dbd_mysql-1.so apr-util-nss-1.4.1-8.fc19.x86_64,/usr/lib64/apr-util-1/apr_crypto_nss.so,apr_crypto_nss-1.so apr-util-odbc-1.4.1-8.fc19.x86_64,/usr/lib64/apr-util-1/apr_dbd_odbc.so,apr_dbd_odbc-1.so apr-util-openssl-1.4.1-8.fc19.x86_64,/usr/lib64/apr-util-1/apr_crypto_openssl.so,apr_crypto_openssl-1.so apr-util-pgsql-1.4.1-8.fc19.x86_64,/usr/lib64/apr-util-1/apr_dbd_pgsql.so,apr_dbd_pgsql-1.so apr-util-sqlite-1.4.1-8.fc19.x86_64,/usr/lib64/apr-util-1/apr_dbd_sqlite3.so,apr_dbd_sqlite3-1.so bacula-devel-5.2.13-11.fc19.x86_64,/usr/lib64/libbac.so,libbac-5.2.13.so bacula-devel-5.2.13-11.fc19.x86_64,/usr/lib64/libbaccfg.so,libbaccfg-5.2.13.so bacula-devel-5.2.13-11.fc19.x86_64,/usr/lib64/libbacfind.so,libbacfind-5.2.13.so bacula-devel-5.2.13-11.fc19.x86_64,/usr/lib64/libbacpy.so,libbacpy-5.2.13.so bacula-devel-5.2.13-11.fc19.x86_64,/usr/lib64/libbacsql.so,libbacsql-5.2.13.so bacula-libs-sql-5.2.13-11.fc19.x86_64,/usr/lib64/libbaccats-mysql.so,libbaccats-5.2.13.so bacula-libs-sql-5.2.13-11.fc19.x86_64,/usr/lib64/libbaccats-postgresql.so,libbaccats-5.2.13.so bacula-libs-sql-5.2.13-11.fc19.x86_64,/usr/lib64/libbaccats-sqlite3.so,libbaccats-5.2.13.so bakery-devel-1:2.6.3-10.fc19.i686,/usr/lib/libbakery-2.6.so,libbakery-2.6-.6.so.1
Re: Circular dependencies in texlive?
I tried to build texlive-2013-0.1.20130608_r30832.fc19.src.rpm for EPEL, the build failed with the following error: error: Failed build dependencies: harfbuzz-devel is needed by texlive-3:2013-0.1.20130608_r30832.el6.x86_64 graphite2-devel is needed by texlive-3:2013-0.1.20130608_r30832.el6.x86_64 Notice that you are mixing .fc19 and .el6. This allows another place for things to go wrong. So, building texlive-2013 requires graphite2-devel, and building graphite2-devel requires texlive2013. Yes, but each dependency can be satisfied by installing a binary .rpm which is available. Building texlive-2013 from source cannot proceed unless the binary of graphite2-devel has been installed before the build starts. So yum install graphite2-devel. Today this is not a circular dependency, although it may be impossible to rebuild the world from source only, without using some previous [or current] binary version of graphite2-devel. Once upon a time the dependencies were not as strict, or there was a bootstrapping stage that is not recorded in the .spec, or there was manual cheating, etc. Does somebody succeed to open texlive.spec? When trying to browse this file, kwrite suddenly stops. I have no trouble. Check your download, disk space, etc. Here are my md5sum: 53c5ebfad7693a476417aa407d3688c8 texlive-2013-0.1.20130608_r30832.fc19.src.rpm d7fe656e5ec3727cc26dbcc216e3553f rpmbuild/SPECS/texlive.spec texlinve.spec has 329,568 lines, 14,562,823 bytes. The texlive-2013 .fc19.src.rpm has 1,672,612,100 bytes. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: More unhelpful update descriptions
On 2013-07-04 2:56, Till Maas wrote: On Tue, Jul 02, 2013 at 09:39:47PM -0700, Adam Williamson wrote: most updates get submitted with the default +3 auto-push, even though it's perhaps not appropriate for all updates. So can we please get a sane default value then that is good for most updates and can be adjusted for special cases (and later per-package)? It would be interesting to make the default 1 or 2 for non-critpath and 3 for critpath... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 19 Gnome Desktop Touchscreen Usability
On 2013-07-04 3:04, Thomas Sailer wrote: I can operate the full gnome desktop with a mouse, the touchpad, and a digitizer pen. I can operate all applications with fingers. However, I cannot operate the gnome shell using fingers. When I tap on for example Activities, the battery icon or a close button in a window title bar, that item gets highlighted, but nothing else happens. On Fedora 18, I could operate the shell with fingers too. I cannot see any difference in the generated ButtonPress and ButtonRelease events (using xev) with the mouse or the finger. The only difference is that finger motion cannot be tracked without button press, i.e. the MotionNotify events are missing from the finger. What is happening here? How can I get the shell to accept finger input too? But...but...Shell is for tablets! Everyone knows that! The internets told me so! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 19 Gnome Desktop Touchscreen Usability
On Thu, Jul 4, 2013 at 12:04 PM, Thomas Sailer sai...@sailer.dynip.lugs.ch wrote: What is happening here? How can I get the shell to accept finger input too? It is fallout from the port to XInput2, see https://bugzilla.gnome.org/show_bug.cgi?id=697192. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: More unhelpful update descriptions
On Thu, Jul 04, 2013 at 02:51:46PM -0700, Adam Williamson wrote: It would be interesting to make the default 1 or 2 for non-critpath and 3 for critpath... +1 Let's do it! -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: New package written in Python, without python-*
Bohuslav/Toshio,
Thank you for opinions and informations, i belive what now this
point is more clear for me.
Marcelo Barbosa
Fedora Project Packager
Fedora Project Ambassador
fireman...@fedoraproject.org
http://planet.fedoraproject.org
On Tue, Jul 2, 2013 at 1:40 PM, Toshio Kuratomi a.bad...@gmail.com wrote:
On Tue, Jul 02, 2013 at 02:45:45AM -0400, Bohuslav Kabrda wrote:
- Original Message -
Hi everybody,
I have a question about the name of a new package and would like
everyone's opinion on this issue, because in our wiki
(http://fedoraproject.org/wiki/Features/PythonNamingDependingOnImplementation)
practically forces whatever is written in Python to have name:
python-% {name}, but I believe this is very bad for our users, if the
package is a tool, not a python module the user would like to use this
package:
Several notes aboout this:
* This proposed feature page hasn't yet been completed so it carries no
official weight as of yet. You should instead read the NamingGuidelines
and Python guidelines pages as bkabrda points out. (All current Packaging
Guidelines live under the /wiki/Packaging: namespace. Things outside of
that are not official standards for packages at this time).
* If you're building a package that has both a python2 and a python3
implementation then that's likely a sign that the usage as a python
library is more important than you think. It's probably wise to use the
python-* naming convention then.
# Yum install python-% {name}
$ ./python-% {Name}-u xxx-p xxx-f file1.txt file2.txt
This is not the real purpose of the package, which aims to be a
tool for use by our users.
There are also packages in Fedora are tools that are written in
Python and is not named python-% {name}, eg fpaste
(https://apps.fedoraproject.org/packages/fpaste/sources/spec).
I created this ticket and transmit it to everyone to view and opine:
https://bugzilla.redhat.com/show_bug.cgi?id=980318
Hi,
there is a note in the naming guidelines regarding this [1]:
If a new package is considered an addon package that enhances or adds a
new functionality to an existing Fedora package without being useful on its
own, its name should reflect this fact.
Therefore if you don't consider your package to be an addon (in this case,
addon would be a Python library), but an application, you should name it
without the python- prefix.
The way you chose to name your application seems perfectly fine to me.
tldr; : +1
The longer version:
Naming of packages of applications written in python often have a bit of
maintainer discretion. Oftentimes a package will contain both a public
module (files exist in %python_sitelib or %python_sitearch) and a program
(something in /usr/bin that is run.) We tell maintainers to evaluate this
according to whether the package is primarily of use as a module (library of
python code) or as an application that end user's invoke.
Thus we have the yum package and python-docutils packages where the
maintainers have evaluated and chosen what they think is the best fit for
their particular packages.
The python-* naming convention can also be used in cases where the name of
the python package might otherwise conflict with another package.
For instance, python-pip and perl-pip even though user's are much more
likely to be using /usr/bin/pip than importing the pip module.
Finally, it isn't currently a requirement of the naming guidelines but it
might be a good idea to use a Virtual Provide or split off a subpackage
where a package has a use case for both python modules and as an
application. That way end users get what they expect when they yum install
python-gists or yum install gists. (and note -- I can't think of any
packages that use a subpackage for this atm so that's likely overkill for
most things).
-Toshio
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: More unhelpful update descriptions
On Thu, 2013-07-04 at 18:55 -0400, Matthew Miller wrote: On Thu, Jul 04, 2013 at 02:51:46PM -0700, Adam Williamson wrote: It would be interesting to make the default 1 or 2 for non-critpath and 3 for critpath... +1 Let's do it! Untested, but this should work: http://bochecha.fedorapeople.org/tmp/0001-Set-the-default-stable_karma-to-1.patch -- Mathieu -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 768846] httpd+mod_perl and BerkeleyDB incompatibility
https://bugzilla.redhat.com/show_bug.cgi?id=768846 --- Comment #14 from Fedora End Of Life endofl...@fedoraproject.org --- This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- 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=Rg86K1uDZSa=cc_unsubscribe -- 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
[Bug 628655] perl segfaults when joining a thread and using perl-Tk
https://bugzilla.redhat.com/show_bug.cgi?id=628655 --- Comment #4 from Fedora End Of Life endofl...@fedoraproject.org --- This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- 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=360lnFWPLXa=cc_unsubscribe -- 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
[Bug 758869] perl-Proc-ProcessTable: unsafe temporary file usage [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=758869 --- Comment #3 from Fedora End Of Life endofl...@fedoraproject.org --- This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- 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=M5PLjbMYkqa=cc_unsubscribe -- 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
[Bug 960011] Sending large object (many levels deep) throws error Incorrect parameter at line 1993
https://bugzilla.redhat.com/show_bug.cgi?id=960011 --- Comment #8 from Fedora End Of Life endofl...@fedoraproject.org --- This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- 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=Arc8KdF7uYa=cc_unsubscribe -- 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
[Bug 849703] Regular Expression matching in signal handler causes side-effects
https://bugzilla.redhat.com/show_bug.cgi?id=849703 --- Comment #12 from Fedora End Of Life endofl...@fedoraproject.org --- This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- 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=f4uyofC1xOa=cc_unsubscribe -- 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
[Bug 967719] Segfault in Perl_gv_fetchpvn_flags when trying to initialize back_perl openldap backend
https://bugzilla.redhat.com/show_bug.cgi?id=967719 --- Comment #6 from Petr Pisar ppi...@redhat.com --- I recompiled only modules in perl binary package and openldap for the test. Not yet all modules that exist. I also reverted the RTLD_GLOBAL patch and checked slapd does not crashes on linkage error. So the test does not use any not-yet-rebuild modules. I conclude this issue is independent on the linking bug #960048. But we will see more after rebuilding everything. -- 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=2WK8MK8aLva=cc_unsubscribe -- 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 perl-5.18.0.tar.bz2 uploaded to lookaside cache by jplesnik
A file has been added to the lookaside cache for perl: a832e928adfd36d162d2a5d3b631265c perl-5.18.0.tar.bz2 -- 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
[Bug 768846] httpd+mod_perl and BerkeleyDB incompatibility
https://bugzilla.redhat.com/show_bug.cgi?id=768846 Jan Pazdziora jpazdzi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Resolution|--- |NEXTRELEASE Last Closed|2012-08-07 14:39:13 |2013-07-04 03:33:31 --- Comment #15 from Jan Pazdziora jpazdzi...@redhat.com --- (In reply to Joe Orton from comment #12) Paul's comment 9 is a good point, downgrading perl-BerkeleyDB to db 4.8 as an f17 update will undoubtedly break existing users of the module. So I think we're screwed here, we can't fix it until f18. We could ship an alternative, conflicting version of perl-BerkeleyDB linked against lidb-4.8 if somebody was screaming for that. But it's probably best to CLOSED-SORRY-NEXTRELEASE this. Yes, I confirm that with Fedora 19 and the packages listed below, the problem is gone. # rpm -q httpd mod_perl perl-BerkeleyDB httpd-2.4.4-6.fc19.x86_64 mod_perl-2.0.7-12.20130221svn1448242.fc19.x86_64 perl-BerkeleyDB-0.51-4.fc19.x86_64 -- 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=KaSkLQT1Bia=cc_unsubscribe -- 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
[Bug 628655] perl segfaults when joining a thread and using perl-Tk
https://bugzilla.redhat.com/show_bug.cgi?id=628655 Jan Pazdziora jpazdzi...@redhat.com changed: What|Removed |Added Version|17 |19 --- Comment #5 from Jan Pazdziora jpazdzi...@redhat.com --- The same result in Fedora 19: # perl /tmp/code.pl exiting init finished Segmentation fault # echo $? 139 # rpm -q perl perl-Tk perl-5.16.3-265.fc19.x86_64 perl-Tk-804.030-4.fc19.x86_64 # -- 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=bT87xLcI8Fa=cc_unsubscribe -- 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
[Bug 880330] CVE-2012-5572 perl-Dancer: Newline injection due to improper CRLF escaping in cookie() and cookies() methods [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=880330 --- Comment #8 from Fedora End Of Life endofl...@fedoraproject.org --- This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- 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=qHfVP1itnQa=cc_unsubscribe -- 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
[Bug 758869] perl-Proc-ProcessTable: unsafe temporary file usage [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=758869 Jan Pazdziora jpazdzi...@redhat.com changed: What|Removed |Added Version|17 |19 --- Comment #4 from Jan Pazdziora jpazdzi...@redhat.com --- Marking as still present on Fedora 19 since changelog between 0.44-10 and 0.44-13 only has mass rebuilds there: # rpm -q perl-Proc-ProcessTable perl-Proc-ProcessTable-0.44-13.fc19.x86_64 # rpm -q --changelog perl-Proc-ProcessTable | head * Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org - 0.44-13 - Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild * Fri Jul 20 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org - 0.44-12 - Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild * Mon Jun 11 2012 Petr Pisar ppi...@redhat.com - 0.44-11 - Perl 5.16 rebuild * Fri Jan 13 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org - 0.44-10 # -- 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=s7E6npNooOa=cc_unsubscribe -- 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
[Bug 849703] Regular Expression matching in signal handler causes side-effects
https://bugzilla.redhat.com/show_bug.cgi?id=849703 --- Comment #13 from Jan Pazdziora jpazdzi...@redhat.com --- (In reply to Fedora Update System from comment #11) perl-5.16.3-264.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. Nice. With perl-5.16.3-262.fc19.x86_64, I see the problem, with perl-5.16.3-265.fc19.x86_64 it's done. I think you can NEXTRELEASE this bugzilla. -- 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=4IVWWMHOuLa=cc_unsubscribe -- 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
[Bug 838700] please update to new upstream version
https://bugzilla.redhat.com/show_bug.cgi?id=838700 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC||ppi...@redhat.com Assignee|rob...@marcanoonline.com|ppi...@redhat.com -- 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=sbo8pGqMSaa=cc_unsubscribe -- 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 Time-Period-1.23.tar.gz uploaded to lookaside cache by ppisar
A file has been added to the lookaside cache for perl-Time-Period: c677ed3e0b7f3f1ea1bc1c03efae699b Time-Period-1.23.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-Time-Period] 1.23 bump
commit 6efe55296002ae45baf347248a70a7951b6f8091
Author: Petr Písař ppi...@redhat.com
Date: Thu Jul 4 09:55:48 2013 +0200
1.23 bump
.gitignore|1 +
perl-Time-Period.spec | 22 --
sources |2 +-
3 files changed, 18 insertions(+), 7 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 285d107..81c773f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
Period-1.20.tar.gz
+/Time-Period-1.23.tar.gz
diff --git a/perl-Time-Period.spec b/perl-Time-Period.spec
index 022b8b8..ab97340 100644
--- a/perl-Time-Period.spec
+++ b/perl-Time-Period.spec
@@ -1,24 +1,31 @@
Name: perl-Time-Period
-Version:1.20
-Release:14%{?dist}
+Version:1.23
+Release:1%{?dist}
Summary:A Perl module to deal with time periods
Group: Development/Libraries
License:GPL+ or Artistic
-URL:http://search.cpan.org/dist/Period/
-Source0:
http://search.cpan.org/CPAN/authors/id/P/PR/PRYAN/Period-%{version}.tar.gz
+URL:http://search.cpan.org/dist/Time-Period/
+Source0:
http://search.cpan.org/CPAN/authors/id/P/PB/PBOYD/Time-Period-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: perl
BuildRequires: perl(ExtUtils::MakeMaker)
+BuildRequires: perl(strict)
+BuildRequires: perl(warnings)
+# Run-time:
+BuildRequires: perl(Exporter)
+# Tests:
+BuildRequires: perl(POSIX)
+BuildRequires: perl(Test::More)
Requires: perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo
$version))
%description
Period.pm is a Perl module that contains code to deal with time periods.
%prep
-%setup -q -n Period-%{version}
+%setup -q -n Time-Period-%{version}
%build
@@ -44,13 +51,16 @@ rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
-%doc
+%doc LICENSE README
# For noarch packages: vendorlib
%{perl_vendorlib}/*
%{_mandir}/man3/*.3*
%changelog
+* Thu Jul 04 2013 Petr Pisar ppi...@redhat.com - 1.23-1
+- 1.23 bump
+
* Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 1.20-14
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
diff --git a/sources b/sources
index 5f8df13..3a9d318 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-63b073af8ec96e7fa48801cd6fcccdd1 Period-1.20.tar.gz
+c677ed3e0b7f3f1ea1bc1c03efae699b Time-Period-1.23.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
[Bug 838700] please update to new upstream version
https://bugzilla.redhat.com/show_bug.cgi?id=838700 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Time-Period-1.23-1.fc2 ||0 Resolution|--- |RAWHIDE Last Closed||2013-07-04 04:02:40 -- 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=CkdtMTtCBNa=cc_unsubscribe -- 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
[Bug 914301] perl-Net-Amazon-S3: FTBFS in rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=914301 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC||ppi...@redhat.com Assignee|rr...@redhat.com|ppi...@redhat.com -- 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=uqDTPiyj2Ca=cc_unsubscribe -- 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
[Bug 890721] perl-Net-Amazon-S3 in Fedora 17 is dated and needs to be updated to stop warnings
https://bugzilla.redhat.com/show_bug.cgi?id=890721 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC||ppi...@redhat.com Assignee|rr...@redhat.com|ppi...@redhat.com --- Comment #2 from Petr Pisar ppi...@redhat.com --- Version 0.59 requires MooseX::Types::DateTime::MoreCoercions = 0.07 which is not packaged yet. -- 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=3i3ESMhDNta=cc_unsubscribe -- 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
[Bug 890721] perl-Net-Amazon-S3 in Fedora 17 is dated and needs to be updated to stop warnings
https://bugzilla.redhat.com/show_bug.cgi?id=890721 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Depends On||981200 -- 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=AVmK9OXJLka=cc_unsubscribe -- 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
[Bug 825678] SDL::App-new() on console framebuffer segfaults
https://bugzilla.redhat.com/show_bug.cgi?id=825678 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-SDL-2.540-2.fc18.x86_6 ||4 Resolution|--- |CURRENTRELEASE Last Closed||2013-07-04 05:58:36 --- Comment #12 from Petr Pisar ppi...@redhat.com --- It does not segfault in F18 anymore. But it does not work either. I will file new bug report. -- 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=J52ZDmct9ta=cc_unsubscribe -- 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
[Bug 981243] New: SDLx::App-new() does not work on frame buffer console
https://bugzilla.redhat.com/show_bug.cgi?id=981243
Bug ID: 981243
Summary: SDLx::App-new() does not work on frame buffer console
Product: Fedora
Version: 18
Component: perl-SDL
Severity: unspecified
Priority: unspecified
Assignee: hdego...@redhat.com
Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: hdego...@redhat.com,
perl-devel@lists.fedoraproject.org
Created attachment 768694
-- https://bugzilla.redhat.com/attachment.cgi?id=768694action=edit
Reproducer
I'm not able to initialize SDL video on frame buffer console using high-level
SDLx::App-new(). But it works with low-level SDL::Video::set_video_mode().
Output from the reproducer:
# DISPLAY= perl test -width 1280 -height 1024 -depth 32
Testing plain SDL:
Plain SDL::Video::set_video_mode() is Ok.
Width is 1280
Testing plain SDL::App:
Couldn't set console screen info at /usr/lib64/perl5/vendor_perl/SDLx/App.pm
line 123.
SDLx::App::new('SDLx::App', '-width', 1280, '-height', 1024, '-depth',
32) called at test line 32
root@dhcp-0-146:/tmp # rpm -q perl-SDL
perl-SDL-2.540-2.fc18.x86_64
--
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=GviunhawfMa=cc_unsubscribe
--
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
[Bug 973910] Upgrade to new upstream version
https://bugzilla.redhat.com/show_bug.cgi?id=973910 Massimo Paladin massimo.pala...@gmail.com changed: What|Removed |Added Status|MODIFIED|CLOSED Resolution|--- |CURRENTRELEASE Last Closed||2013-07-04 06:09:43 -- 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=EtKbhcZ8r3a=cc_unsubscribe -- 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
[Bug 981277] New: Dependency chain brings in X11
https://bugzilla.redhat.com/show_bug.cgi?id=981277 Bug ID: 981277 Summary: Dependency chain brings in X11 Product: Fedora Version: 19 Component: perl-Net-Server Severity: unspecified Priority: unspecified Assignee: ke...@scrye.com Reporter: glandva...@yahoo.com QA Contact: extras...@fedoraproject.org CC: ke...@scrye.com, perl-devel@lists.fedoraproject.org Description of problem: Starting with version 2.xx perl-Net-Server requires perl(Log::Log4perl) which brings in X11. Version-Release number of selected component (if applicable): perl-Net-Server-2.006-1 How reproducible: Always Steps to Reproduce: 1. Upgrade from f17 2. 3. Additional info: As this component may be used from mail servers (through postgrey component), it seems to me overkill to expect graphical libraries. -- 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=biCJBez9sEa=cc_unsubscribe -- 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
[Bug 849703] Regular Expression matching in signal handler causes side-effects
https://bugzilla.redhat.com/show_bug.cgi?id=849703 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Version|17 |18 --- Comment #14 from Petr Pisar ppi...@redhat.com --- I want to push the fix into F18 too. -- 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=OMelCVmnN0a=cc_unsubscribe -- 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
[Bug 959945] perl-WebService-Validator-CSS-W3C-0.3 is available
https://bugzilla.redhat.com/show_bug.cgi?id=959945 Bug 959945 depends on bug 960011, which changed state. Bug 960011 Summary: Sending large object (many levels deep) throws error Incorrect parameter at line 1993 https://bugzilla.redhat.com/show_bug.cgi?id=960011 What|Removed |Added Status|MODIFIED|CLOSED Resolution|--- |ERRATA -- 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=2q8QMuDB9Aa=cc_unsubscribe -- 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
[Bug 880329] CVE-2012-5572 perl-Dancer: Newline injection due to improper CRLF escaping in cookie() and cookies() methods
https://bugzilla.redhat.com/show_bug.cgi?id=880329 Bug 880329 depends on bug 880330, which changed state. Bug 880330 Summary: CVE-2012-5572 perl-Dancer: Newline injection due to improper CRLF escaping in cookie() and cookies() methods [fedora-all] https://bugzilla.redhat.com/show_bug.cgi?id=880330 What|Removed |Added Status|MODIFIED|CLOSED Resolution|--- |ERRATA -- 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=IjsfRiJn5Ya=cc_unsubscribe -- 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
[Bug 880330] CVE-2012-5572 perl-Dancer: Newline injection due to improper CRLF escaping in cookie() and cookies() methods [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=880330 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|MODIFIED|CLOSED Resolution|--- |ERRATA Last Closed||2013-07-04 07:50:10 -- 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=gArejarSxZa=cc_unsubscribe -- 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
[Bug 849703] Regular Expression matching in signal handler causes side-effects
https://bugzilla.redhat.com/show_bug.cgi?id=849703 --- Comment #15 from Jan Pazdziora jpazdzi...@redhat.com --- (In reply to Petr Pisar from comment #14) I want to push the fix into F18 too. Ah, good for you. ;-) -- 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=2Qb0EV1NI7a=cc_unsubscribe -- 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
Broken dependencies: perl-Bio-SamTools
perl-Bio-SamTools has broken dependencies in the rawhide tree: On x86_64: perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq) On i386: perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::SeqFeature::Lite) perl-Bio-SamTools-1.35-2.fc19.i686 requires perl(Bio::PrimarySeq) 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
Broken dependencies: perl-PDL
perl-PDL has broken dependencies in the rawhide tree: On x86_64: perl-PDL-2.4.10-6.fc19.x86_64 requires libgd.so.2()(64bit) On i386: perl-PDL-2.4.10-6.fc19.i686 requires libgd.so.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
Broken dependencies: perl-Bio-ASN1-EntrezGene
perl-Bio-ASN1-EntrezGene has broken dependencies in the rawhide tree: On x86_64: perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) On i386: perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires perl(Bio::Index::AbstractSeq) 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
[Bug 981277] Dependency chain brings in X11
https://bugzilla.redhat.com/show_bug.cgi?id=981277 Petr Pisar ppi...@redhat.com changed: What|Removed |Added CC||ppi...@redhat.com --- Comment #1 from Petr Pisar ppi...@redhat.com --- perl-Net-Server → perl(Log::Log4perl) → perl(RRDs) → rrdtool → libcairo.so.2()(64bit) → libX11.so.6()(64bit). -- 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=xhtP3GKqNVa=cc_unsubscribe -- 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
[Bug 959945] perl-WebService-Validator-CSS-W3C-0.3 is available
https://bugzilla.redhat.com/show_bug.cgi?id=959945 Petr Pisar ppi...@redhat.com changed: What|Removed |Added Status|MODIFIED|CLOSED Resolution|--- |ERRATA Last Closed||2013-07-04 09:01:09 -- 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=Axtcn5JVpfa=cc_unsubscribe -- 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
[Bug 981277] Dependency chain brings in X11
https://bugzilla.redhat.com/show_bug.cgi?id=981277 --- Comment #2 from Paul Howarth p...@city-fan.org --- Updating to the current upstream release 2.007 should resolve this, as the Log::Log4perl dependency is pulled in in such a way that rpm won't find it (i.e. it becomes optional, as upstream intended). A rawhide build will also need the patch I attached to https://rt.cpan.org/Public/Bug/Display.html?id=86707 as IO::Socket::SSL is now trying to verify server certificates by default, which affects Net::Server's test suite. -- 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=eeib9wanmSa=cc_unsubscribe -- 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 Class-C3-0.25.tar.gz uploaded to lookaside cache by pghmcfc
A file has been added to the lookaside cache for perl-Class-C3: 0fa29f69ac69b9ae573e42925fcfc0bd Class-C3-0.25.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
[Bug 977670] abi-compliance-checker-1.99.7 is available
https://bugzilla.redhat.com/show_bug.cgi?id=977670 Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org changed: What|Removed |Added Summary|abi-compliance-checker-1.99 |abi-compliance-checker-1.99 |.6 is available |.7 is available --- Comment #2 from Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org --- Latest upstream release: 1.99.7 Current version/release in Fedora Rawhide: 1.99.1-1.fc20 URL: http://ispras.linuxbase.org/index.php/ABI_compliance_checker_Downloads Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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=5sOtMnkp0Ha=cc_unsubscribe -- 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-Class-C3] Update to 0.25
commit 79b6f013720ef8fa97108a4052c88f848c917521
Author: Paul Howarth p...@city-fan.org
Date: Thu Jul 4 14:48:10 2013 +0100
Update to 0.25
- New upstream release 0.25:
- Drop compatibility from 5.6.2 to 5.6.0
- Pod typo fixes (CPAN RT#77453, CPAN RT#85357)
- Only ask for Devel::Hide on perls where it will be actually used
(CPAN RT#81106)
- Fix SYNOPSIS to actually be executable (CPAN RT#78327)
- This release by MSTROUT - update source URL
- BR: perl(ExtUtils::CBuilder) and perl(File::Glob)
- Bump perl(Class::C3::XS) version requirement to 0.13
perl-Class-C3.spec | 23 ++-
sources|2 +-
2 files changed, 19 insertions(+), 6 deletions(-)
---
diff --git a/perl-Class-C3.spec b/perl-Class-C3.spec
index d8f2321..44c4eb4 100644
--- a/perl-Class-C3.spec
+++ b/perl-Class-C3.spec
@@ -2,21 +2,23 @@
%global mro_in_core %(perl -e 'print $] 5.009005 ? 1 : 0;')
Name: perl-Class-C3
-Version: 0.24
-Release: 5%{?dist}
+Version: 0.25
+Release: 1%{?dist}
Summary: Pragma to use the C3 method resolution order algorithm
License: GPL+ or Artistic
Group: Development/Libraries
URL: http://search.cpan.org/dist/Class-C3/
-Source0:
http://search.cpan.org/CPAN/authors/id/F/FL/FLORA/Class-C3-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/M/MS/MSTROUT/Class-C3-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(id -nu)
BuildArch: noarch
# Build
+BuildRequires: perl(ExtUtils::CBuilder)
BuildRequires: perl(ExtUtils::MakeMaker)
# Module
BuildRequires: perl(Algorithm::C3) = 0.07
BuildRequires: perl(Scalar::Util) = 1.10
# Test suite
+BuildRequires: perl(File::Glob)
BuildRequires: perl(Sub::Name)
BuildRequires: perl(Test::Exception) = 0.15
BuildRequires: perl(Test::More) = 0.47
@@ -34,8 +36,8 @@ Requires: perl(Scalar::Util) = 1.10
# Requirements for older distributions with Perl 5.9.5
%if ! %{mro_in_core}
-BuildRequires: perl(Class::C3::XS) = 0.07
-Requires: perl(Class::C3::XS) = 0.07
+BuildRequires: perl(Class::C3::XS) = 0.13
+Requires: perl(Class::C3::XS) = 0.13
%endif
# Let people use c3;
@@ -90,6 +92,17 @@ rm -rf %{buildroot}
%{_mandir}/man3/Class::C3::next.3pm*
%changelog
+* Thu Jul 4 2013 Paul Howarth p...@city-fan.org - 0.25-1
+- Update to 0.25:
+ - Drop compatibility from 5.6.2 to 5.6.0
+ - Pod typo fixes (CPAN RT#77453, CPAN RT#85357)
+ - Only ask for Devel::Hide on perls where it will be actually used
+(CPAN RT#81106)
+ - Fix SYNOPSIS to actually be executable (CPAN RT#78327)
+- This release by MSTROUT - update source URL
+- BR: perl(ExtUtils::CBuilder) and perl(File::Glob)
+- Bump perl(Class::C3::XS) version requirement to 0.13
+
* Thu Feb 14 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 0.24-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
diff --git a/sources b/sources
index a25623b..0ad0eb2 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-c53c143998d0700c5b3190801b6800ea Class-C3-0.24.tar.gz
+0fa29f69ac69b9ae573e42925fcfc0bd Class-C3-0.25.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-Class-C3] Created tag perl-Class-C3-0.25-1.fc20
The lightweight tag 'perl-Class-C3-0.25-1.fc20' was created pointing to: 79b6f01... Update to 0.25 -- 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
[Bug 981277] Dependency chain brings in X11
https://bugzilla.redhat.com/show_bug.cgi?id=981277 --- Comment #3 from Petr Pisar ppi...@redhat.com --- I've been thinking long time to sub-package the Log::Log4perl::Appender::RRDs from perl-Log-Log4perl because of this reason. I guess it will not affect much users. -- 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=mkStiXNFdta=cc_unsubscribe -- 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 abi-compliance-checker-1.99.7.tar.gz uploaded to lookaside cache by hobbes1069
A file has been added to the lookaside cache for abi-compliance-checker: fcaf993073939e62130b27238e8b6166 abi-compliance-checker-1.99.7.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
[abi-compliance-checker] Update to latest bugfix release.
commit e908fd56ff08f7a8260847a96dd259757e4a04b0
Author: Richard M. Shaw hobbes1...@gmail.com
Date: Thu Jul 4 09:21:21 2013 -0500
Update to latest bugfix release.
.gitignore |1 +
abi-compliance-checker.spec |8 +++-
sources |2 +-
3 files changed, 9 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 3a151b7..9961969 100644
--- a/.gitignore
+++ b/.gitignore
@@ -12,3 +12,4 @@
/abi-compliance-checker-1.98.8.tar.gz
/abi-compliance-checker-1.99.tar.gz
/abi-compliance-checker-1.99.1.tar.gz
+/abi-compliance-checker-1.99.7.tar.gz
diff --git a/abi-compliance-checker.spec b/abi-compliance-checker.spec
index dbc7ab5..e4a9d42 100644
--- a/abi-compliance-checker.spec
+++ b/abi-compliance-checker.spec
@@ -1,5 +1,5 @@
Name: abi-compliance-checker
-Version:1.99.1
+Version:1.99.7
Release:1%{?dist}
Summary:An ABI Compliance Checker
@@ -42,6 +42,12 @@ perl Makefile.pl -install --prefix=%{_prefix}
--destdir=%{buildroot}
%changelog
+* Fri Jun 29 2013 Richard Shaw hobbes1...@gmail.com - 1.99.7-1
+- Update to latest bugfix release.
+
+* Tue Jun 25 2013 Richard Shaw hobbes1...@gmail.com - 1.99.2-1
+- Update to latest bugfix release.
+
* Sat Jun 8 2013 Richard Shaw hobbes1...@gmail.com - 1.99.1-1
- Update to latest bugfix release.
diff --git a/sources b/sources
index e01e2da..a9d7633 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-1d4ed43ebfb995b41cfe2b3ff1e7d9be abi-compliance-checker-1.99.1.tar.gz
+fcaf993073939e62130b27238e8b6166 abi-compliance-checker-1.99.7.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
[abi-compliance-checker/f19] Update to latest bugfix release.
Summary of changes: e908fd5... Update to latest bugfix release. (*) (*) 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
[Bug 981277] Dependency chain brings in X11
https://bugzilla.redhat.com/show_bug.cgi?id=981277 --- Comment #4 from Eduard Kohler glandva...@yahoo.com --- Well, Log::Log4perl adds, to my system at least, about 67 dependent packages. A large chunk being other perl modules. The whole overhead in term of size is about 22MB, which is not huge, but so many unneeded packages just beg for future problems. -- 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=gdjJVYmdpLa=cc_unsubscribe -- 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
[Bug 981398] New: perl-App-cpanminus-1.6923 is available
https://bugzilla.redhat.com/show_bug.cgi?id=981398 Bug ID: 981398 Summary: perl-App-cpanminus-1.6923 is available Product: Fedora Version: rawhide Component: perl-App-cpanminus Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Assignee: mmasl...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mmasl...@redhat.com, perl-devel@lists.fedoraproject.org Latest upstream release: 1.6923 Current version/release in Fedora Rawhide: 1.6922-1.fc20 URL: http://search.cpan.org/dist/App-cpanminus/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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=D7oZXqA6Qna=cc_unsubscribe -- 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
[Bug 981399] New: perl-Config-General-2.52 is available
https://bugzilla.redhat.com/show_bug.cgi?id=981399 Bug ID: 981399 Summary: perl-Config-General-2.52 is available Product: Fedora Version: rawhide Component: perl-Config-General Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Assignee: nathan...@gnat.ca Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: nathan...@gnat.ca, perl-devel@lists.fedoraproject.org Latest upstream release: 2.52 Current version/release in Fedora Rawhide: 2.51-2.fc19 URL: http://search.cpan.org/dist/Config-General/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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=MMPzZuvDQVa=cc_unsubscribe -- 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
[Bug 981400] New: perl-Dancer-1.3116 is available
https://bugzilla.redhat.com/show_bug.cgi?id=981400 Bug ID: 981400 Summary: perl-Dancer-1.3116 is available Product: Fedora Version: rawhide Component: perl-Dancer Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Assignee: mmasl...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mmasl...@redhat.com, perl-devel@lists.fedoraproject.org Latest upstream release: 1.3116 Current version/release in Fedora Rawhide: 1.3115-1.fc20 URL: http://search.cpan.org/dist/Dancer/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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=I2yJ6HEp1Qa=cc_unsubscribe -- 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
[Bug 981401] New: perl-Digest-MD5-2.53 is available
https://bugzilla.redhat.com/show_bug.cgi?id=981401 Bug ID: 981401 Summary: perl-Digest-MD5-2.53 is available Product: Fedora Version: rawhide Component: perl-Digest-MD5 Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com Latest upstream release: 2.53 Current version/release in Fedora Rawhide: 2.52-1.fc20 URL: http://search.cpan.org/dist/Digest-MD5/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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=ZviZ9y2aKka=cc_unsubscribe -- 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
[Bug 981402] New: perl-File-MMagic-1.30 is available
https://bugzilla.redhat.com/show_bug.cgi?id=981402 Bug ID: 981402 Summary: perl-File-MMagic-1.30 is available Product: Fedora Version: rawhide Component: perl-File-MMagic Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Assignee: mmasl...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mmasl...@redhat.com, perl-devel@lists.fedoraproject.org Latest upstream release: 1.30 Current version/release in Fedora Rawhide: 1.29-3.fc19 URL: http://search.cpan.org/dist/File-MMagic/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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=0Y5kiLdsUoa=cc_unsubscribe -- 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
[Bug 981403] New: perl-IPC-Cmd-0.82 is available
https://bugzilla.redhat.com/show_bug.cgi?id=981403 Bug ID: 981403 Summary: perl-IPC-Cmd-0.82 is available Product: Fedora Version: rawhide Component: perl-IPC-Cmd Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com Latest upstream release: 0.82 Current version/release in Fedora Rawhide: 0.80-3.fc20 URL: http://search.cpan.org/dist/IPC-Cmd/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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=Hoet9Z82Owa=cc_unsubscribe -- 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
[Bug 981404] New: perl-POE-Component-Server-SimpleHTTP-2.18 is available
https://bugzilla.redhat.com/show_bug.cgi?id=981404 Bug ID: 981404 Summary: perl-POE-Component-Server-SimpleHTTP-2.18 is available Product: Fedora Version: rawhide Component: perl-POE-Component-Server-SimpleHTTP Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Assignee: psab...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mmasl...@redhat.com, perl-devel@lists.fedoraproject.org, psab...@redhat.com Latest upstream release: 2.18 Current version/release in Fedora Rawhide: 2.16-2.fc19 URL: http://search.cpan.org/dist/POE-Component-Server-SimpleHTTP/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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=wktgDqDhhna=cc_unsubscribe -- 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
[Bug 981405] New: perl-XML-LibXML-2.0019 is available
https://bugzilla.redhat.com/show_bug.cgi?id=981405 Bug ID: 981405 Summary: perl-XML-LibXML-2.0019 is available Product: Fedora Version: rawhide Component: perl-XML-LibXML Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Assignee: mmasl...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mmasl...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Latest upstream release: 2.0019 Current version/release in Fedora Rawhide: 2.0018-3.fc20 URL: http://search.cpan.org/dist/XML-LibXML/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring -- 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=8tP68162J0a=cc_unsubscribe -- 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
[Bug 818651] Conflicts with my package apache-1.3.42-3.fc16.x86_64
https://bugzilla.redhat.com/show_bug.cgi?id=818651 --- Comment #5 from Sergio Monteiro Basto ser...@serjux.com --- https://github.com/sergiomb2/Apache-1.3_mod_perl here is my apache-1.3.42 with mod_perl for Fedora 12-17 and Debian 5 and 6 -- 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=B41c2Kcy80a=cc_unsubscribe -- 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
[Bug 952589] perl-DateTime-1.03 is available
https://bugzilla.redhat.com/show_bug.cgi?id=952589 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-DateTime-1.03-1.fc20 |perl-DateTime-1.03-1.fc17 Resolution|--- |ERRATA Last Closed|2013-06-25 09:33:37 |2013-07-04 21:54:35 --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- perl-DateTime-1.03-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. -- 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=1z3L8nd96Ra=cc_unsubscribe -- 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
[Bug 952589] perl-DateTime-1.03 is available
https://bugzilla.redhat.com/show_bug.cgi?id=952589 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Fixed In Version|perl-DateTime-1.03-1.fc17 |perl-DateTime-1.03-1.fc19 --- Comment #8 from Fedora Update System upda...@fedoraproject.org --- perl-DateTime-1.03-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. -- 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=TfnKVfaRKWa=cc_unsubscribe -- 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
[Bug 952589] perl-DateTime-1.03 is available
https://bugzilla.redhat.com/show_bug.cgi?id=952589 Fedora Update System upda...@fedoraproject.org changed: What|Removed |Added Fixed In Version|perl-DateTime-1.03-1.fc19 |perl-DateTime-1.03-1.fc18 --- Comment #9 from Fedora Update System upda...@fedoraproject.org --- perl-DateTime-1.03-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. -- 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=vuLCZc6MzZa=cc_unsubscribe -- 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
