unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: SWH and lookup (bug?)
Date: Tue, 26 Oct 2021 17:35:38 +0200	[thread overview]
Message-ID: <86bl3b94tx.fsf@gmail.com> (raw)

Hi,

Well, I do not know if it is a bug.  But I note a weird behaviour.
Between 26/10/2021, 16:53:13 and 26/10/2021, 16:59:18, I have scheduled
“missing” packages.  And basically, the status reports “succeeded” (dig
to pages there [1]).  Therefore, I am sure they are in. :-)

Now, if I run “guix lint -c archival” on these same packages, it will
reschedule them again.  Therefore, something is not working as expected,
I guess.


For instance, try with the package ’sway’ (search bar [1]:
https://github.com/swaywm/sway).  SWH says the status for archiving
succeeded.  Even, it is archived for instance there [2].

Then if you give a look at the visit webpage, it says that the
repository had been visited several times on 2021 [3].

1: <https://archive.softwareheritage.org/save/#requests>
2: <https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://github.com/swaywm/sway&release=1.5.1>
3: <https://archive.softwareheritage.org/browse/origin/visits/?origin_url=https://github.com/swaywm/sway>


However, I get this:

--8<---------------cut here---------------start------------->8---
$ guix lint -c archival sway                    
gnu/packages/wm.scm:1527:5: sway@1.5.1: scheduled Software Heritage archival
--8<---------------cut here---------------end--------------->8---

Sway is updated by 7fc378aa7bc1fff5d87ed993205a1e825a7872d9 pushed
on CommitDate: Fri Nov 20 00:10:11 2020 +0100.  And git-blame says that
all the commits modifying the ’source’ field are older.

On the top of that, the Preservation of Guix database pog.db [4] does
not list it as missing; IIUC.

4: <https://ngyro.com/pog-reports/2021-10-22/pog.db>

However, if I get it correctly, it uses another entry point than the one
defined by (guix swh).  Right?


Here a short list of packages providing similar behaviour; IIRC.

--8<---------------cut here---------------start------------->8---
open-zwave
ao
slop
wxwidgets
wxwidgets-gtk2
wlroots
sway
monolith
tidy-html
wabt
rss-bridge
libsass
glslang
spirv-tools
protonvpn-cli
remmina
vlang
ganeti-instance-debootstrap
skopeo
vim-full
xxd
vim
neovim
--8<---------------cut here---------------end--------------->8---

Basically, what triggers ’swh-download’ is somehow using
’lookup-revision’ or ’lookup-origin-revision’, which are the same which
triggers a save (check-archival).


Cheers,
simon


             reply	other threads:[~2021-10-26 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 15:35 zimoun [this message]
2021-10-29 14:57 ` SWH and lookup (bug?) Ludovic Courtès
2021-11-02 11:23   ` zimoun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86bl3b94tx.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).