Pypi publication is not working

[GeorgePantelakis]

The publication of the package to Pip is not working because of some email verification that is needed.

[GeorgePantelakis]

@x00Pavel since it is your account that is connected to it can you please take a look if you can fix it and if you still have access? Also, perhaps we should consider moving it to a non-personal upstream account so the active maintainer of the time will have access and fix these kinds of issues (if any).

[x00Pavel]

@GeorgePantelakis This problem is probably appeared because this package is published to my personal PyPi repository and I didn't maintain this account for a while. To solve this problem and prevent it in future, I would suggest to create/use some company account/repository. O

[GeorgePantelakis]

@x00Pavel I am glad that we are on the same page! Could you enable it for now until I figure out how to make an account and move it there?

[x00Pavel]

@GeorgePantelakis sure, I will check it later this evening.

[x00Pavel]

@GeorgePantelakis Hi. I've just updated settings in my PyPi account. Can you please check that it works? Also, there is an option to create the organisation in PyPi. If you would be able to create one, I think I would be able to transfer the package to the organisation / share somehow it with the organisation

[GeorgePantelakis]

@x00Pavel There is still a problem, a different one this time, which says that the file already exists (https://github.com/redhat-qe-security/SCAutolib/actions/runs/9413600787/job/25930684176). Can you check if is that file indeed there since I can only see up to the 3.2.2 version in Pip? Perhaps just updating the version will do it. Also, about the account I will take a look next week so leaving the issue open until we migrate it.

[x00Pavel]

@GeorgePantelakis

[GeorgePantelakis]

Yes please??

[x00Pavel]

@GeorgePantelakis Sorry, the comment hadn’t posted for some reasons.

The latest version is 3.2.2. So, just bump the version and everything should work.

Regrading accounts, there is an option to collaborate on the package maintains/ownership. I will need a username of the account for this

[GeorgePantelakis]

@x00Pavel Just an update, I have requested the organization to be created by Pypi for a week now but it hasn't been approved yet. Still waiting.

[GeorgePantelakis]

@x00Pavel, since I don't see much movement in the creation of the PyPI organization and we again can't upload it due to some error (https://github.com/redhat-qe-security/SCAutolib/actions/runs/10848823184/job/30106746901), would you be open to transferring the module to me?

[x00Pavel]

Hi @GeorgePantelakis

In such case I don't mind to maintain the PyPi repo myself. If you don't have anything against it, I will check what is wrong there and rich you out right when I will have some info. What do you think?

[GeorgePantelakis]

@x00Pavel,

I have no problem with it, if you have the time, at least until the organization is created. If we have any issue with uploading, I can create an issue here and assign it to you. For now, I think that if you enable 2-FA in your account, it will be sufficient.

Thank you!

[x00Pavel]

@GeorgePantelakis sure, fill free to assign such issues on me. I will check it ASAP

[x00Pavel]

@GeorgePantelakis what is your name on the PyPi? I will invite you for collaboration on this project

[x00Pavel]

@GeorgePantelakis also, the problem appears on the push to Test instance of PyPi. The question is do you still need this test repo? If not, you can just ignore this error in the workflow file or simply to delete this step

[GeorgePantelakis]

@x00Pavel,

Great, thank you.

My profile is https://pypi.org/user/gpantela/.

Now for the test instance of PyPi I don't think I use it at all (didn't know it existed) so probably we can simply skip that. It didn't run the production instance to see that it passed so I am not sure if we will not have the same issue in production as well.