Re: Fedora 20 RC1 AMIs

2013-12-14 Thread Dennis Gilmore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

El Fri, 13 Dec 2013 23:13:01 -0500
Matthew Miller mat...@mattdm.org escribió:
 On Fri, Dec 13, 2013 at 10:05:05PM -0600, Dennis Gilmore wrote:
Note, these are the GA images.
   Hey Dennis, will the images going to mirrors be these or the ones
   with the extra RC1.1 dot, like
   Fedora-x86_64-20-20131211.1-sda.qcow2?
  The Images in RC1 and RC1.1 are exactly the same. the changes in the
  RC1.1 compose was just to respin the install tree making sure that
  none of the older libreoffice packages were in the tree.
 
 Right, sorry, I wasn't clear. I know that part, but I'm wondering
 what the actual filename going to the mirrors will be. This is
 important for the web site and short links.

We do not change file names when composed. what they are in the RC is
what they will be when shipped.

Dennis
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJSrBvwAAoJEH7ltONmPFDR1wgP/2zX6H9Tvp8WEuiHBo5n1rLp
N8sJSJ5VrtR26tqtCEI5DHaujOHjGTwEPMP/QZqXTomm6gQVg6/cgcalL8d8PV+r
/3Cx2epQxX28/ln4xVLI+3PdMXVErl01hEXVnXmAbuwdToUhi1jiDmbDVcpnAUv7
ibwqBn6V3nbk4ThCbfu1Wy2zRHR0qAFo689dsum/mlZPpU7ZelwqcQ7iOimpHvL7
ZwQ38rG1oLJZ0EfW7oe97w8pksn8mCOXdB+DIA17IEMlMWao4cxQ8SAXNsfyyx7l
jwFuPHKAlb0kmDLaqqVljpzx+J7Zibe0aIImbXQ5cDFyiC1ZmRwR9ed2P0SzIscJ
hIL9CPPi0I0nd+dxlIlTGbqu9sRddRVl3O6p4RVsizrrTJ9zF4Ft/MOWBrShlSsP
RnrqiFGR29hP9d/XGA+N0WRFeFfLdrxknrVtIfzV6e8kYgHvdeWh/yRt4WmZDJ8V
5kc84uBBxL/CFZWBrhNbnZmEkoH8qEyrzXkVp6q+ePsGBWROHSX3Gt4eu8TNFsoS
AZtXSfg8tSZnash6nCdTqcEuA0Avc6RA00SaUNHplQlpN8D42MyvCgNeWZNUyZta
+IwOll7skZUIcPvxgnnHpqyhEfJLP+UeYX0+2QPx9/YnupAyiMQDDTOErZCrZdzs
ClvuHNedf0dQLC2kVSHj
=UzA+
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Help needed with systemd script

2013-12-14 Thread Mattia Verga

Hello,
I'm trying to give a user access rights to X with xhost command.
I've created a script named '/usr/bin/boincxhost' (chmod 555) like this:

/#!/bin/sh//
//xhost +SI:localuser:boinc  /dev/null//
//exit 0/

If I run it from command line it works fine.
But I want to run from a systemd unit at startup. So I added this line 
to the unit file:


/ExecStartPre=/usr/bin/boincxhost/

The service starts without errors, but I cannot find the user to have 
rights for accessing X. Maybe someone can tell me where I'm wrong in the 
procedure? Or is there any other way to give that user access to X? I 
already tried to add the user to the 'video' group, but Boinc refuse to 
see the GPU available.

Thanks for any hint.

Mattia
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Help needed with systemd script

2013-12-14 Thread Dridi Boukelmoune
Hi,

On Sat, Dec 14, 2013 at 12:44 PM, Mattia Verga mattia.ve...@tiscali.it wrote:
 Hello,
 I'm trying to give a user access rights to X with xhost command.
 I've created a script named '/usr/bin/boincxhost' (chmod 555) like this:

 #!/bin/sh
 xhost +SI:localuser:boinc  /dev/null
 exit 0

exit 0 will hide a non-zero exit status of the previous command.

In this case I'm not sure what's happening, but if you're running the
command in background, and don't wait for it to complete, you may be
facing a race condition.

 If I run it from command line it works fine.
 But I want to run from a systemd unit at startup. So I added this line to
 the unit file:

 ExecStartPre=/usr/bin/boincxhost

 The service starts without errors, but I cannot find the user to have rights
 for accessing X. Maybe someone can tell me where I'm wrong in the procedure?
 Or is there any other way to give that user access to X? I already tried to
 add the user to the 'video' group, but Boinc refuse to see the GPU
 available.
 Thanks for any hint.

 Mattia

 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Building two packages dependent on each other?

2013-12-14 Thread Michael Schwendt
On Fri, 13 Dec 2013 22:07:21 -0600, Richard Shaw wrote:

 I maintain two package, OpenImageIO and OpenColorIO, which can optionally
 depend on each other. During the review process I intentionally decided
 that it was more important for OpenImageIO to depend on OpenColorIO as it
 uses the latter for color management.
 
 OpenColorIO is not a library, but a binary requirement. It can optionally
 build two binaries that use OpenImageIO. Until now this has not been a
 problem but now I have gotten a request to build the binaries.
 
 This almost seems to be bootstrapping but I'm not quite sure I need to go
 that far...
 
 Since both are established packages, if one is updated, wouldn't the only
 consequence be that once I build the updated package, I would need to also
 rebuild the other package (after adding the former as a buildroot override).
 
 Am I missing something, or is it that easy?

It may be even easier. You only need a buildroot override, if the
build of OpenImageIO that's available in the buildroot (since it has
been published before) is not API-compatible with what OpenColorIO wants.
For future updates/upgrades of OpenImageIO, rebuilds of OpenColorIO would
only be needed for ABI/API changes in OpenImageIO.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Building two packages dependent on each other?

2013-12-14 Thread Richard Shaw
On Sat, Dec 14, 2013 at 5:56 AM, Michael Schwendt mschwe...@gmail.comwrote:

 On Fri, 13 Dec 2013 22:07:21 -0600, Richard Shaw wrote:

  I maintain two package, OpenImageIO and OpenColorIO, which can optionally
  depend on each other. During the review process I intentionally decided
  that it was more important for OpenImageIO to depend on OpenColorIO as it
  uses the latter for color management.
 
  OpenColorIO is not a library, but a binary requirement. It can optionally
  build two binaries that use OpenImageIO. Until now this has not been a
  problem but now I have gotten a request to build the binaries.


Ok, I slightly misspoke here, OpenColorIO is a library, but the only
dependency on OpenImageIO is from the utility binaries...


 
  This almost seems to be bootstrapping but I'm not quite sure I need to go
  that far...
 
  Since both are established packages, if one is updated, wouldn't the only
  consequence be that once I build the updated package, I would need to
 also
  rebuild the other package (after adding the former as a buildroot
 override).
 
  Am I missing something, or is it that easy?

 It may be even easier. You only need a buildroot override, if the
 build of OpenImageIO that's available in the buildroot (since it has
 been published before) is not API-compatible with what OpenColorIO wants.
 For future updates/upgrades of OpenImageIO, rebuilds of OpenColorIO would
 only be needed for ABI/API changes in OpenImageIO.


