Accepted sshfs-fuse 3.7.3-1.1 (source) into unstable
- To: debian-devel-changes@lists.debian.org
- Subject: Accepted sshfs-fuse 3.7.3-1.1 (source) into unstable
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Tue, 07 Feb 2023 21:17:42 +0000
- Debian: DAK
- Debian-architecture: source
- Debian-archive-action: accept
- Debian-changes: sshfs-fuse_3.7.3-1.1_amd64.changes
- Debian-source: sshfs-fuse
- Debian-suite: unstable
- Debian-version: 3.7.3-1.1
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ftp-master.debian.org; s=smtpauto.fasolo; h=Date:Message-Id: Content-Transfer-Encoding:Content-Type:Subject:MIME-Version:To:Reply-To:From: Cc:Content-ID:Content-Description:In-Reply-To:References; bh=umxnXkNDFey2GcoqF/U1ih5s9os5d/gXGxmUxysJGLk=; b=dvFAliQjRIMOQEuaz2cAGY3T9B bRUWzXD3RIXqjK3s/Jk2/0z3dfenfSVp9DOuB/fpfg7pQkfDJ9tAnrGvv0YVTUfEMkWN4WKH+0scb 5AQuf1736zMf+9R7oFn0GBIKclQOZ06CxNZOktVpaAdMQ+8Zee50kyx9CVYJ7eN25lT2Z3kODASwh qM9WrWytMBDNPtDwBBQbXILAS1B1q2jcbqfrIJJcjziNSWVaSOhF8ac34h/qLLiUuprOhc3J3k90X GhF2bRrSjwcCpGpTU0FLviPNkEOg2XbcODN2aSy/3oLwVBGopUSIe5Re3VzuQvL/a6TZUIf7FbBfG lJbO2i+g==;
- Mail-followup-to: debian-devel@lists.debian.org
- Message-id: <E1pPVLS-006ltJ-R0@fasolo.debian.org>
- Reply-to: debian-devel@lists.debian.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 07 Feb 2023 20:33:53 +0100
Source: sshfs-fuse
Architecture: source
Version: 3.7.3-1.1
Distribution: unstable
Urgency: high
Maintainer: Bartosz Fenski <fenio@debian.org>
Changed-By: Daniel Baumann <daniel.baumann@progress-linux.org>
Closes: 1028163
Changes:
sshfs-fuse (3.7.3-1.1) unstable; urgency=high
.
* Non-maintainer upload.
* Disabling test suite (Closes: #1028163):
- First, given that there's no progress on #1028163 for some time now,
and it's not quite clear on how to "properly" address the issue
of using ssh of the host during the test suite (maybe replacing
test with autopkg tests?), I think it's better to disable the test
suite for now rather than to have no sshfs at all (in bookworm).
- Second, in order to prevent the risk of other packages to be autoremoved
that depend on sshfs without having the chance of being re-introduced to
testing after the upcoming freeze in case nobody fixes #1028163 properly,
let's disable the test suite and re-enable it once it's clear how to deal
with it (re-enabling test should be easier to get an unblock for).
Checksums-Sha1:
9da3e54f6bb49da7a8f4f0eaa824a096d7c720d6 1983 sshfs-fuse_3.7.3-1.1.dsc
75b2c17a60a7629057f46a4826b89a28023e630e 8308 sshfs-fuse_3.7.3-1.1.debian.tar.xz
e3324d1855414b25409ebc9ab6c387cf4c687df3 8112 sshfs-fuse_3.7.3-1.1_amd64.buildinfo
Checksums-Sha256:
4e99ccd8e526d0ab5940f057760638a652265d597168d95637b8fbc2f2bebbe2 1983 sshfs-fuse_3.7.3-1.1.dsc
8e5e792818fad69a66172d7465829c53b5a282b04cd3bd4ce86553cffba0cd41 8308 sshfs-fuse_3.7.3-1.1.debian.tar.xz
06a968926ca805fb3361e7ff84515ba74ff6fd56649dd45611b822dfb92218ec 8112 sshfs-fuse_3.7.3-1.1_amd64.buildinfo
Files:
8751f49608722ad6c53d46baf0e4d47d 1983 utils optional sshfs-fuse_3.7.3-1.1.dsc
31c1d564066f0874740b2fbe005ae154 8308 utils optional sshfs-fuse_3.7.3-1.1.debian.tar.xz
895bb89d5fec8c46ef1b4da31398fd06 8112 utils optional sshfs-fuse_3.7.3-1.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmPiuVgACgkQVc8b+Yar
ucf7bQ//fktCV4AvAq33wifFUU57dZjdrPDZiy4HZgeOGGDnk3pdR8Tomk3wjiiY
hgkPN8Cp8RI1yFkctHahz0VAsls3s4rHXmI4Cl3TfjK9z0vXxWJgAxsInkQQCnZ3
ZFxOgIQwdgjlBKQ1BlG0mafmmQTz7lcCW8cKrrfutc9ymj+XQ9pBawNET7x6/+x6
eyvuuDrW6v4Um1nMXQqoUhEqgxMvDJJiznI7B+uFRubrFb1zJ5zVlRpe62iwqCBY
PMNMMlhMxG9agnf9Jt6BeAiNnbXVOJN1RoeVLu26tiDvIA0UdVbQOi/1rLso34jQ
DL7c2I5wD2lar9WJ2l7rApfAc5sLsLt7teoqWTSv0iR2/NQiqHTPspbGFlRf4HoY
trcP/oJPPJeY3ZVmNuP+AsteS0FRUxbNcArX86j4Et2Rg5vT649weG2IUcgReF9v
kKxuhU8y8ZNtSnYqvJhfTPsVAksVmV4C0BuYC2xe6Ry+YjgxONAEMlaYQRD3aMNE
vYTUv8pfMeXmHi/YTx/U91flv0j+Xsbi9uKlKnbie7vFaYkxOwrem0oZ/kotC/oL
Dr4XTbk+slinbulefRg1M6QektYDzvhayv+1FUW2M7JudghdU70FQfLexewcpl3T
T4CwHRB9M9pN/Ez5ZVUbiMdOnmgXK7JmIFaM7U4nuWEwucgayI4=
=ch9w
-----END PGP SIGNATURE-----