1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL

  • Package uploads silently discarded: how to investigate?

    From Ben Finney@21:1/5 to All on Mon Jun 27 01:10:01 2022
    Howdy all,

    For many weeks, my package uploads have been silently discarded. I have
    some guesses as to why but I can't find any concrete report saying so.

    Typically I'll receive an email message to my maintainer email address
    saying the package is being processed, and later a message saying it's succeeded or failed.

    By “silently discarded”, I mean that an upload of a package – whether source package or binary package, and whether using ‘dput’ or FTP
    commands directly – succeeds, then soon afterward the files no longer
    appear in the ‘/pub/UploadQueue/’ directory; then there is no further communication from the Debian archive infrastructure.

    My guess is that this is something to do with an update to the signing
    GnuPG key expiry date. I can get into that in a different thread if
    needed. The trouble is, I can only guess, because there are no messages
    from anything in the Debian archive telling me what went wrong.

    In this thread I want to discover: How can I find out what's happening
    and why the Debian archive is no longer sending me any email messages
    about my package uploads?

    --
    \ “The enjoyment of one's tools is an essential ingredient of |
    `\ successful work.” —Donald Knuth, _The Art of Computer | _o__) Programming_ |
    Ben Finney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to Ben Finney on Mon Jun 27 03:10:01 2022
    Ben Finney <bignose@debian.org> writes:

    My guess is that this is something to do with an update to the signing
    GnuPG key expiry date. I can get into that in a different thread if
    needed. The trouble is, I can only guess, because there are no messages
    from anything in the Debian archive telling me what went wrong.

    My recollection is that if the signature on the upload is invalid, we intentionally delete the upload with no notice (because we have no
    confirmed knowledge of who to notify). It's possible that my information
    is dated, though....

    --
    Russ Allbery (rra@debian.org) <https://www.eyrie.org/~eagle/>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Scott Kitterman@21:1/5 to Russ Allbery on Mon Jun 27 03:20:01 2022
    On June 27, 2022 1:06:10 AM UTC, Russ Allbery <rra@debian.org> wrote:
    Ben Finney <bignose@debian.org> writes:

    My guess is that this is something to do with an update to the signing
    GnuPG key expiry date. I can get into that in a different thread if
    needed. The trouble is, I can only guess, because there are no messages
    from anything in the Debian archive telling me what went wrong.

    My recollection is that if the signature on the upload is invalid, we >intentionally delete the upload with no notice (because we have no
    confirmed knowledge of who to notify). It's possible that my information
    is dated, though....

    That's correct.

    Scott K

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ben Finney@21:1/5 to Russ Allbery on Mon Jun 27 07:40:01 2022
    Russ Allbery <rra@debian.org> writes:

    Ben Finney <bignose@debian.org> writes:

    The trouble is, I can only guess, because there are no messages from anything in the Debian archive telling me what went wrong.

    My recollection is that if the signature on the upload is invalid, we intentionally delete the upload with no notice (because we have no
    confirmed knowledge of who to notify).

    So, the question remains: How can I, the person responsible for
    uploading this to the queue, find out (not guess based on absence of any message) what the error was that caused the submission to fail?

    --
    \ “Our urge to trust our senses overpowers what our measuring |
    `\ devices tell us about the actual nature of reality.” —Ann | _o__) Druyan, _Cosmos_, 2014 |
    Ben Finney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rahmatullin@21:1/5 to Ben Finney on Mon Jun 27 07:40:01 2022
    On Mon, Jun 27, 2022 at 09:02:30AM +1000, Ben Finney wrote:
    In this thread I want to discover: How can I find out what's happening
    and why the Debian archive is no longer sending me any email messages
    about my package uploads?
    You should check usper.debian.org:/srv/upload.debian.org/queued/run/log

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmK5QcgtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh sC4P/ArCWKpD2D7+9leBgH8GFrvDNlRy1o9bwx7DA/z9b7hnSPDs83ImVz+lfMwk 1d7PdlMyvYoq/+gLJiHbbhaDh92JeixRQ32rvC9OSM1gCrpEikncqngPeUNsddem 6pTJtOzmyz6WXkYwNCq1JYG+hddOIgWlQ7O+K34AN0pSbUV0yxgv1lpCuKODwgIe Zx5JmcUYFO/2AIeS04hGR9MZjOPbJp85aK9APEf71Nxw8/p4lOlI3vekY5TO5dyh anhqsvpiEVoStQxkSgIc2kr1r7Xu25mpHtul44Gw0vCR21yqCxeefhx3rOdU374P M3vuZX+2Kb0yIpFMvCACQkjtIB+8LJjGLJWsqtha6Q6B6L7qdFiRt3o8/nGOXMXq oG+CC8McSbMM/0sAWA5rLU8F/1Ejl8h7ERIMMUsosp7OsWeuyY8FYbeoGapT6Zk7 rn2g3+Gb4Tbz2WqR/Sj3xZAOEX9rRSaqA802aHWRvSN9sfYmVfaEoVr5u1nyA1Rs gWEhRHUMrsO+tOdSUpYcZFWmlwc7lk33Z4gWr5QAut3fneoTtmzjDZnX4ZOS+J7H AVfYOltbVKuqw+q34zEuoMAM/8tRmvPXtX9NUPX2lqkj+yokzXBfs/W2eX+diqdC XQTBwHwK7slTqwrRZnbxme8tCdu21evMndxjQHBZjC7iNcDE
    =VINS
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?IOhannes_m_zm=c3=b6lnig_=@21:1/5 to Scott Kitterman on Mon Jun 27 09:30:01 2022
    On 6/27/22 03:08, Scott Kitterman wrote:


    On June 27, 2022 1:06:10 AM UTC, Russ Allbery <rra@debian.org> wrote:
    Ben Finney <bignose@debian.org> writes:

    My guess is that this is something to do with an update to the signing
    GnuPG key expiry date. I can get into that in a different thread if
    needed. The trouble is, I can only guess, because there are no messages
    from anything in the Debian archive telling me what went wrong.

    My recollection is that if the signature on the upload is invalid, we
    intentionally delete the upload with no notice (because we have no
    confirmed knowledge of who to notify). It's possible that my information
    is dated, though....

    That's correct.


    as i've wondered myself about this in the past (not for some time
    though, since i no longer update my keys just-in-time): would it be
    possible to list reasons for (silent) discards on a prominent page?
    (e.g. somewhere on https://ftp-master.d.o¹).

    i see that ftp://ftp.upload.debian.org/pub/UploadQueue/ contains a
    README that says:

    Only known Debian developers can upload here. Uploads have to be
    signed by PGP keys in the Debian keyring. Files not meeting this
    criterion or files not mentioned in a .changes file will be removed
    after some time.

    which hints at the current behaviour (but does not make it explicit).

    and to be honest: i think that some random file on an ftp-server is not
    very visible in the first place.
    chrome and firefox both have ditched ftp support, which reduces the
    options to just *browse* the ftp-directory to...what? filezilla
    (shudder) and ftp on the cmdline (my beard is now white enough to get
    homely feelings when i encounter such a thing; but really?)²

    gfmsar
    IOhannes

    ¹ i guess https://ftp-master.debian.org/#rejections would be a good
    starting place, although this currently only speaks about explicit
    *rejects* , and silently discards the notion of silent *discards*.
    ² is there some special reason to not make the UploadQueue available via
    https *also*? at least i haven't found a browseable link anywhere...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ben Finney@21:1/5 to Andrey Rahmatullin on Tue Jun 28 01:00:01 2022
    Andrey Rahmatullin <wrar@debian.org> writes:

    On Mon, Jun 27, 2022 at 09:02:30AM +1000, Ben Finney wrote:
    In this thread I want to discover: How can I find out what's
    happening and why the Debian archive is no longer sending me any
    email messages about my package uploads?

    You should check usper.debian.org:/srv/upload.debian.org/queued/run/log

    Thank you, that has the information I need, and now I successfully
    diagnosed what was wrong with a couple of uploads.

    As to how someone can know this in future:

    "IOhannes m zmölnig (Debian/GNU)" <umlaeute@debian.org> writes:

    as i've wondered myself about this in the past (not for some time
    though, since i no longer update my keys just-in-time): would it be
    possible to list reasons for (silent) discards on a prominent page?
    (e.g. somewhere on https://ftp-master.d.o¹).

    Yes, please. I think your suggestions are a good starting point.

    --
    \ “Airports are ugly. Some are very ugly. Some attain a degree of |
    `\ ugliness that can only be the result of a special effort.” | _o__) —Douglas Adams, _The Long Dark Tea-Time of the Soul_, 1988 |
    Ben Finney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)