Re: fedpkg / koji error

[Thorsten Leemhuis]

Lo!

On 09.10.2012 20:03, Jesse Keating wrote:
 On 10/09/2012 07:14 AM, Simone Caronni wrote:
 On 19 September 2012 00:26, Orion Poplawski or...@cora.nwra.com wrote:
 On 09/05/2012 08:07 PM, Tom Callaway wrote:
 Jesse, I'm not sure if you're still the correct upstream here, please
 correct me if you're not, and I'll send the patch somewhere else.
 This helps me a lot as well building el srpms from master with fedpkg
 --dist el6 srpm.  +1 from me.
 Any news regarding this? Is the patch planned to be included?
 I don't see any activity in git: http://git.fedorahosted.org/cgit/fedpkg.git/
 Oops.  I dropped the ball.  Spot even pinged me about it and I made a 
 promise I didn't keep.  Rectifying.

Patch was integrated and a updated fedpkg is in updates-testing
currently -- which leads to wayland support in mesa.spec being not build
when you build it with fedpkg, as it contains this %configure statement:

 --with-egl-platforms=x11,drm%{!?rhel:,wayland} \

The ,wayland is not added, as rhel is defined now as 0 when building
with fedpgk. If you build a srpm and try to build it with rpmbuild then
it works, as it's not defined there. I explained it in more detail in
https://bugzilla.redhat.com/show_bug.cgi?id=867375 , which made me
brining up the issue here, as Jesse was unsure how to proceed.

I'd say the current behaviour is the quite bad, as it leads to different
results when building with fedpkg and rpmbuild on F18. The real fix
afaics would be to revert the change and, if wanted, define rhel as 0 in
Fedora's redhat-rpm-config, too -- but then we obviously need to fix all
%{!?rhel:foo} statements in current spec files.

Options? Spot, Simone?

CU
knurd
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Enrico Scholz]

Matthew Miller mat...@fedoraproject.org writes:

   - don't auto-page;

yes; that's the best solution.  The auto-pager is perhaps the most
annoying feature of systemd.  I have no problem in scrolling back some
pages in my terminal with shift-pgup, but having a status request block
(plain 'systemctl' or 'journalctl' request a status) is just broken.

Or, do you want that e.g. the 'ls -l' output gets auto-paged?


I disabled it be setting an empty SYSTEMD_PAGER on my systems; but this
breaks piping into a pager.

E.g. 'systemctl | less -S' or 'journalctl | less -S' is useless because
most information were removed.  I have to remember non-consistent
options now, e.g. 'systemctl -a' has a complete different meaning than
'journalctl -a'.


Hence, the systemd tools should follow Unix/Linux tradition and specialize
on their core functionality and avoid implementing features breaking
user experience.  There are other tools like 'less' which are much better
suited for paging program output and concepts like pipes are well known
and used at thousands of other places.



Enrico

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

[Bug 857845] perl-DateTime-TimeZone-1.51 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=857845

Upstream Release Monitoring upstream-release-monitor...@fedoraproject.org 
changed:

   What|Removed |Added

Summary|perl-DateTime-TimeZone-1.50 |perl-DateTime-TimeZone-1.51
   |is available|is available

-- 
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 857845] perl-DateTime-TimeZone-1.51 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=857845

--- Comment #1 from Upstream Release Monitoring 
upstream-release-monitor...@fedoraproject.org ---
Latest upstream release: 1.51
Current version in Fedora Rawhide: 1.49
URL: http://search.cpan.org/dist/DateTime-TimeZone/

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: fedpkg / koji error

[Simone Caronni]

Hello,

On 18 October 2012 09:57, Thorsten Leemhuis fed...@leemhuis.info wrote:

  --with-egl-platforms=x11,drm%{!?rhel:,wayland} \

 The ,wayland is not added, as rhel is defined now as 0 when building
 with fedpgk. If you build a srpm and try to build it with rpmbuild then
 it works, as it's not defined there. I explained it in more detail in
 https://bugzilla.redhat.com/show_bug.cgi?id=867375 , which made me
 brining up the issue here, as Jesse was unsure how to proceed.


Can't you check that rhel is not defined and different than 0? Something
like the following. It is untested as I don't have commit access; but at
least fedpkg prep on the mesa clone does not give me any error.

$ git diff
diff --git a/mesa.spec b/mesa.spec
index 150a5bc..a61185c 100644
--- a/mesa.spec
+++ b/mesa.spec
@@ -302,7 +302,7 @@ export CXXFLAGS=$RPM_OPT_FLAGS
 --enable-gles1 \
 --enable-gles2 \
 --disable-gallium-egl \
---with-egl-platforms=x11,drm%{!?rhel:,wayland} \
+--with-egl-platforms=x11,drm%{!0%{?rhel}:,wayland} \
 --enable-shared-glapi \
 --enable-gbm \
 %if %{with_hardware}

Or since you are using already the %if statements elsewhere you can add
another one with the 2 different config lines,  like

$ git diff
diff --git a/mesa.spec b/mesa.spec
index 150a5bc..764449a 100644
--- a/mesa.spec
+++ b/mesa.spec
@@ -302,7 +302,11 @@ export CXXFLAGS=$RPM_OPT_FLAGS
 --enable-gles1 \
 --enable-gles2 \
 --disable-gallium-egl \
---with-egl-platforms=x11,drm%{!?rhel:,wayland} \
+%if 0%{?rhel}
+--with-egl-platforms=x11,drm} \
+%else
+--with-egl-platforms=x11,drm,wayland} \
+%endif
 --enable-shared-glapi \
 --enable-gbm \
 %if %{with_hardware}

The packaging guidelines say that a 0 should be used when checking for
conditions:

http://fedoraproject.org/wiki/Packaging:DistTag

I'd say the current behaviour is the quite bad, as it leads to different
 results when building with fedpkg and rpmbuild on F18. The real fix
 afaics would be to revert the change and, if wanted, define rhel as 0 in
 Fedora's redhat-rpm-config, too -- but then we obviously need to fix all
 %{!?rhel:foo} statements in current spec files.


With the old one I had to check like this (first line) for building; which
is not correct anyway as the behaviour was different as well between fedpkg
and rpmbuild/mock:

-%if (0%{?fedora} == 16 || 0%{?fedora} == 17)  !0%{?rhel}
+%if 0%{?fedora} == 16 || 0%{?fedora} == 17

Regards,
--Simone

-- 
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: What are reasonable blockers for making journald the default logger in F19?

[Benny Amorsen]

Lennart Poettering mzerq...@0pointer.de writes:

 One way to achieve that should be to provide /var/log/README with the
 appropriate hints, since I assume much more people will look for logs
 in /var/log like it used to be in most of Linux history rather than in
 a tool logread that is known by an embedded distro by the name of
 OpenWRT...

You do have a way with words. I did not propose logread because it is
used by OpenWRT, I proposed it because it is a sane name.

When I read logs, I do not want to control a journal, that is for
tune2fs to do.

And documentation in /var/log? Seriously?


/Benny
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: What are reasonable blockers for making journald the default logger in F19?

[Miloslav Trmač]

On Wed, Oct 17, 2012 at 10:01 PM, Andrew Schultz ajsch...@verizon.net wrote:
 Additionally, it maybe useful to log this information for intrusion
 detection and correlation.

 Again, you don't need to know that the attacker guessed a username of bob.
 You simply need to recognize that N attempts were made to log in with
 unknown usernames during some time period.

A few years ago, I was a sysadmin of a computer that was compromised
by guessing a password of an user account.  It was extremely useful to
have the log of which specific user names were attempted, because
these were not random user names from a dictionary, but names of
employees of the institution in question - and could even indicate the
department which owned the other compromised computer.
Mirek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: fedpkg / koji error

[Thorsten Leemhuis]

On 18.10.2012 10:45, Simone Caronni wrote:
 On 18 October 2012 09:57, Thorsten Leemhuis fed...@leemhuis.info
 mailto:fed...@leemhuis.info wrote:
  --with-egl-platforms=x11,drm%{!?rhel:,wayland} \
 The ,wayland is not added, as rhel is defined now as 0 when building
 with fedpgk. If you build a srpm and try to build it with rpmbuild then
 it works, as it's not defined there. I explained it in more detail in
 https://bugzilla.redhat.com/show_bug.cgi?id=867375 , which made me
 brining up the issue here, as Jesse was unsure how to proceed.
 Can't you

Just for completeness: Mesa isn't my package. I just build a modified
version locally when I ran into trouble that lead to the bug I mentioned.

 check that rhel is not defined and different than 0?

That's obviously possible.

 The packaging guidelines say that a 0 should be used when checking for
 conditions:

But sometimes people do things wrong :-/ If we define rhel as 0 in
redhat-rpm-config then people will notice this case immediately themselves.

 With the old one I had to check like this (first line) for building;
 which is not correct anyway as the behaviour was different as well
 between fedpkg and rpmbuild/mock: [...]

And that should not be the case imho. But if we define rhel as 0 in
redhat-rpm-config instead (or in addition?) of fedpgk, then your case
should remain fixed as well -- or am I missing something?

Cu
knurd
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

F-18 Branched report: 20121018 changes

[Fedora Branched Report]

Compose started at Thu Oct 18 09:15:36 UTC 2012

