Re: [Fontconfig] Heads up: Droid fonts update in Rawhide
On 07/15/2012 06:01 PM, Nicolas Mailhot wrote: C. I tried to dispatch the Arabic variants in the Latin family they were designed to complement, but I may have misunderstood the design info available online. Please clarify 'dispatch' :-) Kufi with Sans (masquerading as the Arabic block of Droid Sans) and Naskh with Serif the same way (see the long fontconfig ruleset I referenced) http://www.29arabicletters.com/foundry/?m=1-1-1fid=26 states Naskh was designed to complement Serif and https://code.google.com/p/chromium-os/issues/detail?id=17382 that chromium uses Kufi with Sans That may have been the case, but it is my personal understanding that we should dispatch Naskh with both Sans and Serif. Kufi is a horrible font for body text. So make kufi a separate family and keep the old droid sans arabic for sans? Or is it also horrible in some way? Regards, -- Nicolas Mailhot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] CANCELLED: 2012-07-16 Fedora QA Meeting
Looks like another week where we can skip the meeting - there's no significant ongoing business besides the anaconda new UI testing, and we've already discussed that. No-one proposed any topics. If anyone's feeling terribly sad about missing meetings, do let me know... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Fontconfig] Heads up: Droid fonts update in Rawhide
On 07/15/2012 06:01 PM, Nicolas Mailhot wrote: C. I tried to dispatch the Arabic variants in the Latin family they were designed to complement, but I may have misunderstood the design info available online. Please clarify 'dispatch' :-) Kufi with Sans (masquerading as the Arabic block of Droid Sans) and Naskh with Serif the same way (see the long fontconfig ruleset I referenced) http://www.29arabicletters.com/foundry/?m=1-1-1fid=26 states Naskh was designed to complement Serif and https://code.google.com/p/chromium-os/issues/detail?id=17382 that chromium uses Kufi with Sans That may have been the case, but it is my personal understanding that we should dispatch Naskh with both Sans and Serif. Kufi is a horrible font for body text. So make kufi a separate family and keep the old droid sans arabic for sans? Or is it also horrible in some way? BTW regardless of your answer here, with your former fontconfig maintainer hat on, how do you make a font family masquerade as parts of two other font families? If I understand the recipe you gave me for use in Fedora, after Naskh has been morphed in Serif, it is not available anymore to morph in Sans. That would be a useful operation to perform for cultures which had not a western calligraphic separation culture Regards, -- Nicolas Mailhot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Review swaps
Once again I've a number of small audio packages up for review that I'm willing to swap. They are: rtirq - realtime IRQ threading https://bugzilla.redhat.com/show_bug.cgi?id=839527 Add64 - an additive synthesizer for JACK https://bugzilla.redhat.com/show_bug.cgi?id=830664 samplv1 -A polyphonic sampler synthesizer with stereo fx https://bugzilla.redhat.com/show_bug.cgi?id=829971 synthv1 - a 4 oscillator subtractive polyphonic synthesizer https://bugzilla.redhat.com/show_bug.cgi?id=829970 Thanks Brendan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
On Sun, 2012-07-15 at 19:58 +0200, Jan Kratochvil wrote: On Sun, 15 Jul 2012 19:37:26 +0200, Reindl Harald wrote: you must start openoffice damned often that the benfit beats out the overhead of the /etc/cron.daily/prelink When you prelink it nightly on AC and run it at least once on battery, the saving has been done. to beat the battery drain of /etc/cron.daily/prelink That prelink is being run on battery I repeat is a bug of cron. Definitely not a bug. If it is a bug of anything then of the prelink script that it does not check the battery status. Cron cannot know whether the script is lightweight and important enough to be run also on battery power or not. -- Tomas Mraz No matter how far down the wrong road you've gone, turn back. Turkish proverb -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Review swaps
Hello! 2012/7/16 Brendan Jones brendan.jones...@gmail.com: I took these: Add64 - an additive synthesizer for JACK https://bugzilla.redhat.com/show_bug.cgi?id=830664 samplv1 -A polyphonic sampler synthesizer with stereo fx https://bugzilla.redhat.com/show_bug.cgi?id=829971 It would be great if you review these Erlang-related packages in return: * https://bugzilla.redhat.com/823171 - erlang-eleveldb - Erlang LevelDB API * https://bugzilla.redhat.com/823101 - erlang-riak_pipe - Riak Pipelines Both have a set of unit-tests to check whether they are properly functioning and both builds cleanly in Rawhide. -- With best regards, Peter Lemenkov. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: packaging puppet modules
2012/6/27 Ken Dreyer ktdre...@ktdreyer.com I was looking briefly into packaging some Puppet modules, and I was curious if anyone else has gone down this road. [...] Does anyone have suggestions for package naming conventions? It looks like the upstream modules include the creators' names as part of the package names, which strikes me as a little verbose from the perspective of Fedora packaging. I don't think that it make much sense to pack the modules as RPMs. Under normal circumstances they must be customized in several different locations and would only produce a lot of *.rpmnew files after upgrades without proper function test possibilities. The more common way is to organize the modules in a VCS. Kind regards, Thomas -- Linux ... enjoy the ride! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
PackageKit soname bump
Hi all, I'm about to upload PackageKit 0.8.2 which bumps soname due to some removed API. I'll take care of rebuilding gnome-packagekit and apper. Yell if you have any worries or questions. Thanks. Richard. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
Miloslav Trmač writes: On Mon, Jul 16, 2012 at 4:20 AM, Sam Varshavchik mr...@courier-mta.com wrote: Chris Adams writes: Once upon a time, Sam Varshavchik mr...@courier-mta.com said: Chris Adams writes: Is there anything that actually does that and depends on the result? You skipped this part. Can you name something that tries this? I bet somebody can break it if so. When the code is ready, I'll name it, certainly, and I'll welcome anyone to attempt to break it. But that's just a sideshow. Whether something like this can or cannot be broken does not make what prelink does any more or less sensible. What prelink does in this respect is perfectly sensible. Being able to rename() over an executable that is running is a long-standing UNIX tradition, and prelink is only one of the manifestations of this. Not quite. Although renaming over an exe is certainly a tradition, it is not something that happens randomly, at no particular time. It's always a result of a controlled process, such as a scheduled upgrade. Prelink runs …whenever. I don't think there's a precedent for having some maintenance system process of randomly renaming over running executables that it has absolutely no relation to. primary concern is that UNIX just nowhere, never, authenticates executables - it authenticates identities attached to _running_ processes (UID, EUID, SELinux labels), it _never_ looks at the executable file after execve() happens. In particular, what good is it to know that a process was started by running $a_specific_inode, when the process might be under control of a ptracing parent, and might currently be executing a completely different code not present in that inode at all? I did not say that this is all of authentication. Sent credentials over the filesystem domain socket include not just the pid, but the userid and the groupid, of course. I think that 99% of the problems that prelink is creating can be easily avoided simply by having prelink automatically skip executables that are currently running. That would break prelink: 1) prelink would not prelink the most important executables, mostly defeating its purpose. 2) The regular prelink run re-randomizes the whole system, assigning non-conflicting addresses; without the ability to update all executables, some of the addresses would conflict and require run-time relocation, again defeating the purpose of prelink. That would be a valid concern, certainly. So, I suppose, it's either take prelink as it is, or not. There is apparently, no good solution to prelink arbitrarily renaming over an executable, and breaking the documented /proc API in proc(5), at any time. pgpJKG1kO6xaz.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: packaging puppet modules
On 16 July 2012 06:19, Thomas Bendler m...@bendler-net.de wrote: 2012/6/27 Ken Dreyer ktdre...@ktdreyer.com I was looking briefly into packaging some Puppet modules, and I was curious if anyone else has gone down this road. [...] Does anyone have suggestions for package naming conventions? It looks like the upstream modules include the creators' names as part of the package names, which strikes me as a little verbose from the perspective of Fedora packaging. I don't think that it make much sense to pack the modules as RPMs. Under normal circumstances they must be customized in several different locations and would only produce a lot of *.rpmnew files after upgrades without proper function test possibilities. The more common way is to organize the modules in a VCS. This isn't true in all cases. Well written modules shouldn't need customization for use. However, there's a vast array of modules available, with a lot of duplication in functionality, and certainly some would be helpful if packaged as RPMs. I have in mind here some of the puppetlabs modules which will become part of later releases of puppet, for example. As to the original question about naming, I don't think there's any alternative to including the creators' name inthe package name, since there's a lot of different implementations of modules providing similar functionality, and it's useful to know which you're installing. J. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 840453] New: perl-Test-Compile-0.18 is available
https://bugzilla.redhat.com/show_bug.cgi?id=840453 Bug ID: 840453 Keywords: FutureFeature, Triaged QA Contact: extras...@fedoraproject.org Severity: unspecified Version: rawhide Priority: unspecified CC: mmasl...@redhat.com, perl-de...@lists.fedoraproject.org Assignee: mmasl...@redhat.com Summary: perl-Test-Compile-0.18 is available Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: upstream-release-monitor...@fedoraproject.org Type: --- Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: perl-Test-Compile Product: Fedora Latest upstream release: 0.18 Current version in Fedora Rawhide: 0.17 URL: http://search.cpan.org/dist/Test-Compile/ 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. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: prelink should not mess with running executables
On Sun, Jul 15, 2012 at 08:46:06PM -0400, Sam Varshavchik wrote: Chris Adams writes: Once upon a time, Sam Varshavchik mr...@courier-mta.com said: I would expect that /proc/self/exe symlink gives the name of the running executable. I don't think it's an unreasonable expectation. There are lots of ways that can fail already; prelink is just one. Running yum update can break it as well (not every process is restarted in %post). Yes, but that can be controlled, by doing the right thing via all the rpm hooks. I suspect there is still a small race window, even if you've got the right %post hook. Does it need to be the same executable? Isn't it sufficient to check that it's the same user (ie. using SO_PEERCRED): http://www.perlmonks.org/?node_id=952805 Or perhaps something using SCM_RIGHTS/SCM_CREDENTIALS ... Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
On 07/15/2012 09:20 PM, Sam Varshavchik wrote: I think that 99% of the problems that prelink is creating can be easily avoided simply by having prelink automatically skip executables that are currently running. This is something that should not be very difficult to do. All the information is trivially obtainable from /proc/*/exe. That would mean that prelink would skip much of a running system, and a full prelink could be done only by booting from separate media. Not going to happen. -- Bob Nichols NOSPAM is really part of my email address. Do NOT delete it. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
On Mon, Jul 16, 2012 at 9:30 AM, Robert Nichols rnicholsnos...@comcast.net wrote: That would mean that prelink would skip much of a running system, and a full prelink could be done only by booting from separate media. Not going to happen. But now that Fedora will have reboot for updates... problem solved, right? :) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
On Sun, 2012-07-15 at 15:45 +0200, Jan Kratochvil wrote: On Sat, 14 Jul 2012 16:19:23 +0200, Sam Varshavchik wrote: It took me a while to figure out why my daemon kept breaking all the time, when it couldn't stat its /proc/self/exe any more. This is a bug of the daemon. While it is already suspicious it needs to mess with /proc/self/exe stat works for it even when it is already deleted: cp /usr/bin/perl /tmp/perlcopy;/tmp/perlcopy -MData::Dumper -le 'unlink /tmp/perlcopy;print Dumper stat,readlink for /proc/self/exe' $VAR1 = 18; [...] $VAR13 = 32; $VAR14 = '/tmp/perlcopy (deleted)'; On Sat, 14 Jul 2012 16:43:13 +0200, Reindl Harald wrote: it should be generally considered if prelink is useful at all on a distribution with high frequently updates This is a bug of yum, it should run prelink for any updated software. I'd be more inclined to say it's a bug in our rpm setup, in that we're not using collections yet to get rid of boilerplate crap like %post -p /sbin/ldconfig The feature's been there since rpm 4.9.0 (F15). Why aren't we using it yet? - ajax signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
Am 15.07.2012 19:58, schrieb Jan Kratochvil: On Sun, 15 Jul 2012 19:37:26 +0200, Reindl Harald wrote: you must start openoffice damned often that the benfit beats out the overhead of the /etc/cron.daily/prelink When you prelink it nightly on AC and run it at least once on battery, the saving has been done. in a perfect world to beat the battery drain of /etc/cron.daily/prelink That prelink is being run on battery I repeat is a bug of cron. it is NOT a bug of cron how do you imagine this in real life for a notebook user? in the night the machine is off, so most of the time when the machine is on AC prelink cron can not run and start it's job somewhere in the morining while the user works on his machine I had a script to disable such jobs automatically, I do it by hand nowadays. thank god taht this script is installed per default as prelink too and only 1 out of 1000 users has the knowledge how to disable it however, you said here it is a bug in prelink with other words the compiler optimizing is made one time on the buildserver I have considered developers now as we are on fedora-devel that was not the point because yu stripped it there is a huge difference between optimizing in the build-process and things running repeatly on all users machines as long they are not remove things by hand signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 839909] perl-YAML-0.84 is available
https://bugzilla.redhat.com/show_bug.cgi?id=839909 Petr Šabata psab...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-YAML-0.84-1.fc18 Resolution|--- |RAWHIDE Last Closed||2012-07-16 10:39:08 -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: prelink should not mess with running executables
On Mon, 16 Jul 2012 09:30:47 +0200, Tomas Mraz wrote: Definitely not a bug. If it is a bug of anything then of the prelink script that it does not check the battery status. OK, it depends whether you want to make some configuration of cron which scripts should or should not be run on battery or whether each script should decide on its own. So for the prelink script I have filed: https://bugzilla.redhat.com/show_bug.cgi?id=840557 Regards, Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: intel ipw2100/ipw2200 firmware must be removed
On Sun, Jul 15, 2012 at 09:41:26AM -0400, Al Dunsmuir wrote: On Saturday, July 14, 2012, 7:25:15 PM, Eric Smith wrote: Perhaps it means that the file can't be in a supported executable format such as ELF? Downloaded firmware often is in raw binary format, but it's certainly conceivable that some might be in ELF format. This topic has come up at regular intervals in the past, especially when the kernel interfaces for downloading firmware were being developed. The packaging statement is meant to clarify, and to be read literally. It means that the program is not a stand-alone program for use by the host computer. It requires additional hardware to operate. It is marked non-executable -x to prevent attempts to execute by the host computer (or for the security conscious, attempts to disguise malware as firmware). Normally firmware is a binary blob that is downloaded by the kernel to that hardware, and used in some manner by that hardware, It may be a program (code/data) executed by a CPU (or equivalent such as an ASIC) or some form of data required for execution of that hardware. It may be multiple of each, in a fancy wrapper scheme with CRCs. Delivering firmware via a standard kernel API was a big change a few years ago. It allowed standard packaging of firmware, and eliminated the need for users to do nasty things like use programs the cut the firmware images out of Windows PE executables downloaded from chip/card vendor websites. The encoding doesn't matter - what matters is that the content is automatically delivered to the hardware so that hardware can operate. What also matters is that the licence allow Fedora to freely distribute the firmware file, without silly restrictions such as non-commercial use only. Some folks object to Fedora shipping binary blobs, and insist that the only true way is to ship everything with source and build tools. That has been debated fiercely in the past... and the current rules were the IMO reasonable compromise that resulted. This seems to capture the spirit of what the Guidelines for binary firmware try to do. If anyone has wording that they think can make this more clear, feel free to submit it as a draft to the FPC at https://fedorahosted.org/fpc/newticket -Toshio pgpq6BHFdV3LZ.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
On Sun, 15 Jul 2012 22:42:00 +0200, Sam Varshavchik wrote: And I wouldn't be so presumptions as to state authoritatively what is or is not a bug, in something whose purpose is not known to me. Non-existing /proc/self/exe file is a normal UNIX process state so a UNIX process not being able to cope with it should be fixed. This is a bug of yum, it should run prelink for any updated software. This is an obvious yum issue, up to yum, I have not filed the yum Bug now. This is a bug of the intrusion detections software which should run documented way: prelink -u -o - /bin/bash | read the original binary This is a bug of cron, this problem affects me also for nightly updates and nightly build and regression testing jobs. After the mail with Tomas Mraz who does not want the fix placed into cron I have filed it for the prelink Fedora packaging: https://bugzilla.redhat.com/show_bug.cgi?id=840557 What would be the Bugzilla entries for all these bugs you've just discovered? I do not know what is the 'intrusion detections software' package so I cannot file a Bug for it. Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 839706] Review Request: perl-Time-Clock - Twenty-four hour clock object with nanosecond precision
https://bugzilla.redhat.com/show_bug.cgi?id=839706 Jitka Plesnikova jples...@redhat.com changed: What|Removed |Added Flags|fedora-review? |fedora-review+ --- Comment #3 from Jitka Plesnikova jples...@redhat.com --- Changes are ok. Package is APPROVED. -- You are receiving this mail because: You are on the CC list for the bug. -- 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
[Bug 839701] Review Request: perl-SQL-ReservedWords - Determine if words are reserved by ANSI/ISO SQL standard.
https://bugzilla.redhat.com/show_bug.cgi?id=839701 Bill Pemberton wf...@virginia.edu changed: What|Removed |Added Flags||fedora-cvs? --- Comment #4 from Bill Pemberton wf...@virginia.edu --- New Package SCM Request === Package Name: perl-SQL-ReservedWords Short Description: Determine if words are reserved by ANSI/ISO SQL standard Owners: wfp Branches: f16 f17 el6 InitialCC: perl-sig -- You are receiving this mail because: You are on the CC list for the bug. -- 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
[Bug 839706] Review Request: perl-Time-Clock - Twenty-four hour clock object with nanosecond precision
https://bugzilla.redhat.com/show_bug.cgi?id=839706 Bill Pemberton wf...@virginia.edu changed: What|Removed |Added Flags||fedora-cvs? --- Comment #4 from Bill Pemberton wf...@virginia.edu --- New Package SCM Request === Package Name: perl-Time-Clock Short Description: Twenty-four hour clock object with nanosecond precision Owners: wfp Branches: f16 f17 el6 InitialCC: perl-sig -- You are receiving this mail because: You are on the CC list for the bug. -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: prelink should not mess with running executables
On Mon, Jul 16, 2012 at 10:03:27AM -0400, Adam Jackson wrote: On Sun, 2012-07-15 at 15:45 +0200, Jan Kratochvil wrote: On Sat, 14 Jul 2012 16:19:23 +0200, Sam Varshavchik wrote: It took me a while to figure out why my daemon kept breaking all the time, when it couldn't stat its /proc/self/exe any more. This is a bug of the daemon. While it is already suspicious it needs to mess with /proc/self/exe stat works for it even when it is already deleted: cp /usr/bin/perl /tmp/perlcopy;/tmp/perlcopy -MData::Dumper -le 'unlink /tmp/perlcopy;print Dumper stat,readlink for /proc/self/exe' $VAR1 = 18; [...] $VAR13 = 32; $VAR14 = '/tmp/perlcopy (deleted)'; On Sat, 14 Jul 2012 16:43:13 +0200, Reindl Harald wrote: it should be generally considered if prelink is useful at all on a distribution with high frequently updates This is a bug of yum, it should run prelink for any updated software. I'd be more inclined to say it's a bug in our rpm setup, in that we're not using collections yet to get rid of boilerplate crap like %post -p /sbin/ldconfig The feature's been there since rpm 4.9.0 (F15). Why aren't we using it yet? http://meetbot.fedoraproject.org/fedora-meeting-1/2012-05-30/fpc.2012-05-30-16.00.log.html tibbs brought it up but spot thought that it wasn't turned on in our build of rpm because iirc, it would make the rpm format incompatible with older versions. I don't know if anyone followed up on this on the rpm-maint list. Reading the meeting log there, I'd say the FPC would welcome a draft on using rpm collections if they are in a workable state (with some possible questions of whether experimental is a workable state or not.) In terms of how the Guidelines would look, FPC would probably need to either work on the boilerplate that the collections code uses or link to them for the benefit of maintainers that want to maintain rpms in EPEL 5 and EPEL 6. -Toshio pgpDw4zZJw6nv.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
non-responsive
https://bugzilla.redhat.com/show_bug.cgi?id=831743 Maybe anyone knows how to contact the maintainer? (His mail is not answer.) -- Fl@sh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Upstream Release Monitoring status posting
Hi, I was asked to send to send the status of the last run of the Upstream Release Monitoring tool to this list. It would consist of all lines in http://till.fedorapeople.org/tmp/cnucnu-last.log that mention that a package is outdated. Would you welcome this or find it disturbing? I think it would be too noisy, because currently it will contain about 500 packages where some are bogus. Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Summary/Minutes from today's FESCo meeting (2012-07-16)
=== #fedora-meeting: FESCO (2012-07-16) === Meeting started by notting at 17:01:35 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2012-07-16/fesco.2012-07-16-17.01.log.html . Meeting summary --- * init process (notting, 17:01:50) * #889 Retire orphaned packages only after co-maintainers have been notified as it happens in the nonresponsive maintainers procedure (notting, 17:12:13) * AGREED: notting (or other person doing this task) will CC: comaintainers on orphan mails (notting, 17:20:29) * #890 F18 Feature: KDE Plasma Workspaces 4.9 - https://fedoraproject.org/wiki/Features/KDE49 (notting, 17:25:02) * AGREED: feature KDE Plasma Workspaces 4.9 is approved (+:6, -:0, 0:0) (notting, 17:27:09) * #891 F18 Feature: Eucalyptus - https://fedoraproject.org/wiki/Features/Eucalyptus (notting, 17:27:28) * AGREED: feature Eucalyptus is approved (+:6, -:0, 0:0) (notting, 17:29:42) * #892 F18 Feature: GNOME IBus Integration - https://fedoraproject.org/wiki/Features/GNOMEIBusIntegration (notting, 17:29:56) * postponed to next week (notting, 17:52:59) * #893 F18 Feature: GSS Proxy - https://fedoraproject.org/wiki/Features/gss-proxy (notting, 17:53:14) * AGREED: feature GSS Proxy is approved (+:6, -:0, 0:0) (notting, 18:00:10) * #894 F18 Feature: ibus-libpinyin - https://fedoraproject.org/wiki/Features/ibus-libpinyin (notting, 18:00:24) * AGREED: feature ibus-libpinyin is approved (+:6, -:0, 0:0) (notting, 18:02:22) * #895 F18 Feature: Ibus-Typing-Booster - https://fedoraproject.org/wiki/Features/Typing-Booster (notting, 18:02:35) * LINK: https://fedoraproject.org/wiki/Features/english-typing-booster (nirik, 18:05:12) * AGREED: feature Ibus-typing-booster is approved (+:6, -:0, 0:0) (notting, 18:06:36) * Open Floor (notting, 18:06:42) * mass rebuild for F-18 scheduled to start this week (Wednesday) (notting, 18:06:59) * see https://fedorahosted.org/fesco/ticket/896 for discussion on Fixing The Feature Process (notting, 18:16:43) Meeting ended at 18:18:20 UTC. Action Items Action Items, by person --- * **UNASSIGNED** * (none) People Present (lines said) --- * notting (73) * mitr (41) * nirik (33) * jwb (33) * t8m (20) * limburgher (17) * mclasen (15) * zodbot (11) * gd (7) * gholms (6) * drago01 (3) * abadger1999 (1) * pjones (1) * mmaslano (0) * mjg59 (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot 17:01:35 notting #startmeeting FESCO (2012-07-16) 17:01:35 zodbot Meeting started Mon Jul 16 17:01:35 2012 UTC. The chair is notting. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:35 zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:01:42 notting #meetingname fesco 17:01:42 zodbot The meeting name has been set to 'fesco' 17:01:50 notting #chair notting nirik mjg59 mmaslano t8m pjones mitr limburgher jwb 17:01:50 zodbot Current chairs: jwb limburgher mitr mjg59 mmaslano nirik notting pjones t8m 17:01:50 notting #topic init process 17:02:05 * nirik is here. 17:02:05 notting mjg59 and pjones will (theoretically) not be joining us today 17:02:19 mitr Hello 17:03:10 nirik limburgher may or may not be here. 17:03:32 notting heisenburgher? 17:03:43 gholms Heh 17:03:49 pjones yeah, really not here for this meeting. 17:04:59 t8m hello 17:05:34 * limburgher is or is not here 17:05:41 limburgher notting: +1 17:05:59 limburgher please try not to collapse my waveform. 17:06:13 t8m do not open the box 17:06:37 notting that's 5. jwb? 17:08:27 notting mmaslano was on holiday last week, and appears to be not around this week (still on holiday?) 17:10:06 mitr notting: should still be on PTO today 17:11:28 notting ok, that's 5 and jwb can join if he's around 17:12:13 notting #topic #889 Retire orphaned packages only after co-maintainers have been notified as it happens in the nonresponsive maintainers procedure 17:12:13 notting .fesco 889 17:12:18 zodbot notting: #889 (Retire orphaned packages only after co-maintainers have been notified as it happens in the nonresponsive maintainers procedure) – FESCo - https://fedorahosted.org/fesco/ticket/889 17:13:43 notting this is a request to at least notify comaintainers when we go through the orphan packages each release 17:13:52 notting as i've been doing this, i can do so unless people object 17:13:57 t8m +1 17:14:07 t8m I think it is reasonable request. 17:14:13 nirik the request seems to be to notify them as much as if they were unresponsive? 17:14:25 nirik ie, 3 weeks, a bug, a post to devel list, etc. 17:14:35 t8m I do not understand it like that. 17:14:54 notting i would prefer not to go through bugs - we have posts to devel list, and they can be informed as a cc/adjunct to that 17:14:58 nirik Therefore I suggest to
Re: prelink should not mess with running executables
On Mon, 2012-07-16 at 08:32 -0700, Toshio Kuratomi wrote: In terms of how the Guidelines would look, FPC would probably need to either work on the boilerplate that the collections code uses or link to them for the benefit of maintainers that want to maintain rpms in EPEL 5 and EPEL 6. It should mostly be a matter of moving various bits of magic out of scriptlets and into rpm macros, so I don't think there's much _new_ to document besides noting which releases no longer need scriptleting; and for that matter keeping many such scriptlets (like /sbin/ldconfig) is harmless, just inefficient. - ajax signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
On Mon, Jul 16, 2012 at 01:50:58PM -0400, Adam Jackson wrote: On Mon, 2012-07-16 at 08:32 -0700, Toshio Kuratomi wrote: In terms of how the Guidelines would look, FPC would probably need to either work on the boilerplate that the collections code uses or link to them for the benefit of maintainers that want to maintain rpms in EPEL 5 and EPEL 6. It should mostly be a matter of moving various bits of magic out of scriptlets and into rpm macros, so I don't think there's much _new_ to document besides noting which releases no longer need scriptleting; and for that matter keeping many such scriptlets (like /sbin/ldconfig) is harmless, just inefficient. I dunno. there's no documentation on how it works so I don't know what it would look like yet. (I'm guessing that in addition to the scriptlets, there also needs to be rules written that tell when the scriptlets need to be run. And the collections would need to inject the proper Requires(scriptlet): information into the rpn as well). -Toshio pgpc6Jv6hDFnJ.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[perl-SQL-ReservedWords/f16] Initial import (839701).
Summary of changes: 7c60d96... Initial import (839701). (*) (*) 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-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Time-Clock/f16] Initial import (839706).
Summary of changes: 6bac126... Initial import (839706). (*) (*) 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-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
gitweb-caching to cgit move
Greetings. Fedora infrastructure has been looking at moving from gitweb-caching to cgit for git.fedorahosted.org and pkgs.fedoraproject.org. Some reasons: gitweb-caching upstream is not very alive. gitweb-caching needs manual clearing of it's cache from time to time. gitweb-caching seems to run into security issues, and due to inactive upstream it's difficult to fix. gitweb-caching cannot handle the number of repos in pkgs.fedoraproject.org and doesn't display a useful top page. gitweb-caching seems to leave lingering old git-daemon processes around. cgit cleans up after itself. cgit can display the pkgs.fedoraproject.org repo collection (all be it if it's not cached currently it takes a while the first hit and splits pkgs into 248 pages). cgit seems to have a somewhat active upstream. cgit is faster. cgit displays UTF8, where gitweb-caching often doesn't. We have already pushed cgit live for folks to look at: http://git.fedorahosted.org/cgit/ and http://pkgs.fedoraproject.org/cgit/ We don't want to carry a ton of redirects/rewrites forever, so we were planning on just adding a few to go to the project if we can tell what that was/is and redirect the rest to the top level to use the search box. We would like to make this change on 2012-07-30, unless there's some show stopper found before then. In the mean time, if everyone could: - Move any scripts or processes you have that use a gitweb-caching url to using a cgit one. - Look over the interface(s) above and let us know (via a infrastructure ticket or #fedora-admin) if you run into a issue with them. Let us know if you have any other issues or concerns. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: gitweb-caching to cgit move
On Monday, July 16 2012, Kevin Fenzi wrote: cgit is faster. cgit seems great, but I am not sure it is faster. sergio@psique /tmp $ time wget 'http://pkgs.fedoraproject.org/gitweb/?p=gdb.git;a=blob;f=gdb-rhbz-818343-set-solib-absolute-prefix-testcase.patch;h=446709da043ef053ee3c65889bdb8438ca994aef;hb=HEAD' -O 1 ... real 0m0.810s user 0m0.000s sys0m0.004s sergio@psique /tmp $ time wget 'http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-rhbz-818343-set-solib-absolute-prefix-testcase.patch' -O 2 ... real 0m3.700s user 0m0.000s sys0m0.003s sergio@psique /tmp $ time wget 'http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-rhbz-818343-set-solib-absolute-prefix-testcase.patch' -O 2 ... real 0m3.489s user 0m0.001s sys0m0.009s I ran the last command twice to make sure. Not sure if I'm doing something wrong here... -- Sergio -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
Richard W.M. Jones writes: I suspect there is still a small race window, even if you've got the right %post hook. Does it need to be the same executable? Isn't it sufficient to check that it's the same user (ie. using SO_PEERCRED): http://www.perlmonks.org/?node_id=952805 Or perhaps something using SCM_RIGHTS/SCM_CREDENTIALS ... Well, SCM_RIGHTS/SCM_CREDENTIALS is how you get the peer's pid in the first place. This would be an additional check, on top of that. pgpH0X2Qir8p8.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
Gregory Maxwell writes: On Mon, Jul 16, 2012 at 9:30 AM, Robert Nichols rnicholsnos...@comcast.net wrote: That would mean that prelink would skip much of a running system, and a full prelink could be done only by booting from separate media. Not going to happen. But now that Fedora will have reboot for updates... problem solved, right? :) Snort. pgpApKPf96bky.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
Jan Kratochvil writes: On Sun, 15 Jul 2012 22:42:00 +0200, Sam Varshavchik wrote: And I wouldn't be so presumptions as to state authoritatively what is or is not a bug, in something whose purpose is not known to me. Non-existing /proc/self/exe file is a normal UNIX process state so a UNIX It is anything but normal. The normal state of things is documented by proc(5). As documented by that man page, rather plainly, readlink(/proc/self/exe) gives you your own pathname. That's the normal state of things, if normal means anything. When that no longer holds true, that's not normal. process not being able to cope with it should be fixed. Broken maintenance scripts, of dubiuous benefit, that randomly rewrite unrelated binaries, should be fixed. pgpuI5VUqcvki.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
security repo
Hi, list I don't want too many updates so I disable the updates repo. But later I found that fedora repo has no updates so I couldn't get any security updates. I think we can create a new repo called security like Debian. Push all the security updates to it. I believe that there are people like me disabled updates repo. They are very dangerous! Please review whether this is okay. Thanks! -- --- Regards, | 祝好 Mike Manilone http://www.ekd123.org --- signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
On Mon, Jul 16, 2012 at 07:38:52PM -0400, Sam Varshavchik wrote:
Jan Kratochvil writes:
On Sun, 15 Jul 2012 22:42:00 +0200, Sam Varshavchik wrote:
And I wouldn't be so presumptions as to state authoritatively what
is or is not a bug, in something whose purpose is not known to me.
Non-existing /proc/self/exe file is a normal UNIX process state so a UNIX
It is anything but normal. The normal state of things is
documented by proc(5). As documented by that man page, rather
plainly, readlink(/proc/self/exe) gives you your own pathname.
That's the normal state of things, if normal means anything.
When that no longer holds true, that's not normal.
And what's the pathname of a deleted file? Like it or not, that's a real
possibility (normal as opposed to the result of an error condition or
a bug), even if it's possibly not typical.
Well, let's see what happens:
$ echo 'int main() { while(1); }' foo.c
$ gcc foo.c
$ ./a.out
$ ls -ln /proc/$(jobs -p)/exe
lrwxrwxrwx. 1 1000 1000 0 Jul 16 20:27 /proc/7078/exe - /tmp/foo/a.out
$ rm a.out
$ ls -ln /proc/$(jobs -p)/exe
lrwxrwxrwx. 1 1000 1000 0 Jul 16 20:27 /proc/7078/exe - /tmp/foo/a.out
(deleted)
$ file /proc/$(jobs -p)/exe
/proc/7078/exe: symbolic link to `/tmp/foo/a.out (deleted)'
$ file -L /proc/$(jobs -p)/exe
/proc/7078/exe: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.32, not
stripped
$ kill %1
$ gcc foo.c
$ ./a.out
$ gcc foo.c
$ ls -ln /proc/$(jobs -p)/exe
lrwxrwxrwx. 1 1000 1000 0 Jul 16 20:41 /proc/7898/exe - /tmp/foo/a.out
(deleted)
$ kill %1
$ ./a.out
$ echo a a.out
bash: a.out: Text file busy
$ echo a a.out
bash: a.out: Text file busy
It gives you your current path name until that name no longer exists.
Then it tells you that your path is deleted (though you could also have
an executable ending in ' (deleted)'). If you access your file contents
via the link, you'll still get your original file contents.
That's the interface you've got. Playing around a bit, what it looks
like you want to do is open(/proc/self/exe, O_RDONLY), fstat the
resulting file descriptor, and use the device+inode to compare to the
other executables. The device+inode can't be reused while you're
executing, so you know that the other program is using the same
executable (but it still might not be you, since programs can run more
than once).
process not being able to cope with it should be fixed.
Broken maintenance scripts, of dubiuous benefit, that randomly
rewrite unrelated binaries, should be fixed.
Expecting every other program that manipulates/replaces files to cater
to your expectations is not reasonable unless you have 100% control over
everything that runs on your system (and take full responsibilty for
controlling it) and likewise for anyone else using the software. Even
then, the time would be better spent changing your software to use the
interface correctly (or use a more appropriate one) so you never have
problems.
--
Scott Schmit
smime.p7s
Description: S/MIME cryptographic signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Introduction: Interested in becoming a packager for fis-gtm and vista
Dear Fedora Devel, I'm interested in becoming a packager for: * fis-gtm: an open source implementation of the M/MUMPS language/database * vista: The EHR of the Department of Veterans Affairs I have been working recently with the upstream teams of these two projects while packaging them for the Debian Linux distribution, and would like to build on top of that packaging experience to bring both fis-gtm and vista into Fedora. VistA depends on fis-gtm being available. Therefore I'm first preparing the package for fis-gtm. I anticipate to be able to upload the fis-gtm package for review soon Thanks Luis --- More on my background Development work of ITK http://public.kitware.com/pub/itk/gitstat/ITK-2011-12-17/authors.html Blogs at Kitware http://www.kitware.com/blog/home/user/6 Blogs at OpenSource.com http://opensource.com/users/luis-ibanez Role is OSEHRA the project creating an open source environment for VistA. http://osehra.org/users/luisibanez The Open Source Software Practices class that we teach at RPI since 2007 http://www.opensourcesoftwarepractice.org/ Our upcoming presentation about VistA and OSEHRA at OSCON http://opensource.com/health/12/7/open-source-electronic-health-records-all-oscon-2012 http://www.oscon.com/oscon2012/public/schedule/detail/24129 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: security repo
On Tue, 17 Jul 2012, Mike Manilone wrote: I think we can create a new repo called security like Debian. Push all the security updates to it. Uhm, we have that. It is called RHEL Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: security repo
於 一，2012-07-16 於 18:00 -0700，Adam Williamson 提到： Updates are already categorized as 'security', 'bugfix' or 'feature'. You can isolate updates of each type in the GUI app, you can configure the system to automatically install 'security' updates but not other updates in the background. Well. I know they are categorized and I know there's a yum plugin called security... Must I use the GUI? gpk-update-viewer seems that it doesn't have this option. Maybe I forgot something? -- --- Regards, | 祝好 Mike Manilone http://www.ekd123.org --- signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
Scott Schmit writes: On Mon, Jul 16, 2012 at 07:38:52PM -0400, Sam Varshavchik wrote: Jan Kratochvil writes: On Sun, 15 Jul 2012 22:42:00 +0200, Sam Varshavchik wrote: And I wouldn't be so presumptions as to state authoritatively what is or is not a bug, in something whose purpose is not known to me. Non-existing /proc/self/exe file is a normal UNIX process state so a UNIX It is anything but normal. The normal state of things is documented by proc(5). As documented by that man page, rather plainly, readlink(/proc/self/exe) gives you your own pathname. That's the normal state of things, if normal means anything. When that no longer holds true, that's not normal. And what's the pathname of a deleted file? My point exactly. There is none. Thanks, prelink! ... That's the interface you've got. Playing around a bit, what it looks That's a very nice explanation. Unfortunately, all of these semantics are not under question. That's not the issue. like you want to do is open(/proc/self/exe, O_RDONLY), fstat the resulting file descriptor, and use the device+inode to compare to the other executables. Which will, of course, be different. Because prelink rewrote and renamed the executable. I'm not exactly sure what point you were trying to make, other than prelink being broken by design. The device+inode can't be reused while you're executing, so you know that the other program is using the same executable No, it's not using the same executable. The executable has been replaced by prelink, and the executable is now different, even though it is, really, the same executable. Nothing has been installed, or upgraded. Expecting every other program that manipulates/replaces files to cater to your expectations is not reasonable unless you have 100% control over everything that runs on your system (and take full responsibilty for controlling it) and likewise for anyone else using the software. True. That 100% control, of course, includes uninstalling the pest that keeps rewriting executables, any time it feels like it. Even then, the time would be better spent changing your software to use the interface correctly (or use a more appropriate one) so you never have problems. Can you explain, then, the correctly approach by which an executable can affirm whether another pid is either running the same executable, or the post-prelinked version of the same executable. Anyone who suggests readlink- ing /proc/self/exe, then the other /proc/pid/exe, and comparing them sans any hardcoded (deleted) suffix is going to get only howls of laughter, in response. P.S. I have an internal betting pool going on when some top gun offers a suggestion of running prelink --verify on both exe-s (since you can still open a (deleted) exe, inexplicably, even though the actual symlink points to nowhere), and comparing the results. P.P.S. And I'm still trying to process the concept of a symbolic link pointing to a non-existent pathname; yet an open() on that somehow succeeds, nevertheless. That's one a headscratcher, even though I'm told that's how UNIX worked for decades. You always learn something new. pgpcYBIipGSue.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: prelink should not mess with running executables
On Mon, Jul 16, 2012 at 5:45 PM, Scott Schmit i.g...@comcast.net wrote: And what's the pathname of a deleted file? Like it or not, that's a real possibility (normal as opposed to the result of an error condition or a bug), even if it's possibly not typical. [details snipped] It gives you your current path name until that name no longer exists. Then it tells you that your path is deleted (though you could also have an executable ending in ' (deleted)'). If you access your file contents via the link, you'll still get your original file contents. Thanks for the removal and recompile/replace examples. These clear it up for me. -jef -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Introduction: Interested in becoming a packager for fis-gtm and vista
Coincidentally I was looking at gtm this weekend. One of the interesting points in re packaging it is that one must bootstrap gtm from an existing gtm using the providing source. I'm wondering a bit how that might be affected by the Fedora packaging guidelines? I also use Intersystems cache (non free in every sense of course) although also Mumps based even if broken under F16/F17. There's also a seeming FOSS mumpsc compiler out there. Clive (an old Pick-ie in fact) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Bug 839706] Review Request: perl-Time-Clock - Twenty-four hour clock object with nanosecond precision
https://bugzilla.redhat.com/show_bug.cgi?id=839706 Jitka Plesnikova jples...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC||jples...@redhat.com Assignee|nob...@fedoraproject.org|jples...@redhat.com Flags||fedora-review? -- You are receiving this mail because: You are on the CC list for the bug. -- 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 480129] Error at calling service amavisd restart when SELinux is in enforce mode
https://bugzilla.redhat.com/show_bug.cgi?id=480129 Milos Malik mma...@redhat.com changed: What|Removed |Added QA Contact|qe-baseos-security@redhat.c |mma...@redhat.com |om | -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839701] Review Request: perl-SQL-ReservedWords - Determine if words are reserved by ANSI/ISO SQL standard.
https://bugzilla.redhat.com/show_bug.cgi?id=839701 Jitka Plesnikova jples...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC||jples...@redhat.com Assignee|nob...@fedoraproject.org|jples...@redhat.com Flags||fedora-review? -- You are receiving this mail because: You are on the CC list for the bug. -- 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 840449] New: perl-Config-Properties-1.75 is available
https://bugzilla.redhat.com/show_bug.cgi?id=840449 Bug ID: 840449 Keywords: FutureFeature, Triaged QA Contact: extras...@fedoraproject.org Severity: unspecified Version: rawhide Priority: unspecified CC: perl-devel@lists.fedoraproject.org, xav...@bachelot.org Assignee: xav...@bachelot.org Summary: perl-Config-Properties-1.75 is available Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: upstream-release-monitor...@fedoraproject.org Type: --- Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: perl-Config-Properties Product: Fedora Latest upstream release: 1.75 Current version in Fedora Rawhide: 1.73 URL: http://search.cpan.org/dist/Config-Properties/ 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. -- 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 840451] New: perl-Module-Manifest-Skip-0.17 is available
https://bugzilla.redhat.com/show_bug.cgi?id=840451 Bug ID: 840451 Keywords: FutureFeature, Triaged QA Contact: extras...@fedoraproject.org Severity: unspecified Version: rawhide Priority: unspecified CC: mmasl...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Assignee: ppi...@redhat.com Summary: perl-Module-Manifest-Skip-0.17 is available Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: upstream-release-monitor...@fedoraproject.org Type: --- Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: perl-Module-Manifest-Skip Product: Fedora Latest upstream release: 0.17 Current version in Fedora Rawhide: 0.16 URL: http://search.cpan.org/dist/Module-Manifest-Skip/ 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. -- 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 840452] New: perl-MooseX-AttributeShortcuts-0.013 is available
https://bugzilla.redhat.com/show_bug.cgi?id=840452 Bug ID: 840452 Keywords: FutureFeature, Triaged QA Contact: extras...@fedoraproject.org Severity: unspecified Version: rawhide Priority: unspecified CC: mmasl...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Assignee: ppi...@redhat.com Summary: perl-MooseX-AttributeShortcuts-0.013 is available Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: upstream-release-monitor...@fedoraproject.org Type: --- Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: perl-MooseX-AttributeShortcuts Product: Fedora Latest upstream release: 0.013 Current version in Fedora Rawhide: 0.010 URL: http://search.cpan.org/dist/MooseX-AttributeShortcuts/ 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. -- 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-1.fc17.x86_64 requires perl(:MODULE_COMPAT_5.14.2) On i386: perl-PDL-2.4.10-1.fc17.i686 requires perl(:MODULE_COMPAT_5.14.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-Class-InsideOut
perl-Class-InsideOut has broken dependencies in the rawhide tree: On x86_64: perl-Class-InsideOut-1.10-6.fc17.noarch requires perl(:MODULE_COMPAT_5.14.2) On i386: perl-Class-InsideOut-1.10-6.fc17.noarch requires perl(:MODULE_COMPAT_5.14.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
[Bug 840453] perl-Test-Compile-0.18 is available
https://bugzilla.redhat.com/show_bug.cgi?id=840453 Jitka Plesnikova jples...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC||jples...@redhat.com Assignee|mmasl...@redhat.com |jples...@redhat.com -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839909] perl-YAML-0.84 is available
https://bugzilla.redhat.com/show_bug.cgi?id=839909 Petr Šabata psab...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC||psab...@redhat.com Assignee|st...@silug.org |psab...@redhat.com -- You are receiving this mail because: You are on the CC list for the bug. -- 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 Test-Compile-0.18.tar.gz uploaded to lookaside cache by jplesnik
A file has been added to the lookaside cache for perl-Test-Compile: f3c853bb25452580860778cd6b2213fb Test-Compile-0.18.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-Test-Compile] Update to 0.18
commit cc5120ab27cf2fffa9a3a90bf59ccb3ff3d7ec39
Author: Jitka Plesnikova jples...@redhat.com
Date: Mon Jul 16 15:19:25 2012 +0200
Update to 0.18
.gitignore |1 +
perl-Test-Compile.spec |7 +--
sources|2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 4797b9f..598f0cf 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@ Test-Compile-0.13.tar.gz
/Test-Compile-0.15.tar.gz
/Test-Compile-0.16.tar.gz
/Test-Compile-0.17.tar.gz
+/Test-Compile-0.18.tar.gz
diff --git a/perl-Test-Compile.spec b/perl-Test-Compile.spec
index a9164be..4268aab 100644
--- a/perl-Test-Compile.spec
+++ b/perl-Test-Compile.spec
@@ -1,6 +1,6 @@
Name: perl-Test-Compile
-Version:0.17
-Release:2%{?dist}
+Version:0.18
+Release:1%{?dist}
Summary:Check whether Perl module files compile correctly
License:GPL+ or Artistic
Group: Development/Libraries
@@ -46,6 +46,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Mon Jul 16 2012 Jitka Plesnikova jples...@redhat.com - 0.18-1
+- 0.18 bump
+
* Tue Jun 12 2012 Petr Pisar ppi...@redhat.com - 0.17-2
- Perl 5.16 rebuild
diff --git a/sources b/sources
index b1e4fe9..e0f92eb 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-a23529083ab4ba9edeea8fda71eb7512 Test-Compile-0.17.tar.gz
+f3c853bb25452580860778cd6b2213fb Test-Compile-0.18.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 840453] perl-Test-Compile-0.18 is available
https://bugzilla.redhat.com/show_bug.cgi?id=840453 Jitka Plesnikova jples...@redhat.com changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Test-Compile-0.18-1.fc ||18 Resolution|--- |RAWHIDE Last Closed||2012-07-16 09:28:12 -- You are receiving this mail because: You are on the CC list for the bug. -- 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 840451] perl-Module-Manifest-Skip-0.17 is available
https://bugzilla.redhat.com/show_bug.cgi?id=840451 Jitka Plesnikova jples...@redhat.com changed: What|Removed |Added Status|NEW |ASSIGNED CC||jples...@redhat.com Assignee|ppi...@redhat.com |jples...@redhat.com -- You are receiving this mail because: You are on the CC list for the bug. -- 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 840523] New: please update to latest upstream version
https://bugzilla.redhat.com/show_bug.cgi?id=840523 Bug ID: 840523 Blocks: 840451 QA Contact: extras...@fedoraproject.org Severity: unspecified Version: rawhide Priority: unspecified CC: iarn...@gmail.com, perl-devel@lists.fedoraproject.org Assignee: iarn...@gmail.com Summary: please update to latest upstream version Regression: --- Story Points: --- Classification: Fedora OS: Linux Reporter: jples...@redhat.com Type: Bug Documentation: --- Hardware: All Mount Type: --- Status: NEW Component: perl-Moo Product: Fedora Please update perl-Moo to latest upstream version 0.091014. I want to update perl-Module-Manifest-Skip, but it requires version 0.091013 or higher. -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839701] Review Request: perl-SQL-ReservedWords - Determine if words are reserved by ANSI/ISO SQL standard.
https://bugzilla.redhat.com/show_bug.cgi?id=839701 --- Comment #2 from Bill Pemberton wf...@virginia.edu --- Updated to address above comments: Spec URL: http://wfp.fedorapeople.org/perl-SQL-ReservedWords.spec SRPM URL: http://wfp.fedorapeople.org/perl-SQL-ReservedWords-0.7-3.fc17.src.rpm -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839706] Review Request: perl-Time-Clock - Twenty-four hour clock object with nanosecond precision
https://bugzilla.redhat.com/show_bug.cgi?id=839706 --- Comment #2 from Bill Pemberton wf...@virginia.edu --- Updated to address above comments: Spec URL: http://wfp.fedorapeople.org/perl-Time-Clock.spec SRPM URL: http://wfp.fedorapeople.org/perl-Time-Clock-1.02-4.fc17.src.rpm -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839742] Review Request: perl-Rose-Object - Simple object base class
https://bugzilla.redhat.com/show_bug.cgi?id=839742 --- Comment #2 from Bill Pemberton wf...@virginia.edu --- Updated: Spec URL: http://wfp.fedorapeople.org/perl-Rose-Object.spec SRPM URL: http://wfp.fedorapeople.org/perl-Rose-Object-0.859-4.fc17.src.rpm -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839744] Review Request: perl-Rose-DateTime - DateTime helper functions and objects
https://bugzilla.redhat.com/show_bug.cgi?id=839744 --- Comment #1 from Bill Pemberton wf...@virginia.edu --- Updated: Spec URL: http://wfp.fedorapeople.org/perl-Rose-DateTime.spec SRPM URL: http://wfp.fedorapeople.org/perl-Rose-DateTime-0.537-3.fc17.src.rpm -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839751] Review Request: perl-Rose-DB - DBI wrapper and abstraction layer
https://bugzilla.redhat.com/show_bug.cgi?id=839751 --- Comment #1 from Bill Pemberton wf...@virginia.edu --- Updated: Spec URL: http://wfp.fedorapeople.org/perl-Rose-DB.spec SRPM URL: http://wfp.fedorapeople.org/perl-Rose-DB-0.769-4.fc17.src.rpm -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839701] Review Request: perl-SQL-ReservedWords - Determine if words are reserved by ANSI/ISO SQL standard.
https://bugzilla.redhat.com/show_bug.cgi?id=839701 Jitka Plesnikova jples...@redhat.com changed: What|Removed |Added Flags|fedora-review? |fedora-review+ --- Comment #3 from Jitka Plesnikova jples...@redhat.com --- Changes are ok. I have only one more thing. Please add the comment with link of bug before the Patch0. Just to know what it is fixing. Please update the spec before you commit it. Package is APPROVED. -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839701] Review Request: perl-SQL-ReservedWords - Determine if words are reserved by ANSI/ISO SQL standard.
https://bugzilla.redhat.com/show_bug.cgi?id=839701 --- Comment #5 from Jon Ciesla limburg...@gmail.com --- Git done (by process-git-requests). -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839706] Review Request: perl-Time-Clock - Twenty-four hour clock object with nanosecond precision
https://bugzilla.redhat.com/show_bug.cgi?id=839706 --- Comment #5 from Jon Ciesla limburg...@gmail.com --- Git done (by process-git-requests). -- You are receiving this mail because: You are on the CC list for the bug. -- 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-Clock/el6] Initial import (839706).
Summary of changes: 6bac126... Initial import (839706). (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-SQL-ReservedWords/f17] Initial import (839701).
Summary of changes: 7c60d96... Initial import (839701). (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-Time-Clock/f17] Initial import (839706).
Summary of changes: 6bac126... Initial import (839706). (*) (*) 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 839701] Review Request: perl-SQL-ReservedWords - Determine if words are reserved by ANSI/ISO SQL standard.
https://bugzilla.redhat.com/show_bug.cgi?id=839701 --- Comment #6 from Fedora Update System upda...@fedoraproject.org --- perl-SQL-ReservedWords-0.7-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/perl-SQL-ReservedWords-0.7-4.fc16 -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839701] Review Request: perl-SQL-ReservedWords - Determine if words are reserved by ANSI/ISO SQL standard.
https://bugzilla.redhat.com/show_bug.cgi?id=839701 --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- perl-SQL-ReservedWords-0.7-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/perl-SQL-ReservedWords-0.7-4.fc17 -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839701] Review Request: perl-SQL-ReservedWords - Determine if words are reserved by ANSI/ISO SQL standard.
https://bugzilla.redhat.com/show_bug.cgi?id=839701 --- Comment #8 from Fedora Update System upda...@fedoraproject.org --- perl-SQL-ReservedWords-0.7-4.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/perl-SQL-ReservedWords-0.7-4.el6 -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839706] Review Request: perl-Time-Clock - Twenty-four hour clock object with nanosecond precision
https://bugzilla.redhat.com/show_bug.cgi?id=839706 --- Comment #6 from Fedora Update System upda...@fedoraproject.org --- perl-Time-Clock-1.02-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/perl-Time-Clock-1.02-4.fc16 -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839706] Review Request: perl-Time-Clock - Twenty-four hour clock object with nanosecond precision
https://bugzilla.redhat.com/show_bug.cgi?id=839706 --- Comment #7 from Fedora Update System upda...@fedoraproject.org --- perl-Time-Clock-1.02-4.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/perl-Time-Clock-1.02-4.el6 -- You are receiving this mail because: You are on the CC list for the bug. -- 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 839706] Review Request: perl-Time-Clock - Twenty-four hour clock object with nanosecond precision
https://bugzilla.redhat.com/show_bug.cgi?id=839706 --- Comment #8 from Fedora Update System upda...@fedoraproject.org --- perl-Time-Clock-1.02-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/perl-Time-Clock-1.02-4.fc17 -- You are receiving this mail because: You are on the CC list for the bug. -- 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 Config-Properties-1.75.tar.gz uploaded to lookaside cache by xavierb
A file has been added to the lookaside cache for perl-Config-Properties: 10012d80fbb6cd7ec4f1a0eec1ead45f Config-Properties-1.75.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-Config-Properties] update to 1.75
commit 5dd8ce9de707ad3ba71d95b1f5428fa32e2de254
Author: Xavier Bachelot xav...@bachelot.org
Date: Tue Jul 17 00:57:22 2012 +0200
update to 1.75
.gitignore |1 +
perl-Config-Properties.spec |7 +--
sources |2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 51881a5..ab2ad7f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@ Config-Properties-1.70.tar.gz
/Config-Properties-1.71.tar.gz
/Config-Properties-1.72.tar.gz
/Config-Properties-1.73.tar.gz
+/Config-Properties-1.75.tar.gz
diff --git a/perl-Config-Properties.spec b/perl-Config-Properties.spec
index 5fff44c..c5bef37 100644
--- a/perl-Config-Properties.spec
+++ b/perl-Config-Properties.spec
@@ -1,6 +1,6 @@
Name: perl-Config-Properties
-Version:1.73
-Release:3%{?dist}
+Version:1.75
+Release:1%{?dist}
Summary:Read and write property files
License:GPL+ or Artistic
Group: Development/Libraries
@@ -58,6 +58,9 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/man3/*
%changelog
+* Mon Jul 16 2012 Xavier Bachelot xav...@bachelot.org 1.75-1
+- Update to 1.75.
+
* Tue Jun 12 2012 Petr Pisar ppi...@redhat.com - 1.73-3
- Perl 5.16 rebuild
diff --git a/sources b/sources
index 3404519..7da6d44 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-93287453dc21296cc5dfdaccecafec00 Config-Properties-1.73.tar.gz
+10012d80fbb6cd7ec4f1a0eec1ead45f Config-Properties-1.75.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 840449] perl-Config-Properties-1.75 is available
https://bugzilla.redhat.com/show_bug.cgi?id=840449 Xavier Bachelot xav...@bachelot.org changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |RAWHIDE Last Closed||2012-07-16 19:05:59 -- You are receiving this mail because: You are on the CC list for the bug. -- 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
