[Bug 1417508] New: perl-PPIx-Regexp-0.051 is available

[bugzilla]

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

Bug ID: 1417508
   Summary: perl-PPIx-Regexp-0.051 is available
   Product: Fedora
   Version: rawhide
 Component: perl-PPIx-Regexp
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com



Latest upstream release: 0.051
Current version/release in rawhide: 0.050-2.fc25
URL: http://search.cpan.org/dist/PPIx-Regexp/

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

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/3288/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: Fedora 25 Koji buildroots broken…

[Kevin Fenzi]

On Mon, 30 Jan 2017 00:53:05 +0100
Kevin Kofler  wrote:

> Hans de Goede wrote:
> > Well, that is a fix, but the real problem is that either the new
> > libglvnd enabled mesa should not be in updates-stable and thus not
> > in the buildroot; or both the new libglvnd enabled mesa and the new
> > libglvnd should be in updates-stable.  
> 
> This is the result of 4 very poor decisions, by different
> people/groups:
> 
> 1. the decision to enable libglvnd in an update to a stable release.
> IMHO, such a change is totally unsuitable for a stable release update
> and should have been done in Rawhide only.

Perhaps so. I agree it definitely shouldn't have been pushed without
fixing all the packages that are broken by the update. 
> 
> 2. the decision to block Bodhi pushes on ostree failures. Without
> that, Bodhi would not have been stuck for days with all updates
> locked and this fiasco might possibly have been avoided. If the
> ostree compose fails, the Bodhi push should just proceed with an
> empty or old ostree directory (whatever is easier to implement).
> Rarely used experimental delivery methods should not hold the entire
> distribution hostage.

I disagree with you here. I think ostree is important and people are
using it. However, there's two (IMHO better) ways forward here. 
First we could (and should) just back out
rpm-ostree/ostree/bublewrap/whatever updates breaks composing and debug
it on the side. Second, the atomic sig is looking at changing how the
updates stream is made and only push it every 2 weeks. That would
remove it from being done by bodhi. 

> 3. the decision to use autokarma. This is just yet another broken
> update that went stable due to autokarma. Autokarma is an absolutely
>unacceptable practice and should not be allowed. All push requests
> should be issued by a human after reviewing the status.

I disagree. If autokarma wasn't used then the update could well have
been pushed again after the maintainer saw that it was able to be
pushed. Also, it would result it a bunch of updates stalling in
updates-testing as maintainers forget to push things stable. Also, it
would result in maintainers spending a bunch more time looking at
things and seeing... that they are all ready to go to stable.
 
> 4. the decision to disallow direct stable pushes. The right way to
> fix the issue quickly, limiting the damage once done, would have been
> to push libglvnd directly to stable. But Bodhi won't allow that.
> Direct stable pushes are an essential mechanism to fix regressions
> and to limit the number of affected users by minimizing the exposure
> time to the regression.

I disagree again. Right now, mesa in stable updates has a broken dep.
dnf and gnome-software will not update it because of that. So, right
now, no stable updates users are broken, they just see an unsightly
broken dep on trying to update. 

If we push libglvnd to stable right now, everyone will be able to
update mesa and it, and all users of sway will get a black screen and
be broken. So, we should _not_ push libglvnd until sway is fixed. 

kevin




pgpoxAxvbHHtk.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1417505] New: perl-Moose-2.2001 is available

[bugzilla]

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

Bug ID: 1417505
   Summary: perl-Moose-2.2001 is available
   Product: Fedora
   Version: rawhide
 Component: perl-Moose
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, iarn...@gmail.com,
p...@city-fan.org, perl-devel@lists.fedoraproject.org



Latest upstream release: 2.2001
Current version/release in rawhide: 2.2000-1.fc26
URL: http://search.cpan.org/dist/Moose/

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

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/6197/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1417503] New: perl-Mojolicious-7.23 is available

[bugzilla]

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

Bug ID: 1417503
   Summary: perl-Mojolicious-7.23 is available
   Product: Fedora
   Version: rawhide
 Component: perl-Mojolicious
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr,
perl-devel@lists.fedoraproject.org,
robinlee.s...@gmail.com



Latest upstream release: 7.23
Current version/release in rawhide: 7.22-1.fc26
URL: http://mojolicio.us/

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

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/5966/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1417499] New: perl-DateTime-Locale-1.12 is available

[bugzilla]

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

Bug ID: 1417499
   Summary: perl-DateTime-Locale-1.12 is available
   Product: Fedora
   Version: rawhide
 Component: perl-DateTime-Locale
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org



Latest upstream release: 1.12
Current version/release in rawhide: 1.11-1.fc26
URL: http://search.cpan.org/dist/DateTime-Locale/

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

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/6477/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: Fedora 25 Koji buildroots broken…

[Kevin Kofler]

Hans de Goede wrote:
> Well, that is a fix, but the real problem is that either the new libglvnd
> enabled mesa should not be in updates-stable and thus not in the
> buildroot; or both the new libglvnd enabled mesa and the new libglvnd
> should be in updates-stable.

This is the result of 4 very poor decisions, by different people/groups:

1. the decision to enable libglvnd in an update to a stable release. IMHO,
   such a change is totally unsuitable for a stable release update and
   should have been done in Rawhide only.

2. the decision to block Bodhi pushes on ostree failures. Without that,
   Bodhi would not have been stuck for days with all updates locked and this
   fiasco might possibly have been avoided. If the ostree compose fails, the
   Bodhi push should just proceed with an empty or old ostree directory
   (whatever is easier to implement). Rarely used experimental delivery
   methods should not hold the entire distribution hostage.

3. the decision to use autokarma. This is just yet another broken update
   that went stable due to autokarma. Autokarma is an absolutely
   unacceptable practice and should not be allowed. All push requests should
   be issued by a human after reviewing the status.

