On 16. 05. 23 16:32, Sandro wrote:
On 16-05-2023 16:04, Petr Viktorin wrote:
Did I misunderstand/misinterpret the guidelines? The review is
currently stalled due to the PyPI parity issue.
Should I approach PyPI folks myself and ask them to block
vkbasalt-cli for me? Any kind of guidance is
On 16-05-2023 16:04, Petr Viktorin wrote:
Did I misunderstand/misinterpret the guidelines? The review is
currently stalled due to the PyPI parity issue.
Should I approach PyPI folks myself and ask them to block vkbasalt-cli
for me? Any kind of guidance is much appreciated.
Hi! Sorry for the
On 16-05-2023 15:56, Maxwell G wrote:
On Tue May 16, 2023 at 13:15 +0200, Sandro wrote:
Did I misunderstand/misinterpret the guidelines? The review is currently
stalled due to the PyPI parity issue.
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2188653
I didn't mean to hold up the package
On 16. 05. 23 13:15, Sandro wrote:
On 05-05-2023 15:10, Sandro wrote:
On 27-04-2023 14:26, Sandro wrote:
Well, I submitted the package for review [2] and have been told that
vkbasalt not being published on PyPI is an issue wrt naming parity.
So, I filed a bug requesting publication on PyPI
On Tue May 16, 2023 at 13:15 +0200, Sandro wrote:
> Did I misunderstand/misinterpret the guidelines? The review is currently
> stalled due to the PyPI parity issue.
>
> > [2] https://bugzilla.redhat.com/show_bug.cgi?id=2188653
I didn't mean to hold up the package on this. It should be fixed, but
On 05-05-2023 15:10, Sandro wrote:
On 27-04-2023 14:26, Sandro wrote:
Well, I submitted the package for review [2] and have been told that
vkbasalt not being published on PyPI is an issue wrt naming parity.
So, I filed a bug requesting publication on PyPI [3], but I haven't
heard back from
On 27-04-2023 14:26, Sandro wrote:
Well, I submitted the package for review [2] and have been told that
vkbasalt not being published on PyPI is an issue wrt naming parity.
So, I filed a bug requesting publication on PyPI [3], but I haven't
heard back from upstream, yet. If upstream remains