Broken deps for x86_64
--
[almanah]
almanah-0.8.0-7.fc18.x86_64 requires libedataserverui-3.0.so.3()(64bit)
almanah-0.8.0-7.fc18.x86_64 requires libedataserver-1.2.so.16()(64bit)
almanah-0.8.0-7.fc18.x86_64 requires libecal-1.2.so.12()(64bit)
almanah-0.8.0-7.fc18.x86_64 requires libebook-1.2.so.13()(64bit)
[dhcp-forwarder]
dhcp-forwarder-upstart-0.10-1801.fc18.noarch requires /sbin/initctl
[dustmite]
dustmite-1-5.20120304gitcde46e0.fc17.x86_64 requires 
libphobos-ldc.so.59()(64bit)
[epiphany-extensions]
epiphany-extensions-3.5.0-0.2.20120914gitf4fcbfc.fc18.x86_64 requires 
epiphany(abi) = 0:3.5
[evolution-exchange]
evolution-exchange-3.5.2-1.fc18.x86_64 requires 
libedataserverui-3.0.so.3()(64bit)
evolution-exchange-3.5.2-1.fc18.x86_64 requires 
libedataserver-1.2.so.16()(64bit)
evolution-exchange-3.5.2-1.fc18.x86_64 requires 
libedata-cal-1.2.so.17()(64bit)
evolution-exchange-3.5.2-1.fc18.x86_64 requires 
libedata-book-1.2.so.14()(64bit)
evolution-exchange-3.5.2-1.fc18.x86_64 requires 
libecal-1.2.so.12()(64bit)
evolution-exchange-3.5.2-1.fc18.x86_64 requires 
libebook-1.2.so.13()(64bit)
evolution-exchange-3.5.2-1.fc18.x86_64 requires 
libebackend-1.2.so.3()(64bit)
evolution-exchange-3.5.2-1.fc18.x86_64 requires 
libcamel-1.2.so.36()(64bit)
[fedmsg]
fedmsg-0.5.4-4.fc18.noarch requires python-moksha-hub = 0:1.0.1
[flush]
flush-0.9.10-7.fc18.x86_64 requires 
libboost_thread-mt.so.1.48.0()(64bit)
flush-0.9.10-7.fc18.x86_64 requires 
libboost_system-mt.so.1.48.0()(64bit)
flush-0.9.10-7.fc18.x86_64 requires 
libboost_signals-mt.so.1.48.0()(64bit)
flush-0.9.10-7.fc18.x86_64 requires 
libboost_filesystem-mt.so.1.48.0()(64bit)
[func]
func-0.28-1.fc17.noarch requires smolt
[gcc-python-plugin]
gcc-python2-debug-plugin-0.9-5.fc18.x86_64 requires gcc = 0:4.7.2-2.fc18
gcc-python2-plugin-0.9-5.fc18.x86_64 requires gcc = 0:4.7.2-2.fc18
gcc-python3-debug-plugin-0.9-5.fc18.x86_64 requires gcc = 0:4.7.2-2.fc18
gcc-python3-plugin-0.9-5.fc18.x86_64 requires gcc = 0:4.7.2-2.fc18
[gdb-heap]
gdb-heap-0.5-9.fc18.x86_64 requires glibc(x86-64) = 0:2.15
[glom]
glom-1.18.6-1.fc17.x86_64 requires libboost_python.so.1.48.0()(64bit)
glom-libs-1.18.6-1.fc17.i686 requires libboost_python.so.1.48.0
glom-libs-1.18.6-1.fc17.x86_64 requires 
libboost_python.so.1.48.0()(64bit)
[gnome-do-plugins]
gnome-do-plugins-banshee-0.8.4-10.fc18.x86_64 requires 
mono(Banshee.CollectionIndexer) = 0:2.4.0.0
[gnome-pilot]
gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires 
libedataserverui-3.0.so.1()(64bit)
gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires 
libedataserver-1.2.so.16()(64bit)
gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires 
libecal-1.2.so.11()(64bit)
gnome-pilot-eds-2.91.93-5.fc17.x86_64 requires 
libebook-1.2.so.13()(64bit)
[gnome-shell-theme-selene]
gnome-shell-theme-selene-3.4.0-5.fc18.noarch requires 
gnome-shell-extensions-user-theme
[gwibber]
1:gwibber-3.4.2-3.fc18.i686 requires libgee-0.8.so.0
1:gwibber-3.4.2-3.fc18.x86_64 requires libgee-0.8.so.0()(64bit)
[ip-sentinel]
ip-sentinel-upstart-0.12-1303.fc18.noarch requires /sbin/initctl
[libsyncml]
1:libsyncml-0.4.6-4.fc17.i686 requires libsoup-2.2.so.8
1:libsyncml-0.4.6-4.fc17.x86_64 requires libsoup-2.2.so.8()(64bit)
[maniadrive]
raydium-1.2-47.fc18.x86_64 requires libode.so.1()(64bit)
[mapserver]
mapserver-perl-6.0.1-5.fc17.x86_64 requires perl(:MODULE_COMPAT_5.14.2)
[milter-greylist]
milter-greylist-upstart-4.2.7-1701.fc18.noarch requires /sbin/initctl
[mod_pubcookie]
mod_pubcookie-3.3.4a-7.fc18.x86_64 requires httpd-mmn = 
0:20051115-x86-64
[openvrml]
libopenvrml-0.18.9-3.fc18.i686 requires libboost_thread-mt.so.1.48.0
libopenvrml-0.18.9-3.fc18.i686 requires libboost_system-mt.so.1.48.0
libopenvrml-0.18.9-3.fc18.i686 requires libboost_filesystem-mt.so.1.48.0
libopenvrml-0.18.9-3.fc18.x86_64 requires 
libboost_thread-mt.so.1.48.0()(64bit)
libopenvrml-0.18.9-3.fc18.x86_64 requires 
libboost_system-mt.so.1.48.0()(64bit)
libopenvrml-0.18.9-3.fc18.x86_64 requires 
libboost_filesystem-mt.so.1.48.0()(64bit)
libopenvrml-gl-0.18.9-3.fc18.i686 requires libboost_thread-mt.so.1.48.0
libopenvrml-gl-0.18.9-3.fc18.i686 requires libboost_system-mt.so.1.48.0
libopenvrml-gl-0.18.9-3.fc18.i686 requires 
libboost_filesystem-mt.so.1.48.0
libopenvrml-gl-0.18.9-3.fc18.x86_64 requires 
libboost_thread-mt.so.1.48.0()(64bit)
libopenvrml-gl-0.18.9-3.fc18.x86_64 requires 
libboost_system-mt.so.1.48.0()(64bit)
libopenvrml-gl-0.18.9-3.fc18.x86_64 requires 

Re: What are reasonable blockers for making journald the default logger in F19?

[Nicolas Mailhot]

Le Mer 17 octobre 2012 20:39, Lennart Poettering a écrit :

 So, that passwords are logged to authpriv appears to be fabrication to
 me.

Anything auth-related will log passwords, because users are so fed up with
password prompts they type them in zombie mode, and every once in a while
they end up typing them in the username field (because whatever they use
to switch fields didn't work this time)

-- 
Nicolas Mailhot

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

libjpeg-turbo API/ABI bump in F19 (transition from jpeg6 to jpeg8 API/ABI)

[Adam Tkac]

Hello all,

I've just created
https://fedoraproject.org/wiki/Features/libjpeg-turbo-jpeg8-ABI page which
contains plan how to successfully move from current jpeg6 API/ABI to more recent
jpeg8 API/ABI for Fedora 19.

All packages which depends on libjpeg.so will have to be rebuilt. Since I have
provenpackager privileges, I will cook some script which will rebuild all
pkgs automatically so no action will be required from maintainers.

If there are no objections against this approach, I will start with this task
next week.

Regards, Adam

-- 
Adam Tkac, Red Hat, Inc.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: fedpkg / koji error

[Simone Caronni]

On 18 October 2012 14:47, Thorsten Leemhuis fed...@leemhuis.info wrote:
  With the old one I had to check like this (first line) for building;
  which is not correct anyway as the behaviour was different as well
  between fedpkg and rpmbuild/mock: [...]

 And that should not be the case imho. But if we define rhel as 0 in
 redhat-rpm-config instead (or in addition?) of fedpgk, then your case
 should remain fixed as well -- or am I missing something?

People dealing with fedpkg are fedora contributors, so I think they
can deal with it anyway.
From a logical point of view I don't see any objections for adding it
to the base macros, but I'm not the best person to say if there could
be any implication.

Regards,
--Simone

--
You cannot discover new oceans unless you have the courage to lose
sight of the shore (R. W. Emerson).
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: modules, firmware, kernel size (was Re: systemd requires HTTP server and serves QR codes)

[Bill Nottingham]

Josh Boyer (jwbo...@gmail.com) said: 
  You'd want to do it something like that.
 
  kernel-minimal as you say but with a Provides: kernel, kernel-common as you
  say.
 
 
  I'd introduce a third metapackage just kernel that requires both of those
  and implicitly Provides: kernel.  Most people would just get the kernel
  metapackage when a transaction asks for something to provide kernel, but
  if you explicitly ask for kernel-minimal you'd get just the minimal.
 
  This would all be done from one kernel spec and built out at the same time.
  We've got a lot of new infrastructure coming for kernel builds and we don't
  want to make things even more complicated by having to do multiple rpm build
  runs.
 
 All of this can probably already be done with a new 'flavor' in the
 existing kernel.spec.  I really wouldn't do the common/minimal split
 though.  It just makes it more complicated for not a whole lot of gain.
 
 The idea that Dave, Justin, and Kevin all had simlutaneously about
 doing a 'kernel-virtguest' might be worthwhile if someone wants to
 spend time poking at a config, etc.

That also works with the normal paradigm where all the variants provide
'kernel' for RPM dependency purposes; if you try to have a kernel-minimal that
provides 'kernel' while also having a 'kernel' package that requires
'kernel-minimal', things get a bit more strange.

Bill
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: libjpeg-turbo API/ABI bump in F19 (transition from jpeg6 to jpeg8 API/ABI)

[Bill Nottingham]

Adam Tkac (at...@redhat.com) said: 
 I've just created
 https://fedoraproject.org/wiki/Features/libjpeg-turbo-jpeg8-ABI page which
 contains plan how to successfully move from current jpeg6 API/ABI to more 
 recent
 jpeg8 API/ABI for Fedora 19.
 
 All packages which depends on libjpeg.so will have to be rebuilt. Since I have
 provenpackager privileges, I will cook some script which will rebuild all
 pkgs automatically so no action will be required from maintainers.
 
 If there are no objections against this approach, I will start with this task
 next week.

Ouch. I can see a need for a compat library for some period of time here -
the jpeg6 API has certainly been around for quite a long while.

Bill
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: modules, firmware, kernel size (was Re: systemd requires HTTP server and serves QR codes)

[Matthew Miller]

On Thu, Oct 18, 2012 at 10:33:27AM -0400, Bill Nottingham wrote:
  All of this can probably already be done with a new 'flavor' in the
  existing kernel.spec.  I really wouldn't do the common/minimal split
  though.  It just makes it more complicated for not a whole lot of gain.
  
  The idea that Dave, Justin, and Kevin all had simlutaneously about
  doing a 'kernel-virtguest' might be worthwhile if someone wants to
  spend time poking at a config, etc.
 
 That also works with the normal paradigm where all the variants provide
 'kernel' for RPM dependency purposes; if you try to have a kernel-minimal that
 provides 'kernel' while also having a 'kernel' package that requires
 'kernel-minimal', things get a bit more strange.

I'm open to this idea, but I think it's nicer if one can go from the reduced
selection to the full just by adding in the right package, not changing or
removing things. Unlike PAE or etc., I don't think we'd actually build
anything differently (would we?).

-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  mat...@fedoraproject.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: libjpeg-turbo API/ABI bump in F19 (transition from jpeg6 to jpeg8 API/ABI)

[Adam Tkac]

On Thu, Oct 18, 2012 at 10:35:56AM -0400, Bill Nottingham wrote:
 Adam Tkac (at...@redhat.com) said: 
  I've just created
  https://fedoraproject.org/wiki/Features/libjpeg-turbo-jpeg8-ABI page which
  contains plan how to successfully move from current jpeg6 API/ABI to more 
  recent
  jpeg8 API/ABI for Fedora 19.
  
  All packages which depends on libjpeg.so will have to be rebuilt. Since I 
  have
  provenpackager privileges, I will cook some script which will rebuild all
  pkgs automatically so no action will be required from maintainers.
  
  If there are no objections against this approach, I will start with this 
  task
  next week.
 
 Ouch. I can see a need for a compat library for some period of time here -
 the jpeg6 API has certainly been around for quite a long while.

Hm, you are probably right. Since libjpeg is widely used, there might be some 
proprietary
apps which require it.

In my opinion we can just ship compat libjpeg.so.* without development files for
some time. Or do we need devel files as well?

Regards, Adam

-- 
Adam Tkac, Red Hat, Inc.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: modules, firmware, kernel size (was Re: systemd requires HTTP server and serves QR codes)

[Josh Boyer]

On Thu, Oct 18, 2012 at 10:39 AM, Matthew Miller
mat...@fedoraproject.org wrote:
 On Thu, Oct 18, 2012 at 10:33:27AM -0400, Bill Nottingham wrote:
  All of this can probably already be done with a new 'flavor' in the
  existing kernel.spec.  I really wouldn't do the common/minimal split
  though.  It just makes it more complicated for not a whole lot of gain.
 
  The idea that Dave, Justin, and Kevin all had simlutaneously about
  doing a 'kernel-virtguest' might be worthwhile if someone wants to
  spend time poking at a config, etc.

 That also works with the normal paradigm where all the variants provide
 'kernel' for RPM dependency purposes; if you try to have a kernel-minimal 
 that
 provides 'kernel' while also having a 'kernel' package that requires
 'kernel-minimal', things get a bit more strange.

 I'm open to this idea, but I think it's nicer if one can go from the reduced
 selection to the full just by adding in the right package, not changing or
 removing things. Unlike PAE or etc., I don't think we'd actually build
 anything differently (would we?).

Of course we would.  The entire point is to reduce the size, and the
only way to reduce the size is to build it with different config
options.  And we're not talking about going from kernel-virtguest to
kernel by installing kernel-everythingnotinvirtguest.  That's still
going down the split the kernel up into a bunch of subpackages route
which just creates more work for the maintainers.

At the moment though, all of this is just talk anyway.  If something
like this is to happen, someone actually has to do work.

josh
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: libjpeg-turbo API/ABI bump in F19 (transition from jpeg6 to jpeg8 API/ABI)

[Bill Nottingham]

Adam Tkac (at...@redhat.com) said: 
 On Thu, Oct 18, 2012 at 10:35:56AM -0400, Bill Nottingham wrote:
  Adam Tkac (at...@redhat.com) said: 
   I've just created
   https://fedoraproject.org/wiki/Features/libjpeg-turbo-jpeg8-ABI page which
   contains plan how to successfully move from current jpeg6 API/ABI to more 
   recent
   jpeg8 API/ABI for Fedora 19.
   
   All packages which depends on libjpeg.so will have to be rebuilt. Since I 
   have
   provenpackager privileges, I will cook some script which will rebuild all
   pkgs automatically so no action will be required from maintainers.
   
   If there are no objections against this approach, I will start with this 
   task
   next week.
  
  Ouch. I can see a need for a compat library for some period of time here -
  the jpeg6 API has certainly been around for quite a long while.
 
 Hm, you are probably right. Since libjpeg is widely used, there might be some 
 proprietary
 apps which require it.
 
 In my opinion we can just ship compat libjpeg.so.* without development files 
 for
 some time. Or do we need devel files as well?

Just the .so should be fine.

Bill
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Ville Skyttä]

