mediawiki 1.39.5 unable to create new thumbnails

2023-12-27 Thread kjohnson
When I upload new files to our wiki, the thumbnails are not created. Thumbnails created prior to applying the 1.39.5 update still work fine. It appears that the location where new thumbnails would be created has changed with 1.39.5. How can I find out where mediawiki is trying to create files

Mailman3 archive does not display for me after upgrade to Bookworm

2023-09-06 Thread kjohnson
The Mailman3 mailing list forwarding, administration, and archive display all worked here under Bullseye. The symptom I see now is that when I try to view a mailing list archive with a web browser, I see a spinning star where I previously saw data. In addition to the package upgrades, I have

Disk writes much slower in Bookworm i386 [Was: svnadmin dump ...]

2023-08-14 Thread kjohnson
I have done additional research, and it now appears that programs that do extensive disk writes run much slower (3-6x) in Bookworm than they did in Bullseye. The two cases I have observed are 'svnadmin dump', and extracting an SQL backup of a Bacula database from Postgresql (backup file about 3

svnadmin dump much slower in Bookworm

2023-08-10 Thread kjohnson
A set of svnadmin dump commands that run as part of a backup procedure seem to be _much_ slower in Bookworm than in Bullseye. Prior to the upgrade to Bullseye, these commands took slightly less than one hour. After the upgrade, similar commands (dumping a few more revisions) require more than

RE: Determine packages made obsolete in Bookworm

2023-07-20 Thread kjohnson
> I would like to discover which currently installed packages in Bullseye (11) > will be obsolete (no longer available from a Debian repository) in Bookworm > (12) _before starting the upgrade process_. > It might be that there is a list of the more than 6,296 packages removed as > obsolete (

Determine packages made obsolete in Bookworm

2023-07-20 Thread kjohnson
I would like to discover which currently installed packages in Bullseye (11) will be obsolete (no longer available from a Debian repository) in Bookworm (12) _before starting the upgrade process_. It might be that there is a list of the more than 6,296 packages removed as obsolete (source: Debi

Re: mailman3 hyperkitty_import reports sqlite3.OperationalError

2022-07-22 Thread kjohnson
Ken Johnson wrote: > ... > Now I need to find out how to delete a mailing list from Mailman3 > and from django, so that I can practice again. > ... Mailman3: mailman remove django/hyperkitty: In this issue thread, Mark Sapiro points out that "Since HyperKitty 1.3.1 , a site admin has a d

Re: mailman3 hyperkitty_import reports sqlite3.OperationalError

2022-07-22 Thread kjohnson
Andy Smith apparently wrote: > ... > My process looked like this: > $ sudo -u list mailman import21 ${listname}@${mailman_host} > /path/to/${listname}/config.pck > $ sudo -u www-data /usr/share/mailman3-web/manage.py hyperkitty_import -l > ${listname}@${mailman_host} > /path/to/archives/priva

Re: mailman3 hyperkitty_import reports sqlite3.OperationalError

2022-07-21 Thread kjohnson
Charles Curley apparently wrote: > ... So what I would do instead is something like: > cd /var ; find -type f | xargs file | grep -i sqlite > ... > Perhaps there is some sort of error and the mention of sqlite is spurious? Mr. Curley, Thank you for your helpful and informative reply. I did no

How do I see fixed bugs for a package at bugs.debian.org?

2022-07-21 Thread kjohnson
How do I see fixed bugs for a package at bugs.debian.org? I can find open bugs from https://www.debian.org/Bugs/, but maybe something that has been fixed would give me insight. I would like to see fixed bugs for the mailman3 package, and related packages. I am trying to migrate from mailman2 t

mailman3 hyperkitty_import reports sqlite3.OperationalError

2022-07-21 Thread kjohnson
Summary: hyperkitty_import reports 'sqlite3.OperationalError: unable to open database file' during attempt to migrate from Mailman 2 to Mailman 3. I would be very pleased to receive suggestions on how to troubleshoot this further. Details: Background: The first part of my migration plan on th