Thanks! I was hoping it was that easy. Upstream is pretty good about not
breaking API/ABI but I usually check with abi-compliance-checker anyway
since OpenImageIO is needed by blender and I'm not the primary maintainer
for it.

Thanks,
Richard
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: really stop really commits (really!)

2013-12-14 Thread Miro Hrončok

Dne 14.12.2013 02:42, T.C. Hollingsworth napsal(a):

To use it, download it somewhere, make it executable, and symlink
$clone/.git/hooks/pre-commit to it.  If you already have a pre-commit
hook of some sort, you can instead just run that script in it and
abort on a non-zero exit code.


As Rahul somebody already mentioned, it would be great to gave it in 
fedpkg by default.



If that fails from some reason (i.e. fedpkg maintainers are against it), 
what about this.


 * Create a package fedpkg-patch-check with:
   * this script somewhere in libdir
   * command in bindir that would add the check to repo in pwd
   * and that would add the check to all repos specified as arguments

I'm currently trying to draft a script for thiss adding.


Hopefully some of you find it useful.


Yes, it's great. Thanks.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: really stop really commits (really!)

2013-12-14 Thread Miro Hrončok

I'm currently trying to draft a script for thiss adding.


Something like https://gist.github.com/hroncok/7959382

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Help needed with systemd script

2013-12-14 Thread Mattia Verga

Il 14/12/2013 12:55, Dridi Boukelmoune ha scritto:

Hi,

On Sat, Dec 14, 2013 at 12:44 PM, Mattia Verga mattia.ve...@tiscali.it wrote:

Hello,
I'm trying to give a user access rights to X with xhost command.
I've created a script named '/usr/bin/boincxhost' (chmod 555) like this:

#!/bin/sh
xhost +SI:localuser:boinc  /dev/null
exit 0

exit 0 will hide a non-zero exit status of the previous command.

In this case I'm not sure what's happening, but if you're running the
command in background, and don't wait for it to complete, you may be
facing a race condition.



Ok, I tried to edit the boincxhost script in this way:

#!/bin/sh
xhost +SI:localuser:boinc
sleep 1

Now if I run the script from console I get:
$ /usr/bin/boincxhost
localuser:boinc being added to access control list

$ xhost
access control enabled, only authorized clients can connect
SI:localuser:boinc
SI:localuser:marvin

But if I run it within systemd unit the service is started, but xhost 
command silently fails:

# systemctl start boinc-client.service
# systemctl status boinc-client.service
boinc-client.service - Berkeley Open Infrastructure Network Computing Client
   Loaded: loaded (/usr/lib/systemd/system/boinc-client.service; disabled)
   Active: active (running) since sab 2013-12-14 14:52:25 CET; 4s ago
  Process: 2843 ExecStopPost=/bin/rm -f /var/lib/boinc/lockfile 
(code=exited, status=0/SUCCESS)
*Process: 2947 ExecStartPre=/usr/bin/boincxhost (code=exited, 
status=0/SUCCESS)*
  Process: 2944 ExecStartPre=/usr/bin/chown boinc:boinc 
/var/log/boinc.log /var/log/boincerr.log (code=exited, status=0/SUCCESS)
  Process: 2941 ExecStartPre=/usr/bin/touch /var/log/boinc.log 
/var/log/boincerr.log (code=exited, status=0/SUCCESS)

  Process: 2938 ExecStartPre=/bin/sleep 1 (code=exited, status=0/SUCCESS)
 Main PID: 2952 (boinc)
   CGroup: name=systemd:/system/boinc-client.service
   ??2952 /bin/bash /usr/bin/boinc --dir /var/lib/boinc
   ??2953 /usr/bin/boinc_client --allow_multiple_clients --dir 
/var/l...


dic 14 14:52:23 deneb systemd[1]: Starting Berkeley Open Infrastructure 
Net.

*dic 14 14:52:24 deneb boincxhost[2947]: xhost:  unable to open display *
dic 14 14:52:25 deneb systemd[1]: Started Berkeley Open Infrastructure 
Netw...t.


# xhost
access control enabled, only authorized clients can connect
SI:localuser:marvin


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Help needed with systemd script

2013-12-14 Thread Alec Leamas

On 2013-12-14 15:00, Mattia Verga wrote:

Il 14/12/2013 12:55, Dridi Boukelmoune ha scritto:

Hi,

On Sat, Dec 14, 2013 at 12:44 PM, Mattia Vergamattia.ve...@tiscali.it  wrote:

Hello,
I'm trying to give a user access rights to X with xhost command.
I've created a script named '/usr/bin/boincxhost' (chmod 555) like this:

#!/bin/sh
xhost +SI:localuser:boinc  /dev/null
exit 0

exit 0 will hide a non-zero exit status of the previous command.

In this case I'm not sure what's happening, but if you're running the
command in background, and don't wait for it to complete, you may be
facing a race condition.



Ok, I tried to edit the boincxhost script in this way:

#!/bin/sh
xhost +SI:localuser:boinc
sleep 1

Now if I run the script from console I get:
$ /usr/bin/boincxhost
localuser:boinc being added to access control list

$ xhost
access control enabled, only authorized clients can connect
SI:localuser:boinc
SI:localuser:marvin

But if I run it within systemd unit the service is started, but xhost 
command silently fails:

# systemctl start boinc-client.service
# systemctl status boinc-client.service
boinc-client.service - Berkeley Open Infrastructure Network Computing 
Client

   Loaded: loaded (/usr/lib/systemd/system/boinc-client.service; disabled)
   Active: active (running) since sab 2013-12-14 14:52:25 CET; 4s ago
  Process: 2843 ExecStopPost=/bin/rm -f /var/lib/boinc/lockfile 
(code=exited, status=0/SUCCESS)
*Process: 2947 ExecStartPre=/usr/bin/boincxhost (code=exited, 
status=0/SUCCESS)*
  Process: 2944 ExecStartPre=/usr/bin/chown boinc:boinc 
/var/log/boinc.log /var/log/boincerr.log (code=exited, status=0/SUCCESS)
  Process: 2941 ExecStartPre=/usr/bin/touch /var/log/boinc.log 
/var/log/boincerr.log (code=exited, status=0/SUCCESS)

  Process: 2938 ExecStartPre=/bin/sleep 1 (code=exited, status=0/SUCCESS)
 Main PID: 2952 (boinc)
   CGroup: name=systemd:/system/boinc-client.service
   ├─2952 /bin/bash /usr/bin/boinc --dir /var/lib/boinc
   └─2953 /usr/bin/boinc_client --allow_multiple_clients --dir 
/var/l...


dic 14 14:52:23 deneb systemd[1]: Starting Berkeley Open 
Infrastructure Net.
*dic 14 14:52:24 deneb boincxhost[2947]: xhost:  unable to open 
display *
dic 14 14:52:25 deneb systemd[1]: Started Berkeley Open Infrastructure 
Netw...t.


