• Bug#1104886: schleuder: will FTBFS during trixie support period

    From Santiago Vila@21:1/5 to All on Wed May 7 22:50:02 2025
    Package: src:schleuder
    Version: 5.0.0-8
    Severity: serious
    Tags: ftbfs trixie sid
    User: debian-qa@lists.debian.org
    Usertags: ftbfs-during-trixie-support-period

    Dear maintainer:

    During a rebuild of all packages in unstable in the year 2028, your package failed to build:

    --------------------------------------------------------------------------------
    [...]
    Failures:

    1) running filters .key_auto_import_from_autocrypt_header successfully validates a signature, whose previously unknown key is in the autocrypt-header
    Failure/Error: crypto.sign GPGME::Data.new(plain), options

    ArgumentError:
    NULL pointer given
    # ./lib/schleuder/mail/gpg/gpgme_helper.rb:79:in `sign'
    # ./lib/schleuder/mail/gpg/sign_part.rb:6:in `initialize'
    # ./lib/schleuder/mail/gpg/signed_part.rb:29:in `new'
    # ./lib/schleuder/mail/gpg/signed_part.rb:29:in `sign'
    # ./lib/schleuder/mail/gpg.rb:55:in `block in sign'
    # ./lib/schleuder/mail/gpg.rb:111:in `instance_eval'
    # ./lib/schleuder/mail/gpg.rb:111:in `block in construct_mail'
    # ./lib/schleuder/mail/gpg.rb:104:in `construct_mail'
    # ./lib/schleuder/mail/gpg.rb:52:in `sign'
    # ./lib/schleuder/mail/gpg/delivery_handler.rb:13:in `deliver_mail'
    # ./spec/schleuder/integration/filters_spec.rb:178:in `block (3 levels) in <top (required)>'
    # ./spec/spec_helper.rb:60:in `block (3 levels) in <top (required)>'
    # ./spec/spec_helper.rb:59:in `block (2 levels) in <top (required)>'
    # ------------------
    # --- Caused by: ---
    # GPGME::Error::UnusableSecretKey:
    # Unusable secret key
    # ./lib/schleuder/mail/gpg/gpgme_helper.rb:79:in `sign'

    2) running filters .key_auto_import_from_attachments successfully validates a signature, whose previously unknown key is attached
    Failure/Error: crypto.sign GPGME::Data.new(plain), options

    ArgumentError:
    NULL pointer given
    # ./lib/schleuder/mail/gpg/gpgme_helper.rb:79:in `sign'
    # ./lib/schleuder/mail/gpg/sign_part.rb:6:in `initialize'
    # ./lib/schleuder/mail/gpg/signed_part.rb:29:in `new'
    # ./lib/schleuder/mail/gpg/signed_part.rb:29:in `sign'
    # ./lib/schleuder/mail/gpg.rb:55:in `block in sign'
    # ./lib/schleuder/mail/gpg.rb:111:in `instance_eval'
    # ./lib/schleuder/mail/gpg.rb:111:in `block in construct_mail'
    # ./lib/schleuder/mail/gpg.rb:104:in `construct_mail'
    # ./lib/schleuder/mail/gpg.rb:52:in `sign'
    # ./lib/schleuder/mail/gpg/delivery_handler.rb:13:in `deliver_mail'
    # ./spec/schleuder/integration/filters_spec.rb:215:in `block (3 levels) in <top (required)>'
    # ./spec/spec_helper.rb:60:in `block (3 levels) in <top (required)>'
    # ./spec/spec_helper.rb:59:in `block (2 levels) in <top (required)>'
    # ------------------
    # --- Caused by: ---
    # GPGME::Error::UnusableSecretKey:
    # Unusable secret key
    # ./lib/schleuder/mail/gpg/gpgme_helper.rb:79:in `sign'

    3) running filters .key_auto_import_from_attachments successfully validates a signature, whose previously unknown key is attached, from an encrypted+signed message
    Failure/Error: ctx.encrypt_sign(recipient_keys, plain_data, cipher_data, flags)

    GPGME::Error::NoSecretKey:
    No secret key
    # ./lib/schleuder/mail/gpg/gpgme_helper.rb:30:in `block in encrypt'
    # ./lib/schleuder/mail/gpg/gpgme_helper.rb:23:in `encrypt'
    # ./lib/schleuder/mail/gpg/encrypted_part.rb:27:in `initialize'
    # ./lib/schleuder/mail/gpg.rb:39:in `new'
    # ./lib/schleuder/mail/gpg.rb:39:in `block in encrypt'
    # ./lib/schleuder/mail/gpg.rb:111:in `instance_eval'
    # ./lib/schleuder/mail/gpg.rb:111:in `block in construct_mail'
    # ./lib/schleuder/mail/gpg.rb:104:in `construct_mail'
    # ./lib/schleuder/mail/gpg.rb:25:in `encrypt'
    # ./lib/schleuder/mail/gpg/delivery_handler.rb:11:in `deliver_mail'
    # ./spec/schleuder/integration/filters_spec.rb:253:in `block (3 levels) in <top (required)>'
    # ./spec/spec_helper.rb:60:in `block (3 levels) in <top (required)>'
    # ./spec/spec_helper.rb:59:in `block (2 levels) in <top (required)>'

    Finished in 2 minutes 30.6 seconds (files took 1.09 seconds to load)
    583 examples, 3 failures

    Failed examples:

    rspec ./spec/schleuder/integration/filters_spec.rb:159 # running filters .key_auto_import_from_autocrypt_header successfully validates a signature, whose previously unknown key is in the autocrypt-header
    rspec ./spec/schleuder/integration/filters_spec.rb:197 # running filters .key_auto_import_from_attachments successfully validates a signature, whose previously unknown key is attached
    rspec ./spec/schleuder/integration/filters_spec.rb:232 # running filters .key_auto_import_from_attachments successfully validates a signature, whose previously unknown key is attached, from an encrypted+signed message

    Randomized with seed 56554

    /usr/bin/ruby3.3 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.13.1/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/exe/rspec --exclude-pattern \[\"../spec/
    schleuder/integration/keywords_spec.rb\"\] --format documentation failed
    ERROR: Test "ruby3.3" failed. Exiting.
    dh_auto_install: error: dh_ruby --install /<<PKGBUILDDIR>>/debian/schleuder returned exit code 1
    make: *** [debian/rules:9: binary] Error 25
    dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --------------------------------------------------------------------------------

    The above is just how the build ends and not necessarily the most relevant part.
    If required, the full build log is available here:

    https://people.debian.org/~sanvila/build-logs/ftbfs-future/

    About the archive rebuild: This is an effort to keep trixie free from FTBFS bugs
    during its lifetime as a supported distribution, as explained here:

    https://lists.debian.org/debian-devel/2024/05/msg00414.html

    This category of bugs is considered to be RC for trixie.

    The build was made using sbuild and a reduced chroot with only
    build-essential packages.

    If you could not reproduce the bug please contact me privately, as I
    am willing to provide ssh access to a virtual machine where the bug is
    fully reproducible.

    If this is really a bug in one of the build-depends, please use
    reassign and add an affects on src:schleuder, so that this is still
    visible in the BTS web page for this package.

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Santiago Vila@21:1/5 to All on Thu May 29 00:40:01 2025
    This is a multi-part message in MIME format.
    tags 1104886 patch
    thanks

    Hello. The attached patch should fix the issue by disabling the
    three failing tests.

    Thanks. RGVzY3JpcHRpb246IERpc2FibGUgdGVzdHMgd2hpY2ggYXJlIGtub3duIHRvIGZhaWwgZHVy aW5nIHRyaXhpZSBzdXBwb3J0IHBlcmlvZApBdXRob3I6IFNhbnRpYWdvIFZpbGEgPHNhbnZp bGFAZGViaWFuLm9yZz4KQnVnLURlYmlhbjogaHR0cHM6Ly9idWdzLmRlYmlhbi5vcmcvMTEw NDg4NgpMYXN0LVVwZGF0ZTogMjAyNS0wNS0yOQoKLS0tIGEvc3BlYy9zY2hsZXVkZXIvaW50 ZWdyYXRpb24vZmlsdGVyc19zcGVjLnJiCisrKyBiL3NwZWMvc2NobGV1ZGVyL2ludGVncmF0 aW9uL2ZpbHRlcnNfc3BlYy5yYgpAQCAtMTU3LDYgKzE1Nyw3IEBACiAKICAgY29udGV4dCgn LmtleV9hdXRvX2ltcG9ydF9mcm9tX2F1dG9jcnlwdF9oZWFkZXInKSBkbwogICAgIGl0KCdz dWNjZXNzZnVsbHkgdmFsaWRhdGVzIGEgc2lnbmF0dXJlLCB3aG9zZSBwcmV2aW91c2x5IHVu a25vd24ga2V5IGlzIGluIHRoZSBhdXRvY3J5cHQtaGVhZGVyJykgZG8KKyAgICAgIHNraXAo ImRpc2FibGVkIGJlY2F1c2UgaXQgd2lsbCBmYWlsIGR1cmluZyB0cml4aWUgc3VwcG9ydCBw ZXJpb2QiKQogICAgICAgbGlzdCA9IGNyZWF0ZSg6bGlzdCwgc2VuZF9lbmNyeXB0ZWRfb25s eTogZmFsc2UsIGtleV9hdXRvX2ltcG9ydF9mcm9tX2VtYWlsOiB0cnVlKQogICAgICAgbGlz dC5zdWJzY3JpYmUoJ21lQGxvY2FsaG9zdCcsIG5pbCwgdHJ1ZSkKICAgICAgIHRtcF9nbnVw Z19ob21lID0gRGlyLm1rdG1wZGlyCkBAIC0xOTUsNiArMTk2LDcgQEAKIAogICBjb250ZXh0 KCcua2V5X2F1dG9faW1wb3J0X2Zyb21fYXR0YWNobWVudHMnKSBkbwogICAgIGl0KCdzdWNj ZXNzZnVsbHkgdmFsaWRhdGVzIGEgc2lnbmF0dXJlLCB3aG9zZSBwcmV2aW91c2x5IHVua25v d24ga2V5IGlzIGF0dGFjaGVkJykgZG8KKyAgICAgIHNraXAoImRpc2FibGVkIGJlY2F1c2Ug aXQgd2lsbCBmYWlsIGR1cmluZyB0cml4aWUgc3VwcG9ydCBwZXJpb2QiKQogICAgICAgbGlz dCA9IGNyZWF0ZSg6bGlzdCwgc2VuZF9lbmNyeXB0ZWRfb25seTogZmFsc2UsIGtleV9hdXRv X2ltcG9ydF9mcm9tX2VtYWlsOiB0cnVlKQogICAgICAgbGlzdC5zdWJzY3JpYmUoJ21lQGxv Y2FsaG9zdCcsIG5pbCwgdHJ1ZSkKICAgICAgIHRtcF9nbnVwZ19ob21lID0gRGlyLm1rdG1w ZGlyCkBAIC0yMzAsNiArMjMyLDcgQEAKICAgICBlbmQKIAogICAgIGl0KCdzdWNjZXNzZnVs bHkgdmFsaWRhdGVzIGEgc2lnbmF0dXJlLCB3aG9zZSBwcmV2aW91c2x5IHVua25vd24ga2V5 IGlzIGF0dGFjaGVkLCBmcm9tIGFuIGVuY3J5cHRlZCtzaWduZWQgbWVzc2FnZScpIGRvCisg ICAgICBza2lwKCJkaXNhYmxlZCBiZWNhdXNlIGl0IHdpbGwgZmFpbCBkdXJpbmcgdHJpeGll IHN1cHBvcnQgcGVyaW9kIikKICAgICAgIGxpc3QgPSBjcmVhdGUoOmxpc3QsIHNlbmRfZW5j cnlwdGVkX29ubHk6IGZhbHNlLCBrZXlfYXV0b19pbXBvcnRfZnJvbV9lbWFpbDogdHJ1ZSkK ICAgICAgIGxpc3Quc3Vic2NyaWJlKCdtZUBsb2NhbGhvc3QnLCBuaWwsIHRydWUpCiAgICAg ICBsaXN0X2tleSA9IGxpc3Qua2V5LmV4cG9ydAo=

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Holger Levsen@21:1/5 to Santiago Vila on Fri Jun 6 13:00:01 2025
    On Thu, May 29, 2025 at 12:35:29AM +0200, Santiago Vila wrote:
    Hello. The attached patch should fix the issue by disabling the
    three failing tests.

    I'd apply this patch in 2028 (or whenever it will be needed) and until
    then downgrade the severity of this bug. Or extend the patch to only conditionally disable the tests in 2028 or later.

    Disabling the tests now because they will fail in three years is not
    really a good solution.


    --
    cheers,
    Holger

    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
    ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
    ⠈⠳⣄

    "I know what you're thinking" used to be an idiom but now it's a business model.

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

    iQIzBAABCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAmhCx4kACgkQCRq4Vgaa qhyu3A//ZHqMmAV7Qj48OhGlBwJuD07D0SVCOVL60BwR1LsKoNX+TEMD5D7kmmTG Y0qB+vtkCl1HBRjb/9gkeguys6gzk9AbBfL0tu9b2Eg+ZDDSzJYRvnzrdEvhzuLZ gEmEwsmqZVzjEUEjM6rd1Zlf4Jbf02ofxfEKgsGGmW/3YgusqQ0gMjVgpz/i2Wv1 NTC0k+mKsCSuc08ukay8LRLTjqWrNkeDKTEcWfpisKi5MeGNNxYeiTPWlJY4/TYG vbMzyvXGZdzLjGS2B5Bd0hySaLGHPsF87HPTT/DynV7YgU2lhdy7+/EC5ZuX7U5P sOKhF7O6FRQFoEUxmfICLvJhzBTls8CoAaTHTP2bHvsMe5k15WRIE+U3iKk4tCj0 n2gYln0rW21K2WJ2GtlA5ByqfQwBB+NCjlLF7SmiAAu8iUD7X9BbM+egsunc2bPi Ln/EQOg0neZagl8FwxIqWSQFCP5MMOSrVoaZTGrDGeOTyC0w8WZeELOsQf+9E7IE WE/WXmjV443pON98pqLT5VTnHqcmg7x6JsImpoNdL/GuGjm5jGG4cozIEx1Acgrr t3a1sKVgM09vToIDKuE7AA/b27LqKScS
  • From Santiago Vila@21:1/5 to All on Fri Jun 6 13:20:01 2025
    El 6/6/25 a las 12:48, Holger Levsen escribió:
    Or extend the patch to only
    conditionally disable the tests in 2028 or later.

    Note: The bug says "it will start failing to build at some point
    between now and 2028", not "will fail in 2028".

    If you can determine the exact date at which it will start to fail
    and conditionally run the tests according to such date, that would
    be fine as well.

    The idea is to not have any time-bombs in a stable distribution.

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sun Jun 8 16:00:01 2025
    This is a multi-part message in MIME format...

    Your message dated Sun, 08 Jun 2025 13:49:52 +0000
    with message-id <E1uOGPI-005Zdm-79@fasolo.debian.org>
    and subject line Bug#1104886: fixed in schleuder 5.0.1-1
    has caused the Debian Bug report #1104886,
    regarding schleuder: will FTBFS during trixie support period
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    1104886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104886
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 7 May 2025 20:43:06 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-121.4 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,FROMDEVELOPER,HAS_PACKAGE,
    RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_NONE,USER_IN_DKIM_WELCOMELIST,
    USER_IN_DKIM_WHITELIST,X_DEBBUGS_CC autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 54; hammy, 150; neutral, 181; spammy,
    0. spammytokens: hammytokens:0.000-+--trixie, 0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--H*F:U*sanvila, 0.000-+--H*rp:U*sanvila Return-path: <sanvila@debian.org>
    Received: from mitropoulos.debian.org ([2001:648:2ffc: