Bug 1103432 - antimicro-2.4 is available
Summary: antimicro-2.4 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: antimicro
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Backus
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-31 14:11 UTC by Upstream Release Monitoring
Modified: 2014-06-22 23:58 UTC (History)
2 users (show)

Fixed In Version: antimicro-2.4-1.fc20
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-22 23:57:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2014-05-31 14:11:15 UTC
Latest upstream release: 2.4
Current version/release in Fedora Rawhide: 2.3.3-1.fc21
URL: https://api.github.com/repos/Ryochan7/antimicro/tags

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

Comment 1 Björn 'besser82' Esser 2014-06-01 14:50:01 UTC
Successfully imported and build on rawhide [1].

You can easily merge the changes down to the fXX-branches, build and push an update, if you want.  If you don't want to update on the fXX-branches, please change this bug's state to CLOSED ---> RAWHIDE


[1]  https://koji.fedoraproject.org/koji/buildinfo?buildID=520797

Comment 2 Jeff Backus 2014-06-02 22:16:07 UTC
Hi Björn,

Thanks for updating rawhide! I apologize for the noob question, but updating the fXX-branches will require another review, correct? Or can I simply push the update since the spec doesn't require a change?

Regards,
Jeff

Comment 3 Björn 'besser82' Esser 2014-06-03 07:03:07 UTC
(In reply to Jeff Backus from comment #2)
> Or can I simply push the update since the spec doesn't require a change?

Hey Jeff!

In this case you can simply git merge the master branch into the corresponding fXX-branch, push, build and update, since this package is pretty `self-contained` and wouldn't cause other pkgs to become b0rk3n.  There is no need to get this reviewed anytime again, but in case of renaming.

Cheers,
  Björn

Comment 4 Fedora Update System 2014-06-04 09:58:00 UTC
antimicro-2.4-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/antimicro-2.4-1.fc19

Comment 5 Fedora Update System 2014-06-04 10:02:17 UTC
antimicro-2.4-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/antimicro-2.4-1.fc20

Comment 6 Jeff Backus 2014-06-04 10:06:22 UTC
Hi Björn,

Thanks for the clarification. I've pushed updates for f19 and f20. Here are the Koji builds:
f19: http://koji.fedoraproject.org/koji/taskinfo?taskID=6923355
f20: http://koji.fedoraproject.org/koji/taskinfo?taskID=6923358

Thanks again for all your help!

Regards,
Jeff

Comment 7 Fedora Update System 2014-06-05 04:21:33 UTC
Package antimicro-2.4-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing antimicro-2.4-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7075/antimicro-2.4-1.fc19
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2014-06-22 23:57:12 UTC
antimicro-2.4-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2014-06-22 23:58:04 UTC
antimicro-2.4-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.