question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

rebase-helper propose-update failed with traceback on git push --force

See original GitHub issue

I have tried to update rebase-helper by packit but it failed with traceback. .packit.yml configuration file is here: https://github.com/rebase-helper/rebase-helper/blob/master/.packit.yaml

$ packit propose-update
Checking out upstream version 0.16.2
using "master" dist-git branch
syncing ./.packit.yaml
syncing ./rebase-helper.spec
INFO: Running 'anitya' versioneer
INFO: Downloading file from URL https://github.com/rebase-helper/rebase-helper/archive/0.16.2/rebase-helper-0.16.2.tar.gz
    [       <=>                    ]     1.80M   in 00:00:01
downloaded archive: /tmp/tmpeqbb9vh6/rebase-helper-0.16.2.tar.gz
uploading to the lookaside cache
ERROR    Cmd('git') failed due to: exit code(128)
  cmdline: git push --force --porcelain fork 0.16.2-master-update
  stderr: 'fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.'
Unexpected exception occurred,
please fill an issue here:
https://github.com/packit-service/packit/issues

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
TomasTomecekcommented, Mar 14, 2019

Cool, so we should just catch the giterror exc and reraise as packit exc.

1reaction
lachmanfrantisekcommented, Mar 14, 2019

One TODO I have in mind: how about changing the top-most try/catch to: if packitexc is raised, just tell that there was an error during execution and if generic exc is being caught, we should inform user about reporting the issue.

If I got your idea, this is the current state: https://github.com/packit-service/packit/blob/master/packit/cli/utils.py#L30

Read more comments on GitHub >

github_iconTop Results From Across the Web

Why is `git push --force-with-lease` failing with "rejected ...
In this case it turned out that the problem was that the remote branch had been deleted, but there was still a copy...
Read more >
git-push Documentation - Git
git -push - Update remote refs along with associated objects ... This flag forces progress status even if the standard error stream is...
Read more >
Git Push Crashes from IDE [124680708] - Issue Tracker - Google
Commit works fine, its the push that fail.s Change any file from a bitbucket git ... then push dialog appears, and fails to...
Read more >
Introduction to Git rebase and force-push - GitLab Docs
This guide helps you to get started with rebasing, force-pushing, and fixing merge conflicts locally. Before diving into this document, make sure you...
Read more >
force considered harmful; understanding git's -force-with-lease
Git's push --force is destructive because it unconditionally overwrites the remote repository with whatever you have locally, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found