On 2012-10-18 11:35, Enrico Scholz wrote:

 Hence, the systemd tools should follow Unix/Linux tradition and specialize
 on their core functionality and avoid implementing features breaking
 user experience.  There are other tools like 'less' which are much better
 suited for paging program output and concepts like pipes are well known
 and used at thousands of other places.

+1, FWIW

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: modules, firmware, kernel size

[Benny Amorsen]

Josh Boyer jwbo...@gmail.com writes:

 Of course we would.  The entire point is to reduce the size, and the
 only way to reduce the size is to build it with different config
 options.

Just splitting off most modules would do the job I would think... Of
course you can go smaller if you change config options, but that is a
lot of work.

Maintaining a list of core modules does not sound like an unbearable
task. (Easy for me to say, of course). Then everything else under
/lib/modules can go into a separate RPM.

# rpm -ql kernel-3.6.1|grep ^/lib|xargs du -c
31488   total

# du  -s /lib/modules/3.6.1-1.fc17.x86_64/
100324  /lib/modules/3.6.1-1.fc17.x86_64/

Making sure that the right systems get the extra module RPM is left as
an exercise for the reader.


/Benny

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: modules, firmware, kernel size

[Josh Boyer]

On Thu, Oct 18, 2012 at 11:02 AM, Benny Amorsen benny+use...@amorsen.dk wrote:
 Josh Boyer jwbo...@gmail.com writes:

 Of course we would.  The entire point is to reduce the size, and the
 only way to reduce the size is to build it with different config
 options.

 Just splitting off most modules would do the job I would think... Of
 course you can go smaller if you change config options, but that is a
 lot of work.

 Maintaining a list of core modules does not sound like an unbearable
 task. (Easy for me to say, of course). Then everything else under
 /lib/modules can go into a separate RPM.

Your definition of core modules is going to differ from mine, and the
next persons, and the next.

 # rpm -ql kernel-3.6.1|grep ^/lib|xargs du -c
 31488   total

 # du  -s /lib/modules/3.6.1-1.fc17.x86_64/
 100324  /lib/modules/3.6.1-1.fc17.x86_64/

 Making sure that the right systems get the extra module RPM is left as
 an exercise for the reader.

It's not simple.  It's not easy.  It buys you very very little and it
leaves the maintainers having to continuously guess which package a
module goes into.  Then there's the requests to move them from one to
the other.

I'm _very_ against splitting the modules up more than they already are.
The modules-extra subpackage has been somewhat a pain already, and those
are the modules that are very rarely used.  Extending it to common ones
leaves me with a headache just thinking about it.

josh
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: modules, firmware, kernel size (was Re: systemd requires HTTP server and serves QR codes)

[Matthew Miller]

On Thu, Oct 18, 2012 at 10:44:58AM -0400, Josh Boyer wrote:
  I'm open to this idea, but I think it's nicer if one can go from the reduced
  selection to the full just by adding in the right package, not changing or
  removing things. Unlike PAE or etc., I don't think we'd actually build
  anything differently (would we?).
 Of course we would.  The entire point is to reduce the size, and the
 only way to reduce the size is to build it with different config
 options.  And we're not talking about going from kernel-virtguest to
 kernel by installing kernel-everythingnotinvirtguest.  That's still
 going down the split the kernel up into a bunch of subpackages route
 which just creates more work for the maintainers.

We already have kernel-modules-extra. I think the idea would be to add
kernel-modules-virt and kernel-modules-normal to that, at most. (Or, put the
virt modules in kernel, and just add one more subpackage,
kernel-modules-normal.) There's already code in the spec file for dealing
with modules-extra, so it's mostly a matter of extending that slightly --
not doing something entirely new, *and* not going down the alarmist slope of
a horde of subpackages.


 At the moment though, all of this is just talk anyway.  If something
 like this is to happen, someone actually has to do work.

Start with an idea, discuss it, come up with a plan, find resources for that
plan, and then implement. Sometimes things happen the other way around, but
only when we happen to be lucky, and it often has consequences like extra
ongoing work with no support. So, just talk is an important place to start.

-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  mat...@fedoraproject.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: modules, firmware, kernel size

[Matthew Miller]

On Thu, Oct 18, 2012 at 11:10:11AM -0400, Josh Boyer wrote:
 Your definition of core modules is going to differ from mine, and the
 next persons, and the next.

Again: proposed definition is modules that get a functional system running
in some agreed-on list of virt and cloud providers. We decide on that at the
meta level, and then, while the work to initially sort out what modules are
required isn't to be underestimated, at least it isn't an argument over the
individual core-ness of each module over and over again. No guessing, no
no continual stream of requests.


-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  mat...@fedoraproject.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

[Bug 838120] perl-DateTime is too old

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=838120

--- Comment #9 from Fedora Update System upda...@fedoraproject.org ---
Package perl-DateTime-0.77-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing perl-DateTime-0.77-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16391/perl-DateTime-0.77-1.fc18
then log in and leave karma (feedback).

-- 
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 857845] perl-DateTime-TimeZone-1.51 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=857845

--- Comment #6 from Fedora Update System upda...@fedoraproject.org ---
Package perl-DateTime-TimeZone-1.51-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing
perl-DateTime-TimeZone-1.51-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16395/perl-DateTime-TimeZone-1.51-1.fc18
then log in and leave karma (feedback).

-- 
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: modules, firmware, kernel size (was Re: systemd requires HTTP server and serves QR codes)

[Justin M. Forbes]

On Thu, Oct 18, 2012 at 11:34:00AM -0400, Josh Boyer wrote:
 On Thu, Oct 18, 2012 at 11:15 AM, Matthew Miller
 mat...@fedoraproject.org wrote:
  On Thu, Oct 18, 2012 at 10:44:58AM -0400, Josh Boyer wrote:
 
  At the moment though, all of this is just talk anyway.  If something
  like this is to happen, someone actually has to do work.
 
  Start with an idea, discuss it, come up with a plan, find resources for that
  plan, and then implement. Sometimes things happen the other way around, but
  only when we happen to be lucky, and it often has consequences like extra
  ongoing work with no support. So, just talk is an important place to start.
 
 OK.  So here's a more blunt response.
 
 I'm really against splitting the modules up into more subpackages,
 regardless of how many it is.  I will not spend any time looking at how
 to do that.  I won't spend time discussing further plans to do something
 I don't feel is maintainable.  If you find someone willing to, great.
 Post patches to the kernel list and we'll review them.  But I'm telling
 you now that it will be an uphill battle.

Just to be clear on this, if someone feels it is worthwhile and wants to
step up and do the work, it can't just be someone who will send patches to
change the current kernel and leave. It has to be someone willing to sign
up to maintain the solution in the rawhide kernel. Modules change, get added
or removed, and/or have deps change pretty much every single release.  3.7
just moved the nat modules.  This is why we are saying that it is much
easier to do a different build of another flavor than to split out the
modules into more subpackages.

Justin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: modules, firmware, kernel size (was Re: systemd requires HTTP server and serves QR codes)

[Matthew Miller]

On Thu, Oct 18, 2012 at 10:56:21AM -0500, Justin M. Forbes wrote:
  I'm really against splitting the modules up into more subpackages,
  regardless of how many it is.  I will not spend any time looking at how
  to do that.  I won't spend time discussing further plans to do something
  I don't feel is maintainable.  If you find someone willing to, great.
  Post patches to the kernel list and we'll review them.  But I'm telling
  you now that it will be an uphill battle.
 
 Just to be clear on this, if someone feels it is worthwhile and wants to
 step up and do the work, it can't just be someone who will send patches to
 change the current kernel and leave. It has to be someone willing to sign
 up to maintain the solution in the rawhide kernel. Modules change, get added
 or removed, and/or have deps change pretty much every single release.  3.7
 just moved the nat modules.  This is why we are saying that it is much
 easier to do a different build of another flavor than to split out the
 modules into more subpackages.

Head nods to both of you. I'm happy to live in reality rather than utopia
and this is helpful feedback.

-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  mat...@fedoraproject.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: f18: how to install into a LVM partitions (or RAID)

[Ian Pilcher]

On 10/17/2012 10:55 AM, Adam Williamson wrote:
 Was the old one really better, or were you just used to it? Comparing
 the first time you use the new dialog to the 50th time you used the old
 one is an entirely unfair comparison. You have to compare the first time
 you use the new dialog to the first time you used the old one. *Any* new
 design will seem more difficult than the old one, at first, to someone
 who was familiar with the old one.

Just my opinion, but I believe that a lot of the confusion is caused by
the lack of a clear statement that LVM, RAID, etc., are *supposed* to
work.

We are at the beta test compose stage, which most people interpret to
mean something close to feature complete.  Combine this with the fact
there's no indication in the UI (that I could discern) of support for
existing RAID arrays or LVM VGs, and I don't believe it's at all
unreasonable to wonder if this functionality is simply being removed.

-- 

Ian Pilcher arequip...@gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Adam Williamson]

On Thu, 2012-10-18 at 10:35 +0200, Enrico Scholz wrote:
 Matthew Miller mat...@fedoraproject.org writes:
 
- don't auto-page;
 
 yes; that's the best solution.  The auto-pager is perhaps the most
 annoying feature of systemd.  I have no problem in scrolling back some
 pages in my terminal with shift-pgup, but having a status request block
 (plain 'systemctl' or 'journalctl' request a status) is just broken.

I don't really look at it that way. Let's see, how to put it...

Okay, so with the old system, I don't recall *ever* doing
'cat /var/log/messages'. I always, always either less'ed it or grep'ped
it. So to me it makes sense for journalctl to page by default, because
that's what I always wanted to do with the logs anyway. I guess the
assumption might have been that most people use logs like me, and hence
that's why journalctl is designed the way it is.

Did/do you usually less /var/log/messages? Or did you usually cat it?

 Or, do you want that e.g. the 'ls -l' output gets auto-paged?

Thinking about this case, when I'm doing an ls -l which I know will be
long, I usually wind up trying to order it in such a way that what I
want to see will be at the bottom (classically, ls -ltr)...that doesn't
really work with journals. How about you?
-- 
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: What are reasonable blockers for making journald the default logger in F19?

[Adam Williamson]

On Thu, 2012-10-18 at 11:38 +0200, Benny Amorsen wrote:
 Lennart Poettering mzerq...@0pointer.de writes:
 
  One way to achieve that should be to provide /var/log/README with the
  appropriate hints, since I assume much more people will look for logs
  in /var/log like it used to be in most of Linux history rather than in
  a tool logread that is known by an embedded distro by the name of
  OpenWRT...
 
 You do have a way with words. I did not propose logread because it is
 used by OpenWRT, I proposed it because it is a sane name.
 
 When I read logs, I do not want to control a journal, that is for
 tune2fs to do.

Trying to come up with 'intuitive' names for commands strikes me as a
spectacularly worthless pursuit. I'm not sure it's possible. Does anyone
really learn a new system by typing their best guess as to what its
commands and parameters might be into a console?!
-- 
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: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Miloslav Trmač]

On Thu, Oct 18, 2012 at 10:35 AM, Enrico Scholz
enrico.sch...@informatik.tu-chemnitz.de wrote:
 Hence, the systemd tools should follow Unix/Linux tradition and specialize
 on their core functionality and avoid implementing features breaking
 user experience.

FWIW, it's not only implicit tradition: (info standards 'Program
Behavior' 'User Interfaces') .
   Mirek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Nonresponsive maintainer: bogado

[Julian Sikorski]

Hi list,

I have been unsuccessful in trying to contact Victor Bogado:
https://bugzilla.redhat.com/show_bug.cgi?id=770887
Old raw-thumbnailer is not only non-functional, but also blocks
goffice/gnumeric/gnome-chemistry-utils progress.

Best regards,
Julian
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Przemek Klosowski]

On 10/18/2012 01:29 PM, Adam Williamson wrote:


Okay, so with the old system, I don't recall *ever* doing
'cat /var/log/messages'. I always, always either less'ed it or grep'ped

...

Did/do you usually less /var/log/messages? Or did you usually cat it?


Or, do you want that e.g. the 'ls -l' output gets auto-paged?


tail -f, about half of the time...

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: What are reasonable blockers for making journald the default logger in F19?

[Reindl Harald]

