github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-14 11:56:41 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Release Candiate it published to latest tag on docker hub #9096

New Issue
Closed
opened 2025-11-02 08:29:09 -06:00 by GiteaMirror · 16 comments
GiteaMirror commented 2025-11-02 08:29:09 -06:00
Owner
Copy Link

Originally created by @MarcelCoding on GitHub (Jun 20, 2022).

Description

17.0+rc1 got published to gitea/gitea:latest. But the docs say that only stable releases are published to latest:
https://docs.gitea.io/en-us/install-with-docker/#basics

For a stable release you can use :latest, ...

Gitea Version

17.0+rc1

Originally created by @MarcelCoding on GitHub (Jun 20, 2022). ### Description `17.0+rc1` got published to `gitea/gitea:latest`. But the docs say that only stable releases are published to `latest`: https://docs.gitea.io/en-us/install-with-docker/#basics > For a stable release you can use `:latest`, ... ### Gitea Version 17.0+rc1
GiteaMirror added the type/bug label 2025-11-02 08:29:09 -06:00
GiteaMirror commented 2025-11-02 08:29:10 -06:00
Author
Owner
Copy Link

@MilesTEG1 commented on GitHub (Jun 21, 2022):

Same for me.

@MilesTEG1 commented on GitHub (Jun 21, 2022): Same for me.
GiteaMirror commented 2025-11-02 08:29:10 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Jun 21, 2022):

https://github.com/go-gitea/gitea/pull/20060#issuecomment-1160826650

was my fault, code did had in mind that latest = latest tag ...
and for me releasing (by git tag) rc1 as latest did not bring up read flags -> I'm sorry for that

hope it wont hit you that hard, and we (gitea maintainers...) do take action that next version rc wont do the same (would be v1-18-... then)

@6543 commented on GitHub (Jun 21, 2022): https://github.com/go-gitea/gitea/pull/20060#issuecomment-1160826650 was my fault, code did had in mind that latest = latest tag ... and for me releasing (by `git tag`) rc1 as latest did not bring up read flags -> I'm sorry for that hope it wont hit you that hard, and we (gitea maintainers...) do take action that next version rc wont do the same (would be v1-18-... then)
GiteaMirror commented 2025-11-02 08:29:10 -06:00
Author
Owner
Copy Link

@MarcelCoding commented on GitHub (Jun 21, 2022):

All good, my instance is still running. And even just in case I have a backup. 😉

@MarcelCoding commented on GitHub (Jun 21, 2022): All good, my instance is still running. And even just in case I have a backup. 😉
GiteaMirror commented 2025-11-02 08:29:10 -06:00
Author
Owner
Copy Link

@MilesTEG1 commented on GitHub (Jun 21, 2022):

Me too, Nothing to report, everything seems to be functional (with my utilisation). And I have too a backup of my files every night with a homemade script.

@MilesTEG1 commented on GitHub (Jun 21, 2022): Me too, Nothing to report, everything seems to be functional (with my utilisation). And I have too a backup of my files every night with a homemade script.
GiteaMirror commented 2025-11-02 08:29:12 -06:00
Author
Owner
Copy Link

@Snck3rs commented on GitHub (Jun 22, 2022):

luckily the same here - no problems occured. But it would be nice, if the latest - tag would stay stable :)

@Snck3rs commented on GitHub (Jun 22, 2022): luckily the same here - no problems occured. But it would be nice, if the latest - tag would stay stable :)
GiteaMirror commented 2025-11-02 08:29:12 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jun 22, 2022):

Yeah, we are trying to fix the release process bug.

@lunny commented on GitHub (Jun 22, 2022): Yeah, we are trying to fix the release process bug.
GiteaMirror commented 2025-11-02 08:29:13 -06:00
Author
Owner
Copy Link

@xplreitr commented on GitHub (Jul 2, 2022):

I think I may have run into a problem with this. When my conainter updated, it just cycled through the following process:

