Bug 1434086 - Milkytracker 1.0.0 is available
Summary: Milkytracker 1.0.0 is available
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: milkytracker
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Joonas Sarajärvi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-20 17:03 UTC by Joonas Sarajärvi
Modified: 2018-02-04 06:14 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-02-04 06:14:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joonas Sarajärvi 2017-03-20 17:03:18 UTC
Description of problem:
Current version is out of date

Version-Release number of selected component (if applicable):
0.90.86-5.fc26

Expected results:
Milkytracker 1.0.0 is available in repos

Additional info:
This is a bit silly bug for myself, but I wished to test if there is some integration between Koji and BZ.

Comment 1 Joonas Sarajärvi 2017-03-20 17:55:31 UTC
1.0.0 was built for Rawhide. Also planning to do F26.

Comment 2 Fedora Update System 2017-03-20 18:13:36 UTC
milkytracker-1.0.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-87c7357943

Comment 3 Fedora Update System 2017-03-21 14:25:30 UTC
milkytracker-1.0.0-1.fc26 has been pushed to the Fedora 26 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-87c7357943

Comment 4 Jan Kurik 2017-08-15 07:55:36 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 5 Joonas Sarajärvi 2018-02-04 06:14:33 UTC
This had basically been forgotten. I think it is a bad idea to push the update through at this point.

In case anyone is actually waiting to get this update to stable, please comment and reopen.


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