# xhost
access control enabled, only authorized clients can connect
SI:localuser:marvin




I really wonder if $DISPLAY is defined within systemd's execution 
context.  IMHO, it shouldn't E. g.,  try adding


exec  /tmp/boincxhost.log
set -x

at the top of your script. That should give debug output from the 
script. I'd presume there is some error message when run from systemd.


Or, I'm just plain wrong. Dunno :)

--alec
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Help needed with systemd script

2013-12-14 Thread Dridi Boukelmoune
On Sat, Dec 14, 2013 at 3:00 PM, Mattia Verga mattia.ve...@tiscali.it wrote:
 Il 14/12/2013 12:55, Dridi Boukelmoune ha scritto:

 Hi,

 On Sat, Dec 14, 2013 at 12:44 PM, Mattia Verga mattia.ve...@tiscali.it
 wrote:

 Hello,
 I'm trying to give a user access rights to X with xhost command.
 I've created a script named '/usr/bin/boincxhost' (chmod 555) like this:

 #!/bin/sh
 xhost +SI:localuser:boinc  /dev/null
 exit 0

 exit 0 will hide a non-zero exit status of the previous command.

 In this case I'm not sure what's happening, but if you're running the
 command in background, and don't wait for it to complete, you may be
 facing a race condition.


 Ok, I tried to edit the boincxhost script in this way:

 #!/bin/sh
 xhost +SI:localuser:boinc
 sleep 1

This time it's the sleep command that will override the xhost exit
status. Since you're running xhost in foreground, you shoudn't need to
sleep at all.

In general, if you have several commands in a script, but you want it
to abort as soon as one command fail, you can:
- run it with sh -e
- add set -e in your script

This is a one-command script, so you can simply run xhost, and the
shell exit status should be xhost's exit status. Btw, do you really
need a script ? Can't systemd handle something like:
ExecStartPre=/usr/bin/xhost +SI:localuser:boinc

 Now if I run the script from console I get:
 $ /usr/bin/boincxhost
 localuser:boinc being added to access control list

 $ xhost
 access control enabled, only authorized clients can connect
 SI:localuser:boinc
 SI:localuser:marvin

 But if I run it within systemd unit the service is started, but xhost
 command silently fails:
 # systemctl start boinc-client.service
 # systemctl status boinc-client.service
 boinc-client.service - Berkeley Open Infrastructure Network Computing Client
Loaded: loaded (/usr/lib/systemd/system/boinc-client.service; disabled)
Active: active (running) since sab 2013-12-14 14:52:25 CET; 4s ago
   Process: 2843 ExecStopPost=/bin/rm -f /var/lib/boinc/lockfile
 (code=exited, status=0/SUCCESS)
   Process: 2947 ExecStartPre=/usr/bin/boincxhost (code=exited,
 status=0/SUCCESS)
   Process: 2944 ExecStartPre=/usr/bin/chown boinc:boinc /var/log/boinc.log
 /var/log/boincerr.log (code=exited, status=0/SUCCESS)
   Process: 2941 ExecStartPre=/usr/bin/touch /var/log/boinc.log
 /var/log/boincerr.log (code=exited, status=0/SUCCESS)
   Process: 2938 ExecStartPre=/bin/sleep 1 (code=exited, status=0/SUCCESS)
  Main PID: 2952 (boinc)
CGroup: name=systemd:/system/boinc-client.service
├─2952 /bin/bash /usr/bin/boinc --dir /var/lib/boinc
└─2953 /usr/bin/boinc_client --allow_multiple_clients --dir
 /var/l...

 dic 14 14:52:23 deneb systemd[1]: Starting Berkeley Open Infrastructure
 Net.
 dic 14 14:52:24 deneb boincxhost[2947]: xhost:  unable to open display 
 dic 14 14:52:25 deneb systemd[1]: Started Berkeley Open Infrastructure
 Netw...t.

 # xhost
 access control enabled, only authorized clients can connect
 SI:localuser:marvin



 --
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [Base] Proposal for buildrequires cleanup janitorial initiative

2013-12-14 Thread Ben Boeckel
On Fri, 13 Dec, 2013 at 13:41:55 GMT, Phil Knirsch wrote:
 Yea, I suspect both could be combined though in a script that gradually 
 adds new BRs to a package and then iterates over adding and removing BRs 
 until it produces equivalent output (not identical as thats kinda hard 
 to verify and achieve, but same provides/requires of resulting packages 
 and same filelist at least).

What about BRs which are needed, but the script removes because of
transitive dependencies? IMO, BuildRequires: foo-devel getting you
bar-devel, which is also needed, without listing bar-devel means you now
depend on foo-devel not losing that dependency.

--Ben

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [Base] Proposal for buildrequires cleanup janitorial initiative

2013-12-14 Thread Bruno Wolff III

On Fri, Dec 13, 2013 at 17:25:49 -0800,
  Adam Williamson awill...@redhat.com wrote:


That's still not really enough; that metadata doesn't express anything
*close* to all the possible capabilities of a package. Not saying this
isn't a good idea, just that it should involve careful manual double
checking of compose logs and the like.


Another possible problem is that if package A build requires packages 
B and C and today package B requires C, then this would likely result 
in the build requires for C being dropped. Then if later B no longer 
requires C, this will result in problems. If they are obvious then 
it won't be that big of a deal. But if the build succeeds and the package 
just doesn't work correctly there may be confusion as to why it stopped 
working.

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Help needed with systemd script

2013-12-14 Thread Mattia Verga

This is the log outpu:
+ xhost +SI:localuser:boinc
xhost:  unable to open display 
+ sleep 1


Il 14/12/2013 15:12, Alec Leamas ha scritto:






I really wonder if $DISPLAY is defined within systemd's execution 
context.  IMHO, it shouldn't E. g.,  try adding


exec  /tmp/boincxhost.log
set -x

at the top of your script. That should give debug output from the 
script. I'd presume there is some error message when run from systemd.


Or, I'm just plain wrong. Dunno :)

--alec


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Help needed with systemd script

2013-12-14 Thread Alec Leamas

On 2013-12-14 15:31, Mattia Verga wrote:


Il 14/12/2013 15:12, Alec Leamas ha scritto:






I really wonder if $DISPLAY is defined within systemd's execution 
context.  IMHO, it shouldn't E. g.,  try adding


exec  /tmp/boincxhost.log
set -x

at the top of your script. That should give debug output from the 
script. I'd presume there is some error message when run from systemd.


Or, I'm just plain wrong. Dunno :)

--alec

This is the log output:
+ xhost +SI:localuser:boinc
xhost:  unable to open display 
+ sleep 1

I. e., there's no DISPLAY defined when running the systemd script. I'm 
not sure  there's any easy fix, perhaps some of the elderly have a hint. 
You migh ttry to hardcode it (DISPLAY=:0 xhost...) but that would 
probably lead to permissions problem (or timing,  are you sure the X 
server is uprunning when running this script? systemd's 
parallellization have sometimes surprises ).


