Your message dated Tue, 02 Oct 2018 11:19:11 +0000
with message-id <[email protected]>
and subject line Bug#899762: fixed in biblesync 1.1.2-2
has caused the Debian Bug report #899762,
regarding biblesync: Invalid maintainer address 
[email protected]
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 [email protected]
immediately.)


-- 
899762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899762
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:biblesync
Version: 1.1.2-1
Severity: serious
User: [email protected]
Usertag: alioth-lists-maintainer

Dear uploader of biblesync,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package biblesync since the list address
[email protected] used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team <[email protected]>
  and provide all the necessary information.

  More information about the new service can be found here:
  <https://wiki.debian.org/Alioth/MailingListContinuation>

* More options, even if imperfect, can be found at
  <https://wiki.debian.org/Salsa/AliothMigration#Import_mailing_list>


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
[email protected] is 16.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

    Christoph and some alioth-lists maintainers

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: biblesync
Source-Version: 1.1.2-2

We believe that the bug you reported is fixed in the latest version of
biblesync, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Teus Benschop <[email protected]> (supplier of updated biblesync 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 [email protected])


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

Format: 1.8
Date: Tue, 02 Oct 2018 13:01:22 +0200
Source: biblesync
Binary: libbiblesync-dev libbiblesync1.1
Architecture: source
Version: 1.1.2-2
Distribution: unstable
Urgency: high
Maintainer: CrossWire Packaging Team 
<[email protected]>
Changed-By: Teus Benschop <[email protected]>
Description:
 libbiblesync-dev - multicast protocol to support Bible co-navigation 
(development fi
 libbiblesync1.1 - multicast protocol to support Bible co-navigation
Closes: 899762
Changes:
 biblesync (1.1.2-2) unstable; urgency=high
 .
   [ Dominique Corbex ]
   lintian cleanup:
   * Bump Standards-Version to 3.9.8
   * Change Vcs-Git to https
 .
   [ Teus Benschop ]
   * debian/control: Updated maintainer email: Closes: #899762
   * debian/control: Updated Vcs-* for Salsa
Checksums-Sha1:
 cd8718e772845d8efadb9f56e395a0f8d54e269f 2179 biblesync_1.1.2-2.dsc
 09a9c18cce581709b281ead31d9ff633475fd0dc 2972 biblesync_1.1.2-2.debian.tar.xz
 e80273a12c0ff0cae813f55be7fa2d4010f70c4d 6440 
biblesync_1.1.2-2_source.buildinfo
Checksums-Sha256:
 685de5becb018eaee13473822daf2bf232d33a17a2e225d7c5e3c1bfda810f54 2179 
biblesync_1.1.2-2.dsc
 e06ff54b252224b271e073a6ea582fc66d018917a3f11cface266e5c0543f42f 2972 
biblesync_1.1.2-2.debian.tar.xz
 28e308e6dcf9e25d1b477d878df85ba76ce6d4a5ae80007049cd4a77e84de320 6440 
biblesync_1.1.2-2_source.buildinfo
Files:
 738b206a77b6b18304e3664d26031af1 2179 libs optional biblesync_1.1.2-2.dsc
 a17224fd07d3082a4e196c54e43c9c26 2972 libs optional 
biblesync_1.1.2-2.debian.tar.xz
 59c89b28a51a63b47dc92ca083e71d84 6440 libs optional 
biblesync_1.1.2-2_source.buildinfo

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

iQJLBAEBCgA1FiEEher+5c8s1QBza9jekwIrrQVjpR0FAluzUJUXHHRldXNqYW5u
ZXR0ZUBnbWFpbC5jb20ACgkQkwIrrQVjpR1qQxAAklIzQ4k8e0hOxsyPQAiUgHTL
3B06z2jV+XNHoKbsS+rugX8Qk9DpqDAMsrMdpMcAFbH5z/b3HFKAUQv1Kj943m3j
7+xPMDf1Fbiwxetqd49ZIsDURfkqqbne/fK3hgXEsjTY7ZDs5bBPqcLqYv+9CRkJ
mWAm537y8xIpqR/e99fS34nhfFMz7A3leDgqurq5BAcVJ4GgUK+MX+Xn+Gf9d3c+
V6IXfG3nJnpmxeTS8cLG4UdiSYf6P9ImhbzxK79NP4SGPpKUghYUKmFx9u5Vl+wi
wzVkL3aKWmNIN9d8TsUcwtR/JdDomd1nOxhYM6+UrgeeTFnGDhSfXvJv9aQ3iNS9
+Z5tGZ1XAc4BiTAdkLCVJsol8P9SCkBSoFLb96LDljW/iWLtamIz2ib5tOuLo97j
mnaBPZf2/wnDaZ0NL0UrMZReqIg+j0dBVqRezmAe0WkULjiay8TY1f3PAgEqLFbo
njp/vqBcpr+jg0QJtKlQGiLDmFcfG7gHrcKfWigGOObl8Q/LjFy3lHZfd9uLk5zW
YWmNc8i3VBfnA9naFjs4wvoRBaCaqhRDppg7zAsPHZlrHHKUCn2kqR+2GE3GL7tK
iBgM1Qi/YfB2rXPjWYdUpymkwK7U3DMbrzP4uzXiW+wmrpD/lnrnhob9kp5edhtp
cddavCPq0v4IL9UW9N4=
=NKDq
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to