Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net-p2p/resilio-sync: fix upstream silent update #12128

Closed
wants to merge 1 commit into from

Conversation

SpiderX
Copy link
Contributor

@SpiderX SpiderX commented May 29, 2019

Closes: https://bugs.gentoo.org/686360
Signed-off-by: Vladimir Pavljuchenkov spiderx@spiderx.dp.ua
Package-Manager: Portage-2.3.66, Repoman-2.3.11

Closes: https://bugs.gentoo.org/686360
Signed-off-by: Vladimir Pavljuchenkov <spiderx@spiderx.dp.ua>
Package-Manager: Portage-2.3.66, Repoman-2.3.11
@gentoo-bot
Copy link

Copyright policy change

Please note that on 2018-09-15 Trustees have approved new Gentoo copyright policy. All contributions made to Gentoo need to follow this policy. If you include the Signed-off-by line in your commit message, you indicate that you have read the policy and agree to its terms. For more detailed explanation, please see the new Gentoo copyright policy explained article.

Pull Request assignment

Submitter: @SpiderX
Areas affected: ebuilds
Packages affected: net-p2p/resilio-sync

net-p2p/resilio-sync: @SpiderX, @gentoo/proxy-maint

Linked bugs

Bugs linked: 686360


In order to force reassignment and/or bug reference scan, please append [please reassign] to the pull request title.

Docs: Code of ConductCopyright policy (expl.) ● DevmanualGitHub PRsProxy-maint guide

@gentoo-bot gentoo-bot added self-maintained The PR changes only packages that are maintained by the submitter (i.e. no need to ask anybody else) assigned PR successfully assigned to the package maintainer(s). bug linked Bug/Closes found in footer, and cross-linked with the PR. labels May 29, 2019
@gentoo-repo-qa-bot
Copy link
Collaborator

Pull request CI report

Report generated at: 2019-05-29 16:30 UTC
Newest commit scanned: 7ae9e1c
Status: ✅ good

No issues found

@mgorny
Copy link
Member

mgorny commented Jun 9, 2019

I have to ask: have you compared the old and new distfiles?

@SpiderX
Copy link
Contributor Author

SpiderX commented Jun 9, 2019

I checked checksum and they was different.
After that emerged ebuild without any issue.

I am running this package with new distfiles for almost two weeks — no issues for now.

@mgorny
Copy link
Member

mgorny commented Jun 9, 2019

Sure but it would be nice to know why the checksum changed. Was there some change done? Rebuild accident? Upstream has been hacked and someone replaced distfiles with malicious stuff?

@SpiderX
Copy link
Contributor Author

SpiderX commented Jun 10, 2019

I got a confirmation from upstream that these changes were done by him.

http://img.spiderx.dp.ua/screen_17-51-35_KirSIre7.png

@Weuxel
Copy link

Weuxel commented Jun 17, 2019

Please merge.

@mgorny
Copy link
Member

mgorny commented Jun 17, 2019

I'm sorry, I haven't managed to find time to through my PR backlog yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assigned PR successfully assigned to the package maintainer(s). bug linked Bug/Closes found in footer, and cross-linked with the PR. self-maintained The PR changes only packages that are maintained by the submitter (i.e. no need to ask anybody else)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants