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-misc/seafile{,-client}: version bump to 8.0.6 #24544

Closed
wants to merge 2 commits into from

Conversation

CaseOf
Copy link
Contributor

@CaseOf CaseOf commented Mar 13, 2022

No description provided.

@gentoo-bot
Copy link

Pull Request assignment

Submitter: @CaseOf
Areas affected: ebuilds
Packages affected: net-misc/seafile, net-misc/seafile-client

net-misc/seafile: @CaseOf, @gentoo/proxy-maint
net-misc/seafile-client: @CaseOf, @gentoo/proxy-maint

Linked bugs

No bugs to link found. If your pull request references any of the Gentoo bug reports, please add appropriate GLEP 66 tags to the commit message and request reassignment.


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). labels Mar 13, 2022
@gentoo-repo-qa-bot
Copy link
Collaborator

Pull request CI report

Report generated at: 2022-03-14 00:06 UTC
Newest commit scanned: dcb1c7f
Status: ✅ good

There are existing issues already. Please look into the report to make sure none of them affect the packages in question:
https://qa-reports.gentoo.org/output/gentoo-ci/d234ab0b84/output.html

Copy link
Member

@MatthewGentoo MatthewGentoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks :) Some ideas for next time in the review.

I also filed a stabilisation bug. Maybe once version 8.0.5 is marked as stable, you could go and delete all of the old versions.


DESCRIPTION="File syncing and sharing software with file encryption and group sharing"
HOMEPAGE="https://www.seafile.com/ https://github.com/haiwen/seafile/"
SRC_URI="https://github.com/haiwen/${PN}/archive/${RELEASE_COMMIT}.tar.gz -> ${P}.tar.gz"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To save a bit of manual work each update, you can use ${PV} here like this:

Suggested change
SRC_URI="https://github.com/haiwen/${PN}/archive/${RELEASE_COMMIT}.tar.gz -> ${P}.tar.gz"
SRC_URI="https://github.com/haiwen/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"

(S="..." will also need changing)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,
I was using commit hash since some versions ago because upstream was changing tags to other commit without warning.
Then I thought it was better to keep this behavior to avoid unnecessary issues.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, seconding this. I've seen this upstream moving tags around before, and not only once.

fwiw maybe a note in the ebuild be nice so other developers don't wonder why every time?

# Copyright 1999-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2

EAPI=7
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we could bump to EAPI-8 next time :)

Suggested change
EAPI=7
EAPI=8


DESCRIPTION="Seafile desktop client"
HOMEPAGE="https://www.seafile.com/ https://github.com/haiwen/seafile-client/"
SRC_URI="https://github.com/haiwen/${PN}/archive/${RELEASE_COMMIT}.tar.gz -> ${P}.tar.gz"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above, since the upstream are still creating tags for each release, you can use ${PV} here.

Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Quentin Retornaz <gentoo@retornaz.com>
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Quentin Retornaz <gentoo@retornaz.com>
@gentoo-repo-qa-bot
Copy link
Collaborator

Pull request CI report

Report generated at: 2022-03-31 23:04 UTC
Newest commit scanned: c0b0cb0
Status: ✅ good

There are existing issues already. Please look into the report to make sure none of them affect the packages in question:
https://qa-reports.gentoo.org/output/gentoo-ci/74c7e38721/output.html

@MatthewGentoo
Copy link
Member

Sorry for the delay, I saw https://bugs.gentoo.org/685920 and wanted to make sure that it was okay to keep in ::gentoo :)

@gentoo-bot gentoo-bot closed this in 795880d Apr 3, 2022
@CaseOf CaseOf deleted the seafile branch May 15, 2022 00:47
@CaseOf CaseOf restored the seafile branch May 15, 2022 00:47
@CaseOf CaseOf deleted the seafile branch May 15, 2022 00:48
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). self-maintained The PR changes only packages that are maintained by the submitter (i.e. no need to ask anybody else)
Projects
None yet
5 participants