4. the decision to disallow direct stable pushes. The right way to fix the
   issue quickly, limiting the damage once done, would have been to push
   libglvnd directly to stable. But Bodhi won't allow that. Direct stable
   pushes are an essential mechanism to fix regressions and to limit the
   number of affected users by minimizing the exposure time to the
   regression.

Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1417412] abi-compliance-checker-2.0 is available

[bugzilla]

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



--- Comment #8 from Fedora Update System  ---
abi-compliance-checker-2.0-1.fc25 has been pushed to the Fedora 25 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-8f62b1e067

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1417412] abi-compliance-checker-2.0 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #7 from Fedora Update System  ---
abi-compliance-checker-2.0-1.fc24 has been pushed to the Fedora 24 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-08ab29cd50

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[EPEL-devel] Fedora EPEL 7 updates-testing report

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
 693  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087   
dokuwiki-0-0.24.20140929c.el7
 455  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f   
mcollective-2.8.4-1.el7
 173  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-23fa04bf1c   
redis-3.2.3-1.el7
 157  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-e8f4ff76b3   
chicken-4.11.0-3.el7
  37  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-04bc9dd81d   
libbsd-0.8.3-1.el7
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-6e3dadcb1d   
pdns-recursor-3.7.4-1.el7
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-9bcc7b6164   
mingw-nsis-3.01-1.el7
  12  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-ad7467bd9c   
pdns-3.4.11-1.el7
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-8cb1dcd776   
python-crypto-2.6.1-13.el7
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-09ddf72aaa   
percona-xtrabackup-2.3.6-1.el7
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-cd2af02aae   
rabbitmq-server-3.3.5-31.el7
   8  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-8533f605ab   
bubblewrap-0.1.7-1.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-555b5847ec   
drupal7-title-1.0-0.7.alpha9.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-7fb94fc97a   
exim-4.88-3.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-b498a4859e   
moodle-3.1.4-1.el7
   0  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-cc2d96d683   
wordpress-4.7.2-1.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

glfw-3.2.1-2.el7
jcip-annotations-1-15.20060626.el7
ndoutils-2.1.2-1.el7
python-robosignatory-0.2.0-2.el7
uchardet-0.0.6-1.el7

Details about builds:



 glfw-3.2.1-2.el7 (FEDORA-EPEL-2017-94691939a7)
 A cross-platform multimedia library

Update Information:

Update to 3.2.1.

References:

  [ 1 ] Bug #1271026 - glfw-3.2.1 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1271026




 jcip-annotations-1-15.20060626.el7 (FEDORA-EPEL-2017-98507d2ae5)
 Java annotations for multithreaded software

Update Information:

Add initial package for EPEL 7

References:

  [ 1 ] Bug #1128852 - [RFE] - Add findbugs and associated packages to the EPEL
https://bugzilla.redhat.com/show_bug.cgi?id=1128852




 ndoutils-2.1.2-1.el7 (FEDORA-EPEL-2017-71e8629661)
 Stores all configuration and event data from Nagios in a database

Update Information:

- Update ndoutils to 2.1.2. - Rebuild RHEL/CentOS support for Nagios 4.x.




 python-robosignatory-0.2.0-2.el7 (FEDORA-EPEL-2017-29031600f2)
 A fedmsg consumer that automatically signs artifacts

Update Information:

Remove Requires on sigul, which is only necessary for one helper plugin.  
Now, with plugins!




 uchardet-0.0.6-1.el7 (FEDORA-EPEL-2017-2718ae71f0)
 An encoding detector library ported from Mozilla

Update Information:

Update to 0.0.6

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

Re: F25 updates/updates-testing failures in bodhi

[Kevin Kofler]

Kevin Fenzi wrote:
> We do have a staging bodhi setup. The problem is that the composes are
> done with the contents of the compose. So, when a new rpm-ostree update
> is submitted to f25-updates-testing that very new update is used in the
> compose. I don't think it's practical to first try every compose in
> staging with an update that could be in the compose.

An rpm-ostree compose failure should not block the push. Nobody needs ostree 
in the real world. The push should just proceed with the ostree stuff 
missing.

Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Fedora 25 Koji buildroots broken…

[Hans de Goede]

Hi,

On 01/29/2017 08:00 PM, Kevin Fenzi wrote:

On Sun, 29 Jan 2017 18:12:59 +0100
Hans de Goede  wrote:


Hi,

On 01/29/2017 05:23 PM, Björn 'besser82' Esser wrote:

Allrighty…  Looks like the override for libglvnd somehow got
untagged…  Just re-tagged in f25-build…  Should be fixed now.


Well, that is a fix, but the real problem is that either the new
libglvnd enabled mesa should not be in updates-stable and thus not in
the buildroot; or both the new libglvnd enabled mesa and the new
libglvnd should be in updates-stable.

What happened is I created an update in bodhi for
libglvnd-0.2.999-7.gitdc16f8c.fc25 and mesa-13.0.3-3.fc25.

Then airlied did an unrelated bug-fix to mesa and created an update
in bodhi for mesa-13.0.3-4.fc25. This update did not obsolete my
previous update, did not inherit it bugs and did not inherit the
libglvnd package which was only in my update.


Yeah, currently bodhi doesn't obsolete if the other update is locked or
if the other update has a different packageset.


When I noticed things both updates were in perpetual locked state,
when they were finally unlocked airlied's update got auto-pushed to
stable because of karma (I had auto-karma disabled on mine), so now
we have a mesa depending on the latest libglvnd in updates-stable,
without the latest libglvnd.


:(


Yeah, this is quite unfortunate :(



When I tried to also push my update to stable, I could not as bodhi
complained there was a newer mesa already in stable, so I had to
remove mesa from my update (why does it detect conflicts like this on
push and not when someone creates a conflicting update?), loosing all
karma??? and now it is pending for testing.

Frankly I blame this whole mess on bodhi, it should not allow creating
updates which partly obsolete other updates, there likely is a good
reason the partly obsoleted update bundled multiple packages in one
update; or it should allow it and then simply add all non obsoleted
packages from the obsoleted update to the new update and obsolete the
old one.

I've had trouble with bodhi not doing proper obsoleting more often
lately, as well as having trouble with updates which involve
obsoleting getting in a perpetual locked state. Again frankly I've
the feeling that bodhi has regressed and that the old bodhi was more
stable. We really need to do better here, both with obsoleting and
with the locked state thing.


I'll leave the above for bodhi developers to comment on.
This has always been a complicated area, but I agree we could do
better.


I've filed:

https://github.com/fedora-infra/bodhi/issues/1254

To track this.

Regaards,

Hans




Why does the admin side of bodhi not run a check to see everything is
unlocked again once the push is complete ? That should at least catch
the lock issue ?


It does. The "lock issue" was just because we couldn't get a
f25-updates-testing push to complete due to rpm-ostree issues. So, IMHO
it was completely right to lock those until the push finished.

I guess of your suggestions it might indeed be best to reject a new
update when there's already one in existance that it cannot obsolete
(because it's locked or has a different packageset). I'm sure that will
annoy some people, but seems cleanest to me and then allows people to
discuss and modify the in-flight update or whatever.

kevin



___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Fedora 25 Koji buildroots broken…

[Kevin Fenzi]

On Sun, 29 Jan 2017 18:12:59 +0100
Hans de Goede  wrote:

> Hi,
> 
> On 01/29/2017 05:23 PM, Björn 'besser82' Esser wrote:
> > Allrighty…  Looks like the override for libglvnd somehow got
> > untagged…  Just re-tagged in f25-build…  Should be fixed now.  
> 
> Well, that is a fix, but the real problem is that either the new
> libglvnd enabled mesa should not be in updates-stable and thus not in
> the buildroot; or both the new libglvnd enabled mesa and the new
> libglvnd should be in updates-stable.
> 
> What happened is I created an update in bodhi for
> libglvnd-0.2.999-7.gitdc16f8c.fc25 and mesa-13.0.3-3.fc25.
> 
> Then airlied did an unrelated bug-fix to mesa and created an update
> in bodhi for mesa-13.0.3-4.fc25. This update did not obsolete my
> previous update, did not inherit it bugs and did not inherit the
> libglvnd package which was only in my update.

Yeah, currently bodhi doesn't obsolete if the other update is locked or
if the other update has a different packageset. 

> When I noticed things both updates were in perpetual locked state,
> when they were finally unlocked airlied's update got auto-pushed to
> stable because of karma (I had auto-karma disabled on mine), so now
> we have a mesa depending on the latest libglvnd in updates-stable,
> without the latest libglvnd.

:( 

> When I tried to also push my update to stable, I could not as bodhi
> complained there was a newer mesa already in stable, so I had to
> remove mesa from my update (why does it detect conflicts like this on
> push and not when someone creates a conflicting update?), loosing all
> karma??? and now it is pending for testing.
> 
> Frankly I blame this whole mess on bodhi, it should not allow creating
> updates which partly obsolete other updates, there likely is a good
> reason the partly obsoleted update bundled multiple packages in one
> update; or it should allow it and then simply add all non obsoleted
> packages from the obsoleted update to the new update and obsolete the
> old one.
> 
> I've had trouble with bodhi not doing proper obsoleting more often
> lately, as well as having trouble with updates which involve
> obsoleting getting in a perpetual locked state. Again frankly I've
> the feeling that bodhi has regressed and that the old bodhi was more
> stable. We really need to do better here, both with obsoleting and
> with the locked state thing.

I'll leave the above for bodhi developers to comment on.
This has always been a complicated area, but I agree we could do
better. 
> 
> Why does the admin side of bodhi not run a check to see everything is
> unlocked again once the push is complete ? That should at least catch
> the lock issue ?

It does. The "lock issue" was just because we couldn't get a
f25-updates-testing push to complete due to rpm-ostree issues. So, IMHO
it was completely right to lock those until the push finished. 

I guess of your suggestions it might indeed be best to reject a new
update when there's already one in existance that it cannot obsolete
(because it's locked or has a different packageset). I'm sure that will
annoy some people, but seems cleanest to me and then allows people to
discuss and modify the in-flight update or whatever. 

kevin


pgpPRGBMT7D3c.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [embree] patch refused to be applied

[Luya Tshimbalanga]

On 29/01/17 06:46 AM, Mukundan Ragavan wrote:
>
> On 01/29/2017 12:37 AM, Luya Tshimbalanga wrote:
>> Hello team,
>>
>> I applied a patch sent by upstream but some odd reason, the build kept
>> on failing
>>
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=17472254
>>
>> I include the patch for preview so someone can see what went wrong.
>>
>> Thanks
>>
> + /usr/bin/patch -s --fuzz=0 --no-backup-if-mismatch
> The text leading up to this was:
> --
> |diff -ru embree-2.13.0-orig/kernels/common/accel.cpp
> embree-2.13.0/kernels/common/accel.cpp
> |--- embree-2.13.0-orig/kernels/common/accel.cpp  2016-11-21
> 01:12:33.0 -0800
> |+++ embree-2.13.0/kernels/common/accel.cpp   2017-01-28
> 20:47:13.979363972 -0800
>
>
> Using, for example,
>
> %patch0 -p1
>
>
> should fix the issue.
>
>

Thank you both Mukundan and Tom. "-p1" did the trick when used after
"%autosetup".

-- 
Luya Tshimbalanga
Graphic & Web Designer
E: l...@fedoraproject.org
W: http://www.coolest-storm.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Fedora 25 Koji buildroots broken…

[Hans de Goede]

Hi,

On 01/29/2017 05:23 PM, Björn 'besser82' Esser wrote:

Allrighty…  Looks like the override for libglvnd somehow got untagged…  Just 
re-tagged in f25-build…  Should be fixed now.


Well, that is a fix, but the real problem is that either the new libglvnd 
enabled
mesa should not be in updates-stable and thus not in the buildroot; or
both the new libglvnd enabled mesa and the new libglvnd should be in 
updates-stable.

What happened is I created an update in bodhi for 
libglvnd-0.2.999-7.gitdc16f8c.fc25
and mesa-13.0.3-3.fc25.

Then airlied did an unrelated bug-fix to mesa and created an update in bodhi for
mesa-13.0.3-4.fc25. This update did not obsolete my previous update, did not
inherit it bugs and did not inherit the libglvnd package which was only in my
update.

When I noticed things both updates were in perpetual locked state, when they
were finally unlocked airlied's update got auto-pushed to stable because of
karma (I had auto-karma disabled on mine), so now we have a mesa depending on
the latest libglvnd in updates-stable, without the latest libglvnd.

When I tried to also push my update to stable, I could not as bodhi complained
there was a newer mesa already in stable, so I had to remove mesa from my
update (why does it detect conflicts like this on push and not when someone
creates a conflicting update?), loosing all karma??? and now it is pending for
testing.

Frankly I blame this whole mess on bodhi, it should not allow creating
updates which partly obsolete other updates, there likely is a good reason
the partly obsoleted update bundled multiple packages in one update; or
it should allow it and then simply add all non obsoleted packages from
the obsoleted update to the new update and obsolete the old one.

I've had trouble with bodhi not doing proper obsoleting more often
lately, as well as having trouble with updates which involve obsoleting
getting in a perpetual locked state. Again frankly I've the feeling that
bodhi has regressed and that the old bodhi was more stable. We really need
to do better here, both with obsoleting and with the locked state thing.

Why does the admin side of bodhi not run a check to see everything is
unlocked again once the push is complete ? That should at least catch the
lock issue ?

For the 2 updates in question see:

https://bodhi.fedoraproject.org/updates/FEDORA-2017-9f6383547e
https://bodhi.fedoraproject.org/updates/FEDORA-2017-9c9c0899f9

Regards,

Hans



Am 29.01.2017 um 17:19 schrieb Björn 'besser82' Esser:


Hi there!

The Fedora 25 buildroot on Koji is b0rk3n…  :(

DEBUG util.py:435:  Error: nothing provides libGL.so.1()(64bit) needed by 
muffin-devel-3.2.1-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libEGL.so.1()(64bit) needed by 
clutter-1.26.0-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-gobject-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-gobject-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libglvnd-glx(x86-64) needed by 
mesa-libGL-13.0.3-4.fc25.x86_64

Can the one who broke fix it, please?

Cheers
  Björn




___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Fedora 25 Koji buildroots broken…

[Björn 'besser82' Esser]

Allrighty…  Looks like the override for libglvnd somehow got untagged…  
Just re-tagged in f25-build…  Should be fixed now.



Am 29.01.2017 um 17:19 schrieb Björn 'besser82' Esser:


Hi there!

The Fedora 25 buildroot on Koji is b0rk3n…  :(

DEBUG util.py:435:  Error: nothing provides libGL.so.1()(64bit) needed by 
muffin-devel-3.2.1-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libEGL.so.1()(64bit) needed by 
clutter-1.26.0-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-gobject-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-gobject-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libglvnd-glx(x86-64) needed by 
mesa-libGL-13.0.3-4.fc25.x86_64

Can the one who broke fix it, please?

Cheers
   Björn


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Fedora 25 Koji buildroots broken…

[Björn 'besser82' Esser]

Hi there!

The Fedora 25 buildroot on Koji is b0rk3n…  :(

DEBUG util.py:435:  Error: nothing provides libGL.so.1()(64bit) needed by 
muffin-devel-3.2.1-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libEGL.so.1()(64bit) needed by 
clutter-1.26.0-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-gobject-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-gobject-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libGL.so.1()(64bit) needed by 
cairo-1.14.8-1.fc25.x86_64.
DEBUG util.py:435:  nothing provides libglvnd-glx(x86-64) needed by 
mesa-libGL-13.0.3-4.fc25.x86_64

Can the one who broke fix it, please?

Cheers
  Björn

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [embree] patch refused to be applied

[Mukundan Ragavan]

On 01/29/2017 12:37 AM, Luya Tshimbalanga wrote:
> Hello team,
> 
> I applied a patch sent by upstream but some odd reason, the build kept
> on failing
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=17472254
> 
> I include the patch for preview so someone can see what went wrong.
> 
> Thanks
> 

+ /usr/bin/patch -s --fuzz=0 --no-backup-if-mismatch
The text leading up to this was:
--
|diff -ru embree-2.13.0-orig/kernels/common/accel.cpp
embree-2.13.0/kernels/common/accel.cpp
|--- embree-2.13.0-orig/kernels/common/accel.cpp2016-11-21
01:12:33.0 -0800
|+++ embree-2.13.0/kernels/common/accel.cpp 2017-01-28
20:47:13.979363972 -0800


Using, for example,

%patch0 -p1


should fix the issue.


-- 
GPG Key - E5C8BC67
---
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1417412] abi-compliance-checker-2.0 is available

[bugzilla]

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



--- Comment #6 from Fedora Update System  ---
abi-compliance-checker-2.0-1.fc25 has been submitted as an update to Fedora 25.
https://bodhi.fedoraproject.org/updates/FEDORA-2017-8f62b1e067

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1417412] abi-compliance-checker-2.0 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
abi-compliance-checker-2.0-1.fc24 abi-compliance-checker-2.0-1.fc24 has been
submitted as an update to Fedora 24.
https://bodhi.fedoraproject.org/updates/FEDORA-2017-08ab29cd50

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

hobbes1069 pushed to abi-compliance-checker (f24). "Update to latest upstream release."

[notifications]

From 91dd6e933bea108f797a2adda42d20d688c6b7db Mon Sep 17 00:00:00 2001
From: Richard Shaw 
Date: Sun, 29 Jan 2017 06:49:25 -0600
Subject: Update to latest upstream release.

---
 .gitignore  | 1 +
 abi-compliance-checker.spec | 5 -
 sources | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index 68f26b0..db31313 100644
--- a/.gitignore
+++ b/.gitignore
@@ -25,3 +25,4 @@
 /abi-compliance-checker-1.99.19.tar.gz
 /abi-compliance-checker-1.99.20.tar.gz
 /abi-compliance-checker-1.99.25.tar.gz
+/abi-compliance-checker-2.0.tar.gz
diff --git a/abi-compliance-checker.spec b/abi-compliance-checker.spec
index a6ef6fa..244a9b0 100644
--- a/abi-compliance-checker.spec
+++ b/abi-compliance-checker.spec
@@ -1,5 +1,5 @@
 Name:   abi-compliance-checker
-Version:1.99.25
+Version:2.0
 Release:1%{?dist}
 Summary:An ABI Compliance Checker
 
@@ -47,6 +47,9 @@ perl Makefile.pl -install --prefix=%{_prefix} 
--destdir=%{buildroot}
 
 
 %changelog
+* Sun Jan 29 2017 Richard Shaw  - 2.0-1
+- Update to latest upstream release.
+
 * Thu Oct 13 2016 Richard Shaw  - 1.99.25-1
 - Update to latest upstream release.
 
diff --git a/sources b/sources
index f428a52..9f50e44 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-cc4f8e5351c895d325e8010c83931aa4  abi-compliance-checker-1.99.25.tar.gz
+SHA512 (abi-compliance-checker-2.0.tar.gz) = 
f1ee78113ac29814ecdf4130cd2ed2cbe24ffea65853cbdc8803a07b5d08dc8f7ffea9764c2ddf7a4a73eac1159fd13b3ce74cb0d7e412aacadacf6f59e7b663
-- 
cgit v1.1



https://src.fedoraproject.org/cgit/abi-compliance-checker.git/commit/?h=f24=91dd6e933bea108f797a2adda42d20d688c6b7db
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

hobbes1069 pushed to abi-compliance-checker (f25). "Update to latest upstream release."

[notifications]

From 91dd6e933bea108f797a2adda42d20d688c6b7db Mon Sep 17 00:00:00 2001
From: Richard Shaw 
Date: Sun, 29 Jan 2017 06:49:25 -0600
Subject: Update to latest upstream release.

---
 .gitignore  | 1 +
 abi-compliance-checker.spec | 5 -
 sources | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index 68f26b0..db31313 100644
--- a/.gitignore
+++ b/.gitignore
@@ -25,3 +25,4 @@
 /abi-compliance-checker-1.99.19.tar.gz
 /abi-compliance-checker-1.99.20.tar.gz
 /abi-compliance-checker-1.99.25.tar.gz
+/abi-compliance-checker-2.0.tar.gz
diff --git a/abi-compliance-checker.spec b/abi-compliance-checker.spec
index a6ef6fa..244a9b0 100644
--- a/abi-compliance-checker.spec
+++ b/abi-compliance-checker.spec
@@ -1,5 +1,5 @@
 Name:   abi-compliance-checker
-Version:1.99.25
+Version:2.0
 Release:1%{?dist}
 Summary:An ABI Compliance Checker
 
@@ -47,6 +47,9 @@ perl Makefile.pl -install --prefix=%{_prefix} 
--destdir=%{buildroot}
 
 
 %changelog
+* Sun Jan 29 2017 Richard Shaw  - 2.0-1
+- Update to latest upstream release.
+
 * Thu Oct 13 2016 Richard Shaw  - 1.99.25-1
 - Update to latest upstream release.
 
diff --git a/sources b/sources
index f428a52..9f50e44 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-cc4f8e5351c895d325e8010c83931aa4  abi-compliance-checker-1.99.25.tar.gz
+SHA512 (abi-compliance-checker-2.0.tar.gz) = 
f1ee78113ac29814ecdf4130cd2ed2cbe24ffea65853cbdc8803a07b5d08dc8f7ffea9764c2ddf7a4a73eac1159fd13b3ce74cb0d7e412aacadacf6f59e7b663
-- 
cgit v1.1



https://src.fedoraproject.org/cgit/abi-compliance-checker.git/commit/?h=f25=91dd6e933bea108f797a2adda42d20d688c6b7db
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1417412] abi-compliance-checker-2.0 is available

[bugzilla]

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



--- Comment #4 from Upstream Release Monitoring 
 ---
hobbes1069's abi-compliance-checker-2.0-1.fc26 completed
http://koji.fedoraproject.org/koji/buildinfo?buildID=836912

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

hobbes1069 uploaded abi-compliance-checker-2.0.tar.gz for abi-compliance-checker

[notifications]

f1ee78113ac29814ecdf4130cd2ed2cbe24ffea65853cbdc8803a07b5d08dc8f7ffea9764c2ddf7a4a73eac1159fd13b3ce74cb0d7e412aacadacf6f59e7b663
  abi-compliance-checker-2.0.tar.gz

https://src.fedoraproject.org/lookaside/pkgs/abi-compliance-checker/abi-compliance-checker-2.0.tar.gz/sha512/f1ee78113ac29814ecdf4130cd2ed2cbe24ffea65853cbdc8803a07b5d08dc8f7ffea9764c2ddf7a4a73eac1159fd13b3ce74cb0d7e412aacadacf6f59e7b663/abi-compliance-checker-2.0.tar.gz
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

hobbes1069 pushed to abi-compliance-checker (master). "Update to latest upstream release."

[notifications]

From 91dd6e933bea108f797a2adda42d20d688c6b7db Mon Sep 17 00:00:00 2001
From: Richard Shaw 
Date: Sun, 29 Jan 2017 06:49:25 -0600
Subject: Update to latest upstream release.

---
 .gitignore  | 1 +
 abi-compliance-checker.spec | 5 -
 sources | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index 68f26b0..db31313 100644
--- a/.gitignore
+++ b/.gitignore
@@ -25,3 +25,4 @@
 /abi-compliance-checker-1.99.19.tar.gz
 /abi-compliance-checker-1.99.20.tar.gz
 /abi-compliance-checker-1.99.25.tar.gz
+/abi-compliance-checker-2.0.tar.gz
diff --git a/abi-compliance-checker.spec b/abi-compliance-checker.spec
index a6ef6fa..244a9b0 100644
--- a/abi-compliance-checker.spec
+++ b/abi-compliance-checker.spec
@@ -1,5 +1,5 @@
 Name:   abi-compliance-checker
-Version:1.99.25
+Version:2.0
 Release:1%{?dist}
 Summary:An ABI Compliance Checker
 
@@ -47,6 +47,9 @@ perl Makefile.pl -install --prefix=%{_prefix} 
--destdir=%{buildroot}
 
 
 %changelog
+* Sun Jan 29 2017 Richard Shaw  - 2.0-1
+- Update to latest upstream release.
+
 * Thu Oct 13 2016 Richard Shaw  - 1.99.25-1
 - Update to latest upstream release.
 
diff --git a/sources b/sources
index f428a52..9f50e44 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-cc4f8e5351c895d325e8010c83931aa4  abi-compliance-checker-1.99.25.tar.gz
+SHA512 (abi-compliance-checker-2.0.tar.gz) = 
f1ee78113ac29814ecdf4130cd2ed2cbe24ffea65853cbdc8803a07b5d08dc8f7ffea9764c2ddf7a4a73eac1159fd13b3ce74cb0d7e412aacadacf6f59e7b663
-- 
cgit v1.1



https://src.fedoraproject.org/cgit/abi-compliance-checker.git/commit/?h=master=91dd6e933bea108f797a2adda42d20d688c6b7db
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: gperf 3.1 changes the type of the hash 'len' parameter

[Richard W.M. Jones]

On Fri, Jan 27, 2017 at 09:09:14AM +, Richard W.M. Jones wrote:
> I pushed gperf 3.1 to Rawhide.
> 
> This changes the type of one of the parameters of the generated
> perfect hash function:
> 
> -char *in_word_set (register const char *str, register unsigned int len);
> +char *in_word_set (register const char *str, register size_t len);
> 
> If you have the function prototyped in another file, then you have to
> be careful that the prototype exactly matches the new type.  Otherwise
> on 64 bit architectures you'll end up passing an incorrectly sized
> 'len' argument (unsigned int == 32 bits vs size_t == 64 bits) which
> will subtly break in certain circumstances (but on little endian it'll
> still work most of the time, making this bug rather insidious).
> 
> Using the functions (third) section of the gperf file can avoid
> needing to prototype the function elsewhere, since you can drop a
> wrapper of your own choosing into the functions section.

There was a bit of fallout from this change.  Mainly it broke
systemd, although there was already a fix upstream.

If you're wondering how to fix this, here are two approaches you can
take.

Firstly the systemd fix which involves sensing the function signature
at ./configure time and adjusting the prototype:

https://github.com/systemd/systemd/commit/c9f7b4d356a453a01aa77a6bb74ca7ef49732c08

Alternately, this is the approach I took for libguestfs.  Move all
calls to the hash function into the functions (third) section of the
gperf source file, so no explicit prototype is needed:

https://github.com/libguestfs/libguestfs/commit/004de6cf45cfe66ca166cbdcb1c3125a2a81eb31
https://github.com/libguestfs/libguestfs/commit/48d4117789e92489b9a3c6f3456b0770b3fdb290

Hope that helps others who have gperf problems.  You can also follow
up here if you don't know how to fix it for a particular package and
I'll see if I can help.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1417441] New: perl-App-cpm-0.299 is available

[bugzilla]

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

Bug ID: 1417441
   Summary: perl-App-cpm-0.299 is available
   Product: Fedora
   Version: rawhide
 Component: perl-App-cpm
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org



Latest upstream release: 0.299
Current version/release in rawhide: 0.298-1.fc26
URL: http://search.cpan.org/dist/App-cpm/

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

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/8399/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1416589] perl-Dancer2-0.204004 is available

[bugzilla]

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

Emmanuel Seyman  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Dancer2-0.204004-1.fc2
   ||6
 Resolution|--- |RAWHIDE
Last Closed||2017-01-29 06:17:25



--- Comment #9 from Emmanuel Seyman  ---
Built in rawhide:
https://koji.fedoraproject.org/koji/buildinfo?buildID=836896

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1416790] perl-Mojolicious-7.22 is available

[bugzilla]

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

Emmanuel Seyman  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Mojolicious-7.22-1.fc2
   ||6
 Resolution|--- |RAWHIDE
Last Closed||2017-01-29 06:13:17



--- Comment #1 from Emmanuel Seyman  ---
Built in rawhide:
https://koji.fedoraproject.org/koji/buildinfo?buildID=836891

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

eseyman pushed to perl-Moose (master). "Update to 2.2000"

[notifications]

From c375b0552d88c89f42ff98450736d0b590671dd2 Mon Sep 17 00:00:00 2001
From: Emmanuel Seyman 
Date: Sun, 29 Jan 2017 12:02:35 +0100
Subject: Update to 2.2000

---
 .gitignore  | 1 +
 perl-Moose.spec | 5 -
 sources | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index c835364..5ad0535 100644
--- a/.gitignore
+++ b/.gitignore
@@ -37,3 +37,4 @@
 /Moose-2.1805.tar.gz
 /Moose-2.1806.tar.gz
 /Moose-2.1807.tar.gz
+/Moose-2.2000.tar.gz
diff --git a/perl-Moose.spec b/perl-Moose.spec
index 8e506c3..8f731bf 100644
--- a/perl-Moose.spec
+++ b/perl-Moose.spec
@@ -1,6 +1,6 @@
 Name:   perl-Moose
 Summary:Complete modern object system for Perl 5
-Version:2.1807
+Version:2.2000
 Release:1%{?dist}
 License:GPL+ or Artistic
 
@@ -173,6 +173,9 @@ make test
 %{_mandir}/man3/Test::Moose*
 
 %changelog
+* Sun Jan 29 2017 Emmanuel Seyman  - 2.2000-1
+- Update to 2.2000
+
 * Thu Dec 22 2016 Paul Howarth  - 2.1807-1
 - Update to 2.1807
 
diff --git a/sources b/sources
index 0c8556e..c753813 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (Moose-2.1807.tar.gz) = 
ed06452cb7bbeecab8ba237448175f290a21b68bb3f3c15d530d2828968159fe9b9259a8d9e5fc82596b47a4cc571f558557f5c52558733dec2d5eb6b055af13
+SHA512 (Moose-2.2000.tar.gz) = 
a29ba5d8dcb493e7e05cd228253b06f6ea86f9929347ea42bffa77a7253b35fc20fda12fff6e83702d531b8ddc646d25d041e45cb4d39f2e812541121ae2
-- 
cgit v1.1



https://src.fedoraproject.org/cgit/perl-Moose.git/commit/?h=master=c375b0552d88c89f42ff98450736d0b590671dd2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

eseyman uploaded Moose-2.2000.tar.gz for perl-Moose

[notifications]

a29ba5d8dcb493e7e05cd228253b06f6ea86f9929347ea42bffa77a7253b35fc20fda12fff6e83702d531b8ddc646d25d041e45cb4d39f2e812541121ae2
  Moose-2.2000.tar.gz

https://src.fedoraproject.org/lookaside/pkgs/perl-Moose/Moose-2.2000.tar.gz/sha512/a29ba5d8dcb493e7e05cd228253b06f6ea86f9929347ea42bffa77a7253b35fc20fda12fff6e83702d531b8ddc646d25d041e45cb4d39f2e812541121ae2/Moose-2.2000.tar.gz
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1416589] perl-Dancer2-0.204004 is available

[bugzilla]

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



--- Comment #8 from Upstream Release Monitoring 
 ---
eseyman's perl-Dancer2-0.204004-1.fc26 completed
http://koji.fedoraproject.org/koji/buildinfo?buildID=836896

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

eseyman pushed to perl-Dancer2 (master). "Update to 0.204004"

[notifications]

From 774fcf0b7fbf2a265ce196751a251ddd80791b11 Mon Sep 17 00:00:00 2001
From: Emmanuel Seyman 
Date: Sun, 29 Jan 2017 11:38:38 +0100
Subject: Update to 0.204004

---
 .gitignore| 1 +
 perl-Dancer2.spec | 8 ++--
 sources   | 2 +-
 3 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/.gitignore b/.gitignore
index 2d423ab..56ccf1c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -12,3 +12,4 @@
 /Dancer2-0.204000.tar.gz
 /Dancer2-0.204001.tar.gz
 /Dancer2-0.204002.tar.gz
+/Dancer2-0.204004.tar.gz
diff --git a/perl-Dancer2.spec b/perl-Dancer2.spec
index 4d57ca4..ba01260 100644
--- a/perl-Dancer2.spec
+++ b/perl-Dancer2.spec
@@ -1,11 +1,11 @@
 Name:   perl-Dancer2
-Version:0.204002
+Version:0.204004
 Release:1%{?dist}
 Summary:Lightweight yet powerful web application framework
 License:GPL+ or Artistic
 Group:  Development/Libraries
 URL:http://search.cpan.org/dist/Dancer2/
-Source0:
http://search.cpan.org/CPAN/authors/id/C/CR/CROMEDOME/Dancer2-%{version}.tar.gz
+Source0:
http://search.cpan.org/CPAN/authors/id/X/XS/XSAWYERX/Dancer2-%{version}.tar.gz
 BuildArch:  noarch
 BuildRequires:  findutils
 BuildRequires:  make
@@ -74,6 +74,7 @@ BuildRequires:  perl(Sub::Quote)
 BuildRequires:  perl(Template)
 BuildRequires:  perl(Template::Tiny)
 BuildRequires:  perl(Test::Builder)
+BuildRequires:  perl(Test::EOL)
 BuildRequires:  perl(Test::More) >= 0.92
 BuildRequires:  perl(Type::Library)
 BuildRequires:  perl(URI)
@@ -170,6 +171,9 @@ provides nice, easily-extendable CLI interface for it.
 %{_bindir}/*
 
 %changelog
+* Sun Jan 29 2017 Emmanuel Seyman  - 0.204004-1
+- Update to 0.204004
+
 * Sun Dec 25 2016 Emmanuel Seyman  - 0.204002-1
 - Update to 0.204002
 
diff --git a/sources b/sources
index 752ba2a..1d6f263 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (Dancer2-0.204002.tar.gz) = 
257a0c9e40bad749878114be38d7f7654fafecf03e6f68a315170607e7530828f396650d0e3a8d6f905be9c4546cb2f4a96f957f3aefdcbafb7bb800060ca0a3
+SHA512 (Dancer2-0.204004.tar.gz) = 
3d3f4a869d944ac8fb1500f35b3f417ec590c5a087b9091da4842fd89dec1fd8ad38eb22cdf152b88e8f4ff77275705ee1812785a35436e26ff40707c80251f2
-- 
cgit v1.1



https://src.fedoraproject.org/cgit/perl-Dancer2.git/commit/?h=master=774fcf0b7fbf2a265ce196751a251ddd80791b11
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: ImportError: No module named kivy, when run make html

[Mathieu Bridon]

On Sun, 2017-01-29 at 09:51 +, Martin Gansser wrote:
> thanks for your answer.
> 
> my question is, should i build for both python version the html files
> ?
> cd doc && make html PYTHONPATH=../build/lib.linux-%{_arch}-
> %{python2_version}
> cd ..
> cd doc && make html PYTHONPATH=../build/lib.linux-%{_arch}-
> %{python3_version}

Up to you.

Is the documentation going to be different between the python2-kivy and
python3-kivy package?

If yes, then having both python2-kivy-doc and python3-kivy-doc makes
sense.

Otherwise, just build it once as python-kivy-doc (bonus points if you
make it noarch) with whichever version of Python (although python3
being the default now, that's probably the one to use).

There's no need to do more work than necessary.


-- 
Mathieu
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

eseyman uploaded Dancer2-0.204004.tar.gz for perl-Dancer2

[notifications]

3d3f4a869d944ac8fb1500f35b3f417ec590c5a087b9091da4842fd89dec1fd8ad38eb22cdf152b88e8f4ff77275705ee1812785a35436e26ff40707c80251f2
  Dancer2-0.204004.tar.gz

https://src.fedoraproject.org/lookaside/pkgs/perl-Dancer2/Dancer2-0.204004.tar.gz/sha512/3d3f4a869d944ac8fb1500f35b3f417ec590c5a087b9091da4842fd89dec1fd8ad38eb22cdf152b88e8f4ff77275705ee1812785a35436e26ff40707c80251f2/Dancer2-0.204004.tar.gz
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

eseyman pushed to perl-Mojolicious (master). "Update to 7.22"

[notifications]

From ab1b2c3d2b88948e28fe3285bd9fc97c22704bd4 Mon Sep 17 00:00:00 2001
From: Emmanuel Seyman 
Date: Sun, 29 Jan 2017 11:13:31 +0100
Subject: Update to 7.22

---
 .gitignore| 1 +
 perl-Mojolicious.spec | 5 -
 sources   | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index a8e6023..4686934 100644
--- a/.gitignore
+++ b/.gitignore
@@ -216,3 +216,4 @@ Mojolicious-0.26.tar.gz
 /Mojolicious-7.14.tar.gz
 /Mojolicious-7.20.tar.gz
 /Mojolicious-7.21.tar.gz
+/Mojolicious-7.22.tar.gz
diff --git a/perl-Mojolicious.spec b/perl-Mojolicious.spec
index 5b49fb8..c9ce709 100644
--- a/perl-Mojolicious.spec
+++ b/perl-Mojolicious.spec
@@ -1,5 +1,5 @@
 Name:   perl-Mojolicious
-Version:7.21
+Version:7.22
 Release:1%{?dist}
 Summary:A next generation web framework for Perl
 License:Artistic 2.0
@@ -76,6 +76,9 @@ make test
 %{perl_vendorlib}/Test
 
 %changelog
+* Sun Jan 29 2017 Emmanuel Seyman  - 7.22-1
+- Update to 7.22
+
 * Tue Jan 24 2017 Emmanuel Seyman  - 7.21-1
 - Update to 7.21
 
diff --git a/sources b/sources
index 53413e9..625ed8e 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (Mojolicious-7.21.tar.gz) = 
05f2688b7377b47c262e3a3f43610673e72ead7bf486da83066b581ececc94f57495efbcc3536a11ab3a401f098052d26962aca7df0f1b7de90fd6e7efbfcd36
+SHA512 (Mojolicious-7.22.tar.gz) = 
0abfceac89e6e6264ecdcaa3589d69eb4a5bd296019835effe9794f59848f576a4684565103bcb1cb0aefd94f19f4a171555217c93dff4c11ddfde49054b3f6c
-- 
cgit v1.1



https://src.fedoraproject.org/cgit/perl-Mojolicious.git/commit/?h=master=ab1b2c3d2b88948e28fe3285bd9fc97c22704bd4
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

eseyman uploaded Mojolicious-7.22.tar.gz for perl-Mojolicious

[notifications]

0abfceac89e6e6264ecdcaa3589d69eb4a5bd296019835effe9794f59848f576a4684565103bcb1cb0aefd94f19f4a171555217c93dff4c11ddfde49054b3f6c
  Mojolicious-7.22.tar.gz

https://src.fedoraproject.org/lookaside/pkgs/perl-Mojolicious/Mojolicious-7.22.tar.gz/sha512/0abfceac89e6e6264ecdcaa3589d69eb4a5bd296019835effe9794f59848f576a4684565103bcb1cb0aefd94f19f4a171555217c93dff4c11ddfde49054b3f6c/Mojolicious-7.22.tar.gz
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: ImportError: No module named kivy, when run make html

[Martin Gansser]

thanks for your answer.

my question is, should i build for both python version the html files ?
cd doc && make html PYTHONPATH=../build/lib.linux-%{_arch}-%{python2_version}
cd ..
cd doc && make html PYTHONPATH=../build/lib.linux-%{_arch}-%{python3_version}
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [embree] patch refused to be applied

[Tom Hughes]

On 29/01/17 05:37, Luya Tshimbalanga wrote:


I applied a patch sent by upstream but some odd reason, the build kept
on failing

https://koji.fedoraproject.org/koji/taskinfo?taskID=17472254

I include the patch for preview so someone can see what went wrong.


You need -p1 when applying the patch.

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org