gitea-server.1. | Server listening on 0.0.0.0 port 22.
gitea-server.1. | 2022/07/01 00:43:19 cmd/web.go:106:runWeb() [I] Starting Gitea on PID: 19
gitea-server.1. | 2022/07/01 00:43:19 ...s/setting/setting.go:594:deprecatedSetting() [E] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be removed in v1.18.0
gitea-server.1. | 2022/07/01 00:43:19 cmd/web.go:157:runWeb() [I] Global init
gitea-server.1. | 2022/07/01 00:43:19 ...s/setting/setting.go:594:deprecatedSetting() [E] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be removed in v1.18.0
gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:106:GlobalInitInstalled() [I] Git Version: 2.36.1, Wire Protocol Version 2 Enabled (home: /data/git/repositories)
gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:109:GlobalInitInstalled() [I] AppPath: /usr/local/bin/gitea
gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:110:GlobalInitInstalled() [I] AppWorkPath: /app/gitea
gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:111:GlobalInitInstalled() [I] Custom path: /data/gitea
gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:112:GlobalInitInstalled() [I] Log path: /data/gitea/log
gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:113:GlobalInitInstalled() [I] Configuration file: /data/gitea/conf/app.ini
gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:114:GlobalInitInstalled() [I] Run Mode: Prod
gitea-server.1. | 2022/07/01 00:43:19 ...dules/setting/log.go:288:newLogService() [I] Gitea v1.17.0+rc1 built with GNU Make 4.3, go1.18.3 : bindata, timetzdata, sqlite, sqlite_unlock_notify
gitea-server.1. | 2022/07/01 00:43:19 ...dules/setting/log.go:335:newLogService() [I] Gitea Log Mode: Console(Console:debug)
gitea-server.1. | 2022/07/01 00:43:19 ...dules/setting/log.go:249:generateNamedLogger() [I] Router Log: Console(console:debug)
gitea-server.1. | 2022/07/01 00:43:19 ...dules/setting/log.go:249:generateNamedLogger() [I] Xorm Log: Console(console:debug)
gitea-server.1. | 2022/07/01 00:43:19 ...les/setting/cache.go:76:newCacheService() [I] Cache Service Enabled
gitea-server.1. | 2022/07/01 00:43:19 ...les/setting/cache.go:91:newCacheService() [I] Last Commit Cache Service Enabled
gitea-server.1. | 2022/07/01 00:43:19 ...s/setting/session.go:73:newSessionService() [I] Session Service Enabled
gitea-server.1. | 2022/07/01 00:43:19 ...ules/setting/cors.go:36:newCORSService() [I] CORS Service Enabled
gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:176:initAttachments() [I] Initialising Attachment storage with type:
gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/attachments
gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:170:initAvatars() [I] Initialising Avatar storage with type:
gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/avatars
gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:188:initRepoAvatars() [I] Initialising Repository Avatar storage with type:
gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/repo-avatars
gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:182:initLFS() [I] Initialising LFS storage with type:
gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/git/lfs
gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:194:initRepoArchives() [I] Initialising Repository Archive storage with type:
gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/repo-archive
gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:200:initPackages() [I] Initialising Packages storage with type:
gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/packages
gitea-server.1. | 2022/07/01 00:43:19 ...ueue_disk_channel.go:159:Run() [D] [62be9787-20] PersistableChannelQueue: notification-service Starting
gitea-server.1. | 2022/07/01 00:43:19 ...ueue_disk_channel.go:194:Run() [D] [62be9787-20] PersistableChannelQueue: notification-service Skipping running the empty level queue
gitea-server.1. | 2022/07/01 00:43:19 ...ue/queue_bytefifo.go:335:Shutdown() [D] [62be9787-20] level: notification-service-level Shutdown
gitea-server.1. | 2022/07/01 00:43:19 ...ueue_disk_channel.go:188:Run() [D] [62be9787-22] PersistableChannelUniqueQueue: repo-archive Starting
gitea-server.1. | 2022/07/01 00:43:19 ...ueue_disk_channel.go:223:Run() [D] [62be9787-22] PersistableChannelUniqueQueue: repo-archive Skipping running the empty level queue
gitea-server.1. | 2022/07/01 00:43:19 ...ue/queue_bytefifo.go:335:Shutdown() [D] [62be9787-22] unique-level: repo-archive-level Shutdown
gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:132:GlobalInitInstalled() [I] SQLite3 support is enabled
gitea-server.1. | 2022/07/01 00:43:19 routers/common/db.go:20:InitDBEngine() [I] Beginning ORM engine initialization.
gitea-server.1. | 2022/07/01 00:43:19 routers/common/db.go:27:InitDBEngine() [I] ORM engine initialization attempt #1/10...
gitea-server.1. | 2022/07/01 00:43:19 cmd/web.go:160:runWeb() [I] PING DATABASE postgres
gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:137:GlobalInitInstalled() [W] Table session has column created_unix but struct has not related field
gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:137:GlobalInitInstalled() [W] Table email_address Column lower_email db nullable is true, struct nullable is false
gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:137:GlobalInitInstalled() [W] Table user Column max_repo_creation db default is '-1', struct default is -1
gitea-server.1. | 2022/07/01 00:43:20 routers/init.go:137:GlobalInitInstalled() [W] Table project column board_type db type is INTEGER, struct type is BIGINT
gitea-server.1. | 2022/07/01 00:43:20 routers/init.go:137:GlobalInitInstalled() [W] Table project column type db type is INTEGER, struct type is BIGINT
gitea-server.1. | 2022/07/01 00:43:20 routers/init.go:138:GlobalInitInstalled() [I] ORM engine initialization successful!
gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: update_mirrors
gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: repo_health_check
gitea-server.1. | 2022/07/01 00:43:20 ...ueue_disk_channel.go:159:Run() [D] [62be9788] PersistableChannelQueue: push_update Starting
gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: check_repo_stats
gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: archive_cleanup
gitea-server.1. | 2022/07/01 00:43:20 ...ueue_disk_channel.go:194:Run() [D] [62be9788] PersistableChannelQueue: push_update Skipping running the empty level queue
gitea-server.1. | 2022/07/01 00:43:20 ...ue/queue_bytefifo.go:335:Shutdown() [D] [62be9788] level: push_update-level Shutdown
gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: sync_external_users
gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: deleted_branches_cleanup
gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: update_migration_poster_id
gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: cleanup_hook_task_table
gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: cleanup_packages
gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:200:RegisterTaskFatal() [F] [62be9788-3] Unable to register cron task cleanup_packages Error: translation is missing for task "cleanup_packages", please add translation for "admin.dashboard.cleanup_packages"
gitea-server.1. | Received signal 15; terminating.

