From ftpmaster at ftp-master.debian.org  Thu Aug 16 13:08:08 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 16 Aug 2018 12:08:08 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 txtorcon_18.0.2-2_amd64.changes
Message-ID: <E1fqH4S-0007ki-N8@usper.debian.org>

txtorcon_18.0.2-2_amd64.changes uploaded successfully to localhost
along with the files:
  txtorcon_18.0.2-2.dsc
  txtorcon_18.0.2-2.debian.tar.xz
  python-txtorcon-doc_18.0.2-2_all.deb
  python3-txtorcon_18.0.2-2_all.deb
  txtorcon_18.0.2-2_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Thu Aug 16 13:19:48 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 16 Aug 2018 12:19:48 +0000
Subject: [Pkg-privacy-maintainers] txtorcon_18.0.2-2_amd64.changes ACCEPTED
 into unstable
Message-ID: <E1fqHFk-000FAJ-PY@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Thu, 16 Aug 2018 12:50:11 +0100
Source: txtorcon
Binary: python3-txtorcon python-txtorcon-doc
Architecture: source all
Version: 18.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Iain R. Learmonth <irl at debian.org>
Description:
 python-txtorcon-doc - Twisted-based asynchronous Tor control protocol implementation (D
 python3-txtorcon - Twisted-based asynchronous Tor control protocol implementation (P
Closes: 905253
Changes:
 txtorcon (18.0.2-2) unstable; urgency=medium
 .
   * No longer builds a Python 2 package (Closes: #905253)
   * Removes tor from suggests for python-txtorcon-doc
Checksums-Sha1:
 a23e498769e3b1f6067f275b1fa3dc33b7155d5e 2222 txtorcon_18.0.2-2.dsc
 c01ea72ab886661f51f43c5a13189dad97c0b001 7904 txtorcon_18.0.2-2.debian.tar.xz
 c53d6a8fbe5356593c433b349b86abde9f06778b 175616 python-txtorcon-doc_18.0.2-2_all.deb
 79cf6278b1832038b14c9ad5de7e1e78bc08fea7 109680 python3-txtorcon_18.0.2-2_all.deb
 0b91c102e728892995f2e80d04bff6af50f7fb97 9689 txtorcon_18.0.2-2_amd64.buildinfo
Checksums-Sha256:
 5aafa6b6631ee42b3cf994f88ee4e460803f13bf7daa0fbbf0ed2ac922cb1fb7 2222 txtorcon_18.0.2-2.dsc
 69896539e9e5c83c719b9ed5ac4e8885b8b0cf490a85762440606ca44140d4b1 7904 txtorcon_18.0.2-2.debian.tar.xz
 8242bdcae1878d01ab40d564918509e46eac675f0ab110821e5f5cf782c996da 175616 python-txtorcon-doc_18.0.2-2_all.deb
 a069c9de924d8e5e1c934a85e9aa1b96d27fc42b1c2c98e6c4681e25794a8d0c 109680 python3-txtorcon_18.0.2-2_all.deb
 10010e27fd7f83d4a80a48ecc8d583a4919c9f595520b03fea402d8b66b0896f 9689 txtorcon_18.0.2-2_amd64.buildinfo
Files:
 3b352a688d92827d6b0979ed23324108 2222 python optional txtorcon_18.0.2-2.dsc
 c8c5a0d146504171d851c53f52800680 7904 python optional txtorcon_18.0.2-2.debian.tar.xz
 ee51eb72257a206d69e11b439857e733 175616 doc optional python-txtorcon-doc_18.0.2-2_all.deb
 91624097c3dca6950be1f8eb97c86226 109680 python optional python3-txtorcon_18.0.2-2_all.deb
 c40adcf08fe165d04fa07822af3e4887 9689 python optional txtorcon_18.0.2-2_amd64.buildinfo

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

iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAlt1ZxQACgkQF4mIfdjV
vF3/mxAAxH1Dfm3yKk9yXrmFPVV/sJDh//p52oXSS5mF6TmpIhrxkJ6od/xmQosz
JVIGvI+QswYyajTGkP65IfFoJErdug+/i8THKYMVhuFo20eclrGBVuUEBt3kVjIV
St/YnXRI3VGWZN37bOYPHeHdiqKxWGfE9RNObqigrW0e6Fmr/Sw02UD7+5ccXLt0
3T+5Khs5/a+027ochXl8CukoU+Qqlzpss5w7BAQYpNjbbISBIOOjEsMwmqsbutSc
mANNSmnkbEKZDCn1RqVyv//VVJUFJv9vn2D4gk/HmNWIzc1LNsrErCCFY9KGP6gq
NiPgEQZL8xDVGr4vP7kfjXvD0hk7IAw4gPghmyond/zl7kTQXy0rBMPGsPZPIuWX
q4z25hhHBMFEWB5gG8QDgc9pAihBtitnptJ+SC5oIbKQZWEEmeLY7+OfFzCWf3EU
WRBXi/qkpVZ2IzWlTTCHVuWuO/uFnDu0OY/g+ThqEECNQ+XYWdMEXbSqydgAuDjx
hK3Q6NsFV4BHeIITq3HfHrI3jgmZ84Q8jYWWgC7Pg7dA8ZTAzKjbscDPzJdXZvwL
/OGkl/VykxfbApWBxN62eUcmAO87+NJ+UVyW6iJNapmynQHz7y01eVCVHiEdfF/y
vhmbMMz1HugFZXN0SglI6a7Fx470WbvvybD/m+ZTTQsuesQjvys=
=oSxX
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Thu Aug 16 13:21:04 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 16 Aug 2018 12:21:04 +0000
Subject: [Pkg-privacy-maintainers] Bug#905253: marked as done
 (python-txtorcon: fails to install with Python 3.7)
References: <E1fqHFk-000FAT-Rw@fasolo.debian.org>
 <153319015352.19202.3797577197478307432.reportbug@zam581.zam.kfa-juelich.de>
Message-ID: <handler.905253.D905253.15344219915246.ackdone@bugs.debian.org>

Your message dated Thu, 16 Aug 2018 12:19:48 +0000
with message-id <E1fqHFk-000FAT-Rw at fasolo.debian.org>
and subject line Bug#905253: fixed in txtorcon 18.0.2-2
has caused the Debian Bug report #905253,
regarding python-txtorcon: fails to install with Python 3.7
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 at bugs.debian.org
immediately.)


-- 
905253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905253
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Andreas Beckmann <anbe at debian.org>
Subject: python-txtorcon: fails to install with Python 3.7
Date: Thu, 02 Aug 2018 08:09:13 +0200
Size: 16615
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180816/ef0b7c5d/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: irl at debian.org (Iain R. Learmonth)
Subject: Bug#905253: fixed in txtorcon 18.0.2-2
Date: Thu, 16 Aug 2018 12:19:48 +0000
Size: 5938
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180816/ef0b7c5d/attachment-0003.mht>

From ftpmaster at ftp-master.debian.org  Thu Aug 16 14:03:13 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 16 Aug 2018 13:03:13 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 vanguards_0.2.1-1_amd64.changes
Message-ID: <E1fqHvl-00022x-Fq@usper.debian.org>

vanguards_0.2.1-1_amd64.changes uploaded successfully to localhost
along with the files:
  vanguards_0.2.1-1.dsc
  vanguards_0.2.1.orig.tar.gz
  vanguards_0.2.1-1.debian.tar.xz
  vanguards_0.2.1-1_all.deb
  vanguards_0.2.1-1_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Thu Aug 16 14:04:28 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 16 Aug 2018 13:04:28 +0000
Subject: [Pkg-privacy-maintainers] vanguards_0.2.1-1_amd64.changes ACCEPTED
 into unstable
Message-ID: <E1fqHwy-0002y2-ER@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Thu, 16 Aug 2018 13:44:29 +0100
Source: vanguards
Binary: vanguards
Architecture: source all
Version: 0.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Iain R. Learmonth <irl at debian.org>
Description:
 vanguards  - Additional protections for Tor Onion Services
Changes:
 vanguards (0.2.1-1) unstable; urgency=medium
 .
   * New upstream version 0.2.1.
   * Now uses manpage included upstream instead of a Debian specific one.
   * Installs new technical and security READMEs
   * Adds pypy-ipaddress as a new build dependency
Checksums-Sha1:
 c1f5f8a75eca4913ebb5ef3670e18df43e61e531 2024 vanguards_0.2.1-1.dsc
 6dce801861986510ca28640e6f7554e7b52189f7 927935 vanguards_0.2.1.orig.tar.gz
 04bcc6839472531a71993db7c184289edd7d0859 2852 vanguards_0.2.1-1.debian.tar.xz
 716e1fbb726ea8759838c76fd5485f3c33090962 35508 vanguards_0.2.1-1_all.deb
 22e6d4e1ad3a226d430b77f56c9d800c2828f2e4 6731 vanguards_0.2.1-1_amd64.buildinfo
Checksums-Sha256:
 05042df00970e16e1bcc191f0968cbab67fb26285d54a5ec607b12da3b8c1c38 2024 vanguards_0.2.1-1.dsc
 c134dbaf0d98d4f6a5704d7bcf6f323795fc2a4831c45c6464f3f26df2ed7ed5 927935 vanguards_0.2.1.orig.tar.gz
 1299899f873a1945c91882f8751c672ce353626b340902816ac17bbd93bcd019 2852 vanguards_0.2.1-1.debian.tar.xz
 6cd2ca422ca23e228a1682fdb0ea3b903bdf1c6d96207726f4c4fd8dd9455a3b 35508 vanguards_0.2.1-1_all.deb
 fb59a73e63d9ced2664a9bfc8ccf7f46c777790783fc8575edef27dd29249f53 6731 vanguards_0.2.1-1_amd64.buildinfo
Files:
 29290c3e30fe730bcc6a4ee6c2e5c22a 2024 net optional vanguards_0.2.1-1.dsc
 713124792f01fa55a24dee72913f4c57 927935 net optional vanguards_0.2.1.orig.tar.gz
 ef91122ac6b14a3a8f3a076eea20798f 2852 net optional vanguards_0.2.1-1.debian.tar.xz
 20d3cc1008befb98645ae72e94ed127c 35508 net optional vanguards_0.2.1-1_all.deb
 1130fdb709919e623e32fb8eafb84183 6731 net optional vanguards_0.2.1-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAlt1c2MACgkQF4mIfdjV
vF3urw/+Lb8TISeYh6yaC0Y9cex/1YAiPQtSvQPIRJDZ+Zm3hZ4/m7tiSuklrNC6
cmPouiBed2ujhYhriZ7LObc2SmK9ThBDVxZjBWDZ9xj07iUEOi1Rz5HbAUmRTPWP
np0c4XMv/c1zPGO19lNtlg2Mle2GFADU4sXAGdb+y1CSg054gsVqCpNWe6nNSOcX
kdyYma/3XfvLMcYmgWu5FEf7NL5fyTHrrcAfFLPTALb7rGP8h+Vqm9/AE83brdFS
SCo4Dz19Ns4SLubeYRmf7UF9CMPTf7PoCDXdqaOR5ETAnONmljOen76nCjDmaIEx
H+2LWV5Wug4KOlieC1lnC72jWgpNxrLNxlGYMJRhb+fgpbJVvEpaxzNqX+JGU24i
MpAtLp94uRlFC8Bk8JBfYDP70i3U3pMSPC4PGqQiHKjcRplLwtv/chaKAt20FNcb
vIe30lp6cdN++QqBTUxlfw11LIqjumi1SQbjZWIl0HZJ6qUryhLG14ccE1VoQ6HG
xt4dl4OW8gOCeXBHPBq78X9tVbgOvCUHSiyLoZQOBbBI5Cqr6s3ICXkqpDTA0EAN
fkOTYw3aDfrdzMsupIaOzOIlABYeMAwgBKpRsgiw2BnS56RxPcjEKgbwwcuuX1HA
x/x6xoPfaWQZPXnOvXMH4EbCMdxGFUU2J32Wb8CUPe/7Kb7GLZI=
=mvhA
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Thu Aug 16 14:58:22 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 16 Aug 2018 13:58:22 +0000
Subject: [Pkg-privacy-maintainers] Processing of sbws_0.6.0-1_amd64.changes
Message-ID: <E1fqIn8-0004tB-0o@usper.debian.org>

sbws_0.6.0-1_amd64.changes uploaded successfully to localhost
along with the files:
  sbws_0.6.0-1.dsc
  sbws_0.6.0.orig.tar.gz
  sbws_0.6.0-1.debian.tar.xz
  sbws-doc_0.6.0-1_all.deb
  sbws_0.6.0-1_all.deb
  sbws_0.6.0-1_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Thu Aug 16 15:36:31 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 16 Aug 2018 14:36:31 +0000
Subject: [Pkg-privacy-maintainers] sbws_0.6.0-1_amd64.changes is NEW
Message-ID: <E1fqJO3-0006nB-6X@fasolo.debian.org>

binary:sbws is NEW.
binary:sbws-doc is NEW.
binary:sbws-doc is NEW.
binary:sbws is NEW.
source:sbws is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
     or https://ftp-master.debian.org/backports-new.html for *-backports


From ulrike at debian.org  Sat Aug 18 09:57:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Sat, 18 Aug 2018 08:57:00 +0000
Subject: [Pkg-privacy-maintainers] Proposal: membership and
 decision-making process
In-Reply-To: <87eff2nukw.fsf@fifthhorseman.net>
References: <85y3dzvm0i.fsf@boum.org> <877eljujba.fsf@fifthhorseman.net>
 <ab78303a-34af-26dc-ebb4-c413a642ee14@451f.org>
 <87wotit2tk.fsf@fifthhorseman.net>
 <11a789ea-90fc-5224-07b3-9d422f45cf82@451f.org>
 <34b0bb19-0fdc-5378-69b0-3d2dccd404d3@debian.org>
 <87eff2nukw.fsf@fifthhorseman.net>
Message-ID: <1477c360-d55b-a7d2-2a76-0e887d33b247@debian.org>

Hi!

Daniel Kahn Gillmor:
> On Sat 2018-08-11 11:53:00 +0000, Ulrike Uhlig wrote:
>> Two weeks have passed. There were no vetos on the proposal, and five
>> approvals. We can thus consider the proposal accepted. Thanks to all who
>> participated in our first team decision process! <3
> 
> congrats, everyone!  thanks for steering us through these waters, Ulrike
> :)

thanks for being there! :)

>> In the future, I suggest we use
>> https://salsa.debian.org/pkg-privacy-team/team-processes/drafts for new
>> proposals, rejected/ for rejected proposals and use the root folder for
>> accepted proposals.
> 
> I like this suggestion for new documents.  As the repo currently says,
> though, that doesn't work as nicely for amending existing documents:
> 
>      Amendments to existing proposals should be made in a dedicated
>      branch and then sent to the mailing list.

I'm unsure if I understand what you are trying to say, sorry. Could you
rephrase this please? Are you saying that making amendments in a branch
is hard? If yes, let's do it differently, in master, and creating an
"amendments" folder? I'd be fine with this. Or just make a merge request
to master like you previously did?

Cheers!
u.


From ulrike at debian.org  Sat Aug 18 10:01:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Sat, 18 Aug 2018 09:01:00 +0000
Subject: [Pkg-privacy-maintainers] Making it known to debian-project? Re:
 Proposal: membership and decision-making process
In-Reply-To: <87eff2nukw.fsf@fifthhorseman.net>
References: <85y3dzvm0i.fsf@boum.org> <877eljujba.fsf@fifthhorseman.net>
 <ab78303a-34af-26dc-ebb4-c413a642ee14@451f.org>
 <87wotit2tk.fsf@fifthhorseman.net>
 <11a789ea-90fc-5224-07b3-9d422f45cf82@451f.org>
 <34b0bb19-0fdc-5378-69b0-3d2dccd404d3@debian.org>
 <87eff2nukw.fsf@fifthhorseman.net>
Message-ID: <0a46dfb3-6b00-6a73-8e34-26cddea15d19@debian.org>

Hi!

I was wondering: do you think it's a good idea to make the existence of
this process known to debian-project@? It might be useful for other
teams to adopt such a policy.

Cheers!
u.


From intrigeri at debian.org  Sat Aug 18 19:47:54 2018
From: intrigeri at debian.org (intrigeri)
Date: Sat, 18 Aug 2018 20:47:54 +0200
Subject: [Pkg-privacy-maintainers] Making it known to debian-project?
 Re: Proposal: membership and decision-making process
In-Reply-To: <0a46dfb3-6b00-6a73-8e34-26cddea15d19@debian.org>
References: <85y3dzvm0i.fsf@boum.org> <877eljujba.fsf@fifthhorseman.net>
 <ab78303a-34af-26dc-ebb4-c413a642ee14@451f.org>
 <87wotit2tk.fsf@fifthhorseman.net>
 <11a789ea-90fc-5224-07b3-9d422f45cf82@451f.org>
 <34b0bb19-0fdc-5378-69b0-3d2dccd404d3@debian.org>
 <87eff2nukw.fsf@fifthhorseman.net>
 <0a46dfb3-6b00-6a73-8e34-26cddea15d19@debian.org>
Message-ID: <85pnyftsth.fsf@boum.org>

Ulrike Uhlig:
> I was wondering: do you think it's a good idea to make the existence of
> this process known to debian-project@?

Yes, I'd love to see us do that once we've field-tested this new
policy a bit.

I won't veto if someone wants to share it right now though :)


From noreply at release.debian.org  Tue Aug 21 05:39:13 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Tue, 21 Aug 2018 04:39:13 +0000
Subject: [Pkg-privacy-maintainers] vanguards 0.2.1-1 MIGRATED to testing
Message-ID: <E1fryRl-0003ct-Ch@respighi.debian.org>

FYI: The status of the vanguards source package
in Debian's testing distribution has changed.

  Previous version: 0.1.1+git20180727.67539be-3
  Current version:  0.2.1-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From hefee at debian.org  Mon Aug 27 22:51:05 2018
From: hefee at debian.org (Sandro =?UTF-8?Q?Knau=C3=9F?=)
Date: Mon, 27 Aug 2018 23:51:05 +0200
Subject: [Pkg-privacy-maintainers] Bug#821093: torbrowser should be usable
 as sensible-browser
References: <20160415111820.GA17352@matrix.athome>
Message-ID: <7123774.C8jB764J7W@tuxin>

Hey,

you can use torbrowser-launcher as sensible-browser, if you start torbrowser 
every time with --allow-remote. See [15185] that is the upstream bug.

so first console:
~/.local/share/torbrowser/tbb/x86_64/tor-browser_{LANG}/Browser/start-tor-
browser  --allow-remote https://check.torproject.org/
second console open a new tab:
~/.local/share/torbrowser/tbb/x86_64/tor-browser_{LANG}/Browser/start-tor-
browser --allow-remote https://check.torproject.org/

even --new-window, --new-tab and --detach works like you expected them.

hefee

[15185] https://trac.torproject.org/projects/tor/ticket/15185
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180827/b7679c0b/attachment.sig>

From anarcat at debian.org  Tue Aug 28 03:06:06 2018
From: anarcat at debian.org (Antoine =?UTF-8?Q?Beaupr=C3=A9?=)
Date: Mon, 27 Aug 2018 22:06:06 -0400
Subject: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: Bug#836266:
 Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.
In-Reply-To: <87tw96qw1g.fsf@alice.fifthhorseman.net>
References: <56b2d2d0-6e49-5b36-b3ad-e411ea56a749@lelutin.ca>
 <85k2bdax6l.fsf@boum.org> <87y3ztkkn0.fsf@alice.fifthhorseman.net>
 <85r35jkezm.fsf@boum.org> <20170110191543.2iaq3ydyvi3x6phr@curie.anarc.at>
 <87tw96qw1g.fsf@alice.fifthhorseman.net>
 <147271681970.8046.17334661827976627790.reportbug@melchior.hokkemirin.ddo.jp>
Message-ID: <87efejxn1t.fsf@curie.anarc.at>

On 2017-01-10 18:28:59, Daniel Kahn Gillmor wrote:
> On Tue 2017-01-10 14:15:43 -0500, Antoine Beaupre wrote:
>> As things stand now, I see no choice but to stop using parcimonie, which
>> means:
>>
>>  1. i will not update my keyring in a timely manner anymore, or;
>>  2. i will reveal my keyring social graph to the keyserver and
>>     possible attackers
>>
>> That seems like the opposite of what parcimonie is trying to
>> accomplish.
>
> fwiw, the ideal long-term fix here is that the logic of parcimonie gets
> folded into dirmngr itself, and just works automatically if tor is
> available.
>
> i've got sketches for how this would work if anyone has the time to work
> on it.
>
> Please see https://bugs.gnupg.org/gnupg/issue1827 for more details.

We're now a year and a half later and I've upgraded my box to Debian
Buster. Remembering this issue (and that I had no mechanism for key
refresh still!) I figured I would give it a shot again. So I installed
parcimonie and let it run for a while. It seems to do its thing but it's
hard to tell as I'm not sure if there are logs anywhere.

That said, `use-tor` is still as problematic as it was back in
stretch. As a random example, I tried to search for a key on a
keyserver, and gpg just failed to get anything. The diagnostics are, as
usual, fairly limited, but the error Phil Morrell got is pretty typical:

       Failed to fetch key 6ACBAD6A729326258CF725C6E7519C8D747F00DC: gpg: keyserver receive failed: No data

Since it's not the first time I have had this problem, I have full debug
enabled in dirmngr (hello metadata leakage!). This translate into this
error:

2018-08-27 21:20:17 dirmngr[9652.6] erreur d'accès à « https://193.164.133.100:443/pks/lookup?op=index&options=mr&search=milan%40debian%2Eorg » : état HTTP 502
2018-08-27 21:20:17 dirmngr[9652.6] command 'KS_SEARCH' failed: Pas de données
2018-08-27 21:20:17 dirmngr[9652.6] DBG: chan_6 -> ERR 167772218 Pas de données <Dirmngr>

What's dumb here is that dirmngr doesn't fallback to other
servers. Repeated attempts to search keys will fail with the same
incomprehensible and useless error message. ("HTTP status 502" would
actually be more useful for debugging, for example, along with which
host is responsible - but GnuPG only blesses us only with "no data".) So
the bug in dirmngr here at least is that it doesn't rotate to the next
available server in the pool when failing with tor.

The workaround, as Morrell explained, is to restart dirmngr which
magically picks another host and moves on.

I know this is not Parcimonie's fault. It's gnupg's fault or, more
precisely, dirmngr's, but it seems difficult to change things over
there: this would require rewriting dirmngr's network routines or
reimplementing parcimonie within dirmngr itself.

After spending years fighting with GnuPG at various levels, neither
looks very attractive or accessible to me as a developer right now.

Instead, I've started thinking about what a parcimonie rewrite would
look like, one that would *not* depend on dirmngr (or, in fact, any
specific OpenPGP implementation). If you permit, I would like to use
this space to brainstorm such a design, which can be broken up into the
following step:

 1. build a random list of keys to fetch, idempotently
 2. talk with Tor
 3. fetch keys from a keyserver
 4. validate the keys (!)
 5. reinject in the data store

In details, it would look something like this:

 1. The first step is to enumerate keys. This requires talking to the
    keystore: it can be done with gpg --export but that means a lot of
    data. Parsing the `--list-keys --with-colons` output might be
    mandated here, as much as it hurts me to even think about this. This
    would load a list of fingerprints to refresh. This list should be
    sorted internally, and then copied and shuffled so we have a list of
    keys to iterate over reliably. This process can be repeated after a
    timeout: new keys would be added, sorted, to the sorted list and
    then added in a random location in the shuffled list.

 2. Fetching Tor is not that complicated, and is the cornerstone of this
    program. Talking to it is simply like talking with a SOCKS5 proxy,
    something which Python requests supports since 2.10, if my memory
    serves me right (jessie-backports and above).

 3. Then parcimonie also needs to talk to keyservers: right now it lets
    gnupg do the talking, but this is actually fairly easy as well, as
    HKP was implemented on top of a few HTTP verbs. I have implemented
    such a client in the PGPy library in a few lines of code:

    https://github.com/SecurityInnovation/PGPy/blob/d5e46733df34f14f83bda5ed2bc0bcc13bd971e3/pgpy/types.py#L267

 4. This actually parses the packet as well and this is where things get
    a little more complicated: what's an acceptable response from a
    keyserver?  This is another thing that's delegated to GnuPG right
    now, but it would be interesting to formalize this and (self-?)
    authenticate the key material. Or can we delegate *just* that bit to
    GnuPG?

 5. Then the last step is simply to feed the resulting key material back
    into the keystore, either gpg --import or whatever backend we want
    supported.

All this doesn't seem that complicated to me. The tricky bit is the gate
to keep garbage and hostile keys from going into the keyring. It would
probably be where the rubber meets the road, as there's an incredible
variety of stuff on keyservers. Not that many programs or libraries can
parse this reliably or at all, GnuPG included. PGPy, in particular, is
not very well tooled for this just yet and cannot correctly parse ECC
keys, for example.

I would welcome feedback on how this could be done, or if it's just an
incredibly stupid idea.

Thanks, and sorry for hijacking this thread with such wild ideas. :)

A.

-- 
Rock journalism is people who can't write, interviewing people who can't
talk, in order to provide articles for people who can't read.
                        - Frank Zappa


From anarcat at debian.org  Tue Aug 28 03:50:36 2018
From: anarcat at debian.org (Antoine =?UTF-8?Q?Beaupr=C3=A9?=)
Date: Mon, 27 Aug 2018 22:50:36 -0400
Subject: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: Bug#836266:
 Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.
In-Reply-To: <87efejxn1t.fsf@curie.anarc.at>
References: <56b2d2d0-6e49-5b36-b3ad-e411ea56a749@lelutin.ca>
 <85k2bdax6l.fsf@boum.org> <87y3ztkkn0.fsf@alice.fifthhorseman.net>
 <85r35jkezm.fsf@boum.org> <20170110191543.2iaq3ydyvi3x6phr@curie.anarc.at>
 <87tw96qw1g.fsf@alice.fifthhorseman.net> <87efejxn1t.fsf@curie.anarc.at>
 <147271681970.8046.17334661827976627790.reportbug@melchior.hokkemirin.ddo.jp>
Message-ID: <878t4rxkzn.fsf@curie.anarc.at>

>  4. This actually parses the packet as well and this is where things get
>     a little more complicated: what's an acceptable response from a
>     keyserver?  This is another thing that's delegated to GnuPG right
>     now, but it would be interesting to formalize this and (self-?)
>     authenticate the key material. Or can we delegate *just* that bit to
>     GnuPG?

I guess this whole re-implementation feasibility question can be
summarized as such:

    Is `gpg --import` safe to run against untrusted data? If not, how
    does it differ from `gpg --recv-keys`?

A.

-- 
They say that time changes things, but you actually have to change
them yourself.           - Andy Warhol


From owner at bugs.debian.org  Tue Aug 28 07:42:03 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 28 Aug 2018 06:42:03 +0000
Subject: [Pkg-privacy-maintainers] Processed: your mail
References: <d31bd598-7714-590a-9549-6e5e949f6f5f@451f.org>
Message-ID: <handler.s.C.153543836521740.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> forwarded 821093 https://trac.torproject.org/projects/tor/ticket/15185
Bug #821093 [torbrowser-launcher] torbrowser should be usable as sensible-browser
Set Bug forwarded-to-address to 'https://trac.torproject.org/projects/tor/ticket/15185'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
821093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821093
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From mn at mn.com.ua  Fri Aug 31 12:09:46 2018
From: mn at mn.com.ua (Mykola Nikishov)
Date: Fri, 31 Aug 2018 14:09:46 +0300
Subject: [Pkg-privacy-maintainers] Bug#907685: torbrowser-launcher: No such
 file or directory: '/usr/bin/gpg2': '/usr/bin/gpg2'
Message-ID: <153571378663.17801.10749414193248012947.reportbug@think>

Package: torbrowser-launcher
Version: 0.3.0~dev-1~exp3
Severity: normal

--8<---------------cut here---------------start------------->8---
$ torbrowser-launcher --settings
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.3.0.dev
https://github.com/micahflee/torbrowser-launcher
qt5ct: using qt5ct plugin
Downloading Tor Browser for the first time.
Downloading over Tor
Downloading https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US
inotify_add_watch("/home/user/.config/qt5ct") failed: "No such file or directory"
Latest version: 7.5.6
Downloading https://tor.eff.org/dist/torbrowser/7.5.6/tor-browser-linux64-7.5.6_en-US.tar.xz.asc
Downloading https://tor.eff.org/dist/torbrowser/7.5.6/tor-browser-linux64-7.5.6_en-US.tar.xz
Verifying Signature
Refreshing local keyring...
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 593, in verify
    c.verify(signature=sig, signed_data=signed)
  File "/usr/lib/python3/dist-packages/gpg/core.py", line 490, in verify
    raise errors.BadSignatures(results[1], results=results)
gpg.errors.BadSignatures: A4300A6BC93C0877A4451486D1483FA6C3C07136: Key expired

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 604, in run
    verify()
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 598, in verify
    raise Exception
Exception

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 607, in run
    self.common.refresh_keyring()
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/common.py", line 202, in refresh_keyring
    '--refresh-keys'], stderr=subprocess.PIPE)
  File "/usr/lib/python3.6/subprocess.py", line 709, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.6/subprocess.py", line 1344, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/gpg2': '/usr/bin/gpg2'
--8<---------------cut here---------------end--------------->8---


-- System Information:
Debian Release: buster/sid
  APT prefers stable
  APT policy: (900, 'stable'), (190, 'testing'), (180, 'unstable'), (170, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20180409
ii  libdbus-glib-1-2  0.110-3
ii  python3           3.6.6-1
ii  python3-gpg       1.11.1-1
ii  python3-pyqt5     5.11.2+dfsg-1+b1
ii  python3-requests  2.18.4-2
ii  python3-socks     1.6.5-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.3.9-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.13-8
pn  python-pygame  <none>

-- no debconf information


From mn at mn.com.ua  Fri Aug 31 12:23:01 2018
From: mn at mn.com.ua (Mykola Nikishov)
Date: Fri, 31 Aug 2018 14:23:01 +0300
Subject: [Pkg-privacy-maintainers] Bug#907685: torbrowser-launcher: No such
 file or directory: '/usr/bin/gpg2': '/usr/bin/gpg2'
In-Reply-To: <153571378663.17801.10749414193248012947.reportbug@think> (Mykola
 Nikishov's message of "Fri, 31 Aug 2018 14:09:46 +0300")
References: <153571378663.17801.10749414193248012947.reportbug@think>
 <153571378663.17801.10749414193248012947.reportbug@think>
Message-ID: <87bm9i231m.fsf@mn.com.ua>

Mykola Nikishov <mn at mn.com.ua> writes:

> Package: torbrowser-launcher
> Version: 0.3.0~dev-1~exp3
> Severity: normal

>From the user's PoV, the severity is kind of critical: trying to
reinstall Tor browser with 'torbrowser-launcher --settings' leaves user
without neither new nor old one.

-- 
Mykola
https://manandbytes.git{lab,hub}.io/


From ftpmaster at ftp-master.debian.org  Tue Sep  4 14:00:16 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 04 Sep 2018 13:00:16 +0000
Subject: [Pkg-privacy-maintainers] sbws_0.6.0-1_amd64.changes ACCEPTED into
 unstable, unstable
Message-ID: <E1fxAwK-00009h-9z@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Thu, 16 Aug 2018 14:44:32 +0100
Source: sbws
Binary: sbws sbws-doc
Architecture: source all
Version: 0.6.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: ju xor <ju at riseup.net>
Description:
 sbws       - Simple Bandwidth Scanner for the Tor network
 sbws-doc   - Simple Bandwidth Scanner
Closes: 903977
Changes:
 sbws (0.6.0-1) unstable; urgency=low
 .
   * Initial debian import. Closes: #903977.
Checksums-Sha1:
 2c4639e309d9666285c4e4baf52e06164bc5df4f 2064 sbws_0.6.0-1.dsc
 1ad57bf8d44afc28bf04c2f7dff6f2d612c2ce9c 141246 sbws_0.6.0.orig.tar.gz
 4d0985e8773ed0cd70268e7d194ca27443d6785b 4164 sbws_0.6.0-1.debian.tar.xz
 3c6be91ce65b3dacff9eac61142c6398edf462a4 77564 sbws-doc_0.6.0-1_all.deb
 87d034cefd6a21ad14ff12586854105a425aa577 50788 sbws_0.6.0-1_all.deb
 8f780d133e01cfced6b046738a4a5a7dc95a72a7 7604 sbws_0.6.0-1_amd64.buildinfo
Checksums-Sha256:
 feba5fcac4fd366579c64f55e47ec4cf8f3e5067d43421e07648552b0ce145c1 2064 sbws_0.6.0-1.dsc
 e3eb5cf883ee92547919e07f38ba60219b9c1f1477f2b57828abf1b23e7e8cea 141246 sbws_0.6.0.orig.tar.gz
 765159602e9d99df2bdf6c8fad94e79e3cd1300b9a4f6e4eee79634b774de59d 4164 sbws_0.6.0-1.debian.tar.xz
 3a28f0631dc9bb43bef5fdbfadf76fef9af83c1247518714b54aacca7c588bda 77564 sbws-doc_0.6.0-1_all.deb
 88f0f9f23f23b14d793e94417468dcdf4fb79c33702486f54cff7840f85653ac 50788 sbws_0.6.0-1_all.deb
 79189ab8a27a480decda505724e26ca536bc3a419847966904c4086dde8a867f 7604 sbws_0.6.0-1_amd64.buildinfo
Files:
 786ee5cf16bfadf73bb72b0c199f33aa 2064 net optional sbws_0.6.0-1.dsc
 4e9b52410d9a1228ce4cb7b0ea08ae3d 141246 net optional sbws_0.6.0.orig.tar.gz
 c658f62793f33702266a1812f4c650a6 4164 net optional sbws_0.6.0-1.debian.tar.xz
 83fd5be5bb1984224f43c256bb6c528a 77564 doc optional sbws-doc_0.6.0-1_all.deb
 82db74aeb65ddef7cf67f7291a816860 50788 net optional sbws_0.6.0-1_all.deb
 a2ce0a2c253ef040bfa215763c52b0ca 7604 net optional sbws_0.6.0-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAlt1gMIACgkQF4mIfdjV
vF3HPRAAux/ap6sgz9KFiOtKyFnvtucRzqc19ZNeqiXOln+kJTGo+4GrP1kWimmE
WJ2yrTuNAzA0dwrCeKXh2hAUNiA1zCIPBi+VdWcI34Bo9o2V0wEcZF6KNhzKmSOy
GwB6mDxlfI3YkiEmzoBZivIcgBXcMbRgw4k9RCEmZJeEnNt+A8SS0qP8ksZHEa7J
AtBs8Gc/DJxroTjgVU+n6d0e/N6k5EznFF6e3FdXlNn/xRLxUVIZAw2jASnnEiUo
65oSwQAxGdWks42RamOiPmaVNy2/D6d2BhQ1LtYr7MfOtj/6tnKSDAT/JHB64Rlv
D4pEaS7PrCFeqKc9irwMCkBhP7D1blMiVuboqXcx5cM6puwYR6VqoQSR+FBbJWcm
IGcgbFRE6GQFqON5eTW6jQq8DWSU2yOo+GgOiqbKvhbDBW+76okizka+w660ajX4
IJHNyF9rFBJlYhMYmQA0E/s0wQpl0unYppVn51MEWQMrICzqDfUn6EvwhCF0V3QQ
mchZgQIHR116iRbKjYANgRQ/cwwPAexYaEWjOJ7QMpbwi2SKe9p7kWP+UBEZ2NpN
FIXCx2NlBpXdDroimfMYmaZSFK4xcLunF2AHj2N/Dg/jfemc1EM/QWZeO4dde2MM
NSYYtG96OpfQy7nwQ5f2k7D2sg0BeXEXw5PrTOJ6XeS+dFNQ11A=
=fR71
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From gregoa at debian.org  Wed Sep  5 20:41:03 2018
From: gregoa at debian.org (gregor herrmann)
Date: Wed, 05 Sep 2018 21:41:03 +0200
Subject: [Pkg-privacy-maintainers] Bug#908068: torbrowser-launcher fails
 with torbrowser 8.0
Message-ID: <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>

Package: torbrowser-launcher
Version: 0.2.9-3
Severity: grave
Tags: upstream
Justification: renders package unusable
User: pkg-apparmor-team at lists.alioth.debian.org 
Usertags: buggy-profile

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

Today torbrowser 8.0 was released, and after updating it (from
torbrowser 7.x, started with torbrowser-launcher), the new version
doesn't start:

% torbrowser-launcher           
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.9
https://github.com/micahflee/torbrowser-launcher
Refreshing local keyring...
Keyring refreshed successfully...
  No key updates for key: EF6E286DDA85EA2A4BA7DE684E2C6E8793298290
Launching './Browser/start-tor-browser --detach'...
%


At that point AppArmor says:

Sep  5 21:21:28 jadzia kernel: [1647972.387747] audit: type=1400 audit(1536175288.429:218): apparmor="DENIED" operation="open" profile="torbrowser_firefox" name="/dev/tty" pid=27409 comm="firefox" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0
Sep  5 21:21:28 jadzia kernel: [1647972.389168] audit: type=1400 audit(1536175288.429:219): apparmor="DENIED" operation="exec" profile="torbrowser_firefox" name="/usr/bin/dirname" pid=27410 comm="firefox" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
Sep  5 21:21:28 jadzia kernel: [1647972.389200] audit: type=1400 audit(1536175288.429:220): apparmor="DENIED" operation="open" profile="torbrowser_firefox" name="/usr/bin/dirname" pid=27410 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0


Trying to start the browser manually is not better:

% ~/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/start-tor-browser --verbose
./firefox: line 3: /usr/bin/dirname: Permission denied
./firefox: line 14: /firefox.real: No such file or directory


And AppArmor details:

Sep  5 21:22:36 jadzia kernel: [1648040.572592] audit: type=1400 audit(1536175356.609:221): apparmor="DENIED" operation="open" profile="torbrowser_firefox" name="/dev/tty" pid=28449 comm="firefox" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0
Sep  5 21:22:36 jadzia kernel: [1648040.573203] audit: type=1400 audit(1536175356.609:222): apparmor="DENIED" operation="exec" profile="torbrowser_firefox" name="/usr/bin/dirname" pid=28450 comm="firefox" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
Sep  5 21:22:36 jadzia kernel: [1648040.573224] audit: type=1400 audit(1536175356.609:223): apparmor="DENIED" operation="open" profile="torbrowser_firefox" name="/usr/bin/dirname" pid=28450 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0


Same for the version in experimental (0.3.0~dev-1~exp3).


I suppose this needs "just" some AppArmor tweaks but I was not
successful in the first few tries (it's a bit of a rabbit hole for a
layperson like me, after dirname comes firefox.real, and then
something about libstdc++.so.6 …).


Cheers,
gregor


- -- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20180409
ii  gnupg             2.2.10-1
ii  libdbus-glib-1-2  0.110-3
ii  python            2.7.15-3
ii  python-gtk2       2.24.0-5.1+b1
ii  python-lzma       0.5.3-3.1
pn  python-parsley    <none>
pn  python-psutil     <none>
ii  python-twisted    18.7.0-2
pn  python-txsocksx   <none>

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.3.9-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.13-8
ii  python-pygame  1.9.3+dfsg2-2

- -- no debconf information

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

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAluQMU5fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaWZRAAnSKawPgJyZ6ncZ9V76ANmlWF0i7i4lJH5MBUu83ZvcRppBEXjZHM/RD6
Xqtn8G7qhZKcvswm5nMVbGwep9Afk2+SugWHXBpy2RU365a68zj437uxtaHkfVrl
NP7BWf7o2wSbWeU/vNmCAB7i++BJCM6CZnWY4/gEeJ7/badyr2xVnNzjAKc1wMxh
jWoXnZTf/K/4jgOS55GUDOJrqDTRBugYVoDWT6mlByoiBHmmvj5pdUm9hsMH40BC
+9SETYSV16sNUCmdT1RCjgnq8c2xv08CkcXjV+sv6IrgvP4AcXQ66+mcNbx9a/Ii
mSIWxne4n03BymfPLIOcSptFGafZH55jliTxvkqcZ5KreDLmN76gR+U/3gqmnyFo
gDGyPl64RVyJxgbE1HVAQvgCat+f9JotQ/5PYw/ddzJyrB+u6MN0KvM7nIkToKOi
WNXfCzWZ9gYjESw1fh1LXUm2PVewrMlrPxP/DqRFYeh6kk16w6Q4Y9smD2N+YLzg
Qb3jbFxsTuCVKEsZmxkYhUZFakyPXFVj4EAhCbZ9FEF59QuNQv7fHYtTTxYkX0DC
5QDZs265KueZGHAQbTNEHe1/bOxsoHHyBDvNgOaTDjGtGWFNB/FhYm0ZiFGtFgdE
UMQmVFUf/Q9pn6FVsn4MYT6RxbhX46xyfeqO2o/s0uaS+RlleYI=
=hTCu
-----END PGP SIGNATURE-----

From boklm at mars-attacks.org  Wed Sep  5 23:07:26 2018
From: boklm at mars-attacks.org (Nicolas Vigier)
Date: Thu, 6 Sep 2018 00:07:26 +0200
Subject: [Pkg-privacy-maintainers] Bug#908068: torbrowser-launcher fails
 with torbrowser 8.0
In-Reply-To: <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
References: <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
 <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
Message-ID: <20180905220726.GA7161@mars-attacks.org>

On Wed, 05 Sep 2018, gregor herrmann wrote:

> 
> I suppose this needs "just" some AppArmor tweaks but I was not
> successful in the first few tries (it's a bit of a rabbit hole for a
> layperson like me, after dirname comes firefox.real, and then
> something about libstdc++.so.6 …).

It seems to be caused by this change:
https://gitweb.torproject.org/builders/tor-browser-build.git/commit/?id=5933f5916a68fdafd7103a4800e156a0100c3a6c

In this release the firefox binary has been renamed to firefox.real,
and firefox is now a wrapper script running firefox.real.

Nicolas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180906/a3f6d200/attachment.sig>

From intrigeri at debian.org  Thu Sep  6 12:24:24 2018
From: intrigeri at debian.org (intrigeri)
Date: Thu, 06 Sep 2018 13:24:24 +0200
Subject: [Pkg-privacy-maintainers] Bug#908068: Bug#908068:
 torbrowser-launcher fails with torbrowser 8.0
In-Reply-To: <20180905220726.GA7161@mars-attacks.org>
References: <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
 <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
 <20180905220726.GA7161@mars-attacks.org>
 <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
Message-ID: <851sa6swbb.fsf@boum.org>

I have a fix ready somewhere, not sure I've pushed this to the
upstream Git repo yet. I'll try to fix that upstream by the end of
the week.


From u at 451f.org  Thu Sep  6 13:24:00 2018
From: u at 451f.org (u)
Date: Thu, 06 Sep 2018 12:24:00 +0000
Subject: [Pkg-privacy-maintainers] Bug#908068: Bug#908068:
 torbrowser-launcher fails with torbrowser 8.0
In-Reply-To: <851sa6swbb.fsf@boum.org>
References: <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
 <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
 <20180905220726.GA7161@mars-attacks.org>
 <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
 <851sa6swbb.fsf@boum.org>
 <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
Message-ID: <d511c50e-395d-7000-5820-e279bef2ae5a@451f.org>

Hi!

intrigeri:
> I have a fix ready somewhere, not sure I've pushed this to the
> upstream Git repo yet. I'll try to fix that upstream by the end of
> the week.

thanks, intrigeri.

Ulrike


From breton at cynicmansion.ru  Fri Sep  7 20:48:36 2018
From: breton at cynicmansion.ru (Boris Bobrov)
Date: Fri, 7 Sep 2018 21:48:36 +0200
Subject: [Pkg-privacy-maintainers] Bug#908068: Attempted fix
References: <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
Message-ID: <691783ee-1436-de6f-e2d0-195c99151af1@cynicmansion.ru>

I managed to launch torbrowser by applying intigeri's patch
https://github.com/micahflee/torbrowser-launcher/commit/a67f026cc14c0a52decda0250890ee776a35f8a1
to /etc/apparmor.d/torbrowser.Browser.firefox and restarting apparmor,
but it is still broken - i cannot open any page and view/change any
settings. Screen size is not 1024x768 (which was the default version for
my system) either.

I wonder if there is a way to install version <8.0 until things get fixed.

Here are the first errors:

[Parent 29833, Gecko_IOThread] WARNING: pipe error (47): Connection
reset by peer: file
/var/tmp/build/firefox-124fa904c4b2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 353

###!!! [Parent][MessageChannel] Error:
(msgtype=0x2C0056,name=PContent::Msg_RefreshScreens) Channel error:
cannot send/recv


###!!! [Parent][MessageChannel] Error:
(msgtype=0x2C0036,name=PContent::Msg_SetXPCOMProcessAttributes) Channel
error: cannot send/recv


###!!! [Parent][MessageChannel] Error:
(msgtype=0x2C0018,name=PContent::Msg_RegisterChrome) Channel error:
cannot send/recv


From breton at cynicmansion.ru  Fri Sep  7 22:00:52 2018
From: breton at cynicmansion.ru (Boris Bobrov)
Date: Fri, 7 Sep 2018 23:00:52 +0200
Subject: [Pkg-privacy-maintainers] Bug#908068: Attempted fix 2
References: <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
Message-ID: <a3adbc22-9c91-7594-2ef2-d965208eec75@cynicmansion.ru>

Pull request https://github.com/micahflee/torbrowser-launcher/pull/343
is required to make it run. After i applied the change, everything
worked for me.


From rosh at debian.org  Sat Sep  8 16:22:18 2018
From: rosh at debian.org (Roger Shimizu)
Date: Sun, 9 Sep 2018 00:22:18 +0900
Subject: [Pkg-privacy-maintainers] Bug#908068: Bug#908068:
 torbrowser-launcher fails with torbrowser 8.0
In-Reply-To: <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
References: <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
 <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
Message-ID: <CAEQ9gEn8T2_ChRqBbaR658YLf5FZ_D-kdQpdQrobAg1nNvwFdw@mail.gmail.com>

On Thu, Sep 6, 2018 at 4:41 AM, gregor herrmann <gregoa at debian.org> wrote:
> Package: torbrowser-launcher
> Version: 0.2.9-3
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
> User: pkg-apparmor-team at lists.alioth.debian.org
> Usertags: buggy-profile
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Today torbrowser 8.0 was released, and after updating it (from
> torbrowser 7.x, started with torbrowser-launcher), the new version
> doesn't start:

thanks for your report!
have you tried experimental version [1]? It's working in my
environment without any patch or hack.

[1] https://wiki.debian.org/TorBrowser#Debian_.22experimental.22

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


From gregoa at debian.org  Sat Sep  8 18:06:39 2018
From: gregoa at debian.org (gregor herrmann)
Date: Sat, 8 Sep 2018 19:06:39 +0200
Subject: [Pkg-privacy-maintainers] Bug#908068: Bug#908068:
 torbrowser-launcher fails with torbrowser 8.0
In-Reply-To: <CAEQ9gEn8T2_ChRqBbaR658YLf5FZ_D-kdQpdQrobAg1nNvwFdw@mail.gmail.com>
References: <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
 <CAEQ9gEn8T2_ChRqBbaR658YLf5FZ_D-kdQpdQrobAg1nNvwFdw@mail.gmail.com>
 <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
Message-ID: <20180908170639.GT8798@jadzia.comodo.priv.at>

On Sun, 09 Sep 2018 00:22:18 +0900, Roger Shimizu wrote:

> > Today torbrowser 8.0 was released, and after updating it (from
> > torbrowser 7.x, started with torbrowser-launcher), the new version
> > doesn't start:
> 
> thanks for your report!
> have you tried experimental version [1]? It's working in my
> environment without any patch or hack.

Quoting my original bug report:

| Same for the version in experimental (0.3.0~dev-1~exp3).


But it looks like the necessary patches are already upstream, so this
should be sorted out soon.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Bettina Wegner: s dremlen fejgel ofj di zwajgn
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180908/8a022f17/attachment.sig>

From shirishag75 at gmail.com  Sun Sep  9 08:31:37 2018
From: shirishag75 at gmail.com (shirish =?UTF-8?Q?=E0=A4=B6=E0=A4=BF=E0=A4=B0=E0=A5=80=E0=A4=B7?=)
Date: Sun, 9 Sep 2018 13:01:37 +0530
Subject: [Pkg-privacy-maintainers] Bug#908068: The apparmor issue is also
 documented while upgrading to the experimental version,
 hope it gets fixed too.
References: <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
Message-ID: <CADdDZRnuffzB7sNWhLNFC5Eky4vS7vFGZbGZYZUqv4h9n9hkcA@mail.gmail.com>

Dear all,

Sorry for adding more noise to the report but got the same thing at my end -

first there is -

 torbrowser-launcher
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.9-3
https://github.com/micahflee/torbrowser-launcher
Launching './Browser/start-tor-browser --detach'...

Because the process detaches wasn't able to figure out what was going wrong.

Then while installing the experimental version got the same issue and
saw the bug-report.

Saw that adequate also calls out apparmor obsolete conffiles and
removes bunch of python2 libraries (python2 twisted libraries I had to
manually purge from the system ) .

$ sudo aptitude install torbrowser-launcher=0.3.0~dev-1~exp3 -y
The following NEW packages will be installed:
  python3-socks{a}
The following packages will be REMOVED:
  python-attr{u} python-automat{u} python-click{u} python-colorama{u}
python-constantly{u} python-gobject-2{u}
  python-gtk2{u} python-hyperlink{u} python-incremental{u}
python-lzma{u} python-numpy{u} python-pam{u}
  python-parsley{u} python-psutil{u} python-pyasn1-modules{u}
python-serial{u} python-service-identity{u}
  python-twisted{u} python-twisted-bin{u} python-twisted-core{u}
python-txsocksx{u} python-zope.interface{u}
The following packages will be upgraded:
  torbrowser-launcher
1 packages upgraded, 1 newly installed, 22 to remove and 0 not upgraded.
Need to get 82.4 kB of archives. After unpacking 32.9 MB will be freed.
Get: 1 http://cdn-fastly.deb.debian.org/debian buster/main amd64
python3-socks all 1.6.5-1 [18.2 kB]
Get: 2 http://cdn-fastly.deb.debian.org/debian experimental/contrib
amd64 torbrowser-launcher amd64 0.3.0~dev-1~exp3 [64.2 kB]
Fetched 82.4 kB in 21s (3,855 B/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
apt-listchanges: Mailing root: apt-listchanges: changelogs for debian
Selecting previously unselected package python3-socks.
(Reading database ... xxxxxx files and directories currently installed.)
Preparing to unpack .../python3-socks_1.6.5-1_all.deb ...
Unpacking python3-socks (1.6.5-1) ...
dpkg: python-twisted-core: dependency problems, but removing anyway as
you requested:
 python-twisted depends on python-twisted-core (>= 18.7.0-2).

(Reading database ... xxxxxxx files and directories currently installed.)
Removing python-twisted-core (18.7.0-2) ...
dpkg: python-txsocksx: dependency problems, but removing anyway as you
requested:
 torbrowser-launcher depends on python-txsocksx (>= 1.13.0.1).

Removing python-txsocksx (1.15.0.2-1) ...
dpkg: python-twisted: dependency problems, but removing anyway as you requested:
 torbrowser-launcher depends on python-twisted.

Removing python-twisted (18.7.0-2) ...
(Reading database ... xxxxxx files and directories currently installed.)
Preparing to unpack .../torbrowser-launcher_0.3.0~dev-1~exp3_amd64.deb ...
Unpacking torbrowser-launcher (0.3.0~dev-1~exp3) over (0.2.9-3) ...
(Reading database ... xxxxxx files and directories currently installed.)
Removing python-service-identity (16.0.0-2) ...
Removing python-automat (0.6.0-1) ...
Removing python-click (6.7+git20180829-1) ...
Removing python-colorama (0.3.7-1) ...
Removing python-constantly (15.1.0-1) ...
Removing python-gtk2 (2.24.0-5.1+b1) ...
Removing python-gobject-2 (2.28.6-13+b1) ...
Removing python-hyperlink (17.3.1-2) ...
Removing python-incremental (16.10.1-3) ...
Removing python-lzma (0.5.3-3.1) ...
Removing python-numpy (1:1.14.5-1+b1) ...
Removing python-pam (0.4.2-13.2) ...
Removing python-parsley (1.2-1) ...
Removing python-psutil (5.4.6-1+b1) ...
Removing python-pyasn1-modules (0.2.1-0.2) ...
Removing python-serial (3.4-4) ...
Removing python-twisted-bin:amd64 (18.7.0-2) ...
Removing python-zope.interface (4.3.2-1+b2) ...
Removing python-attr (17.4.0-2) ...
Setting up python3-socks (1.6.5-1) ...
Processing triggers for mime-support (3.61) ...
Processing triggers for desktop-file-utils (0.23-3) ...
Processing triggers for menu (2.1.47+b1) ...
Setting up torbrowser-launcher (0.3.0~dev-1~exp3) ...
Processing triggers for libc-bin (2.27-5) ...
Processing triggers for man-db (2.8.4-2) ...
adequate found packaging bugs
-----------------------------

torbrowser-launcher: obsolete-conffile
/etc/apparmor.d/local/torbrowser.Browser.firefox
torbrowser-launcher: obsolete-conffile
/etc/apparmor.d/local/torbrowser.Browser.plugin-container
torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Tor.tor

======  How can you help?  (doc: https://wiki.debian.org/how-can-i-help ) ======

As shared hopefully there will be a fix both in buster/unstable and
hopefully experimental (unless that is planned to moved to
unstable/buster.)

Anyways, look forward to the fix.

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8


From ftpmaster at ftp-master.debian.org  Sun Sep  9 08:45:18 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 09 Sep 2018 07:45:18 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.2.9-4_source.changes
Message-ID: <E1fyuPG-0001t2-LO@usper.debian.org>

torbrowser-launcher_0.2.9-4_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.2.9-4.dsc
  torbrowser-launcher_0.2.9-4.debian.tar.xz
  torbrowser-launcher_0.2.9-4_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sun Sep  9 08:49:20 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 09 Sep 2018 07:49:20 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.2.9-4_source.changes ACCEPTED into unstable
Message-ID: <E1fyuTA-0000BD-LB@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sun, 09 Sep 2018 16:43:19 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.2.9-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Closes: 908068
Changes:
 torbrowser-launcher (0.2.9-4) unstable; urgency=medium
 .
   [ Ulrike Uhlig ]
   * debian/control:
     - Remove myself from uploaders.
 .
   [ Roger Shimizu ]
   * debian/patches:
     - Cherry-pick two upstream commits to fix appamor profile for
       Tor Browser 8.0a9 (Closes: #908068).
Checksums-Sha1:
 40d437626f25db51ef869810b275b9a15592a04d 2202 torbrowser-launcher_0.2.9-4.dsc
 6dc4e79cdb63006ea576b95fb1eefceb4f947167 14196 torbrowser-launcher_0.2.9-4.debian.tar.xz
 51015f7e18f6b0c8b52a28718a289176b5370abe 6444 torbrowser-launcher_0.2.9-4_source.buildinfo
Checksums-Sha256:
 ea948827a8f2f63efdc95d0d0eda9323dc4ecc4c84cef7e245f540d3fcc660d6 2202 torbrowser-launcher_0.2.9-4.dsc
 b9f141776893089b2795ad332a0fd4cf7783adae3bea01f6145ffd3ffa61e3f8 14196 torbrowser-launcher_0.2.9-4.debian.tar.xz
 0fb000c556707e31f53a34c15af6a552b74216df7444502ff79eaea3c182a35c 6444 torbrowser-launcher_0.2.9-4_source.buildinfo
Files:
 b613ababb56c65f2ce4ecc7bae18a9dd 2202 contrib/web optional torbrowser-launcher_0.2.9-4.dsc
 7f2f2ebcb100dd46fcdff4d61a574762 14196 contrib/web optional torbrowser-launcher_0.2.9-4.debian.tar.xz
 1180ce0d43e71faacd70e10bd3271f02 6444 contrib/web optional torbrowser-launcher_0.2.9-4_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluUz1QQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qG92D/wJISfNm44R1v3mZwP919JPrM7WpqaxTfoC
laRZEJ/OmkOs6YOye17C2ysaoGjI0SbXr7YM5A+bNhBqDDUoyD1XxhlzF4ZjAxAb
RnzBF0LaBU4GnOlDCFDf7oSZbV2VoYYOE+eSN8CgGsifnMvNTEFqf99cWNkslpKC
k5HADpN6cImG00BtmBixiIa4SzjiJL3LpbQA9S/bKVgSJdL2ZG9pzkfn0CVf/ahK
0ggsgZU4KEVH2voQwIKWj0CpA/FygDPykrdaKo2mlhJnaL9AhxFhHzcMwyiVVfNi
bbGQR389CzUmrlD+d9Lo3ils4w3NtaFjYQYNy1WyOjIiIx5oo0Lq/WqtWgGS3ff8
6PvbZQURC5vm47KNEqq/lDDxQpQczWJ/gu1v6ceLC29kuve5AsUAXV2E3iLvDSFJ
TRKA5yXfe4hRmjuBqcbSNrcBJyQzCrrPTiIJHt0Bv4BOEKwI9VxspPU1n2gHKU77
knm/XSCzRTOBACwo2MYRch+PfCfsxsUTW/we4fk67w/dOd2h/RRFr4R0mPAg5pAR
Ig012uHwch2tszT9Uhkb/NwZSp9yu79PtFndH25xfQEv66RpDgyOwuUMdHKez8DD
ZJcPFN7kRO1jksSanwl9fIK4PPhA95G7H0kcDEkQsxPHxHVg4FqMc9WvFK00uReO
vkmwA0h/Ww==
=coEi
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Sun Sep  9 08:51:06 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sun, 09 Sep 2018 07:51:06 +0000
Subject: [Pkg-privacy-maintainers] Bug#908068: marked as done
 (torbrowser-launcher fails with torbrowser 8.0)
References: <E1fyuTA-0000BP-Nl@fasolo.debian.org>
 <153617646309.22096.3973249441722145070.reportbug@jadzia.comodo.priv.at>
Message-ID: <handler.908068.D908068.153647937213394.ackdone@bugs.debian.org>

Your message dated Sun, 09 Sep 2018 07:49:20 +0000
with message-id <E1fyuTA-0000BP-Nl at fasolo.debian.org>
and subject line Bug#908068: fixed in torbrowser-launcher 0.2.9-4
has caused the Debian Bug report #908068,
regarding torbrowser-launcher fails with torbrowser 8.0
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 at bugs.debian.org
immediately.)


-- 
908068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908068
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: gregor herrmann <gregoa at debian.org>
Subject: torbrowser-launcher fails with torbrowser 8.0
Date: Wed, 05 Sep 2018 21:41:03 +0200
Size: 8728
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180909/8305644c/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Bug#908068: fixed in torbrowser-launcher 0.2.9-4
Date: Sun, 09 Sep 2018 07:49:20 +0000
Size: 5572
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180909/8305644c/attachment-0001.mht>

From ftpmaster at ftp-master.debian.org  Sun Sep  9 15:52:13 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 09 Sep 2018 14:52:13 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.2.9-4~bpo9+1_source.changes
Message-ID: <E1fz14P-0000h5-W0@usper.debian.org>

torbrowser-launcher_0.2.9-4~bpo9+1_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.2.9-4~bpo9+1.dsc
  torbrowser-launcher_0.2.9-4~bpo9+1.debian.tar.xz
  torbrowser-launcher_0.2.9-4~bpo9+1_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sun Sep  9 15:57:14 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 09 Sep 2018 14:57:14 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.2.9-4~bpo8+1_amd64.changes
Message-ID: <E1fz19G-0000xZ-BW@usper.debian.org>

torbrowser-launcher_0.2.9-4~bpo8+1_amd64.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.2.9-4~bpo8+1.dsc
  torbrowser-launcher_0.2.9-4~bpo8+1.debian.tar.xz
  torbrowser-launcher_0.2.9-4~bpo8+1_amd64.deb

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sun Sep  9 16:04:27 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 09 Sep 2018 15:04:27 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.2.9-4~bpo8+1_amd64.changes ACCEPTED into
 jessie-backports-sloppy
Message-ID: <E1fz1GF-0002Br-Ev@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sun, 09 Sep 2018 23:53:39 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source amd64
Version: 0.2.9-4~bpo8+1
Distribution: jessie-backports-sloppy
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.2.9-4~bpo8+1) jessie-backports-sloppy; urgency=medium
 .
   * Rebuild for jessie-backports-sloppy.
Checksums-Sha1:
 8fc4fa1b75d808df69094e15c7c3b0ad27866d31 2230 torbrowser-launcher_0.2.9-4~bpo8+1.dsc
 ed784ffc48ab4a3e314fa2c3bd4274e2b254ce61 14240 torbrowser-launcher_0.2.9-4~bpo8+1.debian.tar.xz
 53a41d6748e366a7fe7fcbf63e21bb6075c5e0b2 224650 torbrowser-launcher_0.2.9-4~bpo8+1_amd64.deb
Checksums-Sha256:
 ea2bb8983f2ee060cbe4939176d083d8f55b6e1ae365ae8a46945270ab24bdd4 2230 torbrowser-launcher_0.2.9-4~bpo8+1.dsc
 0139fc17bf5f69a54a524a5d7a6fe40769f76885e39c10d32f35bd0bcd92a766 14240 torbrowser-launcher_0.2.9-4~bpo8+1.debian.tar.xz
 cb4b5b5cdfdbd31398501c26c58b2ad5b395499554340f8eeace303cf02ad466 224650 torbrowser-launcher_0.2.9-4~bpo8+1_amd64.deb
Files:
 4e4ef0f6422ee82d432ecd1efe3b8e02 2230 contrib/web optional torbrowser-launcher_0.2.9-4~bpo8+1.dsc
 b49baf628e05dc83baf1a135f2019831 14240 contrib/web optional torbrowser-launcher_0.2.9-4~bpo8+1.debian.tar.xz
 c7e2ed35561a06ed6cd528439193002e 224650 contrib/web optional torbrowser-launcher_0.2.9-4~bpo8+1_amd64.deb

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluVNKcQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qNdLD/48ZfLrDkaqGVoXbV9xMaCq6GPK9DvSxvBf
mDnrqGwpxotC2ZSwfNuCbAhygAeqyMiICGdAFbAxApy1l1LS0YwIv0jpyZ0oRjEe
XYJq+TJcbJEtxEfpROz2jmvHGL9yQwt9HIEVhunHIlrtFat38hXpKIuTEf3T8ChZ
KP1ZKGeNv0w5Nx7xjN6j8L0Xwj4CcMBM8gp1GD4s8b28mCtke4JZzgsp3iJ+FOmb
ZBQ5TqVrfqCvEehm+fNBI9m/6BnJPCqef1NHtJ+l1uI5xW+ILXzFawmdM1SyQFS2
D24TiDuoYeAOKJFdh5rkkadHalucU8Dqr49uvemUHiq8lAyj+FKDVh4FUIsCevVI
u1tK01DDRg3dZW30axvSWqUTNTKifOcrzVWtY+iIUDy+Y7+XphoIA2SqfeKsfCNh
oCWsjsUewlqbZ3KwajNkRh56n4gjJ5CzfyGJW/D6vefA/qQwEEo5oyfOjy/0m3VB
KAUIn5plyvl7g/vV2wN3OY0Wb2EydCPug9CQ515A4ARVuCNDaEvASs7NlImHlpB0
jpExqxYbZqvcVN6alqKaQiPy+aB3NoOtIHxOSXlqQYaE8GcXScISaW7Uota5Jibs
aLSpxRebFy/Pj23JXZ6qgzUL3q1ejRPdjk/108PHnbKhI8pdVtZuinC1QCeQKW/n
N0crlGFyww==
=pSVA
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Sun Sep  9 16:04:32 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 09 Sep 2018 15:04:32 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.2.9-4~bpo9+1_source.changes ACCEPTED into
 stretch-backports
Message-ID: <E1fz1GK-0002DY-Mq@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sun, 09 Sep 2018 23:38:50 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.2.9-4~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.2.9-4~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
Checksums-Sha1:
 2afa722aef0dd26346b8c50fa633bdf4ab10d179 2230 torbrowser-launcher_0.2.9-4~bpo9+1.dsc
 25516fbdf87d0b2dbccccf3372cf84769315411a 14224 torbrowser-launcher_0.2.9-4~bpo9+1.debian.tar.xz
 19fdaa5849615391021e0031a0920107587e5946 6472 torbrowser-launcher_0.2.9-4~bpo9+1_source.buildinfo
Checksums-Sha256:
 c9bf1a2b01bbc20c439f7f52b163f743ee9caa335574439c63795a2efcba49b6 2230 torbrowser-launcher_0.2.9-4~bpo9+1.dsc
 5bcf429aa894ac1ecde32b8f6d95ca3004d88069c07b9b3f3a1b74965bebf711 14224 torbrowser-launcher_0.2.9-4~bpo9+1.debian.tar.xz
 431cd7f04d9e0a8bfdec86bb681a5316e587523b1f7d01f90431b99460b0a8be 6472 torbrowser-launcher_0.2.9-4~bpo9+1_source.buildinfo
Files:
 aa199cbf2dd383b334dcc6cd5b4706b1 2230 contrib/web optional torbrowser-launcher_0.2.9-4~bpo9+1.dsc
 6596b3cca36566ac03223441ed5d020e 14224 contrib/web optional torbrowser-launcher_0.2.9-4~bpo9+1.debian.tar.xz
 8538eb52ea4ac7fc05f554c3d6267b2a 6472 contrib/web optional torbrowser-launcher_0.2.9-4~bpo9+1_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluVMZ4QHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qKpYD/9kvhJwPlkXn2PDNCwZsc8PMiK9unzGtZ4H
ctfY/pXeD5IYjoaiTiXd5mrV9eGf5tkShYadJyn/J9RlltElbvGtDU+jM71x23va
oyulgCKIA3iC+PkeNkBMnA2kf4e4CyaQrhIi/4jCSrym3K+EFho4AXHOf8Q6unSl
LnAoJMDBSicGQ1bUAAFYUG1V2bMOwnOB2ElWRin+NAJd5MWAEFSd848XID1KhqHT
yALDANYgmt31+Tz5FPeTsSIKBqbszWrmicXHX/iIgTHqmqBq+47oQHQ6Pi5TZ/un
bzRI26nKy/JH5O8a9T6KLZBwrDZ1zwYzlpvvBlJuyZ5soS5Ge3Ko4CiPjPHWPOhe
tGUc6UhJSJHJgvQ5+d5UXjdojGZG3CV8DcumX7K2iXpAiQx1IjljUCANtWNgWbs9
GV+z0Eew8weHnWiOGlE1Pg5Jmwv+YMpuIjBAlmSizSTs+1Taaj+QdsnJaEXOE6HR
BMutUKNoqvbfS6MqwfomLI4nlXmT30dwR18OgCDbuE7luJ5oVPDJ47XwyGsbsSb8
zUl6ttfdD2YiTXiBzL3+H1jfVBF98zMcoP+SLGi9AyTq6kcdHH3nSXwP9gQRu5RW
EDJj1hD2jHasFb+QOD7YhNrXWs3QMzcm5OQmCHX8fP3/++mom4GEiRr49BAFF70I
/EAe+VfZlg==
=kRa6
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Sun Sep  9 18:18:10 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sun, 09 Sep 2018 17:18:10 +0000
Subject: [Pkg-privacy-maintainers] Bug#907685: marked as done
 (torbrowser-launcher: No such file or directory: '/usr/bin/gpg2':
 '/usr/bin/gpg2')
References: <CAEQ9gEkkyDWfUPnkOAp2SCD4mSYzbyuKfs3RocrVM7-+kNo5vg@mail.gmail.com>
 <153571378663.17801.10749414193248012947.reportbug@think>
Message-ID: <handler.907685.D907685.153651338421311.ackdone@bugs.debian.org>

Your message dated Mon, 10 Sep 2018 02:16:06 +0900
with message-id <CAEQ9gEkkyDWfUPnkOAp2SCD4mSYzbyuKfs3RocrVM7-+kNo5vg at mail.gmail.com>
and subject line Re: [Pkg-privacy-maintainers] Bug#907685: torbrowser-launcher: No such file or directory: '/usr/bin/gpg2': '/usr/bin/gpg2'
has caused the Debian Bug report #907685,
regarding torbrowser-launcher: No such file or directory: '/usr/bin/gpg2': '/usr/bin/gpg2'
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 at bugs.debian.org
immediately.)


-- 
907685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907685
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Mykola Nikishov <mn at mn.com.ua>
Subject: torbrowser-launcher: No such file or directory: '/usr/bin/gpg2': '/usr/bin/gpg2'
Date: Fri, 31 Aug 2018 14:09:46 +0300
Size: 4707
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180909/b7de8815/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Re: [Pkg-privacy-maintainers] Bug#907685: torbrowser-launcher: No such file or directory: '/usr/bin/gpg2': '/usr/bin/gpg2'
Date: Mon, 10 Sep 2018 02:16:06 +0900
Size: 5027
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180909/b7de8815/attachment-0001.mht>

From intrigeri at debian.org  Mon Sep 10 08:59:54 2018
From: intrigeri at debian.org (intrigeri at debian.org)
Date: Mon, 10 Sep 2018 09:59:54 +0200
Subject: [Pkg-privacy-maintainers] Bug#908463: torbrowser-launcher: Fails to
 start "Web Content" processes due to outdated AppArmor policy
Message-ID: <85o9d5kcjp.fsf@boum.org>

Package: torbrowser-launcher
Version: 0.2.9-4
Severity: serious
Tags: upstream fixed-upstream

Hi,

I've just pushed to commits to the upstream "develop" branch that fix
Tor Browser 8 for me. Without these, Tor Browser does start but with
e10s enabled, no tab will render as Firefox is not allowed to start
any "Web Content" process.

Cheers,
-- 
intrigeri


From mn at mn.com.ua  Mon Sep 10 10:12:37 2018
From: mn at mn.com.ua (Mykola Nikishov)
Date: Mon, 10 Sep 2018 12:12:37 +0300
Subject: [Pkg-privacy-maintainers] Bug#908473: torbrowser-launcher:
 ValueError: Unknown endpoint type: '127.0.0.1'
Message-ID: <153657075796.21415.10838481070950269388.reportbug@think>

Package: torbrowser-launcher
Version: 0.2.9-3
Severity: normal

--8<---------------cut here---------------start------------->8---
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.9
https://github.com/micahflee/torbrowser-launcher
Refreshing local keyring...
Keyring refreshed successfully...
  No key updates for key: EF6E286DDA85EA2A4BA7DE684E2C6E8793298290
Downloading over Tor
Downloading and installing Tor Browser for the first time.
Downloading https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US
Traceback (most recent call last):
  File "/usr/bin/torbrowser-launcher", line 30, in <module>
    torbrowser_launcher.main()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/__init__.py", line 64, in main
    app = Launcher(common, url_list)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 132, in __init__
    self.build_ui()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 253, in build_ui
    self.start(None)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 262, in start
    self.run_task()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 279, in run_task
    self.download('version check', self.common.paths['version_check_url'], self.common.paths['version_check_file'])
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 464, in download
    torendpoint = clientFromString(reactor, self.common.settings['tor_socks_address'])
  File "/usr/lib/python2.7/dist-packages/twisted/internet/endpoints.py", line 1853, in clientFromString
    getPlugins(IStreamClientEndpointStringParserWithReactor), name
  File "/usr/lib/python2.7/dist-packages/twisted/internet/endpoints.py", line 1456, in _matchPluginToPrefix
    raise ValueError("Unknown endpoint type: '%s'" % (endpointType,))
ValueError: Unknown endpoint type: '127.0.0.1'
--8<---------------cut here---------------end--------------->8---


-- System Information:
Debian Release: buster/sid
  APT prefers stable
  APT policy: (900, 'stable'), (190, 'testing'), (180, 'unstable'), (170, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20180409
ii  gnupg             2.2.10-1
ii  libdbus-glib-1-2  0.110-3
ii  python            2.7.15-3
ii  python-gtk2       2.24.0-5.1+b1
ii  python-lzma       0.5.3-3
ii  python-parsley    1.2-1
ii  python-psutil     5.0.1-1
ii  python-twisted    16.6.0-2
ii  python-txsocksx   1.15.0.2-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.3.9-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.13-8
pn  python-pygame  <none>

-- no debconf information


From anarcat at debian.org  Mon Sep 10 15:43:32 2018
From: anarcat at debian.org (Antoine =?UTF-8?Q?Beaupr=C3=A9?=)
Date: Mon, 10 Sep 2018 10:43:32 -0400
Subject: [Pkg-privacy-maintainers] Bug#908463: Bug#908463:
 torbrowser-launcher: Fails to start "Web Content" processes due to outdated
 AppArmor policy
In-Reply-To: <85o9d5kcjp.fsf@boum.org>
References: <85o9d5kcjp.fsf@boum.org> <85o9d5kcjp.fsf@boum.org>
Message-ID: <871sa1ifaj.fsf@curie.anarc.at>

On 2018-09-10 09:59:54, intrigeri at debian.org wrote:
> Package: torbrowser-launcher
> Version: 0.2.9-4
> Severity: serious
> Tags: upstream fixed-upstream
>
> Hi,
>
> I've just pushed to commits to the upstream "develop" branch that fix
> Tor Browser 8 for me. Without these, Tor Browser does start but with
> e10s enabled, no tab will render as Firefox is not allowed to start
> any "Web Content" process.

I confirm this problem is real. It seems that as soon as anyone tries to
upgrade torbrowser in Debian now it either fails with #908068 (before
launcher upgrade) or this (after launcher upgrade).

Here's the full apparmor log I'm getting:

sep 10 10:30:50 curie audit[19914]: AVC apparmor="DENIED" operation="exec" profile="torbrowser_firefox" name="/usr/bin/lsb_release" pid=19914 comm="firefox.real" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 
sep 10 10:30:51 curie audit[19888]: AVC apparmor="DENIED" operation="open" profile="torbrowser_firefox" name="/usr/share/fontconfig/conf.avail/" pid=19888 comm="firefox.real" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 
sep 10 10:30:51 curie dbus-daemon[2881]: [session uid=1000 pid=2865] Activating service name='org.a11y.Bus' requested by ':1.238' (uid=1000 pid=19888 comm="./firefox.real --class Tor Browser -profile TorBro") 
sep 10 10:30:59 curie audit[19975]: AVC apparmor="DENIED" operation="exec" profile="torbrowser_firefox" name="/home/anarcat/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/firefox.real" pid=19975 comm="Gecko_IOThread" requested_mask="x" denied_mask="x" fsuid=1000 ouid=1000 
sep 10 10:30:59 curie audit[19977]: AVC apparmor="DENIED" operation="exec" profile="torbrowser_firefox" name="/home/anarcat/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/firefox.real" pid=19977 comm="Gecko_IOThread" requested_mask="x" denied_mask="x" fsuid=1000 ouid=1000 
sep 10 10:30:59 curie audit[19979]: AVC apparmor="DENIED" operation="exec" profile="torbrowser_firefox" name="/home/anarcat/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/firefox.real" pid=19979 comm="Gecko_IOThread" requested_mask="x" denied_mask="x" fsuid=1000 ouid=1000 
sep 10 10:30:59 curie audit[19981]: AVC apparmor="DENIED" operation="exec" profile="torbrowser_firefox" name="/home/anarcat/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/firefox.real" pid=19981 comm="Gecko_IOThread" requested_mask="x" denied_mask="x" fsuid=1000 ouid=1000 
sep 10 10:30:59 curie audit[19888]: AVC apparmor="DENIED" operation="open" profile="torbrowser_firefox" name="/var/lib/snapd/desktop/applications/" pid=19888 comm="firefox.real" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 
sep 10 10:30:59 curie audit[19888]: AVC apparmor="DENIED" operation="open" profile="torbrowser_firefox" name="/var/lib/snapd/desktop/applications/mimeinfo.cache" pid=19888 comm="firefox.real" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 
sep 10 10:30:59 curie audit[19888]: AVC apparmor="DENIED" operation="open" profile="torbrowser_firefox" name="/var/lib/snapd/desktop/applications/" pid=19888 comm="firefox.real" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 
sep 10 10:30:59 curie audit[19888]: AVC apparmor="DENIED" operation="open" profile="torbrowser_firefox" name="/var/lib/snapd/desktop/applications/mimeinfo.cache" pid=19888 comm="firefox.real" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 
sep 10 10:31:00 curie audit[19999]: AVC apparmor="DENIED" operation="exec" profile="torbrowser_firefox" name="/home/anarcat/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/firefox.real" pid=19999 comm="Gecko_IOThread" requested_mask="x" denied_mask="x" fsuid=1000 ouid=1000 
sep 10 10:31:00 curie kernel: audit: type=1400 audit(1536589860.289:162): apparmor="DENIED" operation="exec" profile="torbrowser_firefox" name="/home/anarcat/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/Browser/firefox.real" pid=19999 comm="Gecko_IOThread" requested_mask="x" denied_mask="x" fsuid=1000 ouid=1000 

Not sure what's going on with the snapd up there - I'm not using the
Firefox snap, as far as I know (although I did in the past) so that part
of the log is a bit strange. I noticed that my language ("fr") is in the
path to `firefox.real` so I figured this could be an issue. But starting
with a `C.UTF-8` locale crashes torbrowser completely with a "Tor
unexpectedly exited" GUI popup:

    Tor exited during startup. This might be due to an error in your
    torrc file, a bug in Tor or another program on your system, or
    faulty hardware. Until you fix the underlying problem and restart
    Tor, Tor Browser will not start.

I have then tried to reinstall TBL in that locale, without luck - same
error. What is strange is that the installer is still trying to write to
my locale-specific directory:

sep 10 10:37:24 curie audit[19888]: AVC apparmor="DENIED" operation="mkdir" profile="torbrowser_firefox" name="/home/anarcat/.local/share/torbrowser/tbb/x86_64/tor-browser_fr/" pid=19888 comm=53747265616D5472616E7320233232 requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 

A message like this is written to the log every second or so, flooding
logs too, and there's no obvious way to stop this from the terminal or
GUI as the process is running in the background. Only `kill 19888` fixes
that flood and obviously does not return correct behavior.

Disabling the apparmor profiles fix this:

aa-complain torbrowser.Tor.tor
aa-complain torbrowser.Browser.firefox

Unfortunately, my browser bookmarks seem to have been lost after the 8.0
upgrade. But at least things work now.

A.


From gregoa at debian.org  Mon Sep 10 15:58:06 2018
From: gregoa at debian.org (gregor herrmann)
Date: Mon, 10 Sep 2018 16:58:06 +0200
Subject: [Pkg-privacy-maintainers] Bug#908463: Bug#908463:
 torbrowser-launcher: Fails to start "Web Content" processes due to outdated
 AppArmor policy
In-Reply-To: <871sa1ifaj.fsf@curie.anarc.at>
References: <85o9d5kcjp.fsf@boum.org> <85o9d5kcjp.fsf@boum.org>
 <871sa1ifaj.fsf@curie.anarc.at> <85o9d5kcjp.fsf@boum.org>
Message-ID: <20180910145806.GA15929@jadzia.comodo.priv.at>

On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:

> Disabling the apparmor profiles fix this:
> 
> aa-complain torbrowser.Tor.tor
> aa-complain torbrowser.Browser.firefox

After upgrading to 0.2.9-4, adequate complains:

torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Tor.tor
torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container
torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.firefox

After getting rid of them, I have a starting torbrowser again.

Looks like some dpkg-maintscript-helper(1) magic is needed here ...


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Tony Joe White: Don't Over Do It
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180910/7124c82e/attachment.sig>

From anarcat at debian.org  Mon Sep 10 16:17:54 2018
From: anarcat at debian.org (Antoine =?UTF-8?Q?Beaupr=C3=A9?=)
Date: Mon, 10 Sep 2018 11:17:54 -0400
Subject: [Pkg-privacy-maintainers] Bug#908463: Bug#908463:
 torbrowser-launcher: Fails to start "Web Content" processes due to outdated
 AppArmor policy
In-Reply-To: <20180910145806.GA15929@jadzia.comodo.priv.at>
References: <85o9d5kcjp.fsf@boum.org> <85o9d5kcjp.fsf@boum.org>
 <871sa1ifaj.fsf@curie.anarc.at>
 <20180910145806.GA15929@jadzia.comodo.priv.at> <85o9d5kcjp.fsf@boum.org>
Message-ID: <87va7dgz4t.fsf@curie.anarc.at>

On 2018-09-10 16:58:06, gregor herrmann wrote:
> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>
>> Disabling the apparmor profiles fix this:
>> 
>> aa-complain torbrowser.Tor.tor
>> aa-complain torbrowser.Browser.firefox
>
> After upgrading to 0.2.9-4, adequate complains:
>
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Tor.tor
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.firefox
>
> After getting rid of them, I have a starting torbrowser again.

After getting rid of them, apparmor collapses in a pile of error and
fails to start:

sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Browser.firefox in /etc/apparmor.d/torbrowser.Browser.firefox at line 123: Could not open 'local/torbrowser.Browser.firefox' 
sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Browser.plugin-container in /etc/apparmor.d/torbrowser.Browser.plugin-container at line 94: Could not open 'local/torbrowser.Browser.plugin-container' 
sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Tor.tor in /etc/apparmor.d/torbrowser.Tor.tor at line 41: Could not open 'local/torbrowser.Tor.tor' 

I doubt this is a real solution: those files are just empty here and
should not significantly change the AA policy.

A.

-- 
>From the age of uniformity, from the age of solitude, from the age of
Big Brother, from the age of doublethink - greetings!
                        - Winston Smith, 1984


From anarcat at debian.org  Mon Sep 10 16:20:47 2018
From: anarcat at debian.org (Antoine =?UTF-8?Q?Beaupr=C3=A9?=)
Date: Mon, 10 Sep 2018 11:20:47 -0400
Subject: [Pkg-privacy-maintainers] Bug#908463: Bug#908463:
 torbrowser-launcher: Fails to start "Web Content" processes due to outdated
 AppArmor policy
In-Reply-To: <87va7dgz4t.fsf@curie.anarc.at>
References: <85o9d5kcjp.fsf@boum.org> <85o9d5kcjp.fsf@boum.org>
 <871sa1ifaj.fsf@curie.anarc.at>
 <20180910145806.GA15929@jadzia.comodo.priv.at>
 <87va7dgz4t.fsf@curie.anarc.at> <85o9d5kcjp.fsf@boum.org>
Message-ID: <87r2i1gz00.fsf@curie.anarc.at>

On 2018-09-10 11:17:54, Antoine Beaupré wrote:
> On 2018-09-10 16:58:06, gregor herrmann wrote:
>> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>>
>>> Disabling the apparmor profiles fix this:
>>> 
>>> aa-complain torbrowser.Tor.tor
>>> aa-complain torbrowser.Browser.firefox
>>
>> After upgrading to 0.2.9-4, adequate complains:
>>
>> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Tor.tor
>> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container
>> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.firefox
>>
>> After getting rid of them, I have a starting torbrowser again.
>
> After getting rid of them, apparmor collapses in a pile of error and
> fails to start:
>
> sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Browser.firefox in /etc/apparmor.d/torbrowser.Browser.firefox at line 123: Could not open 'local/torbrowser.Browser.firefox' 
> sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Browser.plugin-container in /etc/apparmor.d/torbrowser.Browser.plugin-container at line 94: Could not open 'local/torbrowser.Browser.plugin-container' 
> sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Tor.tor in /etc/apparmor.d/torbrowser.Tor.tor at line 41: Could not open 'local/torbrowser.Tor.tor' 
>
> I doubt this is a real solution: those files are just empty here and
> should not significantly change the AA policy.

Also, I'm getting this while trying to load "plugin-container":

root at curie:/etc/apparmor.d# aa-complain torbrowser.Browser.plugin-container
Setting /etc/apparmor.d/torbrowser.Browser.plugin-container to complain mode.

ERROR: Path doesn't start with / or variable: torbrowser_plugin_container

a.

-- 
Blind respect for authority is the greatest enemy of truth.
                       - Albert Einstein


From gregoa at debian.org  Mon Sep 10 16:22:19 2018
From: gregoa at debian.org (gregor herrmann)
Date: Mon, 10 Sep 2018 17:22:19 +0200
Subject: [Pkg-privacy-maintainers] Bug#908463: Bug#908463:
 torbrowser-launcher: Fails to start "Web Content" processes due to outdated
 AppArmor policy
In-Reply-To: <87va7dgz4t.fsf@curie.anarc.at>
References: <85o9d5kcjp.fsf@boum.org> <85o9d5kcjp.fsf@boum.org>
 <871sa1ifaj.fsf@curie.anarc.at>
 <20180910145806.GA15929@jadzia.comodo.priv.at>
 <87va7dgz4t.fsf@curie.anarc.at> <85o9d5kcjp.fsf@boum.org>
Message-ID: <20180910152219.GZ8798@jadzia.comodo.priv.at>

On Mon, 10 Sep 2018 11:17:54 -0400, Antoine Beaupré wrote:

> > torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Tor.tor
> > torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container
> > torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.firefox
> >
> > After getting rid of them, I have a starting torbrowser again.
> 
> After getting rid of them, apparmor collapses in a pile of error and
> fails to start:

I first aa-disable()d them before rm'ing them.
 
> sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Browser.firefox in /etc/apparmor.d/torbrowser.Browser.firefox at line 123: Could not open 'local/torbrowser.Browser.firefox' 
> sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Browser.plugin-container in /etc/apparmor.d/torbrowser.Browser.plugin-container at line 94: Could not open 'local/torbrowser.Browser.plugin-container' 
> sep 10 11:16:25 curie apparmor[8443]: AppArmor parser error for /etc/apparmor.d/torbrowser.Tor.tor in /etc/apparmor.d/torbrowser.Tor.tor at line 41: Could not open 'local/torbrowser.Tor.tor' 
> 
> I doubt this is a real solution: those files are just empty here and
> should not significantly change the AA policy.

Don't know, just sharing my experience and pointing to a packaging
glitch.

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Bob Dylan: I Shall Be Free
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180910/811fae31/attachment-0001.sig>

From ftpmaster at ftp-master.debian.org  Wed Sep 12 13:36:07 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 12 Sep 2018 12:36:07 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 vanguards_0.2.2-1_amd64.changes
Message-ID: <E1g04NL-0004IM-8n@usper.debian.org>

vanguards_0.2.2-1_amd64.changes uploaded successfully to localhost
along with the files:
  vanguards_0.2.2-1.dsc
  vanguards_0.2.2.orig.tar.gz
  vanguards_0.2.2-1.debian.tar.xz
  vanguards_0.2.2-1_all.deb
  vanguards_0.2.2-1_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Wed Sep 12 13:49:30 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 12 Sep 2018 12:49:30 +0000
Subject: [Pkg-privacy-maintainers] vanguards_0.2.2-1_amd64.changes ACCEPTED
 into unstable
Message-ID: <E1g04aI-0009Um-R0@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Wed, 12 Sep 2018 13:18:10 +0100
Source: vanguards
Binary: vanguards
Architecture: source all
Version: 0.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Iain R. Learmonth <irl at debian.org>
Description:
 vanguards  - Additional protections for Tor Onion Services
Changes:
 vanguards (0.2.2-1) unstable; urgency=medium
 .
   * New upstream version 0.2.2
   * debian/control:
    - Explicitly depend on pypy-ipaddress (for some reason this is not picked
      up in the pypy:Depends)
   * debian/vanguards.service:
    - Restart vanguards if process exits to provide some resilience in the
      face of unforeseen fatal bugs
Checksums-Sha1:
 064f6f0fb415e529c663ed05988c51e61584ee67 2024 vanguards_0.2.2-1.dsc
 b12ae2d58f41848131224a0e91abdfd7bdc24723 928529 vanguards_0.2.2.orig.tar.gz
 3488ea8fb177544387dfb3a9d33935f6cbfc3d5b 2992 vanguards_0.2.2-1.debian.tar.xz
 ee9d4aa63e91475fa65e461d14bab69b91f9d904 36136 vanguards_0.2.2-1_all.deb
 027a2196ef804cdbc88eb3fb5bdf21ab4fe14d19 6731 vanguards_0.2.2-1_amd64.buildinfo
Checksums-Sha256:
 9ed3dd17107d675202cfd754bebccfb83955c1375e66feb122df0d1b2984df42 2024 vanguards_0.2.2-1.dsc
 61de2c249fe889ff1b5ae583b4efe7ccfec0276ebc7d75d33866f351e9651313 928529 vanguards_0.2.2.orig.tar.gz
 65074dfe9197ae52119f481bb6e957fe8b91d64bdfe1632b8531a2065dd451c0 2992 vanguards_0.2.2-1.debian.tar.xz
 9000a92d939d108b60c35d9e3c16e711df83b2e2c148a503bc325dfd1f698235 36136 vanguards_0.2.2-1_all.deb
 60349688bf4af8bc047e16b1221e6a0c8460b357c498d0b796fded507e0656bd 6731 vanguards_0.2.2-1_amd64.buildinfo
Files:
 1686f7cd655f68f50cc4bc3b7f6f1e91 2024 net optional vanguards_0.2.2-1.dsc
 6cc88a31255a87801fc486de68df00ac 928529 net optional vanguards_0.2.2.orig.tar.gz
 50f0f9fcb7e881fccad2cad1d6cdf2fb 2992 net optional vanguards_0.2.2-1.debian.tar.xz
 7ea531cf8ff2cdc04e7dbd1ebcae8d90 36136 net optional vanguards_0.2.2-1_all.deb
 a9d971cbb2cd84b399bae64078ad20ed 6731 net optional vanguards_0.2.2-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAluZBYcACgkQF4mIfdjV
vF3aZxAAwPL+WZ2ueTTMH0x7gr0eERXXmwfS/aReN1LU3/o09vVlVxcGCsVgEjK4
Ka2GKCA1ZYpijJIqwauDV+8CDsk0kO6Y+ww05n5yhma0oJkikS9jdfJMrb/rUBlT
CDJhhsMIy7eKdYe6Ki6uXwFOuGR3nko4B2LLOughk3NyJXfLHUeqiSedaAYRk0zB
hTc4Qrh8n+HCcNtBpOBWoFDie3yafMNmRhmQC0tUDl/7xuIHKCA+dfuHi8H066l4
Xbj5wGOnGGUkvpTIRXgsFUWWoLi8xKIo8Wdix0fRdwzzifBTAiGnMZOvPvJ7omnh
3pYoiInq0spMJ9GbFKb3mj4dZmJT3X7Xw681N+nXq3gRGertpPHBTvqU0FGEsoCL
9NIGMatBl11gev/x0nHnI+9w5VedqzCKPY6wh/dDj8DppypUlr+BWvcICxovNrb0
eWAXQWKV6jEYIDaDmXVCL8O+4mtZp/D9xFDB4XNQRnz+cTpq1IPFgbDLLZcqesPZ
qhyZAMlPrU9OVGYxaIWuyIjLpGueuEgjBvfNBEgL7OeJXjhfJtPv83x6Ylp2RtFJ
H90baoWvNOypwpVEKBrmrmDba9NZQ5aLcsTfSOYRLF9XXqOHOSqrHrl0JLvEFBkG
0yjyR99vVrHOxsDxi+8KMBRZqUuxZH4aD5/I9KmazRsCJCTY1mk=
=BE4M
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Wed Sep 12 16:33:04 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 12 Sep 2018 15:33:04 +0000
Subject: [Pkg-privacy-maintainers] Processed: Re: Bug#908463
References: <CAEQ9gEk3TwQmyDdZVfhQYc54qNG0NuNdjg2-9EbNS8E=-ik8gw@mail.gmail.com>
Message-ID: <handler.s.C.15367662104002.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> found 908463 0.2.9-3
Bug #908463 [torbrowser-launcher] torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy
Marked as found in versions torbrowser-launcher/0.2.9-3.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
908463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908463
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From stefan.esterer at gmail.com  Wed Sep 12 21:35:15 2018
From: stefan.esterer at gmail.com (stefan esterer)
Date: Wed, 12 Sep 2018 22:35:15 +0200
Subject: [Pkg-privacy-maintainers] Bug#908706: torbrowser-launcher: error on
 torbrowser-launcher first install: exceptions.AttributeError: 'NoneType'
 object has no attribute 'bio_read'
Message-ID: <3336504d-415a-3534-b393-2b9b79a1f2af@gmail.com>

Package: torbrowser-launcher
Version: 0.2.9-3
Severity: important

Hi!

After installing the torbrowser-launcher package on my system I tried to
run it as a user it tries to download the tor browser but if fails with
an python exception:

Downloading and installing Tor Browser for the first time.
Downloading
https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US
Latest version: 8.0
Downloading
https://dist.torproject.org/torbrowser/8.0/tor-browser-linux64-8.0_de.tar.xz.asc
Unhandled Error
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line
103, in callWithLogger
    return callWithContext({"system": lp}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line
86, in callWithContext
    return context.call({ILogContext: newCtx}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py",
line 122, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py",
line 85, in callWithContext
    return func(*args,**kw)
--- <exception caught here> ---
  File "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py",
line 614, in _doReadOrWrite
    why = selectable.doRead()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/tcp.py", line
243, in doRead
    return self._dataReceived(data)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/tcp.py", line
249, in _dataReceived
    rval = self.protocol.dataReceived(data)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/endpoints.py",
line 125, in dataReceived
    return self._wrappedProtocol.dataReceived(data)
  File "/usr/lib/python2.7/dist-packages/twisted/protocols/tls.py", line
330, in dataReceived
    self._flushReceiveBIO()
  File "/usr/lib/python2.7/dist-packages/twisted/protocols/tls.py", line
300, in _flushReceiveBIO
    self._flushSendBIO()
  File "/usr/lib/python2.7/dist-packages/twisted/protocols/tls.py", line
252, in _flushSendBIO
    bytes = self._tlsConnection.bio_read(2 ** 15)
exceptions.AttributeError: 'NoneType' object has no attribute 'bio_read'

Downloading
https://dist.torproject.org/torbrowser/8.0/tor-browser-linux64-8.0_de.tar.xz
Verifying Signature
Extracting tor-browser-linux64-8.0_de.tar.xz
Running
/home/stefan/.local/share/torbrowser/tbb/x86_64/tor-browser_de/start-tor-browser.desktop
Launching './Browser/start-tor-browser --detach'...
Unhandled Error
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line
103, in callWithLogger
    return callWithContext({"system": lp}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line
86, in callWithContext
    return context.call({ILogContext: newCtx}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py",
line 122, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py",
line 85, in callWithContext
    return func(*args,**kw)
--- <exception caught here> ---
  File "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py",
line 614, in _doReadOrWrite
    why = selectable.doRead()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/tcp.py", line
243, in doRead
    return self._dataReceived(data)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/tcp.py", line
249, in _dataReceived
    rval = self.protocol.dataReceived(data)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/endpoints.py",
line 125, in dataReceived
    return self._wrappedProtocol.dataReceived(data)
  File "/usr/lib/python2.7/dist-packages/twisted/protocols/tls.py", line
330, in dataReceived
    self._flushReceiveBIO()
  File "/usr/lib/python2.7/dist-packages/twisted/protocols/tls.py", line
300, in _flushReceiveBIO
    self._flushSendBIO()
  File "/usr/lib/python2.7/dist-packages/twisted/protocols/tls.py", line
252, in _flushSendBIO
    bytes = self._tlsConnection.bio_read(2 ** 15)
exceptions.AttributeError: 'NoneType' object has no attribute 'bio_read'

Is there any other information I can provider? Am I am making a mistake?

thx

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8),
LANGUAGE=de_AT:de (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  gnupg             2.2.10-1
ii  libdbus-glib-1-2  0.110-3
ii  python            2.7.15-3
ii  python-gtk2       2.24.0-5.1+b1
ii  python-lzma       0.5.3-3.1
ii  python-parsley    1.2-1
ii  python-psutil     5.4.6-1+b1
ii  python-twisted    18.7.0-2
ii  python-txsocksx   1.15.0.2-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.3.9-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.13-8
pn  python-pygame  <none>

-- no debconf information


From noreply at release.debian.org  Thu Sep 13 05:39:07 2018
From: noreply at release.debian.org (Debian testing autoremoval watch)
Date: Thu, 13 Sep 2018 04:39:07 +0000
Subject: [Pkg-privacy-maintainers] torbrowser-launcher is marked for
 autoremoval from testing
Message-ID: <E1g0JPH-000730-Tt@respighi.debian.org>

torbrowser-launcher 0.2.9-3 is marked for autoremoval from testing on 2018-10-04

It is affected by these RC bugs:
908068: torbrowser-launcher: torbrowser-launcher fails with torbrowser 8.0



From noreply at release.debian.org  Fri Sep 14 05:39:12 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Fri, 14 Sep 2018 04:39:12 +0000
Subject: [Pkg-privacy-maintainers] torbrowser-launcher 0.2.9-4 MIGRATED to
 testing
Message-ID: <E1g0fsu-0006de-6j@respighi.debian.org>

FYI: The status of the torbrowser-launcher source package
in Debian's testing distribution has changed.

  Previous version: 0.2.9-3
  Current version:  0.2.9-4

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From rosh at debian.org  Sat Sep 15 03:01:39 2018
From: rosh at debian.org (Roger Shimizu)
Date: Sat, 15 Sep 2018 11:01:39 +0900
Subject: [Pkg-privacy-maintainers] Bug#908463: Bug#908463:
 torbrowser-launcher: Fails to start "Web Content" processes due to outdated
 AppArmor policy
In-Reply-To: <20180910145806.GA15929@jadzia.comodo.priv.at>
References: <85o9d5kcjp.fsf@boum.org> <871sa1ifaj.fsf@curie.anarc.at>
 <20180910145806.GA15929@jadzia.comodo.priv.at> <85o9d5kcjp.fsf@boum.org>
Message-ID: <CAEQ9gEnb38EtjZqen-vWAgajvDLx6GOCWftTnaD5EbqB_1co4g@mail.gmail.com>

On Mon, Sep 10, 2018 at 11:58 PM, gregor herrmann <gregoa at debian.org> wrote:
> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>
>> Disabling the apparmor profiles fix this:
>>
>> aa-complain torbrowser.Tor.tor
>> aa-complain torbrowser.Browser.firefox
>
> After upgrading to 0.2.9-4, adequate complains:
>
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Tor.tor
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.firefox

Sorry, I don't have these errors when upgrading package.

====
# dpkg -i torbrowser-launcher_0.2.9-4_amd64.deb
(Reading database ... 272719 files and directories currently installed.)
Preparing to unpack torbrowser-launcher_0.2.9-4_amd64.deb ...
Unpacking torbrowser-launcher (0.2.9-4) over (0.2.9-3) ...
Setting up torbrowser-launcher (0.2.9-4) ...
Installing new version of config file
/etc/apparmor.d/torbrowser.Browser.firefox ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for man-db (2.7.6.1-2) ...
====

> After getting rid of them, I have a starting torbrowser again.
>
> Looks like some dpkg-maintscript-helper(1) magic is needed here ...

Could you provide an example, or even patch?
Thanks!

BTW. I have pushed not-released-yet 0.2.9-5 to branch debian/sid on salsa.
Maybe you can simply build the package by git-buildpackage, and test
the latest appamor profile from intrigeri.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


From noreply at release.debian.org  Sat Sep 15 05:39:14 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Sat, 15 Sep 2018 04:39:14 +0000
Subject: [Pkg-privacy-maintainers] sbws 0.6.0-1 MIGRATED to testing
Message-ID: <E1g12MU-000681-Q9@respighi.debian.org>

FYI: The status of the sbws source package
in Debian's testing distribution has changed.

  Previous version: (not in testing)
  Current version:  0.6.0-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From intrigeri at debian.org  Sat Sep 15 06:11:53 2018
From: intrigeri at debian.org (intrigeri)
Date: Sat, 15 Sep 2018 07:11:53 +0200
Subject: [Pkg-privacy-maintainers] Bug#908463: Bug#908463:
 torbrowser-launcher: Fails to start "Web Content" processes due to outdated
 AppArmor policy
In-Reply-To: <CAEQ9gEnb38EtjZqen-vWAgajvDLx6GOCWftTnaD5EbqB_1co4g@mail.gmail.com>
References: <85o9d5kcjp.fsf@boum.org> <871sa1ifaj.fsf@curie.anarc.at>
 <20180910145806.GA15929@jadzia.comodo.priv.at> <85o9d5kcjp.fsf@boum.org>
 <CAEQ9gEnb38EtjZqen-vWAgajvDLx6GOCWftTnaD5EbqB_1co4g@mail.gmail.com>
 <85o9d5kcjp.fsf@boum.org>
Message-ID: <85sh2bqr8m.fsf@boum.org>

Roger Shimizu:
> On Mon, Sep 10, 2018 at 11:58 PM, gregor herrmann <gregoa at debian.org> wrote:
>> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>> After upgrading to 0.2.9-4, adequate complains:
>>
>> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Tor.tor
>> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container
>> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.firefox

> Sorry, I don't have these errors when upgrading package.

To reproduce, I think you need 1. adequate installed;
2. upgrading from a specific version of the package.

Cheers,
-- 
intrigeri


From gregoa at debian.org  Sat Sep 15 18:35:31 2018
From: gregoa at debian.org (gregor herrmann)
Date: Sat, 15 Sep 2018 19:35:31 +0200
Subject: [Pkg-privacy-maintainers] Bug#908463: Bug#908463:
 torbrowser-launcher: Fails to start "Web Content" processes due to outdated
 AppArmor policy
In-Reply-To: <CAEQ9gEnb38EtjZqen-vWAgajvDLx6GOCWftTnaD5EbqB_1co4g@mail.gmail.com>
References: <85o9d5kcjp.fsf@boum.org> <871sa1ifaj.fsf@curie.anarc.at>
 <20180910145806.GA15929@jadzia.comodo.priv.at>
 <CAEQ9gEnb38EtjZqen-vWAgajvDLx6GOCWftTnaD5EbqB_1co4g@mail.gmail.com>
 <85o9d5kcjp.fsf@boum.org>
Message-ID: <20180915173531.GD8747@jadzia.comodo.priv.at>

On Sat, 15 Sep 2018 11:01:39 +0900, Roger Shimizu wrote:

> > After upgrading to 0.2.9-4, adequate complains:
> >
> > torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Tor.tor
> > torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container
> > torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.firefox
> 
> Sorry, I don't have these errors when upgrading package.
> 
> ====
> # dpkg -i torbrowser-launcher_0.2.9-4_amd64.deb
> (Reading database ... 272719 files and directories currently installed.)
> Preparing to unpack torbrowser-launcher_0.2.9-4_amd64.deb ...
> Unpacking torbrowser-launcher (0.2.9-4) over (0.2.9-3) ...
> Setting up torbrowser-launcher (0.2.9-4) ...
> Installing new version of config file
> /etc/apparmor.d/torbrowser.Browser.firefox ...
> Processing triggers for desktop-file-utils (0.23-1) ...
> Processing triggers for mime-support (3.60) ...
> Processing triggers for man-db (2.7.6.1-2) ...
> ====
> 
> > After getting rid of them, I have a starting torbrowser again.
> >
> > Looks like some dpkg-maintscript-helper(1) magic is needed here ...
> 
> Could you provide an example, or even patch?
> Thanks!

After looking at the package/repo:

The files under /etc/apparmor.d/local were created in 0.2.9-1 (with
the upstream import) and were removed in 0.2.9-2, probably with
0016-Remove-apparmor-local-path-from-setup.py.patch. Or maybe with
debian/patches/0015-AppArmor-remove-boilerplate-from-local-override-file.patch.
Or with both :)

This is somewhat confusing but 0.2.9-1 seems to be the only release
with

drwxr-xr-x root/root         0 2018-01-29 15:17 ./etc/apparmor.d/local/
-rw-r--r-- root/root       134 2018-01-28 19:33 ./etc/apparmor.d/local/torbrowser.Browser.firefox
-rw-r--r-- root/root       133 2018-01-28 19:33 ./etc/apparmor.d/local/torbrowser.Browser.plugin-container
-rw-r--r-- root/root       133 2018-01-28 19:33 ./etc/apparmor.d/local/torbrowser.Tor.tor

(That also means that adequate must have warned me earlier?)

Anyway, these conffiles are not shipped any more; either that's a
mistake or they need to be properly removed.

There is already debian/torbrowser-launcher.maintscript which IMO
needs three new lines:

rm_conffile /etc/apparmor.d/local/torbrowser.Tor.tor 0.2.9-2~ torbrowser-launcher
rm_conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container 0.2.9-2~ torbrowser-launcher
rm_conffile /etc/apparmor.d/local/torbrowser.Browser.firefox 0.2.9-2~ torbrowser-launcher

Or maybe s/0.2.9-2~/0.2.9-5~/ , if I'm reading dpkg-maintscript-helper(1)
correctly.

HTH,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Peter Jones: Hooked onto your love
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180915/60eee3e4/attachment.sig>

From noreply at release.debian.org  Mon Sep 17 05:39:16 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Mon, 17 Sep 2018 04:39:16 +0000
Subject: [Pkg-privacy-maintainers] vanguards 0.2.2-1 MIGRATED to testing
Message-ID: <E1g1lJc-00063S-F9@respighi.debian.org>

FYI: The status of the vanguards source package
in Debian's testing distribution has changed.

  Previous version: 0.2.1-1
  Current version:  0.2.2-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From rosh at debian.org  Mon Sep 17 06:17:01 2018
From: rosh at debian.org (Roger Shimizu)
Date: Mon, 17 Sep 2018 14:17:01 +0900
Subject: [Pkg-privacy-maintainers] Bug#908463: Bug#908463:
 torbrowser-launcher: Fails to start "Web Content" processes due to outdated
 AppArmor policy
In-Reply-To: <20180915173531.GD8747@jadzia.comodo.priv.at>
References: <85o9d5kcjp.fsf@boum.org> <871sa1ifaj.fsf@curie.anarc.at>
 <20180910145806.GA15929@jadzia.comodo.priv.at>
 <CAEQ9gEnb38EtjZqen-vWAgajvDLx6GOCWftTnaD5EbqB_1co4g@mail.gmail.com>
 <20180915173531.GD8747@jadzia.comodo.priv.at> <85o9d5kcjp.fsf@boum.org>
Message-ID: <CAEQ9gE=4MqE7z9YGXCrxm+_WreTbQwe2=qLqNEHTybxm_CG6kA@mail.gmail.com>

On Sat, Sep 15, 2018 at 2:11 PM, intrigeri <intrigeri at debian.org> wrote:
> Roger Shimizu:
>> On Mon, Sep 10, 2018 at 11:58 PM, gregor herrmann <gregoa at debian.org> wrote:
>>> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>>> After upgrading to 0.2.9-4, adequate complains:
>>>
>>> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Tor.tor
>>> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container
>>> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.firefox
>
>> Sorry, I don't have these errors when upgrading package.
>
> To reproduce, I think you need 1. adequate installed;
> 2. upgrading from a specific version of the package.

I confirmed I already had adequate installed previously.

$ dpkg -l adequate
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                     Version           Architecture      Description
+++-========================-=================-=================-======================================================
ii  adequate                 0.15.1            all
Debian package quality testing tool

On Sun, Sep 16, 2018 at 2:35 AM, gregor herrmann <gregoa at debian.org> wrote:
>> > After getting rid of them, I have a starting torbrowser again.
>> >
>> > Looks like some dpkg-maintscript-helper(1) magic is needed here ...
>>
>> Could you provide an example, or even patch?
>> Thanks!
>
> After looking at the package/repo:
>
> The files under /etc/apparmor.d/local were created in 0.2.9-1 (with
> the upstream import) and were removed in 0.2.9-2, probably with
> 0016-Remove-apparmor-local-path-from-setup.py.patch. Or maybe with
> debian/patches/0015-AppArmor-remove-boilerplate-from-local-override-file.patch.
> Or with both :)
>
> This is somewhat confusing but 0.2.9-1 seems to be the only release
> with
>
> drwxr-xr-x root/root         0 2018-01-29 15:17 ./etc/apparmor.d/local/
> -rw-r--r-- root/root       134 2018-01-28 19:33 ./etc/apparmor.d/local/torbrowser.Browser.firefox
> -rw-r--r-- root/root       133 2018-01-28 19:33 ./etc/apparmor.d/local/torbrowser.Browser.plugin-container
> -rw-r--r-- root/root       133 2018-01-28 19:33 ./etc/apparmor.d/local/torbrowser.Tor.tor
>
> (That also means that adequate must have warned me earlier?)
>
> Anyway, these conffiles are not shipped any more; either that's a
> mistake or they need to be properly removed.

I tried to install 0.2.9-1 and upgrade to 0.2.9-4, but still didn't reproduced.
I tested it again after enabling adequate by set 'Adequate::Enabled
"true";' in /etc/apt/apt.conf.d/20adequate
But same result.

BTW. Old packages can be found on snapshot.d.o [1].

[1] http://snapshot.debian.org/package/torbrowser-launcher/

====
# dpkg -i torbrowser-launcher_0.2.9-1_amd64.deb
(Reading database ... 272854 files and directories currently installed.)
Preparing to unpack torbrowser-launcher_0.2.9-1_amd64.deb ...
Unpacking torbrowser-launcher (0.2.9-1) over (0.2.9-1) ...
Setting up torbrowser-launcher (0.2.9-1) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for man-db (2.7.6.1-2) ...
# dpkg -i torbrowser-launcher_0.2.9-4_amd64.deb
(Reading database ... 272854 files and directories currently installed.)
Preparing to unpack torbrowser-launcher_0.2.9-4_amd64.deb ...
Unpacking torbrowser-launcher (0.2.9-4) over (0.2.9-1) ...
Setting up torbrowser-launcher (0.2.9-4) ...
Installing new version of config file
/etc/apparmor.d/torbrowser.Browser.firefox ...
Installing new version of config file
/etc/apparmor.d/torbrowser.Browser.plugin-container ...
Installing new version of config file /etc/apparmor.d/torbrowser.Tor.tor ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for man-db (2.7.6.1-2) ...
====

> There is already debian/torbrowser-launcher.maintscript which IMO
> needs three new lines:
>
> rm_conffile /etc/apparmor.d/local/torbrowser.Tor.tor 0.2.9-2~ torbrowser-launcher
> rm_conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container 0.2.9-2~ torbrowser-launcher
> rm_conffile /etc/apparmor.d/local/torbrowser.Browser.firefox 0.2.9-2~ torbrowser-launcher
>
> Or maybe s/0.2.9-2~/0.2.9-5~/ , if I'm reading dpkg-maintscript-helper(1)
> correctly.

Thanks for the hint!
I'll try this snippet.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


From shirishag75 at gmail.com  Mon Sep 17 10:34:19 2018
From: shirishag75 at gmail.com (shirish =?UTF-8?Q?=E0=A4=B6=E0=A4=BF=E0=A4=B0=E0=A5=80=E0=A4=B7?=)
Date: Mon, 17 Sep 2018 15:04:19 +0530
Subject: [Pkg-privacy-maintainers] Bug#908463: can confirm the issue at my
 end as well as the presence of the three conffiles -
References: <85o9d5kcjp.fsf@boum.org>
Message-ID: <CADdDZRnFYMftESCg595_-eGF08efpUHayAoyU4ULdH=THU_YiA@mail.gmail.com>

Dear all,

Unable to do anything on tor either using the experimental or using
the 0.2.9-4 version -

###!!! [Parent][MessageChannel] Error:
(msgtype=0x2C000A,name=PContent::Msg_InitProfiler) Channel error:
cannot send/recv

[Parent 5116, Main Thread] WARNING: FileDescriptorSet destroyed with
unconsumed descriptors: file
/var/tmp/build/firefox-124fa904c4b2/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc,
line 22
[Parent 5116, Gecko_IOThread] WARNING: pipe error: Broken pipe: file
/var/tmp/build/firefox-124fa904c4b2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 709

###!!! [Parent][MessageChannel] Error:
(msgtype=0x2C0055,name=PContent::Msg_SetPermissionsWithKey) Channel
error: cannot send/recv


###!!! [Parent][MessageChannel] Error:
(msgtype=0x2C004E,name=PContent::Msg_GMPsChanged) Channel error:
cannot send/recv

[Parent 5116, Gecko_IOThread] WARNING: pipe error (80): Connection
reset by peer: file
/var/tmp/build/firefox-124fa904c4b2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 353
^CSep 17 09:27:32.000 [notice] Interrupt: exiting cleanly.

The error message goes in to a loop and the same message is kept
repeating till you don't break the cycle with CTRL+C .

As far as apparmor conffiles are concerned, they too are here -

/etc/apparmor.d/local$ ls -l
total 16
-rw-r--r-- 1 root root 1111 Feb 25  2018 README
-rw-r--r-- 1 root root    0 Mar 10  2018 system_tor
-rw-r--r-- 1 root root  134 Jan 29  2018 torbrowser.Browser.firefox
-rw-r--r-- 1 root root  133 Jan 29  2018 torbrowser.Browser.plugin-container
-rw-r--r-- 1 root root  133 Jan 29  2018 torbrowser.Tor.tor


There is also this -

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893695

as well as adequate throws me this about apparmor -

$ adequate apparmor
apparmor: obsolete-conffile /etc/apparmor.d/cache.d/CACHEDIR.TAG

hope it helps in getting torbrowser-launcher fixed.

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8


From ftpmaster at ftp-master.debian.org  Mon Sep 17 17:27:41 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 17 Sep 2018 16:27:41 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.2.9-5_source.changes
Message-ID: <E1g1wNB-0003GU-Eq@usper.debian.org>

torbrowser-launcher_0.2.9-5_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.2.9-5.dsc
  torbrowser-launcher_0.2.9-5.debian.tar.xz
  torbrowser-launcher_0.2.9-5_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Mon Sep 17 17:36:15 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 17 Sep 2018 16:36:15 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.2.9-5_source.changes ACCEPTED into unstable
Message-ID: <E1g1wVT-0002VA-9g@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Tue, 18 Sep 2018 01:17:18 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.2.9-5
Distribution: unstable
Urgency: high
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Closes: 908463
Changes:
 torbrowser-launcher (0.2.9-5) unstable; urgency=high
 .
   * debian/source/lintian-overrides:
     - Rename from debian/source.lintian-overrides
   * debian/control:
     - Rename tag X-Python-Version to XS-Python-Version.
     - Add XB-Python-Version tag for binary package.
   * debian/patches:
     - Cherry-pick three upstream commits to fix appamor profile for
       Web Content process (Closes: #908463).
   * debian/torbrowser-launcher.maintscript:
     - rm_conffile appamor profile /etc/apparmor.d/local/*, which was
       removed since 0.2.9-2. Thanks to gregor herrmann for the fix.
Checksums-Sha1:
 bafd35f3732eded83c09de16fcabeabe16c85f92 2225 torbrowser-launcher_0.2.9-5.dsc
 818d0f1c59459d6de25a1f6ebecb2dc5cb995d52 15060 torbrowser-launcher_0.2.9-5.debian.tar.xz
 f6a46fb86833a0f8ce294dc663645d384161ab4c 6443 torbrowser-launcher_0.2.9-5_source.buildinfo
Checksums-Sha256:
 ec500a5c100bea8c24fb18098d7f17864bef2651108050e744b0aabd565e947a 2225 torbrowser-launcher_0.2.9-5.dsc
 efdca1f997a79991a0457caa15e05cb161279996997f6dfd72dfd588b8c48e3b 15060 torbrowser-launcher_0.2.9-5.debian.tar.xz
 19f4c8f9de8bbc6113e2de02e88fd94359884bd8943b8b74af81329870662410 6443 torbrowser-launcher_0.2.9-5_source.buildinfo
Files:
 7b0fa8f047b15129a00a26b248a3ed4a 2225 contrib/web optional torbrowser-launcher_0.2.9-5.dsc
 c896080d84017812c89610fdba1a5a03 15060 contrib/web optional torbrowser-launcher_0.2.9-5.debian.tar.xz
 4fa2f746504e10180a2f680588f4adcb 6443 contrib/web optional torbrowser-launcher_0.2.9-5_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluf1PkQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qD5wEACUlPzslw4B5OrXSZJooHxrTVmZJ6yzsdbM
RWZw6HfEWFwe0dRhOL8YxWCkoL1mLyY75HeyNILrEXpwlfnYQcvQsl1Ub1gwZzWO
KM0RVLGCWBEuakYxzZkmDUsep737hL1MgUAQ5t8wwV84BqSyU563BMiz4ocjkIHd
0BcYCgUmxCAhO1WDdysITmBad/gOymi5rz2IlT1w+6v73rr+e3JizbpgEhOUp2pc
8vFx9liYiAefGfWg+FNxVpKR4N5rzhJgAJssoX3ha5fthx6SFbJoXo5Pl70WS/p/
foGjLwyUBuKSqtS1yIlKOUYsRpjy5wkkDHHMy2chaOoYYSG+Ia6Gr1NX/EWYqDyK
bLjKvYH9GE04oci+7nZ99Z1oCTZqbfwHPpMVpfCoXJOr6/zkH3LqXZSCnO4e+J5e
fEcvm6ernyygfAHIJvYGWAhCVfLMjyZOoy59OAblaG9uLTRm62WIn9nMt4o3Bvpx
4+N1lS1AFn481XTI/vFETa/IeY39Ck28UVBq6WaQhbmEo072RrjksWeqFDAmZGhc
IHj4bZbTMcnYTwIMCRiIY0ZnBHDIgpHMa/FQ2GxRpPvriABFmO3Ew07uTml3HQDZ
w/KbPzBzxpk3eJhglu14PNS/FNGkdG/+6Rfqmz1RNhk8Zs9bfE1VrXZZpQL1R66+
L4YBw5S8Hw==
=JBXO
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Mon Sep 17 17:39:05 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 17 Sep 2018 16:39:05 +0000
Subject: [Pkg-privacy-maintainers] Bug#908463: marked as done
 (torbrowser-launcher: Fails to start "Web Content" processes due to
 outdated AppArmor policy)
References: <E1g1wVT-0002VK-C1@fasolo.debian.org> <85o9d5kcjp.fsf@boum.org>
Message-ID: <handler.908463.D908463.153720217720830.ackdone@bugs.debian.org>

Your message dated Mon, 17 Sep 2018 16:36:15 +0000
with message-id <E1g1wVT-0002VK-C1 at fasolo.debian.org>
and subject line Bug#908463: fixed in torbrowser-launcher 0.2.9-5
has caused the Debian Bug report #908463,
regarding torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy
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 at bugs.debian.org
immediately.)


-- 
908463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908463
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: intrigeri at debian.org
Subject: torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy
Date: Mon, 10 Sep 2018 09:59:54 +0200
Size: 2310
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180917/6bd035b3/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Bug#908463: fixed in torbrowser-launcher 0.2.9-5
Date: Mon, 17 Sep 2018 16:36:15 +0000
Size: 5864
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180917/6bd035b3/attachment-0001.mht>

From ftpmaster at ftp-master.debian.org  Mon Sep 17 18:12:56 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 17 Sep 2018 17:12:56 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.2.9-5~bpo8+1_source.changes
Message-ID: <E1g1x4y-0005sb-Pl@usper.debian.org>

torbrowser-launcher_0.2.9-5~bpo8+1_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.2.9-5~bpo8+1.dsc
  torbrowser-launcher_0.2.9-5~bpo8+1.debian.tar.xz

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Mon Sep 17 18:13:05 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 17 Sep 2018 17:13:05 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.2.9-5~bpo9+1_source.changes
Message-ID: <E1g1x57-0005tt-9d@usper.debian.org>

torbrowser-launcher_0.2.9-5~bpo9+1_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.2.9-5~bpo9+1.dsc
  torbrowser-launcher_0.2.9-5~bpo9+1.debian.tar.xz
  torbrowser-launcher_0.2.9-5~bpo9+1_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Mon Sep 17 18:21:06 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 17 Sep 2018 17:21:06 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.2.9-5~bpo8+1_source.changes ACCEPTED into
 jessie-backports-sloppy
Message-ID: <E1g1xCs-0009Wa-Ca@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Tue, 18 Sep 2018 01:27:31 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.2.9-5~bpo8+1
Distribution: jessie-backports-sloppy
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.2.9-5~bpo8+1) jessie-backports-sloppy; urgency=medium
 .
   * Rebuild for jessie-backports-sloppy.
Checksums-Sha1:
 4bd1262c6ea35797a8c70f270e349d318e2b4f9e 2253 torbrowser-launcher_0.2.9-5~bpo8+1.dsc
 290d8da97f58b40f08930705602d0b2454bbc851 15116 torbrowser-launcher_0.2.9-5~bpo8+1.debian.tar.xz
Checksums-Sha256:
 c0e9cd529f44b9d3e2823067fc4e7d2285997d6af91edb7c0fdec241f98c31ce 2253 torbrowser-launcher_0.2.9-5~bpo8+1.dsc
 94d3c419e62299cddaa593619a7c2b7ba7087618c35e60c94a37f2f66fbb9860 15116 torbrowser-launcher_0.2.9-5~bpo8+1.debian.tar.xz
Files:
 b7e36849ab6d49101e257c19dd521b1c 2253 contrib/web optional torbrowser-launcher_0.2.9-5~bpo8+1.dsc
 4b05f263ce5afc1057af9c6a7fa491ec 15116 contrib/web optional torbrowser-launcher_0.2.9-5~bpo8+1.debian.tar.xz

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluf1z4QHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qOdLD/9G9ycVZ7z525+UxC0BuXKVk9drMW5V9n1l
TCbP4saNsPveWm4P+JwXGLdiEuKR1TdN/BMcrn8ZOY3dwJycXDTsBSCQu32fCsUl
p7kx497Y6p89KsBhnv3H7a1uQdn7Qs4YEUNwDfkJmOnjeFSVyQl2k9JZYg3QAzXl
wH40LFK0wOf+4tPM74EST0saHHbnvriGK8o3KPBJUcZT/aazZYI9ggUrBBzbF7qN
IBwC+KZ6QG2SAIB+LNWZrC8R+G/rVkwy1jJFml9tzIcq8GKOYvFlWvGTr3oAfups
NP/5JVGMoBAZtqm0JmO7RE7939FJV+vCqoQR1FNWIh8QCXnLHQDpbZdcGcXSE07a
/lWl5HW8svHnWvRkuX5O8+5c01frqH6VQ3y3jMGdoeHbH+EXhPfiJRRltknno+vp
xTnHFfG1EQmasokGko0rVLkErKU6ld7AkgMt27l8cu0kPSnXAvO9et4lb+U2XL32
V8Umi4svvNO+p0iLPwpTS3mMu6fa22eXIC7dn4xaVs/3Mew7Ivn7DbhRvzWwsgRq
NKak0WBVjgIMOS+Kj+7Wt+rdFPhRaN8KgM1KN68NLwKYgCGfRUXhQrxV+aUYjjEH
sPJfqb2pgUTLjD+TRnNsrC71ySxzGJ5zmspTkx/VmzkBde6CigHbQ9Ao5bRwOfM2
XMkiFblhQg==
=qmrJ
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Mon Sep 17 18:21:11 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 17 Sep 2018 17:21:11 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.2.9-5~bpo9+1_source.changes ACCEPTED into
 stretch-backports
Message-ID: <E1g1xCx-0009XI-L7@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Tue, 18 Sep 2018 01:26:57 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.2.9-5~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.2.9-5~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
Checksums-Sha1:
 8c1ae49cacd5c81e3bc3c2098333fed36e4ab0b3 2253 torbrowser-launcher_0.2.9-5~bpo9+1.dsc
 21e6fe23742186ddd417b50aa2351e00714349a0 15112 torbrowser-launcher_0.2.9-5~bpo9+1.debian.tar.xz
 a07afb704793090c5ec7e5b9446604603f34c68d 6471 torbrowser-launcher_0.2.9-5~bpo9+1_source.buildinfo
Checksums-Sha256:
 36293335addd804891a0215b846e111fb57c9c3ec322711cbf846d4655b94b2e 2253 torbrowser-launcher_0.2.9-5~bpo9+1.dsc
 a2f30221d9dbd633a338a26f978bc02bb67621fcc7c295f31625a1a29454d009 15112 torbrowser-launcher_0.2.9-5~bpo9+1.debian.tar.xz
 d747f4fcaace159419c5448f89618f75b577389906de1d0f3527dffbc5fe5512 6471 torbrowser-launcher_0.2.9-5~bpo9+1_source.buildinfo
Files:
 b8c4dc02d273d0937ec20be6208af91c 2253 contrib/web optional torbrowser-launcher_0.2.9-5~bpo9+1.dsc
 0f1b6a0036b06103935fe2ac70d7f1c7 15112 contrib/web optional torbrowser-launcher_0.2.9-5~bpo9+1.debian.tar.xz
 6721b414fc552eab4913d87c4138c207 6471 contrib/web optional torbrowser-launcher_0.2.9-5~bpo9+1_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluf1zUQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qG6BD/91MqUpX5YUp3kG3yu2gnubQ7VjvE3YTxae
GpLwpybLbDsS3RuG4I/yGU0Ov/u9G3+2YMPGlIqBeJkyTAX+/Dspn53C5elcKL6o
zaf+UapWmUnqyjozFHMhi3NVDbAXd+N1s2D5mOZlymCvwrOzlngL5xgwoBUk9Dsw
AJYiM1CyGGVruoeMA9yGrx+EHgyLx+tF1wayQtfbAY8G65Qz7H0tIyW/27gDV+ZA
GwKHbyYqIN7ylxBPtCWP8bcs+iAJoT0pyn8l7nB7jdgP8dRJl9/NZ3oOHe4sNzql
Peq8HcI83aXYaJwZBWIRK/7mGCx+sjX/XwdjTVRBgctaSi1uLDexVZfr+cA6ydtK
EuPGFqPQS8WwkRH7Vk7wGyn1ZTM7tghWclvKDVYyw9qt7GiHpFaLIYptDFk5EG9Z
wsE8UQOsYkYmuU12oO7FSDIUtlmsHUualdYEQnPE3bl9E1k43qN+NyHw6huQqNAH
y/A5AF56ovVYZuovsDvOtdyiY7gpLeiAH5cyNRwCAYD+g2tTDWvRL4HjtVPZ00E1
EsVffWX7oXlyf085gNGYiKnwI3vtTKamDNV8XHnMVVXWJA5yBLFQ3A9diBNxKa3x
TWTsvuBqwcfw7LFlaX4Jykb0M3OaVNOX8uiE4f9ehY3+A110Jmh9BlX5BiQa8F8E
eixv6/qBXg==
=v1SN
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From noreply at release.debian.org  Tue Sep 18 05:39:12 2018
From: noreply at release.debian.org (Debian testing autoremoval watch)
Date: Tue, 18 Sep 2018 04:39:12 +0000
Subject: [Pkg-privacy-maintainers] torbrowser-launcher is marked for
 autoremoval from testing
Message-ID: <E1g27n6-00062P-2T@respighi.debian.org>

torbrowser-launcher 0.2.9-4 is marked for autoremoval from testing on 2018-10-09

It is affected by these RC bugs:
908463: torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy



From ftpmaster at ftp-master.debian.org  Tue Sep 18 14:54:19 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 18 Sep 2018 13:54:19 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.3.0~dev-1~exp4_source.changes
Message-ID: <E1g2GSJ-0005Km-Kv@usper.debian.org>

torbrowser-launcher_0.3.0~dev-1~exp4_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.3.0~dev-1~exp4.dsc
  torbrowser-launcher_0.3.0~dev-1~exp4.debian.tar.xz
  torbrowser-launcher_0.3.0~dev-1~exp4_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Tue Sep 18 15:46:35 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 18 Sep 2018 14:46:35 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.3.0~dev-1~exp4_source.changes ACCEPTED into
 experimental
Message-ID: <E1g2HGt-000GPP-4V@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Tue, 18 Sep 2018 22:42:28 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.3.0~dev-1~exp4
Distribution: experimental
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.3.0~dev-1~exp4) experimental; urgency=medium
 .
   * debian/patches:
     - Refresh patches.
     - Cherry-pick 5 upstream patches to fix appamor profile for
       Tor Browser 8.0
   * debian/control:
     - Rename tag X-Python-Version to XS-Python-Version.
     - Add XB-Python-Version tag for binary package.
   * debian/torbrowser-launcher.maintscript:
     - rm_conffile appamor profile /etc/apparmor.d/local/*, which was
       removed since 0.2.9-2. Thanks to gregor herrmann for the fix.
Checksums-Sha1:
 3348844b20f20cdb518681c0b856b30805e39932 2245 torbrowser-launcher_0.3.0~dev-1~exp4.dsc
 7827071ab4889710847178045b66121042c70098 16048 torbrowser-launcher_0.3.0~dev-1~exp4.debian.tar.xz
 9a94511119ffffdcca541db6fbe5a7c0dadcf0b7 6238 torbrowser-launcher_0.3.0~dev-1~exp4_source.buildinfo
Checksums-Sha256:
 68e046f3eaf150440ce7b9f0dc04e87325709aeaf150d22ac4640ea9b780708e 2245 torbrowser-launcher_0.3.0~dev-1~exp4.dsc
 c18999107dd3947965cf357cfb76ca1dd5a6c6a1c63188b81ffdc14b6a808dd3 16048 torbrowser-launcher_0.3.0~dev-1~exp4.debian.tar.xz
 baacbcbcc57ee5aabd1e3c1bdb0159ba9983ebb2f2c932ca628657bacd7e46e4 6238 torbrowser-launcher_0.3.0~dev-1~exp4_source.buildinfo
Files:
 43229f2e7cf9b955e016e373e076ab2c 2245 contrib/web optional torbrowser-launcher_0.3.0~dev-1~exp4.dsc
 39a3a3a5876bda41b3cd13ab78ec845d 16048 contrib/web optional torbrowser-launcher_0.3.0~dev-1~exp4.debian.tar.xz
 a976c57c13bb1d79bbe5a96bbd5af289 6238 contrib/web optional torbrowser-launcher_0.3.0~dev-1~exp4_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluhAUwQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qDXYD/0dKZLrrg0CKth07QHjfmumzKBbb0tWSO71
bQqvnEgbHCbFv7AqEiBtleapr/3EmXiItC1Q0BsP3sCYp0/QJ6kLkri8H6er4FAw
uiLZzfMJkuLuYPeNs/pQdguVOx+yhj2DM5w8tdedaaRw29Ks9ZmMlLLt4AzwvGID
SvVI0/2vcH3/dpN+M1jIZgXgqI1TDOu7EN0hVzF0JLDuwANWg8EVfuGv03/ypIBr
JckWmAgO5F+PdHas7KewyIMew+hy20lpCr+hR6IMIhjKOZZqDqek4X4/UzZYgt9U
R6I2JgRMVahYe3Jv9hGosceEv8vw0G/Rq34Z5SXnYesgkX+VC2EaqLYz50jvzOpz
N0lv9nIoBD+V39il2ylrF8oxM+iE+ioJ6hjVyTKLJP44Qof4iQe4u01sKG3AgAfx
5VSD353/EQpn13u/ca0tsc2aWrrI2ks4EagdZ+zPXqc4UUZsMTl8y47ezTF0HLHr
udcV3G+areSUMdaYPYXzZMw1++kmcm52HPsCagXiZt7TZmakKDWtXjSSpJjCc/BA
UP9xWtMrkX8ouZ+8O+iwc73M7P6AtknN2TN9HYWeOFVCRDua3gEq7A0mpx8lvmr3
jZUsLf4U5E+6J4FHGIiSKkZXD00JhZhUjyzwlh1k7yt7j5RwjoSxvH6ImrhAeNDk
vV/8vY1pug==
=mY06
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Wed Sep 19 15:17:07 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 19 Sep 2018 14:17:07 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.3.0-1~exp1_source.changes
Message-ID: <E1g2dHv-0001zQ-B1@usper.debian.org>

torbrowser-launcher_0.3.0-1~exp1_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.3.0-1~exp1.dsc
  torbrowser-launcher_0.3.0.orig.tar.gz
  torbrowser-launcher_0.3.0-1~exp1.debian.tar.xz
  torbrowser-launcher_0.3.0-1~exp1_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Wed Sep 19 15:43:20 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 19 Sep 2018 14:43:20 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.3.0-1~exp1_source.changes ACCEPTED into experimental
Message-ID: <E1g2dhI-000A1l-Mg@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Wed, 19 Sep 2018 23:06:56 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.3.0-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.3.0-1~exp1) experimental; urgency=medium
 .
   * New upstream release 0.3.0
     - Switched from python2 to python3
     - Switched from gtk2 to Qt5
     - Switched from twisted to requests/socks
     - Use QThreads for async
     - Removed modem sound
     - Only refresh gpg keyring on verification error, instead of every time
     - Updated AppArmor profiles
     - Updated available languages, and fixed locale detection bug
     - Fixed false signature verification error related to twisted
   * debian/patches:
     - Refresh patches.
     - Remove upstreamed patches.
   * debian/control:
     - Remove XS-Python-Version and XB-Python-Version, since lintian says
       it's not necessary.
Checksums-Sha1:
 8d906470e340b3e9c1d793a781ae2d076791d11d 2194 torbrowser-launcher_0.3.0-1~exp1.dsc
 ac22486d875125a5b993dba2883ae0abefff506f 221528 torbrowser-launcher_0.3.0.orig.tar.gz
 4208615bc5df9477375fd239f6464dd6de405e44 11116 torbrowser-launcher_0.3.0-1~exp1.debian.tar.xz
 c01b79097eab18c93756d8160131408dfddd7597 6222 torbrowser-launcher_0.3.0-1~exp1_source.buildinfo
Checksums-Sha256:
 e39cdd1cab52ac9b3f983e229b37ac6df526a260af9305f4d65c243ac31e4021 2194 torbrowser-launcher_0.3.0-1~exp1.dsc
 7377754eaae72ac1fc0a524c8428b816a94fc4c9a638f34896f181900bc8460e 221528 torbrowser-launcher_0.3.0.orig.tar.gz
 3983a31f68024fc81b1db2cac8c4895a3da4342398afc8173042bf7738b7ef88 11116 torbrowser-launcher_0.3.0-1~exp1.debian.tar.xz
 7d8f145621cc9c645349eacbe3100bedb551afa471df3ba7de64161fc79a6aaf 6222 torbrowser-launcher_0.3.0-1~exp1_source.buildinfo
Files:
 cabaf4387c7fe2cdf518137769097346 2194 contrib/web optional torbrowser-launcher_0.3.0-1~exp1.dsc
 a22f435e63d25e5c0507a685d231b07f 221528 contrib/web optional torbrowser-launcher_0.3.0.orig.tar.gz
 a5a3cf2ea98ae8630d2da28a5788af62 11116 contrib/web optional torbrowser-launcher_0.3.0-1~exp1.debian.tar.xz
 8d49606b7acc7e1eda06fe63b345a406 6222 contrib/web optional torbrowser-launcher_0.3.0-1~exp1_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluiWHYQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qNLTD/9nYtC0Bkdi3CSVXAgfPPbMriT/C2IgR3Ah
bIdkNlquaFw/2ZYp3Os/IWkzZK0COhJpfFlAQ07sB1z4lRtDXqdn7kLv8R7x3pJm
U87xrXNMfiffUSaU1V3GUHLJjXtVdkX3oVdtLuGuWbQlT3X+E+lNebNEfG2sKx6Y
3nm66D5Y3OrNKGkYJL/rRd5Pjmk7j4jnyQng5bdihp/TcFWh4oCd+hUdTrhdlmwa
3iNcY0Gx/P6BTLRd8G+CYFYtnQjWJRjXjWTlw4Y/7Iz/ISuC2neKcz6PtNnJRkOq
mBopxyulk8IrMhsHHUl4F38j3Pal2dv1BBjGwlIJIoPYHdiKZhJeC5I1a0K9iAgt
PaaBolkm0BIyjimUhRYEIqI5qvwpoiaYS8R7bG065n/8unL8vQ0C0LvcP4e0wYBf
r782PflfNpJNhP7gxBzGPs/GIERnMDuE+HPNOgtOcBxyyPxWpf45IjW6m9eRU040
Hdy9EUr8BkkmJ6STgDqU9jJCZz9S/pIfBfZpk4q2CjJyG/p0xYGI21kiX9Y+LR5+
9QBsplYVvUgXOFcR4sJP5MXDSywHSmSKq3I2HSnzxJ4SBFDPvSUb6zY3onv60Csy
SfFqVo9ZhXdHQUgagmWjqURyNgFPNh5AvNt0jyF8/UfmZcamRIcKbDFK1wWp8+Ob
E4lv08P2lw==
=2jQJ
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From stefan.esterer at gmail.com  Wed Sep 19 22:55:12 2018
From: stefan.esterer at gmail.com (stefan esterer)
Date: Wed, 19 Sep 2018 23:55:12 +0200
Subject: [Pkg-privacy-maintainers] Bug#908706: new version fixed the problem
In-Reply-To: <handler.908706.B.15367845222488.ack@bugs.debian.org>
References: <3336504d-415a-3534-b393-2b9b79a1f2af@gmail.com>
 <handler.908706.B.15367845222488.ack@bugs.debian.org>
 <3336504d-415a-3534-b393-2b9b79a1f2af@gmail.com>
Message-ID: <0ec3b1bd-ed34-4a2b-c2a4-93dce2b0cff6@gmail.com>

With the new version of torbrowser-launcher 0.2.9-4 I am able to install
and start the tor browser...

So on my view the bug can be closed...

thx
stefan


From noreply at release.debian.org  Thu Sep 20 05:39:13 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Thu, 20 Sep 2018 04:39:13 +0000
Subject: [Pkg-privacy-maintainers] torbrowser-launcher 0.2.9-5 MIGRATED to
 testing
Message-ID: <E1g2qkD-0003vI-IP@respighi.debian.org>

FYI: The status of the torbrowser-launcher source package
in Debian's testing distribution has changed.

  Previous version: 0.2.9-4
  Current version:  0.2.9-5

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From elbrus at debian.org  Thu Sep 20 20:36:19 2018
From: elbrus at debian.org (Paul Gevers)
Date: Thu, 20 Sep 2018 21:36:19 +0200
Subject: [Pkg-privacy-maintainers] Bug#909275: xorg-server breaks
 onioncircuits autopkgtest: expected string, NoneType found
Message-ID: <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>

Source: xorg-server, onioncircuits
Control: found -1 xorg-server/2:1.20.1-3
Control: found -1 onioncircuits/0.5-2
X-Debbugs-CC: debian-ci at lists.debian.org
User: debian-ci at lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of xorg-server the autopkgtest of onioncircuits
fails in testing when that autopkgtest is run with the binary packages
of xorg-server from unstable. Interesting data point, with 2:1.20.1-2
from two days ago it passed. It passes when run with only packages from
testing. In tabular form:
                       pass            pass          fail
xorg-server            from testing    2:1.20.1-2    2:1.20.1-3
onioncircuits          from testing    0.5-2         0.5.2
all others             from testing    from testing  from testing

I copied some of the output at the bottom of this report. Based on
reading the xorg-server changelog, I suspect these tests are trying to
activate something on screen and now they are missing the active area:
  * xvfb-run*: Update default resolution and bitdepth to match upstream
    defaults.

Currently this regression is contributing to the delay of the migration
of xorg-server to testing [1]. Due to the nature of this issue, I filed
this bug report against both packages. Can you please investigate the
situation and reassign the bug to the right package? If needed, please
change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=xorg-server

https://ci.debian.net/data/autopkgtest/testing/amd64/o/onioncircuits/1022616/log.gz

autopkgtest [16:47:15]: test gui-test: [-----------------------
waiting for Tor to settle...
E
======================================================================
ERROR: test_has_correct_circuits (__main__.TestOnionCircuitsGUI)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "debian/tests/check-circuits", line 70, in test_has_correct_circuits
    self.assertEqual(self._get_circuits(), mycircs)
  File "debian/tests/check-circuits", line 54, in _get_circuits
    circs.add(", ".join(nicks))
TypeError: sequence item 0: expected string, NoneType found

----------------------------------------------------------------------
Ran 1 test in 1.046s

FAILED (errors=1)
autopkgtest [16:47:37]: test gui-test: -----------------------]

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180920/97a0368f/attachment.sig>

From owner at bugs.debian.org  Thu Sep 20 20:39:06 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 20 Sep 2018 19:39:06 +0000
Subject: [Pkg-privacy-maintainers] Processed: xorg-server breaks
 onioncircuits autopkgtest: expected string, NoneType found
References: <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>
 <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>
Message-ID: <handler.s.B.153747219930650.transcript@bugs.debian.org>

Processing control commands:

> found -1 xorg-server/2:1.20.1-3
Bug #909275 [src:xorg-server, src:onioncircuits] xorg-server breaks onioncircuits autopkgtest: expected string, NoneType found
Marked as found in versions xorg-server/2:1.20.1-3.
> found -1 onioncircuits/0.5-2
Bug #909275 [src:xorg-server, src:onioncircuits] xorg-server breaks onioncircuits autopkgtest: expected string, NoneType found
Marked as found in versions onioncircuits/0.5-2.

-- 
909275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909275
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From satta at debian.org  Fri Sep 21 08:29:48 2018
From: satta at debian.org (Sascha Steinbiss)
Date: Fri, 21 Sep 2018 09:29:48 +0200
Subject: [Pkg-privacy-maintainers] Bug#909275: Bug#909275: xorg-server
 breaks onioncircuits autopkgtest: expected string, NoneType found
In-Reply-To: <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>
References: <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>
 <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>
Message-ID: <8B84B543-03E1-45CE-B1D2-515B435CEC8E@debian.org>

Hi Paul,

Thanks for reporting this.

> I copied some of the output at the bottom of this report. Based on
> reading the xorg-server changelog, I suspect these tests are trying to
> activate something on screen and now they are missing the active area:
>  * xvfb-run*: Update default resolution and bitdepth to match upstream
>    defaults.

I took a look at the affected code part and it deals with obtaining Tor circuit information from the local Tor daemon via the STEM library, to later compare the ones listed in the UI against them. It looks like the test machine was unable to build circuits at some point in time, and, as a consequence, the tests failed with the specified error.
I do not see an obvious direct connection with Xorg, and a more recent test run from this morning indeed shows that the test succeeds again [1].

> Currently this regression is contributing to the delay of the migration
> of xorg-server to testing [1]. Due to the nature of this issue, I filed
> this bug report against both packages. Can you please investigate the
> situation and reassign the bug to the right package? If needed, please
> change the bug's severity.

I would be tempted to close the bug and maybe adapt the error message given in the test. Any arguments against that?

Best regards
Sascha

[1] https://ci.debian.net/data/autopkgtest/testing/amd64/o/onioncircuits/1024612/log.gz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180921/285b5107/attachment.sig>

From jcristau at debian.org  Fri Sep 21 16:20:32 2018
From: jcristau at debian.org (Julien Cristau)
Date: Fri, 21 Sep 2018 17:20:32 +0200
Subject: [Pkg-privacy-maintainers] Bug#909275: xorg-server breaks
 onioncircuits autopkgtest: expected string, NoneType found
In-Reply-To: <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>
References: <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>
 <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>
Message-ID: <fb8521b8-14db-7ed7-8224-79ee869369b8@debian.org>

Control: reassign -1 onioncircuits 0.5-2
Control: retitle -1 onioncircuits: flaky autopkgtest?

This doesn't seem related to xorg-server.

Cheers,
Julien

On 09/20/2018 09:36 PM, Paul Gevers wrote:
> Source: xorg-server, onioncircuits
> Control: found -1 xorg-server/2:1.20.1-3
> Control: found -1 onioncircuits/0.5-2
> X-Debbugs-CC: debian-ci at lists.debian.org
> User: debian-ci at lists.debian.org
> Usertags: breaks needs-update
> 
> Dear maintainers,
> 
> With a recent upload of xorg-server the autopkgtest of onioncircuits
> fails in testing when that autopkgtest is run with the binary packages
> of xorg-server from unstable. Interesting data point, with 2:1.20.1-2
> from two days ago it passed. It passes when run with only packages from
> testing. In tabular form:
>                        pass            pass          fail
> xorg-server            from testing    2:1.20.1-2    2:1.20.1-3
> onioncircuits          from testing    0.5-2         0.5.2
> all others             from testing    from testing  from testing
> 
> I copied some of the output at the bottom of this report. Based on
> reading the xorg-server changelog, I suspect these tests are trying to
> activate something on screen and now they are missing the active area:
>   * xvfb-run*: Update default resolution and bitdepth to match upstream
>     defaults.
> 
> Currently this regression is contributing to the delay of the migration
> of xorg-server to testing [1]. Due to the nature of this issue, I filed
> this bug report against both packages. Can you please investigate the
> situation and reassign the bug to the right package? If needed, please
> change the bug's severity.
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [1] https://qa.debian.org/excuses.php?package=xorg-server
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/o/onioncircuits/1022616/log.gz
> 
> autopkgtest [16:47:15]: test gui-test: [-----------------------
> waiting for Tor to settle...
> E
> ======================================================================
> ERROR: test_has_correct_circuits (__main__.TestOnionCircuitsGUI)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "debian/tests/check-circuits", line 70, in test_has_correct_circuits
>     self.assertEqual(self._get_circuits(), mycircs)
>   File "debian/tests/check-circuits", line 54, in _get_circuits
>     circs.add(", ".join(nicks))
> TypeError: sequence item 0: expected string, NoneType found
> 
> ----------------------------------------------------------------------
> Ran 1 test in 1.046s
> 
> FAILED (errors=1)
> autopkgtest [16:47:37]: test gui-test: -----------------------]
> 


From owner at bugs.debian.org  Fri Sep 21 16:21:11 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Fri, 21 Sep 2018 15:21:11 +0000
Subject: [Pkg-privacy-maintainers] Processed: Re: xorg-server breaks
 onioncircuits autopkgtest: expected string, NoneType found
References: <fb8521b8-14db-7ed7-8224-79ee869369b8@debian.org>
 <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>
Message-ID: <handler.s.B909275.15375432416809.transcript@bugs.debian.org>

Processing control commands:

> reassign -1 onioncircuits 0.5-2
Bug #909275 [src:xorg-server, src:onioncircuits] xorg-server breaks onioncircuits autopkgtest: expected string, NoneType found
Bug reassigned from package 'src:xorg-server, src:onioncircuits' to 'onioncircuits'.
No longer marked as found in versions onioncircuits/0.5-2 and xorg-server/2:1.20.1-3.
Ignoring request to alter fixed versions of bug #909275 to the same values previously set
Bug #909275 [onioncircuits] xorg-server breaks onioncircuits autopkgtest: expected string, NoneType found
Marked as found in versions onioncircuits/0.5-2.
> retitle -1 onioncircuits: flaky autopkgtest?
Bug #909275 [onioncircuits] xorg-server breaks onioncircuits autopkgtest: expected string, NoneType found
Changed Bug title to 'onioncircuits: flaky autopkgtest?' from 'xorg-server breaks onioncircuits autopkgtest: expected string, NoneType found'.

-- 
909275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909275
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From elbrus at debian.org  Fri Sep 21 21:17:51 2018
From: elbrus at debian.org (Paul Gevers)
Date: Fri, 21 Sep 2018 22:17:51 +0200
Subject: [Pkg-privacy-maintainers] Bug#909275: Bug#909275: xorg-server
 breaks onioncircuits autopkgtest: expected string, NoneType found
In-Reply-To: <8B84B543-03E1-45CE-B1D2-515B435CEC8E@debian.org>
References: <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>
 <8B84B543-03E1-45CE-B1D2-515B435CEC8E@debian.org>
 <cbc667cb-cc21-ad36-8808-21ceb28726fc@debian.org>
Message-ID: <9d610e2e-ad30-96c1-cbd1-817d4f513dd8@debian.org>

Hi Sascha,

On 21-09-18 09:29, Sascha Steinbiss wrote:
> I would be tempted to close the bug and maybe adapt the error message given in the test. Any arguments against that?

Julien already assigned the bug to onioncircuits, and looking at the
test history, I think he has a point with his re-titling of the bug. It
seems that onioncircuits is failing once in a while without clear reasons.

Recent discussion of gating migration by autopkgtests on debian-devel
[1] noted that if this is going to work, and in particular if we are
going to *block* migration when it causes autopkgtest regressions rather
than merely delaying it, intermittent autopkgtest failures are likely to
have to be considered RC due to their impact on the tested package's
dependencies.

Paul

[1] https://lists.debian.org/debian-devel/2018/05/msg00061.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180921/e0dc4870/attachment.sig>

From shirishag75 at gmail.com  Sat Sep 22 17:32:26 2018
From: shirishag75 at gmail.com (shirish =?UTF-8?Q?=E0=A4=B6=E0=A4=BF=E0=A4=B0=E0=A5=80=E0=A4=B7?=)
Date: Sat, 22 Sep 2018 22:02:26 +0530
Subject: [Pkg-privacy-maintainers] Bug#909369: torbrowser-launcher:
 fontconfig in torbrowser-launcher complains about blank element
Message-ID: <CADdDZRmiGC9rCFdVh9tCMD1GnFmPzSi_hYVYUnTYCi46wWDeuQ@mail.gmail.com>

Package: torbrowser-launcher
Version: 0.2.9-5
Severity: normal

Dear Maintainer,

I was looking at torbrowser in verbose mode and came across the
following statement -

Fontconfig warning:
"/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf",
line 85: unknown element "blank"

I looked at fonts.conf and sure enough on line 85

<!--
  These are the default Unicode chars that are expected to be blank
  in fonts.  All other blank chars are assumed to be broken and
  won't appear in the resulting charsets
 -->
		<blank>

I do not know whether it's an issue in fontconfig that is in debian or
an issue with the fonts.conf itself.

Please look into the same.

I also have no idea why the python packages are broken, probably
because everything is shifting to python3 .

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (100,
'unstable-debug'), (100, 'experimental-debug'), (100, 'experimental'),
(100, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  gnupg             2.2.10-1
ii  libdbus-glib-1-2  0.110-3
ii  python            2.7.15-3
pn  python-gtk2       <none>
pn  python-lzma       <none>
pn  python-parsley    <none>
pn  python-psutil     <none>
pn  python-twisted    <none>
pn  python-txsocksx   <none>

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.4.8-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.13-8
pn  python-pygame  <none>

-- no debconf information

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8


From ftpmaster at ftp-master.debian.org  Sun Sep 23 20:32:44 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 23 Sep 2018 19:32:44 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 onionbalance_0.1.8-3~bpo9+1_amd64.changes
Message-ID: <E1g4A7Y-000224-B1@usper.debian.org>

onionbalance_0.1.8-3~bpo9+1_amd64.changes uploaded successfully to localhost
along with the files:
  onionbalance_0.1.8-3~bpo9+1.dsc
  onionbalance_0.1.8.orig.tar.gz
  onionbalance_0.1.8-3~bpo9+1.debian.tar.xz
  onionbalance_0.1.8-3~bpo9+1_all.deb
  onionbalance_0.1.8-3~bpo9+1_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sun Sep 23 20:34:27 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 23 Sep 2018 19:34:27 +0000
Subject: [Pkg-privacy-maintainers] onionbalance_0.1.8-3~bpo9+1_amd64.changes
 is NEW
Message-ID: <E1g4A9D-000IiL-8g@fasolo.debian.org>

binary:onionbalance is NEW.
binary:onionbalance is NEW.
source:onionbalance is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
     or https://ftp-master.debian.org/backports-new.html for *-backports


From anbe at debian.org  Mon Sep 24 14:05:28 2018
From: anbe at debian.org (Andreas Beckmann)
Date: Mon, 24 Sep 2018 15:05:28 +0200
Subject: [Pkg-privacy-maintainers] Bug#909489: sbws: unowned directory after
 purge: /var/lib/sbws/
Message-ID: <153779432819.31552.5159069601282643120.reportbug@zam581.zam.kfa-juelich.de>

Package: sbws
Version: 0.6.0-1
Severity: important
User: debian-qa at lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-removal-and-or-configuration-purging

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

The maintainer scripts create (and later remove) a file in that
directory. Manual directory removal may be not appropriate as this
directory is shared between several packages.

If the package would ship this as an empty directory, dpkg would take
care of the creation and removal (if it's empty).

>From the attached log (scroll to the bottom...):

0m57.4s ERROR: FAIL: Package purging left files on system:
  /var/lib/sbws/	 not owned


cheers,

Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sbws_0.6.0-1.log.gz
Type: application/gzip
Size: 13378 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180924/0cc960aa/attachment.gz>

From ftpmaster at ftp-master.debian.org  Mon Sep 24 18:01:15 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 24 Sep 2018 17:01:15 +0000
Subject: [Pkg-privacy-maintainers] onionbalance_0.1.8-3~bpo9+1_amd64.changes
 ACCEPTED into stretch-backports, stretch-backports
Message-ID: <E1g4UEV-0007T5-UP@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sun, 23 Sep 2018 19:39:27 +0100
Source: onionbalance
Binary: onionbalance
Architecture: source all
Version: 0.1.8-3~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Federico Ceratto <federico at debian.org>
Description:
 onionbalance - Tor hidden service load balancer
Closes: 799973 859476
Changes:
 onionbalance (0.1.8-3~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports
 .
 onionbalance (0.1.8-3) unstable; urgency=medium
 .
   * Upload to unstable
 .
 onionbalance (0.1.8-2) experimental; urgency=medium
 .
   * Fix unit file syntax. Thanks Helle Vaanzinn (Closes: #859476)
 .
 onionbalance (0.1.8-1) experimental; urgency=medium
 .
   * New upstream release
 .
 onionbalance (0.1.7-1) experimental; urgency=medium
 .
   * New upstream release
 .
 onionbalance (0.1.6-1) unstable; urgency=medium
 .
   * New upstream release
 .
 onionbalance (0.1.5-1) unstable; urgency=medium
 .
   * New upstream release
 .
 onionbalance (0.1.4-1) unstable; urgency=low
 .
   * New upstream release
 .
 onionbalance (0.1.3-3) unstable; urgency=low
 .
   * Add patch to disable failing test
 .
 onionbalance (0.1.3-2) unstable; urgency=low
 .
   * Make Tor a dependency
 .
 onionbalance (0.1.3-1) unstable; urgency=low
 .
   * Initial release (Closes: #799973).
Checksums-Sha1:
 6cabcbc6c7afa495f490194d0bc73fdd422a259a 2315 onionbalance_0.1.8-3~bpo9+1.dsc
 871c01f767a1b63926da74ea04b47748fed6f04b 139031 onionbalance_0.1.8.orig.tar.gz
 e687be8932356f056ed828d0854e3ba20f08383d 10272 onionbalance_0.1.8-3~bpo9+1.debian.tar.xz
 fa00351ebc0ae7079e2e0d93a2f12034a5c728a3 135532 onionbalance_0.1.8-3~bpo9+1_all.deb
 f881f2d4e6385d29609db98b563458dc28823f3b 7529 onionbalance_0.1.8-3~bpo9+1_amd64.buildinfo
Checksums-Sha256:
 3bf89bde17d709063dbf0bf8bd42806eb2ff3f988e3a0f29a6d3adc4dce41f6c 2315 onionbalance_0.1.8-3~bpo9+1.dsc
 3a1bfee36d2d8e5c3a3afec03529d7ddb01917e9140603876d05174a3d30b4f5 139031 onionbalance_0.1.8.orig.tar.gz
 bd2dc435081f03a64995dec34e05644b888966029cab320affaa4a773c51aa92 10272 onionbalance_0.1.8-3~bpo9+1.debian.tar.xz
 6279fb410ff444e1afc96555ef7ad8f91c0757257c7ed37383a3ec9669607fb3 135532 onionbalance_0.1.8-3~bpo9+1_all.deb
 7e8d4d17d80fe4ee138d518b90e39bea7197d3adf96c8ffbac2f5e281e013bb9 7529 onionbalance_0.1.8-3~bpo9+1_amd64.buildinfo
Files:
 12f1f50fb77f93c52bfafb7c9338dc9c 2315 net optional onionbalance_0.1.8-3~bpo9+1.dsc
 1db74f0093bbebd43784fb19ba7ad87b 139031 net optional onionbalance_0.1.8.orig.tar.gz
 c3ca308389823f3204aef08c64202350 10272 net optional onionbalance_0.1.8-3~bpo9+1.debian.tar.xz
 d500420aa2349e6abe16b3e563404747 135532 net optional onionbalance_0.1.8-3~bpo9+1_all.deb
 6d3e9291ea66a919b4c6ac657dd13f48 7529 net optional onionbalance_0.1.8-3~bpo9+1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAlun55sACgkQbzG8RPUX
farNpxAApHeXkDmMK/QcIhlyMI/xUxpLAUHsDTE2g7CoA7rFi7MJ1iwX+rbRMyVT
+Pl9+KPEzLqNHJa8KZz8Ly0SWogXFdqUgVP85OoRxzTTzljlm4naIsbUlwEWFetA
YziQz1tWBxklmd6bQEgYBk6ycShe/EPq2tQr3mwfff8tx/Ul3z8BJZ72Q/83+TJb
ol0VcLKqvy2EWDkapbxBWc0IDKxRRSgT6RGqJ2KitGuBmKGNuIDdAgkDbPWTvVLV
C9+rJrLmgLtbDy8D3pbAraVkGNlxy39vClblFlCVSnAKHrwHOK1/Mw5eEvkubsxS
NkhaY1ff7CrgvciYyaIeAP0qlHLc+4foQfvMpnaap8uMWyFlrUjiQoUdRJROYTlQ
MQF3fCk2tJnZF7vxV/3ZGxPvG8LJEceaz56dVrcbgemGKy8fKwPiKoeq5vlplw2C
q9mMHpob3owzmc9G9puEeagCSXGXCcwSzYzCyZ2P1ch4+nswDB5ppP/gcc9OYWhl
5wxULVAkzHG28ERTGdhiEJZKpq7PhpRDxab31Aug6PJ60YvrpV5HucLxdqpgIT03
y7+U6ZHtEpiyadHt9lDgZOBM2AfTLaHiqDff8aSbqxUZBzW6OAN6B9weXL9G//1C
l8PQ33neW/e6HGHdwY+NgOAENhN1o9/ijV3SW44Zs/7EyQBrE/I=
=p1OT
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Fri Sep 28 17:53:05 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Fri, 28 Sep 2018 16:53:05 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.2.9-6_source.changes
Message-ID: <E1g5w0n-0003xT-Am@usper.debian.org>

torbrowser-launcher_0.2.9-6_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.2.9-6.dsc
  torbrowser-launcher_0.2.9-6.debian.tar.xz
  torbrowser-launcher_0.2.9-6_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Fri Sep 28 18:05:37 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Fri, 28 Sep 2018 17:05:37 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.2.9-6_source.changes ACCEPTED into unstable
Message-ID: <E1g5wCv-000J5U-10@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sat, 29 Sep 2018 01:45:32 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.2.9-6
Distribution: unstable
Urgency: high
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.2.9-6) unstable; urgency=high
 .
   * debian/control:
     - Remove XS-Python-Version since lintian says it's not necessary.
   * debian/copyright:
     - Add comment section to explain why this is contrib package,
       which comforts lintian.
   * debian/patches:
     - Cherry-pick upstream patch to update Tor Browser Developers
       public key.
Checksums-Sha1:
 831e441d719fc949b1ca6faf87fb9d9811f22608 2202 torbrowser-launcher_0.2.9-6.dsc
 9b9a7662de6f13606512a98a8efe90f6231be58b 26656 torbrowser-launcher_0.2.9-6.debian.tar.xz
 30f12bd398ccef31cb85bbf453ee7a91c8c91116 6450 torbrowser-launcher_0.2.9-6_source.buildinfo
Checksums-Sha256:
 2c1f27f4a5d525e16ab7d42d80af6e4b5d48c50e865b1961827d52436d8a43c6 2202 torbrowser-launcher_0.2.9-6.dsc
 c08754deb9e31ca0f04c847a8fb83b3fe346d8a05cdfd4fbe5569d35a3f39f19 26656 torbrowser-launcher_0.2.9-6.debian.tar.xz
 25bc5a497503d5067b719dbbb03b811dde6fcc1489be9035141bda06d32ca40e 6450 torbrowser-launcher_0.2.9-6_source.buildinfo
Files:
 8dc8c3c7ef059c2768696d837933c874 2202 contrib/web optional torbrowser-launcher_0.2.9-6.dsc
 f1ef32c45fbf0b198fdbbf5aa0d6a858 26656 contrib/web optional torbrowser-launcher_0.2.9-6.debian.tar.xz
 9709c3ecf8f2c7e1f52003e69d042246 6450 contrib/web optional torbrowser-launcher_0.2.9-6_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluuW0UQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qBKNEACr1P3F8pHXLCH5dw4c43100YSKamFPjtnj
WZY/qYLlanbsxmYCmM1mYJTMATlNi0GZHoZlMFjyAgpFQKr5Q/v6yIue+5kGHpxi
BFjpd5ltPdqcOAci2+i8uQ9bEyDRF+KUX/V+YUo5Lk79HpiAFAiMHIBlAqPYF8/t
Jz0LEedDyZrsxL2B2QjCm/0XSySHauMYrTg72paDLlat5S1HLBscpM/lmtWk00HG
xZlnLXMSAb8vObK1NVAauPrsKlA3GA51Ik1qGh4vizuj1yE4E37etgtfY/anYfeY
jhhYaSWmPGfh8RGuCke7/H2vczVANk6e787bFcN+MOW0QWmaSj0fdxp9vMzbFYcq
y3BDrpWvleKpEwhJ44lttVby7kXmlUnz9ZrPmdMVk4Hr1/TI1cMmz12jOm9wyB+Y
3J7n7TLsBLkmVgaubgfp1izEgb1kpJPa1NJTc/6xzmLPkTYs0KB+yW0MowOe8ZPT
t0Q9eNQTCeBxI4k1lZR3WsKsxJvAxyzJaqtwGCKXNEVqBApA/RyaipEg99IjdyXk
Jr4hAx7QtusemlDCGZbjWcmG309+17MqeswYgqY84Isw0Jelmqinw2SWvSaWvDCB
MTogkJj8/eNjXIslIYvpAFQYo5OMu87Pu6grgvg00IwvHLwPCbyAr10SMRkUFLBz
KZQEiAvAmw==
=ErNV
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From anarcat at debian.org  Sat Sep 29 00:02:08 2018
From: anarcat at debian.org (Antoine =?UTF-8?Q?Beaupr=C3=A9?=)
Date: Fri, 28 Sep 2018 19:02:08 -0400
Subject: [Pkg-privacy-maintainers] Bug#908463: Bug#908463:
 torbrowser-launcher: Fails to start "Web Content" processes due to outdated
 AppArmor policy
In-Reply-To: <871sa1ifaj.fsf@curie.anarc.at>
References: <85o9d5kcjp.fsf@boum.org> <871sa1ifaj.fsf@curie.anarc.at>
 <85o9d5kcjp.fsf@boum.org>
Message-ID: <875zypmdjj.fsf@curie.anarc.at>

On 2018-09-10 10:43:32, Antoine Beaupré wrote:
> On 2018-09-10 09:59:54, intrigeri at debian.org wrote:
>> Package: torbrowser-launcher
>> Version: 0.2.9-4
>> Severity: serious
>> Tags: upstream fixed-upstream
>>
>> Hi,
>>
>> I've just pushed to commits to the upstream "develop" branch that fix
>> Tor Browser 8 for me. Without these, Tor Browser does start but with
>> e10s enabled, no tab will render as Firefox is not allowed to start
>> any "Web Content" process.
>
> I confirm this problem is real. It seems that as soon as anyone tries to
> upgrade torbrowser in Debian now it either fails with #908068 (before
> launcher upgrade) or this (after launcher upgrade).

For what it's worth, I was still getting that error with 0.2.9-5, but a
(forced) update to sid's 0.2.9-6 version fixes the issue on buster.

Thanks for all involved!

A.

-- 
Dr. King’s major assumption was that if you are nonviolent, if you
suffer, your opponent will see your suffering and will be moved to
change his heart. He only made one fallacious assumption: In order for
nonviolence to work, your opponent must have a conscience. The United
States has none.        - Stokely Carmichael


From ftpmaster at ftp-master.debian.org  Sat Sep 29 05:34:08 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 29 Sep 2018 04:34:08 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.2.9-6~bpo8+1_source.changes
Message-ID: <E1g66xE-0007C4-Cp@usper.debian.org>

torbrowser-launcher_0.2.9-6~bpo8+1_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.2.9-6~bpo8+1.dsc
  torbrowser-launcher_0.2.9-6~bpo8+1.debian.tar.xz

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sat Sep 29 05:39:08 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 29 Sep 2018 04:39:08 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.2.9-6~bpo9+1_source.changes
Message-ID: <E1g6725-0007Ry-23@usper.debian.org>

torbrowser-launcher_0.2.9-6~bpo9+1_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.2.9-6~bpo9+1.dsc
  torbrowser-launcher_0.2.9-6~bpo9+1.debian.tar.xz
  torbrowser-launcher_0.2.9-6~bpo9+1_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sat Sep 29 05:49:28 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 29 Sep 2018 04:49:28 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.2.9-6~bpo8+1_source.changes ACCEPTED into
 jessie-backports-sloppy
Message-ID: <E1g67C4-000Bfu-8r@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sat, 29 Sep 2018 13:23:42 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.2.9-6~bpo8+1
Distribution: jessie-backports-sloppy
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.2.9-6~bpo8+1) jessie-backports-sloppy; urgency=medium
 .
   * Rebuild for jessie-backports-sloppy.
Checksums-Sha1:
 858d4dfef7cf0347681e56bc8a87c18039eb5f6e 2230 torbrowser-launcher_0.2.9-6~bpo8+1.dsc
 0521fd2adb86e971c866c4209d27a62dc6f4cecb 26756 torbrowser-launcher_0.2.9-6~bpo8+1.debian.tar.xz
Checksums-Sha256:
 d832a9587424fd91c80c2dfdcd964b286652f40da4e9c9c6faf50d7a7e423095 2230 torbrowser-launcher_0.2.9-6~bpo8+1.dsc
 802dfbcbaa625f3ea64dd52b6e0f96c81b86ba4888b32d52ee7afb2879645809 26756 torbrowser-launcher_0.2.9-6~bpo8+1.debian.tar.xz
Files:
 fd08b5637df94560edadcf3aa805419d 2230 contrib/web optional torbrowser-launcher_0.2.9-6~bpo8+1.dsc
 a3ba216106da67d2d7cca2a4b85e55a8 26756 contrib/web optional torbrowser-launcher_0.2.9-6~bpo8+1.debian.tar.xz

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluu/6kQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qEqND/9/LYdnIdtLTg3yJTwZDyyIkAVlZJe6qysX
WowHaWbaG/7b2ZOlEmu8ENKLwWcdG+n/F2/Plyx0XN2wko/71WsHOxOMV2J92b+d
sMXuEasXAJqgdd5neVk4JGDBtcIkBloAKceMLxGjeho8PWD/pOXqWikutlES6GQ9
2ptwokTdgglmDnxSLsn7i5gDDE9C851vR3UD/CIRZ9F1dxCoYRHyIt8+bMBipVYp
Jj7Bl5TmfBsdGAVJ7UsbaXmNRUnLy7/a3M6SCYV9JSteoWsiCoFEmkPIrjW5z5SA
qc+Y0h5yGj1sUwEOjEQvsC5/sSNui9z7h4BoNomxn08N/I6dTy4gF4sOdBgoxq7Y
y1Bf+gOeTUjFbLrECquQCxKwJfAwMjRoVuCf+/aKagest0xO/2w8bHCgH75z6j3L
+HIO40YKM+CVO92NMCnUcHkz8wY6OU1qQaHUel12krp1SW38TkupCx671wo7xZHV
YCTGkfniW1aEeELJ7RNvPOryaTp59fD/UOLSAqljtqYuZy4sBxz42sLnbIfQVeUi
vJdUccCbvHGcmZ7zGqrXI0Cdlcs0y1iVfQo066o3YxpUUhIeFhaHhWNNwWpQ9S/M
FqU0FGpWbO6THTmT0kNphwKPNHw+Bs5cAxEqynFXXyWJdfS9nK0pnb62CGHCye32
pv5NXfcvHw==
=8a5y
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Sat Sep 29 05:49:33 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 29 Sep 2018 04:49:33 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.2.9-6~bpo9+1_source.changes ACCEPTED into
 stretch-backports
Message-ID: <E1g67C9-000Bge-Kb@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sat, 29 Sep 2018 13:17:22 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.2.9-6~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.2.9-6~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
Checksums-Sha1:
 960ad74c91f0d1e9882de53ef0ccce0dea8352f5 2230 torbrowser-launcher_0.2.9-6~bpo9+1.dsc
 3558386b32032a9d8d95219da4b04fbca3da8892 26748 torbrowser-launcher_0.2.9-6~bpo9+1.debian.tar.xz
 dad891a326c08ec1280bf3318b8aaeff9c26d040 6506 torbrowser-launcher_0.2.9-6~bpo9+1_source.buildinfo
Checksums-Sha256:
 b882afd5d55af03755a843211712c884f83abbcfc3870bec4dd9e8674ade55c7 2230 torbrowser-launcher_0.2.9-6~bpo9+1.dsc
 fca58a29e2a796ceccd6179960f383622407dc15e93893e016e9d52b981b793f 26748 torbrowser-launcher_0.2.9-6~bpo9+1.debian.tar.xz
 87b80c724de7c4671e2978b7f5283c243a1cba43c641f8c81673018f03e77415 6506 torbrowser-launcher_0.2.9-6~bpo9+1_source.buildinfo
Files:
 44a29cb27b0403b51462d343cce4f593 2230 contrib/web optional torbrowser-launcher_0.2.9-6~bpo9+1.dsc
 1a3b3977b301db0456bc6e0ae4b004b4 26748 contrib/web optional torbrowser-launcher_0.2.9-6~bpo9+1.debian.tar.xz
 e0aaca7c7bdd772214de94e971a306ff 6506 contrib/web optional torbrowser-launcher_0.2.9-6~bpo9+1_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluvADYQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qEBtD/4pvksf2LnVXhqKiChgP8sVSzc49tOZAduM
BrLOYW/uLSb0Hhl5bcofpDiDm0g0xxfYRnEq3ztu5BDVxBMeUJ7ryvxu8bPHc+nQ
nc5gDFIkQ81mqeVxlYc7npjRKq/Tb1LUO0epifX5RXL7nYoWYDZE05CcPFNvCpEg
35w5KdVanb2IVfyb0eHinMtS3Jzi+gTsHGk7hSq44t5aqaas3vWeOhi7mgSVfzmO
p4MCRrtVgjWCj4EIxlZNnmZs7AP+4Abw80kp0vDYnzGzJfxJ+scDRKkkOxCmpk0k
V+l3A3FRGNrU6G0HJ7mcP5+PZEDEWaamosn6JWGULetK5DzHhZHHSFuSqQ6MeI+B
ClLzuhNwH3WqNmXejgIhOX6JOp7+VnjIcdCBJjEp82I95YD0wbpYQ//blroF2p2/
2xls8bxUkV95z5u+USPi7G1WPk71hzxnFJh5yfL9yTfUreUTHnRNqb3HBJGVAv4O
oJYtnODLFPCprAEarmn2pp6ZgV4b4R/zjxVOfiUiWWv/+nfIz/eIOvuB75HnlLfT
Lwt428hDQjT3fyOm2G29ZfmwbrY3oF0ku67G987ZK0gmMB4DO56nwDfePl+rgH+6
3p2eWWHPI27B9Ezkefb8YGxXOlTgSi82R/1eKCd2fJj3h/gzHqwDhZESh4+/WWbx
A0fKRsTQuw==
=M51O
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Sun Sep 30 02:27:42 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 30 Sep 2018 01:27:42 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.3.0-1~exp2_amd64.changes
Message-ID: <E1g6QWM-0003zv-MF@usper.debian.org>

torbrowser-launcher_0.3.0-1~exp2_amd64.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.3.0-1~exp2.dsc
  torbrowser-launcher_0.3.0-1~exp2.debian.tar.xz
  torbrowser-launcher_0.3.0-1~exp2_amd64.buildinfo
  torbrowser-launcher_0.3.0-1~exp2_amd64.deb

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sun Sep 30 02:35:55 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 30 Sep 2018 01:35:55 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.3.0-1~exp2_amd64.changes ACCEPTED into experimental
Message-ID: <E1g6QeJ-000BYY-LC@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sun, 30 Sep 2018 10:20:22 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source amd64
Version: 0.3.0-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.3.0-1~exp2) experimental; urgency=medium
 .
   * debian/copyright:
     - Add comment section to explain why this is contrib package,
       which comforts lintian.
   * debian/patches:
     - Cherry-pick upstream patch to update Tor Browser Developers
       public key.
Checksums-Sha1:
 1fb42589c29aaae5e90c3c102a9096648a00f02b 2194 torbrowser-launcher_0.3.0-1~exp2.dsc
 61e88d1eb8dca806b1f7ec975428a18edacc509c 22752 torbrowser-launcher_0.3.0-1~exp2.debian.tar.xz
 19ed4a51f8bb4250bae0f9aa9de3f82bb06e21dd 6552 torbrowser-launcher_0.3.0-1~exp2_amd64.buildinfo
 ac32c0c9343d3ffd91bcf71af30f2cc8ada73cc8 65126 torbrowser-launcher_0.3.0-1~exp2_amd64.deb
Checksums-Sha256:
 d2950983c9745e00f5ad1c0ffc77b911d631e112bb8bdfcf0a9f36f38488448c 2194 torbrowser-launcher_0.3.0-1~exp2.dsc
 207e096dfda3e6b608591a1d0bcbae4787fd5173792a81bd8c95a6d09c6068de 22752 torbrowser-launcher_0.3.0-1~exp2.debian.tar.xz
 c86c4a95efea206df79ee2a0bfa665e5e1c2fcfe12659ed1acb072dd9b507747 6552 torbrowser-launcher_0.3.0-1~exp2_amd64.buildinfo
 258f02e08ca2b947d6d864d2a66bab630511f825052d8fca04782e77d0825d7d 65126 torbrowser-launcher_0.3.0-1~exp2_amd64.deb
Files:
 9b9ffb88214120b75d8e9810c4de2d1a 2194 contrib/web optional torbrowser-launcher_0.3.0-1~exp2.dsc
 0d845baa4e7b4c6975b9b9e98cf643e7 22752 contrib/web optional torbrowser-launcher_0.3.0-1~exp2.debian.tar.xz
 a74a5187dca100552e3fe823d6a21ce6 6552 contrib/web optional torbrowser-launcher_0.3.0-1~exp2_amd64.buildinfo
 c8558681fddb5b80af5dc4742e54d451 65126 contrib/web optional torbrowser-launcher_0.3.0-1~exp2_amd64.deb

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAluwJUUQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qC3+D/9Aggsqx+XKMLJTf4/ck8DJw9R3NJgV3Grn
hJIyLxp6pLxBb5ioOMKe0+T6sWzLHKwKsA1YIve4GnHfyFjIVnbtGGcLX4hY9cLd
tJQX6Fr6LMB0Z44Sv8gjoBMWqlE3SMUP/QupoOaUHb4Ek5hx4kB30HdHzMA9M8kh
Jyo/FlPS+wd0t+1vtSbD/NU0RN8X5O6TMjiumWiwdsQC1jdHipohqbQlkLon+/5R
KlwSpj4U02hfjQnbqYSYpP8ZFwad7EdfUKWEy8nPydNT/vQLkIuCVWn12cGVYMtw
Aj+MegiGW7nRIH+dIi/Tv8P4fnAOpo44quAwwPA3rHV/Ka3D2Es2cDhVL+DBeuOW
JgBilC+oSppjZ3u38U77B5Ndtt8UtbkG4r0hH0xvnh4wvm7dkOXm6BDMSbsG1wHT
l/CGPPWD8aybUJNyah1TQCLBt05Hmw0iJZfOD8Rw4NN9Vdpow1R17sabiWfjx2L2
APatqVHrnIhC1qUOq2VEiUxWAmYPbv0m8FtFSF+7fiZIVb5IoogByA2QbzJRnlin
HcKkSRyYtPNvCCJOMIh9LbWcsw7bkmd0+ls/043W0dcqgqTAnF2NDqALf0X1fWjL
VmfufW0KGSYN4PyBa50ih45GKpgf3uPMucx2SqXioeVBZn/X7Lzl2WXTQCRFh5Wl
aACocSdtqA==
=nWNm
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From noreply at release.debian.org  Mon Oct  1 05:39:43 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Mon, 01 Oct 2018 04:39:43 +0000
Subject: [Pkg-privacy-maintainers] torbrowser-launcher 0.2.9-6 MIGRATED to
 testing
Message-ID: <E1g6pzj-0002yO-3b@respighi.debian.org>

FYI: The status of the torbrowser-launcher source package
in Debian's testing distribution has changed.

  Previous version: 0.2.9-5
  Current version:  0.2.9-6

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From shirishag75 at gmail.com  Sun Sep 30 09:41:25 2018
From: shirishag75 at gmail.com (=?UTF-8?B?c2hpcmlzaCDgpLbgpL/gpLDgpYDgpLc=?=)
Date: Sun, 30 Sep 2018 14:11:25 +0530
Subject: [Pkg-privacy-maintainers] most of the bugs on torbrowser-launcher
 can be closed and need fixing of mail addresses in the wiki page.
Message-ID: <CADdDZRnf8c=92xjwwNVtKjDv0rx-11f-VBpUhmdNweTFir48fw@mail.gmail.com>

Dear all,

First of all a big thank you for all the present and past maintainer,
developers, uploaders who worked on torbrowser.  Even though the
torbrowser or the CLI interface broke now and then, still it has
survived and thrived.

Now please CC me if responding as Im not subscribed to the mailing list.

First of all on the wiki page the e-mail address given is plain wrong,
it should be pkg-privacy-maintainers at alioth-lists.debian.net as the
alioth service is retired unless you/we have a resolver that does the
changes the address from
pkg-privacy-maintainers at lists.alioth.debian.org to
pkg-privacy-maintainers at alioth-lists.debian.net while morally even
doing that is wrong IMO.

The second thing which I don't really understand is not also
understood from https://tracker.debian.org/pkg/torbrowser-launcher
there seems to be no binary in stable/contrib . I am sure there are
valid reasons for it, if somebody can share the reasons for the same
would be nice.

Lastly, most of the bugs in torbrowser-launcher
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=torbrowser-launcher
seems to be resolved,  at least all the bugs which are at -

https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=torbrowser-launcher#_0_3_4

and

https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=torbrowser-launcher#_0_4_3

It would be nice to close them .  Most people have commented the same
but not closed them . Could somebody do the same ?

I could close them on behalf of torbrowser team's behalf but unsure
about what the close message should be.

Look forward and thank  you again for maintaining torbrowser-launcher.

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8


From t8mf4nu6lizp at canaglie.net  Tue Oct  2 09:34:39 2018
From: t8mf4nu6lizp at canaglie.net (Mikko =?UTF-8?Q?Viinam=C3=A4ki?=)
Date: Tue, 2 Oct 2018 11:34:39 +0300
Subject: [Pkg-privacy-maintainers] Bug#910062: torbrowser-launcher will not
 open URL argument
Message-ID: <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net>

Package: torbrowser-launcher
Version: 0.2.9-6~bpo9+1

Provided an URL argument it will not point tor browser to the URL 
requested. I.e.

$ torbrowser-launcher https://debian.org

will not open the said page.


From intrigeri at debian.org  Tue Oct  2 13:59:11 2018
From: intrigeri at debian.org (intrigeri)
Date: Tue, 02 Oct 2018 07:59:11 -0500
Subject: [Pkg-privacy-maintainers] Bug#910062: torbrowser-launcher will not
 open URL argument
In-Reply-To: <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net>
References: <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net>
 <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net>
Message-ID: <85a7nwcxnk.fsf@boum.org>

Control: tag -1 + wishlist
Control: tag -1 + upstream

Mikko Viinamäki:
> Provided an URL argument it will not point tor browser to the URL 
> requested.

Indeed. Can you please check if there's already an upstream feature
request about this, and if not, create one? Thanks!


From owner at bugs.debian.org  Tue Oct  2 14:03:03 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 02 Oct 2018 13:03:03 +0000
Subject: [Pkg-privacy-maintainers] Processed (with 1 error): Re: Bug#910062:
 torbrowser-launcher will not open URL argument
References: <85a7nwcxnk.fsf@boum.org>
 <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net>
Message-ID: <handler.s.B910062.15384851575828.transcript@bugs.debian.org>

Processing control commands:

> tag -1 + wishlist
Unknown tag/s: wishlist.
Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye bullseye-ignore.

Bug #910062 [torbrowser-launcher] torbrowser-launcher will not open URL argument
Requested to add no tags; doing nothing.
> tag -1 + upstream
Bug #910062 [torbrowser-launcher] torbrowser-launcher will not open URL argument
Added tag(s) upstream.

-- 
910062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910062
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From owner at bugs.debian.org  Tue Oct  2 14:09:03 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 02 Oct 2018 13:09:03 +0000
Subject: [Pkg-privacy-maintainers] Processed: severity of 910062 is wishlist
References: <1538485551-3773-bts-intrigeri@debian.org>
Message-ID: <handler.s.C.15384855548530.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> severity 910062 wishlist
Bug #910062 [torbrowser-launcher] torbrowser-launcher will not open URL argument
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
910062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910062
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From rogershimizu at gmail.com  Tue Oct  2 14:16:20 2018
From: rogershimizu at gmail.com (Roger Shimizu)
Date: Tue, 2 Oct 2018 22:16:20 +0900
Subject: [Pkg-privacy-maintainers] Bug#910062: torbrowser-launcher will not
 open URL argument
In-Reply-To: <85a7nwcxnk.fsf@boum.org>
References: <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net>
 <85a7nwcxnk.fsf@boum.org> <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net>
Message-ID: <CAEQ9gEngf7c+SywVZdrrpyCB31-gFZv5n5piLpsC2P4rJx41xA@mail.gmail.com>

On Tue, Oct 2, 2018 at 10:03 PM intrigeri <intrigeri at debian.org> wrote:
> Mikko Viinamäki:
> > Provided an URL argument it will not point tor browser to the URL
> > requested.
>
> Indeed. Can you please check if there's already an upstream feature
> request about this, and if not, create one? Thanks!

I think it's a duplicate of #821093 [1].

[1] https://bugs.debian.org/821093

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


From owner at bugs.debian.org  Tue Oct  2 14:39:04 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 02 Oct 2018 13:39:04 +0000
Subject: [Pkg-privacy-maintainers] Bug#900405: marked as done
 (torbrowser-launcher: conffiles not removed)
References: <CAEQ9gEmy0ikRNX2vpSE+SDGamhzcw3e8Td4d=-NiJg2tFwRMcw@mail.gmail.com>
 <4d439332ab0d15cef094358087f6d7730b37f502.camel@debian.org>
Message-ID: <handler.900405.D900405.153848740922069.ackdone@bugs.debian.org>

Your message dated Tue, 2 Oct 2018 22:36:34 +0900
with message-id <CAEQ9gEmy0ikRNX2vpSE+SDGamhzcw3e8Td4d=-NiJg2tFwRMcw at mail.gmail.com>
and subject line Re: [Pkg-privacy-maintainers] Bug#900405: torbrowser-launcher: conffiles not removed
has caused the Debian Bug report #900405,
regarding torbrowser-launcher: conffiles not removed
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 at bugs.debian.org
immediately.)


-- 
900405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900405
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Paul Wise <pabs at debian.org>
Subject: torbrowser-launcher: conffiles not removed
Date: Wed, 30 May 2018 17:49:31 +0800
Size: 5345
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181002/48f223a3/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Re: [Pkg-privacy-maintainers] Bug#900405: torbrowser-launcher: conffiles not removed
Date: Tue, 2 Oct 2018 22:36:34 +0900
Size: 3914
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181002/48f223a3/attachment-0001.mht>

From micah at micahflee.com  Tue Oct  2 23:12:26 2018
From: micah at micahflee.com (Micah Lee)
Date: Tue, 2 Oct 2018 15:12:26 -0700
Subject: [Pkg-privacy-maintainers] Bug#910062: torbrowser-launcher will not
 open URL argument
In-Reply-To: <85a7nwcxnk.fsf@boum.org>
References: <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net>
 <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net> <85a7nwcxnk.fsf@boum.org>
 <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net>
Message-ID: <52cc2334-5e69-85a2-77ae-47d37f3c2e94@micahflee.com>

On 10/2/18 5:59 AM, intrigeri wrote:
> Indeed. Can you please check if there's already an upstream feature
> request about this, and if not, create one? Thanks!

A long time ago torbrowser-launcher could accept URLs as arguments, but
then a change in Tor Browser itself broke that feature, so I removed it.

Here is a recent pull request that tried to reimplement it, but I closed
without merging after explaining the issue:

https://github.com/micahflee/torbrowser-launcher/pull/274

I'm not sure if there's an upstream-upstream ticket for Tor Browser
itself about this, but that would be the place to start.


From t8mf4nu6lizp at canaglie.net  Wed Oct  3 01:30:52 2018
From: t8mf4nu6lizp at canaglie.net (Mikko =?UTF-8?Q?Viinam=C3=A4ki?=)
Date: Wed, 3 Oct 2018 03:30:52 +0300
Subject: [Pkg-privacy-maintainers] Bug#910062: torbrowser-launcher will not
 open URL argument
In-Reply-To: <52cc2334-5e69-85a2-77ae-47d37f3c2e94@micahflee.com>
References: <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net>
 <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net> <85a7nwcxnk.fsf@boum.org>
 <52cc2334-5e69-85a2-77ae-47d37f3c2e94@micahflee.com>
 <a403478d-4d2b-cff1-a320-5044fb1386e9@canaglie.net>
Message-ID: <c02a17ec-91a7-5a20-6fd1-fec30395f54e@canaglie.net>

On 10/3/18 1:12 AM, Micah Lee wrote:
 > Here is a recent pull request that tried to reimplement it
> https://github.com/micahflee/torbrowser-launcher/pull/274

Hello and thanks alot, this is all I need (because I know tor browser 
won't be running.)

> I'm not sure if there's an upstream-upstream ticket for Tor Browser
> itself about this, but that would be the place to start.

I did search on the tor bug tracker but couldn't find anything that 
looked like this issue. However I did not file a new bug because I 
didn't know how to word it.


From georg at riseup.net  Thu Oct  4 21:18:49 2018
From: georg at riseup.net (Georg Faerber)
Date: Thu, 4 Oct 2018 20:18:49 +0000
Subject: [Pkg-privacy-maintainers] Joining the team to package mat2
In-Reply-To: <20180419162209.GM9503@debian>
References: <20180419162209.GM9503@debian>
Message-ID: <20181004201849.GJ7027@debian>

Hi all,

On 18-04-19 18:22:09, Georg Faerber wrote:
> We'll start working on this during MiniDebConf in Hamburg mid of May.

Well, it took a while, but the initial upload is now upcoming, finally.

Working together with upstream is, and was, a pretty good experiences, a
lot of joy included.. ;) Looking forward!

Cheers,
Georg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181004/c45d3f0c/attachment.sig>

From ftpmaster at ftp-master.debian.org  Fri Oct  5 10:34:29 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Fri, 05 Oct 2018 09:34:29 +0000
Subject: [Pkg-privacy-maintainers] Processing of mat2_0.4.0-1_amd64.changes
Message-ID: <E1g8MVB-0000wV-7Q@usper.debian.org>

mat2_0.4.0-1_amd64.changes uploaded successfully to localhost
along with the files:
  mat2_0.4.0-1.dsc
  mat2_0.4.0.orig.tar.xz
  mat2_0.4.0-1.debian.tar.xz
  mat2_0.4.0-1_all.deb
  mat2_0.4.0-1_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Fri Oct  5 10:50:33 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Fri, 05 Oct 2018 09:50:33 +0000
Subject: [Pkg-privacy-maintainers] mat2_0.4.0-1_amd64.changes is NEW
Message-ID: <E1g8Mkj-0008m5-9z@fasolo.debian.org>

binary:mat2 is NEW.
binary:mat2 is NEW.
source:mat2 is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
     or https://ftp-master.debian.org/backports-new.html for *-backports


From ftpmaster at ftp-master.debian.org  Fri Oct  5 18:00:10 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Fri, 05 Oct 2018 17:00:10 +0000
Subject: [Pkg-privacy-maintainers] mat2_0.4.0-1_amd64.changes ACCEPTED into
 unstable, unstable
Message-ID: <E1g8TSU-000AFn-Ug@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Thu, 04 Oct 2018 23:39:09 +0200
Source: mat2
Binary: mat2
Architecture: source all
Version: 0.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Georg Faerber <georg at riseup.net>
Description:
 mat2       - Metadata anonymisation toolkit v2
Closes: 898622
Changes:
 mat2 (0.4.0-1) unstable; urgency=medium
 .
   [ Georg Faerber + Jonas Meurer ]
   * Initial release. (Closes: #898622)
Checksums-Sha1:
 01729af1bfc0d63dd4b68855b4a446dc830ef366 2134 mat2_0.4.0-1.dsc
 0ad9493d210b6094e900911fc8a73b029ef08117 3439724 mat2_0.4.0.orig.tar.xz
 4887450f04cf3eda84bf99904a29b6b79a969216 8312 mat2_0.4.0-1.debian.tar.xz
 bc55ce12c8088d9b3966d2707ccd3b6c0481e059 19080 mat2_0.4.0-1_all.deb
 c7ed44f314aa720a9cdff6d1ffe874f456c63c4c 7410 mat2_0.4.0-1_amd64.buildinfo
Checksums-Sha256:
 324bac896fc189c0f9027e23c3d06b0cc2d59341ad9034bfa32d5afa5974f2dd 2134 mat2_0.4.0-1.dsc
 8c9e1ac7f1bfb66dffc30d4b511763ec68a9378c7aa9a2318688f18a9f1b117c 3439724 mat2_0.4.0.orig.tar.xz
 9c37adb88504d1d3bf716eabbd7f2e309c0289a73cd12f7319304492809f8793 8312 mat2_0.4.0-1.debian.tar.xz
 e186effab3dbe55749e396d721b5ef01386b4c83a4bdc79f1f0f41a4b2c0ae9e 19080 mat2_0.4.0-1_all.deb
 73c5d99c956ce65a9bb322206fd2fa5ea61a776f2f24816360d48b2a016d039e 7410 mat2_0.4.0-1_amd64.buildinfo
Files:
 c770da086bcf4d97f2cd7f153b5633eb 2134 utils optional mat2_0.4.0-1.dsc
 f1a43cae1e8011d4c25dcffdcfedb5e6 3439724 utils optional mat2_0.4.0.orig.tar.xz
 6252fecbfc92b1b94c79e00a0af65178 8312 utils optional mat2_0.4.0-1.debian.tar.xz
 ab2ebc99c789452e9ea172aa8fc95242 19080 utils optional mat2_0.4.0-1_all.deb
 0dccc21c255dbe57f2ad113507fbda13 7410 utils optional mat2_0.4.0-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEELIzSg9Pv30M4kOeDUmLn/0kQSf4FAlu3LwgACgkQUmLn/0kQ
Sf7bcA/+NBBRa9uCmfikY7axXC7hD2H4DefaAv/bQ1Mn8d+Q2Pkjn9wshXqe0FIv
JKRhZyPWhIWZ9DQnuqrSTm4DOnr3AVFFvaSL4rWQgmFQ9jJrnWiGG+1uE+h70o41
cD3jt3ggUUahZa/KDMUJixpUZ9ZcwdcNzpbqtiXNPTpqw1t2oVrC3H6qY7iDMjSr
KRZKqbJHHNt5f6wgHU8I8u8kX4krEm2UQHQqFRKW+av2A23SH15JN7TrR1cyf5Lz
+M/jIriMGSpo7o9uX/wherkD6MuYN4iEph554tk/OvTUgggHQs84HdMf0ttVH6W8
FkoAezDu0CDuvaYwEo6au0jpiCGVVZDTO+S2usWPRNqcoHLs8KRVdknjZMm2HXlR
Kk0nXG88C1z3l2TQA32ZqRkASEH/Zf1h8q0HGwCqK44WlhBZ7eCQiI7k0XVgwmHJ
Ss6dhIv1FiHHACr6M/jCoyvsyhm78N3ET2RxV0aFVRveONK4yxyC2SddxPL/lLGJ
5LjqqVmJkHZB/cxkT4ALuobEYqB/WLXdl4uQBoCsDMqipWNfqTinDXVMSzcnZHM8
j+4Q+4v4BXRQ+jLR6gtydstGuhq7kncR8yTMToIPjomHz2JX3KblXwfwL/adyMhR
fYKGq6SJ0HG1cbeHg/pdCGiF6K5P0QlNsHzNbtezwBaSEFXE/i4=
=XYxg
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From intrigeri at debian.org  Sun Oct  7 09:16:41 2018
From: intrigeri at debian.org (intrigeri at debian.org)
Date: Sun, 07 Oct 2018 10:16:41 +0200
Subject: [Pkg-privacy-maintainers] Bug#910491: mat2: Please package the
 Nautilus extension
Message-ID: <85ftxi6uja.fsf@boum.org>

Package: mat2
Version: 0.4.0-1
Severity: wishlist

Hi,

I'm filing this bug mostly to document the current state of things.
This is currently blocked by #907591.

Cheers,
-- 
intrigeri


From owner at bugs.debian.org  Sun Oct  7 09:27:04 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sun, 07 Oct 2018 08:27:04 +0000
Subject: [Pkg-privacy-maintainers] Processed: block 910491 with 907591
References: <1538900565-119-bts-intrigeri@debian.org>
Message-ID: <handler.s.C.15389005727566.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> block 910491 with 907591
Bug #910491 [mat2] mat2: Please package the Nautilus extension
910491 was not blocked by any bugs.
910491 was not blocking any bugs.
Added blocking bug(s) of 910491: 907591
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
910491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910491
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From intrigeri at debian.org  Sun Oct  7 09:31:13 2018
From: intrigeri at debian.org (intrigeri)
Date: Sun, 07 Oct 2018 10:31:13 +0200
Subject: [Pkg-privacy-maintainers] Bug#910493: Handle transition from MAT to
 MAT2
In-Reply-To: <85h8m9ijcs.fsf@boum.org>
Message-ID: <858t3a6tv2.fsf@boum.org>

Package: mat2
Version: 0.4.0-1
Severity: normal

Hi,

let's discuss how we'll be handling the transition from MAT to MAT2
in Buster. My goal here is to avoid users keeping using the
deprecated, unmaintained MAT v1, and to nicely transition them to the
new MAT2 implementation.

As I wrote on the ITP (trimming down ideas that don't make sense
anymore):

intrigeri:
> What matters to me is the users' perspective. I think we should
> provide a clear, unambiguous transition path and avoid leaking
> technical details to users. So once MAT2 reaches feature parity with
> MAT (I think the only real blocker is the lack of a Nautilus
> extension; MAT v1's seems to be broken on sid currently but it has
> a GUI which mitigates that problem) I think we should:

>  - Have mat2 conflicts+replaces mat, remove mat from testing+sid,
>    and ship a transitional package called mat that pulls mat2 in.

IMO we should do that as soon as mat2 installs the Nautilus extension
(#910491).

Does this make sense to you? Is there a better way to handle this?

Cheers!
-- 
intrigeri


From owner at bugs.debian.org  Sun Oct  7 09:39:04 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sun, 07 Oct 2018 08:39:04 +0000
Subject: [Pkg-privacy-maintainers] Processed: block 910493 with 910491
References: <1538901308-1529-bts-intrigeri@debian.org>
Message-ID: <handler.s.C.153890131413985.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> block 910493 with 910491
Bug #910493 [mat2] Handle transition from MAT to MAT2
910493 was not blocked by any bugs.
910493 was not blocking any bugs.
Added blocking bug(s) of 910493: 910491
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
910493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910493
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From jonas at freesources.org  Sun Oct  7 19:07:33 2018
From: jonas at freesources.org (Jonas Meurer)
Date: Sun, 7 Oct 2018 20:07:33 +0200
Subject: [Pkg-privacy-maintainers] Bug#910493: Handle transition from MAT to
 MAT2
In-Reply-To: <858t3a6tv2.fsf@boum.org>
References: <858t3a6tv2.fsf@boum.org> <858t3a6tv2.fsf@boum.org>
Message-ID: <7fc9c35d-b572-06b7-be9b-6464f5f7c71f@freesources.org>

Hi intrigeri,

Am 07.10.2018 um 10:31 schrieb intrigeri:
> let's discuss how we'll be handling the transition from MAT to MAT2
> in Buster. My goal here is to avoid users keeping using the
> deprecated, unmaintained MAT v1, and to nicely transition them to the
> new MAT2 implementation.

Full ack. Thanks for bringing this up.

> As I wrote on the ITP (trimming down ideas that don't make sense
> anymore):
> 
> intrigeri:
>> What matters to me is the users' perspective. I think we should
>> provide a clear, unambiguous transition path and avoid leaking
>> technical details to users. So once MAT2 reaches feature parity with
>> MAT (I think the only real blocker is the lack of a Nautilus
>> extension; MAT v1's seems to be broken on sid currently but it has
>> a GUI which mitigates that problem) I think we should:
> 
>>  - Have mat2 conflicts+replaces mat, remove mat from testing+sid,
>>    and ship a transitional package called mat that pulls mat2 in.
> 
> IMO we should do that as soon as mat2 installs the Nautilus extension
> (#910491).
> 
> Does this make sense to you? Is there a better way to handle this?

The main advantage of mat over mat2 I know of is the GUI. But since mat
is broken and should no longer be used for security reasons, my
suggestion would be to ignore this advantage and go ahead with the
transition exactly the way you described it.

Cheers
 jonas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181007/f463e199/attachment.sig>

From jonas at freesources.org  Sun Oct  7 19:07:33 2018
From: jonas at freesources.org (Jonas Meurer)
Date: Sun, 7 Oct 2018 20:07:33 +0200
Subject: [Pkg-privacy-maintainers] Bug#910493: Handle transition from MAT to
 MAT2
In-Reply-To: <858t3a6tv2.fsf@boum.org>
References: <858t3a6tv2.fsf@boum.org> <858t3a6tv2.fsf@boum.org>
Message-ID: <7fc9c35d-b572-06b7-be9b-6464f5f7c71f@freesources.org>

Hi intrigeri,

Am 07.10.2018 um 10:31 schrieb intrigeri:
> let's discuss how we'll be handling the transition from MAT to MAT2
> in Buster. My goal here is to avoid users keeping using the
> deprecated, unmaintained MAT v1, and to nicely transition them to the
> new MAT2 implementation.

Full ack. Thanks for bringing this up.

> As I wrote on the ITP (trimming down ideas that don't make sense
> anymore):
> 
> intrigeri:
>> What matters to me is the users' perspective. I think we should
>> provide a clear, unambiguous transition path and avoid leaking
>> technical details to users. So once MAT2 reaches feature parity with
>> MAT (I think the only real blocker is the lack of a Nautilus
>> extension; MAT v1's seems to be broken on sid currently but it has
>> a GUI which mitigates that problem) I think we should:
> 
>>  - Have mat2 conflicts+replaces mat, remove mat from testing+sid,
>>    and ship a transitional package called mat that pulls mat2 in.
> 
> IMO we should do that as soon as mat2 installs the Nautilus extension
> (#910491).
> 
> Does this make sense to you? Is there a better way to handle this?

The main advantage of mat over mat2 I know of is the GUI. But since mat
is broken and should no longer be used for security reasons, my
suggestion would be to ignore this advantage and go ahead with the
transition exactly the way you described it.

Cheers
 jonas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181007/f463e199/attachment-0001.sig>

From ftpmaster at ftp-master.debian.org  Sun Oct  7 20:02:35 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 07 Oct 2018 19:02:35 +0000
Subject: [Pkg-privacy-maintainers] Processing of mat2_0.4.0-2_source.changes
Message-ID: <E1g9EK3-0003kK-WD@usper.debian.org>

mat2_0.4.0-2_source.changes uploaded successfully to localhost
along with the files:
  mat2_0.4.0-2.dsc
  mat2_0.4.0-2.debian.tar.xz
  mat2_0.4.0-2_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sun Oct  7 20:20:51 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 07 Oct 2018 19:20:51 +0000
Subject: [Pkg-privacy-maintainers] mat2_0.4.0-2_source.changes REJECTED
Message-ID: <E1g9Ebj-000Ge3-LJ@fasolo.debian.org>



mat2_0.4.0-2.dsc: Invalid size hash for mat2_0.4.0.orig.tar.xz:
According to the control file the size hash should be 3439728,
but mat2_0.4.0.orig.tar.xz has 3439724.

If you did not include mat2_0.4.0.orig.tar.xz in your upload, a different version
might already be known to the archive software.



===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.



From ftpmaster at ftp-master.debian.org  Sun Oct  7 20:38:38 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 07 Oct 2018 19:38:38 +0000
Subject: [Pkg-privacy-maintainers] Processing of mat2_0.4.0-2_source.changes
Message-ID: <E1g9Esw-0006QO-PR@usper.debian.org>

mat2_0.4.0-2_source.changes uploaded successfully to localhost
along with the files:
  mat2_0.4.0-2.dsc
  mat2_0.4.0-2.debian.tar.xz
  mat2_0.4.0-2_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sun Oct  7 20:49:46 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 07 Oct 2018 19:49:46 +0000
Subject: [Pkg-privacy-maintainers] mat2_0.4.0-2_source.changes REJECTED
Message-ID: <E1g9F3i-0006tI-Qj@fasolo.debian.org>



mat2_0.4.0-2.dsc: Invalid size hash for mat2_0.4.0.orig.tar.xz:
According to the control file the size hash should be 3439728,
but mat2_0.4.0.orig.tar.xz has 3439724.

If you did not include mat2_0.4.0.orig.tar.xz in your upload, a different version
might already be known to the archive software.



===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.



From ftpmaster at ftp-master.debian.org  Sun Oct  7 22:42:09 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 07 Oct 2018 21:42:09 +0000
Subject: [Pkg-privacy-maintainers] Processing of mat2_0.4.0-2_source.changes
Message-ID: <E1g9GoT-0005oe-5P@usper.debian.org>

mat2_0.4.0-2_source.changes uploaded successfully to localhost
along with the files:
  mat2_0.4.0-2.dsc
  mat2_0.4.0-2.debian.tar.xz
  mat2_0.4.0-2_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sun Oct  7 22:51:42 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 07 Oct 2018 21:51:42 +0000
Subject: [Pkg-privacy-maintainers] mat2_0.4.0-2_source.changes ACCEPTED into
 unstable
Message-ID: <E1g9Gxi-0003zL-2t@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sun, 07 Oct 2018 18:36:57 +0000
Source: mat2
Binary: mat2
Architecture: source
Version: 0.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Georg Faerber <georg at riseup.net>
Description:
 mat2       - Metadata anonymisation toolkit v2
Closes: 910376
Changes:
 mat2 (0.4.0-2) unstable; urgency=medium
 .
   [ Jonas Meurer ]
   * d/copyright:
     * Explicitly list copyright holders for the mat2 logo. (Closes: #910376)
Checksums-Sha1:
 90b905b87bd405e18205961241397a26900a09c3 2134 mat2_0.4.0-2.dsc
 7ae3a0686fcb7e41318334322852caef781764ee 8412 mat2_0.4.0-2.debian.tar.xz
 681d191b8a3f69d1c0ee1ae227cc58b2f429aa67 7410 mat2_0.4.0-2_amd64.buildinfo
Checksums-Sha256:
 a96385edbdf74cffbb3332ee514fe62db2d6836917c0398efc94795b87318b12 2134 mat2_0.4.0-2.dsc
 e34822390f9eb9d76d6de970ebe5e9dfcaaf920bc62912025ca564c12be177c0 8412 mat2_0.4.0-2.debian.tar.xz
 f0c0b9f092b197533b3976e40eca438b6e6e3fecd60eea76053982daa67465ee 7410 mat2_0.4.0-2_amd64.buildinfo
Files:
 37823a01befbaeee069f8e9b26356bc5 2134 utils optional mat2_0.4.0-2.dsc
 4ebdc05a8fd7c530b05a7ee3b2a6e3d3 8412 utils optional mat2_0.4.0-2.debian.tar.xz
 fa8ce649ae4094b000b0b69f6c39042d 7410 utils optional mat2_0.4.0-2_amd64.buildinfo

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

iQIzBAEBCgAdFiEELIzSg9Pv30M4kOeDUmLn/0kQSf4FAlu6fKAACgkQUmLn/0kQ
Sf6ulQ//V/xGnoB1z7vrSdiqUPEy+Kmj7FKJbS0wQSt5ya+qBjT3hJQhss6tz5aU
M6kO+DMyCO7glW4m8vZv5/Si9RzCXUmLAH8poZv41mYX6Cn8wtUynnCx7XbOSopi
OMvFgzx0QtzFY8Waghg9Zi1XhwXn9nnnZFr4VSacFnxapZ/cNISSqrAppbHsqcN5
ydq0ZGFEgydLcfH1KN5tC26PUiP5IznCxQ3B6aoCidAB8so28rOd/1f5xm87w5L4
zpCqWbh+vR19hFckYF2BEi4MQYkCE3U5nnCknJEarYVY7q+HIk9lmKjOpDnqNmAj
38vwDh89SUtr4RXV3Qy1Pfwkms9T566yGzjKELWxePGo97xncucj9BCgC4tbqTCj
hgVAKDZWEJ99qVGY+yiaYDfPH2mZx06fgnIRs+iZbxuuHifouFRateWkSgz9E2j9
EXHRBn1QOyKOuVeocEuifxYhJeS0JCmqZkeyA6N99gG2rarao85ApWL1OxoEi4C9
Ii8azEEYGF2kkUAgOPNJhjr0qnFnrgY8X+MYHd9qy3xZP7Ic3Z4XlDN+SP1WJTFg
BqJSl1ylb1zZphQEXSNr8NHBBNll21fJE8ORzp9vzxmflZ9qsFs2GCvoAriEyEcX
Fb4ZoEar8A4aiECFERu1n64IFmxaLJe0Mscaf/g1FXEWHShavtw=
=HoI3
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Mon Oct  8 10:19:23 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 08 Oct 2018 09:19:23 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbirdy_0.2.6-1_amd64.changes
Message-ID: <E1g9RhD-0002vv-A7@usper.debian.org>

torbirdy_0.2.6-1_amd64.changes uploaded successfully to localhost
along with the files:
  torbirdy_0.2.6-1.dsc
  torbirdy_0.2.6.orig.tar.gz
  torbirdy_0.2.6-1.debian.tar.xz
  torbirdy_0.2.6-1_amd64.buildinfo
  xul-ext-torbirdy_0.2.6-1_all.deb

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Mon Oct  8 10:36:57 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 08 Oct 2018 09:36:57 +0000
Subject: [Pkg-privacy-maintainers] torbirdy_0.2.6-1_amd64.changes ACCEPTED
 into unstable
Message-ID: <E1g9RyD-0003O9-91@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Mon, 08 Oct 2018 10:37:01 +0200
Source: torbirdy
Binary: xul-ext-torbirdy
Architecture: source all
Version: 0.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Ulrike Uhlig <ulrike at debian.org>
Description:
 xul-ext-torbirdy - configures and enhances various Mozilla birds for anonymity use
Changes:
 torbirdy (0.2.6-1) unstable; urgency=medium
 .
   * New upstream version:
     - Improve compatibility with Thunderbird 60.
Checksums-Sha1:
 e9ec2f527a20e623a8b79ff756cdb7f68b3454ca 2021 torbirdy_0.2.6-1.dsc
 be3967ccb099acda9f181fc7ae1ceb06d4c7a757 160598 torbirdy_0.2.6.orig.tar.gz
 d4e9aca265a7d26d81c13ef42b426df6739d3fda 13080 torbirdy_0.2.6-1.debian.tar.xz
 423154c2e3b19ec6f6261270723c2e7db259523c 7175 torbirdy_0.2.6-1_amd64.buildinfo
 483847a1882f52937cdd73f054b00d57c1c054df 136094 xul-ext-torbirdy_0.2.6-1_all.deb
Checksums-Sha256:
 84c740b44560e5d79e6cd5dba5d962c5e9a951ed2a4d574e38d5d53488a29c37 2021 torbirdy_0.2.6-1.dsc
 132a12cea105eaaee9e61b3b76b30e491498f9a894f4be1bd3720e41732e374b 160598 torbirdy_0.2.6.orig.tar.gz
 cfe6c271d8d75b5adeab9dac9ed5466ad1af7b9e42cdeacac543913817105613 13080 torbirdy_0.2.6-1.debian.tar.xz
 46fa43c02bb39b7194c451974a912936a9f6298454c53519542ca58a8b7942c5 7175 torbirdy_0.2.6-1_amd64.buildinfo
 7b0af20810ca73d833ed2291d91957dd7d8ee0d6cc0fd1c6d7ed034e63a5ee41 136094 xul-ext-torbirdy_0.2.6-1_all.deb
Files:
 c6670b3ebfe5ad70ac5e2ba5addc2eef 2021 web optional torbirdy_0.2.6-1.dsc
 af73f29fd8dd41dfb7e771b8dc6ffe5b 160598 web optional torbirdy_0.2.6.orig.tar.gz
 5b8fde602aa5fc621ecc2f05de0b0745 13080 web optional torbirdy_0.2.6-1.debian.tar.xz
 dc7a1589a827ad121f8148dc202aed69 7175 web optional torbirdy_0.2.6-1_amd64.buildinfo
 144506ecd7a367bda7c1006b020f4e4e 136094 web optional xul-ext-torbirdy_0.2.6-1_all.deb

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

iQJGBAEBCgAwFiEE7eP0RD800mGVFNeQsUuww42GHPEFAlu7F9ASHHVscmlrZUBk
ZWJpYW4ub3JnAAoJELFLsMONhhzxyVIP/i66hku9c5FcuBWca/NiiUBbWygq7tCi
I7YYx/D1gvUY5a7VyRmGxIExyPcT4IUZW8xkq60PDa/N/1Btj0jvDUshqR6PVJnZ
u/rb+X54c0N4+b4VIgGZG+GsCCJXibWjvnC9ErKsbsxvOhdZLyAKq/c6Lo25tI+F
KoMHBzbm74SoExJO+h44K8LthDv2IjI27mhO+B2IAA/MTUYDz6ZwxsdISzH5PGp8
VLFqOR8V/fRBI6vdEArCM1AC9Fem76QV0fTVhmkEgExf9+pWZVjhAGcch8lmvh4B
aVC99Aeb5uhS7FbUBZ83QWvHjxP/jXOJh18ynRdJQmli1A/h4/ELfEAwgfXGqHUS
NNTGYdjzHsNNDmaO/OMGIkCAvX68yYQA22Iw9aY/ONUSZkGgjZ8sLfQbAajfRJFa
+c/kXhMaTVmE0vxpl49W/Zp0sODU04uMS+kr3wKAbdEH2jp9s6c/4ygxQhPJO1pI
i+mqlIHzFRDsytQ1BzKeEKhshbESqZJbccwtMMHJT4URrxw6mkJrhK/PZbCTiJ3k
gnWA4AbdeoD9szckXXTKXJiInhQoLS5+cbjyg6nWTb/RHAGIdGjxJMjAiIXsmbrc
OkOvquN1feBS1YFRaEl34MDAdVrTbLQx98RGZLycr9DtbgutGM51e0A3ua9A+yjY
3WjGcQw8sdx0
=JHMb
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From dkg at fifthhorseman.net  Mon Oct  8 19:22:25 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Mon, 08 Oct 2018 14:22:25 -0400
Subject: [Pkg-privacy-maintainers] Bug#910493: Bug#910493: Handle transition
 from MAT to MAT2
In-Reply-To: <858t3a6tv2.fsf@boum.org>
References: <858t3a6tv2.fsf@boum.org> <858t3a6tv2.fsf@boum.org>
Message-ID: <87muronvry.fsf@fifthhorseman.net>

On Sun 2018-10-07 10:31:13 +0200, intrigeri wrote:
> intrigeri:
>> What matters to me is the users' perspective. I think we should
>> provide a clear, unambiguous transition path and avoid leaking
>> technical details to users. So once MAT2 reaches feature parity with
>> MAT (I think the only real blocker is the lack of a Nautilus
>> extension; MAT v1's seems to be broken on sid currently but it has
>> a GUI which mitigates that problem) I think we should:
>
>>  - Have mat2 conflicts+replaces mat, remove mat from testing+sid,
>>    and ship a transitional package called mat that pulls mat2 in.
>
> IMO we should do that as soon as mat2 installs the Nautilus extension
> (#910491).
>
> Does this make sense to you? Is there a better way to handle this?

this all looks reasonable to me as well.

thanks for staying on top of it.

       --dkg


From georg at riseup.net  Tue Oct  9 14:25:06 2018
From: georg at riseup.net (Georg Faerber)
Date: Tue, 9 Oct 2018 13:25:06 +0000
Subject: [Pkg-privacy-maintainers] ITP: intel-me-cleaner -- under the
 umbrella of this team?
Message-ID: <20181009132506.GC2137@debian>

Hi all,

I've took over the ITP of intel-me-cleaner [1], after offering help some
months ago.

I thought, this might be a good fit for this team? Any opinions
regarding this?

Cheers,
Georg


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885152
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181009/3b73d35e/attachment.sig>

From intrigeri at debian.org  Tue Oct  9 15:04:15 2018
From: intrigeri at debian.org (intrigeri)
Date: Tue, 09 Oct 2018 16:04:15 +0200
Subject: [Pkg-privacy-maintainers] ITP: intel-me-cleaner -- under the
 umbrella of this team?
In-Reply-To: <20181009132506.GC2137@debian>
References: <20181009132506.GC2137@debian>
Message-ID: <85zhvnusgw.fsf@boum.org>

Hi Georg & team,

Georg Faerber:
> I've took over the ITP of intel-me-cleaner [1], after offering help some
> months ago.

Excellent! \o/

> I thought, this might be a good fit for this team? Any opinions
> regarding this?

Amusingly, this proved to be harder a question to answer than I expected.

At first glance, this package is about security and is relevant to
privacy in the sense that anything else that improves systems security
also improves privacy. So I'm concerned that if we extend the scope of
team-maintained packages this far, way too much software would
arguably become good fit for this team as well, which feels like
a slippery slope. Arguably pkg-security¹ would be a better fit for it.
Now, we already have codecrypt under our team's umbrella so let's not
pretend our scope is very strictly defined :)

Taking a step back, it seems to me that what has glued this team and
the work we've been doing together so far is not as much specific
technical functionality or vague concepts ("privacy" or "anonymity")
as a shared desire/need to care about a bunch of use cases whose
threat model is traditionally not the top priority of a general
purpose distro such as Debian. With this in mind, it seems to me that
some of the threat models in which people will bother using me_cleaner
fit very well into the set of use cases our team is supporting.
So I take back my initial objection to this proposal :)

(Tangentially related: at some point I'd like us to collectively think
about where we should focus our energy. Seeing dkg struggle mostly
alone with Enigmail maintenance is heart-breaking and makes me wish we
could take a step back together and prioritize which parts of the
ecosystem we feel responsible for most.)

[1] https://wiki.debian.org/Teams/pkg-security

Cheers,
-- 
intrigeri


From dkg at fifthhorseman.net  Tue Oct  9 18:12:44 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Tue, 09 Oct 2018 13:12:44 -0400
Subject: [Pkg-privacy-maintainers] ITP: intel-me-cleaner -- under the
 umbrella of this team?
In-Reply-To: <85zhvnusgw.fsf@boum.org>
References: <20181009132506.GC2137@debian> <85zhvnusgw.fsf@boum.org>
Message-ID: <87d0sjm4c3.fsf@fifthhorseman.net>

On Tue 2018-10-09 16:04:15 +0200, intrigeri wrote:
> Georg Faerber:
>> I've took over the ITP of intel-me-cleaner [1], after offering help some
>> months ago.
>
> Excellent! \o/

agreed \o/!!  thank you georg!

> With this in mind, it seems to me that some of the threat models in
> which people will bother using me_cleaner fit very well into the set
> of use cases our team is supporting.  So I take back my initial
> objection to this proposal :)

:) -- i agree with intri that this is a tricky balance.  the traditional
"security" team doesn't look at systemic issues the way this team seems
inclined to look at them.  Rather, they look at very tightly-controlled
notions of a "security vulnerability":

 * does a piece of software do what it claims to do?

 * can untrusted inputs lead to modifications of trusted components?

 * does it leak information it claims to keep confidential?

 * does it correctly represent the security properties of a piece of
   data or a component to the user?

in contrast, the pkg-privacy team seems more interested in
bigger-picture questions, (as well as more opinionated, pro-active
users):

 * does a package help to mitigate unintended information leaks?

 * does a package help people to be indistinguishable from a large mass
   of other users?

 * does a package help in avoiding leaving local state on a machine?

 * does a package help users identify information leaks?

 * does a package modify another package to put it in a more thoughtful
   mode?


Note that you can solve some "security problems" (in the former set) by
changing documentation or intent -- if a word processor doesn't claim
that it keeps the author's name private, then it's not a security
vulnerability to leak the author's name.  With a privacy focus, the
upstream package doesn't get to make that decision.

moreover, privacy is generally an interdependent, interconnected problem
space.  If my privacy and data protection practices are weak, that has
an impact on everyone who i share data with.  So from a privacy
perspective, we can't afford to take a narrow view.

> (Tangentially related: at some point I'd like us to collectively think
> about where we should focus our energy. Seeing dkg struggle mostly
> alone with Enigmail maintenance is heart-breaking and makes me wish we
> could take a step back together and prioritize which parts of the
> ecosystem we feel responsible for most.)

i really appreciated intrigeri's sympathetic ear. it actually helped me
a lot to talk to him (and a few other good people) about the details of
the technical struggles i was going through with enigmail and GnuPG.  I
don't know whether they were in enough detail to be considered "rubber
duck" sessions, but they were certainly useful for me in getting things
organized in my head (as well as a chance to vent about frustrating
technical choices).

You'll be happy to know that i've proposed updates to GnuPG for stretch
(https://bugs.debian.org/910398) that, if accepted by the release team
(or if pushed forward by the security team, despite not fitting narrowly
in the definition of security fixes) should permit inclusion of enigmail
2.0.8 in stretch.

I welcome feedback on that ticket, if folks have the time or inclination
to review it.

To the extent that this team can offer opportunities for mutual support
-- even just in the simple form of listening and asking the right
questions -- i am grateful for it.

     --dkg


From u at 451f.org  Tue Oct  9 14:50:00 2018
From: u at 451f.org (u)
Date: Tue, 09 Oct 2018 13:50:00 +0000
Subject: [Pkg-privacy-maintainers] ITP: intel-me-cleaner -- under the
 umbrella of this team?
In-Reply-To: <20181009132506.GC2137@debian>
References: <20181009132506.GC2137@debian>
Message-ID: <6951710f-5425-4b76-f1ea-5129c0d9571e@451f.org>

Hi Georg!

Georg Faerber:

> I've took over the ITP of intel-me-cleaner [1], after offering help some
> months ago.
> 
> I thought, this might be a good fit for this team? Any opinions
> regarding this?

Fine with me and our policy:
https://salsa.debian.org/pkg-privacy-team/team-processes/blob/master/pkg-privacy-process.mdwn
$3.3

:))))

Cheers!
Ulrike


From reproducible-builds at lists.alioth.debian.org  Wed Oct 10 01:46:55 2018
From: reproducible-builds at lists.alioth.debian.org (Reproducible builds folks)
Date: Wed, 10 Oct 2018 00:46:55 +0000 (UTC)
Subject: [Pkg-privacy-maintainers] pyptlib: status change on
 tests.reproducible-builds.org/debian
Message-ID: <20181010004655.520F01F7D1@jenkins.debian.net>

2018-10-09 17:00 https://tests.reproducible-builds.org/debian/unstable/amd64/pyptlib changed from reproducible -> FTBFS


From noreply at release.debian.org  Wed Oct 10 05:39:19 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Wed, 10 Oct 2018 04:39:19 +0000
Subject: [Pkg-privacy-maintainers] mat2 0.4.0-2 MIGRATED to testing
Message-ID: <E1gA6HH-0006iq-DA@respighi.debian.org>

FYI: The status of the mat2 source package
in Debian's testing distribution has changed.

  Previous version: (not in testing)
  Current version:  0.4.0-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From shirishag75 at gmail.com  Thu Oct 11 20:16:18 2018
From: shirishag75 at gmail.com (shirish =?UTF-8?Q?=E0=A4=B6=E0=A4=BF=E0=A4=B0=E0=A5=80=E0=A4=B7?=)
Date: Fri, 12 Oct 2018 00:46:18 +0530
Subject: [Pkg-privacy-maintainers] Bug#910827: Doing update on
 torbrowser-launcher 0.2.9-6 resulted in not finding profile
Message-ID: <CADdDZR=bvbS0zdbg45obuJ-TXgwTqQrmv8x543aAj5TkUeW0JQ@mail.gmail.com>

Package: torbrowser-launcher
Version: 0.2.9-6
Severity: normal

Dear Maintainer,
I was using torbrowser-launcher and updated it to torbrowser 8.0.2 .
When the torbrowser restarted it gave me a message stating it could
not find my profile.

While I was able to workaround the issue by using -

~/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/start-tor-browser
--verbose

and in a way forcing/seeing that it got correctly updated. After this
I was able to launch using torbrowser-launcher normally as I always do
via

$ $ torbrowser-launcher

I have no clue why I had to use the workaround, please fix so it
doesn't happen again. Many users wouldn't even know what to do.

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (100,
'unstable-debug'), (100, 'experimental-debug'), (100, 'experimental'),
(100, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  gnupg             2.2.10-3
ii  libdbus-glib-1-2  0.110-3
ii  python            2.7.15-3
ii  python-gtk2       2.24.0-5.1+b1
ii  python-lzma       0.5.3-3.1
ii  python-parsley    1.2-1
ii  python-psutil     5.4.6-1+b1
ii  python-twisted    18.7.0-3
ii  python-txsocksx   1.15.0.2-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.4.8-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.13-8
pn  python-pygame  <none>

-- no debconf information

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8


From shirishag75 at gmail.com  Thu Oct 11 20:32:32 2018
From: shirishag75 at gmail.com (shirish =?UTF-8?Q?=E0=A4=B6=E0=A4=BF=E0=A4=B0=E0=A5=80=E0=A4=B7?=)
Date: Fri, 12 Oct 2018 01:02:32 +0530
Subject: [Pkg-privacy-maintainers] Bug#910829: some upstream errors seen via
 --verbose mode via torbrowser-launcher.
Message-ID: <CADdDZR=mvK+L3Cjrw1tEsp7rrSrbD2AyshgMfw7GodTPebgzxQ@mail.gmail.com>

Package: torbrowser-launcher
Version: 0.2.9-6
Severity: normal

Dear Maintainer,

I saw a few errors on the CLI while using torbrowser-launcher.

First is, it's not known in reportbug which version of torbrowser was
actually used. It was Torbrowser 8.0.2

I did see probably upstream errors which probably upstream has to solve -

Fontconfig warning:
"/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf",
line 85: unknown element "blank"

JavaScript error: resource://gre/modules/ExtensionContent.jsm, line
489: TypeError: Argument 1 of PrecompiledScript.executeInGlobal is not
an object.
JavaScript error: resource://gre/modules/ExtensionContent.jsm, line
489: TypeError: Argument 1 of PrecompiledScript.executeInGlobal is not
an object.
date time [notice] Catching signal TERM, exiting cleanly.
JavaScript error: resource://gre/modules/ExtensionPageChild.jsm, line
191: TypeError: this.contentWindow is null
JavaScript error: resource://gre/modules/ExtensionPageChild.jsm, line
191: TypeError: this.contentWindow is null
JavaScript error: chrome://torbutton/content/tor-circuit-display.js,
line 436: TypeError: myController is null

Would be nice if the above issues can be fixed.


-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (100,
'unstable-debug'), (100, 'experimental-debug'), (100, 'experimental'),
(100, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  gnupg             2.2.10-3
ii  libdbus-glib-1-2  0.110-3
ii  python            2.7.15-3
ii  python-gtk2       2.24.0-5.1+b1
ii  python-lzma       0.5.3-3.1
ii  python-parsley    1.2-1
ii  python-psutil     5.4.6-1+b1
ii  python-twisted    18.7.0-3
ii  python-txsocksx   1.15.0.2-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.4.8-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.13-8
pn  python-pygame  <none>

-- no debconf information


-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8


From intrigeri at debian.org  Fri Oct 12 08:53:07 2018
From: intrigeri at debian.org (intrigeri)
Date: Fri, 12 Oct 2018 09:53:07 +0200
Subject: [Pkg-privacy-maintainers] Bug#910827: Bug#910827: Doing update on
 torbrowser-launcher 0.2.9-6 resulted in not finding profile
In-Reply-To: <CADdDZR=bvbS0zdbg45obuJ-TXgwTqQrmv8x543aAj5TkUeW0JQ@mail.gmail.com>
References: <CADdDZR=bvbS0zdbg45obuJ-TXgwTqQrmv8x543aAj5TkUeW0JQ@mail.gmail.com>
 <CADdDZR=bvbS0zdbg45obuJ-TXgwTqQrmv8x543aAj5TkUeW0JQ@mail.gmail.com>
Message-ID: <85woqnzjmk.fsf@boum.org>

> I was using torbrowser-launcher and updated it to torbrowser 8.0.2 .
> When the torbrowser restarted it gave me a message stating it could
> not find my profile.

This is probably fixed by one of the commits in
https://github.com/micahflee/torbrowser-launcher/pull/360


From noreply at release.debian.org  Sat Oct 13 05:39:14 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Sat, 13 Oct 2018 04:39:14 +0000
Subject: [Pkg-privacy-maintainers] torbirdy 0.2.6-1 MIGRATED to testing
Message-ID: <E1gBBhq-0006rz-Ij@respighi.debian.org>

FYI: The status of the torbirdy source package
in Debian's testing distribution has changed.

  Previous version: 0.2.5-1
  Current version:  0.2.6-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From owner at bugs.debian.org  Mon Oct 15 11:06:03 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 15 Oct 2018 10:06:03 +0000
Subject: [Pkg-privacy-maintainers] Processed: tagging 910491
References: <1539597807-3260-bts-georg@riseup.net>
Message-ID: <handler.s.C.1539597810647.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tags 910491 + confirmed pending
Bug #910491 [mat2] mat2: Please package the Nautilus extension
Added tag(s) pending and confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
910491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910491
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From owner at bugs.debian.org  Mon Oct 15 12:18:08 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 15 Oct 2018 11:18:08 +0000
Subject: [Pkg-privacy-maintainers] Processed: tagging 910491
References: <1539602168-460-bts-georg@riseup.net>
Message-ID: <handler.s.C.15396021711900.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tags 910491 - pending
Bug #910491 [mat2] mat2: Please package the Nautilus extension
Removed tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
910491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910491
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From georg at riseup.net  Mon Oct 15 12:23:13 2018
From: georg at riseup.net (Georg Faerber)
Date: Mon, 15 Oct 2018 11:23:13 +0000
Subject: [Pkg-privacy-maintainers] Bug#910491: Bug#910491: mat2: Please
 package the Nautilus extension
In-Reply-To: <85ftxi6uja.fsf@boum.org>
References: <85ftxi6uja.fsf@boum.org> <85ftxi6uja.fsf@boum.org>
Message-ID: <20181015112313.GJ8706@debian>

Hi all,

Short update on this:

- python-nautilus 1.2.2-1 was uploaded to unstable some days ago.

- Therefore, in theory, we could now ship and install the Nautilus
  extension.

- I just tried to do so, however, it seems, that currently
  python-nautilus builds against python2.7 [1], while we need python3.

- I'll talk to the maintainers how to go forward.

Cheers,
Georg


[1] https://salsa.debian.org/gnome-team/nautilus-python/blob/debian/master/debian/rules#L7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181015/b1e555ce/attachment.sig>

From owner at bugs.debian.org  Mon Oct 15 14:24:05 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 15 Oct 2018 13:24:05 +0000
Subject: [Pkg-privacy-maintainers] Processed: nautilus-python: please build
 against python3
References: <20181015132048.GK8706@debian> <20181015132048.GK8706@debian>
Message-ID: <handler.s.B.153960965127121.transcript@bugs.debian.org>

Processing control commands:

> block 910491 with -1
Bug #910491 [mat2] mat2: Please package the Nautilus extension
910491 was blocked by: 907591
910491 was blocking: 910493
Added blocking bug(s) of 910491: 911082

-- 
910491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910491
911082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911082
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ftpmaster at ftp-master.debian.org  Tue Oct 16 19:02:33 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 16 Oct 2018 18:02:33 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 monkeysphere_0.42-1_amd64.changes
Message-ID: <E1gCTft-0005ld-OD@usper.debian.org>

monkeysphere_0.42-1_amd64.changes uploaded successfully to localhost
along with the files:
  monkeysphere_0.42-1.dsc
  monkeysphere_0.42.orig.tar.gz
  monkeysphere_0.42-1.debian.tar.xz
  monkeysphere_0.42-1_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Tue Oct 16 19:06:22 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 16 Oct 2018 18:06:22 +0000
Subject: [Pkg-privacy-maintainers] monkeysphere_0.42-1_amd64.changes
 ACCEPTED into unstable
Message-ID: <E1gCTja-0006YD-Hi@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Tue, 16 Oct 2018 12:32:30 -0400
Source: monkeysphere
Binary: monkeysphere agent-transfer
Architecture: source
Version: 0.42-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Daniel Kahn Gillmor <dkg at fifthhorseman.net>
Description:
 agent-transfer - copy a secret key from GnuPG's gpg-agent to OpenSSH's ssh-agent
 monkeysphere - leverage the OpenPGP web of trust for SSH and TLS authentication
Closes: 883015 899060 902318 902320 902367 908228 909700
Changes:
 monkeysphere (0.42-1) unstable; urgency=medium
 .
   * new upstream bugfix release.
 .
   [ Daniel Kahn Gillmor ]
   * make print_date_from_seconds_since_the_epoch deal better with bad input
 .
   [ Helmut Grohne ]
   * use generic compiler (closes: #883015)
 .
   [ Daniel Kahn Gillmor ]
   * clean up test suite failures when built against newer GnuPG
 .
   [ Clint Adams ]
   * Remove RSAAuthentication from test ssh config (Closes: #902318)
 .
   [ Antoine Beaupré ]
   * fix more gnupg2 colons changes (Closes: #902367)
   * yet more colon fixes that escaped previous inspections
   * write old-style PEM files to unbreak test suite (Closes: #909700)
 .
   [ Clint Adams ]
   * Remove deprecated option from test sshd config (Closes: #902320)
 .
   [ Sunil Mohan Adapa ]
   * tests: Ensure that stale sockets don't fail socat (Closes: #899060)
 .
   [ Daniel Kahn Gillmor ]
   * use --send-keys instead of --send (closes: #908228)
   * prepare new release
   * enable tests to operate on system installation
   * d/copyright: use https for Format:
   * use priority optional instead of extra
   * added autopkgtest
   * override package-contains-documentation-outside-usr-share-doc for
     transitions README.txt
   * install examples in monkeysphere package
   * d/watch: use https
   * packaging handled by pkg-privacy-team (updated uploaders)
Checksums-Sha1:
 03190e3a46d0f4305e0c70b8e29fdc7c55f12483 1879 monkeysphere_0.42-1.dsc
 546a30e9d003422ee296961417e10ebe9875d3cb 110415 monkeysphere_0.42.orig.tar.gz
 f320e4b5f9d0dece78ed5482ab8d27597bb20c34 6784 monkeysphere_0.42-1.debian.tar.xz
 35224fa0bdad8347c5233d325a7fe7fff541b685 12714 monkeysphere_0.42-1_amd64.buildinfo
Checksums-Sha256:
 d43f26ef40cbbc39b6ce64f113eea8d6e195c53d993d328da0af865172e0c9a3 1879 monkeysphere_0.42-1.dsc
 c1c956b1c86aaa44134fc1a9d75f5aef61266e3a9d8a6218b45d6c54bb7c58c1 110415 monkeysphere_0.42.orig.tar.gz
 dcc0abfeedca392aa32b65994a97f87e6c0d05b78acdca643fb416ea1d2e5446 6784 monkeysphere_0.42-1.debian.tar.xz
 469f78ede8160e3eb4a33d7113ec3b09d1aaedeabcdfd62ac7eadfd97b7d25a6 12714 monkeysphere_0.42-1_amd64.buildinfo
Files:
 6ac2d8ae0a47520504fa6c79b49b87bc 1879 net optional monkeysphere_0.42-1.dsc
 56b5f9f66481eec8716a1726366239b4 110415 net optional monkeysphere_0.42.orig.tar.gz
 02180d3667e081a2bbb71f96e00060b9 6784 net optional monkeysphere_0.42-1.debian.tar.xz
 6d315b1e8b6a8deeed38b57c6f5b6282 12714 net optional monkeysphere_0.42-1_amd64.buildinfo

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

iHUEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCW8YmMgAKCRBsHx7ezFD6
UxIeAP0SC+hD17dMdlVzB8wI8fyKEtbcZoheV034ES5HAwBc7wD8Dm0EreKCx7pG
WwC6BeaHKz7uUeOdIzHHed3k5eqUmQA=
=jgbh
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From dkg at fifthhorseman.net  Tue Oct 16 22:42:18 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Tue, 16 Oct 2018 17:42:18 -0400
Subject: [Pkg-privacy-maintainers] monkeysphere packaging
Message-ID: <87efcpd0w5.fsf@fifthhorseman.net>

hey folks--

today i did some upstream and debian packaging work on the monkeysphere
project.  It was already on salsa in the pkg-privacy-team repos
(https://salsa.debian.org/pkg-privacy-team/monkeysphere), and the
previous maintainer (jrollins, cc'ed here) suggested that he isn't up
for being the official maintainer any longer, so i moved the official
maintainer to pkg-privacy-team.

Anarcat (also cc'ed here) has also volunteered to be an uploader for
this package, so we have at least 3 people capable of handling it
(though i know we all welcome more help if anyone has the cycles).

This upload (0.42-1) closes a bunch of outstanding bugs in monkeysphere,
so hopefully it will get the package back into debian testing.

just wanted to give a heads-up.  If there are any objections, i'm fine
with removing monkeysphere from pkg-privacy-team maintainership, but i
figured since the repo was already set up i'd go ahead with it.

All the best,

        --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181016/0e6b8ca0/attachment.sig>

From u at 451f.org  Wed Oct 17 10:30:00 2018
From: u at 451f.org (u)
Date: Wed, 17 Oct 2018 09:30:00 +0000
Subject: [Pkg-privacy-maintainers] monkeysphere packaging
In-Reply-To: <87efcpd0w5.fsf@fifthhorseman.net>
References: <87efcpd0w5.fsf@fifthhorseman.net>
Message-ID: <e2e4c812-7ee4-7b9c-285b-3b6c415f977d@451f.org>

Hi Daniel,

Daniel Kahn Gillmor:

> just wanted to give a heads-up.  If there are any objections, i'm fine
> with removing monkeysphere from pkg-privacy-team maintainership, but i
> figured since the repo was already set up i'd go ahead with it.

Well done :)

Thank you,
Ulrike


From ulrike at debian.org  Wed Oct 17 10:42:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Wed, 17 Oct 2018 09:42:00 +0000
Subject: [Pkg-privacy-maintainers] Request to join the Privacy
 Maintainers group
In-Reply-To: <5bc67c2385baf_3a82ae22788472411302ef@godard.mail>
References: <5bc67c2385baf_3a82ae22788472411302ef@godard.mail>
Message-ID: <0fb0e9c3-5cac-a819-5e0e-fe32df02767f@debian.org>

Hi!

We have received a membership request from
> Vipul Kumar (https://salsa.debian.org/finn02-guest) requested Developer access to the Privacy Maintainers group.

Vipul, may you please elaborate why you want to join the Privacy
Maintainer group?

Note that forking repositories and asking for merge requests is all you
need to participate.

Please also note that we have a membership policy [1] and we will first
discuss your application before accepting it.

Cheers!
Ulrike

[1]
https://salsa.debian.org/pkg-privacy-team/team-processes/blob/master/pkg-privacy-process.mdwn


From u at 451f.org  Wed Oct 17 10:45:00 2018
From: u at 451f.org (u)
Date: Wed, 17 Oct 2018 09:45:00 +0000
Subject: [Pkg-privacy-maintainers] Request to join the Privacy
 Maintainers group
In-Reply-To: <0fb0e9c3-5cac-a819-5e0e-fe32df02767f@debian.org>
References: <5bc67c2385baf_3a82ae22788472411302ef@godard.mail>
 <0fb0e9c3-5cac-a819-5e0e-fe32df02767f@debian.org>
Message-ID: <6ae051ac-b6c4-bb1d-a081-58b47767eecd@451f.org>

Dear all,

I would suggest that we automatically reset the counter for the decision
making process to the day on which we receive an answer from Vipul.

Cheers!
u.


From georg at riseup.net  Wed Oct 17 13:08:05 2018
From: georg at riseup.net (Georg Faerber)
Date: Wed, 17 Oct 2018 12:08:05 +0000
Subject: [Pkg-privacy-maintainers] Request to join the Privacy
 Maintainers group
In-Reply-To: <6ae051ac-b6c4-bb1d-a081-58b47767eecd@451f.org>
References: <5bc67c2385baf_3a82ae22788472411302ef@godard.mail>
 <0fb0e9c3-5cac-a819-5e0e-fe32df02767f@debian.org>
 <6ae051ac-b6c4-bb1d-a081-58b47767eecd@451f.org>
Message-ID: <20181017120805.GU4144@debian>

Hi,

On 18-10-17 09:45:00, u wrote:
> I would suggest that we automatically reset the counter for the
> decision making process to the day on which we receive an answer from
> Vipul.

Agreed.

Cheers,
Georg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/571b8a37/attachment.sig>

From georg at riseup.net  Wed Oct 17 13:16:08 2018
From: georg at riseup.net (Georg Faerber)
Date: Wed, 17 Oct 2018 12:16:08 +0000
Subject: [Pkg-privacy-maintainers] ITP: intel-me-cleaner -- under the
 umbrella of this team?
In-Reply-To: <20181009132506.GC2137@debian>
References: <20181009132506.GC2137@debian>
Message-ID: <20181017121608.GV4144@debian>

Hi all again,

Thanks to all of you for your answers, and sorry that my initial mail
was quite vague and without any details.

Regarding the pros and cons and just to make sure: All in all, does this
come down to "yes, we do welcome this package under our team umbrella"?
That's at least my (biased?) conclusion after reading.. ;)

Thanks & cheers,
Georg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/4aedcfca/attachment.sig>

From u at 451f.org  Wed Oct 17 14:14:00 2018
From: u at 451f.org (u)
Date: Wed, 17 Oct 2018 13:14:00 +0000
Subject: [Pkg-privacy-maintainers] ITP: intel-me-cleaner -- under the
 umbrella of this team?
In-Reply-To: <20181017121608.GV4144@debian>
References: <20181009132506.GC2137@debian> <20181017121608.GV4144@debian>
Message-ID: <7748996a-ddb5-4265-3c01-7871bc40f66e@451f.org>

Hi Georg,

Georg Faerber:
> Hi all again,
> 
> Thanks to all of you for your answers, and sorry that my initial mail
> was quite vague and without any details.
> 
> Regarding the pros and cons and just to make sure: All in all, does this
> come down to "yes, we do welcome this package under our team umbrella"?
> That's at least my (biased?) conclusion after reading.. ;)

That's what I understood as well.

Cheers!
u.


From georg at riseup.net  Wed Oct 17 14:24:47 2018
From: georg at riseup.net (Georg Faerber)
Date: Wed, 17 Oct 2018 13:24:47 +0000
Subject: [Pkg-privacy-maintainers] ITP: intel-me-cleaner -- under the
 umbrella of this team?
In-Reply-To: <7748996a-ddb5-4265-3c01-7871bc40f66e@451f.org>
References: <20181009132506.GC2137@debian> <20181017121608.GV4144@debian>
 <7748996a-ddb5-4265-3c01-7871bc40f66e@451f.org>
Message-ID: <20181017132447.GB4144@debian>

Hi Ulrike, all,

On 18-10-17 13:14:00, u wrote:
> Georg Faerber:
> > Thanks to all of you for your answers, and sorry that my initial
> > mail was quite vague and without any details.
> > 
> > Regarding the pros and cons and just to make sure: All in all, does
> > this come down to "yes, we do welcome this package under our team
> > umbrella"?  That's at least my (biased?) conclusion after reading..
> > ;)
> 
> That's what I understood as well.

Alright -- could someone then create a repository 'intel-me-cleaner', I
lack the rights to do so.

Cheers,
Georg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/626dea72/attachment.sig>

From jonas at freesources.org  Wed Oct 17 14:16:47 2018
From: jonas at freesources.org (Jonas Meurer)
Date: Wed, 17 Oct 2018 15:16:47 +0200
Subject: [Pkg-privacy-maintainers] ITP: intel-me-cleaner -- under the
 umbrella of this team?
In-Reply-To: <20181017121608.GV4144@debian>
References: <20181009132506.GC2137@debian> <20181017121608.GV4144@debian>
Message-ID: <71eea9d6-81cd-44c3-f8e0-1471f3a0e158@freesources.org>

Am 17.10.18 um 14:16 schrieb Georg Faerber:
> Hi all again,
> 
> Thanks to all of you for your answers, and sorry that my initial mail
> was quite vague and without any details.
> 
> Regarding the pros and cons and just to make sure: All in all, does this
> come down to "yes, we do welcome this package under our team umbrella"?
> That's at least my (biased?) conclusion after reading.. ;)

Yep, I read it that way as well. And I agree with intri and dkg that
there's good reasons for the package to live be under the teams umbrella
even though strictly speaking it might fit better in other teams.

Cheers
 jonas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/a40f66e8/attachment.sig>

From dkg at fifthhorseman.net  Wed Oct 17 15:26:38 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Wed, 17 Oct 2018 10:26:38 -0400
Subject: [Pkg-privacy-maintainers] ITP: intel-me-cleaner -- under the
 umbrella of this team?
In-Reply-To: <20181017132447.GB4144@debian>
References: <20181009132506.GC2137@debian> <20181017121608.GV4144@debian>
 <7748996a-ddb5-4265-3c01-7871bc40f66e@451f.org>
 <20181017132447.GB4144@debian>
Message-ID: <8736t4d4yp.fsf@fifthhorseman.net>

On Wed 2018-10-17 13:24:47 +0000, Georg Faerber wrote:
> Alright -- could someone then create a repository 'intel-me-cleaner', I
> lack the rights to do so.

I've done this at:

   https://salsa.debian.org/pkg-privacy-team/intel-me-cleaner/

and i've granted @georg-guest Maintainer privileges so hopefully you can
do what you need to with it.

Please let me know if you're missing some necessary permission.

thanks for working on this!

       --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/8a0277bf/attachment.sig>

From dkg at fifthhorseman.net  Wed Oct 17 17:57:14 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Wed, 17 Oct 2018 12:57:14 -0400
Subject: [Pkg-privacy-maintainers] Request to join the Privacy
 Maintainers group
In-Reply-To: <20181017120805.GU4144@debian>
References: <5bc67c2385baf_3a82ae22788472411302ef@godard.mail>
 <0fb0e9c3-5cac-a819-5e0e-fe32df02767f@debian.org>
 <6ae051ac-b6c4-bb1d-a081-58b47767eecd@451f.org>
 <20181017120805.GU4144@debian>
Message-ID: <87murcbjf9.fsf@fifthhorseman.net>

On Wed 2018-10-17 12:08:05 +0000, Georg Faerber wrote:
> On 18-10-17 09:45:00, u wrote:
>> I would suggest that we automatically reset the counter for the
>> decision making process to the day on which we receive an answer from
>> Vipul.
>
> Agreed.

Also agreed.

I've sent a patch to our team process list to try to clarify that we
want an explicit explanation for future membership requests, since
gitlab membership requests don't support such a feature. (see
id:87o9bsbjhx.fsf at fifthhorseman.net)

        --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/395c1fbc/attachment-0001.sig>

From dkg at fifthhorseman.net  Wed Oct 17 17:55:38 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Wed, 17 Oct 2018 12:55:38 -0400
Subject: [Pkg-privacy-maintainers] process update proposal: new membership
 process clarification
Message-ID: <87o9bsbjhx.fsf@fifthhorseman.net>

the branch new-member-timeline on
https://salsa.debian.org/pkg-privacy-team/team-processes contains the
following patch, which hopefully will clarify the situation that Vipul
finds themself in today:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-clarify-request-to-join-process.patch
Type: text/x-diff
Size: 1146 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/da07162c/attachment.patch>
-------------- next part --------------

I'm making this proposal explicitly via our decision-making process.
The deadline for this proposal is two weeks from now:

   Wed Oct 31 17:00 UTC 2018

Please let the list know if you have any opinion about it :)

I support this proposal.

  --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/da07162c/attachment.sig>

From georg at riseup.net  Wed Oct 17 19:44:23 2018
From: georg at riseup.net (Georg Faerber)
Date: Wed, 17 Oct 2018 18:44:23 +0000
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification
In-Reply-To: <87o9bsbjhx.fsf@fifthhorseman.net>
References: <87o9bsbjhx.fsf@fifthhorseman.net>
Message-ID: <20181017184423.GG19229@debian>

Hi dkg, all,

Thanks for the continued efforts:

On 18-10-17 12:55:38, Daniel Kahn Gillmor wrote:
>    Anyone who is not a team member may request to become one either via
>    means specific to the infrastructure currently used by the team
> -  (e.g. membership request on GitLab) or by writing to the team
> -  mailing list. A request is then handled using the normal
> -  decision-making process (defined below).
> +  (e.g. membership request on GitLab) and by writing to the team
> +  mailing list with an explanation of how they intend to contribute to
> +  the team.
> +
> +  Once the explanation has been sent to the team mailing list, a
> +  request to join is then handled using the normal decision-making
> +  process (defined below).
>  
>  1.2 Proposal to expel:

All in all this sounds good to me; minor nitpick: Before, this was an
"either ... or ...", now it's an "either ... and ...".

> I support this proposal.

Me too.

Cheers,
Georg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/24a877b3/attachment.sig>

From dkg at fifthhorseman.net  Wed Oct 17 20:16:21 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Wed, 17 Oct 2018 15:16:21 -0400
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v2)
In-Reply-To: <20181017184423.GG19229@debian>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
Message-ID: <87k1mgbcze.fsf@fifthhorseman.net>

On Wed 2018-10-17 18:44:23 +0000, Georg Faerber wrote:
> All in all this sounds good to me; minor nitpick: Before, this was an
> "either ... or ...", now it's an "either ... and ...".

You're absolutely right, this is why we have a review process!  Thanks
for catching this.

I'm modifying the proposal to avoid this infelicity, so the earlier
proposal is withdrawn.  I've revised the patch so that it now highlights
the explanatory message to the mailing list as the required step.
Version 2 of the proposal is now:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-clarify-request-to-join-process.patch
Type: text/x-diff
Size: 1416 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/f5516c39/attachment.patch>
-------------- next part --------------

This change resets the clock so that the deadline is now:

   Wed Oct 31 20:00 UTC 2018

And it clears the outstanding proposals (sigh, sorry this is a bit
cumbersome).

I support version 2 of this proposal.

  --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/f5516c39/attachment.sig>

From georg at riseup.net  Wed Oct 17 20:26:44 2018
From: georg at riseup.net (Georg Faerber)
Date: Wed, 17 Oct 2018 19:26:44 +0000
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v2)
In-Reply-To: <87k1mgbcze.fsf@fifthhorseman.net>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net>
Message-ID: <20181017192644.GH19229@debian>

On 18-10-17 15:16:21, Daniel Kahn Gillmor wrote:
> On Wed 2018-10-17 18:44:23 +0000, Georg Faerber wrote:
> > All in all this sounds good to me; minor nitpick: Before, this was an
> > "either ... or ...", now it's an "either ... and ...".
> 
> You're absolutely right, this is why we have a review process!  Thanks
> for catching this.

Sure!

> I'm modifying the proposal to avoid this infelicity, so the earlier
> proposal is withdrawn.  I've revised the patch so that it now
> highlights the explanatory message to the mailing list as the required
> step.  Version 2 of the proposal is now:

Sounds good, just one last minor nitpick from my side:

>  1.1. Request to join:
>  
> -  Anyone who is not a team member may request to become one either via
> -  means specific to the infrastructure currently used by the team
> -  (e.g. membership request on GitLab) or by writing to the team
> -  mailing list. A request is then handled using the normal
> -  decision-making process (defined below).
> +  Anyone who is not a team member may request to become one by by

                                                               ^^^^^

> +  writing to the team mailing list with a short explanation of how
> +  they intend to contribute to the team.  They may also use means
> +  specific to the infrastructure currently used by the team
> +  (e.g. membership request on GitLab), but an explanatory introduction
> +  e-mail still needs to go to the team mailing list.
> +
> +  Once the explanation has been sent to the team mailing list, a
> +  request to join is then handled using the normal decision-making
> +  process (defined below).
>  
>  1.2 Proposal to expel:

Cheers,
Georg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/ce2374f2/attachment.sig>

From dkg at fifthhorseman.net  Wed Oct 17 22:48:02 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Wed, 17 Oct 2018 17:48:02 -0400
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v2)
In-Reply-To: <20181017192644.GH19229@debian>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
Message-ID: <87h8hkb5yl.fsf@fifthhorseman.net>

On Wed 2018-10-17 19:26:44 +0000, Georg Faerber wrote:
>> +  Anyone who is not a team member may request to become one by by
>
>                                                                ^^^^^

sigh, thanks.  fixed now, in version 3.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-clarify-request-to-join-process.patch
Type: text/x-diff
Size: 1416 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/9cad1a19/attachment.patch>
-------------- next part --------------

I endorse version 3 of this proposal.

the cutoff is now:

  Wed Oct 31 22:00:00 UTC 2018

  --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/9cad1a19/attachment.sig>

From sebastian at breakpoint.cc  Wed Oct 17 23:16:15 2018
From: sebastian at breakpoint.cc (Sebastian Andrzej Siewior)
Date: Thu, 18 Oct 2018 00:16:15 +0200
Subject: [Pkg-privacy-maintainers] Bug#911271: foolscap: (Build) Depends on
 non existing python-txtorcon
Message-ID: <20181017221614.lmul5she3zbewuqo@breakpoint.cc>

Package: foolscap
Version: 0.13.1-1
Severity: serious

txtorcon does not build the Python2 variant (python-txtorcon) since its
last upload, only the python3 one (python3-txtorcon) remains.

As of now the package can't be built due to missing packages.

Sebastian


From sebastian at breakpoint.cc  Wed Oct 17 23:36:53 2018
From: sebastian at breakpoint.cc (Sebastian Andrzej Siewior)
Date: Thu, 18 Oct 2018 00:36:53 +0200
Subject: [Pkg-privacy-maintainers] Bug#911272: RM: python-txtorcon -- NBS;
 decruft
Message-ID: <20181017223653.d4bg7olbaiipj36q@breakpoint.cc>

Package: ftp.debian.org
Severity: normal

Hi,

The source package txtorcon no longer builds the binary package
python-txtorcon. The binary package is still in archive and was not
auto-decrufted. Removing the package breakds two other packages:

|bigeasy at coccia:~$ dak rm -Rnb python-txtorcon
|Will remove the following packages from unstable:
|
|python-txtorcon |   18.0.2-1 | all
|
|Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
|
|------------------- Reason -------------------
|
|----------------------------------------------
|
|Checking reverse dependencies...
|# Broken Depends:
|ooniprobe/contrib: ooniprobe
|
|# Broken Build-Depends:
|foolscap: python-txtorcon
|ooniprobe/contrib: python-txtorcon (>= 0.14.2)
|
|Dependency problem found.

Both packages have a RC bug open:
- #909866 ooniprobe: (Build-) Depends on vanished package python-txtorcon
- #911271 foolscap: (Build) Depends on non existing python-txtorcon

python-txtorcon itself can't be installed in unstable anymore (#905253)
so I doubt it makes sense to wait until the two packages get fixed.
It seems that BTS things that #905253 is still open because the package
is in archive and piuparts tests with the old binary and fails. I think
this is the reason why the package can't migrate to testing. I don't
understand however why the package does not pop up in the cruft report.

Sebastian


From anarcat at debian.org  Thu Oct 18 00:02:51 2018
From: anarcat at debian.org (=?utf-8?Q?Antoine_Beaupr=C3=A9?=)
Date: Wed, 17 Oct 2018 19:02:51 -0400
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v2)
In-Reply-To: <87h8hkb5yl.fsf@fifthhorseman.net>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
 <87h8hkb5yl.fsf@fifthhorseman.net>
Message-ID: <875zy0jhwk.fsf@curie.anarc.at>

On 2018-10-17 17:48:02, Daniel Kahn Gillmor wrote:
> On Wed 2018-10-17 19:26:44 +0000, Georg Faerber wrote:
>>> +  Anyone who is not a team member may request to become one by by
>>
>>                                                                ^^^^^
>
> sigh, thanks.  fixed now, in version 3.

[...]

not in this diff anyways... :/
  
> +  Anyone who is not a team member may request to become one by by

But for what it's worth, I approve the change as well. I always find it
weird to receive join requests without explanations and usually ignore
them.

A.
-- 
Si Dieu existe, j'espère qu'Il a une excuse valable
                        - Daniel Pennac


From dkg at fifthhorseman.net  Thu Oct 18 04:49:31 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Wed, 17 Oct 2018 23:49:31 -0400
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v4)
In-Reply-To: <875zy0jhwk.fsf@curie.anarc.at>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
 <87h8hkb5yl.fsf@fifthhorseman.net> <875zy0jhwk.fsf@curie.anarc.at>
Message-ID: <87bm7rc3sk.fsf@fifthhorseman.net>

On Wed 2018-10-17 19:02:51 -0400, Antoine Beaupré wrote:
> not in this diff anyways... :/

One last try from me, if i screw this up i hope someone else will take
over the revision process :P

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-clarify-request-to-join-process.patch
Type: text/x-diff
Size: 1413 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/e1e76e6b/attachment.patch>
-------------- next part --------------

(i've rebased it on top of georg's earlier typo fix)

I support version 4 of this proposal.

The deadline is now:

    2018-11-01T03:00

  --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181017/e1e76e6b/attachment.sig>

From u at 451f.org  Thu Oct 18 14:51:00 2018
From: u at 451f.org (u)
Date: Thu, 18 Oct 2018 13:51:00 +0000
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v4)
In-Reply-To: <87bm7rc3sk.fsf@fifthhorseman.net>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
 <87h8hkb5yl.fsf@fifthhorseman.net> <875zy0jhwk.fsf@curie.anarc.at>
 <87bm7rc3sk.fsf@fifthhorseman.net>
Message-ID: <06ea4049-9dcc-33da-bce1-b0770140c8f9@451f.org>

Hi!

Daniel Kahn Gillmor:
> On Wed 2018-10-17 19:02:51 -0400, Antoine Beaupré wrote:

> One last try from me, if i screw this up i hope someone else will take
> over the revision process :P

> I support version 4 of this proposal.
> 
> The deadline is now:
> 
>     2018-11-01T03:00

Thanks for working on this. I support this proposal!

Cheers!
u.


From georg at riseup.net  Thu Oct 18 14:52:27 2018
From: georg at riseup.net (Georg Faerber)
Date: Thu, 18 Oct 2018 13:52:27 +0000
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v4)
In-Reply-To: <87bm7rc3sk.fsf@fifthhorseman.net>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
 <87h8hkb5yl.fsf@fifthhorseman.net> <875zy0jhwk.fsf@curie.anarc.at>
 <87bm7rc3sk.fsf@fifthhorseman.net>
Message-ID: <20181018135227.GI19229@debian>

On 18-10-17 23:49:31, Daniel Kahn Gillmor wrote:
> I support version 4 of this proposal.

Me too.

Cheers,
Georg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181018/04c1460a/attachment.sig>

From ftpmaster at ftp-master.debian.org  Thu Oct 18 15:22:46 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 18 Oct 2018 14:22:46 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 monkeysphere_0.42-2_amd64.changes
Message-ID: <E1gD9CI-0006Is-Cz@usper.debian.org>

monkeysphere_0.42-2_amd64.changes uploaded successfully to localhost
along with the files:
  monkeysphere_0.42-2.dsc
  monkeysphere_0.42-2.debian.tar.xz
  monkeysphere_0.42-2_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Thu Oct 18 15:54:33 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 18 Oct 2018 14:54:33 +0000
Subject: [Pkg-privacy-maintainers] monkeysphere_0.42-2_amd64.changes
 ACCEPTED into unstable
Message-ID: <E1gD9h3-0008IT-IY@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Thu, 18 Oct 2018 10:17:55 -0400
Source: monkeysphere
Binary: monkeysphere agent-transfer
Architecture: source
Version: 0.42-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Daniel Kahn Gillmor <dkg at fifthhorseman.net>
Description:
 agent-transfer - copy a secret key from GnuPG's gpg-agent to OpenSSH's ssh-agent
 monkeysphere - leverage the OpenPGP web of trust for SSH and TLS authentication
Changes:
 monkeysphere (0.42-2) unstable; urgency=medium
 .
   * added cpio as a requirement for the basic autopkgtest
   * gpg is super noisy to stderr -- ignore that noise during
     autopkgtest
Checksums-Sha1:
 8272eb61ed4c8311618f706944e17c138b733751 1885 monkeysphere_0.42-2.dsc
 d8b55eaaad34bf703967bfc51cf6b0e020202a59 6864 monkeysphere_0.42-2.debian.tar.xz
 17cac144deb3d83d862e94bc6c2618912288fe30 12714 monkeysphere_0.42-2_amd64.buildinfo
Checksums-Sha256:
 cf70a058329e75f9c015a223076396aade954570e9399762e40fd39fda8b2cd8 1885 monkeysphere_0.42-2.dsc
 99683bbe9ea9df840c449cf3b72027e4474e7d9b6711409e0b397a40259b5bea 6864 monkeysphere_0.42-2.debian.tar.xz
 da895b552c48698af26f9d14d51deb6b8c7687687b37e139963ab1e9fe7dbb90 12714 monkeysphere_0.42-2_amd64.buildinfo
Files:
 ea911ca5f79a1a4ca10eb06734b50a77 1885 net optional monkeysphere_0.42-2.dsc
 3f5746853c42c20d3299c50b37951f2d 6864 net optional monkeysphere_0.42-2.debian.tar.xz
 7bc794fb84fd8019b570c550d80ad68d 12714 net optional monkeysphere_0.42-2_amd64.buildinfo

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

iHUEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCW8iWiwAKCRBsHx7ezFD6
UzhlAQC5XM8sAzPhF+f+ZipkP9EXqz8k4aL5Nlhu7v/0NQlkeQEA3cnsFw3YNS3Q
D1JLKd8bVwquiP7NERm6XU8Sk7O5MQw=
=K2mB
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Sat Oct 20 16:22:48 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 20 Oct 2018 15:22:48 +0000
Subject: [Pkg-privacy-maintainers] Processed: notfound 811308 in 8:6.8.9.9-7,
 found 811308 in 8:6.8.9.9-7, tagging 842316 ..., fixed 849748 in 234
References: <1540048653-424-bts-anbe@debian.org>
Message-ID: <handler.s.C.15400486587477.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> # fixup bug metadata to allow bug archival
> notfound 811308 8:6.8.9.9-7
Bug #811308 {Done: Brian May <bam at debian.org>} [imagemagick] Multiple minor security issues
No longer marked as found in versions imagemagick/8:6.8.9.9-7.
> found 811308 8:6.8.9.9-7
Bug #811308 {Done: Brian May <bam at debian.org>} [imagemagick] Multiple minor security issues
Marked as found in versions imagemagick/8:6.8.9.9-7 and reopened.
> tags 842316 + stretch
Bug #842316 {Done: Rene Engelhard <rene at debian.org>} [libreoffice-base-drivers] Please consider demoting libreoffice-sdbc-firebird to suggests
Added tag(s) stretch.
> fixed 690197 3.17.90-1
Bug #690197 {Done: Laurent Bigonville <bigon at debian.org>} [gdm3] gdm3: fails to correctly add XDMCP user's session to utmp
Marked as fixed in versions gdm3/3.17.90-1.
> notfixed 690197 3.22.3-3
Bug #690197 {Done: Laurent Bigonville <bigon at debian.org>} [gdm3] gdm3: fails to correctly add XDMCP user's session to utmp
No longer marked as fixed in versions gdm3/3.22.3-3.
> reassign 849748 systemd
Bug #849748 {Done: Simon McVittie <smcv at debian.org>} [dbus] dbus is translating SE Linux contexts when it's not appropriate
Bug reassigned from package 'dbus' to 'systemd'.
No longer marked as found in versions dbus/1.10.14-1.
No longer marked as fixed in versions systemd/234.
> fixed 849748 234
Bug #849748 {Done: Simon McVittie <smcv at debian.org>} [systemd] dbus is translating SE Linux contexts when it's not appropriate
There is no source info for the package 'systemd' at version '234' with architecture ''
Unable to make a source version for version '234'
Marked as fixed in versions 234.
> affects 849748 + dbus
Bug #849748 {Done: Simon McVittie <smcv at debian.org>} [systemd] dbus is translating SE Linux contexts when it's not appropriate
Added indication that 849748 affects dbus
> fixed 865493 128
Bug #865493 {Done: Wookey <wookey at debian.org>} [cross-gcc-dev] cross-gcc-dev in stable does not apply to gcc-6 in stable
There is no source info for the package 'cross-gcc-dev' at version '128' with architecture ''
Unable to make a source version for version '128'
Marked as fixed in versions 128.
> notfixed 789594 3.14.10-2
Bug #789594 {Done: Thorsten Alteholz <debian at alteholz.de>} [apcupsd] apcupsd: apcaccess gives cryptic failure message
No longer marked as fixed in versions 3.14.10-2.
> notfound 866500 0.16.3+dfsg-2
Bug #866500 {Done: أحمد المحمودي <aelmahmoudy at users.sourceforge.net>} [src:xpra] xpra: depends on obsolete python-imaging (replace with python3-pil or python-pil)
No longer marked as found in versions xpra/0.16.3+dfsg-2.
> fixed 879476 2.0.2+0.5.7-3
Bug #879476 {Done: Mathieu Parent <sathieu at debian.org>} [php-msgpack] php-msgpack: Please recompile to support php7.1
There is no source info for the package 'php-msgpack' at version '2.0.2+0.5.7-3' with architecture ''
Unable to make a source version for version '2.0.2+0.5.7-3'
Marked as fixed in versions 2.0.2+0.5.7-3.
> tags 871771 + stretch
Bug #871771 {Done: Apollon Oikonomopoulos <apoikos at debian.org>} [ganeti] ganeti: socat support broken in Stretch
Added tag(s) stretch.
> fixed 787498 3.0~20140825-8
Bug #787498 {Done: Marc Dequènes (duck) <duck at duckcorp.org>} [redmine] redmine: Cant change project ID of an earlier created issue
Marked as fixed in versions redmine/3.0~20140825-8.
> tags 846923 + experimental
Bug #846923 {Done: Thorsten Alteholz <debian at alteholz.de>} [src:mpb] mpb: FTBFS on mipsel - hanging on autconf test for BLAS zdotc
Added tag(s) experimental.
> tags 812429 + experimental
Bug #812429 {Done: Salvatore Bonaccorso <carnil at debian.org>} [samba] samba: Share of / no longer works
Bug #814287 {Done: Salvatore Bonaccorso <carnil at debian.org>} [samba] Recent security fix for symlinks renders root filesystem exports unusable
Added tag(s) experimental.
Added tag(s) experimental.
> reassign 878112 src:haskell-cabal-helper
Bug #878112 {Done: Clint Adams <clint at debian.org>} [ghc-mod] ghc-mod: Could not find $libexecdir/cabal-helper-wrapper
Bug reassigned from package 'ghc-mod' to 'src:haskell-cabal-helper'.
No longer marked as found in versions ghc-mod/5.7.0.0-1.
No longer marked as fixed in versions haskell-cabal-helper/0.7.3.0-3.
> fixed 878112 0.7.3.0-3
Bug #878112 {Done: Clint Adams <clint at debian.org>} [src:haskell-cabal-helper] ghc-mod: Could not find $libexecdir/cabal-helper-wrapper
Marked as fixed in versions haskell-cabal-helper/0.7.3.0-3.
> affects 878112 + ghc-mod
Bug #878112 {Done: Clint Adams <clint at debian.org>} [src:haskell-cabal-helper] ghc-mod: Could not find $libexecdir/cabal-helper-wrapper
Added indication that 878112 affects ghc-mod
> notfixed 510877 pillow/5.0.0-1
Bug #510877 {Done: Matthias Klose <doko at debian.org>} [python-imaging] python-imaging: Outline font rendering fails on amd64
No longer marked as fixed in versions pillow/5.0.0-1.
> notfixed 513536 pillow/5.0.0-1
Bug #513536 {Done: Matthias Klose <doko at debian.org>} [python-imaging] python-imaging: scripts with .py extension installed into /usr/bin
No longer marked as fixed in versions pillow/5.0.0-1.
> notfixed 554906 pillow/5.0.0-1
Bug #554906 {Done: Matthias Klose <doko at debian.org>} [python-imaging] python-imaging: install scripts with .py exension into /usr/bin
No longer marked as fixed in versions pillow/5.0.0-1.
> fixed 867429 0.2.1-1
Bug #867429 {Done: Adrian Bunk <bunk at debian.org>} [python3-flask-rdf] python3-flask-rdf: missing dependencies
Marked as fixed in versions python-flask-rdf/0.2.1-1.
> reassign 878606 src:kcron 4:4.14.2-1
Bug #878606 {Done: Pino Toscano <pino at debian.org>} [kcron] please drop transitional package kcron
Bug reassigned from package 'kcron' to 'src:kcron'.
No longer marked as found in versions kcron/4:4.14.2-1.
No longer marked as fixed in versions kcron/4:17.08.3-2.
Bug #878606 {Done: Pino Toscano <pino at debian.org>} [src:kcron] please drop transitional package kcron
Marked as found in versions kcron/4:4.14.2-1.
> fixed 878606 4:17.08.3-2
Bug #878606 {Done: Pino Toscano <pino at debian.org>} [src:kcron] please drop transitional package kcron
Marked as fixed in versions kcron/4:17.08.3-2.
> notfixed 888248 3.26.0-3+b1
Bug #888248 {Done: Jeremy Bicha <jbicha at debian.org>} [gnome-calculator] gnome-calculator: Gnome-calculator abort at startup
Bug #888249 {Done: Jeremy Bicha <jbicha at debian.org>} [gnome-calculator] gnome-calculator: die on startup with "MPFR assertion failed"
No longer marked as fixed in versions 3.26.0-3+b1.
No longer marked as fixed in versions 3.26.0-3+b1.
> tags 889609 + buster experimental
Bug #889609 {Done: Adrian Bunk <bunk at debian.org>} [moonshot-gss-eap] moonshot-gss-eap: uninstallable in sid: libgssapi-krb5-2 : Breaks: moonshot-gss-eap (<= 1.0) but 0.9.5-3+b1 is to be installed
Added tag(s) buster and experimental.
> reassign 877704 src:android-sdk-meta
Bug #877704 {Done: Hans-Christoph Steiner <hans at eds.org>} [android-tools-adb] android-tools-adb: Add 1949:0022 (Amazon Fire TV Stick)
Bug reassigned from package 'android-tools-adb' to 'src:android-sdk-meta'.
No longer marked as found in versions android-platform-system-core/1:7.0.0+r33-2.
No longer marked as fixed in versions android-sdk-meta/25.0.0+6.
> fixed 877704 25.0.0+6
Bug #877704 {Done: Hans-Christoph Steiner <hans at eds.org>} [src:android-sdk-meta] android-tools-adb: Add 1949:0022 (Amazon Fire TV Stick)
Marked as fixed in versions android-sdk-meta/25.0.0+6.
> affects 877704 + android-tools-adb
Bug #877704 {Done: Hans-Christoph Steiner <hans at eds.org>} [src:android-sdk-meta] android-tools-adb: Add 1949:0022 (Amazon Fire TV Stick)
Added indication that 877704 affects android-tools-adb
> reassign 883074 src:android-platform-tools-base
Bug #883074 {Done: Hans-Christoph Steiner <hans at eds.org>} [android-sdk] [android-sdk] Unable to figure out a way to accept licenses
Bug reassigned from package 'android-sdk' to 'src:android-platform-tools-base'.
No longer marked as found in versions android-sdk-meta/25.0.0+5.
No longer marked as fixed in versions android-platform-tools-base/2.2.2-3.
> fixed 883074 2.2.2-3
Bug #883074 {Done: Hans-Christoph Steiner <hans at eds.org>} [src:android-platform-tools-base] [android-sdk] Unable to figure out a way to accept licenses
Marked as fixed in versions android-platform-tools-base/2.2.2-3.
> affects 883074 + android-sdk
Bug #883074 {Done: Hans-Christoph Steiner <hans at eds.org>} [src:android-platform-tools-base] [android-sdk] Unable to figure out a way to accept licenses
Added indication that 883074 affects android-sdk
> reassign 885553 src:python3-stdlib-extensions
Bug #885553 {Done: Matthias Klose <doko at debian.org>} [src:python3.6] /usr/lib/python3.6/lib2to3 not removed during update to 3.6.4-2
Bug reassigned from package 'src:python3.6' to 'src:python3-stdlib-extensions'.
No longer marked as found in versions python3.6/3.6.4-2.
No longer marked as fixed in versions python3-stdlib-extensions/3.6.5~rc1-1.
> fixed 885553 3.6.5~rc1-1
Bug #885553 {Done: Matthias Klose <doko at debian.org>} [src:python3-stdlib-extensions] /usr/lib/python3.6/lib2to3 not removed during update to 3.6.4-2
Marked as fixed in versions python3-stdlib-extensions/3.6.5~rc1-1.
> fixed 881361 2.19.5-1
Bug #881361 {Done: Alberto Garcia <berto at igalia.com>} [src:webkit2gtk] webkit2gtk FTCBFS: uses the build architecture pkg-config for finding the host architecture geoclue-2.0.pc
Marked as fixed in versions webkit2gtk/2.19.5-1.
> tags 893920 + experimental
Bug #893920 {Done: Vincent Legout <vlegout at debian.org>} [qalc] qalc: Don't recommend libgnomevfs2-common
Added tag(s) experimental.
> tags 894923 + experimental
Bug #894923 {Done: Bas Couwenberg <sebastic at debian.org>} [src:mapnik-reference] Quoting fixed in autopkgtest 5.2
Added tag(s) experimental.
> tags 880593 + experimental
Bug #880593 {Done: James McCoy <jamessan at debian.org>} [subversion] subversion: spurious error E160016 when operative and peg revisions differ with fsfs
Added tag(s) experimental.
> reassign 896514 src:libfm-qt
Bug #896514 {Done: Alf Gaida <agaida at siduction.org>} [libfm-qt3] Fix symbols for riscv64 and symbol cleanup
Bug reassigned from package 'libfm-qt3' to 'src:libfm-qt'.
Ignoring request to alter found versions of bug #896514 to the same values previously set
No longer marked as fixed in versions libfm-qt/0.12.0-15.
> fixed 896514 0.12.0-15
Bug #896514 {Done: Alf Gaida <agaida at siduction.org>} [src:libfm-qt] Fix symbols for riscv64 and symbol cleanup
Marked as fixed in versions libfm-qt/0.12.0-15.
> tags 899077 + buster experimental
Bug #899077 {Done: Alastair McKinstry <mckinstry at debian.org>} [src:openmpi] openmpi: libmca_common_monitoring.so* does not get installed
Added tag(s) buster and experimental.
> reassign 898890 src:golang-gopkg-libgit2-git2go.v27
Bug #898890 {Done: Pirate Praveen <praveen at debian.org>} [golang-gopkg-libgit2-git2go.v26] libgit2 0.27 transition
Bug reassigned from package 'golang-gopkg-libgit2-git2go.v26' to 'src:golang-gopkg-libgit2-git2go.v27'.
Warning: Unknown package 'src:golang-gopkg-libgit2-git2go.v27'
Warning: Unknown package 'src:golang-gopkg-libgit2-git2go.v27'
No longer marked as found in versions 0.26+git20170903.0.eb0bf21-1.
Warning: Unknown package 'src:golang-gopkg-libgit2-git2go.v27'
Warning: Unknown package 'src:golang-gopkg-libgit2-git2go.v27'
No longer marked as fixed in versions golang-gopkg-libgit2-git2go.v27/0.27+git20180529.9abc050-1.
Warning: Unknown package 'src:golang-gopkg-libgit2-git2go.v27'
> fixed 898890 0.27+git20180529.9abc050-1
Bug #898890 {Done: Pirate Praveen <praveen at debian.org>} [src:golang-gopkg-libgit2-git2go.v27] libgit2 0.27 transition
Warning: Unknown package 'src:golang-gopkg-libgit2-git2go.v27'
Marked as fixed in versions golang-gopkg-libgit2-git2go.v27/0.27+git20180529.9abc050-1.
Warning: Unknown package 'src:golang-gopkg-libgit2-git2go.v27'
> reassign 901159 src:linux
Bug #901159 {Done: Bastian Blank <waldi at debian.org>} [linux-latest] linux-image-arm64: enable configuration options needed by Firefly-RK3399 board
Bug reassigned from package 'linux-latest' to 'src:linux'.
No longer marked as found in versions 94.
No longer marked as fixed in versions linux/4.16.16-1.
> fixed 901159 4.16.16-1
Bug #901159 {Done: Bastian Blank <waldi at debian.org>} [src:linux] linux-image-arm64: enable configuration options needed by Firefly-RK3399 board
Marked as fixed in versions linux/4.16.16-1.
> notfixed 896986 1.0.0-1
Bug #896986 {Done: Boyuan Yang <073plan at gmail.com>} [galternatives] [galternatives] feature request: symlink search / filter
There is no source info for the package 'galternatives' at version '1.0.0-1' with architecture ''
Unable to make a source version for version '1.0.0-1'
No longer marked as fixed in versions 1.0.0-1.
> fixed 896986 1.0.0
Bug #896986 {Done: Boyuan Yang <073plan at gmail.com>} [galternatives] [galternatives] feature request: symlink search / filter
Marked as fixed in versions galternatives/1.0.0.
> notfixed 801468 2.24+dfsg-1
Bug #801468 {Done: Pirate Praveen <praveen at onenetbeyond.org>} [node-jquery] Cannot be required and misses a dep
There is no source info for the package 'node-jquery' at version '2.24+dfsg-1' with architecture ''
Unable to make a source version for version '2.24+dfsg-1'
No longer marked as fixed in versions 2.24+dfsg-1.
> fixed 801468 2.2.4+dfsg-1
Bug #801468 {Done: Pirate Praveen <praveen at onenetbeyond.org>} [node-jquery] Cannot be required and misses a dep
Marked as fixed in versions node-jquery/2.2.4+dfsg-1.
> notfixed 649542 munin-plugins-core/2.0.0-1
Bug #649542 {Done: Lars Kruse <devel at sumpfralle.de>} [munin-plugins-core] exim_mailstats: exim_mailstats fails to bootstrap
The source munin-plugins-core and version 2.0.0-1 do not appear to match any binary packages
No longer marked as fixed in versions munin-plugins-core/2.0.0-1.
> fixed 649542 2.0.0-1
Bug #649542 {Done: Lars Kruse <devel at sumpfralle.de>} [munin-plugins-core] exim_mailstats: exim_mailstats fails to bootstrap
Marked as fixed in versions munin/2.0.0-1.
> notfixed 568938 munin-plugins-core/2.0.0-1
Bug #568938 {Done: Lars Kruse <devel at sumpfralle.de>} [munin-plugins-core] Unable to override if_ max/min from munin.conf
The source munin-plugins-core and version 2.0.0-1 do not appear to match any binary packages
No longer marked as fixed in versions munin-plugins-core/2.0.0-1.
> fixed 568938 2.0.0-1
Bug #568938 {Done: Lars Kruse <devel at sumpfralle.de>} [munin-plugins-core] Unable to override if_ max/min from munin.conf
Marked as fixed in versions munin/2.0.0-1.
> notfixed 648686 munin-plugins-core/2.0.12-1
Bug #648686 {Done: Lars Kruse <devel at sumpfralle.de>} [munin-plugins-core] Bug in bonding_err_ plugin
The source munin-plugins-core and version 2.0.12-1 do not appear to match any binary packages
No longer marked as fixed in versions munin-plugins-core/2.0.12-1.
> fixed 648686 2.0.12-1
Bug #648686 {Done: Lars Kruse <devel at sumpfralle.de>} [munin-plugins-core] Bug in bonding_err_ plugin
Marked as fixed in versions munin/2.0.12-1.
> tags 853329 + experimental
Bug #853329 {Done: Adrian Bunk <bunk at debian.org>} [src:binutils-msp430] binutils-msp430: ftbfs with GCC-7
Added tag(s) experimental.
> tags 872606 + experimental
Bug #872606 {Done: Adrian Bunk <bunk at debian.org>} [src:ruby-diaspora-federation] ruby-diaspora-federation build-depends on ruby-faraday-middleware (< 0.11~) but 0.12.2-1 is to be installed
Added tag(s) experimental.
> tags 872547 + experimental
Bug #872547 {Done: Adrian Bunk <bunk at debian.org>} [src:mapnik-reference] mapnik-reference FTBFS with nodejs 6.11.2
Added tag(s) experimental.
> tags 640168 + experimental
Bug #640168 {Done: Holger Levsen <holger at layer-acht.org>} [munin-plugins-core] acpi plugin don't work with linux kernel 3.X
Added tag(s) experimental.
> fixed 843497 238
Bug #843497 {Done: Michael Biebl <biebl at debian.org>} [systemd] systemd-networkd block the shutdown process of my nspawn container
There is no source info for the package 'systemd' at version '238' with architecture ''
Unable to make a source version for version '238'
Marked as fixed in versions 238.
> fixed 850534 3:3.2.6-2
Bug #850534 {Done: Chris Lamb <lamby at debian.org>} [redis-server] redis-server.service warns Unknown lvalue 'RunTimeDirectory' in section 'Service'
Marked as fixed in versions redis/3:3.2.6-2.
> fixed 880474 3:3.2.6-2
Bug #880474 {Done: Chris Lamb <lamby at debian.org>} [redis-server] redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'
Marked as fixed in versions redis/3:3.2.6-2.
> tags 880474 - wontfix
Bug #880474 {Done: Chris Lamb <lamby at debian.org>} [redis-server] redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'
Removed tag(s) wontfix.
> reassign 902334 src:texlive-bin
Bug #902334 {Done: Norbert Preining <preining at debian.org>} [texlive-plain-generic] texlive-plain-generic: tex4ht broken - SELFAUTOPARENT used for %%~ which doesn't work
Bug reassigned from package 'texlive-plain-generic' to 'src:texlive-bin'.
No longer marked as found in versions texlive-extra/2018.20180505-1.
No longer marked as fixed in versions texlive-bin/2018.20180416.47457-5.
> fixed 902334 2018.20180416.47457-5
Bug #902334 {Done: Norbert Preining <preining at debian.org>} [src:texlive-bin] texlive-plain-generic: tex4ht broken - SELFAUTOPARENT used for %%~ which doesn't work
Marked as fixed in versions texlive-bin/2018.20180416.47457-5.
> affects 902334 + texlive-plain-generic
Bug #902334 {Done: Norbert Preining <preining at debian.org>} [src:texlive-bin] texlive-plain-generic: tex4ht broken - SELFAUTOPARENT used for %%~ which doesn't work
Added indication that 902334 affects texlive-plain-generic
> reassign 893075 src:lttoolbox 3.4.0~r84331-1
Bug #893075 {Done: Kartik Mistry <kartik at debian.org>} [liblttoolbox3-3.3-0v5] liblttoolbox3-3.3-0v5 must be dropped since it now depends on the wrong soversion
Bug reassigned from package 'liblttoolbox3-3.3-0v5' to 'src:lttoolbox'.
No longer marked as found in versions lttoolbox/3.4.0~r84331-1.
No longer marked as fixed in versions lttoolbox/3.4.0~r84331-2 and lttoolbox/3.4.2-2.
Bug #893075 {Done: Kartik Mistry <kartik at debian.org>} [src:lttoolbox] liblttoolbox3-3.3-0v5 must be dropped since it now depends on the wrong soversion
Marked as found in versions lttoolbox/3.4.0~r84331-1.
> fixed 893075 3.4.0~r84331-2
Bug #893075 {Done: Kartik Mistry <kartik at debian.org>} [src:lttoolbox] liblttoolbox3-3.3-0v5 must be dropped since it now depends on the wrong soversion
Marked as fixed in versions lttoolbox/3.4.0~r84331-2.
> fixed 893075 3.4.2-2
Bug #893075 {Done: Kartik Mistry <kartik at debian.org>} [src:lttoolbox] liblttoolbox3-3.3-0v5 must be dropped since it now depends on the wrong soversion
Marked as fixed in versions lttoolbox/3.4.2-2.
> reassign 878657 src:libpqxx 4.0.1+dfsg3-8
Bug #878657 {Done: Marcin Kulisz <debian at kulisz.net>} [libpqxx3-dev] please drop transitional package libpqxx3-dev
Bug reassigned from package 'libpqxx3-dev' to 'src:libpqxx'.
No longer marked as found in versions libpqxx/4.0.1+dfsg3-8.
No longer marked as fixed in versions libpqxx/6.1.0-1.
Bug #878657 {Done: Marcin Kulisz <debian at kulisz.net>} [src:libpqxx] please drop transitional package libpqxx3-dev
Marked as found in versions libpqxx/4.0.1+dfsg3-8.
> fixed 878657 6.1.0-1
Bug #878657 {Done: Marcin Kulisz <debian at kulisz.net>} [src:libpqxx] please drop transitional package libpqxx3-dev
Marked as fixed in versions libpqxx/6.1.0-1.
> reassign 885673 src:pike8.0 8.0.498-1
Bug #885673 {Done: Magnus Holmgren <holmgren at debian.org>} [pike8.0-gtk] pike8.0-gtk: Depends on old GNOME libraries
Bug reassigned from package 'pike8.0-gtk' to 'src:pike8.0'.
No longer marked as found in versions pike8.0/8.0.498-1.
No longer marked as fixed in versions pike8.0/8.0.610-1.
Bug #885673 {Done: Magnus Holmgren <holmgren at debian.org>} [src:pike8.0] pike8.0-gtk: Depends on old GNOME libraries
Marked as found in versions pike8.0/8.0.498-1.
> fixed 885673 8.0.610-1
Bug #885673 {Done: Magnus Holmgren <holmgren at debian.org>} [src:pike8.0] pike8.0-gtk: Depends on old GNOME libraries
Marked as fixed in versions pike8.0/8.0.610-1.
> fixed 850947 2.4.33-1
Bug #850947 {Done: Stefan Fritsch <sf at debian.org>} [apache2] apache2: mod_http2 issue with option "Indexes" and directive "HeaderName"
Marked as fixed in versions apache2/2.4.33-1.
> reassign 898920 src:hyperkitty
Bug #898920 {Done: Pierre-Elliott Bécue <becue at crans.org>} [mailman3-web] mailman3-web: FontAwesome.otf missing
Bug reassigned from package 'mailman3-web' to 'src:hyperkitty'.
No longer marked as found in versions mailman-suite/0+20170523-14.
No longer marked as fixed in versions hyperkitty/1.1.4-5.
> fixed 898920 1.1.4-5
Bug #898920 {Done: Pierre-Elliott Bécue <becue at crans.org>} [src:hyperkitty] mailman3-web: FontAwesome.otf missing
Marked as fixed in versions hyperkitty/1.1.4-5.
> affects 898920 + mailman3-web
Bug #898920 {Done: Pierre-Elliott Bécue <becue at crans.org>} [src:hyperkitty] mailman3-web: FontAwesome.otf missing
Added indication that 898920 affects mailman3-web
> fixed 763048 1.20160109-1
Bug #763048 {Done: Lars Wirzenius <liw at liw.fi>} [python-cliapp] obnam: please check the config file specified; meaningless message provided
Marked as fixed in versions python-cliapp/1.20160109-1.
> reassign 903408 autodep8
Bug #903408 {Done: Rafael Laboissiere <rafael at debian.org>} [dh-octave-autopkgtest] octave-sockets: failing autopkgtest: 'AF_INET' undefined near line 4 column 19
Bug #903409 {Done: Rafael Laboissiere <rafael at debian.org>} [dh-octave-autopkgtest] octave-sparsersb: failing autopkgtest: 'sparsersb' undefined near line X column 4
Bug reassigned from package 'dh-octave-autopkgtest' to 'autodep8'.
Bug reassigned from package 'dh-octave-autopkgtest' to 'autodep8'.
No longer marked as found in versions dh-octave/0.5.4.
No longer marked as found in versions dh-octave/0.5.4.
No longer marked as fixed in versions autodep8/0.13.
No longer marked as fixed in versions autodep8/0.13.
> fixed 903408 0.13
Bug #903408 {Done: Rafael Laboissiere <rafael at debian.org>} [autodep8] octave-sockets: failing autopkgtest: 'AF_INET' undefined near line 4 column 19
Bug #903409 {Done: Rafael Laboissiere <rafael at debian.org>} [autodep8] octave-sparsersb: failing autopkgtest: 'sparsersb' undefined near line X column 4
Marked as fixed in versions autodep8/0.13.
Marked as fixed in versions autodep8/0.13.
> affects 903408 + dh-octave-autopkgtest
Bug #903408 {Done: Rafael Laboissiere <rafael at debian.org>} [autodep8] octave-sockets: failing autopkgtest: 'AF_INET' undefined near line 4 column 19
Bug #903409 {Done: Rafael Laboissiere <rafael at debian.org>} [autodep8] octave-sparsersb: failing autopkgtest: 'sparsersb' undefined near line X column 4
Added indication that 903408 affects dh-octave-autopkgtest
Added indication that 903409 affects dh-octave-autopkgtest
> notfixed 477297 1.15-1+deb9u1
Bug #477297 {Done: Sam Hartman <hartmans at debian.org>} [krb5-kdc] krb5-kdc: allow configuration of the listening addresses
No longer marked as fixed in versions 1.15-1+deb9u1.
> fixed 477297 1.15-1
Bug #477297 {Done: Sam Hartman <hartmans at debian.org>} [krb5-kdc] krb5-kdc: allow configuration of the listening addresses
Marked as fixed in versions krb5/1.15-1.
> reassign 853734 src:boost1.67
Bug #853734 {Done: Dimitri John Ledkov 🌈 <xnox at ubuntu.com>} [libboost-python1.63-dev] NumPy support in Boost.Python (via a new package?)
Bug reassigned from package 'libboost-python1.63-dev' to 'src:boost1.67'.
Warning: Unknown package 'src:boost1.67'
Warning: Unknown package 'src:boost1.67'
No longer marked as found in versions boost1.63/1.63.0+dfsg-1.
Warning: Unknown package 'src:boost1.67'
Warning: Unknown package 'src:boost1.67'
No longer marked as fixed in versions boost1.67/1.67.0-1.
Warning: Unknown package 'src:boost1.67'
> fixed 853734 1.67.0-1
Bug #853734 {Done: Dimitri John Ledkov 🌈 <xnox at ubuntu.com>} [src:boost1.67] NumPy support in Boost.Python (via a new package?)
Warning: Unknown package 'src:boost1.67'
Marked as fixed in versions boost1.67/1.67.0-1.
Warning: Unknown package 'src:boost1.67'
> notfixed 874702 1.6.2-1
Bug #874702 {Done: Thadeu Lima de Souza Cascardo <cascardo at debian.org>} [makedumpfile] New package version, co-maintaining proposal
There is no source info for the package 'makedumpfile' at version '1.6.2-1' with architecture ''
Unable to make a source version for version '1.6.2-1'
No longer marked as fixed in versions 1.6.2-1.
> fixed 874702 1:1.6.2-1
Bug #874702 {Done: Thadeu Lima de Souza Cascardo <cascardo at debian.org>} [makedumpfile] New package version, co-maintaining proposal
Marked as fixed in versions makedumpfile/1:1.6.2-1.
> notfixed 904663 1.11.1+dfsg.1-0.2+b1
Bug #904663 {Done: Matteo Cypriani <mcy at lm7.fr>} [libtag1v5] libtag1v5: Package can't be updated
No longer marked as fixed in versions 1.11.1+dfsg.1-0.2+b1.
> reassign 878863 src:scikit-learn 0.14.1-3
Bug #878863 {Done: Yaroslav Halchenko <debian at onerussian.com>} [python-scikits-learn] please drop transitional package python-scikits-learn
Bug reassigned from package 'python-scikits-learn' to 'src:scikit-learn'.
No longer marked as found in versions scikit-learn/0.14.1-3.
No longer marked as fixed in versions scikit-learn/0.19.2-1.
Bug #878863 {Done: Yaroslav Halchenko <debian at onerussian.com>} [src:scikit-learn] please drop transitional package python-scikits-learn
Marked as found in versions scikit-learn/0.14.1-3.
> fixed 878863 0.19.2-1
Bug #878863 {Done: Yaroslav Halchenko <debian at onerussian.com>} [src:scikit-learn] please drop transitional package python-scikits-learn
Marked as fixed in versions scikit-learn/0.19.2-1.
> reassign 819172 src:lightbeam 1.3.0+dfsg-1
Bug #819172 {Done: Jeremy Bicha <jbicha at debian.org>} [xul-ext-lightbeam] xul-ext-lightbeam: should depend on firefox-esr | firefox instead of iceweasel
Bug reassigned from package 'xul-ext-lightbeam' to 'src:lightbeam'.
No longer marked as found in versions lightbeam/1.3.0+dfsg-1.
No longer marked as fixed in versions 2.1.0-2.
Bug #819172 {Done: Jeremy Bicha <jbicha at debian.org>} [src:lightbeam] xul-ext-lightbeam: should depend on firefox-esr | firefox instead of iceweasel
Marked as found in versions lightbeam/1.3.0+dfsg-1.
> fixed 819172 2.1.0-2
Bug #819172 {Done: Jeremy Bicha <jbicha at debian.org>} [src:lightbeam] xul-ext-lightbeam: should depend on firefox-esr | firefox instead of iceweasel
Marked as fixed in versions lightbeam/2.1.0-2.
> reassign 904157 src:eproject-el
Bug #904157 {Done: Nicholas D Steeves <nsteeves at gmail.com>} [src:emacs-goodies-el] drop eproject and possibly package elpa-eproject
Bug reassigned from package 'src:emacs-goodies-el' to 'src:eproject-el'.
Warning: Unknown package 'src:eproject-el'
Warning: Unknown package 'src:eproject-el'
No longer marked as found in versions emacs-goodies-el/38.0.
Warning: Unknown package 'src:eproject-el'
Warning: Unknown package 'src:eproject-el'
No longer marked as fixed in versions eproject-el/1.5+git20180312.068218d-1.
Warning: Unknown package 'src:eproject-el'
> fixed 904157 1.5+git20180312.068218d-1
Bug #904157 {Done: Nicholas D Steeves <nsteeves at gmail.com>} [src:eproject-el] drop eproject and possibly package elpa-eproject
Warning: Unknown package 'src:eproject-el'
Marked as fixed in versions eproject-el/1.5+git20180312.068218d-1.
Warning: Unknown package 'src:eproject-el'
> reassign 585098 src:kde4libs
Bug #585098 {Done: Pino Toscano <pino at debian.org>} [libnepomuk4] virtuoso-opensource-6.1-bin: virtuoso indexer takes up too many resources
Bug reassigned from package 'libnepomuk4' to 'src:kde4libs'.
Ignoring request to alter found versions of bug #585098 to the same values previously set
No longer marked as fixed in versions kde4libs/4:4.14.38-2.
> fixed 585098 4:4.14.38-2
Bug #585098 {Done: Pino Toscano <pino at debian.org>} [src:kde4libs] virtuoso-opensource-6.1-bin: virtuoso indexer takes up too many resources
Marked as fixed in versions kde4libs/4:4.14.38-2.
> reassign 674692 src:kde4libs 4:4.7.4-4
Bug #674692 {Done: Pino Toscano <pino at debian.org>} [libnepomuk4] libnepomuk4: Nepomuk complains about missing virtuoso server resp. virtuoso soprano plugin
Bug reassigned from package 'libnepomuk4' to 'src:kde4libs'.
No longer marked as found in versions kde4libs/4:4.7.4-4.
No longer marked as fixed in versions kde4libs/4:4.14.38-2.
Bug #674692 {Done: Pino Toscano <pino at debian.org>} [src:kde4libs] libnepomuk4: Nepomuk complains about missing virtuoso server resp. virtuoso soprano plugin
Marked as found in versions kde4libs/4:4.7.4-4.
> fixed 674692 4:4.14.38-2
Bug #674692 {Done: Pino Toscano <pino at debian.org>} [src:kde4libs] libnepomuk4: Nepomuk complains about missing virtuoso server resp. virtuoso soprano plugin
Marked as fixed in versions kde4libs/4:4.14.38-2.
> tags 791274 =
Bug #791274 {Done: Julien Puydt <jpuydt at debian.org>} [src:scilab] scilab: library transition may be needed when GCC 5 is the default
Removed tag(s) sid, buster, and stretch.
> tags 859829 + experimental
Bug #859829 {Done: Ferenc Wágner <wferi at debian.org>} [xml-security-c] xml-security-c: Please migrate to openssl1.1 in Buster
Added tag(s) experimental.
> reassign 638485 src:bidiui
Bug #638485 {Done: Lior Kaplan <kaplan at debian.org>} [icedove-bidiui] icedove-bidiui: Please fix extension files path
Bug reassigned from package 'icedove-bidiui' to 'src:bidiui'.
Ignoring request to alter found versions of bug #638485 to the same values previously set
No longer marked as fixed in versions bidiui/0.9.7-2.
> fixed 638485 0.9.7-2
Bug #638485 {Done: Lior Kaplan <kaplan at debian.org>} [src:bidiui] icedove-bidiui: Please fix extension files path
Marked as fixed in versions bidiui/0.9.7-2.
> tags 859831 + experimental
Bug #859831 {Done: Ferenc Wágner <wferi at debian.org>} [xmltooling] xmltooling: Please migrate to openssl1.1 in Buster
Added tag(s) experimental.
> reassign 857792 src:bidiui 0.9.7-1
Bug #857792 {Done: Lior Kaplan <kaplanlior at gmail.com>} [icedove-bidiui] icedove-bidiui needs to become thunderbird-bidiui
Bug reassigned from package 'icedove-bidiui' to 'src:bidiui'.
No longer marked as found in versions bidiui/0.9.7-1.
No longer marked as fixed in versions 0.9.7-2 and bidiui/0.9.7-2.
Bug #857792 {Done: Lior Kaplan <kaplanlior at gmail.com>} [src:bidiui] icedove-bidiui needs to become thunderbird-bidiui
Marked as found in versions bidiui/0.9.7-1.
> fixed 857792 0.9.7-2
Bug #857792 {Done: Lior Kaplan <kaplanlior at gmail.com>} [src:bidiui] icedove-bidiui needs to become thunderbird-bidiui
Marked as fixed in versions bidiui/0.9.7-2.
> notfixed 905016 5.0.1-11+b1
Bug #905016 {Done: Ralf Treinen <treinen at irif.fr>} [dose-distcheck] dose-debcheck no longer accepts gzip compressed Packages
No longer marked as fixed in versions 5.0.1-11+b1.
> found 903978 0.3.4-1
Bug #903978 {Done: Reto Buerki <reet at codelabs.ch>} [src:anet] anet: please transition to gcc-8
Marked as found in versions anet/0.3.4-1.
> notfixed 904950 1.6.1.0-1
Bug #904950 {Done: Rene Engelhard <rene at debian.org>} [libreoffice] libreoffice: lost ability to remove single files from Recent Files dialog
There is no source info for the package 'libreoffice' at version '1.6.1.0-1' with architecture ''
Unable to make a source version for version '1.6.1.0-1'
No longer marked as fixed in versions 1.6.1.0-1.
> fixed 904950 1:6.1.0-1
Bug #904950 {Done: Rene Engelhard <rene at debian.org>} [libreoffice] libreoffice: lost ability to remove single files from Recent Files dialog
Marked as fixed in versions libreoffice/1:6.1.0-1.
> reassign 905253 src:txtorcon 18.0.2-1
Bug #905253 {Done: irl at debian.org (Iain R. Learmonth)} [python-txtorcon] python-txtorcon: fails to install with Python 3.7
Bug reassigned from package 'python-txtorcon' to 'src:txtorcon'.
No longer marked as found in versions txtorcon/18.0.2-1.
No longer marked as fixed in versions txtorcon/18.0.2-2.
Bug #905253 {Done: irl at debian.org (Iain R. Learmonth)} [src:txtorcon] python-txtorcon: fails to install with Python 3.7
Marked as found in versions txtorcon/18.0.2-1.
> fixed 905253 18.0.2-2
Bug #905253 {Done: irl at debian.org (Iain R. Learmonth)} [src:txtorcon] python-txtorcon: fails to install with Python 3.7
Marked as fixed in versions txtorcon/18.0.2-2.
> found 903970 0.5.2-3
Bug #903970 {Done: Adrian-Ken Rueegsegger <ken at codelabs.ch>} [src:libalog] libalog: please rebuild against gnat-8
Marked as found in versions libalog/0.5.2-3.
> reassign 615419 src:pidgin-extprefs
Bug #615419 {Done: Adrian Bunk <bunk at debian.org>} [gaim-extendedprefs] gaim-extendedprefs: please use Homepage field to point to upstream homepage
Bug reassigned from package 'gaim-extendedprefs' to 'src:pidgin-extprefs'.
Ignoring request to alter found versions of bug #615419 to the same values previously set
No longer marked as fixed in versions pidgin-extprefs/0.7-3.
> fixed 615419 0.7-3
Bug #615419 {Done: Adrian Bunk <bunk at debian.org>} [src:pidgin-extprefs] gaim-extendedprefs: please use Homepage field to point to upstream homepage
Marked as fixed in versions pidgin-extprefs/0.7-3.
> reassign 878371 src:c-icap-modules 1:0.4.4-1
Bug #878371 {Done: Mathieu Parent <sathieu at debian.org>} [libc-icap-mod-clamav] please drop transitional package libc-icap-mod-clamav
Bug reassigned from package 'libc-icap-mod-clamav' to 'src:c-icap-modules'.
No longer marked as found in versions c-icap-modules/1:0.4.4-1.
No longer marked as fixed in versions c-icap-modules/1:0.5.1-1.
Bug #878371 {Done: Mathieu Parent <sathieu at debian.org>} [src:c-icap-modules] please drop transitional package libc-icap-mod-clamav
Marked as found in versions c-icap-modules/1:0.4.4-1.
> fixed 878371 1:0.5.1-1
Bug #878371 {Done: Mathieu Parent <sathieu at debian.org>} [src:c-icap-modules] please drop transitional package libc-icap-mod-clamav
Marked as fixed in versions c-icap-modules/1:0.5.1-1.
> reassign 904991 src:mozjs60 52.3.1-9
Bug #904991 {Done: Simon McVittie <smcv at debian.org>} [src:mozjs52] mozjs52: new upstream release 60
Bug reassigned from package 'src:mozjs52' to 'src:mozjs60'.
Warning: Unknown package 'src:mozjs60'
Warning: Unknown package 'src:mozjs60'
No longer marked as found in versions mozjs52/52.3.1-9.
Warning: Unknown package 'src:mozjs60'
Warning: Unknown package 'src:mozjs60'
No longer marked as fixed in versions mozjs60/60.1.0-1.
Warning: Unknown package 'src:mozjs60'
Bug #904991 {Done: Simon McVittie <smcv at debian.org>} [src:mozjs60] mozjs52: new upstream release 60
Warning: Unknown package 'src:mozjs60'
The source 'mozjs60' and version '52.3.1-9' do not appear to match any binary packages
Marked as found in versions mozjs60/52.3.1-9.
Warning: Unknown package 'src:mozjs60'
> fixed 904991 60.1.0-1
Bug #904991 {Done: Simon McVittie <smcv at debian.org>} [src:mozjs60] mozjs52: new upstream release 60
Warning: Unknown package 'src:mozjs60'
Marked as fixed in versions mozjs60/60.1.0-1.
Warning: Unknown package 'src:mozjs60'
> reassign 905199 src:mozjs60 52.3.1-9
Bug #905199 {Done: Simon McVittie <smcv at debian.org>} [src:mozjs52] mozjs52: Please update debian/test.sh to add sparc64, remove ppc64el from ignore list
Bug reassigned from package 'src:mozjs52' to 'src:mozjs60'.
Warning: Unknown package 'src:mozjs60'
Warning: Unknown package 'src:mozjs60'
No longer marked as found in versions mozjs52/52.3.1-9.
Warning: Unknown package 'src:mozjs60'
Warning: Unknown package 'src:mozjs60'
No longer marked as fixed in versions mozjs60/60.1.0-1.
Warning: Unknown package 'src:mozjs60'
Bug #905199 {Done: Simon McVittie <smcv at debian.org>} [src:mozjs60] mozjs52: Please update debian/test.sh to add sparc64, remove ppc64el from ignore list
Warning: Unknown package 'src:mozjs60'
The source 'mozjs60' and version '52.3.1-9' do not appear to match any binary packages
Marked as found in versions mozjs60/52.3.1-9.
Warning: Unknown package 'src:mozjs60'
> fixed 905199 60.1.0-1
Bug #905199 {Done: Simon McVittie <smcv at debian.org>} [src:mozjs60] mozjs52: Please update debian/test.sh to add sparc64, remove ppc64el from ignore list
Warning: Unknown package 'src:mozjs60'
Marked as fixed in versions mozjs60/60.1.0-1.
Warning: Unknown package 'src:mozjs60'
> notfound 905664 1.2.1-1
Bug #905664 {Done: Harlan Lieberman-Berg <hlieberman at debian.org>} [src:python-pyhsm] python-pyhsm: maintscript accesses internal dpkg database
No longer marked as found in versions python-pyhsm/1.2.1-1.
> found 905664 1.2.0-1
Bug #905664 {Done: Harlan Lieberman-Berg <hlieberman at debian.org>} [src:python-pyhsm] python-pyhsm: maintscript accesses internal dpkg database
Marked as found in versions python-pyhsm/1.2.0-1.
> reassign 907784 src:texlive-bin
Bug #907784 {Done: Norbert Preining <preining at debian.org>} [texlive-xetex] texlive-xetex: The output is damaged if one compiles the tex file twice
Bug reassigned from package 'texlive-xetex' to 'src:texlive-bin'.
No longer marked as found in versions texlive-base/2018.20180824-1.
No longer marked as fixed in versions texlive-bin/2018.20180907.48586-1.
> fixed 907784 2018.20180907.48586-1
Bug #907784 {Done: Norbert Preining <preining at debian.org>} [src:texlive-bin] texlive-xetex: The output is damaged if one compiles the tex file twice
Marked as fixed in versions texlive-bin/2018.20180907.48586-1.
> affects 907784 + texlive-xetex
Bug #907784 {Done: Norbert Preining <preining at debian.org>} [src:texlive-bin] texlive-xetex: The output is damaged if one compiles the tex file twice
Added indication that 907784 affects texlive-xetex
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
477297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477297
510877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510877
513536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513536
554906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554906
568938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568938
585098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585098
615419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615419
638485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638485
640168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640168
648686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648686
649542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649542
674692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674692
690197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690197
763048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763048
787498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787498
789594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789594
791274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791274
801468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801468
811308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811308
812429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812429
814287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814287
819172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819172
842316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842316
843497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843497
846923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846923
849748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849748
850534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850534
850947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850947
853329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853329
853734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853734
857792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857792
859829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859829
859831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859831
865493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865493
866500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866500
867429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867429
871771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871771
872547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872547
872606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872606
874702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874702
877704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877704
878112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878112
878371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878371
878606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878606
878657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878657
878863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878863
879476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879476
880474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880474
880593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880593
881361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881361
883074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883074
885553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885553
885673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885673
888248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888248
888249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888249
889609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889609
893075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893075
893920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893920
894923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894923
896514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896514
896986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896986
898890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898890
898920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898920
899077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899077
901159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901159
902334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902334
903408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903408
903409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903409
903970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903970
903978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903978
904157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904157
904663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904663
904950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904950
904991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904991
905016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905016
905199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905199
905253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905253
905664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905664
907784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907784
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From noreply at release.debian.org  Sun Oct 21 05:39:18 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Sun, 21 Oct 2018 04:39:18 +0000
Subject: [Pkg-privacy-maintainers] monkeysphere 0.42-2 MIGRATED to testing
Message-ID: <E1gE5WI-0001QO-Cy@respighi.debian.org>

FYI: The status of the monkeysphere source package
in Debian's testing distribution has changed.

  Previous version: (not in testing)
  Current version:  0.42-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From intrigeri at debian.org  Sun Oct 21 08:50:09 2018
From: intrigeri at debian.org (intrigeri)
Date: Sun, 21 Oct 2018 09:50:09 +0200
Subject: [Pkg-privacy-maintainers] Bug#909517: torify: does not expand
 shell aliases
In-Reply-To: <153780862608.13647.11597877222826426288.reportbug@wicksell>
References: <153780862608.13647.11597877222826426288.reportbug@wicksell>
Message-ID: <85va5voi1a.fsf@boum.org>

Control: reassign -1 torsocks

Hi Jeff,

(almost fully quoting for the torsocks maintainers' sake)

Jeff Cliff:
> It is often handy to create shell aliases to do tasks that would otherwise require a lot
> of retyping the same thing over and over.  For example 'git push' might very well be
> aliased to 'push' at the shell level by 

> alias push='git push'

> then you could conceivably use 

>> torify push 

> as a shorthand for 

>> torify git push <git url>

> this however fails: torify does not expand the aliases and doesn't know what 'push' is.

Nowadays torify is a mere wrapper around torsocks ⇒ reassigning.

> As mentioned in the ubuntu downstream bug ( https://bugs.launchpad.net/ubuntu/+source/tor/+bug/1687037 )
> it doesn't matter what shell you use, torify just doesn't check.

> what happens: torify takes the arguments passed in without checking if there are aliases involved
> what should happen: is torify should be alias-aware.

Cheers,
-- 
intrigeri


From owner at bugs.debian.org  Sun Oct 21 08:51:05 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sun, 21 Oct 2018 07:51:05 +0000
Subject: [Pkg-privacy-maintainers] Processed: Re: Bug#909517: torify: does
 not expand shell aliases
References: <85va5voi1a.fsf@boum.org>
 <153780862608.13647.11597877222826426288.reportbug@wicksell>
Message-ID: <handler.s.B909517.154010821615585.transcript@bugs.debian.org>

Processing control commands:

> reassign -1 torsocks
Bug #909517 [tor] torify: does not expand shell aliases
Bug reassigned from package 'tor' to 'torsocks'.
No longer marked as found in versions tor/0.3.4.8-1.
Ignoring request to alter fixed versions of bug #909517 to the same values previously set

-- 
909517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909517
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ftpmaster at ftp-master.debian.org  Tue Oct 23 19:52:01 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 23 Oct 2018 18:52:01 +0000
Subject: [Pkg-privacy-maintainers] Processing of mat2_0.5.0-1_source.changes
Message-ID: <E1gF1mb-0000CW-7w@usper.debian.org>

mat2_0.5.0-1_source.changes uploaded successfully to localhost
along with the files:
  mat2_0.5.0-1.dsc
  mat2_0.5.0.orig.tar.xz
  mat2_0.5.0.orig.tar.xz.asc
  mat2_0.5.0-1.debian.tar.xz
  mat2_0.5.0-1_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Tue Oct 23 20:04:42 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 23 Oct 2018 19:04:42 +0000
Subject: [Pkg-privacy-maintainers] mat2_0.5.0-1_source.changes ACCEPTED into
 unstable
Message-ID: <E1gF1ys-000CtD-Hm@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Tue, 23 Oct 2018 18:27:37 +0000
Source: mat2
Binary: mat2
Architecture: source
Version: 0.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Georg Faerber <georg at riseup.net>
Description:
 mat2       - Metadata anonymisation toolkit v2
Changes:
 mat2 (0.5.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * d/control:
     - Add 'ffmpeg' as a build dependency and as a suggested package to clean
       '.avi' files.
     - Add '.avi' to list of supported file formats.
   * d/mat2.docs:
     - Install documentation about implementation and threat model.
   * d/patches:
     - Drop patches, released upstream.
   * d/t/control:
     - Install 'ffmpeg' to check cleaning of '.avi' files.
   * d/gitlab-ci.yml:
     - Checkout the git 'pristine-tar' branch before the build.
 .
   [ Jonas Meurer ]
   * d/gbp.conf:
     - Enable 'pristine-tar = True'.
Checksums-Sha1:
 17be47d6af62b71bcc6e2e4a66bbfc6e395baf0b 2385 mat2_0.5.0-1.dsc
 4d71dc69a8d678841ba81b866a51d6fba94d8399 3356528 mat2_0.5.0.orig.tar.xz
 8fb200643cf5dc3b8d2803d8c9ff8832c18db098 833 mat2_0.5.0.orig.tar.xz.asc
 a8ab7e72bcb209e3d4b2e0d3ccf3514b79a59e65 7188 mat2_0.5.0-1.debian.tar.xz
 72396d18a7d8e40f2d5a800676644a16f5d2159d 11708 mat2_0.5.0-1_amd64.buildinfo
Checksums-Sha256:
 310481d11a8ec7f76fef385d18cb71c1c8731933fc0c2149f4d5300c3f9a0385 2385 mat2_0.5.0-1.dsc
 b7514ace65801117bf023a44886e3949613b339e055a4b5e80b65ca95f68ff9e 3356528 mat2_0.5.0.orig.tar.xz
 06b0a33c382537d4716f5bf2bad6ba98b2a15ab4300dff3363983cd9ec2493c0 833 mat2_0.5.0.orig.tar.xz.asc
 448844e913bfd1ed58c1d5b4c664ca121c2a88545e2aacb04ed05b3c66fbb82d 7188 mat2_0.5.0-1.debian.tar.xz
 075dcef692b206149a07cf7e20197131906c5f41cf295d18d0ff458d327fef8e 11708 mat2_0.5.0-1_amd64.buildinfo
Files:
 b1f3639f7081ad8abd928bc3946fc7dc 2385 utils optional mat2_0.5.0-1.dsc
 3d9c7060fd468605dabc010f60a390de 3356528 utils optional mat2_0.5.0.orig.tar.xz
 d9510afe1baa89551ceee2ac23698275 833 utils optional mat2_0.5.0.orig.tar.xz.asc
 5965cf48c45eb71f262c9c5111080b78 7188 utils optional mat2_0.5.0-1.debian.tar.xz
 0783ba248f74367657da274209cf305e 11708 utils optional mat2_0.5.0-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEE4p3Q++yWB9ljva4NWtdbQU6kFmcFAlvPad0ACgkQWtdbQU6k
FmfbFg//VL2D7PGiD0A1PjDUsILAjMT+xTI0XG5jsiUU61ShYYpGtRPsp1k1bnWa
00QaaCcOUQRVHuM7kqedMA7l+x5FNy4bu1/uepYabQuvit8WUVc3E4xudrrez0LT
zHuxAxaPEV2tonlbNtmfT77yezvb7QG+h7elkwrjW/O/2N1G57vBM8AxIZ89i5pf
dECdVA8XQi/5EXPVfiQooapd+mNONhaUjH+mWPUGJZUuu6DBw7uJRPhTVS1Hxk6C
B3wB2vEiT4Y83+rFVLySoRu73loOOsICcCPnZ9RUInWElgRnsXLtVLXxa/+dm84b
QSb4s6WqftI3RIVwljY9od7R4crgCZ0lYrMNR12Gn0xQ87DL0dRAw1R/iBFShfVR
8LDuMddKx8Wt5tA3k/Y6Z6r5Ud5KHSmMZjphT1W/2nZ8331E/+mpXEooQFoMT9VA
cL5Sms0Cvhi4ifWT5ryq/EQe1OrLGUjwBp7prKCEurUy/o315GMN9mEAw+ooZAJt
HTvcYtfi4S6DNsoYMo7Io7pqMhnsVi/c76UrZB9H+EghcHrCkAK6Bwzw2ozHDiI8
MJ4K1cLxHqdR9ym5q7Zp131Z6FDoApklv0DI6NuAwbZWPK/eI0+w05iL+AQNsFXu
vp3ZmWKBggt8Anae502JRqlkZZRk7QXaPghFeYBRDvmkxajGjdg=
=P+Lc
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Wed Oct 24 07:43:01 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 24 Oct 2018 06:43:01 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 hexchat-otr_0.2.2-2_source.changes
Message-ID: <E1gFCsg-00060G-1J@usper.debian.org>

hexchat-otr_0.2.2-2_source.changes uploaded successfully to localhost
along with the files:
  hexchat-otr_0.2.2-2.dsc
  hexchat-otr_0.2.2-2.debian.tar.xz
  hexchat-otr_0.2.2-2_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Wed Oct 24 07:48:59 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 24 Oct 2018 06:48:59 +0000
Subject: [Pkg-privacy-maintainers] hexchat-otr_0.2.2-2_source.changes
 ACCEPTED into unstable
Message-ID: <E1gFCyR-0006ST-6q@fasolo.debian.org>



Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 24 Oct 2018 08:28:40 +0200
Source: hexchat-otr
Binary: hexchat-otr
Architecture: source
Version: 0.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Petter Reinholdtsen <pere at debian.org>
Description:
 hexchat-otr - hexchat plugin to support Off The Record (OTR)
Changes:
 hexchat-otr (0.2.2-2) unstable; urgency=medium
 .
   * Changed Vcs-* links in d/control.
   * Documented patch naming scheme.
   * Added 1000-prototypes.patch to get rid of compiler warning.
   * Updated Standards-Version from 4.0.0 to 4.2.1.
Checksums-Sha1:
 f826ac050bc6ddde27bb2f7d5529dd27db75f90e 2051 hexchat-otr_0.2.2-2.dsc
 b627d534beb4e72b5e4356458173961b5995aa29 4268 hexchat-otr_0.2.2-2.debian.tar.xz
 82c6e2fd85d96dc7c2b4225865f2b19e6e6851a5 6573 hexchat-otr_0.2.2-2_source.buildinfo
Checksums-Sha256:
 61b2c85568e35cb97f116857923ef506d509aec8b7fe6335eadfb4768f5e4e2a 2051 hexchat-otr_0.2.2-2.dsc
 453c932341cddbc09a164ea5b144efa92671e3b896784d8a37eb3e7c4102f5b3 4268 hexchat-otr_0.2.2-2.debian.tar.xz
 757008ee5cc56dc036d602ac605f3dfa91ab546d1c3143d20d3d4ccb81aed31d 6573 hexchat-otr_0.2.2-2_source.buildinfo
Files:
 c69976a95434fc822aca5962eb8a2f89 2051 misc optional hexchat-otr_0.2.2-2.dsc
 1ca8aca4779a33bd326e2d0586d9c706 4268 misc optional hexchat-otr_0.2.2-2.debian.tar.xz
 b8523fe9192b0ff6d430eed567a5e913 6573 misc optional hexchat-otr_0.2.2-2_source.buildinfo

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

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAlvQEX8ACgkQgSgKoIe6
+w6Y1Q/9GfYEI9kk7MPZ+xjSc6a/+5+Gw54mwZ6Un+ibVYrOXB6Fwyyy+CYsVqWr
7J6AL02vymZHczALWNTGOmJoWobB3ZSmeRCCzhhuu1F223fx0T5sb9+oAoZxJQRL
JXD50m/t/v8S+7P/grXp99x7ixcz72q4CD+CvnJzIAt8qTnq4a9+PQ/bj0HNw/uH
o8v2lM0c3uHeeCp8iPvn1cqqe4PLXlLxrEoXX/IaVmmPyf8wXzQuuayHBDCuMxYI
e7FgRddONJMK/exqMIkSZPAMRdLHbAG8uhlQDrY2O03D7gUh/VCqm+torEX9XMXt
2CZH0astvQMVRVkh8tDUaCHQLxJkkHZSu0xsarz5AwYSopRdY8Q/bbZ2eSkTQjwd
kacHMLXJjZX1OJAlwCODjImOMbU/4UARWMKLigeqT6HdgYB9dBF1q2+oXiHbBkl4
qQF9SP1zcMeKFCfbsGa6GnEmxhoaFcS884QweAjbfVig6Kq6gdLK/GSGu9+LTFut
4cRj/PhXxyzJBcClmQ8F9D++buEgO+ccuNNJN9W7jpF2dLoZ9FMa4xcFFHoF4Spt
Bbr/2lX2/4GYTaxPAZKKkDmzUP1QWnMEHI+mAy5XYy8+h9p9oZAcaeWiuvPdlAFf
AUSER/3xaM9g7JaCi+XDEW7ZRtE4Zc7BKAaUETpGHvsGDG2fNlk=
=zjFl
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ulrike at debian.org  Wed Oct 24 15:17:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Wed, 24 Oct 2018 14:17:00 +0000
Subject: [Pkg-privacy-maintainers] Bug#911764: nautilus-wipe should confirm
 that it is cancelling the wipe process as soon as the user cancels
Message-ID: <428b2bc0-205f-9de0-da93-b2dad528bcf7@debian.org>

Package: nautilus-wipe
Severity: wishlist

Dear Maintainer,

The current user flow for cancelling a Wipe Available Disk Space process
needs some UX love.

Current situation:

When using the "Wipe Available Disk Space" feature on a 4GB FAT
formatted drive, the process seemed to be taking to long so a user
cancelled, after which a confirmation dialog appears and "Cancel
operation" is pressed. When that happens, the confirmation dialog
disappears but the Wipe Available Disk Space dialog is still there,
unchanged, and seems like it's ignoring the cancel request for a period
of time close to a minute before a cryptic message finally appears to
confirm it was cancelled.

How should the software behave:

Ideally, this flow should change so that when a user confirms the
cancellation, the Wipe Available Disk Space dialog should change to
indicate that the cancellation is being processed. This can be as simple
as changing the "Wiping available disk space..." copy to "Cancelling..."
Instead of seeing a cryptic message when the cancellation kicks in, the
displayed cancellation confirmation should just say that the wipe was
cancelled.

This was reported here: https://labs.riseup.net/code/issues/16066

I have contacted the upstream author by email, as indicated here:
https://wipetools.tuxfamily.org/nautilus-wipe.html


From ftpmaster at ftp-master.debian.org  Wed Oct 24 15:41:12 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 24 Oct 2018 14:41:12 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 nautilus-wipe_0.3-2_amd64.changes
Message-ID: <E1gFKLQ-00082f-V9@usper.debian.org>

nautilus-wipe_0.3-2_amd64.changes uploaded successfully to localhost
along with the files:
  nautilus-wipe_0.3-2.dsc
  nautilus-wipe_0.3-2.debian.tar.xz
  nautilus-wipe-dbgsym_0.3-2_amd64.deb
  nautilus-wipe_0.3-2_amd64.buildinfo
  nautilus-wipe_0.3-2_amd64.deb

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Wed Oct 24 15:51:54 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 24 Oct 2018 14:51:54 +0000
Subject: [Pkg-privacy-maintainers] nautilus-wipe_0.3-2_amd64.changes REJECTED
Message-ID: <E1gFKVm-0006zm-LB@fasolo.debian.org>



nautilus-wipe_0.3-2.dsc: Invalid size hash for nautilus-wipe_0.3.orig.tar.gz:
According to the control file the size hash should be 471521,
but nautilus-wipe_0.3.orig.tar.gz has 468902.

If you did not include nautilus-wipe_0.3.orig.tar.gz in your upload, a different version
might already be known to the archive software.



===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.



From ftpmaster at ftp-master.debian.org  Wed Oct 24 16:06:15 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 24 Oct 2018 15:06:15 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 nautilus-wipe_0.3-2_amd64.changes
Message-ID: <E1gFKjf-0000tm-FD@usper.debian.org>

nautilus-wipe_0.3-2_amd64.changes uploaded successfully to localhost
along with the files:
  nautilus-wipe_0.3-2.dsc
  nautilus-wipe_0.3-2.debian.tar.xz
  nautilus-wipe-dbgsym_0.3-2_amd64.deb
  nautilus-wipe_0.3-2_amd64.buildinfo
  nautilus-wipe_0.3-2_amd64.deb
  nautilus-wipe_0.3.orig.tar.gz

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Wed Oct 24 16:19:26 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 24 Oct 2018 15:19:26 +0000
Subject: [Pkg-privacy-maintainers] nautilus-wipe_0.3-2_amd64.changes REJECTED
Message-ID: <E1gFKwQ-000Biz-AZ@fasolo.debian.org>


nautilus-wipe_0.3.orig.tar.gz: Does not match file already existing in the pool.




===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.



From ftpmaster at ftp-master.debian.org  Thu Oct 25 14:44:59 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 25 Oct 2018 13:44:59 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 nautilus-wipe_0.3-2_amd64.changes
Message-ID: <E1gFfwZ-0001Of-IJ@usper.debian.org>

nautilus-wipe_0.3-2_amd64.changes uploaded successfully to localhost
along with the files:
  nautilus-wipe_0.3-2.dsc
  nautilus-wipe_0.3-2.debian.tar.xz
  nautilus-wipe-dbgsym_0.3-2_amd64.deb
  nautilus-wipe_0.3-2_amd64.buildinfo
  nautilus-wipe_0.3-2_amd64.deb
  nautilus-wipe_0.3.orig.tar.gz

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Thu Oct 25 14:50:20 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 25 Oct 2018 13:50:20 +0000
Subject: [Pkg-privacy-maintainers] nautilus-wipe_0.3-2_amd64.changes
 ACCEPTED into unstable
Message-ID: <E1gFg1k-000BFC-DM@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Thu, 25 Oct 2018 15:32:53 CEST
Source: nautilus-wipe
Binary: nautilus-wipe
Architecture: source amd64
Version: 0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Ulrike Uhlig <ulrike at debian.org>
Description:
 nautilus-wipe - Secure deletion extension for Nautilus
Changes:
 nautilus-wipe (0.3-2) unstable; urgency=medium
 .
   * debian/control:
     - Add myself to uploads.
     - Change VCS to Salsa.
     - Add Multi-Arch entry.
   * debian/gbp.conf:
     - Use pristite-tar.
Checksums-Sha256: 
 4dbb7809af53b568d377f083862a5b0c5a5b0137ff86eb5a8c22be77caa10b3e 2203 nautilus-wipe_0.3-2.dsc
 1639be295c1b1aeefbf8d585470ad24816f1c090005c13f385424f06b89d54c0 6804 nautilus-wipe_0.3-2.debian.tar.xz
 d70c5367314c5462a60755c70777d4d702f473f13f8f2bdfe7a0db140cb36c6e 74712 nautilus-wipe-dbgsym_0.3-2_amd64.deb
 3869ccf2826bffff1a85adc78d30e1b00bb163e5c714a1611aa704815083ffca 14529 nautilus-wipe_0.3-2_amd64.buildinfo
 6a8ec31e3094fa20aaaaae32a130e2dc0f5a3bbbe454711f05316ecaab775b2d 35864 nautilus-wipe_0.3-2_amd64.deb
 d8a94c2b4e17a6e619bc5da79d45c447f9938f82cf9050f0d46b44a1ea620432 468902 nautilus-wipe_0.3.orig.tar.gz
Checksums-Sha1: 
 60507725d84c1183f1df7b96933e30ea1f18c01a 2203 nautilus-wipe_0.3-2.dsc
 13b0d5c2f921724bc37d45f161f9a6b2ad469792 6804 nautilus-wipe_0.3-2.debian.tar.xz
 2b974d424ceba36345d25b8c454906ac31599a3c 74712 nautilus-wipe-dbgsym_0.3-2_amd64.deb
 27558f08eeb039bf82533bdad843a407db6aad41 14529 nautilus-wipe_0.3-2_amd64.buildinfo
 f9ca69f2896c0ef0928807796b1ffc2c61cb9e88 35864 nautilus-wipe_0.3-2_amd64.deb
 a2382ab0f848216e368d87ca6df49626333557aa 468902 nautilus-wipe_0.3.orig.tar.gz
Files: 
 37e9f737f48eb374de4bcae4d1d15b76 2203 utils optional nautilus-wipe_0.3-2.dsc
 864980b1ac0caad96bc276c5e1a258c3 6804 utils optional nautilus-wipe_0.3-2.debian.tar.xz
 5109c6a8c378428e2579d4e7b28adb51 74712 debug extra nautilus-wipe-dbgsym_0.3-2_amd64.deb
 221f8e39c1840bf1a20f58deb6980d50 14529 utils optional nautilus-wipe_0.3-2_amd64.buildinfo
 c346364a4b676fded0e9d351bb2c46a5 35864 utils optional nautilus-wipe_0.3-2_amd64.deb
 89f81a331d072c051cd8423a8fbbda9f 468902 utils optional nautilus-wipe_0.3.orig.tar.gz

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

iQJGBAEBCgAwFiEE7eP0RD800mGVFNeQsUuww42GHPEFAlvRxhoSHHVscmlrZUBk
ZWJpYW4ub3JnAAoJELFLsMONhhzxa/0P/08Ytku0ICrnunCGzqKJXIz2/0Oz+cbY
4y9aaj5pq9B+bpw6jHLAtGgyl3AkImcVogiA7fA4k41yi8B90Ci68615MOjOEBAw
PkyeWOJ+/PZ6eNWWq4sSPn56n6ktaZITo5VqO14DWguPpTVf1jnf6/V2njX5Ou1e
Nkk6CcfPkLKu9yJWdvE4/zBOt9/N1qpE98etyvpenY2YCvMW7/keeR60BQbCAhIB
Od9KqvFdx5puc23bfpQRp1Ld/AZvOsGhj/DsOdfDNZdL2XusQvBTvrSnfZsUQ9aB
e3JiBddcgxUYkdp2DHwF6wemrpusctizTUzg6cBrYfiUcfPMCEmqodTzqF4nGQbb
/5X0YNv+IOiBdCX/xUIrJpt6Ka0Vk2UBgFYz2zRc56H+OQtk+w4AZLJqR6RX8MYS
CF6N18lJ5ETJ+CVSsk6FXlnxhhvpsJrVeVpyyuyuHgmHsGUDro2J1bwhtLwDMr7V
993q05MSEXmojWUBC5aqr4TlC2UxQgoFqsHnXDQkPI9gkf72Gq1rIoEBdJR6CfxV
YLiZmBIc84/ABa2nTmtG9dq2vOYak0IhCEAsUepWyf5T3QaXUu0u0MIC3sNpma+F
fhBnbBYE1ZzatCfPIaHFiy8S4S/i54U6QKT60pJm8l+qpBy8aqAIyMOV7QQtDol4
d6QSTRoq81Ui
=DmeF
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Thu Oct 25 15:00:11 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 25 Oct 2018 14:00:11 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 onionshare_1.3-1~bpo9+1_amd64.changes
Message-ID: <E1gFgBH-0002MR-EA@usper.debian.org>

onionshare_1.3-1~bpo9+1_amd64.changes uploaded successfully to localhost
along with the files:
  onionshare_1.3-1~bpo9+1.dsc
  onionshare_1.3-1~bpo9+1.debian.tar.xz
  onionshare_1.3-1~bpo9+1_all.deb
  onionshare_1.3-1~bpo9+1_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Thu Oct 25 15:58:43 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 25 Oct 2018 14:58:43 +0000
Subject: [Pkg-privacy-maintainers] onionshare_1.3-1~bpo9+1_amd64.changes is
 NEW
Message-ID: <E1gFh5v-000Atc-5E@fasolo.debian.org>

binary:onionshare is NEW.
binary:onionshare is NEW.
source:onionshare is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
     or https://ftp-master.debian.org/backports-new.html for *-backports


From u at 451f.org  Thu Oct 25 17:52:00 2018
From: u at 451f.org (u)
Date: Thu, 25 Oct 2018 16:52:00 +0000
Subject: [Pkg-privacy-maintainers] Packaging purple-lurch?
Message-ID: <12d97023-b4ad-1ddc-c8bf-64eeea603393@451f.org>

Hi!

I wondered.. is anybody interested in packaging purple-lurch which gives
Pidgin OMEMO support? See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905883

Cheers!
u.


From ftpmaster at ftp-master.debian.org  Thu Oct 25 19:13:04 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 25 Oct 2018 18:13:04 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 tails-installer_5.0.12+dfsg-1_amd64.changes
Message-ID: <E1gFk80-0000Ry-Qp@usper.debian.org>

tails-installer_5.0.12+dfsg-1_amd64.changes uploaded successfully to localhost
along with the files:
  tails-installer_5.0.12+dfsg-1.dsc
  tails-installer_5.0.12+dfsg-1.debian.tar.xz
  tails-installer_5.0.12+dfsg-1_amd64.buildinfo
  tails-installer_5.0.12+dfsg-1_amd64.deb
  tails-installer_5.0.12+dfsg.orig.tar.gz

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Thu Oct 25 19:18:05 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 25 Oct 2018 18:18:05 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbirdy_0.2.6-1~bpo9+1_amd64.changes
Message-ID: <E1gFkCr-0000lo-P1@usper.debian.org>

torbirdy_0.2.6-1~bpo9+1_amd64.changes uploaded successfully to localhost
along with the files:
  torbirdy_0.2.6-1~bpo9+1.dsc
  torbirdy_0.2.6-1~bpo9+1.debian.tar.xz
  torbirdy_0.2.6-1~bpo9+1_amd64.buildinfo
  xul-ext-torbirdy_0.2.6-1~bpo9+1_all.deb
  torbirdy_0.2.6.orig.tar.gz

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Thu Oct 25 20:43:53 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 25 Oct 2018 19:43:53 +0000
Subject: [Pkg-privacy-maintainers]
 tails-installer_5.0.12+dfsg-1_amd64.changes ACCEPTED into unstable
Message-ID: <E1gFlXt-00023e-8q@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Thu, 25 Oct 2018 20:01:18 CEST
Source: tails-installer
Binary: tails-installer
Architecture: source amd64
Version: 5.0.12+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Ulrike Uhlig <ulrike at debian.org>
Description:
 tails-installer - Installer for the Tails live operating system
Changes:
 tails-installer (5.0.12+dfsg-1) unstable; urgency=medium
 .
   * New upstream release:
     - Fix crash when reporting errors that contain non-ASCII chars.
     - Update translations.
Checksums-Sha256: 
 8e8da70add56f7ca0c046b9d54d3b79961b6bad7704c05320d8f63b90c821f90 2171 tails-installer_5.0.12+dfsg-1.dsc
 73eb008866beb18b72a7976e44ea3abe752fca1e0bf414086f5676c8a97e2f2b 15716 tails-installer_5.0.12+dfsg-1.debian.tar.xz
 0fafcad0641f012f1360cb27ded0d7e97113577849610c06520cf7af668faaa5 7350 tails-installer_5.0.12+dfsg-1_amd64.buildinfo
 d70380c4b49044f6f5978e3206a9609c69fd2ddb980f9382801b564c6dd3d16e 199422 tails-installer_5.0.12+dfsg-1_amd64.deb
 feb5293809be0c578fa550e9fb4926e5c1d0f53c9dc3230ad0e002de1089e9c7 330189 tails-installer_5.0.12+dfsg.orig.tar.gz
Checksums-Sha1: 
 da8d7c4598e0679593170dd1733752787dfb1284 2171 tails-installer_5.0.12+dfsg-1.dsc
 eb3f5b15cc667b61a22bfc0cf38c2818b340f21c 15716 tails-installer_5.0.12+dfsg-1.debian.tar.xz
 3188eab6088234feeb5f7cca120c3130c465efc5 7350 tails-installer_5.0.12+dfsg-1_amd64.buildinfo
 51e562e14ef327ca2d65fba69773c4443ab40317 199422 tails-installer_5.0.12+dfsg-1_amd64.deb
 272a1b617430cd47204e041ead800e81c5168e1c 330189 tails-installer_5.0.12+dfsg.orig.tar.gz
Files: 
 466fff33369eb8c6db1df445f5094062 2171 python optional tails-installer_5.0.12+dfsg-1.dsc
 e13864c69dd5017d54f83315a0734b14 15716 python optional tails-installer_5.0.12+dfsg-1.debian.tar.xz
 c3f6cdce1ff3ce7c796b97e5c03b1efe 7350 python optional tails-installer_5.0.12+dfsg-1_amd64.buildinfo
 fea95def55d34a7e44d294b61467b5e1 199422 python optional tails-installer_5.0.12+dfsg-1_amd64.deb
 d374d6e81b0263b77da9e888cc49f30e 330189 python optional tails-installer_5.0.12+dfsg.orig.tar.gz

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

iQJGBAEBCgAwFiEE7eP0RD800mGVFNeQsUuww42GHPEFAlvSBPQSHHVscmlrZUBk
ZWJpYW4ub3JnAAoJELFLsMONhhzxXcsQAIK7IErumRSZ9atfGPZRvDWMeirPSTiU
P8E9q8Y30AASHNrPU04nlyEn1GNYRufVnze3C7u8r4dXaHPr3xFICXO2fcCfM8hZ
rAuT3u+5LR498k76ttuWxhJKL14d/4hy6wnQJNnSJL7Qbccjetp4EsYvXIG294R7
KzgHfNDowkqkyqwNw2duNzU4uoWQzyqnLYO5kHVf66tS0UL2JCWDsLRpY4ah8w4G
LHxKOhQXul9eRSJxitoP5OwHgVkea49T8InO/7EMAwAJz36s0EYGkZHJx+lu5TzJ
wSuV+EATPWg6XrNgUs9ceXoGqWHHg2RHyjqDbQytnqHZJ0IdHXVhPQfLl1AvtwRR
aFUNAgfuKnkdN5qq0hynOV9fB9xQguJETpubxlkGoWeHJFiRzuJCK8UAXOlZhhIH
Q8s8TCokLETD4YR0bo0Qzyy2CK36I+bKFi6jUya5jIOubcRkaQdOo9dDln+ceevJ
okZ3ZzbzZaLaZI7Pquxbr3WExVMiHt+JV5nAFuxz+s/xckuesljJ+GSd2MKozBrG
9J1Yuq0y5/y75rJt9X5hR4jh3Kkb8yuihAmVZ0Wwo/ssV6UNTKPFFjvEyWaqV6uW
4WKLxGcEMnjxoLpvTh86AAPi8ZFJnMMv5f3d9+TClwFpNBl9JawWqByjmIWGz5x+
991GWrtPDXFW
=QoSx
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Thu Oct 25 20:45:11 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 25 Oct 2018 19:45:11 +0000
Subject: [Pkg-privacy-maintainers] torbirdy_0.2.6-1~bpo9+1_amd64.changes
 ACCEPTED into stretch-backports
Message-ID: <E1gFlZ9-0002MY-Uc@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Thu, 25 Oct 2018 20:08:26 CEST
Source: torbirdy
Binary: xul-ext-torbirdy
Architecture: source all
Version: 0.2.6-1~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Ulrike Uhlig <ulrike at debian.org>
Description:
 xul-ext-torbirdy - configures and enhances various Mozilla birds for anonymity use
Changes:
 torbirdy (0.2.6-1~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
Checksums-Sha256: 
 83ea6492c7c7fa25f8ba6811b311acab22414d91109b397a189ba43bde3d24f7 2049 torbirdy_0.2.6-1~bpo9+1.dsc
 1e081e673c5bbc7a517a297d7153db12d2ff08b945395df562ca7f88435d375b 13116 torbirdy_0.2.6-1~bpo9+1.debian.tar.xz
 65457819430f0dc725684cbaaa46fe75ed1789f25926b09bae76ab95c2c19f93 7224 torbirdy_0.2.6-1~bpo9+1_amd64.buildinfo
 e1a029f5023dde57df25bbbfad863ca90f9cb5e62c0195c569df932dc8207281 136158 xul-ext-torbirdy_0.2.6-1~bpo9+1_all.deb
 132a12cea105eaaee9e61b3b76b30e491498f9a894f4be1bd3720e41732e374b 160598 torbirdy_0.2.6.orig.tar.gz
Checksums-Sha1: 
 9f5ff5d0e586843ed3bf7c28d08bb749cc7285e0 2049 torbirdy_0.2.6-1~bpo9+1.dsc
 cc432aa274be900ce82bf6345ca833e75d3af350 13116 torbirdy_0.2.6-1~bpo9+1.debian.tar.xz
 52e3558066b9e053aae5ea6f47a88e1892fc8ba9 7224 torbirdy_0.2.6-1~bpo9+1_amd64.buildinfo
 575a46b869a71cd4c2c1961295606b49fe826daf 136158 xul-ext-torbirdy_0.2.6-1~bpo9+1_all.deb
 be3967ccb099acda9f181fc7ae1ceb06d4c7a757 160598 torbirdy_0.2.6.orig.tar.gz
Files: 
 00c062f3dd17b09ab43bdb848d5a3b7c 2049 web optional torbirdy_0.2.6-1~bpo9+1.dsc
 d03a608cd57062b1d7d1f8d18ba5c286 13116 web optional torbirdy_0.2.6-1~bpo9+1.debian.tar.xz
 d81be86d17c5ad1803f292e43228db34 7224 web optional torbirdy_0.2.6-1~bpo9+1_amd64.buildinfo
 1ba9d6e65873e6f8248e893a0fcbdbc4 136158 web optional xul-ext-torbirdy_0.2.6-1~bpo9+1_all.deb
 af73f29fd8dd41dfb7e771b8dc6ffe5b 160598 web optional torbirdy_0.2.6.orig.tar.gz

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

iQJGBAEBCgAwFiEE7eP0RD800mGVFNeQsUuww42GHPEFAlvSBqESHHVscmlrZUBk
ZWJpYW4ub3JnAAoJELFLsMONhhzxhFQQAL5MHixUTv3xyCZqw160j2cz1C8QCajR
nnkMgtZgCDC5bk5PqHoQhLmq5R8TnM+d8oPuCObvMoR9IV1wc/tscmCzNE9hhXRG
utTpRWy2EOTxWq/zQKMlwGfPZxZMAf8PN/EsZZqU5AAUmcOJjXOueCXlHqYAFPub
FY7d2uQlwMAi5U/3Dnsc/HsNA3glvwIfG7rB/e9cGMNncXOtCqoJF02tzOt/VQcZ
v+RMsoCtHfLhGGMn7OMQXyJ6TBef26P1wElTnkfZMOjpzMEDJ7UI0v2b/XwecMOe
vzrVLke0xBBwygNRs4TP9ybrHttoCx41xlnHANpI6yLZQ84MG4NMXWaJkRxOvWii
IaQuSfwaRSwnt3coRYg69CRCk1d8TXy4/dOW9ub4lK2lTb6Be+p5H3tmx8dk+hxV
TADOqwddH8Ob4ulpeXVElEKrsUdaA6621KOdgrmX++/Vr+TWrpDk1lc8P48z0TyV
sKVY8jiuX27/ednJM1K+f4cek0256u0Jpua3k8khCy1OMQMjwwZBzsl0KAZmdrWp
fd/m5YCXdoeo7BpzrTkGHBk0fl/6OcCXZHSxV7lal0v5LbO6+9tb/XZK/EYdX96t
qdfNWfhdc+/lCLrhuR/+HtocK2W2s84w5zwknQgcw4159IwgpVXehaUH5RlW5FuH
9HAU6eEFmD+g
=MyRU
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From sunil at medhas.org  Fri Oct 26 02:20:11 2018
From: sunil at medhas.org (Sunil Mohan Adapa)
Date: Thu, 25 Oct 2018 18:20:11 -0700
Subject: [Pkg-privacy-maintainers] Bug#911907: monkeysphere: Install fails
 on systems with PAM login restrictions
Message-ID: <154051681157.30961.468825320149255298.reportbug@towel.localdomain>

Package: monkeysphere
Version: 0.42-2
Severity: normal
Tags: patch upstream

Dear Maintainer,

When I install monkeysphere on a FreedomBox, I get the following error:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Suggested packages:
  monkeysphere-validation-agent
The following NEW packages will be installed:
  monkeysphere
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/78.0 kB of archives.
After this operation, 280 kB of additional disk space will be used.
Selecting previously unselected package monkeysphere.
(Reading database ... 205917 files and directories currently installed.)
Preparing to unpack .../monkeysphere_0.42-2_all.deb ...
Unpacking monkeysphere (0.42-2) ...
Setting up monkeysphere (0.42-2) ...
ms: setting up Monkeysphere authentication trust core...
su: Permission denied
Failed running transition script /usr/share/monkeysphere/transitions/0.23
dpkg: error processing package monkeysphere (--configure):
 installed monkeysphere package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.8.4-2+b1) ...
Errors were encountered while processing:
 monkeysphere
E: Sub-process /usr/bin/dpkg returned an error code (1)

Further, publishing of keys fails as follows:

root at mybox:/vagrant# monkeysphere-host publish D7D055DF04C101AC1885FC0BA31A54C879664ED1
Really publish key 'D7D055DF04C101AC1885FC0BA31A54C879664ED1' to pool.sks-keyservers.net? (Y/n) 
su: Permission denied

This is due to following setting in /etc/security/access.conf which prohibits non-root users from logging into the system.

-:ALL EXCEPT root fbx plinth (admin) (sudo):ALL

We faced a similar issue with quassel-core package recently and the maintainer fixed it by using runuser instead of su. From what I gather from man pages, it should do the job here as expected. A patch is attached. runuser is part of util-linux and is an essential package on Debian. While all the tests pass, I am unable to ascertain the full impact of the change.


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8), LANGUAGE=en_IN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages monkeysphere depends on:
ii  adduser                    3.118
ii  gnupg                      2.2.10-3
ii  libcrypt-openssl-rsa-perl  0.31-1
ii  lockfile-progs             0.1.18
ii  perl [libdigest-sha-perl]  5.26.2-7+b1

Versions of packages monkeysphere recommends:
pn  agent-transfer           <none>
ii  cron [cron-daemon]       3.0pl1-130
ii  netcat-openbsd [netcat]  1.190-2
ii  openssh-client           1:7.8p1-1
ii  socat                    1.7.3.2-2
pn  ssh-askpass              <none>

Versions of packages monkeysphere suggests:
ii  msva-perl [monkeysphere-validation-agent]  0.9.2-1

-- no debconf information
-------------- next part --------------
>From 93b8d954d489e9b7096b91f82baf64d1bfd0273b Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa <sunil at medhas.org>
Date: Thu, 25 Oct 2018 14:43:57 -0700
Subject: [PATCH] Use runuser instead of su

On systems with restricted PAM security, it may not possible to use su.
---
 src/monkeysphere-authentication |  2 +-
 src/monkeysphere-host           |  2 +-
 src/share/common                | 14 ++------------
 3 files changed, 4 insertions(+), 14 deletions(-)

diff --git a/src/monkeysphere-authentication b/src/monkeysphere-authentication
index b3eb1e6..3223294 100755
--- a/src/monkeysphere-authentication
+++ b/src/monkeysphere-authentication
@@ -137,7 +137,7 @@ GNUPGHOME_SPHERE=${MONKEYSPHERE_GNUPGHOME_SPHERE:="${MADATADIR}/sphere"}
 CORE_KEYLENGTH=${MONKEYSPHERE_CORE_KEYLENGTH:="2048"}
 LOG_PREFIX=${MONKEYSPHERE_LOG_PREFIX:='ms: '}
 
-# export variables needed in su invocation
+# export variables needed for invoking command under monkeysphere user
 export DATE
 export LOG_LEVEL
 export KEYSERVER
diff --git a/src/monkeysphere-host b/src/monkeysphere-host
index 75895e9..089c2b6 100755
--- a/src/monkeysphere-host
+++ b/src/monkeysphere-host
@@ -360,7 +360,7 @@ PROMPT=${MONKEYSPHERE_PROMPT:=$PROMPT}
 GNUPGHOME_HOST=${MONKEYSPHERE_GNUPGHOME_HOST:="${MHDATADIR}"}
 LOG_PREFIX=${MONKEYSPHERE_LOG_PREFIX:='ms: '}
 
-# export variables needed in su invocation
+# export variables needed for invoking command under monkeysphere user
 export DATE
 export LOG_LEVEL
 export KEYSERVER
diff --git a/src/share/common b/src/share/common
index 80ae88a..22c4d3e 100644
--- a/src/share/common
+++ b/src/share/common
@@ -98,26 +98,16 @@ su_monkeysphere_user() {
     # monkeysphere user, but without prompting for any sort of
     # authentication.  If this is not possible, we should just fail.
 
-    # FIXME: our current implementation is overly restrictive, because
-    # there may be some su PAM configurations that would allow su
-    # "$MONKEYSPHERE_USER" -c "$@" to Just Work without prompting,
-    # allowing specific users to invoke commands which make use of
-    # this user.
-
-    # chpst (from runit) would be nice to use, but we don't want to
-    # introduce an extra dependency just for this.  This may be a
-    # candidate for re-factoring if we switch implementation languages.
-
     case $(id -un) in
 	# if monkeysphere user, run the command as a subshell
 	"$MONKEYSPHERE_USER")
 	    ( "$@" )
 	    ;;
 
-         # if root, su command as monkeysphere user
+         # if root, run command as monkeysphere user
 	'root')
             # requote arguments using bash builtin feature (see "help printf"):
-	    su "$MONKEYSPHERE_USER" -s "$(which bash)" -c "$(printf "%q " "$@")"
+	    runuser -u "$MONKEYSPHERE_USER" -- "$@"
 	    ;;
 
 	# otherwise, fail
-- 
2.19.1


From noreply at release.debian.org  Fri Oct 26 05:39:11 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Fri, 26 Oct 2018 04:39:11 +0000
Subject: [Pkg-privacy-maintainers] mat2 0.5.0-1 MIGRATED to testing
Message-ID: <E1gFttv-0007TY-TG@respighi.debian.org>

FYI: The status of the mat2 source package
in Debian's testing distribution has changed.

  Previous version: 0.4.0-2
  Current version:  0.5.0-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From intrigeri at debian.org  Fri Oct 26 09:15:49 2018
From: intrigeri at debian.org (intrigeri)
Date: Fri, 26 Oct 2018 10:15:49 +0200
Subject: [Pkg-privacy-maintainers] Packaging purple-lurch?
In-Reply-To: <12d97023-b4ad-1ddc-c8bf-64eeea603393@451f.org>
References: <12d97023-b4ad-1ddc-c8bf-64eeea603393@451f.org>
Message-ID: <87h8h986oa.fsf@boum.org>

u:
> I wondered.. is anybody interested in packaging purple-lurch which gives
> Pidgin OMEMO support? See:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905883

FWIW, personally I'm not: I'm headed towards migrating away from
Pidgin for this sort of things more than towards adding new Pidgin
stuff to the archive.

Cheers!
-- 
intrigeri


From u at 451f.org  Fri Oct 26 09:30:00 2018
From: u at 451f.org (u)
Date: Fri, 26 Oct 2018 08:30:00 +0000
Subject: [Pkg-privacy-maintainers] Packaging purple-lurch?
In-Reply-To: <87h8h986oa.fsf@boum.org>
References: <12d97023-b4ad-1ddc-c8bf-64eeea603393@451f.org>
 <87h8h986oa.fsf@boum.org>
Message-ID: <016e3fcf-fc30-0d8f-ea32-3ed7f5378596@451f.org>

Hi!

intrigeri:
> u:
>> I wondered.. is anybody interested in packaging purple-lurch which gives
>> Pidgin OMEMO support? See:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905883
> 
> FWIW, personally I'm not: I'm headed towards migrating away from
> Pidgin for this sort of things more than towards adding new Pidgin
> stuff to the archive.

Indeed, I also ended up using a different client :)

Cheers!
u.


From jonas at freesources.org  Fri Oct 26 09:33:57 2018
From: jonas at freesources.org (Jonas Meurer)
Date: Fri, 26 Oct 2018 10:33:57 +0200
Subject: [Pkg-privacy-maintainers] Packaging purple-lurch?
In-Reply-To: <87h8h986oa.fsf@boum.org>
References: <12d97023-b4ad-1ddc-c8bf-64eeea603393@451f.org>
 <87h8h986oa.fsf@boum.org>
Message-ID: <8a7dd457-667d-16e0-51be-59639c1e2628@freesources.org>

Hello,

Am 26.10.18 um 10:15 schrieb intrigeri:
> u:
>> I wondered.. is anybody interested in packaging purple-lurch which gives
>> Pidgin OMEMO support? See:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905883
> 
> FWIW, personally I'm not: I'm headed towards migrating away from
> Pidgin for this sort of things more than towards adding new Pidgin
> stuff to the archive.

I have a different (probably more pragmatic) view on this. Pidgin is
old, crappy and probably poorly maintained code. So in theory I agree
with you: I would love to advice people to switch to a more modern and
clean XMPP client. But unfortunately, to my knowledge, no other
(graphical) XMPP client exists, that allows to use both OTR and OMEMO at
the same time. If anybody can recommend such a graphical XMPP client
with support for both, I'd be happy to learn about it :)

Since there's still a lot of usability issues with OMEMO, switching
entirely to OMEMO for e2e encryption is not an option either.

That's why I consider it important to keep support for Pidgin for now.
Adding OMEMO support to it in Debian would be a benefit in my eyes and
help people who actually rely on e2e encrypted XMPP communication.

Unfortunately I don't have much capacities. But I'll see whether I find
some time do help with the packaging. If anybody else would be
interested in taking the lead - even better. Count me in as
co-maintainer at least.

Cheers
 jonas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181026/37c29ff5/attachment.sig>

From dkg at fifthhorseman.net  Fri Oct 26 13:41:39 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Fri, 26 Oct 2018 08:41:39 -0400
Subject: [Pkg-privacy-maintainers] Bug#911907: Bug#911907: monkeysphere:
 Install fails on systems with PAM login restrictions
In-Reply-To: <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
References: <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
Message-ID: <87d0rwnam4.fsf@fifthhorseman.net>

Control: tags 911907 + confirmed

Hi Sunil--

thanks for catching this, and for proposing a fix.

On Thu 2018-10-25 18:20:11 -0700, Sunil Mohan Adapa wrote:
> We faced a similar issue with quassel-core package recently and the
> maintainer fixed it by using runuser instead of su. From what I gather
> from man pages, it should do the job here as expected. A patch is
> attached. runuser is part of util-linux and is an essential package on
> Debian.

Thanks!  I agree that we should be moving from su to runuser here.  Good
call!

>              # requote arguments using bash builtin feature (see "help printf"):
> -	    su "$MONKEYSPHERE_USER" -s "$(which bash)" -c "$(printf "%q " "$@")"
> +	    runuser -u "$MONKEYSPHERE_USER" -- "$@"
>             ;;

This makes several different changes besides just moving to runuser.  in
particular, it drops the -s "$(which bash)" (and therefore i think
relies on the monkeysphere user's chosen shell in /etc/passwd --
hopefully that's correct, but it might have changed somehow).  Would you
be ok with reinstating the -s "$(which bash)" arguments?


And, it changes how the invocation is passed through -- rather than
using -c (which can pass shell-specific data) it passes the arguments
directly to runuser.  This is fine for most cases, but it might fail if
invoked as something like:

   su_monkeysphere_user echo test '>' /tmp/foo

this could do two different things:

 a) echo "test", the literal ">" symbol,  and the string "/tmp/foo"
 b) echo "test" into the file "/tmp/foo" as the monkeysphere user.

The current code seems to assume that the you might want to pass shell
metacharacters through to be executed that way, and that (b) should be
the correct result.  I think it's a bad idea to do that, though, and i
prefer your simpler formulation.

I'm concerned about the complex constructions (sigh, shell is such a
mess) passed to su_monkeysphere_user in update_users and add_certifier
(for monkeysphere-authentication), and add_revoker (for
monkeysphere-host), though.  Have you tested those subcommands on a live
system as the superuser?

If we can go with your proposed simpler argument passing, we definitely
should!

> While all the tests pass, I am unable to ascertain the full impact of
> the change.

hm, the test suite is designed to run as a non-priv user, so you're
right that the test suite passing doesn't give us enough information at
this point.

     --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181026/04988090/attachment.sig>

From owner at bugs.debian.org  Fri Oct 26 13:45:06 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Fri, 26 Oct 2018 12:45:06 +0000
Subject: [Pkg-privacy-maintainers] Processed: Re: Bug#911907: monkeysphere:
 Install fails on systems with PAM login restrictions
References: <87d0rwnam4.fsf@fifthhorseman.net>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
Message-ID: <handler.s.B911907.154055771116956.transcript@bugs.debian.org>

Processing control commands:

> tags 911907 + confirmed
Bug #911907 [monkeysphere] monkeysphere: Install fails on systems with PAM login restrictions
Added tag(s) confirmed.

-- 
911907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911907
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From jtaylor.debian at googlemail.com  Fri Oct 26 21:51:57 2018
From: jtaylor.debian at googlemail.com (Julian Taylor)
Date: Fri, 26 Oct 2018 22:51:57 +0200
Subject: [Pkg-privacy-maintainers] Bug#911988: reintroduce fixed python2
 package for rdepends
Message-ID: <a973a99e-6a09-4e92-417d-716992e5fd00@googlemail.com>

Package: txtorcon
Version:  18.0.2-2
Severity: important

The removal of the python2 package in #905253 due to a packaging bug
made its reverse dependencies RC buggy.
As upstream still supports python2 [0], it is tested in the package
build and its rdepends and buster will still ship with python2 please
reintroduce the python2 package.

Attached a debdiff that fixes the installation of the python3 only file
in the python2 package.


[0] https://github.com/meejah/txtorcon
-------------- next part --------------
diff --git a/debian/changelog b/debian/changelog
index f266461..b644918 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+txtorcon (18.0.2-3) unstable; urgency=medium
+
+  * reintroduce fixed Python 2 package needed by reverse dependencies
+    Closes: #911271
+
+ -- Julian Taylor <jtaylor.debian at googlemail.com>  Fri, 26 Oct 2018 22:30:43 +0200
+
 txtorcon (18.0.2-2) unstable; urgency=medium
 
   * No longer builds a Python 2 package (Closes: #905253)
diff --git a/debian/control b/debian/control
index 0eac5fa..a20741c 100644
--- a/debian/control
+++ b/debian/control
@@ -8,6 +8,14 @@ Build-Depends: debhelper (>= 9),
                dh-python,
                graphviz,
                lsof,
+               python-all,
+               python-geoip,
+               python-ipaddress,
+               python-mock,
+               python-repoze.sphinx.autointerface,
+               python-setuptools,
+               python-sphinx,
+               python-twisted,
                python3-all,
                python3-geoip,
                python3-mock,
@@ -21,6 +29,29 @@ Vcs-Browser: https://salsa.debian.org/pkg-privacy-team/txtorcon
 Vcs-Git: https://salsa.debian.org/pkg-privacy-team/txtorcon.git
 Homepage: https://github.com/meejah/txtorcon
 
+Package: python-txtorcon
+Architecture: all
+Depends: python-geoip,
+         python-ipaddress,
+         python-twisted,
+         python-zope.interface,
+         ${misc:Depends},
+         ${python:Depends}
+Suggests: tor
+Provides: ${python:Provides}
+Description: Twisted-based asynchronous Tor control protocol implementation (Python 2)
+ txtorcon main feature is to present an asynchronous API to speak the Tor
+ client protocol in Python. It also provides abstractions to track and get
+ updates about Tor's state and current configuration (including writing it to
+ Tor or disk), along with helpers to asynchronously launch slave instances of
+ Tor including Twisted endpoint support.
+ .
+ Twisted is an event-driven networking engine written in Python and Tor is an
+ onion-routing network designed to improve people's privacy and anonymity on the
+ Internet.
+ .
+ This package contains the Python 2 module.
+
 Package: python3-txtorcon
 Architecture: all
 Depends: python3-geoip,
diff --git a/debian/rules b/debian/rules
index a334f92..aa0b193 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,7 +3,7 @@
 export PYBUILD_NAME=txtorcon
 
 %:
-	dh $@ --with=python3,sphinxdoc --buildsystem=pybuild
+	dh $@ --with=python2,python3,sphinxdoc --buildsystem=pybuild
 
 override_dh_auto_build:
 	PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ docs/_build/html # HTML generator
@@ -11,17 +11,28 @@ override_dh_auto_build:
 
 override_dh_auto_install:
 	dh_auto_install -O--buildsystem=pybuild
+	# don't install py3 files in py2 as they don't compile during installation
+	find debian/python-txtorcon/ -name controller_py3.py -delete
+	mkdir -p debian/python-txtorcon/usr/share/doc/python-txtorcon
 	mkdir -p debian/python3-txtorcon/usr/share/doc/python3-txtorcon
 	set -e && \
+	for data_src in README.rst TODO examples; do \
+		mv debian/python-txtorcon/usr/share/txtorcon/$$data_src \
+			debian/python-txtorcon/usr/share/doc/python-txtorcon; \
+	done
+	set -e && \
 	for data_src in README.rst TODO examples; do \
 		mv debian/python3-txtorcon/usr/share/txtorcon/$$data_src \
 			debian/python3-txtorcon/usr/share/doc/python3-txtorcon; \
 	done
+	chmod 644 debian/python-txtorcon/usr/share/doc/python-txtorcon/examples/*.py
 	chmod 644 debian/python3-txtorcon/usr/share/doc/python3-txtorcon/examples/*.py
+	rm -r debian/python-txtorcon/usr/share/txtorcon
 	rm -r debian/python3-txtorcon/usr/share/txtorcon
 
 override_dh_compress:
 	dh_compress -Xlaunch_tor_with_simplehttpd.py -O--buildsystem=pybuild
 
 override_dh_auto_test:
+	PYTHONPATH=. trial --reporter=text test
 	PYTHONPATH=. trial3 --reporter=text test

From jtaylor.debian at googlemail.com  Fri Oct 26 22:17:27 2018
From: jtaylor.debian at googlemail.com (Julian Taylor)
Date: Fri, 26 Oct 2018 23:17:27 +0200
Subject: [Pkg-privacy-maintainers] Bug#911988: reintroduce fixed python2
 package for rdepends
In-Reply-To: <handler.911988.B.154058712315377.ack@bugs.debian.org>
References: <a973a99e-6a09-4e92-417d-716992e5fd00@googlemail.com>
 <handler.911988.B.154058712315377.ack@bugs.debian.org>
 <a973a99e-6a09-4e92-417d-716992e5fd00@googlemail.com>
Message-ID: <8aa100df-ef23-d969-daa9-a2f4ea216947@googlemail.com>

tags 911988 + patch
thanks

Ops I forgot to adapt a runtime check, attached a fixed debdiff
-------------- next part --------------
diff --git a/debian/changelog b/debian/changelog
index f266461..a94e1bb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+txtorcon (18.0.2-3) unstable; urgency=medium
+
+  * reintroduce fixed Python 2 package needed by reverse dependencies
+    do not install python3 files to avoid failure during installation
+    add fix-controller-py3check.patch to correct the python3 runtime check
+    Closes: #911271
+
+ -- Julian Taylor <jtaylor.debian at googlemail.com>  Fri, 26 Oct 2018 22:30:43 +0200
+
 txtorcon (18.0.2-2) unstable; urgency=medium
 
   * No longer builds a Python 2 package (Closes: #905253)
diff --git a/debian/control b/debian/control
index 0eac5fa..a20741c 100644
--- a/debian/control
+++ b/debian/control
@@ -8,6 +8,14 @@ Build-Depends: debhelper (>= 9),
                dh-python,
                graphviz,
                lsof,
+               python-all,
+               python-geoip,
+               python-ipaddress,
+               python-mock,
+               python-repoze.sphinx.autointerface,
+               python-setuptools,
+               python-sphinx,
+               python-twisted,
                python3-all,
                python3-geoip,
                python3-mock,
@@ -21,6 +29,29 @@ Vcs-Browser: https://salsa.debian.org/pkg-privacy-team/txtorcon
 Vcs-Git: https://salsa.debian.org/pkg-privacy-team/txtorcon.git
 Homepage: https://github.com/meejah/txtorcon
 
+Package: python-txtorcon
+Architecture: all
+Depends: python-geoip,
+         python-ipaddress,
+         python-twisted,
+         python-zope.interface,
+         ${misc:Depends},
+         ${python:Depends}
+Suggests: tor
+Provides: ${python:Provides}
+Description: Twisted-based asynchronous Tor control protocol implementation (Python 2)
+ txtorcon main feature is to present an asynchronous API to speak the Tor
+ client protocol in Python. It also provides abstractions to track and get
+ updates about Tor's state and current configuration (including writing it to
+ Tor or disk), along with helpers to asynchronously launch slave instances of
+ Tor including Twisted endpoint support.
+ .
+ Twisted is an event-driven networking engine written in Python and Tor is an
+ onion-routing network designed to improve people's privacy and anonymity on the
+ Internet.
+ .
+ This package contains the Python 2 module.
+
 Package: python3-txtorcon
 Architecture: all
 Depends: python3-geoip,
diff --git a/debian/patches/fix-controller-py3check.patch b/debian/patches/fix-controller-py3check.patch
new file mode 100644
index 0000000..3e38df3
--- /dev/null
+++ b/debian/patches/fix-controller-py3check.patch
@@ -0,0 +1,20 @@
+Description: adapt python3 check for missing file
+Author: Julian Taylor <jtaylor.debian at googlemail.com>
+
+The file is not installed in python2 to avoid pycompile trying to compile it
+with python2.
+For this the runtime check needs to be adapted.
+
+Index: txtorcon/txtorcon/controller.py
+===================================================================
+--- txtorcon.orig/txtorcon/controller.py
++++ txtorcon/txtorcon/controller.py
+@@ -42,7 +42,7 @@ from .interface import ITor
+ try:
+     from .controller_py3 import _AsyncOnionAuthContext
+     HAVE_ASYNC = True
+-except SyntaxError:
++except Exception:
+     HAVE_ASYNC = False
+ 
+ if sys.platform in ('linux', 'linux2', 'darwin'):
diff --git a/debian/patches/series b/debian/patches/series
index ed80250..6bfd16d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
+fix-controller-py3check.patch
 disable_test_for_invalid_geoip.patch
 remove-privacy-infringing-buttons.patch
 remove-privacy-infringing-JS.patch
diff --git a/debian/rules b/debian/rules
index a334f92..aa0b193 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,7 +3,7 @@
 export PYBUILD_NAME=txtorcon
 
 %:
-	dh $@ --with=python3,sphinxdoc --buildsystem=pybuild
+	dh $@ --with=python2,python3,sphinxdoc --buildsystem=pybuild
 
 override_dh_auto_build:
 	PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ docs/_build/html # HTML generator
@@ -11,17 +11,28 @@ override_dh_auto_build:
 
 override_dh_auto_install:
 	dh_auto_install -O--buildsystem=pybuild
+	# don't install py3 files in py2 as they don't compile during installation
+	find debian/python-txtorcon/ -name controller_py3.py -delete
+	mkdir -p debian/python-txtorcon/usr/share/doc/python-txtorcon
 	mkdir -p debian/python3-txtorcon/usr/share/doc/python3-txtorcon
 	set -e && \
+	for data_src in README.rst TODO examples; do \
+		mv debian/python-txtorcon/usr/share/txtorcon/$$data_src \
+			debian/python-txtorcon/usr/share/doc/python-txtorcon; \
+	done
+	set -e && \
 	for data_src in README.rst TODO examples; do \
 		mv debian/python3-txtorcon/usr/share/txtorcon/$$data_src \
 			debian/python3-txtorcon/usr/share/doc/python3-txtorcon; \
 	done
+	chmod 644 debian/python-txtorcon/usr/share/doc/python-txtorcon/examples/*.py
 	chmod 644 debian/python3-txtorcon/usr/share/doc/python3-txtorcon/examples/*.py
+	rm -r debian/python-txtorcon/usr/share/txtorcon
 	rm -r debian/python3-txtorcon/usr/share/txtorcon
 
 override_dh_compress:
 	dh_compress -Xlaunch_tor_with_simplehttpd.py -O--buildsystem=pybuild
 
 override_dh_auto_test:
+	PYTHONPATH=. trial --reporter=text test
 	PYTHONPATH=. trial3 --reporter=text test

From owner at bugs.debian.org  Fri Oct 26 22:21:07 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Fri, 26 Oct 2018 21:21:07 +0000
Subject: [Pkg-privacy-maintainers] Processed: reintroduce fixed python2
 package for rdepends
References: <8aa100df-ef23-d969-daa9-a2f4ea216947@googlemail.com>
Message-ID: <handler.s.C.154058865427050.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tags 911988 + patch
Bug #911988 [txtorcon] reintroduce fixed python2 package for rdepends
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
911988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911988
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ametzler at bebt.de  Sat Oct 27 08:06:05 2018
From: ametzler at bebt.de (Andreas Metzler)
Date: Sat, 27 Oct 2018 09:06:05 +0200
Subject: [Pkg-privacy-maintainers] Bug#864093: libotr: diff for NMU version
 4.1.1-2.1
References: <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
Message-ID: <20181027070605.GA26137@argenau.bebt.de>

Control: tags 864093 + patch
Control: tags 864093 + pending


Dear maintainer,

I've prepared an NMU for libotr (versioned as 4.1.1-2.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.

kind regards
Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libotr-4.1.1-2.1-nmu.diff
Type: text/x-diff
Size: 1123 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181027/1aef49d4/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181027/1aef49d4/attachment.sig>

From owner at bugs.debian.org  Sat Oct 27 08:09:04 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 27 Oct 2018 07:09:04 +0000
Subject: [Pkg-privacy-maintainers] Processed: libotr: diff for NMU version
 4.1.1-2.1
References: <20181027070605.GA26137@argenau.bebt.de>
 <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
Message-ID: <handler.s.B864093.154062396922526.transcript@bugs.debian.org>

Processing control commands:

> tags 864093 + patch
Bug #864093 [src:libotr] libotr: Please stop (Build-)Depending on libgcrypt11-dev transition package
Added tag(s) patch.
> tags 864093 + pending
Bug #864093 [src:libotr] libotr: Please stop (Build-)Depending on libgcrypt11-dev transition package
Added tag(s) pending.

-- 
864093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864093
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ftpmaster at ftp-master.debian.org  Sat Oct 27 08:19:01 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 27 Oct 2018 07:19:01 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 libotr_4.1.1-2.1_multi.changes
Message-ID: <E1gGIs9-0006a7-I0@usper.debian.org>

libotr_4.1.1-2.1_multi.changes uploaded successfully to localhost
along with the files:
  libotr_4.1.1-2.1.dsc
  libotr_4.1.1-2.1.debian.tar.xz

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ametzler at bebt.de  Sat Oct 27 12:19:42 2018
From: ametzler at bebt.de (Andreas Metzler)
Date: Sat, 27 Oct 2018 13:19:42 +0200
Subject: [Pkg-privacy-maintainers] Bug#864093: libotr: diff for NMU version
 4.1.1-2.1
In-Reply-To: <20181027070605.GA26137@argenau.bebt.de>
References: <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
 <20181027070605.GA26137@argenau.bebt.de>
 <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
Message-ID: <20181027111942.GD1425@argenau.bebt.de>

On 2018-10-27 Andreas Metzler <ametzler at bebt.de> wrote:
> Dear maintainer,

> I've prepared an NMU for libotr (versioned as 4.1.1-2.1) and
> uploaded it to DELAYED/15.
[...]

Hello,

Corrected NMUdiff (also fixing dependency) attached.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libotr-4.1.1-2.1-nmu.diff
Type: text/x-diff
Size: 1362 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181027/896eedc0/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181027/896eedc0/attachment.sig>

From ftpmaster at ftp-master.debian.org  Sat Oct 27 12:35:57 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 27 Oct 2018 11:35:57 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 libotr_4.1.1-2.1_multi.changes
Message-ID: <E1gGMsn-0002ls-I6@usper.debian.org>

libotr_4.1.1-2.1_multi.changes uploaded successfully to localhost
along with the files:
  libotr_4.1.1-2.1.dsc
  libotr_4.1.1-2.1.debian.tar.xz

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From anarcat at debian.org  Sat Oct 27 13:45:00 2018
From: anarcat at debian.org (Antoine =?UTF-8?Q?Beaupr=C3=A9?=)
Date: Sat, 27 Oct 2018 08:45:00 -0400
Subject: [Pkg-privacy-maintainers] Bug#864093: Bug#864093: libotr: diff for
 NMU version 4.1.1-2.1
In-Reply-To: <20181027070605.GA26137@argenau.bebt.de>
References: <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
 <20181027070605.GA26137@argenau.bebt.de>
 <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
Message-ID: <877ei3eeyb.fsf@curie.anarc.at>

Patch looks good to me.

I've merged the patch in the tree, and will upload a new version. Do you
mind canceling yours?

A.

On 2018-10-27 09:06:05, Andreas Metzler wrote:
> Control: tags 864093 + patch
> Control: tags 864093 + pending
>
>
> Dear maintainer,
>
> I've prepared an NMU for libotr (versioned as 4.1.1-2.1) and
> uploaded it to DELAYED/15. Please feel free to tell me if I
> should delay it longer.
>
> kind regards
> Andreas
>
> -- 
> `What a good friend you are to him, Dr. Maturin. His other friends are
> so grateful to you.'
> `I sew his ears on from time to time, sure'
> diff -Nru libotr-4.1.1/debian/changelog libotr-4.1.1/debian/changelog
> --- libotr-4.1.1/debian/changelog	2016-08-14 11:17:06.000000000 +0200
> +++ libotr-4.1.1/debian/changelog	2018-10-27 09:01:03.000000000 +0200
> @@ -1,3 +1,11 @@
> +libotr (4.1.1-2.1) unstable; urgency=low
> +
> +  * Non-maintainer upload.
> +  * B-d on libgcrypt20-dev instead of (dummy transition package)
> +    libgcrypt11-dev. Closes: #864093
> +
> + -- Andreas Metzler <ametzler at debian.org>  Sat, 27 Oct 2018 09:01:03 +0200
> +
>  libotr (4.1.1-2) unstable; urgency=medium
>  
>    * New Debian-specific patch: suggest pidgin-otr to Debian and Ubuntu users
> diff -Nru libotr-4.1.1/debian/control libotr-4.1.1/debian/control
> --- libotr-4.1.1/debian/control	2016-08-14 11:17:06.000000000 +0200
> +++ libotr-4.1.1/debian/control	2018-10-27 09:01:03.000000000 +0200
> @@ -7,7 +7,7 @@
>  Build-Depends: debhelper (>= 9),
>                 dh-autoreconf,
>                 libgpg-error-dev,
> -               libgcrypt11-dev,
> +               libgcrypt20-dev,
>                 autotools-dev
>  Standards-Version: 3.9.8
>  Vcs-Browser: https://anonscm.debian.org/cgit/pkg-privacy/packages/libotr.git
> _______________________________________________
> Pkg-privacy-maintainers mailing list
> Pkg-privacy-maintainers at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-privacy-maintainers

-- 
Les plus beaux chants sont les chants de revendications
Le vers doit faire l'amour dans la tête des populations.
À l'école de la poésie, on n'apprend pas: on se bat!
                        - Léo Ferré, "Préface"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181027/d4803d2d/attachment.sig>

From ametzler at bebt.de  Sat Oct 27 13:55:59 2018
From: ametzler at bebt.de (Andreas Metzler)
Date: Sat, 27 Oct 2018 14:55:59 +0200
Subject: [Pkg-privacy-maintainers] Bug#864093: Bug#864093: libotr: diff for
 NMU version 4.1.1-2.1
In-Reply-To: <877ei3eeyb.fsf@curie.anarc.at>
References: <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
 <20181027070605.GA26137@argenau.bebt.de> <877ei3eeyb.fsf@curie.anarc.at>
 <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
Message-ID: <20181027125559.GK1425@argenau.bebt.de>

On 2018-10-27 Antoine Beaupré <anarcat at debian.org> wrote:
> Patch looks good to me.

> I've merged the patch in the tree, and will upload a new version.

Hello,

Did you grab the second version, which also fixes libotr5-dev
dependency and not only the b-d?

> Do you mind canceling yours?

I have just uploaded the dcut file.

Thanks for taking care of the bug!

cu Andreas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181027/b0e77046/attachment.sig>

From anarcat at debian.org  Sat Oct 27 14:07:57 2018
From: anarcat at debian.org (Antoine =?UTF-8?Q?Beaupr=C3=A9?=)
Date: Sat, 27 Oct 2018 09:07:57 -0400
Subject: [Pkg-privacy-maintainers] Bug#864093: Bug#864093: Bug#864093:
 libotr: diff for NMU version 4.1.1-2.1
In-Reply-To: <20181027125559.GK1425@argenau.bebt.de>
References: <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
 <20181027070605.GA26137@argenau.bebt.de> <877ei3eeyb.fsf@curie.anarc.at>
 <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
 <20181027125559.GK1425@argenau.bebt.de>
 <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
Message-ID: <874ld7edw2.fsf@curie.anarc.at>

On 2018-10-27 14:55:59, Andreas Metzler wrote:
> On 2018-10-27 Antoine Beaupré <anarcat at debian.org> wrote:
>> Patch looks good to me.
>
>> I've merged the patch in the tree, and will upload a new version.
>
> Hello,
>
> Did you grab the second version, which also fixes libotr5-dev
> dependency and not only the b-d?

Oups! I had not. But fixed. :) Thanks for the heads up!

>> Do you mind canceling yours?
>
> I have just uploaded the dcut file.
>
> Thanks for taking care of the bug!

Well thank you for the patch! :)

A.
-- 
C'est avec les pierres de la loi qu'on a bâti les prisons,
et avec les briques de la religion, les bordels.
                        - William Blake


From reproducible-builds at lists.alioth.debian.org  Sat Oct 27 01:54:13 2018
From: reproducible-builds at lists.alioth.debian.org (Reproducible builds folks)
Date: Sat, 27 Oct 2018 00:54:13 +0000 (UTC)
Subject: [Pkg-privacy-maintainers] pyptlib: status change on
 tests.reproducible-builds.org/debian
Message-ID: <20181027005413.E445C1F35C@jenkins.debian.net>

2018-10-26 06:48 https://tests.reproducible-builds.org/debian/unstable/amd64/pyptlib changed from FTBFS -> reproducible


From ftpmaster at ftp-master.debian.org  Sat Oct 27 16:03:53 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 27 Oct 2018 15:03:53 +0000
Subject: [Pkg-privacy-maintainers] Processing of libotr_4.1.1-3_amd64.changes
Message-ID: <E1gGQ81-0007PR-7m@usper.debian.org>

libotr_4.1.1-3_amd64.changes uploaded successfully to localhost
along with the files:
  libotr_4.1.1-3.dsc
  libotr_4.1.1-3.debian.tar.xz
  libotr5-bin-dbgsym_4.1.1-3_amd64.deb
  libotr5-bin_4.1.1-3_amd64.deb
  libotr5-dbgsym_4.1.1-3_amd64.deb
  libotr5-dev_4.1.1-3_amd64.deb
  libotr5_4.1.1-3_amd64.deb
  libotr_4.1.1-3_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sat Oct 27 18:36:47 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 27 Oct 2018 17:36:47 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.3.1-1~exp1_source.changes
Message-ID: <E1gGSVz-0007UU-MS@usper.debian.org>

torbrowser-launcher_0.3.1-1~exp1_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.3.1-1~exp1.dsc
  torbrowser-launcher_0.3.1.orig.tar.gz
  torbrowser-launcher_0.3.1-1~exp1.debian.tar.xz
  torbrowser-launcher_0.3.1-1~exp1_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sat Oct 27 18:55:31 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 27 Oct 2018 17:55:31 +0000
Subject: [Pkg-privacy-maintainers] libotr_4.1.1-3_amd64.changes REJECTED
Message-ID: <E1gGSo7-000ILy-4Y@fasolo.debian.org>



libotr_4.1.1-3.dsc: Invalid size hash for libotr_4.1.1.orig.tar.gz:
According to the control file the size hash should be 643927,
but libotr_4.1.1.orig.tar.gz has 655791.

If you did not include libotr_4.1.1.orig.tar.gz in your upload, a different version
might already be known to the archive software.



===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.



From ftpmaster at ftp-master.debian.org  Sat Oct 27 18:59:57 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 27 Oct 2018 17:59:57 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.3.1-1~exp1_source.changes ACCEPTED into experimental
Message-ID: <E1gGSsP-000J3X-HA@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sun, 28 Oct 2018 02:27:31 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.3.1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.3.1-1~exp1) experimental; urgency=medium
 .
   * New upstream release 0.3.1
     - Ship with latest version of the Tor Browser Developers
       OpenPGP public key
     - Fix bug where TBL window stays open after Tor Browser
       is launched
   * debian/patches:
     - Remove 0004 patch which is already merged upstream.
Checksums-Sha1:
 af46f4c1bf12ceabf4dcd54a4bf6a8a9092dad93 2194 torbrowser-launcher_0.3.1-1~exp1.dsc
 6be2835837261c678da990015cce6f20c0608366 221128 torbrowser-launcher_0.3.1.orig.tar.gz
 99659fc222af26196a9e1b446fdb1b9427f7b100 11280 torbrowser-launcher_0.3.1-1~exp1.debian.tar.xz
 29eb39a2a894c6e593553217e5a9ffbf7f74f31e 6257 torbrowser-launcher_0.3.1-1~exp1_source.buildinfo
Checksums-Sha256:
 5aff9514c2a565964a5d7c990b57e52c699e692d828a8a28ca582706a7b45106 2194 torbrowser-launcher_0.3.1-1~exp1.dsc
 b08b5a09f579fc00ccfac3c4ba9a92d7b2c9d4e2bb8bd3444bfc96a9892a113d 221128 torbrowser-launcher_0.3.1.orig.tar.gz
 1c4e71356c61720d030285d1ae1b41e66606df6ffe2ee4371d3c4fde7d9ff5f4 11280 torbrowser-launcher_0.3.1-1~exp1.debian.tar.xz
 5e0b86dc2e34443c5563034b549e4aca1e97cd5a4ed79dabe5d32c958e0fd1cb 6257 torbrowser-launcher_0.3.1-1~exp1_source.buildinfo
Files:
 6b562c27c18ab128a42cc287ddefafb4 2194 contrib/web optional torbrowser-launcher_0.3.1-1~exp1.dsc
 ba0ac26558e81c9718c32030e9c8110f 221128 contrib/web optional torbrowser-launcher_0.3.1.orig.tar.gz
 3865679ee7c338c9aeaa588172074da7 11280 contrib/web optional torbrowser-launcher_0.3.1-1~exp1.debian.tar.xz
 e807692738f69da8d7a98acb4e89d12c 6257 contrib/web optional torbrowser-launcher_0.3.1-1~exp1_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAlvUoJAQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qG86D/9ExHF2rvxOPS6mi7aZNdaZ41Y9vSAjzZOi
nZrZsznincnccR4p59t+aUnEFffhnjcvZdEZ/IBk3bPCKIukdphBA6HAend1/VdZ
QOvt/dfSOTLUPKsQJeEN1umKK0qlA32kRQ96X7BMr9r1cDRIR9VoU/g/QRufOy+/
xK5VWdRGe3uG9y1tEkcyBOgVR1XXIQHpUuuuv6YB3frE9+jIJUD1sQHbDBg+R187
iLF7xeXONCYmYoNjuwzD/kFrYIhoCrN5QFK9UFGixDlPRKHOG8mTTqPkfOt2mxvE
p2l/MieyiTOyx4OfbpKDQWWmPI2udaV6bJzyK2VaaR60umN2ml4+lWA8bFr3Bqqu
2qgjLXNVx95KRrKSb1S4cCvq2z8d+RF72rbMv+y9f65EYx1tNBTi5uU+t0v3jDVP
j3iT2BZLMMumxjzkHnO9fRkqoiID/V5kPIfzvbFf7e5PKGCupplUSry0qHKyUtsi
tQy7qeJyqYN2AVZ1DYT04TXWrwSMhsVDHul86kXeHnI9EYqk7scqw/i0RMgwnNph
DpwN0Nil9P2WdRVllnOB12NhKWKKO3XzFVMhfC87TlPOZkZ4GtmUcyEhiR64ras6
7unngcZbgOMg0TdER0BFAHKgjlHYR4cS3BhV8GM7pnGMWjFW19jOQtzOKa73GcvH
wjPJyM762A==
=8gzX
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Sat Oct 27 19:47:45 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 27 Oct 2018 18:47:45 +0000
Subject: [Pkg-privacy-maintainers] Processing of libotr_4.1.1-3_amd64.changes
Message-ID: <E1gGTcf-0003t3-7z@usper.debian.org>

libotr_4.1.1-3_amd64.changes uploaded successfully to localhost
along with the files:
  libotr_4.1.1-3.dsc
  libotr_4.1.1-3.debian.tar.xz
  libotr5-bin-dbgsym_4.1.1-3_amd64.deb
  libotr5-bin_4.1.1-3_amd64.deb
  libotr5-dbgsym_4.1.1-3_amd64.deb
  libotr5-dev_4.1.1-3_amd64.deb
  libotr5_4.1.1-3_amd64.deb
  libotr_4.1.1-3_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sat Oct 27 20:26:50 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 27 Oct 2018 19:26:50 +0000
Subject: [Pkg-privacy-maintainers] libotr_4.1.1-3_amd64.changes ACCEPTED
 into unstable
Message-ID: <E1gGUEU-000B6r-0t@fasolo.debian.org>



Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 27 Oct 2018 10:31:51 -0400
Source: libotr
Binary: libotr5 libotr5-bin libotr5-dev
Architecture: source amd64
Version: 4.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Antoine Beaupré <anarcat at debian.org>
Description:
 libotr5    - Off-the-Record Messaging library
 libotr5-bin - toolkit for Off-the-Record Messaging library
 libotr5-dev - Off-the-Record Messaging library development files
Closes: 864093
Changes:
 libotr (4.1.1-3) unstable; urgency=medium
 .
   [ Antoine Beaupré ]
   * Team upload.
   * fix Vcs-* URLs to point at salsa
   * set package to Multi-Arch: same as per QA
   * bump dh compat to 11, drop deps on dh-autoreconf and autotools-dev
   * bump policy to 4.1.2, no change
   * fix minor lintian warnings
 .
   [ Andreas Metzler ]
   * B-d on libgcrypt20-dev instead of (dummy transition package)
     libgcrypt11-dev. (Closes: #864093)
Checksums-Sha1:
 d58cfdf2a8251756fdf4fe70a0f821ccd731f6e9 1740 libotr_4.1.1-3.dsc
 d0939a06f9543d2b508a1917b668561fec58708a 11040 libotr_4.1.1-3.debian.tar.xz
 eeeedd60a3e124af0937e0d73dd57eb6373186fa 129368 libotr5-bin-dbgsym_4.1.1-3_amd64.deb
 75c77d19937e5b010077661ec4b20903ef1289d6 39700 libotr5-bin_4.1.1-3_amd64.deb
 302f7a8c4858269b747dd8011347d31e19434a73 139972 libotr5-dbgsym_4.1.1-3_amd64.deb
 1a9b7c9a8d3f28f908adc6a86bbe82b494ba8393 71680 libotr5-dev_4.1.1-3_amd64.deb
 30195692a4b21c22d9d4160fd3898da4639d4ffb 86476 libotr5_4.1.1-3_amd64.deb
 960286d8051f3850b193e75f85bfb2258c9fc1e0 6302 libotr_4.1.1-3_amd64.buildinfo
Checksums-Sha256:
 6a79a6a6bad8a910e0a5cfeb491b219660cb80d687a32c15d15b1a8228849d10 1740 libotr_4.1.1-3.dsc
 2714873a1f0b569aace609ce5df1bed4a54b17f58094c6dec9fd4e55675b497d 11040 libotr_4.1.1-3.debian.tar.xz
 76dee5567504c1874e9e29d793e008e58a96105fcf5cb2c761a7cfac1ff1bc9a 129368 libotr5-bin-dbgsym_4.1.1-3_amd64.deb
 8b5323a54ea7dffc5acf74c4baf7d174e6c9415ba64a26a11e267fd18a4dab9c 39700 libotr5-bin_4.1.1-3_amd64.deb
 847658fcbfbba6a66d12aa7fab4dc70798577667a5a9d74914de077a5778d432 139972 libotr5-dbgsym_4.1.1-3_amd64.deb
 88a763f6694a73b41647b8e4ace3996f8f543141b137bd59dd50268d28af1b1f 71680 libotr5-dev_4.1.1-3_amd64.deb
 c8bbb69c2d069a4c2b1b8d8740b3b7dec6c45df50a140493f88f91e961dc0dcb 86476 libotr5_4.1.1-3_amd64.deb
 5bccc5c4e16a37df247d16232b5eb43af89921237c423e8c309f40098a598204 6302 libotr_4.1.1-3_amd64.buildinfo
Files:
 d7be74b3ff9a7db2fde22e1dbf68d5c0 1740 libs optional libotr_4.1.1-3.dsc
 e227e666a924a16fa69820ccfe5a6eca 11040 libs optional libotr_4.1.1-3.debian.tar.xz
 53e49d1e950f75057a0c23b0a60557ba 129368 debug optional libotr5-bin-dbgsym_4.1.1-3_amd64.deb
 017f7e6601aabd0e1ee4649d1f0a1411 39700 misc optional libotr5-bin_4.1.1-3_amd64.deb
 9d01ca0e4ad83a5a9ed6caa1087b2184 139972 debug optional libotr5-dbgsym_4.1.1-3_amd64.deb
 2e62bc3ae7d6cc27b45a3194c6f067bc 71680 libdevel optional libotr5-dev_4.1.1-3_amd64.deb
 a500ffaf25b47310f2a84dd6f8cd9dc3 86476 libs optional libotr5_4.1.1-3_amd64.deb
 a172ec763e3974016a233cc793451bdb 6302 libs optional libotr_4.1.1-3_amd64.buildinfo

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

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAlvUr+MACgkQPqHd3bJh
2XtGlAgApwtzUWTNxgb9RobqOGWTFQZ5WjX4xXb3J/M4Hxou7NPm5nrXzkpFm46r
YT1DJRXJux6FOPKajdFnbhlDoLBG3k9sVEsSK3U2rpZJpRVH6E6h8mCnZYO/bJo/
MpAWNUbqXfHif8DYS5fzo2Q0JBzH2g0APkpkF3Ww39uVn9sdZ3SKLGMImA1DYZh0
I73mNUBNxpxfNeRk4GxG8kI4/9D4J5ZFX8HXQUJyL1IxLHyL17txPX8MgyjHxauX
pQf60vFy8K5TtyTwWUP2RN3vSVh3qKliHB5Zn+4B2O404yxUpt8SlqCU/L8VIXpJ
cPjnspVxd93mXWrU4x7dMeuJFW2CPA==
=m+3G
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Sat Oct 27 20:30:03 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 27 Oct 2018 19:30:03 +0000
Subject: [Pkg-privacy-maintainers] Bug#864093: marked as done (libotr:
 Please stop (Build-)Depending on libgcrypt11-dev transition package)
References: <E1gGUEU-000B71-3M@fasolo.debian.org>
 <20170604101838.nqtf52oumj5m47qy@argenau.bebt.de>
Message-ID: <handler.864093.D864093.154066841312320.ackdone@bugs.debian.org>

Your message dated Sat, 27 Oct 2018 19:26:50 +0000
with message-id <E1gGUEU-000B71-3M at fasolo.debian.org>
and subject line Bug#864093: fixed in libotr 4.1.1-3
has caused the Debian Bug report #864093,
regarding libotr: Please stop (Build-)Depending on libgcrypt11-dev transition package
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 at bugs.debian.org
immediately.)


-- 
864093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864093
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Andreas Metzler <ametzler at bebt.de>
Subject: libotr: Please stop (Build-)Depending on libgcrypt11-dev transition package
Date: Sun, 4 Jun 2017 12:18:38 +0200
Size: 2337
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181027/af370c95/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: =?utf-8?q?Antoine_Beaupr=C3=A9?= <anarcat at debian.org>
Subject: Bug#864093: fixed in libotr 4.1.1-3
Date: Sat, 27 Oct 2018 19:26:50 +0000
Size: 6619
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181027/af370c95/attachment-0003.mht>

From noreply at release.debian.org  Mon Oct 29 04:39:11 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Mon, 29 Oct 2018 04:39:11 +0000
Subject: [Pkg-privacy-maintainers] hexchat-otr 0.2.2-2 MIGRATED to testing
Message-ID: <E1gGzKZ-0004Hn-Rx@respighi.debian.org>

FYI: The status of the hexchat-otr source package
in Debian's testing distribution has changed.

  Previous version: 0.2.2-1
  Current version:  0.2.2-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From sunil at medhas.org  Mon Oct 29 07:35:53 2018
From: sunil at medhas.org (Sunil Mohan Adapa)
Date: Mon, 29 Oct 2018 00:35:53 -0700
Subject: [Pkg-privacy-maintainers] Bug#911907: [monkeysphere] Bug#911907:
 Bug#911907: monkeysphere: Install fails on systems with PAM login
 restrictions
In-Reply-To: <87d0rwnam4.fsf@fifthhorseman.net>
References: <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <87d0rwnam4.fsf@fifthhorseman.net>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
Message-ID: <bd9895b5-4096-dd06-367b-c62623a9dc95@medhas.org>

Thank you for the feedback.

On Friday 26 October 2018 05:41 AM, Daniel Kahn Gillmor wrote:
[...]
>>              # requote arguments using bash builtin feature (see "help printf"):
>> -	    su "$MONKEYSPHERE_USER" -s "$(which bash)" -c "$(printf "%q " "$@")"
>> +	    runuser -u "$MONKEYSPHERE_USER" -- "$@"
>>             ;;
> 
> This makes several different changes besides just moving to runuser.  in
> particular, it drops the -s "$(which bash)" (and therefore i think
> relies on the monkeysphere user's chosen shell in /etc/passwd --
> hopefully that's correct, but it might have changed somehow).  Would you
> be ok with reinstating the -s "$(which bash)" arguments?

-s "$(which bash)" was necessary to fix #827660 because su, which uses
user's shell, was used and monkeysphere user had a shell other than bash.

runuser does not seem to depend on the user's shell. It simply runs a
given process under that user's id (with a different PAM configuration).
 This is better at least for the purposes we are using it. Whenever
evaluating bash expressions as a user, we are already doing
'su_monkeysphere_user bash -c "<EXPR>"'.

# usermod -s /usr/sbin/nologin monkeysphere
# su monkeysphere ls
This account is currently not available.
# runuser --user monkeysphere ls
<output>

I am additionally proposing another patch which will remove the shell
for the monkeysphere user in Debian packaging. This closes #901489. We
don't need the monkeysphere user's shell.

> 
> 
> And, it changes how the invocation is passed through -- rather than
> using -c (which can pass shell-specific data) it passes the arguments
> directly to runuser.  This is fine for most cases, but it might fail if
> invoked as something like:
> 
>    su_monkeysphere_user echo test '>' /tmp/foo
> 
> this could do two different things:
> 
>  a) echo "test", the literal ">" symbol,  and the string "/tmp/foo"
>  b) echo "test" into the file "/tmp/foo" as the monkeysphere user.
> 
> The current code seems to assume that the you might want to pass shell
> metacharacters through to be executed that way, and that (b) should be
> the correct result.  I think it's a bad idea to do that, though, and i
> prefer your simpler formulation.
> 
> I'm concerned about the complex constructions (sigh, shell is such a
> mess) passed to su_monkeysphere_user in update_users and add_certifier
> (for monkeysphere-authentication), and add_revoker (for
> monkeysphere-host), though.  Have you tested those subcommands on a live
> system as the superuser?
> 
> If we can go with your proposed simpler argument passing, we definitely
> should!
> 

I didn't test all the situations before, but in this round I did. I ran
all commands with bash -x and ensured that every invocation of the
method in all branches was indeed triggered.

I explicitly changed the name of the method to
'run_as_monkeysphere_user' and changed all invocations to make them
reflect the changed semantics and also to see the full impact. All the
invocations fall into the these categories:

1) Simple invocation of gpg/openpgp2ssh command without passing
environment variables and shell expressions. There is no issues here.

2) Execution of bash snippets. All of these executions where already
wrapped with bash -c "<EXPR>". So they all work as is with runuser.

3) Execution of commands with environment variable passing. Since
runuser preserves environment from the parent process, we can now say
`KEY=VALUE runuser -u monkeysphere gpg` instead of the shell expression
`su monkeysphere KEY=VALUE gpg`. I have updated the patch to handle
these situations properly.

# TESTVAR1='Hello!' runuser -u monkeysphere -- bash -c 'set' |grep TESTVAR1
TESTVAR1='Hello!'

4) Redirection expressions like what you have described above currently
do not exist. I added documentation that bash expressions should not be
run using the method.

It looks like we can keep the simplification.

Thanks,

-- 
Sunil

PS: I ran into issues with TMPDIR as described in #656750 and I am
currently working around them.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Use-runuser-instead-of-su.patch
Type: text/x-patch
Size: 8314 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181029/9b7df83c/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-debian-Remove-shell-for-monkeysphere-user.patch
Type: text/x-patch
Size: 1313 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181029/9b7df83c/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181029/9b7df83c/attachment-0001.sig>

From ftpmaster at ftp-master.debian.org  Mon Oct 29 10:00:31 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Mon, 29 Oct 2018 10:00:31 +0000
Subject: [Pkg-privacy-maintainers] onionshare_1.3-1~bpo9+1_amd64.changes
 ACCEPTED into stretch-backports, stretch-backports
Message-ID: <E1gH4LX-0009AK-HM@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Thu, 25 Oct 2018 15:45:15 +0200
Source: onionshare
Binary: onionshare
Architecture: source all
Version: 1.3-1~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Ulrike Uhlig <ulrike at debian.org>
Description:
 onionshare - Share a file over Tor Hidden Services anonymously and securely
Changes:
 onionshare (1.3-1~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
Checksums-Sha1:
 d0d5833f49b5248c64a1e553c71ecc64d5e61a29 2184 onionshare_1.3-1~bpo9+1.dsc
 ad5eabb2d23ae75039718c9b3b4d4e554e9d498a 5436 onionshare_1.3-1~bpo9+1.debian.tar.xz
 b094ad461b2c7ecd1e5a5d077a600df9e71dd1cd 104308 onionshare_1.3-1~bpo9+1_all.deb
 51271c3d4cba6f8772e65a6826c45247ad99c368 12703 onionshare_1.3-1~bpo9+1_amd64.buildinfo
Checksums-Sha256:
 46f63e6496ab9c41d3b17b1eb2c05ef4001a0ee4d0bc6f94b3ed1ab5effe4182 2184 onionshare_1.3-1~bpo9+1.dsc
 228fc61a17845204cdac66c58f7b3b0d015c36441e0c2a39af6c3e1d63c09317 5436 onionshare_1.3-1~bpo9+1.debian.tar.xz
 205e795aa3206216e3800bb420c94f433ed8b8804e0e001d57813569e405e145 104308 onionshare_1.3-1~bpo9+1_all.deb
 59a1c1266486ef0ec7f0535c783acebcbbf9da2979b9054bf4e753975ef9e0d2 12703 onionshare_1.3-1~bpo9+1_amd64.buildinfo
Files:
 b3d1ba1af7818013740cc2a5045d058a 2184 net optional onionshare_1.3-1~bpo9+1.dsc
 969b16aee82389566ed22a9875af84ca 5436 net optional onionshare_1.3-1~bpo9+1.debian.tar.xz
 81f696e45b6e092f6a5d855ec9d20ba3 104308 net optional onionshare_1.3-1~bpo9+1_all.deb
 141f11f8e376796b5365dabfe193ad58 12703 net optional onionshare_1.3-1~bpo9+1_amd64.buildinfo

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

iQJGBAEBCgAwFiEE7eP0RD800mGVFNeQsUuww42GHPEFAlvRyiISHHVscmlrZUBk
ZWJpYW4ub3JnAAoJELFLsMONhhzxtM8P/3kO9fKNxCbM1JDUovYXIRc5bMmqJP9J
ffmEFspCTNJe+FaADmUKHktGOzfi5tVZfaapvfj3tj+Hdhyx0dqwf3sgtPzfnp1i
4bLSFudF/qixvVO+xQ1GccPWps3l8dYDKpVdT7p7zSr/HNGr5ZlMDd/fYzzeNXE8
qhp0qa2xj1WXdzI5Y9Keh9XwafzxudDZGouAWH413kcz80AHHCal6CHANDJsYLkD
HNRHV/P8ZHQlSjbtUoXmZSVa4DjLw8Eu7sTXjBjFHaOk290in/pbGulWMYWDq3St
YD8sN0JbcHRJf6LUzZ+GVwIdgJ/5Vn0rBC6FIhj3R18b6z8EExfaXhBomKuQhQkq
7a7H+sk38VN3r/CPtkpVmbtpr9GZnz8GebK1ccHuG2cVA9RSHzjf6YiOGgDlMvHQ
sId7DfzWLvizbsEe1mSjXXbMvvcbiVnfNmufB2VeHKgc4rGWpEWzLcxGm4X/A4TA
+ne1Xklm5MJtspwRJs+OuDYT/prNQxj/SoozHGnWaptI2CuqcqB+jGnQVf/zroh0
Y/1HKQj23a9ftjsTLRxNwL2a9b7tndRTtQR2xuM8OBDxvQoVvxnkD60eR9VLJjmY
khcD6RLEVtlLee66x7jlibDRRiN3vgIQy25Jwe4o9j1fMglvB3L26L6NSo4qUNDb
7D8Qph9ULQCC
=4A8b
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From dkg at fifthhorseman.net  Mon Oct 29 12:24:39 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Mon, 29 Oct 2018 08:24:39 -0400
Subject: [Pkg-privacy-maintainers] Bug#911907: [monkeysphere] Bug#911907:
 Bug#911907: monkeysphere: Install fails on systems with PAM login
 restrictions
In-Reply-To: <bd9895b5-4096-dd06-367b-c62623a9dc95@medhas.org>
References: <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <87d0rwnam4.fsf@fifthhorseman.net>
 <bd9895b5-4096-dd06-367b-c62623a9dc95@medhas.org>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
Message-ID: <87lg6hj5yw.fsf@fifthhorseman.net>

Hi Sunil--

thanks for all your work on this.  i think we're heading for a
significant improvement here :)

On Mon 2018-10-29 00:35:53 -0700, Sunil Mohan Adapa wrote:
> runuser does not seem to depend on the user's shell. It simply runs a
> given process under that user's id (with a different PAM configuration).
>  This is better at least for the purposes we are using it. Whenever
> evaluating bash expressions as a user, we are already doing
> 'su_monkeysphere_user bash -c "<EXPR>"'.
>
> # usermod -s /usr/sbin/nologin monkeysphere
> # su monkeysphere ls
> This account is currently not available.
> # runuser --user monkeysphere ls
> <output>

reading the documentation for runuser:

       -s, --shell=shell
              Run  the  specified  shell instead of the default.  The shell to
              run is selected according to the following rules, in order:

                 o      the shell specified with --shell

                 o      the shell specified in the environment variable  SHELL
                        if the --preserve-environment option is used

                 o      the  shell  listed  in  the passwd entry of the target
                        user

                 o      /bin/sh

              If the target user has a restricted shell (i.e.  not  listed  in
              /etc/shells)  the --shell option and the SHELL environment vari‐
              ables are ignored unless the calling user is root.


which of these cases do you think is triggering the shell selection in
run_as_monkeysphere_user?

> I am additionally proposing another patch which will remove the shell
> for the monkeysphere user in Debian packaging. This closes #901489. We
> don't need the monkeysphere user's shell.

Interesting, thanks!

> I didn't test all the situations before, but in this round I did. I ran
> all commands with bash -x and ensured that every invocation of the
> method in all branches was indeed triggered.
>
> I explicitly changed the name of the method to
> 'run_as_monkeysphere_user' and changed all invocations to make them
> reflect the changed semantics and also to see the full impact.

Thanks, this is a good move.

> All the invocations fall into the these categories:
>
> 1) Simple invocation of gpg/openpgp2ssh command without passing
> environment variables and shell expressions. There is no issues here.
>
> 2) Execution of bash snippets. All of these executions where already
> wrapped with bash -c "<EXPR>". So they all work as is with runuser.
>
> 3) Execution of commands with environment variable passing. Since
> runuser preserves environment from the parent process, we can now say
> `KEY=VALUE runuser -u monkeysphere gpg` instead of the shell expression
> `su monkeysphere KEY=VALUE gpg`. I have updated the patch to handle
> these situations properly.
>
> # TESTVAR1='Hello!' runuser -u monkeysphere -- bash -c 'set' |grep TESTVAR1
> TESTVAR1='Hello!'

while we certainly *can* do this, this change means that runuser itself
will see the changed environment variable, which might affect runuser's
behavior, or the behavior of the (arbitrary, unknown!) pam stack that
runuser executes.  Is that really a desirable outcome?  in general, i'd
lean toward the smallest perturbation possible.  Can we avoid that
problem?

What if we replaced "su_monkeysphere_user KEY=value foo arg" with
"run_as_monkeysphere_user env KEY=value foo arg" instead?

> 4) Redirection expressions like what you have described above currently
> do not exist. I added documentation that bash expressions should not be
> run using the method.

I didn't mean to imply that redirection was the only thing.  what about
other shell metacharacters, like ';' or '||' ?

When you say "no shell expressions" in the comments, does that include
function invocations? variable assignments?

> PS: I ran into issues with TMPDIR as described in #656750 and I am
> currently working around them.

hm, this sounds like it might be an interaction across your changes made
to point 3, above, but i'm not sure how.  can you explain the issues
you're running into in more detail?  can you explain your workaround?

thanks for working on this!

       --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181029/e0e76fe4/attachment.sig>

From owner at bugs.debian.org  Mon Oct 29 16:21:15 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 29 Oct 2018 16:21:15 +0000
Subject: [Pkg-privacy-maintainers] Bug#908473: marked as done
 (torbrowser-launcher: ValueError: Unknown endpoint type: '127.0.0.1')
References: <CAEQ9gEk8a_SwGPiOV-ykcB1Pim8qQZosQ_jHHo9+ewCR7Yqngg@mail.gmail.com>
 <153657075796.21415.10838481070950269388.reportbug@think>
Message-ID: <handler.908473.D908473.154082984532436.ackdone@bugs.debian.org>

Your message dated Tue, 30 Oct 2018 01:17:10 +0900
with message-id <CAEQ9gEk8a_SwGPiOV-ykcB1Pim8qQZosQ_jHHo9+ewCR7Yqngg at mail.gmail.com>
and subject line Re: [Pkg-privacy-maintainers] Bug#908473: torbrowser-launcher: ValueError: Unknown endpoint type: '127.0.0.1'
has caused the Debian Bug report #908473,
regarding torbrowser-launcher: ValueError: Unknown endpoint type: '127.0.0.1'
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 at bugs.debian.org
immediately.)


-- 
908473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908473
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Mykola Nikishov <mn at mn.com.ua>
Subject: torbrowser-launcher: ValueError: Unknown endpoint type: '127.0.0.1'
Date: Mon, 10 Sep 2018 12:12:37 +0300
Size: 4501
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181029/285a9668/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Re: [Pkg-privacy-maintainers] Bug#908473: torbrowser-launcher: ValueError: Unknown endpoint type: '127.0.0.1'
Date: Tue, 30 Oct 2018 01:17:10 +0900
Size: 3778
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181029/285a9668/attachment-0001.mht>

From sunil at medhas.org  Mon Oct 29 18:50:14 2018
From: sunil at medhas.org (Sunil Mohan Adapa)
Date: Mon, 29 Oct 2018 11:50:14 -0700
Subject: [Pkg-privacy-maintainers] Bug#911907: [monkeysphere] Bug#911907:
 Bug#911907: monkeysphere: Install fails on systems with PAM login
 restrictions
In-Reply-To: <87lg6hj5yw.fsf@fifthhorseman.net>
References: <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <87d0rwnam4.fsf@fifthhorseman.net>
 <bd9895b5-4096-dd06-367b-c62623a9dc95@medhas.org>
 <87lg6hj5yw.fsf@fifthhorseman.net>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
Message-ID: <9d74d54a-e901-c01a-e6db-9b8aa36f752e@medhas.org>

On Monday 29 October 2018 05:24 AM, Daniel Kahn Gillmor wrote:
[...]
>> # usermod -s /usr/sbin/nologin monkeysphere
>> # su monkeysphere ls
>> This account is currently not available.
>> # runuser --user monkeysphere ls
>> <output>
> 
> reading the documentation for runuser:
> 
>        -s, --shell=shell
>               Run  the  specified  shell instead of the default.  The shell to
>               run is selected according to the following rules, in order:
> 
>                  o      the shell specified with --shell
> 
>                  o      the shell specified in the environment variable  SHELL
>                         if the --preserve-environment option is used
> 
>                  o      the  shell  listed  in  the passwd entry of the target
>                         user
> 
>                  o      /bin/sh
> 
>               If the target user has a restricted shell (i.e.  not  listed  in
>               /etc/shells)  the --shell option and the SHELL environment vari‐
>               ables are ignored unless the calling user is root.
> 
> 
> which of these cases do you think is triggering the shell selection in
> run_as_monkeysphere_user?
> 

I believe this option is only applicable if we run `runuser -
monkeysphere` and not when we run `runuser --user monkeysphere`.

From runuser man page: "runuser allows to run commands with a substitute
user and group ID. If the option -u is not given, it falls back to
su-compatible semantics and a shell is executed."

Running with -u
---------------

# usermod -s /bin/dash monkeysphere
# runuser -u monkeysphere --shell /bin/dash sleep 100
runuser: options --{shell,fast,command,session-command,login} and --user
are mutually exclusive

# runuser -u monkeysphere sleep 100
# pstree -ap 8969
bash,8969
  `-runuser,32377 -u monkeysphere sleep 100
      `-sleep,32378 100

Running with -
--------------

# usermod -s /bin/dash monkeysphere
# runuser monkeysphere -s /bin/dash -c 'sleep 100'
# pstree -ap 8969
bash,8969
  `-runuser,4677 monkeysphere -s /bin/dash -c sleep 100
      `-dash,4678 -c sleep 100
          `-sleep,4679 100
# runuser monkeysphere -c 'sleep 100'
# pstree -ap 8969
bash,8969
  `-runuser,5403 monkeysphere -c sleep 100
      `-dash,5404 -c sleep 100
          `-sleep,5405 100

[..]
>> # TESTVAR1='Hello!' runuser -u monkeysphere -- bash -c 'set' |grep TESTVAR1
>> TESTVAR1='Hello!'
> 
> while we certainly *can* do this, this change means that runuser itself
> will see the changed environment variable, which might affect runuser's
> behavior, or the behavior of the (arbitrary, unknown!) pam stack that
> runuser executes.  Is that really a desirable outcome?  in general, i'd
> lean toward the smallest perturbation possible.  Can we avoid that
> problem?
> 
> What if we replaced "su_monkeysphere_user KEY=value foo arg" with
> "run_as_monkeysphere_user env KEY=value foo arg" instead?

I agree that it is better to not expose the environment to runuser. I
will make the change to use 'env' instead.

A bigger concern should be to scrub all environment from the parent root
user process except for the values that need to be passed down.
Unfortunately, this is an issue equally problematic in the earlier and
proposed code.

# TESTVAR1='test' su -s /bin/bash -c 'set' |grep TESTVAR
TESTVAR1=test

# TESTVAR1='test' runuser -u monkeysphere -- bash -c set |grep TESTVAR
TESTVAR1=test

I will try to scrub the environment using 'env -i' and see if that
introduces any breakages.

> 
>> 4) Redirection expressions like what you have described above currently
>> do not exist. I added documentation that bash expressions should not be
>> run using the method.
> 
> I didn't mean to imply that redirection was the only thing.  what about
> other shell metacharacters, like ';' or '||' ?
> 
> When you say "no shell expressions" in the comments, does that include
> function invocations? variable assignments?

Yes, that includes:

- No function invocations which have been done explicitly using bash -c
'. <source>; <function>'.

- No shell metacharacters such as '&', ';', '|', '||', '<', '>' etc.

- Variable assignments were done but handled differently in my patch
(above discussion).

> 
>> PS: I ran into issues with TMPDIR as described in #656750 and I am
>> currently working around them.
> 
> hm, this sounds like it might be an interaction across your changes made
> to point 3, above, but i'm not sure how.  can you explain the issues
> you're running into in more detail?  can you explain your workaround?
> 

I belive this is because I have libpam-tmpdir installed on my test VM
(FreedomBox). I will test my next patch without this.

Thanks,

-- 
Sunil

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181029/463862e5/attachment-0001.sig>

From sunil at medhas.org  Mon Oct 29 19:56:48 2018
From: sunil at medhas.org (Sunil Mohan Adapa)
Date: Mon, 29 Oct 2018 12:56:48 -0700
Subject: [Pkg-privacy-maintainers] Bug#911907: monkeysphere: Patch v3
In-Reply-To: <9d74d54a-e901-c01a-e6db-9b8aa36f752e@medhas.org>
References: <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <87d0rwnam4.fsf@fifthhorseman.net>
 <bd9895b5-4096-dd06-367b-c62623a9dc95@medhas.org>
 <87lg6hj5yw.fsf@fifthhorseman.net>
 <9d74d54a-e901-c01a-e6db-9b8aa36f752e@medhas.org>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
Message-ID: <d94ae239-02f1-2720-5f40-71512454f044@medhas.org>

On Monday 29 October 2018 11:50 AM, Sunil Mohan Adapa wrote:
[...]
> 
> I agree that it is better to not expose the environment to runuser. I
> will make the change to use 'env' instead.

Attached the patches do this with /usr/bin/env (better to have full
path?). I have retested all invocations again.

> 
> A bigger concern should be to scrub all environment from the parent root
> user process except for the values that need to be passed down.
> Unfortunately, this is an issue equally problematic in the earlier and
> proposed code.
> 
> # TESTVAR1='test' su -s /bin/bash -c 'set' |grep TESTVAR
> TESTVAR1=test
> 
> # TESTVAR1='test' runuser -u monkeysphere -- bash -c set |grep TESTVAR
> TESTVAR1=test
> 
> I will try to scrub the environment using 'env -i' and see if that
> introduces any breakages.

I tried this and it looks like this requires more changes and time which
I currently am short on. So, I am not proposing 'env -i' at this time.

[...]
> 
> I belive this is because I have libpam-tmpdir installed on my test VM
> (FreedomBox). I will test my next patch without this.

I confirm that I no longer see problems with TMPDIR after removing
libpam-tmpdir from the system.

Thanks,

-- 
Sunil
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Use-runuser-instead-of-su.patch
Type: text/x-patch
Size: 8385 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181029/f2692592/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-debian-Remove-shell-for-monkeysphere-user.patch
Type: text/x-patch
Size: 1313 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181029/f2692592/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181029/f2692592/attachment.sig>

From noreply at release.debian.org  Tue Oct 30 04:39:13 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Tue, 30 Oct 2018 04:39:13 +0000
Subject: [Pkg-privacy-maintainers] nautilus-wipe 0.3-2 MIGRATED to testing
Message-ID: <E1gHLo9-0003k4-CG@respighi.debian.org>

FYI: The status of the nautilus-wipe source package
in Debian's testing distribution has changed.

  Previous version: 0.3-1
  Current version:  0.3-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From dkg at fifthhorseman.net  Tue Oct 30 16:19:49 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Tue, 30 Oct 2018 12:19:49 -0400
Subject: [Pkg-privacy-maintainers] Bug#911907: monkeysphere: Patch v3
In-Reply-To: <d94ae239-02f1-2720-5f40-71512454f044@medhas.org>
References: <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <87d0rwnam4.fsf@fifthhorseman.net>
 <bd9895b5-4096-dd06-367b-c62623a9dc95@medhas.org>
 <87lg6hj5yw.fsf@fifthhorseman.net>
 <9d74d54a-e901-c01a-e6db-9b8aa36f752e@medhas.org>
 <d94ae239-02f1-2720-5f40-71512454f044@medhas.org>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
Message-ID: <877ehzflui.fsf@fifthhorseman.net>

On Mon 2018-10-29 12:56:48 -0700, Sunil Mohan Adapa wrote:
> Attached the patches do this with /usr/bin/env (better to have full
> path?). I have retested all invocations again.

thanks!  I've applied your patch on the master branch upstream, and then
also changed /usr/bin/env to just "env" -- no reason to be brittle about
where "env" is found on the system.

We haven't released 0.43 yet, but when we do, this change will be
incorporated in it.

> I tried this and it looks like this requires more changes and time which
> I currently am short on. So, I am not proposing 'env -i' at this time.

sounds reasonable to me.

> I confirm that I no longer see problems with TMPDIR after removing
> libpam-tmpdir from the system.

do you think we could just explicitly override TMPDIR as proposed in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656750#57 to solve
that problem on systems where libpam-tmpdir is present?  I'd welcome a
patch for that too.  Maybe that'd be enough to ship a new upstream
bugfix release -- or do you have other bugs you want to fix before a
release?

> From 435f978ac7815b10eae87c82aa7198d6833c4857 Mon Sep 17 00:00:00 2001
> From: Sunil Mohan Adapa <sunil at medhas.org>
> Date: Sat, 27 Oct 2018 11:00:04 -0700
> Subject: [PATCH] debian: Remove shell for monkeysphere user

i applied a variant of this patch on the debian/master branch (with the
intent that it will only ship as part of the debian packaging once 0.43
is released.  the variant includes a comment encouraging removal of the
additional usermod once a debian stable release has been made that
forces the shell to nologin.

thanks for this work, Sunil!

       --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181030/5bffa4c2/attachment.sig>

From intrigeri at debian.org  Tue Oct 30 17:59:16 2018
From: intrigeri at debian.org (intrigeri)
Date: Tue, 30 Oct 2018 18:59:16 +0100
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v4)
In-Reply-To: <20181018135227.GI19229@debian>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
 <87h8hkb5yl.fsf@fifthhorseman.net> <875zy0jhwk.fsf@curie.anarc.at>
 <87bm7rc3sk.fsf@fifthhorseman.net> <20181018135227.GI19229@debian>
Message-ID: <877ehz71u3.fsf@boum.org>

Georg Faerber:
> On 18-10-17 23:49:31, Daniel Kahn Gillmor wrote:
>> I support version 4 of this proposal.

> Me too.

+1 and thanks a lot :)


From sunil at medhas.org  Tue Oct 30 18:03:02 2018
From: sunil at medhas.org (Sunil Mohan Adapa)
Date: Tue, 30 Oct 2018 11:03:02 -0700
Subject: [Pkg-privacy-maintainers] Bug#911907: [monkeysphere] Bug#911907:
 monkeysphere: Patch v3
In-Reply-To: <877ehzflui.fsf@fifthhorseman.net>
References: <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <87d0rwnam4.fsf@fifthhorseman.net>
 <bd9895b5-4096-dd06-367b-c62623a9dc95@medhas.org>
 <87lg6hj5yw.fsf@fifthhorseman.net>
 <9d74d54a-e901-c01a-e6db-9b8aa36f752e@medhas.org>
 <d94ae239-02f1-2720-5f40-71512454f044@medhas.org>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <877ehzflui.fsf@fifthhorseman.net>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
Message-ID: <e372db8f-4332-798e-de9c-1bf7a7a885db@medhas.org>

On Tuesday 30 October 2018 09:19 AM, Daniel Kahn Gillmor wrote:
> On Mon 2018-10-29 12:56:48 -0700, Sunil Mohan Adapa wrote:
>> Attached the patches do this with /usr/bin/env (better to have full
>> path?). I have retested all invocations again.
> 
> thanks!  I've applied your patch on the master branch upstream, and then
> also changed /usr/bin/env to just "env" -- no reason to be brittle about
> where "env" is found on the system.
> 
> We haven't released 0.43 yet, but when we do, this change will be
> incorporated in it.

Sounds good. Thank you for accepting the patch.

[...]
>> I confirm that I no longer see problems with TMPDIR after removing
>> libpam-tmpdir from the system.
> 
> do you think we could just explicitly override TMPDIR as proposed in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656750#57 to solve
> that problem on systems where libpam-tmpdir is present?  I'd welcome a
> patch for that too.  Maybe that'd be enough to ship a new upstream
> bugfix release -- or do you have other bugs you want to fix before a
> release?

We have been setting the TMPDIR to
/var/lib/monkeysphere/authentication/tmp/ in FreedomBox for some time
now to work around the problem.  So, I think, in general, this solution
is fine.  However, perhaps we could conservatively use it only in the
very few situations that we actually need to share TMPDIR across two
process owned by different users.

Thanks,

-- 
Sunil

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181030/a4a5857a/attachment.sig>

From intrigeri at debian.org  Tue Oct 30 18:08:32 2018
From: intrigeri at debian.org (intrigeri)
Date: Tue, 30 Oct 2018 19:08:32 +0100
Subject: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: Bug#836266:
 Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.
In-Reply-To: <87efejxn1t.fsf@curie.anarc.at>
References: <56b2d2d0-6e49-5b36-b3ad-e411ea56a749@lelutin.ca>
 <85k2bdax6l.fsf@boum.org> <87y3ztkkn0.fsf@alice.fifthhorseman.net>
 <85r35jkezm.fsf@boum.org> <20170110191543.2iaq3ydyvi3x6phr@curie.anarc.at>
 <87tw96qw1g.fsf@alice.fifthhorseman.net> <87efejxn1t.fsf@curie.anarc.at>
 <147271681970.8046.17334661827976627790.reportbug@melchior.hokkemirin.ddo.jp>
Message-ID: <8736sn71en.fsf@boum.org>

Hi!

Antoine Beaupré:
> I know this is not Parcimonie's fault. It's gnupg's fault or, more
> precisely, dirmngr's, but it seems difficult to change things over
> there: this would require rewriting dirmngr's network routines

… at least so they're network-status aware and don't treat "my system
is offline" as "the keyserver is down".

> or reimplementing parcimonie within dirmngr itself.

Sure, that would be ideal. Note that it *also* requires fixing dirmngr.

> Instead, I've started thinking about what a parcimonie rewrite would
> look like, one that would *not* depend on dirmngr (or, in fact, any
> specific OpenPGP implementation). If you permit, I would like to use
> this space to brainstorm such a design […]

I'm glad you're bringing such out-of-the-box thinking in this space!
It's refreshing. I did not put much thought into it yet but at first
glance, your design makes sense to me.

> All this doesn't seem that complicated to me. The tricky bit is the gate
> to keep garbage and hostile keys from going into the keyring.

Agreed, that was my concern as well.

> I would welcome feedback on how this could be done, or if it's just an
> incredibly stupid idea.

I'll happily let you reuse the parcimonie name once you have it
working with good enough™ backwards compatibility with the
current interfaces.

> Thanks, and sorry for hijacking this thread with such wild ideas. :)

By all means, please keep going wild :)

Cheers,
-- 
intrigeri


From anarcat at debian.org  Tue Oct 30 18:28:50 2018
From: anarcat at debian.org (Antoine =?UTF-8?Q?Beaupr=C3=A9?=)
Date: Tue, 30 Oct 2018 14:28:50 -0400
Subject: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: Bug#836266:
 Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.
In-Reply-To: <8736sn71en.fsf@boum.org>
References: <56b2d2d0-6e49-5b36-b3ad-e411ea56a749@lelutin.ca>
 <85k2bdax6l.fsf@boum.org> <87y3ztkkn0.fsf@alice.fifthhorseman.net>
 <85r35jkezm.fsf@boum.org> <20170110191543.2iaq3ydyvi3x6phr@curie.anarc.at>
 <87tw96qw1g.fsf@alice.fifthhorseman.net> <87efejxn1t.fsf@curie.anarc.at>
 <8736sn71en.fsf@boum.org>
 <147271681970.8046.17334661827976627790.reportbug@melchior.hokkemirin.ddo.jp>
Message-ID: <87k1lz9tlp.fsf@curie.anarc.at>

On 2018-10-30 19:08:32, intrigeri wrote:

[...]

>> Instead, I've started thinking about what a parcimonie rewrite would
>> look like, one that would *not* depend on dirmngr (or, in fact, any
>> specific OpenPGP implementation). If you permit, I would like to use
>> this space to brainstorm such a design […]
>
> I'm glad you're bringing such out-of-the-box thinking in this space!
> It's refreshing. I did not put much thought into it yet but at first
> glance, your design makes sense to me.

Thanks! :)

>> All this doesn't seem that complicated to me. The tricky bit is the gate
>> to keep garbage and hostile keys from going into the keyring.
>
> Agreed, that was my concern as well.

As it turns out, while doing a review of the upcoming gpg2 update for
stretch, I found out that GnuPG supports "filters" in gpg --import,
through the `--import-filter` commandline option. Some key improvements
of that are being backported to stretch as well. This is basically what
we'd be looking at to implement this crucial component:

https://manpages.debian.org/unstable/gpg/gpg.1.en.html#FILTER_EXPRESSIONS

Through those, there should be a way to avoid importing secret keys and
make sure the imported key material matches (one of?) the UID we are
looking at. It's too bad we can't restrict on a fingerprint there...

Something to think about, anyways.

>> I would welcome feedback on how this could be done, or if it's just an
>> incredibly stupid idea.
>
> I'll happily let you reuse the parcimonie name once you have it
> working with good enough™ backwards compatibility with the
> current interfaces.

Glad to hear that.

A.
-- 
Sous un gouvernement qui emprisonne injustement, la place de l’homme
juste est aussi en prison.
                        - La désobéissance civile, Henry David Thoreau


From dkg at fifthhorseman.net  Tue Oct 30 18:49:39 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Tue, 30 Oct 2018 14:49:39 -0400
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v4)
In-Reply-To: <877ehz71u3.fsf@boum.org>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
 <87h8hkb5yl.fsf@fifthhorseman.net> <875zy0jhwk.fsf@curie.anarc.at>
 <87bm7rc3sk.fsf@fifthhorseman.net> <20181018135227.GI19229@debian>
 <877ehz71u3.fsf@boum.org>
Message-ID: <87bm7be0cc.fsf@fifthhorseman.net>

On Tue 2018-10-30 18:59:16 +0100, intrigeri wrote:
> Georg Faerber:
>> On 18-10-17 23:49:31, Daniel Kahn Gillmor wrote:
>>> I support version 4 of this proposal.
>
>> Me too.
>
> +1 and thanks a lot :)

two days from now is the deadline for this proposal, and we currently
have (i think) 5 approvers:

  * dkg
  * anarcat
  * u.
  * georg
  * intrigeri

and no dissenters.

reading our decision-making process to try to figure out if this is
right, i realize that i don't know how we assess who is actually on the
team!

is this the canonical list?

   https://salsa.debian.org/groups/pkg-privacy-team/-/group_members

the decision-making process says:

      At the end of its time limit, the proposal is accepted if there
      are positive votes from 1/3 (rounding up) of the team members at
      the time the proposal is made, or 3 team members, whichever is the
      smallest; and no negative votes.

the list above has 21 members.  so 1/3 of that is 7.  3 < 7, so we need
at least 3, and we have 5 supporters.

so, barring objections in the next couple of days, this looks like it
will be approved and adopted by the group.  If you have a problem with
it, please speak up!

     --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181030/e1cd3407/attachment.sig>

From dkg at fifthhorseman.net  Tue Oct 30 18:44:01 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Tue, 30 Oct 2018 14:44:01 -0400
Subject: [Pkg-privacy-maintainers] Bug#911907: [monkeysphere] Bug#911907:
 monkeysphere: Patch v3
In-Reply-To: <e372db8f-4332-798e-de9c-1bf7a7a885db@medhas.org>
References: <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <87d0rwnam4.fsf@fifthhorseman.net>
 <bd9895b5-4096-dd06-367b-c62623a9dc95@medhas.org>
 <87lg6hj5yw.fsf@fifthhorseman.net>
 <9d74d54a-e901-c01a-e6db-9b8aa36f752e@medhas.org>
 <d94ae239-02f1-2720-5f40-71512454f044@medhas.org>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
 <877ehzflui.fsf@fifthhorseman.net>
 <e372db8f-4332-798e-de9c-1bf7a7a885db@medhas.org>
 <154051681157.30961.468825320149255298.reportbug@towel.localdomain>
Message-ID: <87efc7e0lq.fsf@fifthhorseman.net>

On Tue 2018-10-30 11:03:02 -0700, Sunil Mohan Adapa wrote:
> We have been setting the TMPDIR to
> /var/lib/monkeysphere/authentication/tmp/ in FreedomBox for some time
> now to work around the problem.  So, I think, in general, this solution
> is fine.  However, perhaps we could conservatively use it only in the
> very few situations that we actually need to share TMPDIR across two
> process owned by different users.

Are you patching monkeysphere for this?  or are you doing it outside of
monkeysphere?

on systems that i'm looking at, /varlib/monkeysphere/authentication/tmp
is owned root:monkeysphere, with permissions 0750.

so the monkeysphere user can read in it, but can't write.

can you give an example of the specific error cases you're seeing with
libpam-tmpdir?  even better, perhaps this could be followup on
https://bugs.debian.org/656750 :)

Regards,

        --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181030/81854c52/attachment.sig>

From intrigeri at debian.org  Tue Oct 30 19:04:00 2018
From: intrigeri at debian.org (intrigeri)
Date: Tue, 30 Oct 2018 20:04:00 +0100
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v4)
In-Reply-To: <87bm7be0cc.fsf@fifthhorseman.net>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
 <87h8hkb5yl.fsf@fifthhorseman.net> <875zy0jhwk.fsf@curie.anarc.at>
 <87bm7rc3sk.fsf@fifthhorseman.net> <20181018135227.GI19229@debian>
 <877ehz71u3.fsf@boum.org> <87bm7be0cc.fsf@fifthhorseman.net>
Message-ID: <878t2f5k9r.fsf@boum.org>

Daniel Kahn Gillmor:
> reading our decision-making process to try to figure out if this is
> right, i realize that i don't know how we assess who is actually on the
> team!

> is this the canonical list?

>    https://salsa.debian.org/groups/pkg-privacy-team/-/group_members

I would say so, yes. The closest thing I've found in our process is
"Team members are given commit rights on all team-maintained packages
repositories", which seems to confirm this hunch. I think that's the
only list we have that can only be joined after some collective
decision making process.

Cheers,
-- 
intrigeri


From noreply at release.debian.org  Wed Oct 31 04:39:14 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Wed, 31 Oct 2018 04:39:14 +0000
Subject: [Pkg-privacy-maintainers] tails-installer 5.0.12+dfsg-1 MIGRATED to
 testing
Message-ID: <E1gHiHi-0002nw-F7@respighi.debian.org>

FYI: The status of the tails-installer source package
in Debian's testing distribution has changed.

  Previous version: 5.0.8+dfsg-1
  Current version:  5.0.12+dfsg-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From jonas at freesources.org  Wed Oct 31 13:51:05 2018
From: jonas at freesources.org (Jonas Meurer)
Date: Wed, 31 Oct 2018 14:51:05 +0100
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v4)
In-Reply-To: <877ehz71u3.fsf@boum.org>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
 <87h8hkb5yl.fsf@fifthhorseman.net> <875zy0jhwk.fsf@curie.anarc.at>
 <87bm7rc3sk.fsf@fifthhorseman.net> <20181018135227.GI19229@debian>
 <877ehz71u3.fsf@boum.org>
Message-ID: <795e21e3-ee68-2a51-b48b-25d555c1ec6c@freesources.org>

Am 30.10.18 um 18:59 schrieb intrigeri:
> Georg Faerber:
>> On 18-10-17 23:49:31, Daniel Kahn Gillmor wrote:
>>> I support version 4 of this proposal.
> 
>> Me too.
> 
> +1 and thanks a lot :)

+1 from me as well. Thanks a lot for the proposal!

Cheers
 jonas


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181031/14e28b37/attachment.sig>

From ulrike at debian.org  Wed Oct 31 14:03:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Wed, 31 Oct 2018 14:03:00 +0000
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v4)
In-Reply-To: <87bm7be0cc.fsf@fifthhorseman.net>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
 <87h8hkb5yl.fsf@fifthhorseman.net> <875zy0jhwk.fsf@curie.anarc.at>
 <87bm7rc3sk.fsf@fifthhorseman.net> <20181018135227.GI19229@debian>
 <877ehz71u3.fsf@boum.org> <87bm7be0cc.fsf@fifthhorseman.net>
Message-ID: <d5d25ec6-cf19-d01f-d4fe-c2e145e4c602@debian.org>

Hi!

Daniel Kahn Gillmor:
> On Tue 2018-10-30 18:59:16 +0100, intrigeri wrote:
>> Georg Faerber:
>>> On 18-10-17 23:49:31, Daniel Kahn Gillmor wrote:
>>>> I support version 4 of this proposal.

> reading our decision-making process to try to figure out if this is
> right, i realize that i don't know how we assess who is actually on the
> team!
> 
> is this the canonical list?
> 
>    https://salsa.debian.org/groups/pkg-privacy-team/-/group_members

I fear that not everyone on the member list is on the mailing list.

Also, it might actually make sense to see who of the members (that had
been copied from Alioth) are actually active. I see at least two people
who I believe to not really be active in this team anymore. Should I
draft something according to point 1.3 of
https://salsa.debian.org/pkg-privacy-team/team-processes/blob/master/pkg-privacy-process.mdwn
?

Cheers!
u.


From ftpmaster at ftp-master.debian.org  Wed Oct 31 15:59:53 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 31 Oct 2018 15:59:53 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.3.1-1_source.changes
Message-ID: <E1gHsuP-0006g0-Im@usper.debian.org>

torbrowser-launcher_0.3.1-1_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.3.1-1.dsc
  torbrowser-launcher_0.3.1-1.debian.tar.xz
  torbrowser-launcher_0.3.1-1_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Wed Oct 31 16:14:13 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 31 Oct 2018 16:14:13 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.3.1-1_source.changes ACCEPTED into unstable
Message-ID: <E1gHt8H-000Hib-E4@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Thu, 01 Nov 2018 00:46:54 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.3.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.3.1-1) unstable; urgency=low
 .
   * Upload to unstable.
Checksums-Sha1:
 07c808fa943392b8895cff5a3c2aade677fda796 2174 torbrowser-launcher_0.3.1-1.dsc
 9d875a0462e301da267f052bef3299103ea2c482 11332 torbrowser-launcher_0.3.1-1.debian.tar.xz
 29060f05c4f26153725552792a04803a63785901 6237 torbrowser-launcher_0.3.1-1_source.buildinfo
Checksums-Sha256:
 06f55003043fbebb241ec77522588a7208ba7fc7f62ca5b00cfaec62679cdb5e 2174 torbrowser-launcher_0.3.1-1.dsc
 059c65f80e34532c1bf6415e8a64d3204308213641f34aacb3b671736a7e004c 11332 torbrowser-launcher_0.3.1-1.debian.tar.xz
 7fa6d065d12a4922c4b244e0a14dff108f51870924cad44ebfc4a11021d33425 6237 torbrowser-launcher_0.3.1-1_source.buildinfo
Files:
 df0170726aedfc2ed93e50586d10a764 2174 contrib/web optional torbrowser-launcher_0.3.1-1.dsc
 a65537a56cf44c14f25b5ccf09ef6592 11332 contrib/web optional torbrowser-launcher_0.3.1-1.debian.tar.xz
 b893203f6261af433f5eac3dab02d489 6237 contrib/web optional torbrowser-launcher_0.3.1-1_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAlvZz6oQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qHngEACBiii1xJ/dHKRUa1i4Ln8I4l2Z8e4RXTQA
AcqYIDSTix6hK1VyqVmy9tRDV/uWxtzqaT3IpaYE8GCEcOjRFCPqd/00AbDIB9ms
ST2z3pus9Xt1yO3P5d/qWCa0tmqtOC7vZ0zMzXJFZFe1CdVM8o8vgK9j4ATxjiCF
uWvg1NKXjqP320DcGbXC5aAa+UvfYOZbScwrpIgS2FWiLl938CS5JDsUVCR0ICXU
0hfatsqgYd/ekcUvj+/ymSTGErkIgUwkYLquULlLHZBkRfoxqalg4dN9lNZjlOtv
2aBh37OJYydD7HN1RsDDroGif0ZWhj7DBPJu4hx3rJKLnCVjLy2QgQwdOCI7no7c
5OcI423lC/NGr/eD53GhkYmN129TwCVfcEs4ecAW/rzzERMSXGOtD++AQiJouuDb
OKGnD3qBiHmYPyekRMBVcfNiqH43YE7KMAK2I90Mbuvom1SjKR1sPSX2vP3NNclP
+wCoH7OMTutH/kW8n2ZFVZw5Ad6rtWUmaMRDmPJQTmMPkVNCtSXXOM/9fAb3crOP
n3tnI+VAVL6qkd3zXx7/m7EeVTddB4hqZUb99xfFRbAy1aec54PqyfS8kfuIJ/k6
ywafSkyPwNZJXQT/3P52UMEkIiteqWI4TMuPqyhnk8G1MYA6/m3oRNncCx+aYrtk
qKJ06xJe4Q==
=T03z
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From dkg at fifthhorseman.net  Wed Oct 31 18:13:09 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Wed, 31 Oct 2018 14:13:09 -0400
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v4)
In-Reply-To: <d5d25ec6-cf19-d01f-d4fe-c2e145e4c602@debian.org>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
 <87h8hkb5yl.fsf@fifthhorseman.net> <875zy0jhwk.fsf@curie.anarc.at>
 <87bm7rc3sk.fsf@fifthhorseman.net> <20181018135227.GI19229@debian>
 <877ehz71u3.fsf@boum.org> <87bm7be0cc.fsf@fifthhorseman.net>
 <d5d25ec6-cf19-d01f-d4fe-c2e145e4c602@debian.org>
Message-ID: <87efc6c7d6.fsf@fifthhorseman.net>

On Wed 2018-10-31 14:03:00 +0000, Ulrike Uhlig wrote:
> I fear that not everyone on the member list is on the mailing list.

hm, or, they're on the mailing list and not reading it because
ETOOMUCHMAIL :/

> Also, it might actually make sense to see who of the members (that had
> been copied from Alioth) are actually active. I see at least two people
> who I believe to not really be active in this team anymore. Should I
> draft something according to point 1.3 of
> https://salsa.debian.org/pkg-privacy-team/team-processes/blob/master/pkg-privacy-process.mdwn
> ?

It would be great if you're up for driving the first iteration of that
process, Ulrike.  We don't have a specific schedule for it, but just
establishing some simple precedent would be helpful, i think.

         --dkg


From natureshadow at debian.org  Wed Oct 31 22:28:57 2018
From: natureshadow at debian.org (natureshadow at debian.org)
Date: Wed, 31 Oct 2018 23:28:57 +0100
Subject: [Pkg-privacy-maintainers] Bug#912490: torbrowser-launcher: Please
 migrate to python3-pygame
Message-ID: <20181031222859.2910F18C5A8B@shore.naturalnet.de>

Package: torbrowser-launcher
Severity: wishlist
User: python-modules-team at lists.alioth.debian.org
Usertags: python3-migration

Dear maintainer,

thanks for maintaining a pygame-based game in Debian!

As you might have heard, Python 2 will be end of life in the not so
far future. Thus, I would like to start to get the reverse
dependencies of the Python 2 version of pygame down, so this can be
done with some time and not in a hurried effort that probably makes
us loose games from Debian.

If you already know that your game will work with Python 3, please
build against and depend on python3-pygame, which has long been
available in sid and will migrate to buster shortly.

If you do not yet know whether this will work, your chances that it
will just work are still quite good, so please just give it a shot.

If you find your package does not work with Python 3 yet, you can…

a) …check what to do with upstream

b) …try to patch it (and forward your patch upstream)

c) …tag this bug report help - the next pygame-fluent kangaroo

is reserved for you!

Feel free to ask any questions if you are unsure what to do.

Cheers, Nik 


From noreply at release.debian.org  Thu Nov  1 04:39:22 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Thu, 01 Nov 2018 04:39:22 +0000
Subject: [Pkg-privacy-maintainers] txtorcon 18.0.2-2 MIGRATED to testing
Message-ID: <E1gI4lO-0000pD-7u@respighi.debian.org>

FYI: The status of the txtorcon source package
in Debian's testing distribution has changed.

  Previous version: 0.19.3-4
  Current version:  18.0.2-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From 1579548 at bugs.launchpad.net  Thu Nov  1 07:48:58 2018
From: 1579548 at bugs.launchpad.net (Mustafa)
Date: Thu, 01 Nov 2018 07:48:58 -0000
Subject: [Pkg-privacy-maintainers] [Bug 1579548] Re: OTR plugin does not
 load in Xenial
References: <20160508170515.1051.55417.malonedeb@chaenomeles.canonical.com>
Message-ID: <154105853811.24850.8433136144183522116.malone@wampee.canonical.com>

Still have the same bug. Is this going to be patched?

-- 
You received this bug notification because you are a member of Debian
Privacy Tools Maintainers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1579548

Title:
  OTR plugin does not load in Xenial

Status in irssi-plugin-otr package in Ubuntu:
  Confirmed

Bug description:
  1.0.0-1build1

  When I try to load the OTR module, Irssi says:

  -!- Irssi: Error loading module otr/core: /usr/lib/x86_64-linux-
  gnu/irssi/modules/libotr_core.so: cannot open shared object file: No
  such file or directory

  When I copy the *.so file to the named directory, Irssi says:

  -!- Irssi: otr/otr is ABI version 0 but Irssi is version 2, cannot
  load

  So this package is completly useless.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irssi-plugin-otr/+bug/1579548/+subscriptions


From owner at bugs.debian.org  Thu Nov  1 13:45:05 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 01 Nov 2018 13:45:05 +0000
Subject: [Pkg-privacy-maintainers] Processed: unarchiving 753173,
 found 753173 in 0.3.1-1
References: <1541079830-2374-bts-gregoa@debian.org>
Message-ID: <handler.s.C.154107983624879.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> unarchive 753173
Bug #753173 {Done: Holger Levsen <holger at debian.org>} [torbrowser-launcher] torbrowser-launcher: wrongly detects language
Unarchived Bug 753173
> found 753173 0.3.1-1
Bug #753173 {Done: Holger Levsen <holger at debian.org>} [torbrowser-launcher] torbrowser-launcher: wrongly detects language
Marked as found in versions torbrowser-launcher/0.3.1-1 and reopened.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
753173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753173
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From gregoa at debian.org  Thu Nov  1 13:52:11 2018
From: gregoa at debian.org (gregor herrmann)
Date: Thu, 1 Nov 2018 14:52:11 +0100
Subject: [Pkg-privacy-maintainers] Bug#753173: the locale bug is back
In-Reply-To: <20160217160808.GR11057@jadzia.comodo.priv.at>
References: <201602170939.22213.holger@layer-acht.org>
 <20160217160808.GR11057@jadzia.comodo.priv.at>
 <20140629182253.GA7207@valiant.palfrader.org>
Message-ID: <20181101135211.GA2764@jadzia.comodo.priv.at>

On Wed, 17 Feb 2016 17:08:08 +0100, gregor herrmann wrote:

> I can confirm that this works for my locale settings as well.
> Nice :)

And the bug is back with 0.3.1-1:

With this locale settings ...

% locale
LANG=
LANGUAGE=
LC_CTYPE=de_AT.utf8
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=

... the German tarball is downloaded ...

% torbrowser-launcher 
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.3.1
https://github.com/micahflee/torbrowser-launcher
Creating GnuPG homedir /home/gregoa/.local/share/torbrowser/gnupg_homedir
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/home/gregoa/tmp/runtime-gregoa'
Downloading Tor Browser for the first time.
Downloading https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US
Latest version: 8.0.3
Downloading https://dist.torproject.org/torbrowser/8.0.3/tor-browser-linux64-8.0.3_de.tar.xz.asc
Downloading https://dist.torproject.org/torbrowser/8.0.3/tor-browser-linux64-8.0.3_de.tar.xz
Verifying Signature
Extracting tor-browser-linux64-8.0.3_de.tar.xz
Running /home/gregoa/.local/share/torbrowser/tbb/x86_64/tor-browser_de/start-tor-browser.desktop
Launching './Browser/start-tor-browser --detach'...

... and the configuration dialog is in German, and torbrowser itself
as well.


And the fix seems to be the same one as last time:

#v+
--- /usr/lib/python3/dist-packages/torbrowser_launcher/common.py~	2018-10-25 19:27:46.000000000 +0200
+++ /usr/lib/python3/dist-packages/torbrowser_launcher/common.py	2018-11-01 14:48:21.363114182 +0100
@@ -73,7 +73,7 @@
 
         # figure out the language
         available_languages = ['ar', 'ca', 'da', 'de', 'en-US', 'es-ES', 'fa', 'fr', 'ga-IE', 'he', 'id', 'is', 'it', 'ja', 'ko', 'nb-NO', 'nl', 'pl', 'pt-BR', 'ru', 'sv-SE', 'tr', 'vi', 'zh-CN', 'zh-TW']
-        default_locale = locale.getlocale()[0]
+        default_locale = locale.getlocale(locale.LC_MESSAGES)[0]
         if default_locale is None:
             self.language = 'en-US'
         else:
#v-


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: The Doors: People are Strange
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181101/9a45220e/attachment.sig>

From dkg at fifthhorseman.net  Thu Nov  1 18:32:07 2018
From: dkg at fifthhorseman.net (dkg)
Date: Thu, 01 Nov 2018 18:32:07 -0000
Subject: [Pkg-privacy-maintainers] [Bug 1579548] Re: OTR plugin does not
 load in Xenial
References: <20160508170515.1051.55417.malonedeb@chaenomeles.canonical.com>
 <154105853811.24850.8433136144183522116.malone@wampee.canonical.com>
Message-ID: <87y3acmyxk.fsf@fifthhorseman.net>

note that a similar issue is fixed for the xmpp plugin in debian's
https://bugs.debian.org/772479, by a rebuild.

it will be fixed in a more prinicipled way once the irssi package
Provides: an abi-specific virtual package name. (see the discussion in
that debian bug for more details).

     --dkg

-- 
You received this bug notification because you are a member of Debian
Privacy Tools Maintainers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1579548

Title:
  OTR plugin does not load in Xenial

Status in irssi-plugin-otr package in Ubuntu:
  Confirmed

Bug description:
  1.0.0-1build1

  When I try to load the OTR module, Irssi says:

  -!- Irssi: Error loading module otr/core: /usr/lib/x86_64-linux-
  gnu/irssi/modules/libotr_core.so: cannot open shared object file: No
  such file or directory

  When I copy the *.so file to the named directory, Irssi says:

  -!- Irssi: otr/otr is ABI version 0 but Irssi is version 2, cannot
  load

  So this package is completly useless.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irssi-plugin-otr/+bug/1579548/+subscriptions


From dkg at fifthhorseman.net  Thu Nov  1 20:27:23 2018
From: dkg at fifthhorseman.net (dkg)
Date: Thu, 01 Nov 2018 20:27:23 -0000
Subject: [Pkg-privacy-maintainers] [Bug 1579548] Re: OTR plugin does not
 load in Xenial
References: <20160508170515.1051.55417.malonedeb@chaenomeles.canonical.com>
Message-ID: <154110404378.10168.2396433681899635608.launchpad@loganberry.canonical.com>

** Bug watch added: Debian Bug tracker #772479
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772479

-- 
You received this bug notification because you are a member of Debian
Privacy Tools Maintainers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1579548

Title:
  OTR plugin does not load in Xenial

Status in irssi-plugin-otr package in Ubuntu:
  Confirmed

Bug description:
  1.0.0-1build1

  When I try to load the OTR module, Irssi says:

  -!- Irssi: Error loading module otr/core: /usr/lib/x86_64-linux-
  gnu/irssi/modules/libotr_core.so: cannot open shared object file: No
  such file or directory

  When I copy the *.so file to the named directory, Irssi says:

  -!- Irssi: otr/otr is ABI version 0 but Irssi is version 2, cannot
  load

  So this package is completly useless.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irssi-plugin-otr/+bug/1579548/+subscriptions


From noreply at release.debian.org  Fri Nov  2 04:39:11 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Fri, 02 Nov 2018 04:39:11 +0000
Subject: [Pkg-privacy-maintainers] libotr 4.1.1-3 MIGRATED to testing
Message-ID: <E1gIREl-0007r7-Md@respighi.debian.org>

FYI: The status of the libotr source package
in Debian's testing distribution has changed.

  Previous version: 4.1.1-2
  Current version:  4.1.1-3

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From owner at bugs.debian.org  Fri Nov  2 15:45:06 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Fri, 02 Nov 2018 15:45:06 +0000
Subject: [Pkg-privacy-maintainers] Processed: your mail
References: <CAEQ9gEmGtS7JnpBTZNrWGAoMtWxRMyhzaLnTvVCGFhvCDHtidw@mail.gmail.com>
Message-ID: <handler.s.C.154117333622093.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> fixed 908068 0.3.0~dev-1~exp4
Bug #908068 {Done: Roger Shimizu <rosh at debian.org>} [torbrowser-launcher] torbrowser-launcher fails with torbrowser 8.0
Marked as fixed in versions torbrowser-launcher/0.3.0~dev-1~exp4.
> fixed 908463 0.3.0~dev-1~exp4
Bug #908463 {Done: Roger Shimizu <rosh at debian.org>} [torbrowser-launcher] torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy
Marked as fixed in versions torbrowser-launcher/0.3.0~dev-1~exp4.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
908068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908068
908463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908463
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From georg at riseup.net  Fri Nov  2 16:20:39 2018
From: georg at riseup.net (Georg Faerber)
Date: Fri, 2 Nov 2018 16:20:39 +0000
Subject: [Pkg-privacy-maintainers] process update proposal: new
 membership process clarification (v4)
In-Reply-To: <87bm7be0cc.fsf@fifthhorseman.net>
References: <87o9bsbjhx.fsf@fifthhorseman.net> <20181017184423.GG19229@debian>
 <87k1mgbcze.fsf@fifthhorseman.net> <20181017192644.GH19229@debian>
 <87h8hkb5yl.fsf@fifthhorseman.net> <875zy0jhwk.fsf@curie.anarc.at>
 <87bm7rc3sk.fsf@fifthhorseman.net> <20181018135227.GI19229@debian>
 <877ehz71u3.fsf@boum.org> <87bm7be0cc.fsf@fifthhorseman.net>
Message-ID: <20181102162039.GB21875@debian>

On 18-10-30 14:49:39, Daniel Kahn Gillmor wrote:
> so, barring objections in the next couple of days, this looks like it
> will be approved and adopted by the group.  If you have a problem with
> it, please speak up!

I've merged and pushed to master, hope that's okay with everyone.

Cheers,
Georg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181102/d731e5cb/attachment.sig>

From weasel at debian.org  Sat Nov  3 08:51:11 2018
From: weasel at debian.org (Peter Palfrader)
Date: Sat, 3 Nov 2018 08:51:11 +0000
Subject: [Pkg-privacy-maintainers] Bug#912719: fails open if it cannot parse
 -a
Message-ID: <20181103085111.g67kuuw2yshzs46e@sarek.noreply.org>

Package: torsocks
Version: 2.2.0-1+deb9u1

torsocks fails open if it cannot parse the -a argument.

| weasel at orinoco:~/test$ torsocks -a "foo" curl -L -s https://deb.debian.org/debian/dists/stable/Release  | grep Origin
| 1541235000 ERROR torsocks[4883]: Config file unknown tor address: foo (in conf_file_set_tor_address() at config-file.c:281)
| Origin: Debian

Since torsocks could not parse -a, it just used the tor on 127.0.0.1:9050.  I
would expect it to fail closed instead.

-- 
                            |  .''`.       ** Debian **
      Peter Palfrader       | : :' :      The  universal
 https://www.palfrader.org/ | `. `'      Operating System
                            |   `-    https://www.debian.org/


From intrigeri at debian.org  Sun Nov  4 08:58:16 2018
From: intrigeri at debian.org (intrigeri)
Date: Sun, 04 Nov 2018 09:58:16 +0100
Subject: [Pkg-privacy-maintainers] Bug#912719: fails open if it cannot parse
 -a
In-Reply-To: <20181103085111.g67kuuw2yshzs46e@sarek.noreply.org>
References: <20181103085111.g67kuuw2yshzs46e@sarek.noreply.org>
 <20181103085111.g67kuuw2yshzs46e@sarek.noreply.org>
Message-ID: <871s81p6c7.fsf@boum.org>

Control: found -1 2.2.0-2

Ouch :/ Reproduced on sid. I see a few potentially related changes in
upstream Git, might be worth trying to import them and see what happens.

Cheers,
-- 
intrigeri


From owner at bugs.debian.org  Sun Nov  4 09:03:04 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sun, 04 Nov 2018 09:03:04 +0000
Subject: [Pkg-privacy-maintainers] Processed: Re: Bug#912719: fails open if
 it cannot parse -a
References: <871s81p6c7.fsf@boum.org>
 <20181103085111.g67kuuw2yshzs46e@sarek.noreply.org>
Message-ID: <handler.s.B912719.15413219089705.transcript@bugs.debian.org>

Processing control commands:

> found -1 2.2.0-2
Bug #912719 [torsocks] fails open if it cannot parse -a
Marked as found in versions torsocks/2.2.0-2.

-- 
912719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912719
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ftpmaster at ftp-master.debian.org  Sun Nov  4 17:13:52 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 04 Nov 2018 17:13:52 +0000
Subject: [Pkg-privacy-maintainers] Bug#911272: Removed package(s) from
 unstable
Message-ID: <E1gJLyC-000CLU-68@fasolo.debian.org>

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-txtorcon |   18.0.2-1 | all

------------------- Reason -------------------
NBS; decruft
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 911272 at bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/911272

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)


From debian-bts-link at lists.debian.org  Mon Nov  5 17:13:58 2018
From: debian-bts-link at lists.debian.org (debian-bts-link at lists.debian.org)
Date: Mon, 05 Nov 2018 17:13:58 +0000
Subject: [Pkg-privacy-maintainers] [bts-link] source package
 torbrowser-launcher
Message-ID: <154143803800.8658.4728395728049125888.btslink@sonntag.debian.org>

#
# bts-link upstream status pull for source package torbrowser-launcher
# see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
#     https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-link at lists.debian.org

# remote status report for #753173 (http://bugs.debian.org/753173)
# Bug title: torbrowser-launcher: wrongly detects language
#  * https://github.com/micahflee/torbrowser-launcher/issues/220
#  * remote status changed: (?) -> closed
usertags 753173 + status-closed

thanks


From noreply at release.debian.org  Tue Nov  6 04:39:24 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Tue, 06 Nov 2018 04:39:24 +0000
Subject: [Pkg-privacy-maintainers] torbrowser-launcher 0.3.1-1 MIGRATED to
 testing
Message-ID: <E1gJt9A-0000ig-0j@respighi.debian.org>

FYI: The status of the torbrowser-launcher source package
in Debian's testing distribution has changed.

  Previous version: 0.2.9-6
  Current version:  0.3.1-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From ftpmaster at ftp-master.debian.org  Tue Nov  6 13:56:17 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 06 Nov 2018 13:56:17 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.3.1-1~bpo9+1_source.changes
Message-ID: <E1gK1q5-0005db-RI@usper.debian.org>

torbrowser-launcher_0.3.1-1~bpo9+1_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.3.1-1~bpo9+1.dsc
  torbrowser-launcher_0.3.1-1~bpo9+1.debian.tar.xz
  torbrowser-launcher_0.3.1-1~bpo9+1_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Tue Nov  6 15:12:17 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 06 Nov 2018 15:12:17 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.3.1-1~bpo9+1_source.changes ACCEPTED into
 stretch-backports
Message-ID: <E1gK31d-000C7E-7b@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Tue, 06 Nov 2018 22:31:07 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.3.1-1~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.3.1-1~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
Checksums-Sha1:
 20280712ae8e518a70c9d597afe5590fcef78656 2202 torbrowser-launcher_0.3.1-1~bpo9+1.dsc
 6b3fa42dd2e0fbe2e10b8631bdf2468e07174779 11460 torbrowser-launcher_0.3.1-1~bpo9+1.debian.tar.xz
 c2dc033b7437b5d827460845c654b7fa0a737fcd 6265 torbrowser-launcher_0.3.1-1~bpo9+1_source.buildinfo
Checksums-Sha256:
 80d0390b3644b76549ef04af2a766bef3903ef9865dee9f39f28897b44d71ff3 2202 torbrowser-launcher_0.3.1-1~bpo9+1.dsc
 ecf0ecd258f8f1fbf11fb2ff6f9cc28747f05e7fd0545e62cb8cccef60f273c5 11460 torbrowser-launcher_0.3.1-1~bpo9+1.debian.tar.xz
 eb5832beb9606e4ca8f5a4cfcb8480f228217cdbc439c580efba1cbd237cb34c 6265 torbrowser-launcher_0.3.1-1~bpo9+1_source.buildinfo
Files:
 a0f1d1809e9c39a6a7f1834a6c75cbde 2202 contrib/web optional torbrowser-launcher_0.3.1-1~bpo9+1.dsc
 bcd6a041c08848a612a9f703b6e1ce3b 11460 contrib/web optional torbrowser-launcher_0.3.1-1~bpo9+1.debian.tar.xz
 ccead9020405560517a3595eaa4cbd2e 6265 contrib/web optional torbrowser-launcher_0.3.1-1~bpo9+1_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAlvhmpAQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qM6LD/4vzw8SzS6M6EPHGKFK0BPKX00KHPSad2aq
s8Igs52b9F3RCUgL1t8KgGSKe3v/Vhbchf517TiVWyKjqSeQWrfoauLsnKVoDxLz
Y6KwkScmPEZDOBJ9KWUaPdGo5BEq/1ulsphhGWPtW7LZkhOS4eKEG5SvPpKsBSaY
wUw111ytyVM7wdO5kSk2FJ/UgXVxf9VQpo4mhpCMTsGBLGfLP7DSYRLKKOhZh4/Y
6P51B14NQsuuqjSJfHw1FeAth+itcwSlKtQSHLdZGJkFLLI+EYyfIPZJ9Vojfpg9
Jpgz9tHaFOA5e026unsLmS7fZeSimh5uRJZJHn82Z+HfAXEJ+pzILf3VxkIMATV6
bLFldQ2na6dDMxqiRo0p2L9LMwrmD1MTr8FgIR/oCpAN++OuHNtMLVTR0pjf0RjD
CyzuKie9X569JysSDYngwa6N2f9qpIdoyV4uame+4Bj+2Q0YHlYCrJqECmcdtzUC
mFfNx03WJLM2t/A+1h4M+jmz5tNZim0lCXPkDBUMqbBOpVsZnoxUteElaEZ9vEGt
GbFdS5ozlQ0/GStPFOQRQ0q6c3BViR0oOjsTKDIJJigxTNPLPLO+JstJIN1Yq8Qy
uQrTNYKeiH7uaYZZYEANU1KpcJFjMv09Wsi/QTLNHWN81EBKBbhvmzloRFxAR1PR
Z9fxMIUByw==
=UCH9
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From ftpmaster at ftp-master.debian.org  Tue Nov  6 15:27:12 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 06 Nov 2018 15:27:12 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.3.1-1~bpo8+1_amd64.changes
Message-ID: <E1gK3G4-0002E0-8o@usper.debian.org>

torbrowser-launcher_0.3.1-1~bpo8+1_amd64.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.3.1-1~bpo8+1.dsc
  torbrowser-launcher_0.3.1-1~bpo8+1.debian.tar.xz
  torbrowser-launcher_0.3.1-1~bpo8+1_amd64.deb

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Tue Nov  6 15:37:58 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 06 Nov 2018 15:37:58 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.3.1-1~bpo8+1_amd64.changes ACCEPTED into
 jessie-backports-sloppy
Message-ID: <E1gK3QU-000FZr-7i@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Tue, 06 Nov 2018 22:35:54 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source amd64
Version: 0.3.1-1~bpo8+1
Distribution: jessie-backports-sloppy
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.3.1-1~bpo8+1) jessie-backports-sloppy; urgency=medium
 .
   * Rebuild for jessie-backports-sloppy.
Checksums-Sha1:
 452a2aa87568bc97d95d2bd2e39743a93061b555 2202 torbrowser-launcher_0.3.1-1~bpo8+1.dsc
 e33f240052e6231a997cf67d6a6387c1c8623efd 11484 torbrowser-launcher_0.3.1-1~bpo8+1.debian.tar.xz
 852d293ed0fa52190946a00b778f2706c4f11646 65666 torbrowser-launcher_0.3.1-1~bpo8+1_amd64.deb
Checksums-Sha256:
 44c9d4ad49f0ec875503ed20d09806254b3c6afd6810c235748fbf28b5aa6318 2202 torbrowser-launcher_0.3.1-1~bpo8+1.dsc
 e2b2274909cc43de33afcd77c7ed821050a522234294e5f69708db8b1169b3ad 11484 torbrowser-launcher_0.3.1-1~bpo8+1.debian.tar.xz
 627911021954b7b9fe601c1faefae26365c02957b4dc5ee034f4c72ba2b6574f 65666 torbrowser-launcher_0.3.1-1~bpo8+1_amd64.deb
Files:
 7be0b9790895cab9fefd559b0d54ed9e 2202 contrib/web optional torbrowser-launcher_0.3.1-1~bpo8+1.dsc
 28ec8bafb8c78e4a6abbfe775bf27159 11484 contrib/web optional torbrowser-launcher_0.3.1-1~bpo8+1.debian.tar.xz
 70b1750c8ca43ba2abb913dc8b8a43fb 65666 contrib/web optional torbrowser-launcher_0.3.1-1~bpo8+1_amd64.deb

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAlvhr9YQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qCWwD/9Bdz+ErxLN9JsS6QQ7tzfyXUkaNzbl1ATg
fVInzIlAgG4mpooKrA+3Nw3G3U3e0d9InCfKlYGeDWCiIPFerE178+QXCKjxkXn1
qlNYnvbOAtsAlFS4Rl0Y0C97hLdkeAqf6VSkN2Y+5PvXSJBISDRq4FL8IM6JRHyu
vp8KXV9L6FMww3GNe9kK39EJZDvqaQdujlRFMK3Pv4bikfIeWS3/PI/V/bvPqYsT
NlIq6AVeOpXcoXtKZpw+jHYhAYi5/kNaU1RLyNDTMqyux8GoNpiWuQR2siL1anS+
v4jewHzic7gKVDljw8mFN/PXxBVfimIzsZhRrH2rEJxUHYBmv6SmBzr3xfdMQOy1
JjURz4h0NLL4MlpFdyMfHLY3qoWVZAHu71wshABhlVyRH5JG5/hTkELUPvAqcimK
Ouo3o++iXmcHIZsX9XzYK3T2gNP8qA+a4wcQGNkRpolw2cugGF5I0MuXZrxUD4NI
TiZtMU+yPlWWC4x3viqpHWG52EWMD+vBe3Kk78ivSEKKkMDlknEfFAV3S0EqO6eq
QzpbwCRk5gFUB3yc03q6CfktQOFyOODI8t0hvAFDsW2fwjOC5Aj2L8ZXbX/E28W2
TqM9kA+JKYsiv6S8+DyDx+c3RmgFc3rTPOLOKmRtsbWy0NwI36dyvek1e6RspuRX
9WqrebdmzA==
=W25V
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From pabs at debian.org  Tue Nov  6 23:10:58 2018
From: pabs at debian.org (Paul Wise)
Date: Wed, 07 Nov 2018 07:10:58 +0800
Subject: [Pkg-privacy-maintainers] Bug#913104: torbrowser-launcher: apparmor
 denials: lsb_release, fontconfig conf.avail, gtk-3.0 settings.ini
Message-ID: <d134a403ca7a7f32fd7b8d9858833ca24dd34141.camel@debian.org>

Package: torbrowser-launcher
Version: 0.3.1-1
Severity: minor
Usertags: apparmor
File: /etc/apparmor.d/torbrowser.Browser.firefox
File: /etc/apparmor.d/torbrowser.Browser.plugin-container

I noticed some apparmor denials when I start Tor Browser, they do not
seem to have any effect but I wonder if they should be allowed.

AVC apparmor="DENIED" operation="exec" profile="torbrowser_firefox" name="/usr/bin/lsb_release" pid=20472 comm="firefox.real" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
AVC apparmor="DENIED" operation="open" profile="torbrowser_firefox" name="/usr/share/fontconfig/conf.avail/" pid=20184 comm="firefox.real" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
AVC apparmor="DENIED" operation="open" profile="torbrowser_plugin_container" name="/home/pabs/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/.config/gtk-3.0/settings.ini" pid=20839 comm="firefox.real" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
AVC apparmor="DENIED" operation="open" profile="torbrowser_plugin_container" name="/usr/share/fontconfig/conf.avail/" pid=20839 comm=57656220436F6E74656E74 requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
AVC apparmor="DENIED" operation="open" profile="torbrowser_plugin_container" name="/home/pabs/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/.config/gtk-3.0/settings.ini" pid=20922 comm="firefox.real" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
AVC apparmor="DENIED" operation="open" profile="torbrowser_plugin_container" name="/usr/share/fontconfig/conf.avail/" pid=20922 comm=57656220436F6E74656E74 requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  libdbus-glib-1-2  0.110-3
ii  python3           3.6.7-1
ii  python3-gpg       1.12.0-4
ii  python3-pyqt5     5.11.3+dfsg-1+b1
ii  python3-requests  2.20.0-2
ii  python3-socks     1.6.8+dfsg-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.4.8-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.13.1-3+b1
ii  python-pygame  1.9.1release+dfsg-10+b2

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181107/85e1ce4a/attachment.sig>

From ftpmaster at ftp-master.debian.org  Wed Nov  7 11:56:45 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 07 Nov 2018 11:56:45 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 tails-installer_5.0.12+dfsg-1~bpo9+1_amd64.changes
Message-ID: <E1gKMRy-0004Sf-0B@usper.debian.org>

tails-installer_5.0.12+dfsg-1~bpo9+1_amd64.changes uploaded successfully to localhost
along with the files:
  tails-installer_5.0.12+dfsg-1~bpo9+1.dsc
  tails-installer_5.0.12+dfsg-1~bpo9+1.debian.tar.xz
  tails-installer_5.0.12+dfsg-1~bpo9+1_amd64.buildinfo
  tails-installer_5.0.12+dfsg-1~bpo9+1_amd64.deb
  tails-installer_5.0.12+dfsg.orig.tar.gz

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Wed Nov  7 12:05:26 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 07 Nov 2018 12:05:26 +0000
Subject: [Pkg-privacy-maintainers]
 tails-installer_5.0.12+dfsg-1~bpo9+1_amd64.changes ACCEPTED into
 stretch-backports
Message-ID: <E1gKMaM-0009Qn-9X@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Wed,  7 Nov 2018 12:48:59 CET
Source: tails-installer
Binary: tails-installer
Architecture: source amd64
Version: 5.0.12+dfsg-1~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Ulrike Uhlig <ulrike at debian.org>
Description:
 tails-installer - Installer for the Tails live operating system
Changes:
 tails-installer (5.0.12+dfsg-1~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
Checksums-Sha256: 
 a032e27b91c7dc469071a15e5b084a1225203d66bba2021d19d26dd14670701c 2199 tails-installer_5.0.12+dfsg-1~bpo9+1.dsc
 d3dc02785df929d541b0593bf8c4fc1d181d45c079decf24788af9204ba2640e 15732 tails-installer_5.0.12+dfsg-1~bpo9+1.debian.tar.xz
 7e28b036106fc3487963f8d9c1285f5cecb7e8c20b47cd62911042432182fb81 7399 tails-installer_5.0.12+dfsg-1~bpo9+1_amd64.buildinfo
 e8ec05446bdb42f31c88c407dbdfaeaf0f961c1f702a7fdafcea9cb9ff32e3b7 199402 tails-installer_5.0.12+dfsg-1~bpo9+1_amd64.deb
 feb5293809be0c578fa550e9fb4926e5c1d0f53c9dc3230ad0e002de1089e9c7 330189 tails-installer_5.0.12+dfsg.orig.tar.gz
Checksums-Sha1: 
 c3bb6cea1f2ed4d872b76cbbad8d503f549b30d8 2199 tails-installer_5.0.12+dfsg-1~bpo9+1.dsc
 52b30d6732b36eec2cfed6829c8dc8cab10b4431 15732 tails-installer_5.0.12+dfsg-1~bpo9+1.debian.tar.xz
 d1c8cb73ca08d994fedb1e09a3aab2846b3f7573 7399 tails-installer_5.0.12+dfsg-1~bpo9+1_amd64.buildinfo
 29702a0784813e1abfa4a57224a6aad7bfa102c1 199402 tails-installer_5.0.12+dfsg-1~bpo9+1_amd64.deb
 272a1b617430cd47204e041ead800e81c5168e1c 330189 tails-installer_5.0.12+dfsg.orig.tar.gz
Files: 
 64f2d50d70b5db4b22afdb81416cc054 2199 python optional tails-installer_5.0.12+dfsg-1~bpo9+1.dsc
 ce0aa3d347c91b7c2ad5aa662d574c3f 15732 python optional tails-installer_5.0.12+dfsg-1~bpo9+1.debian.tar.xz
 53b335ae30376fe7d112639600d8f538 7399 python optional tails-installer_5.0.12+dfsg-1~bpo9+1_amd64.buildinfo
 9caec020c0f01814d1e212b217284b4b 199402 python optional tails-installer_5.0.12+dfsg-1~bpo9+1_amd64.deb
 d374d6e81b0263b77da9e888cc49f30e 330189 python optional tails-installer_5.0.12+dfsg.orig.tar.gz

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

iQJGBAEBCgAwFiEE7eP0RD800mGVFNeQsUuww42GHPEFAlvi0TMSHHVscmlrZUBk
ZWJpYW4ub3JnAAoJELFLsMONhhzxhBUQAITKhBEtFENHoZcx71QsNJuBEzFda1Qu
hz3OQYCWcNAB0SdWXkOO7uvwaPhgsPVWxlDtv+jJBojsf/GxwQFjpTqNVWUXh9AG
mG8g33+XqBYhaFP5K619EpetxaPszVh7iOYBmMsnXA40zRk8UuPhpIP4NsR05YrI
ur1crKDHAxKyCQfD2BteM14C94DET49NV8VbxMf3dERoH+KcaZkYCC8C8gEDVaC6
SRHy3uzJwbYoESiKXUCcnn4poMJPX+Wh5/vK4rEVb5g1pFOJ1gEqM8Jj5HhtZpcx
wzlwHe8i7EE6cHlfb1tMu2XUB+aqUE6NAgGQk6zGgu3+kja2WGrSFbzZJ0RK+64r
Kciy9XYFUZwdEsHBniIbAuBeJ9KQgY+gWTyV5riIW7jgwo+qzxmhQHczv5dHIvSm
8CH3a+aCQHb7wmj01mF7m/yTsuo6WcKNmVhboHSGhNcp7gdakBO9AIrCkRy+Gc6Q
d6uC9qbzFCe1ixa40zqo4+WdpWX/P4MzS7cM3M6D7HXjyANF8iVyPEiOFKzupO8C
q2yoKcnI68Lpd9+0TOkRbbjRMSwjFYTdAwvXKJ/vb5myC+J5yd+lUzrDEqDUir18
kgWWUmAQOVLb+TTCBfyjCA3G+JWdZ+npztvIk908N6XT3/8CoO/xlvzivHIkWH8o
GA52cmAKaNO8
=BTsg
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From pabs at debian.org  Wed Nov  7 15:59:47 2018
From: pabs at debian.org (Paul Wise)
Date: Wed, 07 Nov 2018 23:59:47 +0800
Subject: [Pkg-privacy-maintainers] Bug#913151: torbrowser-launcher: modem
 sound was removed, python-pygame is unused,
 drop both from suggests/appdata.xml
Message-ID: <350aada78a71d996f6bf2f467b2993594b3d0356.camel@debian.org>

Package: torbrowser-launcher
Version: 0.3.1-1
Severity: minor

torbrowser-launcher removed the modem sound so the python-pygame
suggests is no longer needed, please remove it and remove mention of
the modem sound from the torbrowser.appdata.xml file. Please note that
bug #912490 about switching to python3-pygame should be closed too.

$ dpkg -L torbrowser-launcher | xargs zgrep -E 'modem|game' 2> /dev/null
/usr/share/doc/torbrowser-launcher/changelog.Debian.gz:    - Removed modem sound
/usr/share/doc/torbrowser-launcher/changelog.Debian.gz:    - Remove modem sound
/usr/share/doc/torbrowser-launcher/changelog.Debian.gz:        * python-pygame dependency is now optional
/usr/share/doc/torbrowser-launcher/changelog.gz:* Removed modem sound
/usr/share/doc/torbrowser-launcher/changelog.gz:* Modem sound and python-pygame dependency is now optional
/usr/share/doc/torbrowser-launcher/changelog.gz:* Made optional modem sound when launching Tor, because it's sooo slow :)
/usr/share/metainfo/torbrowser.appdata.xml:   <li>Optionally playing a modem sound when you open Tor Browser (because Tor is so slow)</li>

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  libdbus-glib-1-2  0.110-3
ii  python3           3.6.7-1
ii  python3-gpg       1.12.0-4
ii  python3-pyqt5     5.11.3+dfsg-1+b1
ii  python3-requests  2.20.0-2
ii  python3-socks     1.6.8+dfsg-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.4.8-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.13.1-3+b1
ii  python-pygame  1.9.4.post1+dfsg-2

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181107/8f6a58d1/attachment.sig>

From didi.debian at cknow.org  Sat Nov 10 00:42:23 2018
From: didi.debian at cknow.org (Diederik de Haas)
Date: Sat, 10 Nov 2018 01:42:23 +0100
Subject: [Pkg-privacy-maintainers] Bug#913366: torbrowser-launcher: more
 apparmor fixes needed, otherwise fails to launch
Message-ID: <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>

Package: torbrowser-launcher
Version: 0.3.1-1
Severity: grave
Tags: upstream patch
Justification: renders package unusable

I had applied the patch before, but I guess it got overwritten with a
new version (which I thought wasn't supposed to happen without asking).
Applied the patch again and then torbrowser started again.

For completeness sake, this is the patch intrigeri submitted upstream,
but the upstream pull request is now already waiting more then a month
for approval/merge, so it's probably good to apply this patch to the
Debian package in the meantime.

  owner @{torbrowser_home_dir}/TorBrowser/Data/Browser/profile.default/extensions/*.xpi r,
+ owner @{torbrowser_home_dir}/TorBrowser/Data/Browser/profiles.ini r,
+ owner @{torbrowser_home_dir}/TorBrowser/UpdateInfo/updates/[0-9]*/update.{status,version} r,
+ owner @{torbrowser_home_dir}/TorBrowser/UpdateInfo/updates/[0-9]/updater rw,
  owner @{torbrowser_home_dir}/TorBrowser/Data/Browser/profile.default/startupCache/* r,

Cheers,
  Diederik

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20180409
ii  libdbus-glib-1-2  0.110-3
ii  python3           3.6.7-1
ii  python3-gpg       1.12.0-4
ii  python3-pyqt5     5.11.3+dfsg-1+b1
ii  python3-requests  2.20.0-2
ii  python3-socks     1.6.8+dfsg-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.4.9-5

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.13.1-3+b1
ii  python-pygame  1.9.4.post1+dfsg-2

-- Configuration Files:
/etc/apparmor.d/torbrowser.Browser.plugin-container changed:
@{torbrowser_firefox_executable} = /home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox.real
profile torbrowser_plugin_container {
  #include <abstractions/gnome>
  # Uncomment the following lines if you want Tor Browser
  # to have direct access to your sound hardware. You will also
  # need to remove, further bellow:
  #  - the "deny" word in the machine-id lines
  #  - the rules that deny reading /etc/pulse/client.conf
  #    and executing /usr/bin/pulseaudio
  # #include <abstractions/audio>
  # /etc/asound.conf r,
  # owner @{torbrowser_home_dir}/TorBrowser/Data/Browser/profile.default/tmp/mozilla-temp-* rw,
  signal (receive) set=("term") peer=torbrowser_firefox,
  deny /etc/host.conf r,
  deny /etc/hosts r,
  deny /etc/nsswitch.conf r,
  deny /etc/resolv.conf r,
  deny /etc/passwd r,
  deny /etc/group r,
  deny /etc/mailcap r,
  deny /etc/machine-id r,
  deny /var/lib/dbus/machine-id r,
  /etc/mime.types r,
  /usr/share/applications/gnome-mimeapps.list r,
  /dev/shm/ r,
  owner @{PROC}/@{pid}/environ r,
  owner @{PROC}/@{pid}/fd/ r,
  owner @{PROC}/@{pid}/mountinfo r,
  owner @{PROC}/@{pid}/stat r,
  owner @{PROC}/@{pid}/status r,
  owner @{PROC}/@{pid}/task/*/stat r,
  @{PROC}/sys/kernel/random/uuid r,
  owner @{torbrowser_home_dir}/*.dat r,
  owner @{torbrowser_home_dir}/*.manifest r,
  owner @{torbrowser_home_dir}/*.so mr,
  owner @{torbrowser_home_dir}/.cache/fontconfig/   rw,
  owner @{torbrowser_home_dir}/.cache/fontconfig/** rw,
  owner @{torbrowser_home_dir}/browser/** r,
  owner @{torbrowser_home_dir}/components/*.so mr,
  owner @{torbrowser_home_dir}/browser/components/*.so mr,
  owner @{torbrowser_home_dir}/defaults/pref/     r,
  owner @{torbrowser_home_dir}/defaults/pref/*.js r,
  owner @{torbrowser_home_dir}/dependentlibs.list r,
  owner @{torbrowser_home_dir}/fonts/   r,
  owner @{torbrowser_home_dir}/fonts/** r,
  owner @{torbrowser_home_dir}/omni.ja r,
  owner @{torbrowser_home_dir}/TorBrowser/Data/Browser/profile.default/extensions/*.xpi r,
  owner @{torbrowser_home_dir}/TorBrowser/Data/Browser/profiles.ini r,
  owner @{torbrowser_home_dir}/TorBrowser/UpdateInfo/updates/[0-9]*/update.{status,version} r,
  owner @{torbrowser_home_dir}/TorBrowser/UpdateInfo/updates/[0-9]*/updater rw,
  owner @{torbrowser_home_dir}/TorBrowser/Data/Browser/profile.default/startupCache/* r,
  owner @{torbrowser_home_dir}/TorBrowser/Data/Browser/profile.default/tmp/* rw,
  owner @{torbrowser_home_dir}/TorBrowser/Data/fontconfig/fonts.conf r,
  owner @{torbrowser_home_dir}/TorBrowser/Tor/ r,
  owner @{torbrowser_home_dir}/TorBrowser/Tor/*.so mr,
  owner @{torbrowser_home_dir}/TorBrowser/Tor/*.so.* mr,
  owner @{torbrowser_home_dir}/Downloads/ rwk,
  owner @{torbrowser_home_dir}/Downloads/** rwk,
  owner @{torbrowser_firefox_executable} ixmr -> torbrowser_plugin_container,
  /sys/devices/system/cpu/ r,
  /sys/devices/system/cpu/present r,
  /sys/devices/system/node/ r,
  /sys/devices/system/node/node[0-9]*/meminfo r,
  deny /sys/devices/virtual/block/*/uevent r,
  # Should use abstractions/gstreamer instead once merged upstream
  /etc/udev/udev.conf r,
  /run/udev/data/+pci:* r,
  /sys/devices/pci[0-9]*/**/uevent r,
  owner /{dev,run}/shm/shmfd-* rw,
  # Required for multiprocess Firefox (aka Electrolysis, i.e. e10s)
  owner /{dev,run}/shm/org.chromium.* rw,
  # Deny access to DRM nodes, that's granted by the X abstraction, which is
  # sourced by the gnome abstraction, that we include.
  deny /dev/dri/** rwklx,
  # Silence denial logs about permissions we don't need
  deny /dev/dri/   rwklx,
  deny @{PROC}/@{pid}/net/route r,
  deny /sys/devices/system/cpu/cpufreq/policy[0-9]*/cpuinfo_max_freq r,
  deny /sys/devices/system/cpu/*/cache/index[0-9]*/size r,
  # Silence denial logs about PulseAudio
  deny /etc/pulse/client.conf r,
  deny /usr/bin/pulseaudio x,
  #include <local/torbrowser.Browser.plugin-container>
}


-- no debconf information


From owner at bugs.debian.org  Sat Nov 10 01:39:03 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 10 Nov 2018 01:39:03 +0000
Subject: [Pkg-privacy-maintainers] Processed: Re: Bug#913366:
 Acknowledgement (torbrowser-launcher: more apparmor fixes needed,
 otherwise fails to launch)
References: <2508264.EhUU4kZMXY@bagend>
 <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>
Message-ID: <handler.s.B913366.154181373919165.transcript@bugs.debian.org>

Processing control commands:

> forwarded -1 https://github.com/micahflee/torbrowser-launcher/pull/
Bug #913366 [torbrowser-launcher] torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
Set Bug forwarded-to-address to 'https://github.com/micahflee/torbrowser-launcher/pull/'.

-- 
913366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913366
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From didi.debian at cknow.org  Sat Nov 10 01:29:10 2018
From: didi.debian at cknow.org (Diederik de Haas)
Date: Sat, 10 Nov 2018 02:29:10 +0100
Subject: [Pkg-privacy-maintainers] Bug#913366: Acknowledgement
 (torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch)
In-Reply-To: <handler.913366.B.15418111064847.ack@bugs.debian.org>
References: <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>
 <handler.913366.B.15418111064847.ack@bugs.debian.org>
 <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>
Message-ID: <2508264.EhUU4kZMXY@bagend>

Control: forwarded -1 https://github.com/micahflee/torbrowser-launcher/pull/
360
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181110/28e20871/attachment.sig>

From didi.debian at cknow.org  Sat Nov 10 01:41:52 2018
From: didi.debian at cknow.org (Diederik de Haas)
Date: Sat, 10 Nov 2018 02:41:52 +0100
Subject: [Pkg-privacy-maintainers] Bug#913366: Now properly setting
 forwarded address
In-Reply-To: <2508264.EhUU4kZMXY@bagend>
References: <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>
 <handler.913366.B.15418111064847.ack@bugs.debian.org>
 <2508264.EhUU4kZMXY@bagend>
 <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>
Message-ID: <2186104.oSjUA9jnoT@bagend>

Control: forwarded -1 https://github.com/micahflee/torbrowser-launcher/pull/360

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181110/affe06bf/attachment-0001.sig>

From owner at bugs.debian.org  Sat Nov 10 01:45:04 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 10 Nov 2018 01:45:04 +0000
Subject: [Pkg-privacy-maintainers] Processed: Re: Bug#913366: Now properly
 setting forwarded address
References: <2186104.oSjUA9jnoT@bagend>
 <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>
Message-ID: <handler.s.B913366.154181411821614.transcript@bugs.debian.org>

Processing control commands:

> forwarded -1 https://github.com/micahflee/torbrowser-launcher/pull/360
Bug #913366 [torbrowser-launcher] torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
Changed Bug forwarded-to-address to 'https://github.com/micahflee/torbrowser-launcher/pull/360' from 'https://github.com/micahflee/torbrowser-launcher/pull/'.

-- 
913366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913366
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ftpmaster at ftp-master.debian.org  Sat Nov 10 13:54:57 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 10 Nov 2018 13:54:57 +0000
Subject: [Pkg-privacy-maintainers] Processing of mat2_0.6.0-1_source.changes
Message-ID: <E1gLTiz-0007K8-3E@usper.debian.org>

mat2_0.6.0-1_source.changes uploaded successfully to localhost
along with the files:
  mat2_0.6.0-1.dsc
  mat2_0.6.0.orig.tar.xz
  mat2_0.6.0.orig.tar.xz.asc
  mat2_0.6.0-1.debian.tar.xz
  mat2_0.6.0-1_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sat Nov 10 15:55:10 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 10 Nov 2018 15:55:10 +0000
Subject: [Pkg-privacy-maintainers] mat2_0.6.0-1_source.changes ACCEPTED into
 unstable
Message-ID: <E1gLVbK-0005ai-AR@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sat, 10 Nov 2018 13:33:52 +0000
Source: mat2
Binary: mat2
Architecture: source
Version: 0.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Georg Faerber <georg at riseup.net>
Description:
 mat2       - Metadata anonymisation toolkit v2
Changes:
 mat2 (0.6.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * d/control:
     - Add debhelper-compat as build dependency.
     - Declare that the build doesn't need root privileges.
     - Mention '.mp4' support in description.
   * d/compat:
     - Drop obsolete compat control file.
   * d/gitlab-ci.yml:
     - Drop custom config, rely on the "Salsa CI Team".
   * d/u/signing-key.asc:
     - Use clean and minimal key to remove cruft. Thanks, lintian.
   * d/watch:
     - Use '@ARCHIVE_EXT@' substitution.
     - Relax archive name regex, due to inconsistent upstream naming scheme.
Checksums-Sha1:
 95e658f522b63ac4498794c11c19b675a271f79b 2410 mat2_0.6.0-1.dsc
 bfb434a5d68999c682565e039edc84201d3d3bf1 3740396 mat2_0.6.0.orig.tar.xz
 79c2e2940a93eb37dc8b3326f94cdf38661d4eed 833 mat2_0.6.0.orig.tar.xz.asc
 62021f07ef4c6c4cc0e837f94fda8721969fd9e5 7060 mat2_0.6.0-1.debian.tar.xz
 bb5807606d46bed0c5eca6c342c4d3a9de972ae6 11733 mat2_0.6.0-1_amd64.buildinfo
Checksums-Sha256:
 7b56ea26eeb92e1003dc8f6f1336a08c453e9516d2163cd5cdc7bfe03164b732 2410 mat2_0.6.0-1.dsc
 96c55c455a5d556bed41487476ae98866ebe8e7ef01a75325c9e274c7e1ce842 3740396 mat2_0.6.0.orig.tar.xz
 01228c8eaeef1ee167c5712be6cd16664de0f05ddcd0a8cd7d8c3c7ca0fdab0a 833 mat2_0.6.0.orig.tar.xz.asc
 ab7cc863af53d73395188ed6075a754f3a90ccd5e0346c0267e36046ec5eb62b 7060 mat2_0.6.0-1.debian.tar.xz
 5746c7e291e2f6a0580e5c14fd68a1e8e0432c803cbb15907adc2721446f4bec 11733 mat2_0.6.0-1_amd64.buildinfo
Files:
 111912d8b32579097b68d2c17a6f9ff4 2410 utils optional mat2_0.6.0-1.dsc
 a1c20f0243e03f1bb313d838794c7784 3740396 utils optional mat2_0.6.0.orig.tar.xz
 3f93cd6681800d36e41e9a6e0360c58c 833 utils optional mat2_0.6.0.orig.tar.xz.asc
 38a65f056c8519a1847671d97fece8f9 7060 utils optional mat2_0.6.0-1.debian.tar.xz
 46fafeb095f8908e4ff7913c0258a827 11733 utils optional mat2_0.6.0-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEE4p3Q++yWB9ljva4NWtdbQU6kFmcFAlvm3yEACgkQWtdbQU6k
FmeHOQ//WjGcui0mP3A/XWSmtG0hxGhkD8MPAXEzFc1YbC2vZLelz5+ia7lX+xU2
5FPwHSc56qXp1NOm+ilEZkX9S3+j1vRh+Hw1NbK6bvpmTDm8/wwAE7OkDl27KfYU
aPk49mBD25OUAqThvFmt8e+pXr39qAQTg94JfgsJUOx1nhQtUHQyg4YnMOXoNLAz
aadh/yTuViar57gIGUxvoyUB9M2C2l3YjP9bsoqvP6dj3oMleGg5H656pJvNfvIR
8R+85D5nzQyitmDDNSmd7G0vkFgFaXYfIYcrDQk9zSUQhIPt7ZDCp0N1oMndxE7A
TcSDsZnT7JPW52aDaVrAov+49E3W9PReC876eYkcZU8/kBMmSQSc7AcUJpclKBtX
Mw12u9IlkiLUlg5esXSpQ3a3++29YPyL9W+tnh5eowApJybFavmew9P2B4qzw7Ar
87pmXUwiTCJc4C2exiXoqkRmJatZL15lTKsEikHji1CgwBMMZQBwxnorKWnzp8r8
/0uTIJ+Lme41UoYGgVqpnWhk5lH/laMcr7RO7LVyIdVHFNbc/+ktJKam4UXGdfEH
qE5EVDQEzzM3ApVWLaNPadUnjZW8F6zExJ1g4vPUEqSN2jP028pWsyBKWa6lWHIQ
2i/NXcieRAvNaPgYbODroKpF0UiBJL21n4ZlL1z5CzB7pTedHyc=
=16pu
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Sat Nov 10 16:24:05 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 10 Nov 2018 16:24:05 +0000
Subject: [Pkg-privacy-maintainers] Processed: Re: Bug#913366:
 torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
References: <CAEQ9gEnO6Yg9qbhHMuUWWsXjF7bzRgG8i14sueXU7w9u9eeHJg@mail.gmail.com>
 <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>
Message-ID: <handler.s.B913366.154186690314143.transcript@bugs.debian.org>

Processing control commands:

> severity -1 important
Bug #913366 [torbrowser-launcher] torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
Severity set to 'important' from 'grave'
> tags -1 +pending
Bug #913366 [torbrowser-launcher] torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
Added tag(s) pending.

-- 
913366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913366
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From rosh at debian.org  Sat Nov 10 16:21:30 2018
From: rosh at debian.org (Roger Shimizu)
Date: Sun, 11 Nov 2018 01:21:30 +0900
Subject: [Pkg-privacy-maintainers] Bug#913366: Bug#913366:
 torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
In-Reply-To: <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>
References: <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>
 <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>
Message-ID: <CAEQ9gEnO6Yg9qbhHMuUWWsXjF7bzRgG8i14sueXU7w9u9eeHJg@mail.gmail.com>

control: severity -1 important
control: tags -1 +pending

On Sat, Nov 10, 2018 at 9:54 AM Diederik de Haas <didi.debian at cknow.org> wrote:
>
> Package: torbrowser-launcher
> Version: 0.3.1-1
> Severity: grave
> Tags: upstream patch
> Justification: renders package unusable

Thanks for your report!
However this is not grave level, IMHO. I think important should be proper.

> I had applied the patch before, but I guess it got overwritten with a
> new version (which I thought wasn't supposed to happen without asking).
> Applied the patch again and then torbrowser started again.
>
> For completeness sake, this is the patch intrigeri submitted upstream,
> but the upstream pull request is now already waiting more then a month
> for approval/merge, so it's probably good to apply this patch to the
> Debian package in the meantime.

It'd be included in next upload. Thanks!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


From ftpmaster at ftp-master.debian.org  Sun Nov 11 14:30:28 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 11 Nov 2018 14:30:28 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 sbws_1.0.2-1_sourceonly.changes
Message-ID: <E1gLqku-0002VI-Br@usper.debian.org>

sbws_1.0.2-1_sourceonly.changes uploaded successfully to localhost
along with the files:
  sbws_1.0.2-1.dsc
  sbws_1.0.2.orig.tar.gz
  sbws_1.0.2.orig.tar.gz.asc
  sbws_1.0.2-1.debian.tar.xz
  sbws_1.0.2-1_sourceonly.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sun Nov 11 14:40:22 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sun, 11 Nov 2018 14:40:22 +0000
Subject: [Pkg-privacy-maintainers] sbws_1.0.2-1_sourceonly.changes ACCEPTED
 into unstable
Message-ID: <E1gLquU-000HxF-8g@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sun, 11 Nov 2018 15:23:03 CET
Source: sbws
Binary: sbws sbws-doc
Architecture: source
Version: 1.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: ju xor <ju at riseup.net>
Description: 
 sbws - Simple Bandwidth Scanner for the Tor network
 sbws-doc - Simple Bandwidth Scanner
Changes:
 sbws (1.0.2-1) unstable; urgency=medium
 .
   * New upstream version
   * d/manpages: rename to d/sbws.manpages
   * Standards-Version: bump to 2.4.1 (no changes needed)
   * d/clean: include everything under doc/build
     since there is also man/, not only html/
   * d/control: add dvipng dependendy to build -doc
     since documentation includes latex mathematical formulae that are
     converted to images.
   * d/control: change project home to the main website.
     Instead of using the git URL that does not speak HTTP.
   * d/copyright: change source to the git Web interface
   * d/copyright: use https in the license URL
   * d/rules: check DEB_BUILD_OPTIONS.
     And also run the tests with all the installed python3 versions.
   * d/tests/control: add python3-all.
     So that all python3 versions can be tested.
     Change also format.
   * d/service: restrict dir permissions
   * d/systemd: Add environment variable
   * Remove RTT from description.
     Since it is disabled by default in v1.0.0
   * Fix Vcs URL to the correct team
   * Remove fix for stem old version
   * Update patch removing third party requests
   * d/manpages: use the ones generated by sphinx
   * d/control,rules: run pytest
   * d/control: Add dependency to build docs
   * d/sbws.docs: include example config
   * d/watch: update to canonical GH url
     and check signatures
   * d/tests: add minimal autopkgtest run pytest
   * d/upstream: add signing keys
Checksums-Sha256: 
 c2e24a18c63adae42c303be6513efb3bc75dbf4967af13760195c739436fc19a 2550 sbws_1.0.2-1.dsc
 fccc5cfbdd6a91b61e153518d50b703e27af4cd4ad325b840c5635f7b0e695f4 153521 sbws_1.0.2.orig.tar.gz
 6019bfdf1f1ffa05da5e94c12f8b6d0f6a225542e9088118cd629fdb13043575 119 sbws_1.0.2.orig.tar.gz.asc
 55303ed9d6aafedaaa245a75689c8dae65ca481a7787daedaf3abfe57018d0a2 31336 sbws_1.0.2-1.debian.tar.xz
 e51088af15bd211433b32736e7e21753835f85c1208ea65f35bb4c4af8f19f17 10538 sbws_1.0.2-1_sourceonly.buildinfo
Checksums-Sha1: 
 72a33bf55f14af355c9494f3d619ba772e8d25ca 2550 sbws_1.0.2-1.dsc
 084e5c888ed6edff90701c53180e7a6db6c2e44b 153521 sbws_1.0.2.orig.tar.gz
 d11689512d69826fb98baa583c86cdeb181ba7e2 119 sbws_1.0.2.orig.tar.gz.asc
 a170950f076521bed0488d906bea19b0ee7cff7f 31336 sbws_1.0.2-1.debian.tar.xz
 4492d58eb19beddf3151440c0d8d35b109c6186f 10538 sbws_1.0.2-1_sourceonly.buildinfo
Files: 
 e7c8bb9696125f57561e1314fcc38e62 2550 net optional sbws_1.0.2-1.dsc
 ca169f0dfd5a021972ce499bf8d0dfef 153521 net optional sbws_1.0.2.orig.tar.gz
 309f755736eebc90cd3022f474b0b691 119 net optional sbws_1.0.2.orig.tar.gz.asc
 27261415f6c3314a051acdb17db22698 31336 net optional sbws_1.0.2-1.debian.tar.xz
 55e8487c8f49d54d7abf1b33edf111a0 10538 - - sbws_1.0.2-1_sourceonly.buildinfo

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

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlvoO0dfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbZvxAAtx/Nx98rsumLzAy9PcnB8hRhwtwBiLbrNbpCvyZj8Jufm5HXOdY4OuEq
mE9FOvM0ijTcTXRlnbkA83OlDF+Hv0LBiZIWZ07ErSvtwNkpTTyeJ9D+quHbENa7
R6Ss12jkN69c3m1VQNKYkBlN0JPnWgiTeTHOiUatKTJvn9snkn4nY906tVgsqst+
BMyC9SdrUu2gZ2jJoyCjYYhQ8JmCimPfPHfFLwPEC3e9gJiTeZjcin6iqG76xFGM
9i6gn1ikhhYiZtVg+GoXAUK3Vd+ERVRZrBCLm+7V+elQt9Os2ub/irZYM0RrvPfk
pxfT6O6hTfGlb9RvekedZ8mBodXXu1wtIiQGbiOw9Ot92LCBjw0KgsDxXhStK1Q7
7ew/SyNPb9x/eZ4jTgy/djVmy2fPqUdgnvH6VgwOlUt6jS/njUjs6dSqK5BLCMwC
BbTtKyKG2QfbqEajuhJrqZ6QDImaVlfSKyDGVtqU6rf/a0R9yAY0ggL2AIIySv7g
GoBh1eP72EIMOfEBKmU9enhQ3ScwHqM1TyKRWTLn+RnHbs00265HEii7Q2U2oXhu
TDUA0FREzYD82rLxbTptorZ0/EbrQnHEehFRAYseUngttiUczbPgUbs6E0XxHedu
Bl0ij3BKrSOWDpmpzEs3qf6iYejLuGBK/C9aL0xKG41SopqGR84=
=mBqb
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Sun Nov 11 17:15:08 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sun, 11 Nov 2018 17:15:08 +0000
Subject: [Pkg-privacy-maintainers] Bug#908706: marked as done
 (torbrowser-launcher: error on torbrowser-launcher first install:
 exceptions.AttributeError: 'NoneType' object has no attribute 'bio_read')
References: <CAEQ9gEkEjA6W0sSwPBrKEsvQUTk2vYOGa1xdg3Kp=wUwxzKSRA@mail.gmail.com>
 <3336504d-415a-3534-b393-2b9b79a1f2af@gmail.com>
Message-ID: <handler.908706.D908706.15419563157827.ackdone@bugs.debian.org>

Your message dated Mon, 12 Nov 2018 02:11:40 +0900
with message-id <CAEQ9gEkEjA6W0sSwPBrKEsvQUTk2vYOGa1xdg3Kp=wUwxzKSRA at mail.gmail.com>
and subject line Re: [Pkg-privacy-maintainers] Bug#908706: new version fixed the problem
has caused the Debian Bug report #908706,
regarding torbrowser-launcher: error on torbrowser-launcher first install: exceptions.AttributeError: 'NoneType' object has no attribute 'bio_read'
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 at bugs.debian.org
immediately.)


-- 
908706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908706
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: stefan esterer <stefan.esterer at gmail.com>
Subject: torbrowser-launcher: error on torbrowser-launcher first install: exceptions.AttributeError: 'NoneType' object has no attribute 'bio_read'
Date: Wed, 12 Sep 2018 22:35:15 +0200
Size: 8911
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181111/76366d86/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Re: [Pkg-privacy-maintainers] Bug#908706: new version fixed the problem
Date: Mon, 12 Nov 2018 02:11:40 +0900
Size: 3756
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181111/76366d86/attachment-0001.mht>

From owner at bugs.debian.org  Sun Nov 11 17:30:07 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sun, 11 Nov 2018 17:30:07 +0000
Subject: [Pkg-privacy-maintainers] Processed: your mail
References: <CAEQ9gEnH9kOWHBsWJ3-R-RTXL-VEAPQbLcX7zUh_vH4noEAL6g@mail.gmail.com>
Message-ID: <handler.s.C.154195719413558.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tag 910827 +pending
Bug #910827 [torbrowser-launcher] Doing update on torbrowser-launcher 0.2.9-6 resulted in not finding profile
Added tag(s) pending.
> tag 913366 +pending
Bug #913366 [torbrowser-launcher] torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
Ignoring request to alter tags of bug #913366 to the same tags previously set
> tag 913151 +pending
Bug #913151 [torbrowser-launcher] torbrowser-launcher: modem sound was removed, python-pygame is unused, drop both from suggests/appdata.xml
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
910827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910827
913151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913151
913366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913366
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From rosh at debian.org  Mon Nov 12 15:50:01 2018
From: rosh at debian.org (Roger Shimizu)
Date: Tue, 13 Nov 2018 00:50:01 +0900
Subject: [Pkg-privacy-maintainers] Bug#753173: Bug#753173: the locale bug is
 back
In-Reply-To: <20181101135211.GA2764@jadzia.comodo.priv.at>
References: <201602170939.22213.holger@layer-acht.org>
 <20140629182253.GA7207@valiant.palfrader.org>
 <20160217160808.GR11057@jadzia.comodo.priv.at>
 <20181101135211.GA2764@jadzia.comodo.priv.at>
 <20140629182253.GA7207@valiant.palfrader.org>
Message-ID: <CAEQ9gE=BdC9D_=FoWh64VWPqxmVDGXfm4Pp2hPWyuQOc=5WsOA@mail.gmail.com>

control: tag -1 pending

On Thu, Nov 1, 2018 at 10:57 PM gregor herrmann <gregoa at debian.org> wrote:
>
> On Wed, 17 Feb 2016 17:08:08 +0100, gregor herrmann wrote:
>
> > I can confirm that this works for my locale settings as well.
> > Nice :)
>
> And the bug is back with 0.3.1-1:

Because upstream chose so..
- https://github.com/micahflee/torbrowser-launcher/commit/b828bdfafe60bb9bcf93ec660ad5c07ff7fdbdf5

I'll include a revert commit on next upload.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


From owner at bugs.debian.org  Mon Nov 12 15:51:04 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 12 Nov 2018 15:51:04 +0000
Subject: [Pkg-privacy-maintainers] Processed: Re: Bug#753173: the locale bug
 is back
References: <CAEQ9gE=BdC9D_=FoWh64VWPqxmVDGXfm4Pp2hPWyuQOc=5WsOA@mail.gmail.com>
 <20140629182253.GA7207@valiant.palfrader.org>
Message-ID: <handler.s.B753173.154203781624604.transcript@bugs.debian.org>

Processing control commands:

> tag -1 pending
Bug #753173 [torbrowser-launcher] torbrowser-launcher: wrongly detects language
Added tag(s) pending.

-- 
753173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753173
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From gregoa at debian.org  Mon Nov 12 16:57:55 2018
From: gregoa at debian.org (gregor herrmann)
Date: Mon, 12 Nov 2018 17:57:55 +0100
Subject: [Pkg-privacy-maintainers] Bug#753173: Bug#753173: the locale bug is
 back
In-Reply-To: <CAEQ9gE=BdC9D_=FoWh64VWPqxmVDGXfm4Pp2hPWyuQOc=5WsOA@mail.gmail.com>
References: <201602170939.22213.holger@layer-acht.org>
 <20140629182253.GA7207@valiant.palfrader.org>
 <20160217160808.GR11057@jadzia.comodo.priv.at>
 <20181101135211.GA2764@jadzia.comodo.priv.at>
 <CAEQ9gE=BdC9D_=FoWh64VWPqxmVDGXfm4Pp2hPWyuQOc=5WsOA@mail.gmail.com>
 <20140629182253.GA7207@valiant.palfrader.org>
Message-ID: <20181112165755.GV8930@jadzia.comodo.priv.at>

On Tue, 13 Nov 2018 00:50:01 +0900, Roger Shimizu wrote:

> > And the bug is back with 0.3.1-1:
> Because upstream chose so..
> - https://github.com/micahflee/torbrowser-launcher/commit/b828bdfafe60bb9bcf93ec660ad5c07ff7fdbdf5

Oh dear :)
 
> I'll include a revert commit on next upload.

Thanks, much appreciated.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Joan Baez: Lady Di and I
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181112/5fda4875/attachment.sig>

From noreply at release.debian.org  Tue Nov 13 04:39:11 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Tue, 13 Nov 2018 04:39:11 +0000
Subject: [Pkg-privacy-maintainers] mat2 0.6.0-1 MIGRATED to testing
Message-ID: <E1gMQTn-0005KJ-K3@respighi.debian.org>

FYI: The status of the mat2 source package
in Debian's testing distribution has changed.

  Previous version: 0.5.0-1
  Current version:  0.6.0-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From noreply at release.debian.org  Wed Nov 14 04:39:12 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Wed, 14 Nov 2018 04:39:12 +0000
Subject: [Pkg-privacy-maintainers] sbws 1.0.2-1 MIGRATED to testing
Message-ID: <E1gMmxM-000301-32@respighi.debian.org>

FYI: The status of the sbws source package
in Debian's testing distribution has changed.

  Previous version: 0.6.0-1
  Current version:  1.0.2-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From georg at riseup.net  Wed Nov 14 22:17:07 2018
From: georg at riseup.net (Georg Faerber)
Date: Wed, 14 Nov 2018 22:17:07 +0000
Subject: [Pkg-privacy-maintainers] Mailing list archive broken since ~ mid
 of August
Message-ID: <20181114221707.GM9522@debian>

Dear team,

FYI: As per the subject [1], I've reported this [2].

Cheers,
Georg


[1] https://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/
[2] https://salsa.debian.org/alioth-lists-team/support/issues/11
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181114/f6dd2156/attachment.sig>

From debian-bts-link at lists.debian.org  Thu Nov 15 17:15:06 2018
From: debian-bts-link at lists.debian.org (debian-bts-link at lists.debian.org)
Date: Thu, 15 Nov 2018 17:15:06 +0000
Subject: [Pkg-privacy-maintainers] [bts-link] source package
 torbrowser-launcher
Message-ID: <154230210671.6097.14716334266187895571.btslink@sonntag.debian.org>

#
# bts-link upstream status pull for source package torbrowser-launcher
# see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
#     https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-link at lists.debian.org

# remote status report for #913366 (http://bugs.debian.org/913366)
# Bug title: torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
#  * https://github.com/micahflee/torbrowser-launcher/pull/360
#  * remote status changed: (?) -> open
usertags 913366 + status-open

thanks


From ulrike at debian.org  Fri Nov 16 11:25:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Fri, 16 Nov 2018 11:25:00 +0000
Subject: [Pkg-privacy-maintainers] Mailing list archive broken since ~
 mid of August
In-Reply-To: <20181114221707.GM9522@debian>
References: <20181114221707.GM9522@debian>
Message-ID: <023e0bac-7d1c-b772-5dde-5d1ac47116f4@debian.org>

Hi Georg,

Georg Faerber:
> Dear team,
> 
> FYI: As per the subject [1], I've reported this [2].

Interesting, I think this happened when we decided it might be more
useful to have a non-weekly archive.

I'll look into it (next week I've scheduled some Debian work).

And also into receiving emails from Salsa which seems to not have worked
out correctly.

> [1] https://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/
> [2] https://salsa.debian.org/alioth-lists-team/support/issues/11

Cheers!
u.


From ulrike at debian.org  Fri Nov 16 11:33:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Fri, 16 Nov 2018 11:33:00 +0000
Subject: [Pkg-privacy-maintainers] Fwd: Request to join the Privacy
 Maintainers group
In-Reply-To: <5bedc1e5dc0d2_3553fca1d44dde8638764@godard.mail>
References: <5bedc1e5dc0d2_3553fca1d44dde8638764@godard.mail>
Message-ID: <088aeac7-ecc1-92df-410a-1facc31cb8e9@debian.org>

Hi!

We received this request to join the team from Nicoo (in Cc:). Nicoo is
already a (valuable!) member of our team, but until now used another
account name (nicoo-guest) in the Salsa group.

So without waiting for your consent, I will approve this request, and
check back with nicoo what to do about the other account.

If anybody does not agree, please let me know.

Cheers,
Ulrike


-------- Forwarded Message --------
Subject: Request to join the Privacy Maintainers group
Date: Thu, 15 Nov 2018 18:58:45 +0000
From: Debian GitLab <gitlab at salsa.debian.org>
Reply-To: Debian GitLab <noreply at salsa.debian.org>
To: ulrike at debian.org

Nicolas Braud-Santoni (https://salsa.debian.org/nicoo) requested
Developer access to the Privacy Maintainers group.

https://salsa.debian.org/groups/pkg-privacy-team/-/group_members

-- 

You're receiving this email because of your account on salsa.debian.org.



From ulrike at debian.org  Fri Nov 16 11:36:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Fri, 16 Nov 2018 11:36:00 +0000
Subject: [Pkg-privacy-maintainers] Request to join the Privacy
 Maintainers group
In-Reply-To: <20181017120805.GU4144@debian>
References: <5bc67c2385baf_3a82ae22788472411302ef@godard.mail>
 <0fb0e9c3-5cac-a819-5e0e-fe32df02767f@debian.org>
 <6ae051ac-b6c4-bb1d-a081-58b47767eecd@451f.org>
 <20181017120805.GU4144@debian>
Message-ID: <f70d3d18-deb0-bd51-de20-316209b79ab3@debian.org>

Hi!

Georg Faerber:
> On 18-10-17 09:45:00, u wrote:
>> I would suggest that we automatically reset the counter for the
>> decision making process to the day on which we receive an answer from
>> Vipul.
> 
> Agreed.

That was a month ago and we did not receive a reply, so I'll reject this
request now.

Cheers,
Ulrike


From ulrike at debian.org  Fri Nov 16 11:39:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Fri, 16 Nov 2018 11:39:00 +0000
Subject: [Pkg-privacy-maintainers] Request to join the Privacy
 Maintainers group
In-Reply-To: <87murcbjf9.fsf@fifthhorseman.net>
References: <5bc67c2385baf_3a82ae22788472411302ef@godard.mail>
 <0fb0e9c3-5cac-a819-5e0e-fe32df02767f@debian.org>
 <6ae051ac-b6c4-bb1d-a081-58b47767eecd@451f.org>
 <20181017120805.GU4144@debian> <87murcbjf9.fsf@fifthhorseman.net>
Message-ID: <f941b191-2219-ebca-64bf-7b1f8d4b4664@debian.org>

Hi!

Daniel Kahn Gillmor:
> On Wed 2018-10-17 12:08:05 +0000, Georg Faerber wrote:
>> On 18-10-17 09:45:00, u wrote:

> I've sent a patch to our team process list to try to clarify that we
> want an explicit explanation for future membership requests, since
> gitlab membership requests don't support such a feature. (see
> id:87o9bsbjhx.fsf at fifthhorseman.net)

This was merged.

Cheers!
u.


From ulrike at debian.org  Fri Nov 16 11:48:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Fri, 16 Nov 2018 11:48:00 +0000
Subject: [Pkg-privacy-maintainers] Mailing list archive broken since ~
 mid of August
In-Reply-To: <023e0bac-7d1c-b772-5dde-5d1ac47116f4@debian.org>
References: <20181114221707.GM9522@debian>
 <023e0bac-7d1c-b772-5dde-5d1ac47116f4@debian.org>
Message-ID: <7c04238b-77d1-8151-df3b-926a3df8a54b@debian.org>

Hi!

Ulrike Uhlig:
> Georg Faerber:

>> FYI: As per the subject [1], I've reported this [2].
> 
> Interesting, I think this happened when we decided it might be more
> useful to have a non-weekly archive.
> 
> I'll look into it (next week I've scheduled some Debian work).

Ack: I replied on [1].

> And also into receiving emails from Salsa which seems to not have worked
> out correctly.

… understood as well, because this was for Alioth Lists Team. :=)

>> [1] https://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/
>> [2] https://salsa.debian.org/alioth-lists-team/support/issues/11


From dkg at fifthhorseman.net  Fri Nov 16 12:09:42 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Fri, 16 Nov 2018 07:09:42 -0500
Subject: [Pkg-privacy-maintainers] Fwd: Request to join the Privacy
 Maintainers group
In-Reply-To: <088aeac7-ecc1-92df-410a-1facc31cb8e9@debian.org>
References: <5bedc1e5dc0d2_3553fca1d44dde8638764@godard.mail>
 <088aeac7-ecc1-92df-410a-1facc31cb8e9@debian.org>
Message-ID: <87y39tql4p.fsf@fifthhorseman.net>

On Fri 2018-11-16 11:33:00 +0000, Ulrike Uhlig wrote:

> We received this request to join the team from Nicoo (in Cc:). Nicoo is
> already a (valuable!) member of our team, but until now used another
> account name (nicoo-guest) in the Salsa group.
>
> So without waiting for your consent, I will approve this request, and
> check back with nicoo what to do about the other account.
>
> If anybody does not agree, please let me know.

Changing the account name under which nicoo is a privacy-team member,
now that she is a DD is totally reasonable.  On other teams i've been
on, i think the ${foo}-guest account has been removed from group
membership when the person has deleted that account.  I suppose for the
privacy-team, the only important thing is to remember in the meantime
that nicoo doesn't count twice when calculating quorum or voting, but i
think we can handle that :)

Thanks for taking on DD responsibilities, nicoo!  And thanks for taking
care of the logistics, Ulrike!

             --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181116/ec096190/attachment.sig>

From georg at riseup.net  Fri Nov 16 19:51:25 2018
From: georg at riseup.net (Georg Faerber)
Date: Fri, 16 Nov 2018 19:51:25 +0000
Subject: [Pkg-privacy-maintainers] Mailing list archive broken since ~
 mid of August
In-Reply-To: <023e0bac-7d1c-b772-5dde-5d1ac47116f4@debian.org>
References: <20181114221707.GM9522@debian>
 <023e0bac-7d1c-b772-5dde-5d1ac47116f4@debian.org>
Message-ID: <20181116195125.GB3472@debian>

Hi,

On 18-11-16 11:25:00, Ulrike Uhlig wrote:
> Interesting, I think this happened when we decided it might be more
> useful to have a non-weekly archive.

Furthermore, the archive is not broken, all the messages are available
via [1]. The link to this site is just not on the top, where I expected
it, but it's the first link after all the ones which point to the weekly
archives of 2017. IMHO, that's not really intuitive, at the same time, I
doubt that it's possible to change this.

I guess this will be fixed, at least for the future, with the beginning
of 2019.

Cheers,
Georg


[1] https://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/2018/thread.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181116/4b090db0/attachment.sig>

From georg at riseup.net  Fri Nov 16 19:58:24 2018
From: georg at riseup.net (Georg Faerber)
Date: Fri, 16 Nov 2018 19:58:24 +0000
Subject: [Pkg-privacy-maintainers] Mailing list archive broken since ~
 mid of August
In-Reply-To: <20181116195125.GB3472@debian>
References: <20181114221707.GM9522@debian>
 <023e0bac-7d1c-b772-5dde-5d1ac47116f4@debian.org>
 <20181116195125.GB3472@debian>
Message-ID: <20181116195824.GC3472@debian>

Hi again,

On 18-11-16 19:51:25, Georg Faerber wrote:
> Furthermore, the archive is not broken, all the messages are available
> via [1]. The link to this site is just not on the top, where I
> expected it, but it's the first link after all the ones which point to
> the weekly archives of 2017. IMHO, that's not really intuitive, at the
> same time, I doubt that it's possible to change this.

Well, I was wrong on this, the admins just offered us to rebuild the
archive [1], which would:
  - fix the above described problem,
  - make the former weekly pages disappear, which would break links
    pointing to them.

Any opinions on this?

Cheers,
Georg


[1] https://salsa.debian.org/alioth-lists-team/support/issues/11#note_52301
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181116/11d55407/attachment.sig>

From ulrike at debian.org  Fri Nov 16 21:06:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Fri, 16 Nov 2018 21:06:00 +0000
Subject: [Pkg-privacy-maintainers] Mailing list archive broken since ~
 mid of August
In-Reply-To: <20181116195824.GC3472@debian>
References: <20181114221707.GM9522@debian>
 <023e0bac-7d1c-b772-5dde-5d1ac47116f4@debian.org>
 <20181116195125.GB3472@debian> <20181116195824.GC3472@debian>
Message-ID: <e8cb57ae-b0bb-ebde-ae79-0d23730affbd@debian.org>

Hello!

Georg Faerber:
> On 18-11-16 19:51:25, Georg Faerber wrote:
>> Furthermore, the archive is not broken, all the messages are available
>> via [1]. The link to this site is just not on the top, where I
>> expected it, but it's the first link after all the ones which point to
>> the weekly archives of 2017. IMHO, that's not really intuitive, at the
>> same time, I doubt that it's possible to change this.
> 
> Well, I was wrong on this, the admins just offered us to rebuild the
> archive [1], which would:
>   - fix the above described problem,
>   - make the former weekly pages disappear, which would break links
>     pointing to them.
> 
> Any opinions on this?

Does that mean that 2017 will have a page?
That would be super nice :)

Cheers
u.


From georg at riseup.net  Fri Nov 16 21:09:19 2018
From: georg at riseup.net (Georg Faerber)
Date: Fri, 16 Nov 2018 21:09:19 +0000
Subject: [Pkg-privacy-maintainers] Mailing list archive broken since ~
 mid of August
In-Reply-To: <e8cb57ae-b0bb-ebde-ae79-0d23730affbd@debian.org>
References: <20181114221707.GM9522@debian>
 <023e0bac-7d1c-b772-5dde-5d1ac47116f4@debian.org>
 <20181116195125.GB3472@debian> <20181116195824.GC3472@debian>
 <e8cb57ae-b0bb-ebde-ae79-0d23730affbd@debian.org>
Message-ID: <20181116210919.GF3472@debian>

On 18-11-16 21:06:00, Ulrike Uhlig wrote:
> Georg Faerber:
> > On 18-11-16 19:51:25, Georg Faerber wrote:
> >> Furthermore, the archive is not broken, all the messages are
> >> available via [1]. The link to this site is just not on the top,
> >> where I expected it, but it's the first link after all the ones
> >> which point to the weekly archives of 2017. IMHO, that's not really
> >> intuitive, at the same time, I doubt that it's possible to change
> >> this.
> > 
> > Well, I was wrong on this, the admins just offered us to rebuild the
> > archive [1], which would:
> >   - fix the above described problem,
> >   - make the former weekly pages disappear, which would break links
> >     pointing to them.
> > 
> > Any opinions on this?
> 
> Does that mean that 2017 will have a page?

I think so; there would be one for 2015 and 2016 as well.

> That would be super nice :)

:)

Cheers,
Georg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181116/f7370903/attachment.sig>

From intrigeri at debian.org  Sat Nov 17 06:36:49 2018
From: intrigeri at debian.org (intrigeri)
Date: Sat, 17 Nov 2018 07:36:49 +0100
Subject: [Pkg-privacy-maintainers] Mailing list archive broken since ~
 mid of August
In-Reply-To: <e8cb57ae-b0bb-ebde-ae79-0d23730affbd@debian.org>
References: <20181114221707.GM9522@debian>
 <023e0bac-7d1c-b772-5dde-5d1ac47116f4@debian.org>
 <20181116195125.GB3472@debian> <20181116195824.GC3472@debian>
 <e8cb57ae-b0bb-ebde-ae79-0d23730affbd@debian.org>
Message-ID: <87efbkrz0e.fsf@boum.org>

Hi,

Ulrike Uhlig:
> Georg Faerber:
>> On 18-11-16 19:51:25, Georg Faerber wrote:
>>> Furthermore, the archive is not broken, all the messages are available
>>> via [1]. The link to this site is just not on the top, where I
>>> expected it, but it's the first link after all the ones which point to
>>> the weekly archives of 2017. IMHO, that's not really intuitive, at the
>>> same time, I doubt that it's possible to change this.
>> 
>> Well, I was wrong on this, the admins just offered us to rebuild the
>> archive [1], which would:
>>   - fix the above described problem,
>>   - make the former weekly pages disappear, which would break links
>>     pointing to them.
>> 
>> Any opinions on this?

I'm not sure whether improving browsing of the old archive and making
the August-December 2018 one more visible is worth the cost of
breaking existing links. Either way, I suspect that only relatively
rare use cases are affected so I can live with both options.

> Does that mean that 2017 will have a page?
> That would be super nice :)

Yes, I think so and indeed it would be nice.

Cheers
-- 
intrigeri


From ftpmaster at ftp-master.debian.org  Sat Nov 17 10:27:41 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 17 Nov 2018 10:27:41 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.3.1-2_source.changes
Message-ID: <E1gNxpF-0007SS-I0@usper.debian.org>

torbrowser-launcher_0.3.1-2_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.3.1-2.dsc
  torbrowser-launcher_0.3.1-2.debian.tar.xz
  torbrowser-launcher_0.3.1-2_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Sat Nov 17 10:37:10 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 17 Nov 2018 10:37:10 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.3.1-2_source.changes ACCEPTED into unstable
Message-ID: <E1gNxyQ-00026E-9q@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sat, 17 Nov 2018 19:15:20 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Closes: 753173 910827 912490 913151 913366
Changes:
 torbrowser-launcher (0.3.1-2) unstable; urgency=medium
 .
   * debian/control:
     - Remove Suggests for python-pygame, which was related to modem
       sound (Closes: #912490, #913151).
   * debian/patches:
     - Add translation patches from pull-request of upstream: hu, da,
       and sv.
     - Add patch 0008 to remove mention of modem sound in docs and
       translation po files. Thanks to Paul Wise for the information.
     - Cherry-pick 2 new appamor patch from pull-request of upstream:
       [1b2e6aa] AppArmor: allow Web Content processes to check
                 the update status.
       [3cd8aeb] AppArmor: allow Web Content processes to read
                 profile.ini and the updates' "updater" file.
       Thanks to intrigeri for the patches, and Diederik de Haas
       & Shirish Agarwal for the bug report (Closes: #910827, #913366).
     - Revert [b828bdf] to fix detecting system locale (Closes: #753173).
Checksums-Sha1:
 c1aa730d1b6d683c80345234ac101cb36bef3187 2174 torbrowser-launcher_0.3.1-2.dsc
 64c2ea2e811416ef3cb2cc645d738738cb94b238 18460 torbrowser-launcher_0.3.1-2.debian.tar.xz
 3266476edc585cfc5984683c6e0e6e3a8f66e2ce 6237 torbrowser-launcher_0.3.1-2_source.buildinfo
Checksums-Sha256:
 b855888779bd99b9cdcb477e18ba31d43f40e334e0a2e9df5b55cd76c6a0084a 2174 torbrowser-launcher_0.3.1-2.dsc
 5c225c0a60a7d39157892c93823ddd2f5ae9e59123e3463e62981fa9b476ee68 18460 torbrowser-launcher_0.3.1-2.debian.tar.xz
 ce09243ec9698336c369936020d7cff8c33df1f7370aa615bbc60e9603276ba1 6237 torbrowser-launcher_0.3.1-2_source.buildinfo
Files:
 9c5bbe788c104a455299c172e7ac917f 2174 contrib/web optional torbrowser-launcher_0.3.1-2.dsc
 617bc18d8c6ca498a8c0764059011bf4 18460 contrib/web optional torbrowser-launcher_0.3.1-2.debian.tar.xz
 e8d2c6748f6235513ccfd07b3232ff11 6237 contrib/web optional torbrowser-launcher_0.3.1-2_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAlvv67cQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qEvXEACau1JpgdVm+7QdSmeZ2zRmwM5kCg5qGIvd
qbTKXLB13cIcR1AJpaeTMsC7QCCZ2tXZyjzcxX/pKr9gihXs/AS2Rjj5BNUI+5D9
hBOg2cYxWHUuT7oGOC8WgKAtUdqzX7z9QJoWqsIJK9ZQAntx4S886Wknk0UiThXF
jZ3L5dnIJvPYnDcmEWEs67bM66o/TgRoSb7qLaql/uQSwWp0nNwmQlokqKX0NFJN
o9F/OWGiYr7MQuANJQqnynKq/WY0RUtY8WYWhYolVwuWoj8moAO0xofr7oY3nhgx
A9A14LN6cKn6LlNxpf3NMq8Kl+whSnwrA104T73i8CrjDxFaPo0w+MO72ou2I+nK
GcsjKNUlvX+SKhGJanNsXadMCXntnqOYRwAP75ArZU3uyq0Z8Lu+ZVVh2C508upG
7U+fVO0kzj47wO+zNmKl4XB3HsY6VO5xa9u2neWOAaHeycFWzdjEiGT9N6qvF6nz
kBZ+F0yavXHimLmPpzxes2tQHoJSWmIkGy2zidbPkmQifNV52e58PggMrBxJbi/7
f7ZLdPuTSdkkxxgwx6wqBk3LcLbfSwKB2FzbLJ4XRsFR3zfKfyDXQ1i7hVp7nN3l
fLIeIWcNHQ4G+GcIuvsVqG32BTpigVJjo7T9e8lG15HHle/5aJjClPdLH9TAQpfG
MC11x8TjLA==
=BLYX
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Sat Nov 17 10:39:03 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 17 Nov 2018 10:39:03 +0000
Subject: [Pkg-privacy-maintainers] Bug#753173: marked as done
 (torbrowser-launcher: wrongly detects language)
References: <E1gNxyQ-00026O-CV@fasolo.debian.org>
 <20140629182253.GA7207@valiant.palfrader.org>
Message-ID: <handler.753173.D753173.154245103217605.ackdone@bugs.debian.org>

Your message dated Sat, 17 Nov 2018 10:37:10 +0000
with message-id <E1gNxyQ-00026O-CV at fasolo.debian.org>
and subject line Bug#753173: fixed in torbrowser-launcher 0.3.1-2
has caused the Debian Bug report #753173,
regarding torbrowser-launcher: wrongly detects language
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 at bugs.debian.org
immediately.)


-- 
753173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753173
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Peter Palfrader <weasel at debian.org>
Subject: wrongly detects language
Date: Sun, 29 Jun 2014 20:22:55 +0200
Size: 2358
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/5b34e68e/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Bug#753173: fixed in torbrowser-launcher 0.3.1-2
Date: Sat, 17 Nov 2018 10:37:10 +0000
Size: 6261
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/5b34e68e/attachment-0001.mht>

From owner at bugs.debian.org  Sat Nov 17 10:39:06 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 17 Nov 2018 10:39:06 +0000
Subject: [Pkg-privacy-maintainers] Bug#851236: marked as done
 (torbrowser-launcher gives python errors and doesn't launch)
References: <CAEQ9gEkuj4P6PKbOfbyYATnegD9ccd5+=xrAzYOys+tgTE4Dow@mail.gmail.com>
 <148429632048.3818.832592359795096760.reportbug@athena>
Message-ID: <handler.851236.D851236.154245096416754.ackdone@bugs.debian.org>

Your message dated Sat, 17 Nov 2018 19:35:48 +0900
with message-id <CAEQ9gEkuj4P6PKbOfbyYATnegD9ccd5+=xrAzYOys+tgTE4Dow at mail.gmail.com>
and subject line Re: [Pkg-privacy-maintainers] Bug#851236: Ping?
has caused the Debian Bug report #851236,
regarding torbrowser-launcher gives python errors and doesn't launch
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 at bugs.debian.org
immediately.)


-- 
851236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851236
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Russell Coker <russell at coker.com.au>
Subject: torbrowser-launcher gives python errors and doesn't launch
Date: Fri, 13 Jan 2017 19:32:00 +1100
Size: 5841
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/9b0aa129/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Re: [Pkg-privacy-maintainers] Bug#851236: Ping?
Date: Sat, 17 Nov 2018 19:35:48 +0900
Size: 3684
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/9b0aa129/attachment-0001.mht>

From owner at bugs.debian.org  Sat Nov 17 10:39:08 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 17 Nov 2018 10:39:08 +0000
Subject: [Pkg-privacy-maintainers] Bug#910827: marked as done (Doing update
 on torbrowser-launcher 0.2.9-6 resulted in not finding profile)
References: <E1gNxyQ-00026U-Ds@fasolo.debian.org>
 <CADdDZR=bvbS0zdbg45obuJ-TXgwTqQrmv8x543aAj5TkUeW0JQ@mail.gmail.com>
Message-ID: <handler.910827.D910827.154245103217606.ackdone@bugs.debian.org>

Your message dated Sat, 17 Nov 2018 10:37:10 +0000
with message-id <E1gNxyQ-00026U-Ds at fasolo.debian.org>
and subject line Bug#910827: fixed in torbrowser-launcher 0.3.1-2
has caused the Debian Bug report #910827,
regarding Doing update on torbrowser-launcher 0.2.9-6 resulted in not finding 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 owner at bugs.debian.org
immediately.)


-- 
910827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910827
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: =?UTF-8?B?c2hpcmlzaCDgpLbgpL/gpLDgpYDgpLc=?= <shirishag75 at gmail.com>
Subject: Doing update on torbrowser-launcher 0.2.9-6 resulted in not finding profile
Date: Fri, 12 Oct 2018 00:46:18 +0530
Size: 5414
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/e0487ac4/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Bug#910827: fixed in torbrowser-launcher 0.3.1-2
Date: Sat, 17 Nov 2018 10:37:10 +0000
Size: 6236
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/e0487ac4/attachment-0003.mht>

From owner at bugs.debian.org  Sat Nov 17 10:39:11 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 17 Nov 2018 10:39:11 +0000
Subject: [Pkg-privacy-maintainers] Bug#912490: marked as done
 (torbrowser-launcher: Please migrate to python3-pygame)
References: <E1gNxyQ-00026a-FC@fasolo.debian.org>
 <20181031222859.2910F18C5A8B@shore.naturalnet.de>
Message-ID: <handler.912490.D912490.154245103417636.ackdone@bugs.debian.org>

Your message dated Sat, 17 Nov 2018 10:37:10 +0000
with message-id <E1gNxyQ-00026a-FC at fasolo.debian.org>
and subject line Bug#912490: fixed in torbrowser-launcher 0.3.1-2
has caused the Debian Bug report #912490,
regarding torbrowser-launcher: Please migrate to python3-pygame
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 at bugs.debian.org
immediately.)


-- 
912490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912490
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: natureshadow at debian.org
Subject: torbrowser-launcher: Please migrate to python3-pygame
Date: Wed, 31 Oct 2018 23:28:57 +0100
Size: 2671
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/6a10932f/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Bug#912490: fixed in torbrowser-launcher 0.3.1-2
Date: Sat, 17 Nov 2018 10:37:10 +0000
Size: 6273
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/6a10932f/attachment-0001.mht>

From owner at bugs.debian.org  Sat Nov 17 10:39:13 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 17 Nov 2018 10:39:13 +0000
Subject: [Pkg-privacy-maintainers] Bug#913151: marked as done
 (torbrowser-launcher: modem sound was removed, python-pygame is unused,
 drop both from suggests/appdata.xml)
References: <E1gNxyQ-00026g-GT@fasolo.debian.org>
 <350aada78a71d996f6bf2f467b2993594b3d0356.camel@debian.org>
Message-ID: <handler.913151.D913151.154245103217609.ackdone@bugs.debian.org>

Your message dated Sat, 17 Nov 2018 10:37:10 +0000
with message-id <E1gNxyQ-00026g-GT at fasolo.debian.org>
and subject line Bug#913151: fixed in torbrowser-launcher 0.3.1-2
has caused the Debian Bug report #913151,
regarding torbrowser-launcher: modem sound was removed, python-pygame is unused, drop both from suggests/appdata.xml
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 at bugs.debian.org
immediately.)


-- 
913151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913151
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Paul Wise <pabs at debian.org>
Subject: torbrowser-launcher: modem sound was removed, python-pygame is unused, drop both from suggests/appdata.xml
Date: Wed, 07 Nov 2018 23:59:47 +0800
Size: 5211
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/c39ab2ac/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Bug#913151: fixed in torbrowser-launcher 0.3.1-2
Date: Sat, 17 Nov 2018 10:37:10 +0000
Size: 6260
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/c39ab2ac/attachment-0001.mht>

From owner at bugs.debian.org  Sat Nov 17 10:39:15 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 17 Nov 2018 10:39:15 +0000
Subject: [Pkg-privacy-maintainers] Bug#913366: marked as done
 (torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch)
References: <E1gNxyQ-00026m-Hr@fasolo.debian.org>
 <154181054356.29360.5404631142935194557.reportbug@bagend.home.cknow.org>
Message-ID: <handler.913366.D913366.154245103417639.ackdone@bugs.debian.org>

Your message dated Sat, 17 Nov 2018 10:37:10 +0000
with message-id <E1gNxyQ-00026m-Hr at fasolo.debian.org>
and subject line Bug#913366: fixed in torbrowser-launcher 0.3.1-2
has caused the Debian Bug report #913366,
regarding torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
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 at bugs.debian.org
immediately.)


-- 
913366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913366
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Diederik de Haas <didi.debian at cknow.org>
Subject: torbrowser-launcher: more apparmor fixes needed, otherwise fails to launch
Date: Sat, 10 Nov 2018 01:42:23 +0100
Size: 10402
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/a940b7cd/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Bug#913366: fixed in torbrowser-launcher 0.3.1-2
Date: Sat, 17 Nov 2018 10:37:10 +0000
Size: 6272
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/a940b7cd/attachment-0003.mht>

From owner at bugs.debian.org  Sat Nov 17 10:45:07 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 17 Nov 2018 10:45:07 +0000
Subject: [Pkg-privacy-maintainers] Bug#890238: marked as done
 (torbrowser-launcher: Failed to launcher torbrowswer with permission denied
 error regarding dbus)
References: <CAEQ9gEkFVfNRirs-sCQzjjo9zkcphdj-JoF_GovCiJmwDaZwAw@mail.gmail.com>
 <CAPZRg5gFuZDCx5UzzfDBfR+KqYqEBKuBA01f44Z+1PZbmbBD_g@mail.gmail.com>
Message-ID: <handler.890238.D890238.154245147020276.ackdone@bugs.debian.org>

Your message dated Sat, 17 Nov 2018 19:44:15 +0900
with message-id <CAEQ9gEkFVfNRirs-sCQzjjo9zkcphdj-JoF_GovCiJmwDaZwAw at mail.gmail.com>
and subject line Re: [Pkg-privacy-maintainers] Bug#890238: torbrowser-launcher: Failed to launcher torbrowswer with permission denied error regarding dbus
has caused the Debian Bug report #890238,
regarding torbrowser-launcher: Failed to launcher torbrowswer with permission denied error regarding dbus
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 at bugs.debian.org
immediately.)


-- 
890238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890238
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Godspeed Dash <zhitaoli.hust at gmail.com>
Subject: torbrowser-launcher: Failed to launcher torbrowswer with permission denied error regarding dbus
Date: Mon, 12 Feb 2018 04:00:11 -0700
Size: 8598
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/f18dda9e/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Re: [Pkg-privacy-maintainers] Bug#890238: torbrowser-launcher: Failed to launcher torbrowswer with permission denied error regarding dbus
Date: Sat, 17 Nov 2018 19:44:15 +0900
Size: 5125
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/f18dda9e/attachment-0001.mht>

From owner at bugs.debian.org  Sat Nov 17 10:51:11 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 17 Nov 2018 10:51:11 +0000
Subject: [Pkg-privacy-maintainers] Bug#893308: marked as done ((Re)install
 leads to AttributeError: 'module' object has no attribute
 'OP_SINGLE_ECDH_USE')
References: <CAEQ9gEk2m9WmirspCqFat_VfhHOnBAhP0vdsFBtetwz+wgvYkQ@mail.gmail.com>
 <20180317213610.GA7657@debian>
Message-ID: <handler.893308.D893308.154245173422269.ackdone@bugs.debian.org>

Your message dated Sat, 17 Nov 2018 19:48:38 +0900
with message-id <CAEQ9gEk2m9WmirspCqFat_VfhHOnBAhP0vdsFBtetwz+wgvYkQ at mail.gmail.com>
and subject line Re: [Pkg-privacy-maintainers] Bug#893308: (Re)install leads to AttributeError: 'module' object has no attribute 'OP_SINGLE_ECDH_USE'
has caused the Debian Bug report #893308,
regarding (Re)install leads to AttributeError: 'module' object has no attribute 'OP_SINGLE_ECDH_USE'
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 at bugs.debian.org
immediately.)


-- 
893308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893308
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Georg Faerber <georg at riseup.net>
Subject: (Re)install leads to AttributeError: 'module' object has no attribute 'OP_SINGLE_ECDH_USE'
Date: Sat, 17 Mar 2018 22:36:10 +0100
Size: 6047
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/b37e4c6d/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Roger Shimizu <rosh at debian.org>
Subject: Re: [Pkg-privacy-maintainers] Bug#893308: (Re)install leads to AttributeError: 'module' object has no attribute 'OP_SINGLE_ECDH_USE'
Date: Sat, 17 Nov 2018 19:48:38 +0900
Size: 6214
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181117/b37e4c6d/attachment-0003.mht>

From ftpmaster at ftp-master.debian.org  Sat Nov 17 10:58:11 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 17 Nov 2018 10:58:11 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torbrowser-launcher_0.3.1-2~bpo9+1_source.changes
Message-ID: <E1gNyIl-0000wr-6q@usper.debian.org>

torbrowser-launcher_0.3.1-2~bpo9+1_source.changes uploaded successfully to localhost
along with the files:
  torbrowser-launcher_0.3.1-2~bpo9+1.dsc
  torbrowser-launcher_0.3.1-2~bpo9+1.debian.tar.xz
  torbrowser-launcher_0.3.1-2~bpo9+1_source.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Tue Nov 20 11:39:55 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 20 Nov 2018 11:39:55 +0000
Subject: [Pkg-privacy-maintainers]
 torbrowser-launcher_0.3.1-2~bpo9+1_source.changes ACCEPTED into
 stretch-backports
Message-ID: <E1gP4Nn-0000qg-IV@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Sat, 17 Nov 2018 19:55:11 +0900
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.3.1-2~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Roger Shimizu <rosh at debian.org>
Description:
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.3.1-2~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
Checksums-Sha1:
 200ed8f62a1b78c65fc53f5ea4f6485ec81de3e8 2202 torbrowser-launcher_0.3.1-2~bpo9+1.dsc
 cc5954634aaa37abad09aba47dc5548e4da5ea99 18580 torbrowser-launcher_0.3.1-2~bpo9+1.debian.tar.xz
 f9ef512eba0d002372c025647ad7fd1e3ef2c1eb 6265 torbrowser-launcher_0.3.1-2~bpo9+1_source.buildinfo
Checksums-Sha256:
 a890455521ae1144df6802e76df05494c3ebbf1c41f5f8c159cb8d65dca92dba 2202 torbrowser-launcher_0.3.1-2~bpo9+1.dsc
 355577f844b1404e4ff0a5ba64686eff10f44155cc6b294657c036e5eedae72c 18580 torbrowser-launcher_0.3.1-2~bpo9+1.debian.tar.xz
 2ffc3304f0a789a72bd7c11e5e8ff1d95c49a5d0385140f5ab91cc95fe3b135c 6265 torbrowser-launcher_0.3.1-2~bpo9+1_source.buildinfo
Files:
 0533972e71d6b103ddc2b0709ecee10b 2202 contrib/web optional torbrowser-launcher_0.3.1-2~bpo9+1.dsc
 7e1508a188a9238be77ced90abb7ccb3 18580 contrib/web optional torbrowser-launcher_0.3.1-2~bpo9+1.debian.tar.xz
 56e86901f0dfa5e81609c3dcdc9f7bff 6265 contrib/web optional torbrowser-launcher_0.3.1-2~bpo9+1_source.buildinfo

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

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAlvv86QQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qIRYD/47xCoIKVtlGFkmK3ThsexPZJOrTDsEqUcq
zVCTLi/ukJ9pcLOV7RIkK7Uecmp4c9DHVE03M4Y2Jwk78xStbIhCGpYPyyjHMwbq
xerBxlUBYzqbuwKcXaWu6wvYZXP7zW5jXhd4agh+aVdPdHwmD6VmlMq1MukqEfHp
uU4jULnoaBdN4RKH8DKPM03gA0BOHEYlH9BQJ1UZiBYw0+NC+mhfXL46YCRAUNJ0
eofef2xIfQAsgyTElZDTCHwhn36OdHPbZ0gihQancWfwwMY7czY2H/7HXun5AC/X
IyfgHYtxRSpQ+zALjyDtXI80bQe6A7cz5zg/Yg34Vqkj9gBXn+B/G6gUk7g2JYvJ
aZppU8PDn8WUzUb6iK66ppBPjo5cgXLpAHUwQCaCaBJXE6hUhnMP1F71mvRhN5te
Bk9Qw02aJNxgT5GjUTvgn0qcfw9kvU9JilIpln9mkVdl3nh68VlOtNcB0jTwZWm8
1ZZ7BEL4GFGUTKsWo7k8rQgaupkUERCvlzo3ZEwcFeQlzQhrf1dfjWiD6RsMJsEd
rWUpkNF4u5C887dqFxfhDw9xIDuYkNQZnOJXs8GwWcjIVPKt2153U0ZAHz0cmzDk
n0GLnmIrmzdyk4Nogl8/zA2Pg4tYbznYo2rUHEZ5uhYNINCc1e6C0UouwjYxH7Gh
3eNpTjTxeA==
=1Q9A
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From noreply at release.debian.org  Fri Nov 23 04:39:26 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Fri, 23 Nov 2018 04:39:26 +0000
Subject: [Pkg-privacy-maintainers] torbrowser-launcher 0.3.1-2 MIGRATED to
 testing
Message-ID: <E1gQ3FW-0005hd-0x@respighi.debian.org>

FYI: The status of the torbrowser-launcher source package
in Debian's testing distribution has changed.

  Previous version: 0.3.1-1
  Current version:  0.3.1-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From owner at bugs.debian.org  Tue Nov 27 12:51:06 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 27 Nov 2018 12:51:06 +0000
Subject: [Pkg-privacy-maintainers] Processed: your mail
References: <30f64555-6fa4-6e39-ff09-d3011261ed08@debian.org>
Message-ID: <handler.s.C.15433230309412.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tag 895903 upstream
Bug #895903 [torsocks] [torsocks] AAAA replies from Tor not handled
Added tag(s) upstream.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
895903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895903
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ftpmaster at ftp-master.debian.org  Tue Nov 27 13:49:28 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 27 Nov 2018 13:49:28 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 torsocks_2.3.0-1_amd64.changes
Message-ID: <E1gRdk0-0000PT-1v@usper.debian.org>

torsocks_2.3.0-1_amd64.changes uploaded successfully to localhost
along with the files:
  torsocks_2.3.0-1.dsc
  torsocks_2.3.0.orig.tar.xz
  torsocks_2.3.0-1.debian.tar.xz
  torsocks-dbgsym_2.3.0-1_amd64.deb
  torsocks_2.3.0-1_amd64.buildinfo
  torsocks_2.3.0-1_amd64.deb

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From owner at bugs.debian.org  Tue Nov 27 14:15:11 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 27 Nov 2018 14:15:11 +0000
Subject: [Pkg-privacy-maintainers] Processed: your mail
References: <15f149d1-3d83-d793-62d3-2c2bd04506f1@debian.org>
Message-ID: <handler.s.C.154332796214651.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> forwarded 895903 https://trac.torproject.org/projects/tor/ticket/28627
Bug #895903 [torsocks] [torsocks] AAAA replies from Tor not handled
Set Bug forwarded-to-address to 'https://trac.torproject.org/projects/tor/ticket/28627'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
895903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895903
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ulrike at debian.org  Tue Nov 27 14:17:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Tue, 27 Nov 2018 14:17:00 +0000
Subject: [Pkg-privacy-maintainers] Bug#895903: [torsocks] AAAA replies from
 Tor not handled
References: <edbf9b66-df9b-e9ba-64e5-e303a8f73fe8@kevinsteen.net>
Message-ID: <0dc35b80-77d5-24ea-d6e6-c2ba5a49b4b0@debian.org>

Hi,

thank you for this bug report. I confirm this behavior and thus I've
forwarded it to Tor's bugtracker.

Cheers
Ulrike


From ftpmaster at ftp-master.debian.org  Tue Nov 27 15:12:19 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Tue, 27 Nov 2018 15:12:19 +0000
Subject: [Pkg-privacy-maintainers] torsocks_2.3.0-1_amd64.changes ACCEPTED
 into unstable
Message-ID: <E1gRf2B-0007rU-QX@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Tue, 27 Nov 2018 13:00:20 +0100
Source: torsocks
Binary: torsocks
Architecture: source amd64
Version: 2.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Ulrike Uhlig <ulrike at debian.org>
Description:
 torsocks   - use SOCKS-friendly applications with Tor
Changes:
 torsocks (2.3.0-1) unstable; urgency=medium
 .
   * New upstream version.
   * debian/control:
     - update VCS fields.
   * debian/README.source:
     - update instructions.
Checksums-Sha1:
 118d990fa403ebc8d2ce7379093ce6cc0f282e50 2059 torsocks_2.3.0-1.dsc
 18dcef8b7f0a9b63f9c7b5f8159d96ca122f1377 313072 torsocks_2.3.0.orig.tar.xz
 5b93911c4bb1c2722b2aaf9172f418243de1e914 10644 torsocks_2.3.0-1.debian.tar.xz
 510238e0de7c9064a027d98219118cb4d3f4d77d 99240 torsocks-dbgsym_2.3.0-1_amd64.deb
 b334010204de03339bf31721bba8855e9ff5b8af 6080 torsocks_2.3.0-1_amd64.buildinfo
 46684b5ddd9885cfc2d5b993e005bb0b64b00d1f 75096 torsocks_2.3.0-1_amd64.deb
Checksums-Sha256:
 c4d8bd6be820f8d4bdf8d24791670497bdddc902fe3951526fec3c1a8a748959 2059 torsocks_2.3.0-1.dsc
 b9f1b981d6b3fd4e1820de1eee325f8a7038c84765d5a6cd9af12571d5cc3622 313072 torsocks_2.3.0.orig.tar.xz
 2a84b0a21497fe04725b89514fbe03e65ededd33bb965f63cf6ec8f2f467466c 10644 torsocks_2.3.0-1.debian.tar.xz
 7e23d83e0b2c45879dd1294cb42171070cccc9c7a776d3ce6bcf5b1ccd0ebdf1 99240 torsocks-dbgsym_2.3.0-1_amd64.deb
 8892913e8c0739140edc8a843cbcc9711b0245d99fb14069726e190adb390eb4 6080 torsocks_2.3.0-1_amd64.buildinfo
 eccc1b204d9ce85edc4d22d2d8c7502bec0143d7e72f03d748d5eaa319c2faea 75096 torsocks_2.3.0-1_amd64.deb
Files:
 76324c0bb54158047786f4159e79069a 2059 net optional torsocks_2.3.0-1.dsc
 146ed4f2d6a1a110d8ce8a5f7937d87a 313072 net optional torsocks_2.3.0.orig.tar.xz
 32046bb448b81c6f820fbe9e92572746 10644 net optional torsocks_2.3.0-1.debian.tar.xz
 7521fdb47d6a16c563b9e91c111b12ee 99240 debug extra torsocks-dbgsym_2.3.0-1_amd64.deb
 9479b72e81f0c7d5848dd5d7e77cc06d 6080 net optional torsocks_2.3.0-1_amd64.buildinfo
 35a69b771e5298545a5d731f9f6b30e8 75096 net optional torsocks_2.3.0-1_amd64.deb

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

iQJGBAEBCgAwFiEE7eP0RD800mGVFNeQsUuww42GHPEFAlv9REYSHHVscmlrZUBk
ZWJpYW4ub3JnAAoJELFLsMONhhzxqOsP/iM4uGya3FbJRADJJqUcGrevUITIAgqe
KO0OHCsBoYw2H/Lwc0pK8ENR/TmUkPOY03PmOJQFg+fPfkJBXgU3KI7E+Zek7kA8
wekUgy8wr3HtJJtUWSOilJ1t9QQDr2VUb0EwQ7xmIHFXt+9bd7wmYBvsiYQV2+DR
gvUtdNy6llmBeYaoze8+XyToAaRqdIdQt4W7qI0Zv3QUqS9BGiPqj2Spa3LpoZBa
HVCPWXapjcrtmxlcdY+OnKV5z77xBiTZAFdV3W6fCX1PzYxZyd822+lHJ8UVG5a/
s4YJraCjErYdzHMyYa6SBB/hSAHE2hiiO/KkT4b4OR+CoeVE0HSWMP4ArXDsSkD2
kZ9eJU09chQObv5jDv5+1L43a+/fb1pHgjivlth8PY1LO54+Fy0D1upbFLgZhSWk
DUFYsARZ3GYqlbvBsucgMXpZ31lgDHzYesMA/WuSS/G6cxjMaU0T6Zl8hikWkSgO
YUKSGhK+ICR1oWrUNaq6nUTVDV9N3fbAqCiD3rkxrUmmKbTwqldkKKf/H7P0pkUY
obHWIMt/4/N7xQPdljgnTECR8aqGgnxEWVpxv++ncKJxjlhUAsq3luttem/99S9h
FzJQCzetiJGuv7zw264ceEX6M0jKzc3SGNA0PmBGUXyh0aKNqZmutf86uMclDjVJ
iBVdaUK5+byp
=j844
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Tue Nov 27 15:33:08 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 27 Nov 2018 15:33:08 +0000
Subject: [Pkg-privacy-maintainers] Processed: your mail
References: <b36effe0-7a75-a855-4cd1-84fe0068fff3@451f.org>
Message-ID: <handler.s.C.154333267220657.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> close 705777
Bug #705777 [torsocks] Please add a way to disable tordns
Marked Bug as done
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
705777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705777
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From owner at bugs.debian.org  Tue Nov 27 15:36:03 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 27 Nov 2018 15:36:03 +0000
Subject: [Pkg-privacy-maintainers] Processed: your mail
References: <f2cc89a1-7127-dd5e-b4ac-1e1503098844@451f.org>
Message-ID: <handler.s.C.154333286222257.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tag 870763 + fixed pending
Bug #870763 [src:torsocks] torsocks: Package description makes safety promises that upstream prefers not to
Added tag(s) fixed and pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
870763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870763
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ulrike at debian.org  Tue Nov 27 15:38:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Tue, 27 Nov 2018 15:38:00 +0000
Subject: [Pkg-privacy-maintainers] Bug#865368: torsocks: procmail spawned by
 mpop in torsocks fails with "Operation not permitted"
References: <149798253703.20877.9514493553345872209.reportbug@viper>
Message-ID: <467c78d1-9ea9-3b7d-0906-83ce5b3daae3@debian.org>

Hi Nick,

does this still occur?

It could be a problem related to multiprocesses in which procmail does
"socket passing" and which torsocks might not handle well, or at all.

mpop seems to have examples working with Tor though:
https://www.mankier.com/1/mpop#Examples Have you contacted the authors
of this software to ask for advice?

Cheers!
u.


From ulrike at debian.org  Tue Nov 27 15:44:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Tue, 27 Nov 2018 15:44:00 +0000
Subject: [Pkg-privacy-maintainers] Bug#895903: [torsocks] AAAA replies from
 Tor not handled
References: <edbf9b66-df9b-e9ba-64e5-e303a8f73fe8@kevinsteen.net>
Message-ID: <c45941bc-f3c4-7016-6863-9234ff8dd42d@debian.org>

This seems to be due to a limit in torsocks that has not yet been
resolved upstream: to resolve an IPv6 address, Tor must listen on the
IPv6 SocksPort and the request must be sent to this SocksPort. As far as
i understand it.


From owner at bugs.debian.org  Wed Nov 28 09:27:06 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 28 Nov 2018 09:27:06 +0000
Subject: [Pkg-privacy-maintainers] Processed: found 905516 in 14,
 found 771085 in 3.30.2-1, found 782155 in 2.02+dfsg1-8,
 found 858954 in 0.7.6.0 ...
References: <1543397151-2186-bts-anbe@debian.org>
Message-ID: <handler.s.C.154339715615927.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> found 905516 14
Bug #905516 [openstack-cluster-installer-poc] openstack-cluster-installer-poc: unowned directories after purge: /var/lib/openstack-cluster-installer-poc/{runtime,templates}/
Marked as found in versions openstack-cluster-installer/14.
> found 771085 3.30.2-1
Bug #771085 [gdm3] gdm3: unowned symlink after purge (policy 6.8, 10.8): /etc/systemd/system/display-manager.service
Marked as found in versions gdm3/3.30.2-1.
> found 782155 2.02+dfsg1-8
Bug #782155 [grub-pc] grub-pc: unowned files after purge (policy 6.8, 10.8): /boot/grub/unicode.pf2
Marked as found in versions grub2/2.02+dfsg1-8.
> found 858954 0.7.6.0
Bug #858954 [diaspora-common] diaspora-common: unowned directories after purge: /var/cache/diaspora/, /var/lib/diaspora-common/, /var/log/diaspora/
Marked as found in versions diaspora-installer/0.7.6.0.
> found 782156 2.02+dfsg1-8
Bug #782156 [grub-xen] grub-xen: unowned files after purge (policy 6.8, 10.8): /boot/grub/{locale, x86_64-xen}/* and some more
Marked as found in versions grub2/2.02+dfsg1-8.
> found 909489 1.0.2-1
Bug #909489 [sbws] sbws: unowned directory after purge: /var/lib/sbws/
Marked as found in versions sbws/1.0.2-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
771085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771085
782155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782155
782156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782156
858954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858954
905516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905516
909489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909489
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From noreply at release.debian.org  Mon Dec  3 04:39:15 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Mon, 03 Dec 2018 04:39:15 +0000
Subject: [Pkg-privacy-maintainers] torsocks 2.3.0-1 MIGRATED to testing
Message-ID: <E1gTg0p-000789-0t@respighi.debian.org>

FYI: The status of the torsocks source package
in Debian's testing distribution has changed.

  Previous version: 2.2.0-2
  Current version:  2.3.0-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From reproducible-builds at lists.alioth.debian.org  Thu Dec  6 00:40:50 2018
From: reproducible-builds at lists.alioth.debian.org (Reproducible builds folks)
Date: Thu,  6 Dec 2018 00:40:50 +0000 (UTC)
Subject: [Pkg-privacy-maintainers] pyptlib: status change on
 tests.reproducible-builds.org/debian
Message-ID: <20181206004050.71A281F34D@jenkins.debian.net>

2018-12-05 06:34 https://tests.reproducible-builds.org/debian/unstable/amd64/pyptlib changed from reproducible -> FTBFS


From weasel at debian.org  Fri Dec  7 11:40:00 2018
From: weasel at debian.org (Peter Palfrader)
Date: Fri, 7 Dec 2018 11:40:00 +0000
Subject: [Pkg-privacy-maintainers] Bug#915859: uses a fixed filename in /tmp
Message-ID: <20181207114000.GA28729@sarek.noreply.org>

Package: onionshare
Version: 1.3-1
Severity: grave
Tags: security

onionshare uses /tmp/onionshare_server.log as a logfile with --debug.

in onionshare/web.py:
| def debug_mode():
|     temp_dir = tempfile.gettempdir()
|     log_handler = logging.FileHandler(
|         os.path.join(temp_dir, 'onionshare_server.log'))

tempfile.gettempdir() returns /tmp.  It does not give you a
dedicated temp-directory.  It is not mkdtemp.

-- 
                            |  .''`.       ** Debian **
      Peter Palfrader       | : :' :      The  universal
 https://www.palfrader.org/ | `. `'      Operating System
                            |   `-    https://www.debian.org/


From intrigeri at debian.org  Fri Dec  7 12:04:57 2018
From: intrigeri at debian.org (intrigeri)
Date: Fri, 07 Dec 2018 13:04:57 +0100
Subject: [Pkg-privacy-maintainers] Bug#915859: Bug#915859: uses a fixed
 filename in /tmp
In-Reply-To: <20181207114000.GA28729@sarek.noreply.org>
References: <20181207114000.GA28729@sarek.noreply.org>
 <20181207114000.GA28729@sarek.noreply.org>
Message-ID: <87ftv9wniu.fsf@boum.org>

Hi,

Peter Palfrader:
> onionshare uses /tmp/onionshare_server.log as a logfile with --debug.

Good catch!

While that code obviously conflicts with basic secure programming best
practices, it seems to me that the default settings of the
fs.protected_symlinks and fs.protected_hardlinks sysctls protect
Debian users against exploitation, so I find RC severity hard to
justify given this only affects users who manually pass --debug under
a non-default sysctl/kernel configuration.

In any case, this should be fixed :)

Cheers,
-- 
intrigeri


From weasel at debian.org  Fri Dec  7 12:06:38 2018
From: weasel at debian.org (Peter Palfrader)
Date: Fri, 7 Dec 2018 12:06:38 +0000
Subject: [Pkg-privacy-maintainers] Bug#915859: Bug#915859: uses a fixed
 filename in /tmp
In-Reply-To: <87ftv9wniu.fsf@boum.org>
References: <20181207114000.GA28729@sarek.noreply.org>
 <87ftv9wniu.fsf@boum.org> <20181207114000.GA28729@sarek.noreply.org>
Message-ID: <20181207120638.GA1802@sarek.noreply.org>

On Fri, 07 Dec 2018, intrigeri wrote:

> Hi,
> 
> Peter Palfrader:
> > onionshare uses /tmp/onionshare_server.log as a logfile with --debug.
> 
> Good catch!
> 
> While that code obviously conflicts with basic secure programming best
> practices, it seems to me that the default settings of the
> fs.protected_symlinks and fs.protected_hardlinks sysctls protect
> Debian users against exploitation, so I find RC severity hard to
> justify given this only affects users who manually pass --debug under
> a non-default sysctl/kernel configuration.
> 
> In any case, this should be fixed :)

In addition to the security issues of bad tempfile handling, it causes
onionshare to break for me as on this system several users run
onionshare.

-- 
                            |  .''`.       ** Debian **
      Peter Palfrader       | : :' :      The  universal
 https://www.palfrader.org/ | `. `'      Operating System
                            |   `-    https://www.debian.org/


From weasel at debian.org  Fri Dec  7 13:12:00 2018
From: weasel at debian.org (Peter Palfrader)
Date: Fri, 7 Dec 2018 13:12:00 +0000
Subject: [Pkg-privacy-maintainers] Bug#915869: sometimes get backtrace on
 shutdown
Message-ID: <20181207131200.GA12584@sarek.noreply.org>

Package: onionshare
Version: 1.3-1
Severity: normal

sometimes onionshare throws an exception on shutdown:

| Onionshare 1.3 | https://onionshare.org/
| [Dec 07 2018 13:55:25] Settings.__init__
| [Dec 07 2018 13:55:25] Onion.__init__
| [Dec 07 2018 13:55:25] Onion.connect
| [Dec 07 2018 13:55:25] Settings.__init__
| [Dec 07 2018 13:55:25] Settings.load
| Connecting to the Tor network: 5% - Connecting to directory server
| Connecting to Tor is taking too long. Maybe your computer is offline, or your clock isn't accurate.
| Exception ignored in: <finalize object at 0x7f27c93361f0; dead>
| Traceback (most recent call last):
|   File "/usr/lib/python3.5/weakref.py", line 548, in __call__
|     return info.func(*info.args, **(info.kwargs or {}))
|   File "/usr/lib/python3.5/tempfile.py", line 936, in _cleanup
|     _rmtree(name)
|   File "/usr/lib/python3.5/shutil.py", line 480, in rmtree
|     _rmtree_safe_fd(fd, path, onerror)
|   File "/usr/lib/python3.5/shutil.py", line 438, in _rmtree_safe_fd
|     onerror(os.unlink, fullname, sys.exc_info())
|   File "/usr/lib/python3.5/shutil.py", line 436, in _rmtree_safe_fd
|     os.unlink(name, dir_fd=topfd)
| FileNotFoundError: [Errno 2] No such file or directory: 'state.tmp'


Cheers,
-- 
                            |  .''`.       ** Debian **
      Peter Palfrader       | : :' :      The  universal
 https://www.palfrader.org/ | `. `'      Operating System
                            |   `-    https://www.debian.org/


From carnil at debian.org  Fri Dec  7 15:51:05 2018
From: carnil at debian.org (Salvatore Bonaccorso)
Date: Fri, 7 Dec 2018 16:51:05 +0100
Subject: [Pkg-privacy-maintainers] Bug#915859: Bug#915859: uses a fixed
 filename in /tmp
In-Reply-To: <20181207120638.GA1802@sarek.noreply.org>
References: <20181207114000.GA28729@sarek.noreply.org>
 <87ftv9wniu.fsf@boum.org> <20181207114000.GA28729@sarek.noreply.org>
 <20181207120638.GA1802@sarek.noreply.org>
 <20181207114000.GA28729@sarek.noreply.org>
Message-ID: <20181207155105.GA19097@eldamar.local>

Conrol: retitle -1 onionshare: CVE-2018-19960: uses a fixed filename in /tmp

Hi,

So it will additionally allow potentially denial of service on
multi-user systems. 

Not sure if the grave severity is warranted, though, will leave this
discussion to you both :)

For tracking the issue, I have requested a CVE from MITRE, which got
assigned CVE-2018-19960.

Regards,
Salvatore


From owner at bugs.debian.org  Tue Dec 11 10:45:10 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 11 Dec 2018 10:45:10 +0000
Subject: [Pkg-privacy-maintainers] Processed: your mail
References: <a72f4ba9-f3f4-09f1-3953-602badf96999@debian.org>
Message-ID: <handler.s.C.154452501532000.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tag 915859 upstream
Bug #915859 [onionshare] uses a fixed filename in /tmp
Added tag(s) upstream.
> forwarded 915859 https://github.com/micahflee/onionshare/issues/837
Bug #915859 [onionshare] uses a fixed filename in /tmp
Set Bug forwarded-to-address to 'https://github.com/micahflee/onionshare/issues/837'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
915859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915859
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ulrike at debian.org  Wed Dec 12 15:49:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Wed, 12 Dec 2018 15:49:00 +0000
Subject: [Pkg-privacy-maintainers] Bug#915859: Bug#915859: uses a fixed
 filename in /tmp
In-Reply-To: <20181207155105.GA19097@eldamar.local>
References: <20181207114000.GA28729@sarek.noreply.org>
 <87ftv9wniu.fsf@boum.org> <20181207114000.GA28729@sarek.noreply.org>
 <20181207120638.GA1802@sarek.noreply.org>
 <20181207114000.GA28729@sarek.noreply.org>
 <20181207155105.GA19097@eldamar.local>
 <20181207114000.GA28729@sarek.noreply.org>
Message-ID: <c5ec9d8d-303f-5fe0-bcde-439de78e47f6@debian.org>

Hi!

Salvatore Bonaccorso:

> So it will additionally allow potentially denial of service on
> multi-user systems. 
> 
> Not sure if the grave severity is warranted, though, will leave this
> discussion to you both :)

Ack, grave sounds a bit grave.

> For tracking the issue, I have requested a CVE from MITRE, which got
> assigned CVE-2018-19960.

Thank you.

I've asked upstream to fix it yesterday, and they did. So I'll upload a
newer version of onionshare a bit later this week (probably not today
though).

Cheers!
u.


From scootergrisen at gmail.com  Wed Dec 12 16:12:42 2018
From: scootergrisen at gmail.com (scootergrisen)
Date: Wed, 12 Dec 2018 17:12:42 +0100
Subject: [Pkg-privacy-maintainers] Delete da_DK.po from MAT package
Message-ID: <9f6d3a7f-f166-e1da-2916-a0437ae8d479@gmail.com>

Any chance i can have the untranslated po/da_DK.po translation file 
deleted from MAT?
https://packages.debian.org/stretch/mat

mat_0.6.1.orig.tar.xz contains both da.po and da_DK.po but i would like 
to only have da.po.

da.po is translated apart from 1 string.
da_DK.po have no translated strings.



If possible i would also like the one untranslated string "Cant read 
file" to be translated to "Kan ikke læse fil" in the da.po file.

I think i asked the MAT developer about this but MAT is not maintained 
any more.



Reason i ask is so all the danish translations are using "da" instad of 
a mixture of "da" and "da_DK".


From ftpmaster at ftp-master.debian.org  Wed Dec 12 22:12:09 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 12 Dec 2018 22:12:09 +0000
Subject: [Pkg-privacy-maintainers] Processing of mat_0.6.1-5_amd64.changes
Message-ID: <E1gXCjh-00078A-5t@usper.debian.org>

mat_0.6.1-5_amd64.changes uploaded successfully to localhost
along with the files:
  mat_0.6.1-5.dsc
  mat_0.6.1-5.debian.tar.xz
  mat_0.6.1-5_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ftpmaster at ftp-master.debian.org  Wed Dec 12 22:19:46 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 12 Dec 2018 22:19:46 +0000
Subject: [Pkg-privacy-maintainers] mat_0.6.1-5_amd64.changes ACCEPTED into
 unstable
Message-ID: <E1gXCr4-0006aD-Di@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Wed, 12 Dec 2018 17:02:06 -0500
Source: mat
Binary: mat
Architecture: source
Version: 0.6.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Daniel Kahn Gillmor <dkg at fifthhorseman.net>
Description:
 mat        - Metadata anonymisation toolkit
Changes:
 mat (0.6.1-5) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * Remove unnecessary 'Testsuite: autopkgtest' header.
 .
   [ Daniel Kahn Gillmor ]
   * fix up danish translation
   * correct Vcs-* metadata
   * convert to dh 11
   * Remove unnecessary X-Python{,3}-Version field in debian/control.
   * Re-export upstream signing key without extra signatures.
   * avoid running tests if DEB_BUILD_OPTIONS includes nocheck
   * move to pybuild
   * no need for xvfb if we are not running the test suite
   * explicitly list depends in the autopkgtest
   * Standards-Version: bump to 4.2.1 (no changes needed)
   * clean up po/MAT.pot after build
   * added myself to uploaders
Checksums-Sha1:
 58696c2c57b74ba94a2645dc947384d82e2dc55e 1730 mat_0.6.1-5.dsc
 f9334b5dda050d0662230924870284b84ddc1c42 14656 mat_0.6.1-5.debian.tar.xz
 25effc249427ff507e2c1e0a9c921edc7677f0da 9426 mat_0.6.1-5_amd64.buildinfo
Checksums-Sha256:
 436a54aac9a0ec3cfc0211d35470aa8d2bd6787fa34f6aebd72750245a4a690e 1730 mat_0.6.1-5.dsc
 ddcf30191ff6e00f34d2fbcd69e14d60ab29e699c31535560ae31340657668d1 14656 mat_0.6.1-5.debian.tar.xz
 d5105992e6bff4908b48372e7e2d45937bcc89eeb3291e3a9c92d8b8b4bc63ce 9426 mat_0.6.1-5_amd64.buildinfo
Files:
 8d0fce5602081c29346e26341f407b07 1730 python optional mat_0.6.1-5.dsc
 faecde84160198e31c9272ee7ff87f42 14656 python optional mat_0.6.1-5.debian.tar.xz
 00729c1a75ee521bf73659480062a4ae 9426 python optional mat_0.6.1-5_amd64.buildinfo

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

iHQEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCXBGGwQAKCRBsHx7ezFD6
Uy4DAPd7HL4Pkl8Pca60AtHyHRmaRRksH0QVet3ADqa3oof8AP4jPUeMfrGIvFkV
OUnJNcG8Rauv6CVWbXnN5FE0VRqnCg==
=TxFs
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From dkg at fifthhorseman.net  Wed Dec 12 22:11:32 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Wed, 12 Dec 2018 17:11:32 -0500
Subject: [Pkg-privacy-maintainers] Delete da_DK.po from MAT package
In-Reply-To: <9f6d3a7f-f166-e1da-2916-a0437ae8d479@gmail.com>
References: <9f6d3a7f-f166-e1da-2916-a0437ae8d479@gmail.com>
Message-ID: <871s6mv1ij.fsf@fifthhorseman.net>

On Wed 2018-12-12 17:12:42 +0100, scootergrisen at gmail.com wrote:
> Any chance i can have the untranslated po/da_DK.po translation file 
> deleted from MAT?
> https://packages.debian.org/stretch/mat
>
> mat_0.6.1.orig.tar.xz contains both da.po and da_DK.po but i would like 
> to only have da.po.
>
> da.po is translated apart from 1 string.
> da_DK.po have no translated strings.
>
> If possible i would also like the one untranslated string "Cant read 
> file" to be translated to "Kan ikke læse fil" in the da.po file.
>
> I think i asked the MAT developer about this but MAT is not maintained 
> any more.
>
> Reason i ask is so all the danish translations are using "da" instad of 
> a mixture of "da" and "da_DK".

This is type of thing probably best reported in the future as an issue
in the debian BTS (e.g. using the "reportbug" tool to file the issue).
that ensures that we can keep track of it.

The changes that you're asking for make sense to me, and i've gone ahead
and implemented them in debian, and have uploaded 0.6.1-5 (with a bit
more cleanup of the debian packaging as well).

In the course of doing this, i noticed that the debian packaging Vcs on
salsa was in a bit of a messy state.  to fix the worst problems, i did
two things:

 * i refreshed the pristine-tar delta for 0.6.1 -- i don't know why it
   was wrong earlier.

 * i merged the "upstream" branch into the "master" branch -- "master"
   had only merged 0.6, and not 0.6.1 for some reason.

It now builds fine via gbp buildpackage, at least.

Regards,

       --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181212/e6ee3305/attachment.sig>

From dkg at fifthhorseman.net  Thu Dec 13 13:37:10 2018
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Thu, 13 Dec 2018 08:37:10 -0500
Subject: [Pkg-privacy-maintainers] Delete da_DK.po from MAT package
In-Reply-To: <d0ddc201-a6f3-61cd-68aa-daf77ca27875@gmail.com>
References: <9f6d3a7f-f166-e1da-2916-a0437ae8d479@gmail.com>
 <871s6mv1ij.fsf@fifthhorseman.net>
 <d0ddc201-a6f3-61cd-68aa-daf77ca27875@gmail.com>
Message-ID: <87imzx4kft.fsf@fifthhorseman.net>

On Thu 2018-12-13 07:38:32 +0100, scootergrisen wrote:
> Thank you.

you're welcome!  I recommend switching to mat2, btw, since as you
noticed, mat itself is currently unmaintained.

         --dkg


From ftpmaster at ftp-master.debian.org  Thu Dec 13 16:07:35 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 13 Dec 2018 16:07:35 +0000
Subject: [Pkg-privacy-maintainers] Processing of
 onionshare_1.3.2-1_amd64.changes
Message-ID: <E1gXTWR-0000eG-Ua@usper.debian.org>

onionshare_1.3.2-1_amd64.changes uploaded successfully to localhost
along with the files:
  onionshare_1.3.2-1.dsc
  onionshare_1.3.2.orig.tar.gz
  onionshare_1.3.2-1.debian.tar.xz
  onionshare_1.3.2-1_all.deb
  onionshare_1.3.2-1_amd64.buildinfo

Greetings,

	Your Debian queue daemon (running on host usper.debian.org)


From ulrike at debian.org  Thu Dec 13 16:17:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Thu, 13 Dec 2018 16:17:00 +0000
Subject: [Pkg-privacy-maintainers] Bug#849227: GUI ignores server stay-open
 checkbox state
References: <20161223205605.12954.69099.reportbug@feeble.seestieto.com>
Message-ID: <7bd87aa5-82a5-3a7a-3ed1-6500730e6833@debian.org>

This is fixed in the current version of Onionshare (> 1.3).


From owner at bugs.debian.org  Thu Dec 13 16:18:07 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 13 Dec 2018 16:18:07 +0000
Subject: [Pkg-privacy-maintainers] Processed: your mail
References: <a67ea8a6-1c9a-b923-15c2-e8cc99c5c923@debian.org>
Message-ID: <handler.s.C.15447178298575.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> close 849227
Bug #849227 [onionshare] GUI ignores server stay-open checkbox state
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
849227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849227
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ftpmaster at ftp-master.debian.org  Thu Dec 13 16:20:06 2018
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Thu, 13 Dec 2018 16:20:06 +0000
Subject: [Pkg-privacy-maintainers] onionshare_1.3.2-1_amd64.changes ACCEPTED
 into unstable
Message-ID: <E1gXTiY-0009dk-VA@fasolo.debian.org>



Accepted:

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

Format: 1.8
Date: Thu, 13 Dec 2018 16:20:37 +0100
Source: onionshare
Binary: onionshare
Architecture: source all
Version: 1.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers <pkg-privacy-maintainers at lists.alioth.debian.org>
Changed-By: Ulrike Uhlig <ulrike at debian.org>
Description:
 onionshare - Share a file over Tor Hidden Services anonymously and securely
Closes: 915859
Changes:
 onionshare (1.3.2-1) unstable; urgency=medium
 .
   * New upstream version. (Closes: #915859.)
     - In debug mode, stop saving flask debug log in /tmp, where all users can
       access it
     - Updated Tor to 0.2.3.10.
   * debian/README.source:
     - Improve instructions for updating and building this package.
   * debian/gbp.conf:
     - Improve rules.
   * debian/rules:
     - Adapt.
Checksums-Sha1:
 83ec2c6d3765cf4e59af5e0ba8d76a7150c41689 2170 onionshare_1.3.2-1.dsc
 e0ddce8e92ea21a745fe40998acdf01c94696657 436856 onionshare_1.3.2.orig.tar.gz
 86c5f0cd693d00b4477094e41005f79214bee566 5676 onionshare_1.3.2-1.debian.tar.xz
 0f9d47d1a3fd2917e2a73260f4c7e199665432be 104636 onionshare_1.3.2-1_all.deb
 a4bcdc442319cb9840baf5d37e05928136168169 12724 onionshare_1.3.2-1_amd64.buildinfo
Checksums-Sha256:
 f94d730256a589d6430f8d5d8b6bd1f3b263509c416b14f5ee4c5af2e0c09865 2170 onionshare_1.3.2-1.dsc
 deb6d2c25a9c0fdb0f37d9ab38a168b028256a4b6015fe6b678224bf33465042 436856 onionshare_1.3.2.orig.tar.gz
 e2c5b6a0c94d7fffbe62b25d3ef3df3dd325a456d2d9dfd385b9f0bdf751961b 5676 onionshare_1.3.2-1.debian.tar.xz
 65dbf0c079a084c2c649cd84cd20d472110fdced0690c90e36f640bb5176578f 104636 onionshare_1.3.2-1_all.deb
 f45976b955b7af2bbaea1ea6f746f4a7168c64ffcea9f98f71f02306f1b5d329 12724 onionshare_1.3.2-1_amd64.buildinfo
Files:
 0f60ecbae30490e0da13557ee9cb72c0 2170 net optional onionshare_1.3.2-1.dsc
 5316de2e366a9c9cd182742f995276f5 436856 net optional onionshare_1.3.2.orig.tar.gz
 0ed8aec88224caddad674438bf1e9c66 5676 net optional onionshare_1.3.2-1.debian.tar.xz
 900fbcd2e2673be0262533391f7a2c37 104636 net optional onionshare_1.3.2-1_all.deb
 b355a507e99549774af95e3c828e80d1 12724 net optional onionshare_1.3.2-1_amd64.buildinfo

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

iQJGBAEBCgAwFiEE7eP0RD800mGVFNeQsUuww42GHPEFAlwSfuYSHHVscmlrZUBk
ZWJpYW4ub3JnAAoJELFLsMONhhzx8e0P+we2TO5xvW1gfcI5DVdqI5TtpklXxLmj
k5wRSCj9I+MxzoHfoqyxJIJ3psJQFG7mJBCMtvcTFq12YOPu7m2efckq/vzd5upu
VrQbnrytzPKkZAD7FXtH4CWQzXq2IKjsPJGehNyED+bzl6ATx8Oa4cbW0dv1n4jP
A7RaSdOZsko+FUuFUMMuodwHz3+XjQN7cw5mYOTiTDJXj/XaItVgo9M8Hb5R32vx
6fd9tEAITn9y7LFiUOzTmEbB2yyWSKg5zFXdM0HRnyWAZqirVqOvc1y5SMIygWe0
j+uGKx+GNaUrECQJExc0/zQEYPajmx8128ntIvFYdEdQLD4nsezV9JT3UQtcas6q
na6ETCFFI0pwrvmT/uIGDO1ugYPrReXRm5LpW7tpOgAcJ0TmdmoI9s7A9FYPmA9W
eJMtgMeCnwUdN8syb81PAb/Fk0QECIbm4FVPU+Vz/4TsqGSHZuDNMeXBFCKCccOt
N11HhdMBDSpn9acbB5XyBWvplSSNfc4sVSXBMdO1PaHGujKc/5mGNdaM4GJnDCZX
rpqafVBOgeVzcdDpevLxBBIht9vw+ZL4URq0nk6ZEmTgMcGaU5MTKBJutcKacziq
88YkiAtZPgNeNcS5fYMjhOPQbhR6iuSUvPkEKoOG/PS9t3gEr5sfbwsEmADXqMb4
DJP5F7WJPmK7
=BUFT
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Thu Dec 13 16:21:03 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 13 Dec 2018 16:21:03 +0000
Subject: [Pkg-privacy-maintainers] Bug#915859: marked as done (uses a fixed
 filename in /tmp)
References: <E1gXTiZ-0009du-1D@fasolo.debian.org>
 <20181207114000.GA28729@sarek.noreply.org>
Message-ID: <handler.915859.D915859.15447180109891.ackdone@bugs.debian.org>

Your message dated Thu, 13 Dec 2018 16:20:07 +0000
with message-id <E1gXTiZ-0009du-1D at fasolo.debian.org>
and subject line Bug#915859: fixed in onionshare 1.3.2-1
has caused the Debian Bug report #915859,
regarding uses a fixed filename in /tmp
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 at bugs.debian.org
immediately.)


-- 
915859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915859
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Peter Palfrader <weasel at debian.org>
Subject: uses a fixed filename in /tmp
Date: Fri, 7 Dec 2018 11:40:00 +0000
Size: 2239
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181213/1f132e39/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Ulrike Uhlig <ulrike at debian.org>
Subject: Bug#915859: fixed in onionshare 1.3.2-1
Date: Thu, 13 Dec 2018 16:20:07 +0000
Size: 6023
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181213/1f132e39/attachment-0001.mht>

From scootergrisen at gmail.com  Thu Dec 13 06:38:32 2018
From: scootergrisen at gmail.com (scootergrisen)
Date: Thu, 13 Dec 2018 07:38:32 +0100
Subject: [Pkg-privacy-maintainers] Delete da_DK.po from MAT package
In-Reply-To: <871s6mv1ij.fsf@fifthhorseman.net>
References: <9f6d3a7f-f166-e1da-2916-a0437ae8d479@gmail.com>
 <871s6mv1ij.fsf@fifthhorseman.net>
Message-ID: <d0ddc201-a6f3-61cd-68aa-daf77ca27875@gmail.com>

Den 12-12-2018 kl. 23:11 skrev Daniel Kahn Gillmor:
> On Wed 2018-12-12 17:12:42 +0100, scootergrisen at gmail.com wrote:
>> Any chance i can have the untranslated po/da_DK.po translation file
>> deleted from MAT?
>> https://packages.debian.org/stretch/mat
>>
>> mat_0.6.1.orig.tar.xz contains both da.po and da_DK.po but i would like
>> to only have da.po.
>>
>> da.po is translated apart from 1 string.
>> da_DK.po have no translated strings.
>>
>> If possible i would also like the one untranslated string "Cant read
>> file" to be translated to "Kan ikke læse fil" in the da.po file.
>>
>> I think i asked the MAT developer about this but MAT is not maintained
>> any more.
>>
>> Reason i ask is so all the danish translations are using "da" instad of
>> a mixture of "da" and "da_DK".
> 
> This is type of thing probably best reported in the future as an issue
> in the debian BTS (e.g. using the "reportbug" tool to file the issue).
> that ensures that we can keep track of it.
> 
> The changes that you're asking for make sense to me, and i've gone ahead
> and implemented them in debian, and have uploaded 0.6.1-5 (with a bit
> more cleanup of the debian packaging as well).
> 
> In the course of doing this, i noticed that the debian packaging Vcs on
> salsa was in a bit of a messy state.  to fix the worst problems, i did
> two things:
> 
>   * i refreshed the pristine-tar delta for 0.6.1 -- i don't know why it
>     was wrong earlier.
> 
>   * i merged the "upstream" branch into the "master" branch -- "master"
>     had only merged 0.6, and not 0.6.1 for some reason.
> 
> It now builds fine via gbp buildpackage, at least.
> 
> Regards,
> 
>         --dkg
> 

Thank you.


From noreply at release.debian.org  Sat Dec 15 04:39:03 2018
From: noreply at release.debian.org (Debian testing autoremoval watch)
Date: Sat, 15 Dec 2018 04:39:03 +0000
Subject: [Pkg-privacy-maintainers] onionshare is marked for autoremoval from
 testing
Message-ID: <E1gY1jD-0005Jb-S4@respighi.debian.org>

onionshare 1.3-1 is marked for autoremoval from testing on 2019-01-05

It is affected by these RC bugs:
915859: onionshare: uses a fixed filename in /tmp



From noreply at release.debian.org  Sat Dec 15 04:39:10 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Sat, 15 Dec 2018 04:39:10 +0000
Subject: [Pkg-privacy-maintainers] mat 0.6.1-5 MIGRATED to testing
Message-ID: <E1gY1jK-0005Ns-Q8@respighi.debian.org>

FYI: The status of the mat source package
in Debian's testing distribution has changed.

  Previous version: 0.6.1-4
  Current version:  0.6.1-5

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From intrigeri at debian.org  Sat Dec 15 10:25:58 2018
From: intrigeri at debian.org (intrigeri)
Date: Sat, 15 Dec 2018 11:25:58 +0100
Subject: [Pkg-privacy-maintainers] Bug#849227: Bug#849227: GUI ignores
 server stay-open checkbox state
In-Reply-To: <7bd87aa5-82a5-3a7a-3ed1-6500730e6833@debian.org>
References: <20161223205605.12954.69099.reportbug@feeble.seestieto.com>
 <7bd87aa5-82a5-3a7a-3ed1-6500730e6833@debian.org>
 <20161223205605.12954.69099.reportbug@feeble.seestieto.com>
Message-ID: <87ftuzm6h5.fsf@boum.org>

Control: fixed -1 1.3-1

Ulrike Uhlig:
> This is fixed in the current version of Onionshare (> 1.3).

Cool! I'm letting the BTS know about it then :)


From owner at bugs.debian.org  Sat Dec 15 10:30:04 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 15 Dec 2018 10:30:04 +0000
Subject: [Pkg-privacy-maintainers] Processed: Re: Bug#849227: GUI ignores
 server stay-open checkbox state
References: <87ftuzm6h5.fsf@boum.org>
 <20161223205605.12954.69099.reportbug@feeble.seestieto.com>
Message-ID: <handler.s.B849227.154486957118517.transcript@bugs.debian.org>

Processing control commands:

> fixed -1 1.3-1
Bug #849227 {Done: Ulrike Uhlig <ulrike at debian.org>} [onionshare] GUI ignores server stay-open checkbox state
Marked as fixed in versions onionshare/1.3-1.

-- 
849227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849227
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From jiderlesi at outlook.de  Sun Dec 16 14:18:45 2018
From: jiderlesi at outlook.de (Freach)
Date: Sun, 16 Dec 2018 22:18:45 +0800
Subject: [Pkg-privacy-maintainers] Bug#916605: torbrowser-launcher: I can't
 start torbrowser-launcher
Message-ID: <154496992559.3442.6847397552972575684.reportbug@debian.rqz>

Package: torbrowser-launcher
Version: 0.3.1-2
Severity: grave
Justification: renders package unusable

When I first time installed and started,it prompted me to install something for
the first time start.After the automatic installation is completed,it auto quit
this torbrowser-launcher,Then I clicked the run torbrowser-launcher
agin,Nothing happend and it not start,if I type"torbrowser-launcher"in the
terminal.It show these:"Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.3.1
https://github.com/micahflee/torbrowser-launcher
Launching Tor Browser.
Running /home/anon/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/start-
tor-browser.desktop
Launching './Browser/start-tor-browser --detach'...
QFileSystemWatcher::removePaths: list is empty
QFileSystemWatcher::removePaths: list is empty
"



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

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN:zh (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  libdbus-glib-1-2  0.110-3
ii  python3           3.6.7-1
ii  python3-gpg       1.12.0-4
ii  python3-pyqt5     5.11.3+dfsg-1+b1
ii  python3-requests  2.20.0-2
ii  python3-socks     1.6.8+dfsg-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.4.9-7

Versions of packages torbrowser-launcher suggests:
ii  apparmor  2.13.1-3+b1

-- no debconf information


From noreply at release.debian.org  Wed Dec 19 04:39:14 2018
From: noreply at release.debian.org (Debian testing watch)
Date: Wed, 19 Dec 2018 04:39:14 +0000
Subject: [Pkg-privacy-maintainers] onionshare 1.3.2-1 MIGRATED to testing
Message-ID: <E1gZTda-0006tW-83@respighi.debian.org>

FYI: The status of the onionshare source package
in Debian's testing distribution has changed.

  Previous version: 1.3-1
  Current version:  1.3.2-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From owner at bugs.debian.org  Wed Dec 19 13:06:06 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 19 Dec 2018 13:06:06 +0000
Subject: [Pkg-privacy-maintainers] Bug#865368: marked as done (torsocks:
 procmail spawned by mpop in torsocks fails with "Operation not permitted")
References: <20181219130414.nse6zldqt3bmmk3h@viper>
 <149798253703.20877.9514493553345872209.reportbug@viper>
Message-ID: <handler.865368.D865368.154522466514103.ackdone@bugs.debian.org>

Your message dated Wed, 19 Dec 2018 13:04:14 +0000
with message-id <20181219130414.nse6zldqt3bmmk3h at viper>
and subject line Re: torsocks: procmail spawned by mpop in torsocks fails with "Operation not permitted"
has caused the Debian Bug report #865368,
regarding torsocks: procmail spawned by mpop in torsocks fails with "Operation not permitted"
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 at bugs.debian.org
immediately.)


-- 
865368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865368
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Nick <debbugs at njw.name>
Subject: torsocks: procmail spawned by mpop in torsocks fails with "Operation not permitted"
Date: Tue, 20 Jun 2017 19:15:37 +0100
Size: 2899
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181219/61cd0d68/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Nick <debbugs at njw.me.uk>
Subject: Re: torsocks: procmail spawned by mpop in torsocks fails with "Operation not permitted"
Date: Wed, 19 Dec 2018 13:04:14 +0000
Size: 4129
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20181219/61cd0d68/attachment-0001.mht>

From ulrike at debian.org  Wed Dec 19 13:48:00 2018
From: ulrike at debian.org (Ulrike Uhlig)
Date: Wed, 19 Dec 2018 13:48:00 +0000
Subject: [Pkg-privacy-maintainers] Bug#865368: marked as done (torsocks:
 procmail spawned by mpop in torsocks fails with "Operation not permitted")
References: <149798253703.20877.9514493553345872209.reportbug@viper>
Message-ID: <852f1ea1-0810-accb-2f76-ea11a68f0dba@debian.org>

Dear Nick,

> I hadn't seen the section of the manpage with the working Tor
> example, though, many thanks for pointing me to that. I have tested
> it, and that solution works fine.

Great!

> I'm closing the bug report, as this method is just as reasonable as
> using torsocks, and is well documented (despite my failure to find
> it).

Thank you.

> I'm quite new to the debian bugtracker, hopefully I've done
> everything right, apologies if not.

Welcome then! You did everything perfectly correct, thank you.

Cheers,
Ulrike


From jscott at posteo.net  Wed Dec 19 22:33:17 2018
From: jscott at posteo.net (John Scott)
Date: Wed, 19 Dec 2018 17:33:17 -0500
Subject: [Pkg-privacy-maintainers] Bug#916889: onionshare: recommends
 torbrowser-launcher in contrib
Message-ID: <154525879785.2957.11555978248248281585.reportbug@X200>

Package: onionshare
Version: 0.9.2-1
Severity: minor

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

The Policy Manual suggests that OnionShare shouldn't depend or
recommend torbrowser-launcher unless as an alternative to tor
because it's in main (assuming OnionShare 1.3+ works with that).

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages onionshare depends on:
ii  obfs4proxy     0.0.7-4+b1
ii  python3        3.7.1-2
ii  python3-flask  1.0.2-3
ii  python3-pyqt5  5.11.3+dfsg-1+b2
ii  python3-stem   1.7.0-1
ii  tor            0.3.4.9-7

Versions of packages onionshare recommends:
pn  torbrowser-launcher  <none>

onionshare suggests no packages.

- -- no debconf information

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

iQEzBAEBCgAdFiEEAXEkn09uX7g8Tv8W3qerYfa4vJcFAlwaxykACgkQ3qerYfa4
vJd6MAf/Vr0UFF6W0Y/4yGZFouceKI8qaf/8JKVTnYC2aRGtavAwtpTIMR7KEp5H
On54T8JaWDdWQU1T+Lkc20Jl1EkAnoeOYiQQ+hgwM3l6W0n3JLfMNl8ySH0YxipI
8IAPiPHlE3guBjgLtUmHiny6BlPlybenqqiyolYy+sqiJs41VaS0AnAC17+OUe5G
RZuTA5VUR04GMMRN/857DFbJZgQNfnOu6QK93QasvDOr2nwqL/wDSULquT0Z7ekB
R5ypVcc0DU9Nax8KPHQx8KltWuqFXfUuBhzfz4zKSJb6hUkBKSedfLgzpZDpseQX
/PCjVGQzUqEhhHphK8Z06MnTJb4a4g==
=6eKc
-----END PGP SIGNATURE-----


From noreply at release.debian.org  Mon Dec 24 04:39:06 2018
From: noreply at release.debian.org (Debian testing autoremoval watch)
Date: Mon, 24 Dec 2018 04:39:06 +0000
Subject: [Pkg-privacy-maintainers] torbrowser-launcher is marked for
 autoremoval from testing
Message-ID: <E1gbI1C-0005RC-3n@respighi.debian.org>

torbrowser-launcher 0.3.1-2 is marked for autoremoval from testing on 2019-01-14

It is affected by these RC bugs:
916605: torbrowser-launcher: I can't start torbrowser-launcher



From rosh at debian.org  Mon Dec 24 16:57:10 2018
From: rosh at debian.org (Roger Shimizu)
Date: Tue, 25 Dec 2018 01:57:10 +0900
Subject: [Pkg-privacy-maintainers] Bug#916605: Bug#916605:
 torbrowser-launcher: I can't start torbrowser-launcher
In-Reply-To: <154496992559.3442.6847397552972575684.reportbug@debian.rqz>
References: <154496992559.3442.6847397552972575684.reportbug@debian.rqz>
 <154496992559.3442.6847397552972575684.reportbug@debian.rqz>
Message-ID: <CAEQ9gEn7rfKnuMFE4WtkfGSdw=kPjZ2ds4YUm2J6zs+=iJ-h7Q@mail.gmail.com>

control: severity -1 important

Thanks for your report!

On Sun, Dec 16, 2018 at 11:21 PM Freach <jiderlesi at outlook.de> wrote:
>
> Package: torbrowser-launcher
> Version: 0.3.1-2
> Severity: grave
> Justification: renders package unusable
>
> When I first time installed and started,it prompted me to install something for
> the first time start.After the automatic installation is completed,it auto quit
> this torbrowser-launcher,Then I clicked the run torbrowser-launcher
> agin,Nothing happend and it not start,if I type"torbrowser-launcher"in the
> terminal.It show these:"Tor Browser Launcher
> By Micah Lee, licensed under MIT
> version 0.3.1
> https://github.com/micahflee/torbrowser-launcher
> Launching Tor Browser.
> Running /home/anon/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/start-
> tor-browser.desktop
> Launching './Browser/start-tor-browser --detach'...
> QFileSystemWatcher::removePaths: list is empty
> QFileSystemWatcher::removePaths: list is empty
> "

I'm sorry that it doesn't occur on my environment. And I don't see
other similar report neither in debian ML nor upstream.
So I guess it's related your environment. Did you ever install this
package before?

And you may try "torbrowser-launcher --settings" command to download
it again by force.
Please share your experience if you tried. Thank you!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


From owner at bugs.debian.org  Mon Dec 24 17:00:03 2018
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 24 Dec 2018 17:00:03 +0000
Subject: [Pkg-privacy-maintainers] Processed: Re: Bug#916605:
 torbrowser-launcher: I can't start torbrowser-launcher
References: <CAEQ9gEn7rfKnuMFE4WtkfGSdw=kPjZ2ds4YUm2J6zs+=iJ-h7Q@mail.gmail.com>
 <154496992559.3442.6847397552972575684.reportbug@debian.rqz>
Message-ID: <handler.s.B916605.154567064532489.transcript@bugs.debian.org>

Processing control commands:

> severity -1 important
Bug #916605 [torbrowser-launcher] torbrowser-launcher: I can't start torbrowser-launcher
Severity set to 'important' from 'grave'

-- 
916605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916605
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems