Your message dated Sat, 04 Feb 2023 07:49:07 +0000
with message-id <[email protected]>
and subject line Bug#1030042: fixed in opentracker 0.0~git20210823.110868e-3
has caused the Debian Bug report #1030042,
regarding opentracker: Misleading README.Debian, compile flags only allow use 
with whitelist profile
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.)


-- 
1030042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030042
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: opentracker
Version: 0.0~git20210823.110868e-2+b1
Severity: normal
X-Debbugs-Cc: [email protected]

Dear Agathe,

from the /usr/share/doc/opentracker/README.Debian, I thougth that it is possible
to switch from white- to blacklist or use no list at all (public tracker):  

| By default, the tracker is run in "private" mode using a whitelist access.
| You need to explicitly list all of the torrent hashes that you want to 
announce
| into the /etc/opentracker/whitelist.txt file.
|
| If you want to switch to "public" mode, allowing to announce any torrent hash,
| you can comment the "access.whitelist" option in
| /etc/opentracker/opentracker.conf.

However, especially the last paragraph seems to be wrong, running without 
"access.whitelist" does not allow any trackers (like an empty whitelist).  

>From upstream's documentation [1]:

| Some variables in opentracker's Makefile control features and behaviour of 
opentracker. Here they are:
| [...]
| You can change that behaviour by enabling ONE of -DWANT_ACCESSLIST_BLACK or 
-DWANT_ACCESSLIST_WHITE.
                                           ^^^^^
So, it looks like the use cases whitelist tracker, blacklist tracker and open 
tacker
are defined by compile time options and can't be modified later when invoking 
the 
program.  Comments in the config file state:

#      It is pointless and hence not possible to compile black AND white
#      listing, so choose one of those options at compile time.
                                               ^^^^^^^^^^^^^^^
Several tests and package rebuilds with different compile flags in 
debian/rules have confirmed this. 

Hm. It would of course be great to be able to modify the mode with options / 
config file. 

Best regards,

  Andi


[1] http://erdgeist.org/arts/software/opentracker/

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages opentracker depends on:
ii  libc6      2.36-8
ii  libowfat0  0.32-4
ii  zlib1g     1:1.2.13.dfsg-1

opentracker recommends no packages.

opentracker suggests no packages.

-- Configuration Files:
/etc/opentracker/whitelist.txt changed:
a2a3a73e80da24ab2a4ac2a0624bdefb9b1fa20a


-- no debconf information

--- End Message ---
--- Begin Message ---
Source: opentracker
Source-Version: 0.0~git20210823.110868e-3
Done: Agathe Porte <[email protected]>

We believe that the bug you reported is fixed in the latest version of
opentracker, 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.
Agathe Porte <[email protected]> (supplier of updated opentracker 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: Sat, 04 Feb 2023 08:31:50 +0100
Source: opentracker
Architecture: source
Version: 0.0~git20210823.110868e-3
Distribution: unstable
Urgency: medium
Maintainer: Agathe Porte <[email protected]>
Changed-By: Agathe Porte <[email protected]>
Closes: 1030042
Changes:
 opentracker (0.0~git20210823.110868e-3) unstable; urgency=medium
 .
   * Fix wrong README.debian instructions (Closes: #1030042)
   * d/copyright: Update year
   * Update Standards-Version to 4.6.2 (no change)
Checksums-Sha1:
 acf36614c15f996ea1c37d16590345b6549eef3b 2103 
opentracker_0.0~git20210823.110868e-3.dsc
 f0a07a98429f603bc12a93166616c7bb947aaaa9 6316 
opentracker_0.0~git20210823.110868e-3.debian.tar.xz
 6aa9875c0b96fdd47459287d09ef66d228e71c05 5603 
opentracker_0.0~git20210823.110868e-3_source.buildinfo
Checksums-Sha256:
 2473df619af3ee5013e8fe03925c38599ace2cb5b7842f8ef3509546bdde5dd0 2103 
opentracker_0.0~git20210823.110868e-3.dsc
 b55aab3f9a929b6d37ec8817f48674bd00da9337ad1ea5b762655bef52dde4fe 6316 
opentracker_0.0~git20210823.110868e-3.debian.tar.xz
 d92ed6299c555a41418cda9bcacd815f914ed7bebc91b72df7a867c8d693928c 5603 
opentracker_0.0~git20210823.110868e-3_source.buildinfo
Files:
 92f65df33c567e52b822672482c354c5 2103 net optional 
opentracker_0.0~git20210823.110868e-3.dsc
 6bd6ccb7f30e75e1404c2a28f69461cd 6316 net optional 
opentracker_0.0~git20210823.110868e-3.debian.tar.xz
 1d5b1bda518436a3278362eda02abe4e 5603 net optional 
opentracker_0.0~git20210823.110868e-3_source.buildinfo

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

iQJIBAEBCgAyFiEE2xMJtrCqCOwoob8cBjaerR0+AQUFAmPeCg8UHGRlYmlhbkBt
aWNyb2pvZS5vcmcACgkQBjaerR0+AQWzAg//aOWrmcqs24sqwgeBTSg3cERRbwlv
Viyqv6GbiKo6Z1yi4pl7kbupUpNMXtLx5WRnAuMSw+muf48vdnQYWGgjG/yyCKw8
mTBxBzzQxpF/AgwnEfNTOciZkYpZO9zPzFlUcd60PefGrJ4JSgdSdmMhSMamuebK
cCrLTQjIga65eNjwEAQ6IrOg/Oz0yOj4+uLiM4jAYSRk2oYZUbNj1gLcEoW+tAyX
/kk3L40RfotGCXNaNuJF5i/PG2almtWIcug3QkjaiTlNNLMYqwP3u6bLckIJQYQN
R10FulycGDhIxqcub9QCx18yYoHdoRcL/YXevDnqTgbgZacaIhfUH2Hemlxsw33Z
Ye+pNeKZRPnfrxF6SljreCGiqqkzW455pHfUzPCwoEFJDPTGByq7RVKlirn2okVi
A8p3S+DRiW6oNPELiAH9mGjTFxhtoURpsu661yDJmU1bCdg2xu70zndcpaSM2Qxc
OIEP+5qoaMCwurDSaBDEzYSboxbhK9BLMg8OCWAU9OvG5TEmYx0q9kMKOYqeBJND
mbSZB1vVhM3FGnge7NqspI/8NHDwn2kIbw2ihZG7N28fFKni6onfcIFS5IWkQJIp
UtUyyIGkL9M7fKiC1NKvfLuMZ62CGEK3DHDQqamAMlB2h0pUm8wzxzrxXIF0f0jj
Z6VnqhFu4TsvsCw=
=XpWD
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to