Skip to content

Cannot delete repositories #667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
yspreen opened this issue Apr 11, 2017 · 3 comments
Closed

Cannot delete repositories #667

yspreen opened this issue Apr 11, 2017 · 3 comments
Assignees

Comments

@yspreen
Copy link

yspreen commented Apr 11, 2017

This seems to be issue #586, but I could not find a fix.

From production.log:

Started DELETE "/repositories/104" for ${IP} at 2017-04-11 16:29:18 +0200
Processing by RepositoriesController#destroy as HTML
  Parameters: {"authenticity_token"=>"${token}", "id"=>"104"}
  Current user: ${user} (id=5)
Completed 500 Internal Server Error in 352ms (ActiveRecord: 327.5ms)

ActiveRecord::StatementInvalid (Mysql2::Error: Table 'redmine.repository_git_notifications' doesn't exist: SHOW FULL FIELDS FROM `repository_git_notifications`):
  app/controllers/repositories_controller.rb:109:in `destroy'
  plugins/redmine_git_hosting/lib/redmine_git_hosting/patches/repositories_controller_patch.rb:58:in `destroy_with_git_hosting'
  lib/redmine/sudo_mode.rb:63:in `sudo_mode'
@gituser
Copy link

gituser commented Apr 13, 2017

Try creating repository_git_notifications table:

CREATE TABLE `repository_git_notifications` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `repository_id` int(11) DEFAULT NULL,
  `include_list` text,
  `exclude_list` text,
  `prefix` varchar(255) DEFAULT NULL,
  `sender_address` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `index_repository_git_notifications_on_repository_id` (`repository_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

@yspreen
Copy link
Author

yspreen commented Apr 15, 2017

@gituser​: This is a viable workaround, thanks!

Shouldn't this be handled by the migration of the plugin? That went through without issues btw.

@n-rodriguez n-rodriguez self-assigned this Apr 18, 2017
@PowerKiKi
Copy link
Collaborator

As discussed in #732 (comment), issues related to Redmine < 4.0 or severely outdated issues are being closed to help clean up the issue tracker.

If this issue is still relevant to you and you are running Redmine >= 4.0, please open a new issue including all new relevant information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants