• No processing/acceptance from dak for some packages?

    From Nilesh Patra@21:1/5 to All on Sun Sep 26 09:10:01 2021
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2bumYlpZPtpgiNrpU9qBQFDuzqXnRIVV0
    Content-Type: text/plain; charset=utf-8
    Content-Language: en-US
    Content-Transfer-Encoding: quoted-printable

    Hi,

    I have been trying to upload yaggo 1.5.10-5 for more than 12 hours by now.
    And I have done this several times by now[look here]

    It gets to the ftp upload server, sits there for a while, and vanishes eventually.
    There is however no further processing, neither accept, nor reject.

    I however, tried uploading golang-github-shenwei356-bio 0.3.2-1, and golang-github-shenwei356-util 0.4.0-1 and these went smoothly.

    This looks just... weird. Would someone know why this happens?

    [look here]: All attempts visible here: https://alioth-lists.debian.net/pipermail/debian-med-packaging/2021-September/thread.html

    Nilesh











    --2bumYlpZPtpgiNrpU9qBQFDuzqXnRIVV0--

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

    wsF5BAABCAAjFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmFQGqQFAwAAAAAACgkQALrnSzQzafEO QA//eeA0NwPFYruVZPkUSdsCLke45YN5FLZY+dALhq5dc+Th7tLhMCSzIRc94TJu+NuLuc0AOGz6 b2g0Y+z/B0hBflj06TYOaj81HpdFexOkba8tabCbBHqdyQKYs8tUGdHiPKJ9iSHN2bVGZr9n+7Ov HD7fZZIql9fUIZwxItPfMDT+hVX4m+JEpvhNW4QWzipCeNfdVtXl3HamhE8u+cjOxgVc338PBY5U uuQIj9e/c+YDFEkh5Huzehiqnt0PEeSh9Ga3PCuGnxYcOKg8+ElPMn4iOltqt7wEfI9WjpVVbVGk FSXk5ISpZliVyOxmMROi3gVYpsXsNZIk1ctHpp/fQ5C0HWaz7ycQBDnBfnKn1w8mMROwlMEpAJ/9 9C7CZ72eLuotKmAOza3aLNiIYbyOoMFlV8DpXtfRHsEROewBdT2gWOtRcDoVo/AEOl+q0xa/5J8w EusBh9/wa1E/VvNEL9lADOMKRAtK1HnQk0jikS0ZQmUmT8mZUtMmkcpYt6F24xXnufh8cxT5nqVf UZNBlEo0jg+nN0CDMfEMDJX5sbLaEjnP95582in23ckRuJLoB875quqPRrfwSPk7B6DXEBJ8duvL VGrvjTZ3iJHph3I9mwUYzJxqSi24g4BF+pKdMh8cFzSLVJOAhJHZhE77j5Nq68/e3SdJ148RMpb2 ebc=
    =V2rp
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ansgar@21:1/5 to Nilesh Patra on Sun Sep 26 12:30:02 2021
    Nilesh Patra writes:
    This looks just... weird. Would someone know why this happens?

    Someone uploaded a broken .changes file that had different sizes for the
    same file:

    +---
    | Checksums-Sha256:
    | [...]
    | 209dda5709e1a67eab2762013136adc7c3b6977a17a7e3d8a12f5b2c27569875 156580 [...]
    | Files:
    | [...]
    | cda6f0841c01ae3ffb3f9584ba9c5f20 157910 science optional [...]
    +---

    The error handling in the archive software is not very good for this
    error: it stops processing, thus all .changes files sorted after this
    one did not get processed.

    The file was now moved away.

    Anyway, people should *not* edit .changes files manually as it is too
    easy to refer to the wrong files, e.g., a different .orig tarball than
    was used to build the package. I suspect someone did manually edit the
    file here.

    Ansgar

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