django-dbbackup: ugettext_lazy breaks with Django 4.0 alpha 1 release

Can a release be made including #342 (replace ugettext_lazy with gettext_lazy)?

The newly released Django 4.0 alpha 1 has dropped ugettext_lazy. The latest release of django-dbbackup still uses ugettext_lazy. This was addressed in #342 however not yet released, meaning of dbbackup run into errors and can not try their applications on Django 4.0 alpha 1 until this is done.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 7
  • Comments: 27 (19 by maintainers)

Most upvoted comments

Hey @ZuluPro

I’m coming over from the Jazzband GitHub organization. We’re currently the biggest organization for OSS Django packages.

I would be interested in taking temporary ownership for this repo and doing the necessary changes to get it transferred to Jazzband.

Including myself, there are various members that I’m sure would support maintenance for this repo.

4.0.0b0 has been released: https://pypi.org/project/django-dbbackup/4.0.0b0/ 🎉

I just confirmed that john had not been invited to PyPI, so I’ve sent him an invite.

Thanks!

I am currently not a maintainer on the GitHub repo though so I’ll need @johnthagen to add me as one if I am to tag releases in the future.

@Archmonger You have been invited as an owner to the django-dbackup organization

I have the ability to create releases and will do so once @johnthagen tags a solid build

4.0.0b0 has been tagged in GitHub, but as a pre-release it doesn’t show up in the main page UI, so it might not have been obvious it had been tagged before: https://github.com/django-dbbackup/django-dbbackup/releases/tag/4.0.0b0

Hi @Archmonger Yes Jazzband iis a good idea, I think a bit of maitenance and cleaning should be good before submit Dbbackup.

Hi @johnthagen Thank you for you time and attention, I give you the rights for the Github Organization and the the Pypi repo.

But like @Archmonger suggested, it could be a good thing to transfer it to Jazzband

Hi everyone, I’m sorry for my absence and my late reply.

I absolutely don’t have the time to maintain DBBackup but it would be a pleasure to pass the ownership to someone with more time and knowledge.

Who’s volunteer to maintain DBBackup ?

Please follow #415. Unfortunately we are still waiting for the original maintainers to give access to the ReadTheDocs site.

As a temporary workaround, you can install pip install via git git+https://github.com/django-dbbackup/django-dbbackup.git

ex pip install git+https://github.com/django-dbbackup/django-dbbackup.git

I just confirmed that john had not been invited to PyPI, so I’ve sent him an invite.

I am currently not a maintainer on the GitHub repo though so I’ll need @johnthagen to add me as one if I am to tag releases in the future.

I also agree Jazzband would be a very good long term plan.

Thanks @ZuluPro!

Let me know if you need any support on this!

I have enough time to do very basic maintenance (keep dbbackup working on latest Django / remove deprecation warnings / etc.) I’m currently doing the same for django-solo.

If you also want to grant ability to upload to PyPI my username there is: https://pypi.org/user/johnthagen/

If @jonathan-s is no longer maintaining this project, there may need to be a new community fork. There have been no commits for a year.