I just upgraded Django from version 3.0.11 to 3.2.15 receiving this confirmation
Successfully installed Django-3.2.15 asgiref-3.5.2
I also upgraded flufl.lock from version 7.0 to 7.1
Successfully installed flufl.lock-7.1
Then I restarted mailman, qcluster & gunicorn
Now for some reason I'm not receiving my own postings to the list whereas before I was. 'Receive own postings' is still set to yes.
Thank you!
-----Original Message----- From: David Newman <dnewman@networktest.com> Sent: Friday, July 8, 2022 11:29 AM To: mailman-users@mailman3.org Subject: [MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14
On 7/8/22 6:34 AM, Stephen J. Turnbull wrote:
David Newman writes:
Interesting -- that does produce two directories with names starting with a tilde:
/opt/mailman/venv/lib/python3.9/site-packages/~jango: /opt/mailman/venv/lib/python3.9/site-packages/~jango-3.0.14.dist-info:
I would guess that those are the previous versions before the upgrade, moved out of the way in case a revert-to-previous was needed. Again, guessing, they should have been removed by the upgrade process once the new package was fully installed. Was there an interrupted or partially successful upgrade in the past?
Yes
So I would guess you can remove them. Probably you have the relevant Ubuntu packages cached somewhere, and they're probably available from Ubuntu if you really wanted them.
This system runs Debian 11, with everything installed in a venv. I'm unclear on the relationship between the usual apt* tools and pip, and just do everything Mailman-related using pip.
On 7/8/22 7:47 AM, Mark Sapiro wrote:
When pip is doing an upgrade of the xyz package, it renames the existing package as ~yz and then ultimately deletes the old ~yz package after > successfully installing the new xyz. In this case, the upgrade was > aborted because of the Django<3.1 constraint in mailman-web and > apparently pip then installed Django<3.1 and left the ~jango* > directories behind.
Ahhh, that explains it.
Thanks for your replies. I've deleted the ~ directories and so far have not noticed any adverse effects.
dn
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/