Am 18.10.2012 19:32, schrieb Adam Williamson:
 Trying to come up with 'intuitive' names for commands strikes me as a
 spectacularly worthless pursuit. I'm not sure it's possible. Does anyone
 really learn a new system by typing their best guess as to what its
 commands and parameters might be into a console?!

yes!

with bash-completion and double-TAB it is desirable
in many situations and at least it is helpful also
if read all the docs and do not exactly remember
not so often used commands - man unknown is hard

[root@srv-rhsoft:~]$ system
system-config-keyboard  systemd-delta   
systemd-readahead-analyze
systemctl   systemd-detect-virt 
systemd-stdio-bridge
systemd systemd-inhibit 
systemd-systemctl
systemd-analyze systemd-journalctl  
systemd-sysv-convert
systemd-ask-passwordsystemd-loginctlsystemd-tmpfiles
systemd-cat systemd-machine-id-setup
systemd-tty-ask-password-agent
systemd-cglssystemd-notify  systemsettings
systemd-cgtop   systemd-nspawn  
system-setup-keyboard

[root@srv-rhsoft:~]$ man systemd-journalctl..



signature.asc
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Matthew Miller]

On Thu, Oct 18, 2012 at 01:41:59PM -0400, Przemek Klosowski wrote:
 Okay, so with the old system, I don't recall *ever* doing
 'cat /var/log/messages'. I always, always either less'ed it or grep'ped
 Did/do you usually less /var/log/messages? Or did you usually cat it?
 Or, do you want that e.g. the 'ls -l' output gets auto-paged?
 tail -f, about half of the time...

And, there _is_ `journalctl -f`, which does just what you'd expect. 


-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  mat...@fedoraproject.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Przemek Klosowski]

On 10/18/2012 01:41 PM, Przemek Klosowski wrote:

On 10/18/2012 01:29 PM, Adam Williamson wrote:


Okay, so with the old system, I don't recall *ever* doing
'cat /var/log/messages'. I always, always either less'ed it or grep'ped

...

Did/do you usually less /var/log/messages? Or did you usually cat it?


Or, do you want that e.g. the 'ls -l' output gets auto-paged?


tail -f, about half of the time...



BTW, I hope that journald will allow doing the equivalent of

tail -f /var/log/**

This would be tricky during the transition when some programs will still 
use /var/log/xxx files and some will go through journald. Sort of like 
currently dmesg working differently than /var/log/* files (I keep making 
the mistake of 'tail dmesg'/'less dmesg').

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Reindl Harald]

Am 18.10.2012 19:29, schrieb Adam Williamson:
 On Thu, 2012-10-18 at 10:35 +0200, Enrico Scholz wrote:
 Matthew Miller mat...@fedoraproject.org writes:

   - don't auto-page;

 yes; that's the best solution.  The auto-pager is perhaps the most
 annoying feature of systemd.  I have no problem in scrolling back some
 pages in my terminal with shift-pgup, but having a status request block
 (plain 'systemctl' or 'journalctl' request a status) is just broken.
 
 I don't really look at it that way. Let's see, how to put it...
 
 Okay, so with the old system, I don't recall *ever* doing
 'cat /var/log/messages'. I always, always either less'ed it or grep'ped
 it. So to me it makes sense for journalctl to page by default

and i am doing tail -n 500 -f /var/log/messages or whatever
logfle i want to watch since years because i want to see what
happened before, can scroll up and watch what is going on

the same works for tail -n 500 -f /var/log/messages | grep whatever
for me i prcatically NEVER use any pager!

so you see how different workflows are
and that is why the unix-principle is basic tools and stick them together
this way yours and mine way to do things are equally supported





signature.asc
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Matthew Miller]

On Thu, Oct 18, 2012 at 01:50:38PM -0400, Przemek Klosowski wrote:
 BTW, I hope that journald will allow doing the equivalent of
 tail -f /var/log/**

That is effectively what 'journalctl -f' does by default.

 This would be tricky during the transition when some programs will
 still use /var/log/xxx files and some will go through journald. Sort

Effectively, any server that doesn't use syslog now.

 of like currently dmesg working differently than /var/log/* files (I
 keep making the mistake of 'tail dmesg'/'less dmesg').

Here, you are in luck -- journald handles those messages. (By default in
F18, optionally in F17.)

-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  mat...@fedoraproject.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Matthew Miller]

On Thu, Oct 18, 2012 at 07:46:46PM +0200, Reindl Harald wrote:
 and i am doing tail -n 500 -f /var/log/messages or whatever
 logfle i want to watch since years because i want to see what
 happened before, can scroll up and watch what is going on

This will work *right now* with journald, with almost identical semantics:

 journalctl  -n500 -f

(No space allowed after then -n.)

 the same works for tail -n 500 -f /var/log/messages | grep whatever
 for me i prcatically NEVER use any pager!

There's a bug with that right now, but theoretically should work. You can
also use journalctl's built-in filtering, which does matches on fields.



-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  mat...@fedoraproject.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Lennart Poettering]

On Thu, 18.10.12 14:05, Matthew Miller (mat...@fedoraproject.org) wrote:

  journalctl  -n500 -f
 
 (No space allowed after then -n.)

The space thing is really annoying actually. glibc's getopt() insists on
that for options such as -n that have an optional argument (i.e. which
appear as n:: in the opt string). I'd love to fix this if somebody has
an idea to get getopt() to be nice to us here...

Lennart

-- 
Lennart Poettering - Red Hat, Inc.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Reindl Harald]

Am 18.10.2012 20:05, schrieb Matthew Miller:
 On Thu, Oct 18, 2012 at 07:46:46PM +0200, Reindl Harald wrote:
 and i am doing tail -n 500 -f /var/log/messages or whatever
 logfle i want to watch since years because i want to see what
 happened before, can scroll up and watch what is going on
 
 This will work *right now* with journald, with almost identical semantics:
 
  journalctl  -n500 -f
 
 (No space allowed after then -n.)

thats not the point

the point is that tail, grep, less, more, wathever-pager-you-use
can be stucked with nearly any console-application in any
creative way BUT the same way for all

if i want a pager - i use a pager

[root@srv-rhsoft:~]$ which systemctl
alias systemctl='/bin/systemctl --no-pager --full'
/bin/systemctl

sad that you need to use aliases to get the normal unix.behavior
some tools like git doing not so is no excusion because this
sounds like i do it wrong because some others do too



signature.asc
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[John . Florian]

 From: Reindl Harald h.rei...@thelounge.net
 Am 18.10.2012 20:05, schrieb Matthew Miller:
  On Thu, Oct 18, 2012 at 07:46:46PM +0200, Reindl Harald wrote:
  and i am doing tail -n 500 -f /var/log/messages or whatever
  logfle i want to watch since years because i want to see what
  happened before, can scroll up and watch what is going on
  
  This will work *right now* with journald, with almost identical 
semantics:
  
   journalctl  -n500 -f
  
  (No space allowed after then -n.)
 
 thats not the point
 
 the point is that tail, grep, less, more, wathever-pager-you-use
 can be stucked with nearly any console-application in any
 creative way BUT the same way for all
 
 if i want a pager - i use a pager
 
 [root@srv-rhsoft:~]$ which systemctl
 alias systemctl='/bin/systemctl --no-pager --full'
 /bin/systemctl
 
 sad that you need to use aliases to get the normal unix.behavior
 some tools like git doing not so is no excusion because this
 sounds like i do it wrong because some others do too

This is doomed to a flameware like vi vs emacs, I'm afraid.  I love the 
auto-page feature, but agree the implementation might be more friendly.  I 
like *nix traditions and pipelines -- I make some huge ones -- but 
systemctl and journalctl are user-interfaces, like git, man, info, etc. 
and I see nothing wrong with an implied pager.  I think git has nailed the 
perfect combo where it allows configs of always, never and auto 
(turns off paging, color, etc. for non-tty stdout).

--
John Florian

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Matthew Miller]

On Thu, Oct 18, 2012 at 08:30:43PM +0200, Lennart Poettering wrote:
   journalctl  -n500 -f
  (No space allowed after then -n.)
 The space thing is really annoying actually. glibc's getopt() insists on
 that for options such as -n that have an optional argument (i.e. which
 appear as n:: in the opt string). I'd love to fix this if somebody has
 an idea to get getopt() to be nice to us here...

How about an option --tail (and maybe -t) which defaults to 10 (and turns
off the pager?), and then making the value to -n be non-optional? This fits
with the behavior of the tail command, where the number for n is also
non-optional if n is given.

-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  mat...@fedoraproject.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: aha! I figured out why journalctl's auto-pager bugs me when git's doesn't (and possible solution)

[Miloslav Trmač]

On Thu, Oct 18, 2012 at 8:30 PM, Lennart Poettering
mzerq...@0pointer.de wrote:
 On Thu, 18.10.12 14:05, Matthew Miller (mat...@fedoraproject.org) wrote:

  journalctl  -n500 -f

 (No space allowed after then -n.)

 The space thing is really annoying actually. glibc's getopt() insists on
 that for options such as -n that have an optional argument (i.e. which
 appear as n:: in the opt string). I'd love to fix this if somebody has
 an idea to get getopt() to be nice to us here...

Please just don't use optional arguments.
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
is the closest we have for a consensus on argument handling:
 Guideline 7:
 Option-arguments should not be optional.

(The glibc behavior is also consistent with 12.1 item 2.)
Mirek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: What are reasonable blockers for making journald the default logger in F19?

[Björn Persson]

Adam Williamson wrote:
 Trying to come up with 'intuitive' names for commands strikes me as a
 spectacularly worthless pursuit. I'm not sure it's possible. Does
 anyone really learn a new system by typing their best guess as to
 what its commands and parameters might be into a console?!

Not exactly learn a new system, but I do sometimes guess at the 
beginning of a command. I might for example type rpmTabTab to see 
if there is an RPM-related command that looks like it might do what I 
want, or vgTabTab to get a list of commands related to LVM volume 
groups.

What's more important, though, is that it's much easier to remember a 
command that's named after what it does. When I want to read a log it's 
easier to remember a command that sounds like log reader than one that 
sounds like journal controller. I might accept that the log is now 
called a journal instead for unknown reasons, but even then the 
controller part is quite confusing. Controller is a good word for a 
program that starts, stops and reconfigures something, not for a program 
that reads logs.

But perhaps ctl is short for cutler and alludes to Journalctl's 
ability to slice up logs in several different ways? In that case the name 
would be easier to remember if cutler were spelled out.

Björn Persson

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: modules, firmware, kernel size

[Benny Amorsen]

Josh Boyer jwbo...@gmail.com writes:

 It's not simple.  It's not easy.  It buys you very very little and it
 leaves the maintainers having to continuously guess which package a
 module goes into.  Then there's the requests to move them from one to
 the other.

I certainly buy those arguments. The whole thing may be too much of a
bother even though it does not mean recompiling anything.

It IS quite a lot of work.

The savings are quite substantial though. The modules currently loaded
on my laptop take up 8MB of disk space, out of about 95MB of modules. It
does not seem unreasonable to think that the modules needed for most
virtualizated devices could fit in 10MB perhaps, which means a saving of
75MB.


/Benny


(By the way, I have Infiniband modules loaded, but alas the laptop seems
rather lacking when it comes to Infiniband cards!?)
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: libjpeg-turbo API/ABI bump in F19 (transition from jpeg6 to jpeg8 API/ABI)

[Adam Williamson]

On Thu, 2012-10-18 at 16:43 +0200, Adam Tkac wrote:
 On Thu, Oct 18, 2012 at 10:35:56AM -0400, Bill Nottingham wrote:
  Adam Tkac (at...@redhat.com) said: 
   I've just created
   https://fedoraproject.org/wiki/Features/libjpeg-turbo-jpeg8-ABI page which
   contains plan how to successfully move from current jpeg6 API/ABI to more 
   recent
   jpeg8 API/ABI for Fedora 19.
   
   All packages which depends on libjpeg.so will have to be rebuilt. Since I 
   have
   provenpackager privileges, I will cook some script which will rebuild all
   pkgs automatically so no action will be required from maintainers.
   
   If there are no objections against this approach, I will start with this 
   task
   next week.
  
  Ouch. I can see a need for a compat library for some period of time here -
  the jpeg6 API has certainly been around for quite a long while.
 
 Hm, you are probably right. Since libjpeg is widely used, there might be some 
 proprietary
 apps which require it.

Yeah, I'm with Bill. I note you listed this as the 'contingency plan'
for the feature:

 Contingency Plan

Create libjpeg-turbo-compat and libjpeg-turbo-compat-devel libraries
with jpeg6 API/ABI and ship them in distro. 

I'd suggest you should just make it a plan from the start to have the
-compat library available as part of the feature (so, really, just drop
step 4 of 'scope'), and have the 'contingency plan' be 'abandon ship and
go back to building with the jpeg6 API'.
-- 
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: f18: how to install into a LVM partitions (or RAID)

[Adam Williamson]

On Thu, 2012-10-18 at 12:17 -0500, Ian Pilcher wrote:
 On 10/17/2012 10:55 AM, Adam Williamson wrote:
  Was the old one really better, or were you just used to it? Comparing
  the first time you use the new dialog to the 50th time you used the old
  one is an entirely unfair comparison. You have to compare the first time
  you use the new dialog to the first time you used the old one. *Any* new
  design will seem more difficult than the old one, at first, to someone
  who was familiar with the old one.
 
 Just my opinion, but I believe that a lot of the confusion is caused by
 the lack of a clear statement that LVM, RAID, etc., are *supposed* to
 work.
 
 We are at the beta test compose stage, which most people interpret to
 mean something close to feature complete.  Combine this with the fact
 there's no indication in the UI (that I could discern) of support for
 existing RAID arrays or LVM VGs, and I don't believe it's at all
 unreasonable to wonder if this functionality is simply being removed.

I'm not sure what 'indication' you're expecting, exactly. AIUI, existing
RAID arrays and VGs should just show up in the list of existing
filesystems on the left-hand side of the custom partitioning screen. (In
a recent enough Beta TC, of course, Alpha is ancient stuff now). If they
don't, that's a bug. Do you have a case where they don't? If so, it
should just be reported as a bug.
-- 
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

Using koji via a ssh tunnel

[Ankur Sinha]

Hi folks,

Seems I cannot use koji (therefore fedpkg build and related commands) on
my university wifi. It gives me an error: 


 [ankur@ankur SRPMS]$ ps aux | egrep ssh
 root   999  0.0  0.0  77608  1288 ?Ss   Oct18   0:00 
 /usr/sbin/sshd -D
 ankur 4714  0.0  0.0 106996   848 pts/9S+   14:17   0:00 egrep 
 --color=auto ssh
 ankur 7810  0.0  0.0  75528  1276 ?Ss   11:31   0:00 ssh -f -L 
 6667:irc.freenode.net:6667 ankursi...@fedorapeople.org -N
 [ankur@ankur SRPMS]$ koji --debug-xmlrpc list-tasks --mine
 send: POST /kojihub/ssllogin HTTP/1.1\r\nHost: 
 koji.fedoraproject.org:443\r\nAccept-Encoding: gzip\r\nUser-Agent: 
 pyOpenSSL_XMLRPC/0.12 - xmlrpclib.py/1.0.1 (by 
 www.pythonware.com)\r\nContent-Type: text/xml\r\nContent-Length: 
 140\r\n\r\n?xml 
 version='1.0'?\nmethodCall\nmethodNamesslLogin/methodName\nparams\nparam\nvaluenil//value/param\n/params\n/methodCall\n
 reply: 'HTTP/1.1 200 OK\r\n'
 header: Date: Fri, 19 Oct 2012 03:18:14 GMT
 header: Server: Apache/2.2.15 (Red Hat)
 header: Content-Length: 304
 header: AppTime: D=1222732
 header: AppServer: koji03.phx2.fedoraproject.org
 header: Connection: close
 header: Content-Type: text/xml
 body: ?xml 
 version='1.0'?\nmethodResponse\nparams\nparam\nvaluestruct\nmember\nnamesession-id/name\nvalueint8020825/int/value\n/member\nmember\nnamesession-key/name\nvaluestring935-c3ou3TL42EtyQayMxKv/string/value\n/member\n/struct/value\n/param\n/params\n/methodResponse\n
 send: POST 
 /kojihub?session-id=8020825session-key=935-c3ou3TL42EtyQayMxKvcallnum=0 
 HTTP/1.1\r\nHost: koji.fedoraproject.org:443\r\nAccept-Encoding: 
 gzip\r\nUser-Agent: pyOpenSSL_XMLRPC/0.12 - xmlrpclib.py/1.0.1 (by 
 www.pythonware.com)\r\nContent-Type: text/xml\r\nContent-Length: 
 107\r\n\r\n?xml 
 version='1.0'?\nmethodCall\nmethodNamegetAPIVersion/methodName\nparams\n/params\n/methodCall\n
 reply: 'HTTP/1.1 200 OK\r\n'
 header: Date: Fri, 19 Oct 2012 03:18:16 GMT
 header: Server: Apache/2.2.15 (Red Hat)
 header: Content-Length: 292
 header: AppTime: D=5592
 header: AppServer: koji03.phx2.fedoraproject.org
 header: Connection: close
 header: Content-Type: text/xml
 body: ?xml 
 version='1.0'?\nmethodResponse\nfault\nvaluestruct\nmember\nnamefaultCode/name\nvalueint1002/int/value\n/member\nmember\nnamefaultString/name\nvaluestringInvalid
  session or bad 
 credentials/string/value\n/member\n/struct/value\n/fault\n/methodResponse\n
 AuthError: Invalid session or bad credentials
 send: POST /kojihub?session-id=8020825session-key=935-c3ou3TL42EtyQayMxKv 
 HTTP/1.1\r\nHost: koji.fedoraproject.org:443\r\nAccept-Encoding: 
 gzip\r\nUser-Agent: pyOpenSSL_XMLRPC/0.12 - xmlrpclib.py/1.0.1 (by 
 www.pythonware.com)\r\nContent-Type: text/xml\r\nContent-Length: 
 100\r\n\r\n?xml 
 version='1.0'?\nmethodCall\nmethodNamelogout/methodName\nparams\n/params\n/methodCall\n
 reply: 'HTTP/1.1 200 OK\r\n'
 header: Date: Fri, 19 Oct 2012 03:18:17 GMT
 header: Server: Apache/2.2.15 (Red Hat)
 header: Content-Length: 292
 header: AppTime: D=5696
 header: AppServer: koji03.phx2.fedoraproject.org
 header: Connection: close
 header: Content-Type: text/xml
 body: ?xml 
 version='1.0'?\nmethodResponse\nfault\nvaluestruct\nmember\nnamefaultCode/name\nvalueint1002/int/value\n/member\nmember\nnamefaultString/name\nvaluestringInvalid
  session or bad 
 credentials/string/value\n/member\n/struct/value\n/fault\n/methodResponse\n
 send: POST /kojihub?session-id=8020825session-key=935-c3ou3TL42EtyQayMxKv 
 HTTP/1.1\r\nHost: koji.fedoraproject.org:443\r\nAccept-Encoding: 
 gzip\r\nUser-Agent: pyOpenSSL_XMLRPC/0.12 - xmlrpclib.py/1.0.1 (by 
 www.pythonware.com)\r\nContent-Type: text/xml\r\nContent-Length: 
 100\r\n\r\n?xml 
 version='1.0'?\nmethodCall\nmethodNamelogout/methodName\nparams\n/params\n/methodCall\n
 reply: 'HTTP/1.1 200 OK\r\n'
 header: Date: Fri, 19 Oct 2012 03:18:18 GMT
 header: Server: Apache/2.2.15 (Red Hat)
 header: Content-Length: 292
 header: AppTime: D=5242
 header: AppServer: koji03.phx2.fedoraproject.org
 header: Connection: close
 header: Content-Type: text/xml
 body: ?xml 
 version='1.0'?\nmethodResponse\nfault\nvaluestruct\nmember\nnamefaultCode/name\nvalueint1002/int/value\n/member\nmember\nnamefaultString/name\nvaluestringInvalid
  session or bad 
 credentials/string/value\n/member\n/struct/value\n/fault\n/methodResponse\n
 [ankur@ankur SRPMS]$
 

I already need to use ssh tunneling for irc, as you can see. Would any
one know how I can use koji from this connection? Another ssh tunnel? 

I can't use 443 on my system for the tunnel since it requires root
privileges and my keys etc are only set up for the non root user. (I
wasn't sure what port koji used, so I tried 443 and 80 both with a local
port) I tried using another such as 9000, but koji doesn't take port as
an argument at all. -s localhost:9000 doesn't appear to work. I get a
bad xml-rpc response error. 


This bug/issue looks like what I'm hitting:
https://bugzilla.redhat.com/show_bug.cgi?id=668947

but 

Re: libjpeg-turbo API/ABI bump in F19 (transition from jpeg6 to jpeg8 API/ABI)

[Peter Robinson]

On 19 Oct 2012 00:51, Adam Williamson awill...@redhat.com wrote:

 On Thu, 2012-10-18 at 16:43 +0200, Adam Tkac wrote:
  On Thu, Oct 18, 2012 at 10:35:56AM -0400, Bill Nottingham wrote:
   Adam Tkac (at...@redhat.com) said:
I've just created
https://fedoraproject.org/wiki/Features/libjpeg-turbo-jpeg8-ABIpage 
which
contains plan how to successfully move from current jpeg6 API/ABI
to more recent
jpeg8 API/ABI for Fedora 19.
   
All packages which depends on libjpeg.so will have to be rebuilt.
Since I have
provenpackager privileges, I will cook some script which will
rebuild all
pkgs automatically so no action will be required from maintainers.
   
If there are no objections against this approach, I will start with
this task
next week.
  
   Ouch. I can see a need for a compat library for some period of time
here -
   the jpeg6 API has certainly been around for quite a long while.
 
  Hm, you are probably right. Since libjpeg is widely used, there might
be some proprietary
  apps which require it.

 Yeah, I'm with Bill. I note you listed this as the 'contingency plan'
 for the feature:

  Contingency Plan

 Create libjpeg-turbo-compat and libjpeg-turbo-compat-devel libraries
 with jpeg6 API/ABI and ship them in distro.

 I'd suggest you should just make it a plan from the start to have the
 -compat library available as part of the feature (so, really, just drop
 step 4 of 'scope'), and have the 'contingency plan' be 'abandon ship and
 go back to building with the jpeg6 API'.

You have to have the compat option to build everything as otherwise the
build root breaks from the outset similar to what we saw with the recent
libpng update to 1.5.

Peter
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: f18: how to install into a LVM partitions (or RAID)

[Ian Pilcher]

On 10/18/2012 05:02 PM, Adam Williamson wrote:
 I'm not sure what 'indication' you're expecting, exactly. AIUI, existing
 RAID arrays and VGs should just show up in the list of existing
 filesystems on the left-hand side of the custom partitioning screen. (In
 a recent enough Beta TC, of course, Alpha is ancient stuff now). If they
 don't, that's a bug. Do you have a case where they don't? If so, it
 should just be reported as a bug.
 

They didn't the last time I checked, which I believe was beta TC2.

Just checked again in a test VM and I don't see any way to use the free
space in the existing VG.  (vgdisplay reports 7.74 GiB free of 19.48
GiB.)

On the left hand side, I see:

- New Fedora 18-Beta-TC2
  Installation

You haven't created any mount points for your
Fedora 18-Beta-TC2 installation yet:

Click here to create them automatically

Or, create new mount points below with the '+'
icon.

- CentOS Linux 6.3 for x86_64

  DATA
  SYSTEM

Root7.92 GB
/
Swap  4.09 GB

- Unknown
Unknown 19.97 GB

Unknown498 MB

Unknown  19.97 GB

When I attempt to add a 6GB mount point for /, I get a not enough
free space on disks error.

So how's it supposed to work?

-- 

Ian Pilcher arequip...@gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

[perl-MogileFS-Utils] Modernize spec file (Šíleně žluťoučký kůň úpěl ďábělské ódy. おはよフェドラ�

[Petr Pisar]

commit 3cf60ae2beb57e1a2baddefce87deddc0bbc0c4d
Author: Petr Písař ppi...@redhat.com
Date:   Thu Oct 18 09:10:02 2012 +0200

Modernize spec file (Šíleně žluťoučký kůň úpěl ďábělské ódy.  おはよフェドラ！)

The crazy subject is to test
https://fedorahosted.org/rel-eng/ticket/3930.

 perl-MogileFS-Utils.spec |8 +---
 1 files changed, 5 insertions(+), 3 deletions(-)
---
diff --git a/perl-MogileFS-Utils.spec b/perl-MogileFS-Utils.spec
index c9c8703..53835c1 100644
--- a/perl-MogileFS-Utils.spec
+++ b/perl-MogileFS-Utils.spec
@@ -2,7 +2,7 @@
 
 Name:   perl-%{cpan_name}
 Version:2.26
-Release:1%{?dist}
+Release:2%{?dist}
 Summary:Utilities for MogileFS
 License:GPL+ or Artistic
 Group:  Development/Libraries
@@ -31,9 +31,8 @@ Utilities for the MogileFS distributed storage system.
 make %{?_smp_mflags}
 
 %install
-make pure_install PERL_INSTALL_ROOT=%{buildroot}
+make pure_install DESTDIR=%{buildroot}
 find %{buildroot} -type f -name .packlist -exec rm -f {} \;
-find %{buildroot} -depth -type d -exec rmdir {} 2/dev/null \;
 %{_fixperms} %{buildroot}/*
 
 %check
@@ -47,6 +46,9 @@ make test
 %{_mandir}/man3/*
 
 %changelog
+* Thu Oct 18 2012 Petr Pisar ppi...@redhat.com - 2.26-2
+- Modernize spec file
+
 * Tue Aug 14 2012 Petr Pisar ppi...@redhat.com - 2.26-1
 - 2.26 bump
 
--
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/f18] Do not crash when vivifying $|

[Jitka Plesnikova]

commit 88d9e0fb9f68dfa4ffa4b64a20810b06b4ec897d
Author: Jitka Plesnikova jples...@redhat.com
Date:   Thu Oct 18 10:11:04 2012 +0200

Do not crash when vivifying $|

 1-perl-115206-Don-t-crash-when-vivifying.patch |   75 
 perl.spec  |   10 +++-
 2 files changed, 84 insertions(+), 1 deletions(-)
---
diff --git a/perl-5.16.1-perl-115206-Don-t-crash-when-vivifying.patch 
b/perl-5.16.1-perl-115206-Don-t-crash-when-vivifying.patch
new file mode 100644
index 000..9141946
--- /dev/null
+++ b/perl-5.16.1-perl-115206-Don-t-crash-when-vivifying.patch
@@ -0,0 +1,75 @@
+Ported to 5.16.1:
+
+From 4505a31f43ca4e1a0e9203b389f6d4bebab9d899 Mon Sep 17 00:00:00 2001
+From: Father Chrysostomos spr...@cpan.org
+Date: Tue, 9 Oct 2012 20:47:18 -0700
+Subject: [PATCH] =?UTF-8?q?[perl=20#115206]=20Don=E2=80=99t=20crash=20when=20?=
+ =?UTF-8?q?vivifying=20$|?=
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+It was trying to read the currently-selected handle without checking
+whether it was selected.  It is actually not necessary to initialise
+the variable this way, as the next use of get-magic on it will clobber
+the cached value.
+
+This initialisation was originally added in commit d8ce0c9a45.  The
+bug it was fixing was probably caused by missing FETCH calls that are
+no longer missing.
+---
+ gv.c |5 +
+ t/op/magic.t |5 -
+ 2 files changed, 5 insertions(+), 5 deletions(-)
+
+diff --git a/gv.c b/gv.c
+index f352452..cf02ca4 100644
+--- a/gv.c
 b/gv.c
+@@ -1913,10 +1913,6 @@ Perl_gv_fetchpvn_flags(pTHX_ const char *nambeg, STRLEN 
full_len, I32 flags,
+   Perl_ck_warner_d(aTHX_ packWARN2(WARN_DEPRECATED, WARN_SYNTAX),
+$%c is no longer supported, *name);
+   break;
+-  case '|':   /* $| */
+-  sv_setiv(GvSVn(gv), (IV)(IoFLAGS(GvIOp(PL_defoutgv))  IOf_FLUSH) 
!= 0);
+-  goto magicalize;
+-
+   case '\010':/* $^H */
+   {
+   HV *const hv = GvHVn(gv);
+@@ -1957,6 +1953,7 @@ Perl_gv_fetchpvn_flags(pTHX_ const char *nambeg, STRLEN 
full_len, I32 flags,
+   case '':   /* $ */
+   case '\\':  /* $\ */
+   case '/':   /* $/ */
++  case '|':   /* $| */
+   case '$':   /* $$ */
+   case '\001':/* $^A */
+   case '\003':/* $^C */
+diff --git a/t/op/magic.t b/t/op/magic.t
+index 3fb1ea1..1bcfbd9 100644
+--- a/t/op/magic.t
 b/t/op/magic.t
+@@ -5,7 +5,7 @@ BEGIN {
+ chdir 't' if -d 't';
+ @INC = '../lib';
+ require './test.pl';
+-plan (tests = 156);
++plan (tests = 157);
+ }
+ 
+ # Test that defined() returns true for magic variables created on the fly,
+@@ -581,6 +581,11 @@ SKIP: {
+ }
+ }
+ 
++# $|
++fresh_perl_is
++ 'select f; undef *f; ${q/|/}; print STDOUT qq|ok\n|', ok\n, {}, 
++ '[perl #115206] no crash when vivifying $| while *{+select}{IO} is undef';
++
+ # ^ New tests go here ^
+ 
+ SKIP: {
+-- 
+1.7.7.6
+
diff --git a/perl.spec b/perl.spec
index c48e248..36aca0f 100644
--- a/perl.spec
+++ b/perl.spec
@@ -26,7 +26,7 @@
 Name:   perl
 Version:%{perl_version}
 # release number must be even higher, because dual-lived modules will be 
broken otherwise
-Release:232%{?dist}
+Release:233%{?dist}
 Epoch:  %{perl_epoch}
 Summary:Practical Extraction and Report Language
 Group:  Development/Languages
@@ -106,6 +106,9 @@ Patch17:perl-5.16.1-perl-105924-require-1-2.patch
 # Extend stack in File::Glob::glob, rhbz#859332, RT#114984, fixed after 5.17.4
 Patch18:
perl-5.16.1-perl-114984-Glob.xs-Extend-stack-when-returning.patch
 
+# Do not crash when vivifying $|, rhbz#865296, RT#115206
+Patch19:perl-5.16.1-perl-115206-Don-t-crash-when-vivifying.patch
+
 # Update some of the bundled modules
 # see http://fedoraproject.org/wiki/Perl/perl.spec for instructions
 
@@ -1330,6 +1333,7 @@ tarball from perl.org.
 %patch16 -p1
 %patch17 -p1
 %patch18 -p1
+%patch19 -p1
 
 #copy the example script
 cp -a %{SOURCE5} .
@@ -1540,6 +1544,7 @@ pushd %{build_archlib}/CORE/
 'Fedora Patch16: Do not leak with attribute on my variable (RT#114764)' \
 'Fedora Patch17: Allow operator after numeric keyword argument 
(RT#105924)' \
 'Fedora Patch18: Extend stack in File::Glob::glob, (RT#114984)' \
+'Fedora Patch19: Do not crash when vivifying $|' \
 %{nil}
 
 rm patchlevel.bak
@@ -2610,6 +2615,9 @@ sed \
 
 # Old changelog entries are preserved in CVS.
 %changelog
+* Wed Oct 17 2012 Jitka Plesnikova jples...@redhat.com - 4:5.16.1-233
+- Do not crash when vivifying $| (bug #865296)
+
 * Fri Sep 21 2012 Petr Pisar ppi...@redhat.com - 4:5.16.1-232
 - perl-PathTools uses Carp
 - Do not leak with attribute on my variable (bug #858966)
--
Fedora Extras Perl SIG

[Bug 867753] New: perl-XML-LibXML-2.0007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=867753

Bug ID: 867753
  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: mmasl...@redhat.com
   Summary: perl-XML-LibXML-2.0007 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-XML-LibXML
   Product: Fedora

Latest upstream release: 2.0007
Current version in Fedora Rawhide: 2.0006
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.
--
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 865296] Setting OUTPUT_AUTOFLUSH in eval when STDOUT is localized in upper scope leads to segmentation fault

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=865296

--- Comment #1 from Fedora Update System upda...@fedoraproject.org ---
perl-5.16.1-233.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/perl-5.16.1-233.fc18

-- 
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 857845] perl-DateTime-TimeZone-1.51 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=857845

Petr Pisar ppi...@redhat.com changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC||ppi...@redhat.com
   Assignee|iarn...@gmail.com   |ppi...@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 867753] perl-XML-LibXML-2.0007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=867753

Petr Šabata psab...@redhat.com changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC||psab...@redhat.com
   Assignee|mmasl...@redhat.com |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 DateTime-TimeZone-1.51.tar.gz uploaded to lookaside cache by ppisar

[Petr Pisar]

A file has been added to the lookaside cache for perl-DateTime-TimeZone:

e250604603064f9d22f74b8bae79eb3d  DateTime-TimeZone-1.51.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-DateTime-TimeZone] update to 1.51 - Olson 2012g

[Petr Pisar]

commit 4825aaf287f710ebc2823d951cf9f99325665b0a
Author: Petr Písař ppi...@redhat.com
Date:   Thu Oct 18 10:59:37 2012 +0200

update to 1.51 - Olson 2012g

 .gitignore  |1 +
 perl-DateTime-TimeZone.spec |6 --
 sources |2 +-
 3 files changed, 6 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index f83a87a..3fdf3f8 100644
--- a/.gitignore
+++ b/.gitignore
@@ -11,3 +11,4 @@
 /DateTime-TimeZone-1.47.tar.gz
 /DateTime-TimeZone-1.48.tar.gz
 /DateTime-TimeZone-1.49.tar.gz
+/DateTime-TimeZone-1.51.tar.gz
diff --git a/perl-DateTime-TimeZone.spec b/perl-DateTime-TimeZone.spec
index b0b1ae7..1890856 100644
--- a/perl-DateTime-TimeZone.spec
+++ b/perl-DateTime-TimeZone.spec
@@ -1,5 +1,5 @@
 Name:   perl-DateTime-TimeZone
-Version:1.49
+Version:1.51
 Release:1%{?dist}
 Summary:Time zone object base class and factory
 License:GPL+ or Artistic
@@ -21,7 +21,6 @@ BuildRequires:  perl(Pod::Man) = 1.14
 BuildRequires:  perl(Test::More) = 0.88
 BuildRequires:  perl(Test::Output)
 # not automatically detected
-Requires:   perl(Cwd) = 3
 Requires:   perl(File::Compare)
 Requires:   perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo 
$version))
 