Sorry to bring bad news,

--alec

PS: Please don't top-post DS
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Help needed with systemd script

2013-12-14 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Dec 14, 2013 at 04:13:21PM +0100, Alec Leamas wrote:
 On 2013-12-14 15:31, Mattia Verga wrote:
 This is the log output:
 + xhost +SI:localuser:boinc
 xhost:  unable to open display 
 + sleep 1
 
 I. e., there's no DISPLAY defined when running the systemd script.
 I'm not sure  there's any easy fix, perhaps some of the elderly have
 a hint. You migh ttry to hardcode it (DISPLAY=:0 xhost...) but that
 would probably lead to permissions problem (or timing,  are you sure
 the X server is uprunning when running this script? systemd's
 parallellization have sometimes surprises ).
Yeah, this isn't going to work in any robust way.

If you really want to use xhost, it'd be better to run xhost from
whatever starts X.

(And just to clear up some confusion that you need a shell to do
those things, you can set variables with

Environment=DISPLAY=:0
ExecStartPre=/usr/bin/xhost +SI:localuser:boinc
...

or

ExecStartPre=/usr/bin/env DISPLAY=:0 xhost +SI:localuser:boinc
)

Zbyszek

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

gammaray includes qt-everywhere-opensource-src-4.8.5.tar.gz

2013-12-14 Thread Michael Schwendt
 Source1:
 http://releases.qt-project.org/qt4/source/qt-everywhere-opensource-src-%{qt_version}.tar.gz

 BuildRequires:  qt-devel
 BuildRequires:  qt-devel-private

 %cmake . 
 -DQT_PRIVATE_INCLUDE_DIR=%{_builddir}/qt-everywhere-opensource-src-%{qt_version}/include/QtCore

The package review request was: https://bugzilla.redhat.com/905615

Nowhere is a comment that explains why the 230MB Qt source is included
and used to build GammaRay. Isn't qt-devel-private sufficient?
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: gammaray includes qt-everywhere-opensource-src-4.8.5.tar.gz

2013-12-14 Thread Daniel Vrátil
On Saturday 14 of December 2013 19:21:14 Michael Schwendt wrote:
  Source1:   
  http://releases.qt-project.org/qt4/source/qt-everywhere-opensource-src-%{
  qt_version}.tar.gz
  
  BuildRequires:  qt-devel
  BuildRequires:  qt-devel-private
  
  %cmake .
  -DQT_PRIVATE_INCLUDE_DIR=%{_builddir}/qt-everywhere-opensource-src-%{qt_v
  ersion}/include/QtCore
 The package review request was: https://bugzilla.redhat.com/905615
 
 Nowhere is a comment that explains why the 230MB Qt source is included
 and used to build GammaRay. Isn't qt-devel-private sufficient?

Hi

it's documented in the very first comment:

The package needs Qt sources in order to have access to some private headers 
and sources that are not available in qt-devel and qt-devel-private

AFAIK this was necessary to get access to QPainter internals for painter 
introspection, and to build against the harfbuzz shipped with Qt sources.

Cheers,
Dan

-- 
Daniel Vrátil
KDE Desktop Team
Associate Software Engineer, Red Hat, Inc.

GPG Key: 0xC59D614F6F4AE348
Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348

signature.asc
Description: This is a digitally signed message part.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 20 RC1 AMIs

2013-12-14 Thread Matthew Miller
On Sat, Dec 14, 2013 at 02:50:50AM -0600, Dennis Gilmore wrote:
Hey Dennis, will the images going to mirrors be these or the ones
with the extra RC1.1 dot, like
Fedora-x86_64-20-20131211.1-sda.qcow2?
   The Images in RC1 and RC1.1 are exactly the same. the changes in the
   RC1.1 compose was just to respin the install tree making sure that
   none of the older libreoffice packages were in the tree.
  Right, sorry, I wasn't clear. I know that part, but I'm wondering
  what the actual filename going to the mirrors will be. This is
  important for the web site and short links.
 We do not change file names when composed. what they are in the RC is
 what they will be when shipped.

I see that the RC1 tree now alo contains
Fedora-x86_64-20-20131211.1-sda.qcow2 -- I am pretty sure that it was
previously Fedora-x86_64-20-20131211-sda.qcow2, without the .1. That is what
I was referring to.

-- 
Matthew Miller  --  Fedora Project Architect --  mat...@fedoraproject.org
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

General fedpkg git hook support [was: Re: really stop really commits (really!)]

2013-12-14 Thread T.C. Hollingsworth
On Fri, Dec 13, 2013 at 8:35 PM, Rahul Sundaram methe...@gmail.com wrote:
 On Fri, Dec 13, 2013 at 8:42 PM, T.C. Hollingsworth wrote:
 To prevent this from happening in the future, I wrote a little git
 pre-commit hook to help out, which I figured I'd share with you all:
 http://patches.fedorapeople.org/patchcheck.py

 Would it be possible to hook it up with fedpkg by default so that all Fedora
 packagers get this functionality?

Sure.  `fedpkg clone` could easily be taught to install hooks.  Not
sure what to do about existing clones.  (I guess we could provide a
`fedpkg install-hooks` or just require a new clone if you want the new
magic.)

If fedpkg (actually I'd say pyrpkg, I suppose RHEL maintainers would
find this useful too ;-) were to have hook support, I'd much prefer to
add some general support for git hooks to it and include this one as a
default one, rather than just this one specifically.

So it would just symlink a simple script in each clone that executes
everything in some drop-in directory.  (/usr/lib/rpkg/hooks/pre-commit
or so?  If we do it in rpkg do we need a Fedora-specific dir too?
Maybe $XDG_CONFIG_DIR/rpkg/hooks/pre-commit also so packagers can add
their own stuff easily?)  This way rpkg/fedpkg can ship some common
obvious ones and there's an easy way for others to add additional ones
that aren't of interest to the entire packaging community.

Also, I wonder if there are use cases for other hooks.  Pre-commit is
definitely useful, but some of them ([prepare-]commit-msg, update
[which runs prior to a push]) could possibly be relevant.  Might be
overengineering, but I'd hate to go through all the work to enable
pre-commit hooks just for someone to come up with an awesome use-case
for another one three months later.

Anyway, I'd be happy to cook up a patch for this if it would be
something dgilmore is interested in merging.

-T.C.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

idea for installation - web

2013-12-14 Thread חץ בן חמו
Hi,

As a long time Fedora user, I find my self installing Fedora on many
systems, and I thought about an idea about the whole installation process.

IMHO, at the moment, the current installation process is quite ..
confusing. text mode installation has gone, and so VNC method (last I
checked), and we have a graphical installation which has it's own issues
like weird places for buttons, and weirder setup for the disk. Again, it's
only my opinion.

So I thought about it for a long time and I would like to purpose a
different installation method - a web installer.

Think about it - currently Anaconda knows how to detect most of the network
cards (which is what we need to setup IP/Subnet/Gateway/DNS), and everyone
has either a laptop or a tablet or a smartphone. All the other parts that
needs to be added to the installation are small web server (nginx?), and
the HTML/JS and graphics files. All of it won't be bigger then few dozens
of MB to the DVD ISO.

