Hello,

I had noticed in December of 2023 that forge was basically incapable of pulling anything (from github that time).

I had solved the issue by updating it to a newer upstream snapshot.

Now, for various reasons, this update has not been pushed to the archive yet, but it should be soon (the relevant commits have now been pushed to salsa).

I would be curious whether you can still reproduce the problem after updating to 0.3.2+git20231227.1.299bbaa-1, once it gets uploaded.

Sorry for the inconvenience.

Best,

Aymeric, of the debian-emacsen team

Le vendredi 29 mars 2024 à 18:12, Daniel Kahn Gillmor <d...@fifthhorseman.net> a écrit :

[[PGP Signed Part:Undecided]]
Package: elpa-magit-forge
Version: 0.3.2-1
Severity: normal
X-Debbugs-Cc: Daniel Kahn Gillmor <d...@fifthhorseman.net>

I'm trying to do some work on impass, which is publicly hosted on
salsa.debian.org.

From emacs, i'm using forge in my working copy of the impass git repo,
and i've configured ~/.gitconfig to have:

```
[gitlab "salsa.debian.org/api/v4"]
        user = dkg
```

In my local working copy's .git/config i have:

```
[remote "salsa"]
        url = https://salsa.debian.org/debian/impass.git
        fetch = +refs/heads/*:refs/remotes/salsa/*
        pushurl = g...@salsa.debian.org:debian/impass.git
        fetch = +refs/merge-requests/*/head:refs/pullreqs/*
[forge]
        remote = salsa
```

However, when i try to do M-x forge-pull, i end up with this error
message:

```
Pulling debian/impass...
Pulling debian/impass issues...
error in process filter: ghub--errorback: HTTP Error: 400, "Bad Request", "/api/v4/projects/debian%2Fimpass/issues?per_page=100&order_by=updated_at&updated_after=false", ((error . "updated_after is invalid")) error in process filter: HTTP Error: 400, "Bad Request", "/api/v4/projects/debian%2Fimpass/issues?per_page=100&order_by=updated_at&updated_after=false", ((error . "updated_after is invalid"))
```

If this is a bug on the salsa.debian.org side, feel free to reassign to
the appropriate metapackage.

        --dkg

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages elpa-magit-forge depends on:
ii  dh-elpa-helper       2.0.17
ii  elpa-closql          1.2.1-3
ii  elpa-dash            2.19.1+git20220608.1.0ac1ecf+dfsg-1
ii  elpa-emacsql-sqlite  3.1.1+git20230417.6401226+ds-1
ii  elpa-ghub            3.6.0-4
ii  elpa-let-alist       1.0.6-2
ii  elpa-magit           3.3.0-3
ii  elpa-markdown-mode   2.6-1
ii  elpa-yaml            0.5.5-1
ii  emacsen-common       3.0.5

Versions of packages elpa-magit-forge recommends:
ii  emacs               1:29.2+1-2
ii  emacs-pgtk [emacs]  1:29.2+1-2

elpa-magit-forge suggests no packages.

-- no debconf information

[[End of PGP Signed Part]]

Reply via email to