@@ -76,6 +75,9 @@ make test
 %{_mandir}/man3/*
 
 %changelog
+* Thu Oct 18 2012 Petr Pisar ppi...@redhat.com - 1.51-1
+- update to latest upstream version - Olson 2012g
+
 * Sat Sep 15 2012 Iain Arnell iarn...@gmail.com 1.49-1
 - update to latest upstream version - Olson 2012f
 
diff --git a/sources b/sources
index b378dc2..2ab218c 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-595f80ab9770ec25ffd31e453e42918e  DateTime-TimeZone-1.49.tar.gz
+e250604603064f9d22f74b8bae79eb3d  DateTime-TimeZone-1.51.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-DateTime-TimeZone/f18] update to 1.51 - Olson 2012g

[Petr Pisar]

Summary of changes:

  4825aaf... update to 1.51 - Olson 2012g (*)

(*) 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-DateTime-TimeZone/f17] update to 1.51 - Olson 2012g

[Petr Pisar]

Summary of changes:

  4825aaf... update to 1.51 - Olson 2012g (*)

(*) 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-DateTime-TimeZone/f16] update to 1.51 - Olson 2012g

[Petr Pisar]

Summary of changes:

  4825aaf... update to 1.51 - Olson 2012g (*)

(*) 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 857845] perl-DateTime-TimeZone-1.51 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=857845

--- Comment #2 from Petr Pisar ppi...@redhat.com ---
This updates time zone database to Olson 2012g and contains a few bug fixes.

-- 
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-XML-LibXML] 2.0007 bump

[Petr Šabata]

commit 8744963fcfd359033c6df735e848edd3bbb7ea18
Author: Petr Šabata con...@redhat.com
Date:   Thu Oct 18 11:02:33 2012 +0200

2.0007 bump

 .gitignore   |1 +
 perl-XML-LibXML.spec |7 +--
 sources  |2 +-
 3 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 04aa970..9a9945a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -14,3 +14,4 @@ XML-LibXML-1.70.tar.gz
 /XML-LibXML-2.0003.tar.gz
 /XML-LibXML-2.0004.tar.gz
 /XML-LibXML-2.0006.tar.gz
+/XML-LibXML-2.0007.tar.gz
diff --git a/perl-XML-LibXML.spec b/perl-XML-LibXML.spec
index c4cc3c3..8307a6f 100644
--- a/perl-XML-LibXML.spec
+++ b/perl-XML-LibXML.spec
@@ -3,8 +3,8 @@ Name:   perl-XML-LibXML
 # https://bugzilla.redhat.com/show_bug.cgi?id=469480
 # it might not be needed anymore
 # this module is maintained, the other is not
-Version:2.0006
-Release:2%{?dist}
+Version:2.0007
+Release:1%{?dist}
 Epoch:  1
 Summary:Perl interface to the libxml2 library
 
@@ -102,6 +102,9 @@ fi
 %{_mandir}/man3/*.3*
 
 %changelog
+* Thu Oct 18 2012 Petr Šabata con...@redhat.com - 1:2.0007-1
+- 2.0007 bump
+
 * Mon Oct 15 2012 Jitka Plesnikova jples...@redhat.com - 1:2.0006-1
 - 2.0006 bump
 - Remove bundled library and add BR perl(Devel::CheckLib).
diff --git a/sources b/sources
index 08f6487..247ab81 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-84be673c899ae1cf7b204ab7c7f3be46  XML-LibXML-2.0006.tar.gz
+cbce16e0081f2129f44e02293f0d175a  XML-LibXML-2.0007.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 857845] perl-DateTime-TimeZone-1.51 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=857845

Petr Pisar ppi...@redhat.com changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-DateTime-TimeZone-1.51
   ||-1.fc19

-- 
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 857845] perl-DateTime-TimeZone-1.51 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=857845

--- Comment #3 from Fedora Update System upda...@fedoraproject.org ---
perl-DateTime-TimeZone-1.51-1.fc18 has been submitted as an update for Fedora
18.
https://admin.fedoraproject.org/updates/perl-DateTime-TimeZone-1.51-1.fc18

-- 
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 857845] perl-DateTime-TimeZone-1.51 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=857845

--- Comment #4 from Fedora Update System upda...@fedoraproject.org ---
perl-DateTime-TimeZone-1.51-1.fc17 has been submitted as an update for Fedora
17.
https://admin.fedoraproject.org/updates/perl-DateTime-TimeZone-1.51-1.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 857845] perl-DateTime-TimeZone-1.51 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=857845

--- Comment #5 from Fedora Update System upda...@fedoraproject.org ---
perl-DateTime-TimeZone-1.51-1.fc16 has been submitted as an update for Fedora
16.
https://admin.fedoraproject.org/updates/perl-DateTime-TimeZone-1.51-1.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 838120] perl-DateTime is too old

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=838120

Petr Pisar ppi...@redhat.com changed:

   What|Removed |Added

   Assignee|st...@silug.org |ppi...@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 867753] perl-XML-LibXML-2.0007 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=867753

Petr Šabata psab...@redhat.com changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-XML-LibXML-2.0007-1.fc
   ||19
 Resolution|--- |RAWHIDE
Last Closed||2012-10-18 05:25:17

-- 
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 DateTime-0.77.tar.gz uploaded to lookaside cache by ppisar

[Petr Pisar]

A file has been added to the lookaside cache for perl-DateTime:

1c35bb64f0a261cd3ab4cc161726290a  DateTime-0.77.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-DateTime] 0.77 bump

[Petr Pisar]

commit 50167b2ccf00579f087dc3e5582d0707219fefe0
Author: Petr Písař ppi...@redhat.com
Date:   Thu Oct 18 11:58:30 2012 +0200

0.77 bump

 .gitignore |1 +
 .rpmlint   |2 ++
 perl-DateTime.spec |   32 ++--
 sources|2 +-
 4 files changed, 22 insertions(+), 15 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 965ea31..c4cc360 100644
--- a/.gitignore
+++ b/.gitignore
@@ -13,3 +13,4 @@ DateTime-TimeZone-1.10.tar.gz
 /DateTime-TimeZone-1.34.tar.gz
 /DateTime-0.70.tar.gz
 /DateTime-TimeZone-1.35.tar.gz
+/DateTime-0.77.tar.gz
diff --git a/.rpmlint b/.rpmlint
new file mode 100644
index 000..6486422
--- /dev/null
+++ b/.rpmlint
@@ -0,0 +1,2 @@
+from Config import *
+addFilter(spelling-error .* proleptic);
diff --git a/perl-DateTime.spec b/perl-DateTime.spec
index 2b38913..1f8fa01 100644
--- a/perl-DateTime.spec
+++ b/perl-DateTime.spec
@@ -1,36 +1,39 @@
 Name:   perl-DateTime
 Epoch:  2
-Version:0.70
-Release:5%{?dist}
+Version:0.77
+Release:1%{?dist}
 Summary:Date and time object
 License:Artistic 2.0
 Group:  Development/Libraries
 URL:http://search.cpan.org/dist/DateTime/
 Source0:
http://www.cpan.org/authors/id/D/DR/DROLSKY/DateTime-%{version}.tar.gz
-# circular dependency - only used for one test
-#BuildRequires:  perl(DateTime::Format::Strptime) = 1.2000
+BuildRequires:  perl(Module::Build)
+# Run-time:
 BuildRequires:  perl(base)
+BuildRequires:  perl(Carp)
 BuildRequires:  perl(constant)
 BuildRequires:  perl(DateTime::Locale) = 0.41
 BuildRequires:  perl(DateTime::TimeZone) = 1.09
 BuildRequires:  perl(Math::Round)
-BuildRequires:  perl(Module::Build)
 BuildRequires:  perl(Params::Validate) = 0.76
 BuildRequires:  perl(Scalar::Util)
-BuildRequires:  perl(Test::Exception)
-BuildRequires:  perl(Test::More) = 0.88
-BuildRequires:  perl(Time::Local) = 1.04
 BuildRequires:  perl(XSLoader)
-Requires:   perl(DateTime::Locale) = 0.41
-Requires:   perl(DateTime::TimeZone) = 1.09
-Requires:   perl(XSLoader)
+# Tests:
+BuildRequires:  perl(Test::More) = 0.88
+# Optional tests:
+# circular dependency - perl(DateTime::Format::Strptime) = 1.2000
+BuildRequires:  perl(Storable)
+BuildRequires:  perl(Test::Fatal)
 Requires:   perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo 
$version))
+Requires:   perl(XSLoader)
 
 # not automatically detected
 Provides:   perl(DateTimePP) = %{version}
 Provides:   perl(DateTimePPExtra) = %{version}
 
 %{?perl_default_filter}
+# Filter under-specified dependencies
+%global __requires_exclude 
%{?__requires_exclude:%__requires_exclude|}^perl\\((DateTime::TimeZone|Params::Validate)\\)$
 
 %description
 DateTime is a class for the representation of date/time combinations.  It
@@ -50,12 +53,10 @@ believed to be the birth of Jesus Christ.
 %install
 ./Build install destdir=%{buildroot} create_packlist=0
 find %{buildroot} -type f -name '*.bs' -size 0 -exec rm -f {} \;
-find %{buildroot} -depth -type d -exec rmdir {} 2/dev/null \;
-
 %{_fixperms} %{buildroot}/*
 
 %check
-RELEASE_TESTING=1 ./Build test
+./Build test
 
 %files
 %doc Changes CREDITS LICENSE README TODO
@@ -64,6 +65,9 @@ RELEASE_TESTING=1 ./Build test
 %{_mandir}/man3/*
 
 %changelog
+* Thu Oct 18 2012 Petr Pisar ppi...@redhat.com - 2:0.77-1
+- 0.77 bump
+
 * Fri Jul 20 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org 
- 2:0.70-5
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
 
diff --git a/sources b/sources
index 823b718..aaf7b0a 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-228a3ca93b49e308fc7a3b7a47341ab3  DateTime-0.70.tar.gz
+1c35bb64f0a261cd3ab4cc161726290a  DateTime-0.77.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-DateTime/f18] 0.77 bump

[Petr Pisar]

Summary of changes:

  50167b2... 0.77 bump (*)

(*) 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-DateTime/f17] 0.77 bump

[Petr Pisar]

commit c1dcc908609be21037650817634b468a58e451c6
Author: Petr Písař ppi...@redhat.com
Date:   Thu Oct 18 11:58:30 2012 +0200

0.77 bump

 .gitignore |1 +
 .rpmlint   |2 ++
 perl-DateTime.spec |   32 ++--
 sources|2 +-
 4 files changed, 22 insertions(+), 15 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 965ea31..c4cc360 100644
--- a/.gitignore
+++ b/.gitignore
@@ -13,3 +13,4 @@ DateTime-TimeZone-1.10.tar.gz
 /DateTime-TimeZone-1.34.tar.gz
 /DateTime-0.70.tar.gz
 /DateTime-TimeZone-1.35.tar.gz
+/DateTime-0.77.tar.gz
diff --git a/.rpmlint b/.rpmlint
new file mode 100644
index 000..6486422
--- /dev/null
+++ b/.rpmlint
@@ -0,0 +1,2 @@
+from Config import *
+addFilter(spelling-error .* proleptic);
diff --git a/perl-DateTime.spec b/perl-DateTime.spec
index 24cf770..5689991 100644
--- a/perl-DateTime.spec
+++ b/perl-DateTime.spec
@@ -1,36 +1,39 @@
 Name:   perl-DateTime
 Epoch:  2
-Version:0.70
-Release:3%{?dist}
+Version:0.77
+Release:1%{?dist}
 Summary:Date and time object
 License:Artistic 2.0
 Group:  Development/Libraries
 URL:http://search.cpan.org/dist/DateTime/
 Source0:
http://www.cpan.org/authors/id/D/DR/DROLSKY/DateTime-%{version}.tar.gz
-# circular dependency - only used for one test
-#BuildRequires:  perl(DateTime::Format::Strptime) = 1.2000
+BuildRequires:  perl(Module::Build)
+# Run-time:
 BuildRequires:  perl(base)
+BuildRequires:  perl(Carp)
 BuildRequires:  perl(constant)
 BuildRequires:  perl(DateTime::Locale) = 0.41
 BuildRequires:  perl(DateTime::TimeZone) = 1.09
 BuildRequires:  perl(Math::Round)
-BuildRequires:  perl(Module::Build)
 BuildRequires:  perl(Params::Validate) = 0.76
 BuildRequires:  perl(Scalar::Util)
-BuildRequires:  perl(Test::Exception)
-BuildRequires:  perl(Test::More) = 0.88
-BuildRequires:  perl(Time::Local) = 1.04
 BuildRequires:  perl(XSLoader)
-Requires:   perl(DateTime::Locale) = 0.41
-Requires:   perl(DateTime::TimeZone) = 1.09
-Requires:   perl(XSLoader)
+# Tests:
+BuildRequires:  perl(Test::More) = 0.88
+# Optional tests:
+# circular dependency - perl(DateTime::Format::Strptime) = 1.2000
+BuildRequires:  perl(Storable)
+BuildRequires:  perl(Test::Fatal)
 Requires:   perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo 
$version))
+Requires:   perl(XSLoader)
 
 # not automatically detected
 Provides:   perl(DateTimePP) = %{version}
 Provides:   perl(DateTimePPExtra) = %{version}
 
 %{?perl_default_filter}
+# Filter under-specified dependencies
+%global __requires_exclude 
%{?__requires_exclude:%__requires_exclude|}^perl\\((DateTime::TimeZone|Params::Validate)\\)$
 
 %description
 DateTime is a class for the representation of date/time combinations.  It
@@ -50,12 +53,10 @@ believed to be the birth of Jesus Christ.
 %install
 ./Build install destdir=%{buildroot} create_packlist=0
 find %{buildroot} -type f -name '*.bs' -size 0 -exec rm -f {} \;
-find %{buildroot} -depth -type d -exec rmdir {} 2/dev/null \;
-
 %{_fixperms} %{buildroot}/*
 
 %check
-RELEASE_TESTING=1 ./Build test
+./Build test
 
 %files
 %doc Changes CREDITS LICENSE README TODO
@@ -64,6 +65,9 @@ RELEASE_TESTING=1 ./Build test
 %{_mandir}/man3/*
 
 %changelog
+* Thu Oct 18 2012 Petr Pisar ppi...@redhat.com - 2:0.77-1
+- 0.77 bump
+
 * Fri Jan 13 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org 
- 2:0.70-3
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild
 
diff --git a/sources b/sources
index 823b718..aaf7b0a 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-228a3ca93b49e308fc7a3b7a47341ab3  DateTime-0.70.tar.gz
+1c35bb64f0a261cd3ab4cc161726290a  DateTime-0.77.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 838120] perl-DateTime is too old

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=838120

Petr Pisar ppi...@redhat.com changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-DateTime-0.77-1.fc19

-- 
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 838120] perl-DateTime is too old

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=838120

--- Comment #6 from Fedora Update System upda...@fedoraproject.org ---
perl-DateTime-0.77-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/perl-DateTime-0.77-1.fc18

-- 
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 838120] perl-DateTime is too old

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=838120

--- Comment #7 from Fedora Update System upda...@fedoraproject.org ---
perl-DateTime-0.77-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/perl-DateTime-0.77-1.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 838120] perl-DateTime is too old

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=838120

--- Comment #8 from Fedora Update System upda...@fedoraproject.org ---
perl-DateTime-0.77-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/perl-DateTime-0.77-1.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

Broken dependencies: perl-OpenOffice-UNO

[buildsys]

perl-OpenOffice-UNO has broken dependencies in the F-18 tree:
On x86_64:
perl-OpenOffice-UNO-0.07-3.fc17.x86_64 requires 
perl(:MODULE_COMPAT_5.14.2)
On i386:
perl-OpenOffice-UNO-0.07-3.fc17.i686 requires 
perl(:MODULE_COMPAT_5.14.2)
perl-OpenOffice-UNO-0.07-3.fc17.i686 requires libsal_textenc.so
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

[perl-Devel-CheckLib] Specify all dependencies

[Petr Pisar]

commit b9caeb99ca3770c5cea4777b41de175582f5cdde
Author: Petr Písař ppi...@redhat.com
Date:   Thu Oct 18 14:57:28 2012 +0200

Specify all dependencies

 perl-Devel-CheckLib.spec |   14 +-
 1 files changed, 13 insertions(+), 1 deletions(-)
---
diff --git a/perl-Devel-CheckLib.spec b/perl-Devel-CheckLib.spec
index b83afec..acfcc12 100644
--- a/perl-Devel-CheckLib.spec
+++ b/perl-Devel-CheckLib.spec
@@ -1,6 +1,6 @@
 Name:   perl-Devel-CheckLib
 Version:0.98
-Release:3%{?dist}
+Release:4%{?dist}
 Summary:Check that a library is available
 
 License:GPL+ or Artistic
@@ -11,8 +11,17 @@ Source0:
http://www.cpan.org/modules/by-module/Devel/Devel-CheckLib-%{ver
 BuildArch:  noarch
 
 BuildRequires:  perl(ExtUtils::MakeMaker)
+# Run-time:
+BuildRequires:  perl(Exporter)
 BuildRequires:  perl(File::Spec)
+BuildRequires:  perl(File::Temp) = 0.16
+BuildRequires:  perl(Text::ParseWords)
+# Tests:
+BuildRequires:  perl(Cwd)
+BuildRequires:  perl(File::Spec::Functions)
+BuildRequires:  perl(IO::File)
 BuildRequires:  perl(IO::CaptureOutput) = 1.0801
+BuildRequires:  perl(lib)
 BuildRequires:  perl(Test::More) = 0.62
 
 Requires:   perl(:MODULE_COMPAT_%(eval `%{__perl} -V:version`; echo 
$version))
@@ -52,6 +61,9 @@ rm -rf $RPM_BUILD_ROOT
 %{_mandir}/man3/*.3*
 
 %changelog
+* Thu Oct 18 2012 Petr Pisar ppi...@redhat.com - 0.98-4
+- Specify all dependencies
+
 * Fri Jul 20 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org 
- 0.98-3
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
 
--
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-Devel-CheckLib] Modernize spec file

[Petr Pisar]

commit 83ff69351e16eafc080de21962350485739522d1
Author: Petr Písař ppi...@redhat.com
Date:   Thu Oct 18 14:57:57 2012 +0200

Modernize spec file

 perl-Devel-CheckLib.spec |   10 +-
 1 files changed, 1 insertions(+), 9 deletions(-)
---
diff --git a/perl-Devel-CheckLib.spec b/perl-Devel-CheckLib.spec
index acfcc12..0b5a23c 100644
--- a/perl-Devel-CheckLib.spec
+++ b/perl-Devel-CheckLib.spec
@@ -38,21 +38,13 @@ and its headers are available.
 make %{?_smp_mflags}
 
 %install
-rm -rf $RPM_BUILD_ROOT
-
-make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
-
+make pure_install DESTDIR=$RPM_BUILD_ROOT
 find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
-find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2/dev/null \;
-
 %{_fixperms} $RPM_BUILD_ROOT/*
 
 %check
 make test
 
-%clean
-rm -rf $RPM_BUILD_ROOT
-
 %files
 %doc CHANGES README
 %{_bindir}/*
--
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-Devel-CheckLib] Package TODO

[Petr Pisar]

commit 91e7189ef8ce4deb186f823685165b3a385446d9
Author: Petr Písař ppi...@redhat.com
Date:   Thu Oct 18 14:58:54 2012 +0200

Package TODO

 perl-Devel-CheckLib.spec |3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
---
diff --git a/perl-Devel-CheckLib.spec b/perl-Devel-CheckLib.spec
index 0b5a23c..cdfa35c 100644
--- a/perl-Devel-CheckLib.spec
+++ b/perl-Devel-CheckLib.spec
@@ -46,7 +46,7 @@ find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
 make test
 
 %files
-%doc CHANGES README
+%doc CHANGES README TODO
 %{_bindir}/*
 %{perl_vendorlib}/Devel*
 %{_mandir}/man1/*.1*
@@ -55,6 +55,7 @@ make test
 %changelog
 * Thu Oct 18 2012 Petr Pisar ppi...@redhat.com - 0.98-4
 - Specify all dependencies
+- Package TODO
 
 * Fri Jul 20 2012 Fedora Release Engineering rel-...@lists.fedoraproject.org 
- 0.98-3
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
--
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-OpenOffice-UNO

[buildsys]

perl-OpenOffice-UNO has broken dependencies in the rawhide tree:
On x86_64:
perl-OpenOffice-UNO-0.07-3.fc17.x86_64 requires 
perl(:MODULE_COMPAT_5.14.2)
On i386:
perl-OpenOffice-UNO-0.07-3.fc17.i686 requires 
perl(:MODULE_COMPAT_5.14.2)
perl-OpenOffice-UNO-0.07-3.fc17.i686 requires libsal_textenc.so
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

[perl/f17] Do not crash when vivifying $|

[Jitka Plesnikova]

commit 67c66444384247011fbf2749b1c65a8f2a1f9f14
Author: Jitka Plesnikova jples...@redhat.com
Date:   Thu Oct 18 15:21:24 2012 +0200

Do not crash when vivifying $|

 1-perl-115206-Don-t-crash-when-vivifying.patch |   51 
 perl.spec  |   10 -
 2 files changed, 60 insertions(+), 1 deletions(-)
---
diff --git a/perl-5.16.1-perl-115206-Don-t-crash-when-vivifying.patch 
b/perl-5.16.1-perl-115206-Don-t-crash-when-vivifying.patch
new file mode 100644
index 000..3b6a213
--- /dev/null
+++ b/perl-5.16.1-perl-115206-Don-t-crash-when-vivifying.patch
@@ -0,0 +1,51 @@
+diff --git a/gv.c b/gv.c
+index f352452..cf02ca4 100644
+--- a/gv.c
 b/gv.c
+@@ -1504,10 +1504,6 @@ Perl_gv_fetchpvn_flags(pTHX_ const char
+   Perl_ck_warner_d(aTHX_ packWARN2(WARN_DEPRECATED, WARN_SYNTAX),
+$%c is no longer supported, *name);
+   break;
+-  case '|':   /* $| */
+-  sv_setiv(GvSVn(gv), (IV)(IoFLAGS(GvIOp(PL_defoutgv))  IOf_FLUSH) 
!= 0);
+-  goto magicalize;
+-
+   case '\010':/* $^H */
+   {
+   HV *const hv = GvHVn(gv);
+@@ -1540,6 +1536,7 @@ Perl_gv_fetchpvn_flags(pTHX_ const char
+   case '':   /* $ */
+   case '\\':  /* $\ */
+   case '/':   /* $/ */
++  case '|':   /* $| */
+   case '\001':/* $^A */
+   case '\003':/* $^C */
+   case '\004':/* $^D */
+diff --git a/t/op/magic.t b/t/op/magic.t
+index 3fb1ea1..1bcfbd9 100644
+--- a/t/op/magic.t
 b/t/op/magic.t
+@@ -12,7 +12,7 @@ BEGIN {
+ use warnings;
+ use Config;
+ 
+-plan (tests = 87);
++plan (tests = 88);
+ 
+ $Is_MSWin32  = $^O eq 'MSWin32';
+ $Is_NetWare  = $^O eq 'NetWare';
+@@ -471,6 +471,11 @@ foreach my $sig (qw(__DIE__ _BOGUS_HOOK
+ 
+ }
+ 
++# $|
++fresh_perl_is
++ 'select f; undef *f; ${q/|/}; print STDOUT qq|ok\n|', ok\n, {}, 
++ '[perl #115206] no crash when vivifying $| while *{+select}{IO} is undef';
++
+ # ^ New tests go here ^
+ 
+ SKIP: {
+-- 
+1.7.7.6
+
diff --git a/perl.spec b/perl.spec
index 4cddecf..98c8d1b 100644
--- a/perl.spec
+++ b/perl.spec
@@ -24,7 +24,7 @@
 Name:   perl
 Version:%{perl_version}
 # release number must be even higher, because dual-lived modules will be 
broken otherwise
-Release:216%{?dist}
+Release:217%{?dist}
 Epoch:  %{perl_epoch}
 Summary:Practical Extraction and Report Language
 Group:  Development/Languages
@@ -101,6 +101,9 @@ Patch17:
perl-5.14.2-RT-113730-should-be-cleared-on-do-IO-error.patch
 # Do not truncate syscall() return value to 32 bits, rhbz#838551, RT#113980
 Patch18:
perl-5.16.1-perl-113980-pp_syscall-I32-retval-truncates-the-retu.patch
 
+# Do not crash when vivifying $|, rhbz#865296, RT#115206
+Patch19:perl-5.16.1-perl-115206-Don-t-crash-when-vivifying.patch
+
 # Free hash entries before values on delete, rhbz#771303, RT#100340
 Patch20:
perl-5.14.2-perl-100340-Free-hash-entries-before-values-on-delet.patch
 
@@ -1277,6 +1280,7 @@ tarball from perl.org.
 %patch16 -p1
 %patch17 -p1
 %patch18 -p1
+%patch19 -p1
 %patch20 -p1
 %patch21 -p1
 
@@ -1486,6 +1490,7 @@ pushd %{build_archlib}/CORE/
 'Fedora Patch16: Fix find2perl to translate ? glob properly (RT#113054)' \
 'Fedora Patch17: Clear $@ before do I/O error (RT#113730)' \
 'Fedora Patch18: Do not truncate syscall() return value to 32 bits 
(RT#113980)' \
+'Fedora Patch19: Do not crash when vivifying $|' \
 'Fedora Patch20: Free hash entries before values on delete (RT#100340)' \
 'Fedora Patch21: Override the Pod::Simple::parse_file (CPANRT#77530)' \
 %{nil}
@@ -2439,6 +2444,9 @@ sed \
 
 # Old changelog entries are preserved in CVS.
 %changelog
+* Wed Oct 17 2012 Jitka Plesnikova jples...@redhat.com - 4:5.14.3-217
+- Do not crash when vivifying $| (bug #865296)
+
 * Mon Oct 15 2012 Jitka Plesnikova jples...@redhat.com - 4:5.14.3-216
 - 5.14.3 bump (see
   https://metacpan.org/module/DOM/perl-5.14.3/pod/perldelta.pod for release
--
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 865296] Setting OUTPUT_AUTOFLUSH in eval when STDOUT is localized in upper scope leads to segmentation fault

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=865296

--- Comment #2 from Fedora Update System upda...@fedoraproject.org ---
perl-5.14.3-217.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/perl-5.14.3-217.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 865296] Setting OUTPUT_AUTOFLUSH in eval when STDOUT is localized in upper scope leads to segmentation fault

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=865296

--- Comment #3 from Fedora Update System upda...@fedoraproject.org ---
Package perl-5.16.1-233.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing perl-5.16.1-233.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16405/perl-5.16.1-233.fc18
then log in and leave karma (feedback).

-- 
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