So the web installation will do something simple:

* Upon booting the DVD ISO and selecting web installation, it will detect
the network card and show them so the user could select which network card
to use
* The user will select the card and enter the IP/Subnet Mask/Default
Gateway and the DNS
* The installer will show the user a URL that he can connect to in order to
continue the installation
* The user will connect to this IP using his laptop/tablet/smart phone
through it's web browser.
* The user will select and do all the installation.

Advantages:

* No more graphics issues if you're in a place where you don't have a mouse
or you got some really crappy CRT on a hosting company wanting to install a
new OS.
* There are basically tons of people who would be happy to contribute
either HTML/JS code or graphics for the installer, which could give a
really good look to the installer
* Easier way to install Fedora using your browser
* You don't need to sit in a freezing colo place just to install your OS :-)

What do you think about this idea?

Thanks,
Hetz
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 20 RC1 AMIs

2013-12-14 Thread Dennis Gilmore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

El Sat, 14 Dec 2013 14:22:42 -0500
Matthew Miller mat...@fedoraproject.org escribió:
 On Sat, Dec 14, 2013 at 02:50:50AM -0600, Dennis Gilmore wrote:
 Hey Dennis, will the images going to mirrors be these or the
 ones with the extra RC1.1 dot, like
 Fedora-x86_64-20-20131211.1-sda.qcow2?
The Images in RC1 and RC1.1 are exactly the same. the changes
in the RC1.1 compose was just to respin the install tree making
sure that none of the older libreoffice packages were in the
tree.
   Right, sorry, I wasn't clear. I know that part, but I'm wondering
   what the actual filename going to the mirrors will be. This is
   important for the web site and short links.
  We do not change file names when composed. what they are in the RC
  is what they will be when shipped.
 
 I see that the RC1 tree now alo contains
 Fedora-x86_64-20-20131211.1-sda.qcow2 -- I am pretty sure that it was
 previously Fedora-x86_64-20-20131211-sda.qcow2, without the .1. That
 is what I was referring to.
 

the .1 is refering to the RC that it was. there is issues using just
the date, it clashes with the nightly images for one. if we had done a
rc2 there would have been a .2 at the end.

going forward Im going to name the images as we do for ARM and livecds

Dennis
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJSrNmnAAoJEH7ltONmPFDRLc0P/RqkGeQ/svpoeTkDXIIfyegl
L5lVbuQOB//Tviwq/3uGSt9vaR06EqniKpP9phSdwMxiXO5de0JQe/CAejiQvpsu
Ko/ZwhMznDGCTar+okKs+FjtroC5ZYoHlU7afiAS/ZCo10QPYHsvsmnmccqKmvM9
ZYVUBha0fg++bWZzxXcblzh9kFzB/dny+s+dMpEVhi14kdcq9Fp26ncLmZ/4g1m8
vT/08vFLXA9hrUBDirDJXz3PNdLRZ6GWIoU8cSVdqPEu8bG6os00OxAtuCQyuvvs
/TLjFLQBXmCWwZfebDEQDZu3PFTCBcnHWM3IcHizj3Eauwh9dsa1R8iVAR9hbbMv
iFPHNRoLNxtiUkxNXVVBZJqaulOkyD5/eqBIdqhPMaDX5rIXWz84DMQPjL5FwDbT
//n3tHWIe5Vpco8czaAJJXxFIcKbuEhnxWesIgdXuuXmVdya3ceJdoj6QzR64k+/
xj0xGYXYwxM61rZdxibY3P5a32IGgg8OKkmq+57s8chUNp5xpkq1giDGbQON/C9z
8SKO3Yhmo1ckpfezVy1Mw7sbJ79oiHqVVkMfJVxcX3vPDnZ0TNsn1u5Rsc9btRHf
UF5dVGzDtusthxfzQjv2ToRru+8ebiF8oVp1BVCgSd8hobHuosOoxf0cNf7DaeKG
IA/QRfSEZ4zACly/inpf
=hXgD
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Building two packages dependent on each other?

2013-12-14 Thread Samuel Sieb

On 12/14/2013 05:10 AM, Richard Shaw wrote:

Ok, I slightly misspoke here, OpenColorIO is a library, but the only
dependency on OpenImageIO is from the utility binaries...

Wouldn't it be easier to split the binaries into a sub-package so you 
could avoid the circular dependency?

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Building two packages dependent on each other?

2013-12-14 Thread Richard Shaw
On Sat, Dec 14, 2013 at 5:02 PM, Samuel Sieb sam...@sieb.net wrote:

 On 12/14/2013 05:10 AM, Richard Shaw wrote:

 Ok, I slightly misspoke here, OpenColorIO is a library, but the only
 dependency on OpenImageIO is from the utility binaries...

  Wouldn't it be easier to split the binaries into a sub-package so you
 could avoid the circular dependency?


Sub-package or separate package? A sub-package wouldn't change how anything
it built, it just let's people install the library without pulling in the
binaries. I plan on doing that anyway.

Richard
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: idea for installation - web

2013-12-14 Thread Adam Williamson
On Sat, 2013-12-14 at 23:22 +0200, חץ בן חמו wrote:
 Hi,
 
 
 As a long time Fedora user, I find my self installing Fedora on many
 systems, and I thought about an idea about the whole installation
 process.
 
 
 IMHO, at the moment, the current installation process is quite ..
 confusing. text mode installation has gone,

No it hasn't. Boot with parameter 'text'.

  and so VNC method (last I checked),

No it hasn't. Boot with parameter 'vnc'.

  and we have a graphical installation which has it's own issues like
 weird places for buttons, and weirder setup for the disk. Again, it's
 only my opinion.
 
 
 So I thought about it for a long time and I would like to purpose a
 different installation method - a web installer. 
 
 
 Think about it - currently Anaconda knows how to detect most of the
 network cards (which is what we need to setup IP/Subnet/Gateway/DNS),
 and everyone has either a laptop or a tablet or a smartphone. All the
 other parts that needs to be added to the installation are small web
 server (nginx?), and the HTML/JS and graphics files. All of it won't
 be bigger then few dozens of MB to the DVD ISO.
 
 
 So the web installation will do something simple:
 
 
 * Upon booting the DVD ISO and selecting web installation, it will
 detect the network card and show them so the user could select which
 network card to use
 * The user will select the card and enter the IP/Subnet Mask/Default
 Gateway and the DNS
 * The installer will show the user a URL that he can connect to in
 order to continue the installation
 * The user will connect to this IP using his laptop/tablet/smart phone
 through it's web browser.
 * The user will select and do all the installation.
 
 
 Advantages:
 
 
 * No more graphics issues if you're in a place where you don't have a
 mouse or you got some really crappy CRT on a hosting company wanting
 to install a new OS.
 * There are basically tons of people who would be happy to contribute
 either HTML/JS code or graphics for the installer, which could give a
 really good look to the installer
 * Easier way to install Fedora using your browser
 * You don't need to sit in a freezing colo place just to install your
 OS :-)
 
 
 What do you think about this idea?

