Skip to content
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

Debian Upgrade fail #15030

Open
2 tasks done
sefaarslan41 opened this issue Jul 5, 2024 · 3 comments
Open
2 tasks done

Debian Upgrade fail #15030

sefaarslan41 opened this issue Jul 5, 2024 · 3 comments

Comments

@sefaarslan41
Copy link

Debug mode

Describe the bug

1 - I am using snipe it installed on Debian, which is the turnkey version. When I try to update with the sudo -u www-data php upgrade.php command, it gives an error as follows.

STEP 8: Updating composer dependencies:
(This may take a moment.)


-- Running the app in production mode.
-- We couldn't find a local composer.phar. No worries, trying globally.
Since you are running composer globally, we won't try to update it for you.
If you run into issues with this step, try running composer self-update
before running this updater again

Installing dependencies from lock file
Verifying lock file contents can be installed on current platform.
Package operations: 20 installs, 113 updates, 20 removals

2- In composer update conditions, I get the following error:
Failed to execute git show-ref --head -d

fatal: detected dubious ownership in repository at '/var/www/snipe-it/vendor/symfony/polyfill-php73'
To add an exception for this directory, call:

git config --global --add safe.directory /var/www/snipe-it/vendor/symfony/polyfill-php73

3- After receiving this error, I get a 500 SERVER ERROR error and I cannot log in again.

Reproduction steps

1.sudo -u www-data php upgrade.php

Expected behavior

I want to update the version. If I cannot update it, I want to be able to access the site again.

Screenshots

1
2
3
4

Snipe-IT Version

6

Operating System

debian

Web Server

apache

PHP Version

8.1.29

Operating System

No response

Browser

No response

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

Copy link

welcome bot commented Jul 5, 2024

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

@uberbrady
Copy link
Collaborator

composer --version should give you some interesting output - weird that the self-update option isn't in there, but if Composer is installed as a Debian package, I could see why they might omit that.

As for the part where github won't let you download stuff from it, we do see this every now and then. You can try what it recommends - the _public_ token should definitely be enough. Once you paste that in to the terminal, everything should continue normally.

I am seeing a 'modified' status on your composer.lock file - which is strange, but hopefully shouldn't cause any problems.

If you can give a couple of those ideas a shot, maybe you'll get a little bit farther down the path?

@MajorOli
Copy link

MajorOli commented Jul 21, 2024

Same Problem here with composer install --no-dev --prefer-source command
So, when you use only composer install --no-dev also without --prefer-source the composer update works again

In my case

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

3 participants