Latest upstream release: 0.17.1 Current version/release in rawhide: 0.17-2.fc30 URL: http://martinos.org/mne/ 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/8152/
Manas, Could you look at this please? Looks like a straight forward package update? Thanks, Ankur!
(In reply to Ankur Sinha (FranciscoD) from comment #1) > Manas, > > Could you look at this please? Looks like a straight forward package update? > > Thanks, > Ankur! It seems it is already up to date after looking at the spec.
(In reply to Manas Mangaonkar (Pac23) from comment #2) > (In reply to Ankur Sinha (FranciscoD) from comment #1) > > Manas, > > > > Could you look at this please? Looks like a straight forward package update? > > > > Thanks, > > Ankur! > > It seems it is already up to date after looking at the spec. I could be wrong though.
The package is at 0.17-2. So version 0.17 (which can be thought of as 0.17.0) and release 2. This bug indicates that version 0.17.1 (so > 0.17) is available so an update can be made. The updated package will then be 0.17.1-1, 0.17.1-2 and so on. Would you be able to do the update and open a PR? Please assign the bug to yourself and change the status from NEW to ASSIGNED if that sound fine.
(In reply to Ankur Sinha (FranciscoD) from comment #4) > The package is at 0.17-2. So version 0.17 (which can be thought of as > 0.17.0) and release 2. This bug indicates that version 0.17.1 (so > 0.17) is > available so an update can be made. The updated package will then be > 0.17.1-1, 0.17.1-2 and so on. > > Would you be able to do the update and open a PR? Please assign the bug to > yourself and change the status from NEW to ASSIGNED if that sound fine. ah yes noticed it in the spec,sorry did'nt notice it before,will do . Thanks!
Awesome, thanks very much!
(In reply to Ankur Sinha (FranciscoD) from comment #6) > Awesome, thanks very much! So i updated it,i had some doubts about the source file that is there. also my push to the repo was rejected.
(In reply to Manas Mangaonkar (Pac23) from comment #7) > (In reply to Ankur Sinha (FranciscoD) from comment #6) > > Awesome, thanks very much! > > So i updated it, Great, thanks. > i had some doubts about the source file that is there. > also my push to the repo was rejected. That's because while you are a packager, you are not in the neuro-sig packager group yet. Please fork the repo and open a PR. Someone will review and merge it, and then kick a build off (the usual). What is the issue with the source file? Please comment on the PR and we'll check it out over there. Cheers!
(In reply to Ankur Sinha (FranciscoD) from comment #8) > (In reply to Manas Mangaonkar (Pac23) from comment #7) > > (In reply to Ankur Sinha (FranciscoD) from comment #6) > > > Awesome, thanks very much! > > > > So i updated it, > > Great, thanks. > > > i had some doubts about the source file that is there. > > also my push to the repo was rejected. > > That's because while you are a packager, you are not in the neuro-sig > packager group yet. Please fork the repo and open a PR. Someone will review > and merge it, and then kick a build off (the usual). > > What is the issue with the source file? Please comment on the PR and we'll > check it out over there. > > Cheers! okay,so basically the sha checksum in there is autogenerated or is it to be added manually also,i used the inbuilt fedora sha512 <name_of_file> module to add the sha to it which fedpkg local(i treid testing) wont accept. What exactly is the process for the source file. Also my irc is broken btw,cant see the messages there if any sorry.
I suspect you need to go through these pages: - https://fedoraproject.org/wiki/Package_maintenance_guide - https://fedoraproject.org/wiki/Package_update_HOWTO?rd=PackageMaintainers/UpdatingPackageHowTo Do let me know if they don't clear your queries up.
python-mne-0.17.1-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea2140dfdf
python-mne-0.17.1-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-15a894d0a4
python-mne-0.17.1-1.fc28 has been pushed to the Fedora 28 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-2019-ea2140dfdf
python-mne-0.17.1-1.fc29 has been pushed to the Fedora 29 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-2019-15a894d0a4
python-mne-0.17.1-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
python-mne-0.17.1-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.