I don't think it'll be any use to most people as port 80 won't be open,
and I think you're badly under-estimating the difficulty of writing an
installer UI. I don't think it really provides anything that VNC install
doesn't...
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Bug 1043149] New: /usr/lib/rpm/macros.perl: __find_provides macro point to non existing file

2013-12-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1043149

Bug ID: 1043149
   Summary: /usr/lib/rpm/macros.perl: __find_provides macro point
to non existing file
   Product: Fedora
   Version: 19
 Component: perl-rpm-build-perl
  Severity: low
  Assignee: ppi...@redhat.com
  Reporter: olivier.laha...@free.fr
QA Contact: extras...@fedoraproject.org
CC: mmasl...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com,
psab...@redhat.com



Description of problem:
/usr/lib/rpm/macros.perl: __find_provides macro point to non existing file

Version-Release number of selected component (if applicable):
tested on fc-17 to fc-19 at least

How reproducible:
100%

Steps to Reproduce:

$grep __find_provides /usr/lib/rpm/macros.perl

$ rpm --eval '%{_rpmconfigdir}/find-perl-provides'
/usr/lib/rpm/find-perl-provides

$ LC_ALL=C ls /usr/lib/rpm/find-perl-provides
ls: cannot access /usr/lib/rpm/find-perl-provides: No such file or directory
Actual results:


Expected results:
Point to the adequate helper script

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=4w3Ot9zWNNa=cc_unsubscribe
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

File Digest-Perl-MD5-1.9.tar.gz uploaded to lookaside cache by pghmcfc

2013-12-14 Thread Paul Howarth
A file has been added to the lookaside cache for perl-Digest-Perl-MD5:

41f1160e11ce0d99021fc8d6c725fa3d  Digest-Perl-MD5-1.9.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-Digest-Perl-MD5] Update to 1.9

2013-12-14 Thread Paul Howarth
commit 2ad04f92544934a13917367f1ec730500bec0456
Author: Paul Howarth p...@city-fan.org
Date:   Sat Dec 14 20:24:25 2013 +

Update to 1.9

- New upstream release 1.9
  - Don't clobber $_ (CPAN RT#78392)
  - Typo fixes (CPAN RT#86853)
  - Remove /usr/bin/false shebang (CPAN RT#85872)
- Don't need to remove empty directories from the buildroot
- Upstream dropped README file (probably unintentionally)

 perl-Digest-Perl-MD5.spec |   17 -
 sources   |2 +-
 2 files changed, 13 insertions(+), 6 deletions(-)
---
diff --git a/perl-Digest-Perl-MD5.spec b/perl-Digest-Perl-MD5.spec
index af443b2..952ef3d 100644
--- a/perl-Digest-Perl-MD5.spec
+++ b/perl-Digest-Perl-MD5.spec
@@ -1,6 +1,6 @@
 Name:  perl-Digest-Perl-MD5
-Version:   1.8
-Release:   8%{?dist}
+Version:   1.9
+Release:   1%{?dist}
 Summary:   Perl implementation of Ron Rivest's MD5 Algorithm
 Group: Development/Libraries
 License:   GPL+ or Artistic
@@ -20,7 +20,7 @@ A pure-perl implementation of Ron Rivest's MD5 Algorithm.
 %setup -q -n Digest-Perl-MD5-%{version}
 
 # Remove spurious exec permissions
-chmod -c -x README lib/Digest/Perl/MD5.pm
+chmod -c -x lib/Digest/Perl/MD5.pm
 
 %build
 perl Makefile.PL INSTALLDIRS=vendor
@@ -30,7 +30,6 @@ make %{?_smp_mflags}
 rm -rf %{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
@@ -41,11 +40,19 @@ rm -rf %{buildroot}
 
 %files
 %defattr(-,root,root,-)
-%doc CHANGES README
+%doc CHANGES
 %{perl_vendorlib}/Digest/
 %{_mandir}/man3/Digest::Perl::MD5.3pm*
 
 %changelog
+* Sat Dec 14 2013 Paul Howarth p...@city-fan.org - 1.9-1
+- Update to 1.9
+  - Don't clobber $_ (CPAN RT#78392)
+  - Typo fixes (CPAN RT#86853)
+  - Remove /usr/bin/false shebang (CPAN RT#85872)
+- Don't need to remove empty directories from the buildroot
+- Upstream dropped README file (probably unintentionally)
+
 * Sat Aug 03 2013 Fedora Release Engineering rel-...@lists.fedoraproject.org 
- 1.8-8
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
 
diff --git a/sources b/sources
index 5f2ef41..a3cfb93 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-8b54271ffe5f174456dd68b79bf3f8f3  Digest-Perl-MD5-1.8.tar.gz
+41f1160e11ce0d99021fc8d6c725fa3d  Digest-Perl-MD5-1.9.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

File CPAN-Changes-0.27.tar.gz uploaded to lookaside cache by pghmcfc

2013-12-14 Thread Paul Howarth
A file has been added to the lookaside cache for perl-CPAN-Changes:

b9d5b5cc6422793907324fc05087e9e4  CPAN-Changes-0.27.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-CPAN-Changes] Update to 0.27

2013-12-14 Thread Paul Howarth
commit f78448cfe8c02145ae627b56699f42beec7dfd9e
Author: Paul Howarth p...@city-fan.org
Date:   Sat Dec 14 20:31:37 2013 +

Update to 0.27

- New upstream release 0.27:
  - Bump spec version to 0.04
  - Allow non-word characters between a Version and a Date

 perl-CPAN-Changes.spec |7 ++-
 sources|2 +-
 2 files changed, 7 insertions(+), 2 deletions(-)
---
diff --git a/perl-CPAN-Changes.spec b/perl-CPAN-Changes.spec
index ff53ef7..dbdae88 100644
--- a/perl-CPAN-Changes.spec
+++ b/perl-CPAN-Changes.spec
@@ -1,6 +1,6 @@
 Name:  perl-CPAN-Changes
 Summary:   Read and write Changes files
-Version:   0.26
+Version:   0.27
 Release:   1%{?dist}
 License:   GPL+ or Artistic
 Group: Development/Libraries
@@ -61,6 +61,11 @@ make test TEST_FILES=$(echo $(find xt/ -name '*.t'))
 %{_mandir}/man3/Test::CPAN::Changes.3pm*
 
 %changelog
+* Sat Dec 14 2013 Paul Howarth p...@city-fan.org - 0.27-1
+- Update to 0.27:
+  - Bump spec version to 0.04
+  - Allow non-word characters between a Version and a Date
+
 * Fri Nov 22 2013 Paul Howarth p...@city-fan.org - 0.26-1
 - Update to 0.26:
   - Fix reference issues when adding a release (CPAN RT#90605)
diff --git a/sources b/sources
index f554a0a..f13f5a6 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-5717e9f7e2a0ca490b53bbcaf4766734  CPAN-Changes-0.26.tar.gz
+b9d5b5cc6422793907324fc05087e9e4  CPAN-Changes-0.27.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-Digest-Perl-MD5] Created tag perl-Digest-Perl-MD5-1.9-1.fc21

2013-12-14 Thread Paul Howarth
The lightweight tag 'perl-Digest-Perl-MD5-1.9-1.fc21' was created pointing to:

 2ad04f9... Update to 1.9
--
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-CPAN-Changes] Created tag perl-CPAN-Changes-0.27-1.fc21

2013-12-14 Thread Paul Howarth
The lightweight tag 'perl-CPAN-Changes-0.27-1.fc21' was created pointing to:

 f78448c... Update to 0.27
--
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 1023711] perl-Text-Table-1.128 is available

2013-12-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1023711



--- Comment #4 from Fedora Update System upda...@fedoraproject.org ---
perl-Text-Table-1.128-1.fc19 has been pushed to the Fedora 19 stable
repository.  If problems still persist, please make note of it in this bug
report.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=PYXQkSICmNa=cc_unsubscribe
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[Bug 1043086] perl-ExtUtils-CChecker-0.09 is available

2013-12-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1043086

Fedora Update System upda...@fedoraproject.org changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=InBbDdU9QAa=cc_unsubscribe
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[Bug 1038513] perl-Rose-DB-Object-0.809 is available

2013-12-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1038513

Fedora Update System upda...@fedoraproject.org changed:

   What|Removed |Added

   Fixed In Version|perl-Rose-DB-Object-0.809-2 |perl-Rose-DB-Object-0.809-1
   |.fc20   |.fc19



--- Comment #7 from Fedora Update System upda...@fedoraproject.org ---
perl-Rose-DB-Object-0.809-1.fc19 has been pushed to the Fedora 19 stable
repository.  If problems still persist, please make note of it in this bug
report.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=qzYZ5OSWGZa=cc_unsubscribe
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

[Bug 1030920] perl-Text-CSV_XS-1.02 is available

2013-12-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1030920



--- Comment #4 from Fedora Update System upda...@fedoraproject.org ---
perl-Text-CSV_XS-1.02-1.fc19 has been pushed to the Fedora 19 stable
repository.  If problems still persist, please make note of it in this bug
report.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=VGizgph692a=cc_unsubscribe
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-DBIx-Class

2013-12-14 Thread buildsys


perl-DBIx-Class has broken dependencies in the epel-6 tree:
On ppc64:
perl-DBIx-Class-0.08123-2.el6.noarch requires perl(Class::Trigger)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-File-Pid

2013-12-14 Thread buildsys


perl-File-Pid has broken dependencies in the epel-6 tree:
On ppc64:
perl-File-Pid-1.01-2.el6.noarch requires perl(Class::Accessor::Fast) = 
0:0.19
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Class-Accessor-Chained

2013-12-14 Thread buildsys


perl-Class-Accessor-Chained has broken dependencies in the epel-6 tree:
On ppc64:
perl-Class-Accessor-Chained-0.01-9.el6.noarch requires 
perl(Class::Accessor::Fast)
perl-Class-Accessor-Chained-0.01-9.el6.noarch requires 
perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-SGML-Parser-OpenSP

2013-12-14 Thread buildsys


perl-SGML-Parser-OpenSP has broken dependencies in the epel-6 tree:
On ppc64:
perl-SGML-Parser-OpenSP-0.994-4.el6.ppc64 requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-HTTP-Request-AsCGI

2013-12-14 Thread buildsys


perl-HTTP-Request-AsCGI has broken dependencies in the epel-6 tree:
On ppc64:
perl-HTTP-Request-AsCGI-1.2-2.el6.noarch requires 
perl(Class::Accessor::Fast)
perl-HTTP-Request-AsCGI-1.2-2.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Catalyst-Devel

2013-12-14 Thread buildsys


perl-Catalyst-Devel has broken dependencies in the epel-6 tree:
On ppc64:
perl-Catalyst-Devel-1.28-1.el6.1.noarch requires 
perl(File::Copy::Recursive)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Catalyst-View-TT

2013-12-14 Thread buildsys


perl-Catalyst-View-TT has broken dependencies in the epel-6 tree:
On ppc64:
perl-Catalyst-View-TT-0.34-1.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Class-DBI

2013-12-14 Thread buildsys


perl-Class-DBI has broken dependencies in the epel-6 tree:
On ppc64:
perl-Class-DBI-3.0.17-5.el6.noarch requires perl(Class::Trigger) = 
0:0.07
perl-Class-DBI-3.0.17-5.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Data-ICal

2013-12-14 Thread buildsys


perl-Data-ICal has broken dependencies in the epel-6 tree:
On ppc64:
perl-Data-ICal-0.16-1.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-SQL-Translator

2013-12-14 Thread buildsys


perl-SQL-Translator has broken dependencies in the epel-6 tree:
On ppc64:
perl-SQL-Translator-0.11006-1.el6.noarch requires 
perl(Class::Data::Inheritable) = 0:0.02
perl-SQL-Translator-0.11006-1.el6.noarch requires 
perl(Class::Accessor::Fast)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Ima-DBI

2013-12-14 Thread buildsys


perl-Ima-DBI has broken dependencies in the epel-6 tree:
On ppc64:
perl-Ima-DBI-0.35-7.el6.noarch requires perl(Class::Data::Inheritable)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Data-Visitor

2013-12-14 Thread buildsys


perl-Data-Visitor has broken dependencies in the epel-6 tree:
On ppc64:
perl-Data-Visitor-0.27-1.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Array-Diff

2013-12-14 Thread buildsys


perl-Array-Diff has broken dependencies in the epel-6 tree:
On ppc64:
1:perl-Array-Diff-0.07-7.el6.noarch requires perl(Class::Accessor::Fast)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Nagios-Plugin

2013-12-14 Thread buildsys


perl-Nagios-Plugin has broken dependencies in the epel-6 tree:
On ppc64:
perl-Nagios-Plugin-0.35-1.el6.noarch requires 
perl(Class::Accessor::Fast)
perl-Nagios-Plugin-0.35-1.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-OpenOffice-UNO

2013-12-14 Thread buildsys


perl-OpenOffice-UNO has broken dependencies in the epel-6 tree:
On x86_64:
perl-OpenOffice-UNO-0.07-4.el6.x86_64 requires 
libsal_textenc.so.3()(64bit)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Catalyst-Plugin-Session-Store-FastMmap

2013-12-14 Thread buildsys


perl-Catalyst-Plugin-Session-Store-FastMmap has broken dependencies in the 
epel-6 tree:
On ppc64:
perl-Catalyst-Plugin-Session-Store-FastMmap-0.14-2.el6.noarch requires 
perl(Class::Data::Inheritable)
perl-Catalyst-Plugin-Session-Store-FastMmap-0.14-2.el6.noarch requires 
perl(Class::Accessor::Fast)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Text-RecordParser

2013-12-14 Thread buildsys


perl-Text-RecordParser has broken dependencies in the epel-6 tree:
On ppc64:
perl-Text-RecordParser-1.3.0-2.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Data-Visitor

2013-12-14 Thread buildsys


perl-Data-Visitor has broken dependencies in the epel-6 tree:
On ppc64:
perl-Data-Visitor-0.27-1.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Nagios-Plugin

2013-12-14 Thread buildsys


perl-Nagios-Plugin has broken dependencies in the epel-6 tree:
On ppc64:
perl-Nagios-Plugin-0.35-1.el6.noarch requires 
perl(Class::Accessor::Fast)
perl-Nagios-Plugin-0.35-1.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-SGML-Parser-OpenSP

2013-12-14 Thread buildsys


perl-SGML-Parser-OpenSP has broken dependencies in the epel-6 tree:
On ppc64:
perl-SGML-Parser-OpenSP-0.994-4.el6.ppc64 requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Class-DBI

2013-12-14 Thread buildsys


perl-Class-DBI has broken dependencies in the epel-6 tree:
On ppc64:
perl-Class-DBI-3.0.17-5.el6.noarch requires perl(Class::Trigger) = 
0:0.07
perl-Class-DBI-3.0.17-5.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Array-Diff

2013-12-14 Thread buildsys


perl-Array-Diff has broken dependencies in the epel-6 tree:
On ppc64:
1:perl-Array-Diff-0.07-7.el6.noarch requires perl(Class::Accessor::Fast)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Text-RecordParser

2013-12-14 Thread buildsys


perl-Text-RecordParser has broken dependencies in the epel-6 tree:
On ppc64:
perl-Text-RecordParser-1.3.0-2.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-HTTP-Request-AsCGI

2013-12-14 Thread buildsys


perl-HTTP-Request-AsCGI has broken dependencies in the epel-6 tree:
On ppc64:
perl-HTTP-Request-AsCGI-1.2-2.el6.noarch requires 
perl(Class::Accessor::Fast)
perl-HTTP-Request-AsCGI-1.2-2.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Catalyst-View-TT

2013-12-14 Thread buildsys


perl-Catalyst-View-TT has broken dependencies in the epel-6 tree:
On ppc64:
perl-Catalyst-View-TT-0.34-1.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Data-ICal

2013-12-14 Thread buildsys


perl-Data-ICal has broken dependencies in the epel-6 tree:
On ppc64:
perl-Data-ICal-0.16-1.el6.noarch requires perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Exception-Class

2013-12-14 Thread buildsys


perl-Exception-Class has broken dependencies in the epel-6 tree:
On ppc64:
perl-Exception-Class-1.29-1.1.el6.noarch requires 
perl(Class::Data::Inheritable)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Catalyst-Devel

2013-12-14 Thread buildsys


perl-Catalyst-Devel has broken dependencies in the epel-6 tree:
On ppc64:
perl-Catalyst-Devel-1.28-1.el6.1.noarch requires 
perl(File::Copy::Recursive)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Class-Accessor-Chained

2013-12-14 Thread buildsys


perl-Class-Accessor-Chained has broken dependencies in the epel-6 tree:
On ppc64:
perl-Class-Accessor-Chained-0.01-9.el6.noarch requires 
perl(Class::Accessor::Fast)
perl-Class-Accessor-Chained-0.01-9.el6.noarch requires 
perl(Class::Accessor)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Catalyst-Plugin-Session-Store-FastMmap

2013-12-14 Thread buildsys


perl-Catalyst-Plugin-Session-Store-FastMmap has broken dependencies in the 
epel-6 tree:
On ppc64:
perl-Catalyst-Plugin-Session-Store-FastMmap-0.14-2.el6.noarch requires 
perl(Class::Data::Inheritable)
perl-Catalyst-Plugin-Session-Store-FastMmap-0.14-2.el6.noarch requires 
perl(Class::Accessor::Fast)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-DBIx-Class

2013-12-14 Thread buildsys


perl-DBIx-Class has broken dependencies in the epel-6 tree:
On ppc64:
perl-DBIx-Class-0.08123-2.el6.noarch requires perl(Class::Trigger)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-OpenOffice-UNO

2013-12-14 Thread buildsys


perl-OpenOffice-UNO has broken dependencies in the epel-6 tree:
On x86_64:
perl-OpenOffice-UNO-0.07-4.el6.x86_64 requires 
libsal_textenc.so.3()(64bit)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-SQL-Translator

2013-12-14 Thread buildsys


perl-SQL-Translator has broken dependencies in the epel-6 tree:
On ppc64:
perl-SQL-Translator-0.11006-1.el6.noarch requires 
perl(Class::Data::Inheritable) = 0:0.02
perl-SQL-Translator-0.11006-1.el6.noarch requires 
perl(Class::Accessor::Fast)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Authen-Simple

2013-12-14 Thread buildsys


perl-Authen-Simple has broken dependencies in the epel-6 tree:
On ppc64:
perl-Authen-Simple-0.4-5.el6.noarch requires perl(Crypt::PasswdMD5)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-Ima-DBI

2013-12-14 Thread buildsys


perl-Ima-DBI has broken dependencies in the epel-6 tree:
On ppc64:
perl-Ima-DBI-0.35-7.el6.noarch requires perl(Class::Data::Inheritable)
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-File-Pid

2013-12-14 Thread buildsys


perl-File-Pid has broken dependencies in the epel-6 tree:
On ppc64:
perl-File-Pid-1.01-2.el6.noarch requires perl(Class::Accessor::Fast) = 
0:0.19
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-WWW-GoodData

2013-12-14 Thread buildsys


perl-WWW-GoodData has broken dependencies in the epel-5 tree:
On ppc:
perl-WWW-GoodData-1.6-1.el5.noarch requires perl(Getopt::Long) = 0:2.36
On i386:
perl-WWW-GoodData-1.6-1.el5.noarch requires perl(Getopt::Long) = 0:2.36
Please resolve this as soon as possible.


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Broken dependencies: perl-WWW-GoodData

2013-12-14 Thread buildsys


perl-WWW-GoodData has broken dependencies in the epel-5 tree:
On ppc:
perl-WWW-GoodData-1.6-1.el5.noarch requires perl(Getopt::Long) = 0:2.36
On i386:
perl-WWW-GoodData-1.6-1.el5.noarch requires perl(Getopt::Long) = 0:2.36
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

Important note regarding /root permissions for those who installed Fedora 20 pre-releases

2013-12-14 Thread Adam Williamson
Hi, folks. I wanted to draw the attention of anyone who used Fedora 20
pre-release (Alpha, Beta, or TC/RC for Alpha, Beta or Final) to this
issue:

https://fedoraproject.org/wiki/Common_F20_bugs#.2Froot_permissions_incorrect_on_pre-release_installations

Briefly, if you did use F20 pre-release - this includes yum or otherwise
upgrading to F20 at any time the older 'rootfiles' package was in the
F20 repos, that is any time prior to about 12-05 (testing) /12-11
(stable) - permissions on the /root directory are likely to be 0755,
which is probably not what most sysadmins would expect. You may wish to
change them to 0550 or something similarly locked-down.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

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