sys-fs/cryfs: bump to 0.10.3 #20733
sys-fs/cryfs: bump to 0.10.3 #20733
Conversation
|
Thanks! Can you commit with 'repoman commit' or 'pkgdev commit' to ensure that the commit message is right? Also, we avoid 'git mv' in general because we need to keep the old version around. The new version needs to be committed with unstable keywords ( The bot should shortly give some other needed information. |
Pull Request assignmentSubmitter: @DankDumpster sys-fs/cryfs: @aristocrates, @gentoo/proxy-maint Linked bugsNo 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. If you do not receive any reply to this pull request, please open or link a bug to attract the attention of maintainers. Missing GCO sign-offPlease read the terms of Gentoo Certificate of Origin and acknowledge them by adding a sign-off to all your commits. In order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
gentoo-bot
added
assigned
Pull request CI reportReport generated at: 2021-05-09 03:14 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
|
Sorry for that, it should be fixed now! 😄 |
Pull request CI reportReport generated at: 2021-05-09 03:24 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
|
@thesamesam could you take a look? |
|
Looking good! Two questions:
|
|
Sorry forgot the gco sign off |
Pull request CI reportReport generated at: 2021-05-09 08:49 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Package-Manager: Portage-3.0.18, Repoman-3.0.3 Signed-off-by: Matthew Bakhtiari <dev@mtbk.me>
|
@thesamesam sorry for mention but is the sign off correct? |
Pull request CI reportReport generated at: 2021-05-09 09:29 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
|
Looks great now! Can test later :) |
| PATCHES=( | ||
| # TODO upstream: | ||
| "${FILESDIR}/0.10.2-unbundle-libs.patch" | ||
| "${FILESDIR}/0.10.2-install-targets.patch" |
There was a problem hiding this comment.
You forgot to test after changing ;)
You're missing a ${PN} here. It doesn't apply right now:
>>> Preparing source in /var/tmp/portage/sys-fs/cryfs-0.10.3/work ...
* Applying 0.10.2-unbundle-libs.patch ...
/var/tmp/portage/sys-fs/cryfs-0.10.3/temp/environment: line 1611: /var/tmp/portage/sys-fs/cryfs-0.10.3/files/0.10.2-unbundle-libs.patch: No such file or directory
/var/tmp/portage/sys-fs/cryfs-0.10.3/temp/environment: line 1614: /var/tmp/portage/sys-fs/cryfs-0.10.3/files/0.10.2-unbundle-libs.patch: No such file or directory [ !! ]
* ERROR: sys-fs/cryfs-0.10.3::gentoo failed (prepare phase):
* patch -p1 failed with /var/tmp/portage/sys-fs/cryfs-0.10.3/files/0.10.2-unbundle-libs.patch
*
* Call stack:
* ebuild.sh, line 125: Called src_prepare
* environment, line 3516: Called cmake_src_prepare
* environment, line 1528: Called default_src_prepare
* phase-functions.sh, line 920: Called __eapi6_src_prepare
* environment, line 237: Called eapply '/var/tmp/portage/sys-fs/cryfs-0.10.3/files/0.10.2-unbundle-libs.patch' '/var/tmp/portage/sys-fs/cryfs-0.10.3/files/0.10.2-install-targets.patch'
* environment, line 1679: Called _eapply_patch '/var/tmp/portage/sys-fs/cryfs-0.10.3/files/0.10.2-unbundle-libs.patch'
* environment, line 1617: Called __helpers_die 'patch -p1 failed with /var/tmp/portage/sys-fs/cryfs-0.10.3/files/0.10.2-unbundle-libs.patch'
* isolated-functions.sh, line 112: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=sys-fs/cryfs-0.10.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-fs/cryfs-0.10.3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-fs/cryfs-0.10.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-fs/cryfs-0.10.3/temp/environment'.
* Working directory: '/var/tmp/portage/sys-fs/cryfs-0.10.3/work'
* S: '/var/tmp/portage/sys-fs/cryfs-0.10.3/work'
I'll fix
|
Cheers, I applied the GCC 11 patch too |
No description provided.