I came across some other posts mentioning signal 15 that were resolved with:

  • Deleted /data/queues
  • Disabling the SSH server with DISABLE_SSH=true

But neither of these suggestions resolved my issue.

I never found any issues regarding the line Unable to register cron task cleanup_packages Error: translation is missing for task "cleanup_packages", please add translation for "admin.dashboard.cleanup_packages", But I did find some settings mentioning the setting cron.cleanup_packages and I tried to disable it by putting the following in my app.ini:

[cron.cleanup_packages]
ENABLED = false
RUN_AT_START = false
NOTICE_ON_SUCCESS = false

I also tried to step back to v1.16.8, but ran into the following:

Your database (migration version: 218) is for a newer Gitea, you can not use the newer database for this old Gitea release (211).

I found an issue dealing with downgrading databases using 'UPDATE version SET version=211 WHERE id=1;', but I wasn't sure it was appropriate for this situation

Do you think this thread is the right place to address this option? Or should I start a new issue?

@xplreitr commented on GitHub (Jul 2, 2022): I think I may have run into a problem with this. When my conainter updated, it just cycled through the following process: ``` gitea-server.1. | Server listening on 0.0.0.0 port 22. gitea-server.1. | 2022/07/01 00:43:19 cmd/web.go:106:runWeb() [I] Starting Gitea on PID: 19 gitea-server.1. | 2022/07/01 00:43:19 ...s/setting/setting.go:594:deprecatedSetting() [E] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be removed in v1.18.0 gitea-server.1. | 2022/07/01 00:43:19 cmd/web.go:157:runWeb() [I] Global init gitea-server.1. | 2022/07/01 00:43:19 ...s/setting/setting.go:594:deprecatedSetting() [E] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be removed in v1.18.0 gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:106:GlobalInitInstalled() [I] Git Version: 2.36.1, Wire Protocol Version 2 Enabled (home: /data/git/repositories) gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:109:GlobalInitInstalled() [I] AppPath: /usr/local/bin/gitea gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:110:GlobalInitInstalled() [I] AppWorkPath: /app/gitea gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:111:GlobalInitInstalled() [I] Custom path: /data/gitea gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:112:GlobalInitInstalled() [I] Log path: /data/gitea/log gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:113:GlobalInitInstalled() [I] Configuration file: /data/gitea/conf/app.ini gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:114:GlobalInitInstalled() [I] Run Mode: Prod gitea-server.1. | 2022/07/01 00:43:19 ...dules/setting/log.go:288:newLogService() [I] Gitea v1.17.0+rc1 built with GNU Make 4.3, go1.18.3 : bindata, timetzdata, sqlite, sqlite_unlock_notify gitea-server.1. | 2022/07/01 00:43:19 ...dules/setting/log.go:335:newLogService() [I] Gitea Log Mode: Console(Console:debug) gitea-server.1. | 2022/07/01 00:43:19 ...dules/setting/log.go:249:generateNamedLogger() [I] Router Log: Console(console:debug) gitea-server.1. | 2022/07/01 00:43:19 ...dules/setting/log.go:249:generateNamedLogger() [I] Xorm Log: Console(console:debug) gitea-server.1. | 2022/07/01 00:43:19 ...les/setting/cache.go:76:newCacheService() [I] Cache Service Enabled gitea-server.1. | 2022/07/01 00:43:19 ...les/setting/cache.go:91:newCacheService() [I] Last Commit Cache Service Enabled gitea-server.1. | 2022/07/01 00:43:19 ...s/setting/session.go:73:newSessionService() [I] Session Service Enabled gitea-server.1. | 2022/07/01 00:43:19 ...ules/setting/cors.go:36:newCORSService() [I] CORS Service Enabled gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:176:initAttachments() [I] Initialising Attachment storage with type: gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/attachments gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:170:initAvatars() [I] Initialising Avatar storage with type: gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/avatars gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:188:initRepoAvatars() [I] Initialising Repository Avatar storage with type: gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/repo-avatars gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:182:initLFS() [I] Initialising LFS storage with type: gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/git/lfs gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:194:initRepoArchives() [I] Initialising Repository Archive storage with type: gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/repo-archive gitea-server.1. | 2022/07/01 00:43:19 ...s/storage/storage.go:200:initPackages() [I] Initialising Packages storage with type: gitea-server.1. | 2022/07/01 00:43:19 ...les/storage/local.go:46:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/packages gitea-server.1. | 2022/07/01 00:43:19 ...ueue_disk_channel.go:159:Run() [D] [62be9787-20] PersistableChannelQueue: notification-service Starting gitea-server.1. | 2022/07/01 00:43:19 ...ueue_disk_channel.go:194:Run() [D] [62be9787-20] PersistableChannelQueue: notification-service Skipping running the empty level queue gitea-server.1. | 2022/07/01 00:43:19 ...ue/queue_bytefifo.go:335:Shutdown() [D] [62be9787-20] level: notification-service-level Shutdown gitea-server.1. | 2022/07/01 00:43:19 ...ueue_disk_channel.go:188:Run() [D] [62be9787-22] PersistableChannelUniqueQueue: repo-archive Starting gitea-server.1. | 2022/07/01 00:43:19 ...ueue_disk_channel.go:223:Run() [D] [62be9787-22] PersistableChannelUniqueQueue: repo-archive Skipping running the empty level queue gitea-server.1. | 2022/07/01 00:43:19 ...ue/queue_bytefifo.go:335:Shutdown() [D] [62be9787-22] unique-level: repo-archive-level Shutdown gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:132:GlobalInitInstalled() [I] SQLite3 support is enabled gitea-server.1. | 2022/07/01 00:43:19 routers/common/db.go:20:InitDBEngine() [I] Beginning ORM engine initialization. gitea-server.1. | 2022/07/01 00:43:19 routers/common/db.go:27:InitDBEngine() [I] ORM engine initialization attempt #1/10... gitea-server.1. | 2022/07/01 00:43:19 cmd/web.go:160:runWeb() [I] PING DATABASE postgres gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:137:GlobalInitInstalled() [W] Table session has column created_unix but struct has not related field gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:137:GlobalInitInstalled() [W] Table email_address Column lower_email db nullable is true, struct nullable is false gitea-server.1. | 2022/07/01 00:43:19 routers/init.go:137:GlobalInitInstalled() [W] Table user Column max_repo_creation db default is '-1', struct default is -1 gitea-server.1. | 2022/07/01 00:43:20 routers/init.go:137:GlobalInitInstalled() [W] Table project column board_type db type is INTEGER, struct type is BIGINT gitea-server.1. | 2022/07/01 00:43:20 routers/init.go:137:GlobalInitInstalled() [W] Table project column type db type is INTEGER, struct type is BIGINT gitea-server.1. | 2022/07/01 00:43:20 routers/init.go:138:GlobalInitInstalled() [I] ORM engine initialization successful! gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: update_mirrors gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: repo_health_check gitea-server.1. | 2022/07/01 00:43:20 ...ueue_disk_channel.go:159:Run() [D] [62be9788] PersistableChannelQueue: push_update Starting gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: check_repo_stats gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: archive_cleanup gitea-server.1. | 2022/07/01 00:43:20 ...ueue_disk_channel.go:194:Run() [D] [62be9788] PersistableChannelQueue: push_update Skipping running the empty level queue gitea-server.1. | 2022/07/01 00:43:20 ...ue/queue_bytefifo.go:335:Shutdown() [D] [62be9788] level: push_update-level Shutdown gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: sync_external_users gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: deleted_branches_cleanup gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: update_migration_poster_id gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: cleanup_hook_task_table gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:148:RegisterTask() [D] [62be9788-3] Registering task: cleanup_packages gitea-server.1. | 2022/07/01 00:43:20 ...rvices/cron/tasks.go:200:RegisterTaskFatal() [F] [62be9788-3] Unable to register cron task cleanup_packages Error: translation is missing for task "cleanup_packages", please add translation for "admin.dashboard.cleanup_packages" gitea-server.1. | Received signal 15; terminating. ``` I came across some other posts mentioning signal 15 that were resolved with: * Deleted /data/queues * Disabling the SSH server with DISABLE_SSH=true But neither of these suggestions resolved my issue. I never found any issues regarding the line `Unable to register cron task cleanup_packages Error: translation is missing for task "cleanup_packages", please add translation for "admin.dashboard.cleanup_packages"`, But I did find some settings mentioning the setting `cron.cleanup_packages` and I tried to disable it by putting the following in my app.ini: ``` [cron.cleanup_packages] ENABLED = false RUN_AT_START = false NOTICE_ON_SUCCESS = false ``` I also tried to step back to v1.16.8, but ran into the following: ``` Your database (migration version: 218) is for a newer Gitea, you can not use the newer database for this old Gitea release (211). ``` I found an [issue](https://github.com/go-gitea/gitea/issues/13451) dealing with downgrading databases using 'UPDATE version SET version=211 WHERE id=1;', but I wasn't sure it was appropriate for this situation Do you think this thread is the right place to address this option? Or should I start a new issue?
GiteaMirror commented 2025-11-02 08:29:13 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Jul 2, 2022):

@xplreitr thats a new issue ... - please move it into one

@6543 commented on GitHub (Jul 2, 2022): @xplreitr thats a new issue ... - please move it into one
GiteaMirror commented 2025-11-02 08:29:13 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jul 3, 2022):

Just update your translation files to add admin.dashboard.cleanup_package should be OK.

@lunny commented on GitHub (Jul 3, 2022): Just update your translation files to add admin.dashboard.cleanup_package should be OK.
GiteaMirror commented 2025-11-02 08:29:13 -06:00
Author
Owner
Copy Link

@MarcelCoding commented on GitHub (Aug 8, 2022):

I think this is fixed, can this be closed? At least 17 is now released and latest is stable again.

@MarcelCoding commented on GitHub (Aug 8, 2022): I think this is fixed, can this be closed? At least 17 is now released and latest is stable again.
GiteaMirror commented 2025-11-02 08:29:14 -06:00
Author
Owner
Copy Link

@julmb commented on GitHub (Oct 26, 2022):

This happened to me again today with latest on the docker hub currently pointing to the same image as 1.18.0-rc0 (167f91cbf8f2 for amd64).

What should I do? Keep running 1.18.0-rc0 for now? Downgrade to 1.17.3 even though the gitea 1.18.0-rc0 has already touched the files and database? Or restore from backup?

