[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1068505: marked as done (RFH: reprepro -- Move experimental multi-version feature to unstable)

Your message dated Fri, 31 Jan 2025 12:06:31 +0000
with message-id <E1tdpn5-00HEOE-CP@fasolo.debian.org>
and subject line Bug#1068505: fixed in reprepro 5.4.6-2
has caused the Debian Bug report #1068505,
regarding RFH: reprepro -- Move experimental multi-version feature to unstable
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.)


-- 
1068505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068505
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
X-Debbugs-Cc: debian-devel@lists.debian.org
Control: affects -1 src:reprepro

Hi,
To tackle the much-requested #570623 multiple version management in reprepro, I took over Maintainership of the package and integrated the existing work in experimental. There are three important bugs that were filed against it that need to be fixed to finally merge that work to unstable. The bugs are 

#1051537
#1016111
#1017983

One of them is surely a big endian-only bug, the other ones are database consistency problems that might be related.
As many in the Debian world depend on reprepro to manage their repositories, I would like to ask for help because I did not have the capacity in the last two years (and probably not in the remaining year to come during the trixy cycle) to give those bugs the attention that they deserve. 

Thanks for your help,
Bastian

--- End Message ---
--- Begin Message --- 
Source: reprepro
Source-Version: 5.4.6-2
Done: Bastian Germann <bage@debian.org>

We believe that the bug you reported is fixed in the latest version of
reprepro, 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 1068505@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann <bage@debian.org> (supplier of updated reprepro 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Fri, 31 Jan 2025 12:44:44 +0100
Source: reprepro
Architecture: source
Version: 5.4.6-2
Distribution: unstable
Urgency: medium
Maintainer: Bastian Germann <bage@debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 1068505
Changes:
 reprepro (5.4.6-2) unstable; urgency=medium
 .
   * Move to unstable (Closes: #1068505)
   * d/copyright: Add filecntl.c info
Checksums-Sha1:
 31558d52aaddc1ca4ad7d939344957689f5a4a62 1756 reprepro_5.4.6-2.dsc
 f5568dfe643dea7cfde7207a3da123906b50866e 15248 reprepro_5.4.6-2.debian.tar.xz
 b2c1287cfc7f4c6e5f7099a30684816b888f97e1 5286 reprepro_5.4.6-2_source.buildinfo
Checksums-Sha256:
 7aa5e23d0a24e94fbeb1e80f02eb2cc8199d04ae93e1a708c0b1e528cc1ce822 1756 reprepro_5.4.6-2.dsc
 b9dda8bd9e0d998af0afe0af0e2d3b93ca79a3d8b9d532208c4bf22461fded3d 15248 reprepro_5.4.6-2.debian.tar.xz
 effc79a9c53bf1ffc4d93b1e2d448553e5f2edb95f1383222c752a294eb8448d 5286 reprepro_5.4.6-2_source.buildinfo
Files:
 e1fe6b192fe0a7a149f512f337a4837c 1756 utils optional reprepro_5.4.6-2.dsc
 bcade2b6045f9e56741754ea74fda17d 15248 utils optional reprepro_5.4.6-2.debian.tar.xz
 6b58d89f0ffeb9efa0b65e0c7fdb6843 5286 utils optional reprepro_5.4.6-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmecuHUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFHcKC/sHVmrvkDkorzShu8V3p1YHT8DahRtpSrvh
4+Ur4SZKygRwD7b7zcTPH4Bm/B7YLN+hiEyMq6Pr8e9rGf/jc8UYb19IEjoxO1eT
tTmF+HCXONzeVbRQ8bBZoQNFcuDPqU4TBmVqMMOBaXv++lWXo2rby1e1kJ0FlviZ
f2TbIT4Dv/DWq6kVJTQDsWR4odFpu5+BHXwQGioL5T0KCvqhQFEzq2ABNvKAu2Et
MG1Mhor/LYj3XC/qAhe6IuErjXwbBlfFvo+MVTvc0QEwW+IKC/hkKto60zlbWUHa
iLEoSXQSAfrQt3lg1cn0UhBgxQNUAEvoxk8nMSFNUDI3e0yyhKyt4YmDcY3M29sz
q3MbjfuOzKXYqAz51Y6mU50voHVrMkx0LEXR9Uknrg3vr4VhYkJHmcxwi3JaBEft
IIFRTUOUNNNN0UPCU1s2/xU7wU+3/4bwm8qe3lCbnUaCK5XuoHQ/PJllO2rWYDIO
3F/KPDD0/EMRoMKWuTgJhl+jjWLj9NE=
=+ixl
-----END PGP SIGNATURE-----

Attachment: pgpmljKHJKNYh.pgp
Description: PGP signature


--- End Message ---
Reply to: