Your message dated Wed, 15 Jan 2025 01:56:18 +0000
with message-id <e1txsdm-006djt...@fasolo.debian.org>
and subject line Bug#1091073: fixed in meli 0.8.10+dfsg-2
has caused the Debian Bug report #1091073,
regarding meli: FTBFS: Could not create log file in XDG_DATA_DIR: Os { code: 
13, kind: PermissionDenied, message: \"Permission denied\" }
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 ow...@bugs.debian.org
immediately.)


-- 
1091073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meli
Version: 0.8.10+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20241222 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> running 1 test
> test test_cli_subcommands ... FAILED
> 
> failures:
> 
> ---- test_cli_subcommands stdout ----
> thread 'test_cli_subcommands' panicked at 
> /<<PKGBUILDDIR>>/debian/cargo_registry/rusty-fork-0.3.0/src/fork_test.rs:135:9:
> child exited unsuccessfully with exit status: 70
> stack backtrace:
> note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
> backtrace.
> 
> running 1 test
> thread 'test_cli_subcommands' panicked at 
> /usr/src/rustc-1.83.0/library/core/src/ops/function.rs:250:5:
> Unexpected return code, failed var == 0
> └── var: 101
> 
> code=101
> stdout=""
> stderr=```
> thread \'main\' panicked at melib/src/utils/logging.rs:190:37:
> Could not create log file in XDG_DATA_DIR: Os { code: 13, kind: 
> PermissionDenied, message: \"Permission denied\" }
> stack backtrace:
> note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
> backtrace.
> ```
> 
> 
> stack backtrace:
> note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
> backtrace.
> 
> 
> failures:
>     test_cli_subcommands
> 
> test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered 
> out; finished in 0.85s
> 
> error: test failed, to rerun pass `-p meli --test test_cli_subcommands`
> dh_auto_test: error: /usr/share/dh-rust/bin/cargo test returned exit code 101


The full build log is available from:
http://qa-logs.debian.net/2024/12/22/meli_0.8.10+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20241222;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20241222&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
Source: meli
Source-Version: 0.8.10+dfsg-2
Done: Jonas Smedegaard <d...@jones.dk>

We believe that the bug you reported is fixed in the latest version of
meli, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1091...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard <d...@jones.dk> (supplier of updated meli package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 15 Jan 2025 01:37:20 +0100
Source: meli
Architecture: source
Version: 0.8.10+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard <d...@jones.dk>
Changed-By: Jonas Smedegaard <d...@jones.dk>
Closes: 1091073
Changes:
 meli (0.8.10+dfsg-2) unstable; urgency=medium
 .
   * add patch cherry-picked upstream
     to purge subprocess envs in tests;
     closes: bug#1091073,
     thanks to Lucas Nussbaum and Manos Pitsidianakis
   * update copyright info: update coverage
Checksums-Sha1:
 1987e3f88a6567c6c5424f8f5c652b64e124c8a6 4188 meli_0.8.10+dfsg-2.dsc
 acc78bfd2dde47603597bb086968f49d4cb3a5e2 18868 meli_0.8.10+dfsg-2.debian.tar.xz
 6d0219a176a899dc2ce72d78203c134e9acd382a 25541 
meli_0.8.10+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 ea5d246ef3df68db62d940f0057e5900d4a4b75b4f6ad385e7796c132e09f23a 4188 
meli_0.8.10+dfsg-2.dsc
 970da39e77fb0b1c565552071b14d12953eb2192409981c7af5a31de25ded9f1 18868 
meli_0.8.10+dfsg-2.debian.tar.xz
 3ae5b3efbebf2d6decd5001db7e96228fd555ffb6a715aef77eac215a06710ad 25541 
meli_0.8.10+dfsg-2_amd64.buildinfo
Files:
 44d7d91f9c79dafc52b1a952974432da 4188 mail optional meli_0.8.10+dfsg-2.dsc
 fbb761ce8938a2954b1e4d6c8d79d894 18868 mail optional 
meli_0.8.10+dfsg-2.debian.tar.xz
 4468aa316cbc005468176a13ee013deb 25541 mail optional 
meli_0.8.10+dfsg-2_amd64.buildinfo


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

wsG7BAEBCgBvBYJnhwRcCRAsfDFGwaABIUcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmdnoWvLnQ+WEqIKpLEGTvBakxyY4Rs+0EMQT25NSsuW
oxYhBJ/j6cNmkaaf9TzGhCx8MUbBoAEhAAB2Vw/+PiHkqproCFHTXr5MT25iwLyt
bekn4xOG18ySnbfVACPqUE/MURjfwghoc17FwX0RTPPza8KYGlj8FLllo9GshDOS
YPwVtfewfcHoYMPduHxueEtK8vZ5jVERyDAifG4hRQ+l1aARrj19Wh3FSh6GLxM2
rTAGvIqajaboObsjbSx6A3lTxToIaBeyCe6V98wQqa0fasVLZFKTyMIT9HPpHR7Y
iHP9M+uVCrvU1avRlPeXqKPGax2Zq/PD06MFzg39ZjF+LmbcKxvJ4yxrNnmW/UJI
iBwY5v7o3I5SU8k6qarrP0bhiDXWZo8MWkZsfNkidWwXgiw/FpR/5ZC1OnfbzB1j
UWxyxh47rH9kcw1jnme4Ht5t2EVlVvnu2/eiwDZsEELktuaELiEQzqsmQBqj+7QQ
9hwq0/mLAXY99YKrH2jV5ANEbKo76GdLvDSnJPuNCOmkvYUQWIzYNVbfvixzmf/f
L+YPBig4gbVFgJlSifJhycpWeofwxTfVj6fvSGFuGDa3spPqySlOOw5GgWURSw+z
BVY1Unb0euBth3AVjHv72hqBTWBzUPVDThRhHXx3ipl8KHsB6P3kC4mjhbUeUfVH
gw4aZpDvuSnITHVLSFYnRZhLdeE4InekRELCCIZYowL0KA8niPnI1/HWDBIoTWqB
rFkm1XsYI3wjArDRuDo=
=LLhP
-----END PGP SIGNATURE-----

Attachment: pgpzcIyE6QMEw.pgp
Description: PGP signature


--- End Message ---

Reply via email to