Possible bug on setting whitelisted packages
Hello devpi-Team, we were using devpi-client to set the formerly pypi_whitelist and everything was working as expected. Recently we updated to devpi-server 3.0.1 (running export/import cycle), devpi-web 3.0.0, and devpi-client 2.5.0. From that moment on we switched from setting pypi_whitelist to mirror_whitelist. Unfortunately the result is not as expected: We are executing: devpi index /descript_cli/stable "mirror_whitelist=django-cms,Django,django-devserver,django-exclusivebooleanfield,South,pywin32" But as a result devpi web shows the following: whitelisted packages , , , , , - - - 2 3 D S a a a a a b c c d d d d d e e e e e e e f g g g g h i i i j j j j l l l m n n n n n n o o o o o o o p r r s s s t u u v v v w x y The command: devpi index /descript_cli/stable Results in: type=stage bases=root/pypi volatile=False acl_upload=descript_cli pypi_whitelist= mirror_whitelist=django-cms,Django,django-devserver,django-exclusivebooleanfield,South,pywin32 The whitelist setting is not working. To circumvent this issue we are using mirror_whitelist=* in the meantime to circumvent the bug. Using the asterisk works like expected. Can please someone support us on that issue? Regards, Henk Kahlfuss
I can confirm the bug. I'm very baffled by it though. Regards, Florian Schulze On 2 Mar 2016, at 11:00, Henk Kahlfuss wrote:
Hello devpi-Team,
we were using devpi-client to set the formerly pypi_whitelist and everything was working as expected.
Recently we updated to devpi-server 3.0.1 (running export/import cycle), devpi-web 3.0.0, and devpi-client 2.5.0. From that moment on we switched from setting pypi_whitelist to mirror_whitelist.
Unfortunately the result is not as expected:
We are executing: devpi index /descript_cli/stable "mirror_whitelist=django-cms,Django,django-devserver,django-exclusivebooleanfield,South,pywin32"
But as a result devpi web shows the following: whitelisted packages
, , , , , - - - 2 3 D S a a a a a b c c d d d d d e e e e e e e f g g g g h i i i j j j j l l l m n n n n n n o o o o o o o p r r s s s t u u v v v w x y
The command: devpi index /descript_cli/stable
Results in: type=stage bases=root/pypi volatile=False acl_upload=descript_cli pypi_whitelist=
mirror_whitelist=django-cms,Django,django-devserver,django-exclusivebooleanfield,South,pywin32
The whitelist setting is not working.
To circumvent this issue we are using mirror_whitelist=* in the meantime to circumvent the bug. Using the asterisk works like expected.
Can please someone support us on that issue?
Regards, Henk Kahlfuss
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
On 2 Mar 2016, at 11:20, Florian Schulze wrote:
I can confirm the bug. I'm very baffled by it though.
One should always test things explicitly and not rely on implicit behaviour. Preparing a PR and we will hopefully make a release soon. Regards, Florian Schulze
On 2 Mar 2016, at 11:00, Henk Kahlfuss wrote:
Hello devpi-Team,
we were using devpi-client to set the formerly pypi_whitelist and everything was working as expected.
Recently we updated to devpi-server 3.0.1 (running export/import cycle), devpi-web 3.0.0, and devpi-client 2.5.0. From that moment on we switched from setting pypi_whitelist to mirror_whitelist.
Unfortunately the result is not as expected:
We are executing: devpi index /descript_cli/stable "mirror_whitelist=django-cms,Django,django-devserver,django-exclusivebooleanfield,South,pywin32"
But as a result devpi web shows the following: whitelisted packages
, , , , , - - - 2 3 D S a a a a a b c c d d d d d e e e e e e e f g g g g h i i i j j j j l l l m n n n n n n o o o o o o o p r r s s s t u u v v v w x y
The command: devpi index /descript_cli/stable
Results in: type=stage bases=root/pypi volatile=False acl_upload=descript_cli pypi_whitelist=
mirror_whitelist=django-cms,Django,django-devserver,django-exclusivebooleanfield,South,pywin32
The whitelist setting is not working.
To circumvent this issue we are using mirror_whitelist=* in the meantime to circumvent the bug. Using the asterisk works like expected.
Can please someone support us on that issue?
Regards, Henk Kahlfuss
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
Hi! I made a development release available: https://devpi.net/fschulze/dev/+f/20f/71d64fc847835/devpi-server-3.0.2.dev1.... We hope to make a release tomorrow. Regards, Florian Schulze On 2 Mar 2016, at 11:00, Henk Kahlfuss wrote:
Hello devpi-Team,
we were using devpi-client to set the formerly pypi_whitelist and everything was working as expected.
Recently we updated to devpi-server 3.0.1 (running export/import cycle), devpi-web 3.0.0, and devpi-client 2.5.0. From that moment on we switched from setting pypi_whitelist to mirror_whitelist.
Unfortunately the result is not as expected:
We are executing: devpi index /descript_cli/stable "mirror_whitelist=django-cms,Django,django-devserver,django-exclusivebooleanfield,South,pywin32"
But as a result devpi web shows the following: whitelisted packages
, , , , , - - - 2 3 D S a a a a a b c c d d d d d e e e e e e e f g g g g h i i i j j j j l l l m n n n n n n o o o o o o o p r r s s s t u u v v v w x y
The command: devpi index /descript_cli/stable
Results in: type=stage bases=root/pypi volatile=False acl_upload=descript_cli pypi_whitelist=
mirror_whitelist=django-cms,Django,django-devserver,django-exclusivebooleanfield,South,pywin32
The whitelist setting is not working.
To circumvent this issue we are using mirror_whitelist=* in the meantime to circumvent the bug. Using the asterisk works like expected.
Can please someone support us on that issue?
Regards, Henk Kahlfuss
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
Hi, we tried your development release and it worked. Thanks for your quick response. On testing the new development release we also found another possible bug in correlation with this point from the devpi-server 3.0.0 release notes "internally use normalized project names everywhere, simplifying code and slightly speeding up some operations." If we provide mirror_whitelist=Django it is not recognized and the whitelist is not working for this package. Instead if we set mirror_whitelist=django everything works as expected. Perhaps the values (project names) for mirror_whitelist should also be normalized before being set. Regards, Henk Kahlfuss Am Mittwoch, 2. März 2016 12:47:29 UTC+1 schrieb Florian Schulze:
Hi!
I made a development release available:
https://devpi.net/fschulze/dev/+f/20f/71d64fc847835/devpi-server-3.0.2.dev1....
We hope to make a release tomorrow.
Regards, Florian Schulze
On 2 Mar 2016, at 11:00, Henk Kahlfuss wrote:
Hello devpi-Team,
we were using devpi-client to set the formerly pypi_whitelist and everything was working as expected.
Recently we updated to devpi-server 3.0.1 (running export/import cycle), devpi-web 3.0.0, and devpi-client 2.5.0. From that moment on we switched from setting pypi_whitelist to mirror_whitelist.
Unfortunately the result is not as expected:
We are executing: devpi index /descript_cli/stable
"mirror_whitelist=django-cms,Django,django-devserver,django-exclusivebooleanfield,South,pywin32"
But as a result devpi web shows the following: whitelisted packages
, , , , , - - - 2 3 D S a a a a a b c c d d d d d e e e e e e e f g g g g h i i i j j j j l l l m n n n n n n o o o o o o o p r r s s s t u u v v v w x y
The command: devpi index /descript_cli/stable
Results in: type=stage bases=root/pypi volatile=False acl_upload=descript_cli pypi_whitelist=
mirror_whitelist=django-cms,Django,django-devserver,django-exclusivebooleanfield,South,pywin32
The whitelist setting is not working.
To circumvent this issue we are using mirror_whitelist=* in the meantime to circumvent the bug. Using the asterisk works like expected.
Can please someone support us on that issue?
Regards, Henk Kahlfuss
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-...@googlegroups.com <javascript:>. To post to this group, send email to dev...@googlegroups.com
<javascript:>.
Visit this group at https://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
If we provide mirror_whitelist=Django it is not recognized and the whitelist is not working for this package. Instead if we set mirror_whitelist=django everything works as expected.
Perhaps the values (project names) for mirror_whitelist should also be normalized before being set.
Very good idea! Regards, Florian Schulze
participants (2)
-
Florian Schulze -
Henk Kahlfuss