[14:38:49] <vdaskalov_> I know it's impossible by documentation but isn't there really no way to make small adjustments to a package I've just uploaded
[14:39:18] <vdaskalov_> It's my fault that I didn't verify all is good on TestPyPi site but still
[14:39:40] <vdaskalov_> My licensing information is just wrong https://pypi.org/project/dcli/
[14:42:00] <di_codes> vdaskalov_ the best way to fix this is to make a new release. if you don’t want to increase the version number, you can make it a “post” release `2.9.1.post0`
[14:42:59] <vdaskalov_> oh that sounds good. It's really a tedious process to create new release in our company currently. it's another long story :)
[14:43:15] <vdaskalov_> Is there public documentation about this option somewhere?
[14:47:33] <vdaskalov_> Ahaa, I guess what you mean is change the version string by appending .post0 at the end?
[15:02:02] <di_codes> vdaskalov_: correct. you mean documentation about post releases?
[15:03:17] <di_codes> you can find that here: <https://www.python.org/dev/peps/pep-0440/#post-releases>
[15:55:30] <di_codes> anyone remember who the person was who works at Travis and came in here to help with a PyPI outage? having troubles with builds at the moment: <https://travis-ci.org/pypa/warehouse/builds/378776987>
[17:01:34] <Habbie> di_codes, it was emdantrim who sadly fell out
[17:01:39] <Habbie> di_codes, what problem are you having?
[17:01:46] <Habbie> 17:22Z <emdantrim> as does emma@travis-ci.org. also, you can DM me here and it'll go more directly to my phone. I should be signed in indefinitely
[17:04:15] <di_codes> anyone at the sprints looking for something to do: i’d love for this to get fixed: <https://github.com/pypa/warehouse/issues/1536>
[17:07:34] <di_codes> Packaging mini-summit happening in 26C nowish