@julmb commented on GitHub (Oct 26, 2022): This happened to me again today with `latest` on the docker hub currently pointing to the same image as `1.18.0-rc0` (167f91cbf8f2 for amd64). What should I do? Keep running 1.18.0-rc0 for now? Downgrade to 1.17.3 even though the gitea 1.18.0-rc0 has already touched the files and database? Or restore from backup?
GiteaMirror commented 2025-11-02 08:29:14 -06:00
Author
Owner
Copy Link

@MarcelCoding commented on GitHub (Oct 26, 2022):

I would leave it on the rc, If you have anything that is broken, use a database and file backup and downgrade. I now use static versions and manage my docker-compose field using git. I also use renovate to get notified (via pr's) when updates are available. This way this can't happen anymore and you are always up to date without constantly checking for the latest version: https://git.m4rc3l.de/marcel/stack/src/branch/main/git/docker-compose.yaml#L18

@MarcelCoding commented on GitHub (Oct 26, 2022): I would leave it on the rc, If you have anything that is broken, use a database and file backup and downgrade. I now use static versions and manage my docker-compose field using git. I also use renovate to get notified (via pr's) when updates are available. This way this can't happen anymore and you are always up to date without constantly checking for the latest version: https://git.m4rc3l.de/marcel/stack/src/branch/main/git/docker-compose.yaml#L18
GiteaMirror commented 2025-11-02 08:29:14 -06:00
Author
Owner
Copy Link

@julmb commented on GitHub (Oct 26, 2022):

I would leave it on the rc, If you have anything that is broken, use a database and file backup and downgrade. I now use static versions and manage my docker-compose field using git. I also use renovate to get notified (via pr's) when updates are available. This way this can't happen anymore and you are always up to date without constantly checking for the latest version: https://git.m4rc3l.de/marcel/stack/src/branch/main/git/docker-compose.yaml#L18

Maybe I should do that too. Although I get the feeling that the Gitea developers actually do not want the latest tag to point to a release candidate and that this was just an accident.

@julmb commented on GitHub (Oct 26, 2022): > I would leave it on the rc, If you have anything that is broken, use a database and file backup and downgrade. I now use static versions and manage my docker-compose field using git. I also use renovate to get notified (via pr's) when updates are available. This way this can't happen anymore and you are always up to date without constantly checking for the latest version: https://git.m4rc3l.de/marcel/stack/src/branch/main/git/docker-compose.yaml#L18 Maybe I should do that too. Although I get the feeling that the Gitea developers actually do not want the `latest` tag to point to a release candidate and that this was just an accident.
GiteaMirror commented 2025-11-02 08:29:14 -06:00
Author
Owner
Copy Link

@MarcelCoding commented on GitHub (Oct 26, 2022):

Your right, that's not indented: https://github.com/go-gitea/gitea/issues/20058#issuecomment-1161665151

@MarcelCoding commented on GitHub (Oct 26, 2022): Your right, that's not indented: https://github.com/go-gitea/gitea/issues/20058#issuecomment-1161665151
GiteaMirror commented 2025-11-02 08:29:15 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Oct 26, 2022):

well last time (v1.17.0 it was a mistake) now it's definitely a bug as it should be fixed?

@6543 commented on GitHub (Oct 26, 2022): well last time (v1.17.0 it was a mistake) now it's definitely a bug as it should be fixed?
GiteaMirror commented 2025-11-02 08:29:15 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Oct 26, 2022):

please one a new issue!!! (& link to here)

@6543 commented on GitHub (Oct 26, 2022): please one a new issue!!! (& link to here)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9096
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?