Learn more about these different git repos.
Other Git URLs
Hi! I've given @lgmducazu temporary membership to the group. They're meant to be taking over the sci-tech spin, but they're not CLA+1 yet so their alias etc. doesn't work.
Opened this ticket as a tracker. When they've joined other FAS groups, we can remove them from here.
References: - https://pagure.io/fedora-project-schedule/issue/168
Metadata Update from @ankursinha: - Issue tagged with: S: Future-meeting, S: In review
Their account is @lducazu , they'll be using that. I'll add this one temporarily too.
@lducazu : we've had a ping on the mailing list about the scientific spin image failing etc. Would you have time to take a look please?
https://lists.fedoraproject.org/archives/list/scitech@lists.fedoraproject.org/message/2ICK55NVXOFNPSQH4FQXHEPLSCDNGWY3/
Hi Ankur,
Thanks for letting me know. I subscribed to that list and answered Christian.
Kind regards, -- Luc
On Sun, Jul 19, 2020 at 5:17 PM Ankur Sinha pagure@pagure.io wrote:
ankursinha added a new comment to an issue you are following: `` @lducazu : we've had a ping on the mailing list about the scientific spin image failing etc. Would you have time to take a look please? https://lists.fedoraproject.org/archives/list/scitech@lists.fedoraproject.org/message/2ICK55NVXOFNPSQH4FQXHEPLSCDNGWY3/ `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-join/Fedora-Join/issue/201
ankursinha added a new comment to an issue you are following: `` @lducazu : we've had a ping on the mailing list about the scientific spin image failing etc. Would you have time to take a look please?
https://lists.fedoraproject.org/archives/list/scitech@lists.fedoraproject.org/message/2ICK55NVXOFNPSQH4FQXHEPLSCDNGWY3/ ``
To reply, visit the link below or just reply to this email https://pagure.io/fedora-join/Fedora-Join/issue/201
I have a patch, but apparently not enough karma to push ;-) Can you please apply the attached patch? The build for the Fedora Scientific spin should succeed again.
Hi @lducazu : I don't see a patch attached here. Is it for a package or for the kickstarts?
Perhaps attachments get stripped from mails? Here is the patch inline, I used git format-patch. It is one for the kickstart files.
From e65725828317e1257f722c8d4a5041646b7ec053 Mon Sep 17 00:00:00 2001 From: Luc Ducazu lducazu@fedoraproject.org Date: Tue, 21 Jul 2020 17:54:38 +0200 Subject: [PATCH] Remove missing packages.
fedora-scientific-common.ks | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/fedora-scientific-common.ks b/fedora-scientific-common.ks index 904bb11..6a21a53 100644 --- a/fedora-scientific-common.ks +++ b/fedora-scientific-common.ks @@ -4,9 +4,9 @@ @engineering-and-scientific
# scilab -scilab -scilab-devel -scilab-doc +## scilab +## scilab-devel +## scilab-doc
# Remove sagemath explicitly? -sagemath @@ -128,8 +128,8 @@ dia inkscape xzgv gimp -ggobi -ggobi-devel +## ggobi +## ggobi-devel #g3data #Mayavi
-- 2.26.2
On Wed, Jul 22, 2020 at 8:05 PM Ankur Sinha pagure@pagure.io wrote:
ankursinha added a new comment to an issue you are following: Hi @lducazu : I don't see a patch attached here. Is it for a package or for the kickstarts? To reply, visit the link below or just reply to this email https://pagure.io/fedora-join/Fedora-Join/issue/201
ankursinha added a new comment to an issue you are following: Hi @lducazu : I don't see a patch attached here. Is it for a package or for the kickstarts?
Yes, I don't think patches go via e-mail.
I don't have commit access on the kickstart repo either. Only releng (release engineering) has. So, the process is to open a pull request that they'll review and merge.
Since you already have your changes, you'll also have a fork I guess? Could you open a PR here?
https://pagure.io/fedora-kickstarts/pull-requests
Thanks for your help. I just opened a PR.
On Wed, Jul 22, 2020 at 9:14 PM Ankur Sinha pagure@pagure.io wrote:
ankursinha added a new comment to an issue you are following: `` Yes, I don't think patches go via e-mail. I don't have commit access on the kickstart repo either. Only releng (release engineering) has. So, the process is to open a pull request that they'll review and merge. Since you already have your changes, you'll also have a fork I guess? Could you open a PR here? https://pagure.io/fedora-kickstarts/pull-requests `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-join/Fedora-Join/issue/201
ankursinha added a new comment to an issue you are following: `` Yes, I don't think patches go via e-mail.
https://pagure.io/fedora-kickstarts/pull-requests ``
@lducazu
HI! Sorry for ping you but, we've had this ticket open for a long time:
1.- We've found that we've had two FAS account for the same user: lducazu with a lot of activity lgmducazu with no activity 2.- We would like to cancel the duplicate account -> lgmducazu 3.- We would like to close this ticket because you're well integrated in the community.
As a Scitech Maintainer you should apply for this group in their respective FAS group to get CLA+1...
Are you agree with me?
Regards.,
Hi Hector,
Yes, please, delete account 'lgmducazu', this is a duplicate indeed. Feel free to close this ticket.
Thanks! -- Luc
On Fri, Nov 20, 2020 at 11:20 AM H=C3=A9ctor H. Louzao P. <pagure@pagure.io=
wrote: hhlp added a new comment to an issue you are following: `` @lducazu HI! Sorry for ping you but, we've had this ticket open for a long time: 1.- We've found that we've had two FAS account for the same user: lducazu with a lot of activity lgmducazu with no activity 2.- We would like to cancel the duplicate account -> lgmducazu 3.- We would like to close this ticket because you're well integrated in the community. Sugestion As a Scitech Maintainer you should apply for this group in their respective FAS group to get CLA+1... Are you agree with me? Regards., `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-join/Fedora-Join/issue/201
wrote:
hhlp added a new comment to an issue you are following: `` @lducazu
Regards., ``
thx for your quick response
Metadata Update from @hhlp: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.