Package: htmldoc
Version: 1.9.7
All "" in the webpage are converted to visible  (U+00C2) in PDF.
with htmldoc -t pdf --webpage --quiet --no-title --textfont helvetica
--left 16 --bottom 8 --top 8 --browserwidth 800 --headfootsize 8.0
--fontsize 7.0 --header xtx --footer xd/
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: fr...@geoinfo.tuwien.ac.at
it is included in buster and then again in sid.
lacking libffi6 breaks installation routines of other programs, which are
asking for it (e.g. ghcup - which could also be included in debian).
thank you for
Hi,
On 16.07.20 22:52, Jakub Wilk wrote:
> * Jakub Wilk , 2020-07-15, 11:30:
>> The onionshare(1) man page says: "the crypto key lives in
>> /tmp/onionshare/tmpXXX/private_key". I don't belive this is correct.
>
> The onionshare-gui(1) man page includes this sentence too.
Yes, I'm well aware of
. However, as we will continue
to ship the package in Tails for cloning Tails devices, it might be
relevant there.
Cheers!
u.
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
Hi Russell,
if this problem is not present anymore, I suggest we close this bug.
Cheers!
u.
.run()
> File "/usr/lib/python2.7/dist-packages/tails_installer/gui.py", line 264,
> in run
> self.live.log.exception(unicode(e))
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 8:
> ordinal not in range(128)
>
>
> I did enter my password at the prompt, but it failed to do the right
> thing.
What does `pkexec whoami` tell you?
Cheers!
u.
:
/usr/bin/tails-installer
Now, indeed, as you mentioned, "packages.debian.org" shows something
else in the file list. However, I believe this must rather be a bug
related to packages.debian.org, and seems unrelated to the packaging.
If you agree, I think we should reassign this bug to packages.debian.org
or simply close it. But maybe I miss something?
Cheers!
u.
hat case can I fix it?
This simply needs to be fixed in the Tails documentation, I'll do that
once I have uploaded a more recent backport.
Ack?
Cheers!
u.
Hi Antoine,
in order to eventually close this bug sometime, could you reply to
intrigeri's last question?
Thanks & cheers!
u.
Hola, mi nombre es Gen.Jessica U Meir, soldado del estado
norteamericano de Estados Unidos, tengo algo muy importante que
discutir contigo, por favor mándame un correo electrónico
(jessicaumei...@gmail.com) para que sepa si recibes mi correo o tú me
puede enviar su dirección de correo electrónico
Hi!
thanks for your patch, I will try to add this as soon as I can, once
reviewed.
Cheers!
u.
obably sneak this in if needed.
I actually planned to work on it either tomorrow or wednesday, so it
should be fine :)
Cheers!
u.
Well, apparently I've read too fast. Reopening for further discussion.
Hello Roger,
Roger Shimizu:
> Dear Maintainer,
>
> Is it time to upload backports of 0.2.7-3 to stretch?
> I'm also wondering why it didn't hit testing yet.
I agree with you and will take care of it this month.
Cheers!
u.
Hi!
the great news is that Georg Koppen and Nicolas Vigier from the
Torproject have been very helpful and created a temporary fix for this
situation. Nicolas even committed a pull request for torbrowser-launcher
to use the new URL to check for updates (see
is listed, even though it is not downloadable anymore.
I'll try to see what can be done.
Cheers!
u.
I prepare a newer backport, you might want to use
torbrowser-launcher from sid:
https://tracker.debian.org/pkg/torbrowser-launcher
torbrowser-launcher will not be available in Stretch anymore by the way.
Cheers!
u.
Hi Andreas,
Andreas Metzler:
> Source: pidgin-otr
> Version: 4.0.2-1
> Severity: normal
>
> pidgin-otr build-depends on libgcrypt11-dev. This is a transition
> package, please use libgcrypt20-dev instead.
Thanks for sharing this. I'll take care of it.
Cheers!
u.
Hi Andreas,
Andreas Metzler:
> Source: libotr
> Version: 4.1.1-2
> Severity: normal
>
> libotr build-depends and libotr5-dev depends on libgcrypt11-dev. This is
> a transition package, please use libgcrypt20-dev instead.
Thanks, will do.
Cheers,
ulrike
Hi Henrik,
I cannot reproduce this. It works perfectly for me. The server is not
stopped when I uncheck the box.
Can you please try using oionshare 0.9.2 and confirm if this still
persists or not?
Cheers!
ulrike
t; patch, if it isn't already applied.
> But I hope it will be fixed by upstream.
I'll open an issue upstream to ask for review / inclusion of your patch
or a modified version thereof.
Cheers!
u.
Hi,
removing rdeps is needed & desired.
Please note that this bug is blocked by #863409 which you might want to
act upon first.
Cheers!
ulrike
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Hi,
onionshare is marked for autoremoval on 22 June 2017: 861744" because of
it's dependency on torbrowser-launcher. This is correct and wanted.
However, it looks like Stretch might already be
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Hi,
torbrowser-launcher is marked for autoremoval on 22 June 2017: 861744".
This is correct and wanted.
However, it looks like Stretch might already be out at that date.
So I'm hereby asking
Hi Henrik,
I've just tried what you report here and for me it works perfectly fine.
Let me explain what I did:
- I start onionshare using the GUI to share a file.
- I download the file over Tor using Tor Browser.
- In the GUI I now get a message "Time elapsed: 1second" on a turquoise
background.
y, sure, but still better than not having it at all IMO.
>
> What do you think? Sounds doable?
Thanks for caring and coming up with this plan. I'll handle it that way.
This will also allow adding some upstream modifications that were made
recently.
Cheers!
u.
Control: reopen 796295
Hi,
I'd like to reopen this bug, it's a call for help and it still applies
as long as the software is in the archive.
Cheers!
u.
to close this bug, as I
believe that it exceeds the intended usage of this package and is not a
bug in the packaging itself. This should either be reported upstream or
documented on the Debian wiki. What do you think?
Cheers!
u.
or the SSL certificate of the server changes. This is not
reliable and normal users will be unable to workaround these issues
themselves.
It'll be easier and safer to provide up-to-date versions to users using
stable-backports. This shall be documented on the Debian wiki.
Cheers!
u.
signature.asc
Hi,
thank you very much for your remarks. I'd certainly appreciate some help
by fellow members of the Privacy team, as well as insight, since I
suddenly became the de-facto maintainer of this package.
Holger Levsen:
> On Wed, May 03, 2017 at 08:29:00AM +0000, u wrote:
>> As you m
n Jessie is 1.9.x - very outdated and
one should always use the version from jessie-backports. However,
currently, this one is not up-to-date either.
So, meanwhile, you should install the version from unstable or even
experimental. I'll try to upload a newer backport today.
Cheers!
u.
As this error looked familiar to me, I stumbled across a previous very
similar bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794847 This report
stated that the error you reported might be linked to a problem in
Python Twisted. May you please also tell us which version of
Hi Russell,
your bug report initially says that your version of torbrowser-launcher
is 0.2.0. On some other channel I've seen you saying that the problem
still persists. May you please tell us if this concerns the current
version 2.6.3 or the old one?
Cheers,
ulrike
Sorry for writing three emails for one problem..
I forgot to mention that if the upstream patch gets integrated, we would
need to copy this into the Debian AppArmor profile too.
Hi,
thanks for your bug report.
Upstream has partly implemented this in a newer version of onionshare.
It has also been implemented in Tails.
I'm working on getting it to Debian, but I did not have the time yet to
test everything well. However, it shall happen! :)
Cheers!
u.
, 0.2.7-1, on Jessie with AppArmor enabled
without any problem.
Cheers!
u.
I believe this bug is a duplicate of 855522
doesn't want it to be in Debian stable.
This bug is opened in coordination with upstream.
It'll be easier and safer to provide new versions to users using
stable-backports.
See upstream bug https://labs.riseup.net/code/issues/11945
Cheers!
u.
Hi,
intrigeri:
> u:
>>> Package: torbrowser-launcher Version: 0.1.9-1+deb8u3
>
>> First of all, this looks like a *very* old version of
>> torbrowser-launcher. You should probably update your system once in a
>> while :)
>
> FWIW that's the one availa
Hi,
Micah Lee:
> On 01/26/2017 03:23 PM, Gregor Zattler wrote:
>> Package: torbrowser-launcher
>> Version: 0.2.6-3
>> Followup-For: Bug #852732
>>
>> Dear Maintainer,
>>
>> I have the very same problem as Sebastian Niehaus with
>> torbrowser-launcher from debian testing while trying to download
Hi,
thanks for this report.
Sebastian Niehaus:
> Package: torbrowser-launcher Version: 0.1.9-1+deb8u3 Severity:
> normal
First of all, this looks like a *very* old version of
torbrowser-launcher. You should probably update your system once in a
while :)
> I now get an error message:
>
>
Hi Carlos,
Carlos Maddela:
> On 09/01/17 20:29, intrigeri wrote:
>> Carlos Maddela:
>>> I had been thinking of adopting this package myself, but since you'd
>>> like to adopt it too, I've opted for a QA upload instead.
>> How about joining pkg-privacy and participating in the maintenance of
>>
Hi!
Henrik Ahlgren:
> However I still cannot get the "stop server automatically" checkbox
> in the GUI to work as expected.
thank you for your bug report. I'll look into it soon.
Cheers!
u.
Hi,
thanks for your investigations.
I think this bug is not release critical, so I've downgraded it now.
Cheers!
u.
lly be that this bug will
need to be reassigned to p7zip-full, but I'm in not position to judge this.
The headers are created nonetheless, and thus this might still represent
a problem when using @dh-stripnondeterminism@.
Cheers!
u.
(The script is a fast dirty hack, I did not write it myself.)
ease?
Cheers!
u.
FWIW, one can see the contents of those header fields as follows (only
visible on directories as it looks like):
@unzip -ZTv $some_zip@
Example output:
entral directory entry #1:
---
chrome/
offset of local header from start of archive: 0
Hi!
> (adding back u. to CC - sorry, I didn't realize mails for this bugreport
> don't get delivered to pkg-apparmor when cleaning up the recipients)
Thanks!
> So here's the patch I hereby propose upstream:
Thank you very much Christian! :))
Take care,
ulrike
Hi Shirish,
thanks for reporting this.
I can't reproduce this on a stable system using the latest
torbrowser-launcher from jessie-backports.
Did you test this on a clean installation?
Cheers!
u.
I've put the upstream list and the original author of the profile in
Cc:. @Upstream, what do you think?
Cheers!
u.
Hi,
Ben Finney:
> On 16-Nov-2016, u wrote:
>> Well, dput is supposed to work with SFTP simply by specifying
>> "method = sftp" in any dput config file such as ~/.dput.cf.
>
> That has never been the case for the ‘dput’ package.
> This bug is a request for a n
Hi,
built and tested the binary. Looks good!
Cheers!
u.
diff -Nru seahorse-nautilus-3.11.92/debian/changelog
seahorse-nautilus-3.11.92/debian/changelog
--- seahorse-nautilus-3.11.92/debian/changelog 2014-09-15 21:35:21.0
+0200
+++ seahorse-nautilus-3.11.92/debian/changelog 2016-11-16
Hi!
Ben Finney:
> Thanks for your interest.
>
> On 15-Nov-2016, u wrote:
>
>> I'd like to be able to use SFTP to upload from Debian to a Ubuntu
>> PPA too.
>
> What tools already exist to do this?
Well, dput is supposed to work with SFTP simply by specifying &quo
Hi!
I'd like to be able to use SFTP to upload from Debian to a Ubuntu PPA too.
Is there any progress / ETA on integrating this patch into Debian's dput?
Thanks & cheers!
u.
make sure that polkit is running.
Can you try running the installer using gksudo?
Can you please report back on what "pkexec whoami" gives you?
Cheers,
u.
Hi Andreas,
thank you for your bug report.
I confirm this broken behaviour.
We have seen this before, as mentioned here:
https://github.com/micahflee/torbrowser-launcher/issues/241
I've not yet investigated in detail what's common here and what's not,
but I'm on it.
Cheers!
u.
userfriendly.
Thank you,
u.
title this bug report as "Please bring back PDF
support to mat"?
Cheers!
u.
Thanks Matthias, I wasn't aware of these packaging policies, please suggest me
a possible way to handle this case.
Regards,
Avinash
HPE
Thanks Matthias, I wasn't aware of these packaging policies, please suggest me
a possible way to handle this case.
Regards,
Avinash
HPE
Version : 8u102-b14.1
Package: openjdk-8-jre-headless
Tags: patch
Reproducer:
Installation of openjdk-8-jre-headless on i386 or sparc.
Patch:
Warning occurs due to the usage of -XX:PermSize=128m with java during postinst
script of jre-headless package and PermSize; support was removed in 8.0
; It's simple to fix, add:
>
> owner
> @{HOME}/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/{Browser/TorBrowser/,}Data/Tor/
> r,
>
> (we only had permissions for Tor/* before).
Great, that works. I've created a pull request upstream with this
modification: https://github.com/micahflee/torbrowser-launcher/pull/243
Cheers!
u.
profile="icedove" name="/usr/lib/icedove/icedove" pid=10080
> comm="icedove" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
Thanks for this bug report. I'll look into it.
Also Cc:ing Simon Déziel who is the original author of the profile.
Cheers!
u.
Hi James,
Would you please share the more info / reproducer steps and Warning logs what
you noticed?
Thanks.
> The prerm is looking for /var/lib/binfmts/@basename@ (e.g., openjdk-8) but the
> files under /var/lib/binfmts are named after the binfmt being registered, not
> the package.
> This
ch;msg=25>
On Thu, 28 Jul 2016 11:59:02 + "U B, Avinash" <avinash@hpe.com> wrote:
> Package: Package: openjdk-7-jdk
> Source: openjdk-7
> Version: 7u101-2.6.6-2~deb7u1
> Severity: minor
>
On Thu, 28 Jul 2016 11:55:08 + "U B, Avinash"
Package: Package: openjdk-7-jdk
Source: openjdk-7
Version: 7u101-2.6.6-2~deb7u1
Severity: minor
Issue:
adequate openjdk-7-jdk
openjdk-7-jdk:arm64: broken-symlink /usr/lib/jvm/java-7-openjdk-arm64/src.zip
-> ../openjdk-7/src.zip
Dynamic symbolic link will get created only after installation
Package: openjdk-8-jdk-headless
Source: openjdk-8
Version: 8u91-b14-1
Severity: minor
Issue:
$ adequate openjdk-8-jdk-headless
openjdk-8-jdk-headless:arm64: broken-symlink
/usr/lib/jvm/java-8-openjdk-arm64/src.zip -> ../openjdk-8/src.zip
Dynamic symbolic link will get created only after
Hi!
Carsten Schoenert:
> Am 25.07.2016 um 16:05 schrieb u:
>>> Could you please, if needed, prepare a new patch against the already
>>> commited changes?
>>
>> I'll take care of it tomorrow.
>
> we queue the upload then to get the actual profile in. Than
a782da7b416f40943931bf994000ea006b
> https://anonscm.debian.org/cgit/pkg-mozilla/icedove.git/commit/?id=6fe4897bbe86dc74a74aa1747454adbcacbf2e7f
>
> Could you please, if needed, prepare a new patch against the already
> commited changes?
I'll take care of it tomorrow.
Cheers!
u.
For your view only
United Nations Compensation Uni1.docx
Description: Binary data
of the
packaging itself.
However, when I uninstall I might actually want to get rid of the
downloaded browser, history, bookmarks etc. or at least i'd like to know
that I should/could delete/wipe this folder manually.
This bug report is here simply to keep track of this issue.
Cheers!
u.
Upstream has recently moved to Git, and the URL i've linked to earlier
points still to the old repository. The new one is here:
https://code.launchpad.net/~apparmor-dev/apparmor-profiles/+git/apparmor-profiles
And the direct link to the profile is:
ckage. [..] Manual pages for protocols and
other auxiliary things are optional."
Symlinking man pages is allowed, as described in this policy, but I do
not have an example in mind where this has been done.
Cheers!
u.
is available here:
https://wiki.debian.org/AppArmor/Debug
I'm happy to help with any testing, for this and future versions. I'll
also happily help to update this profile when upstream modifies it and
when Debian bug #816679 is resolved.
Cheers!
u.
From f7ca341b9abea2d88de14518e3aab45679a7791d Mon
Hi!
> On 07/02/2016 10:37 AM, u wrote:
>> Here's a debdiff which fixes this bug.
>> I've tested building in a chroot using gcc-6.
>>
>> One might want to consider setting up a Git repository for this package :)
>
> Thanks!
Actually, it did not build correctly
Hi Holger,
Holger Levsen:
> On Thu, Jun 30, 2016 at 12:32:58AM +0200, Nicolas Braud-Santoni wrote:
>> Tested independently by U and myself.
>
> I'm looking forward for the next upstream release.
I started preparing some patches for the current version. I'll not be
able to
Hi,
Here's a debdiff which fixes this bug.
I've tested building in a chroot using gcc-6.
One might want to consider setting up a Git repository for this package :)
Cheers,
u.
diff -Nru ppl-1.1/debian/changelog ppl-1.1/debian/changelog
--- ppl-1.1/debian/changelog 2015-12-11 22:07:13.0
I confirm that using the profiles from the commit/pull request which
intrigeri linked to, work correctly on Jessie.
thanks!
Hi!
thanks for your quick answer.
Shell Xu:
> Hi, u:
>
> That's very interesting. Let's see what happened one by one.
>
> First of all, source code are not been "deleted". It's just a branch
> called "rm". If you switch branch to master, code is s
1. So this package is also
completely outdated.
Cheers!
u.
This has been merged upstream today.
As stated on http://crypto.cat, a complete software rewrite is been done
currently. In the meantime, there won't be any updates to the source
code which has been unmaintained since 19 months.
I am waiting for this to happen before continuing to work on the packaging.
cheers!
signature.asc
Hi,
in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815006#5, you state
that similar discussions are going on for the renaming of Icedove. Are
those publicly trackable somewhere?
Cheers!
u.
ink it should indeed be documented in README.Debian and the manpage
- I can handle this.
Cheers!
u.
I've modified your email address and issued a new pull request.
Packaging is more or less ready but blocked by
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81
I did not yet have the time to look at this in detail.
Hi,
Chris Knadle:
> u:
>> Hi Chris,
>
> Hey, u. ;-)
>
>> Chris Knadle:
>>> Package: xul-ext-torbirdy
>>> Version: 0.1.4-1
>>> Severity: normal
>>> Tags: patch
>>>
>>> Torbirdy sets mail.smtpserver.defaul
setting on every Icedove
> startup until I found where it was being set.
thank you very much.
I'll forward this bug & patch upstream. I think it belongs there -
unless you want to do that yourself? In that case, please go ahead :)
Cheers!
u.
signature.asc
Description: OpenPGP digital signature
Package: lintian
Version: 2.5.38.1
Severity: normal
In the packaging for the Cryptocat extension, there is a false positive.
The file is source code but contains a very long line that is a
cryptographic
constant
cryptocat source: source-is-missing chrome/content/data/js/lib/otr.js
Hey Alexandre,
Alexandre Viau:
> Unless you object, I intend to take over this ITP.
>
> I am in contact with upstream and we have already begun working on it
> together.
No objections :)
Cheers!
Package: policykit-1
Version: 0.105-14
Severity: normal
Dear Maintainer,
In a package (tails-installer, currently in Debian NEW queue), we use
polkit to ask the user for authorization to rewrite the MBR of a USB
stick and to use syslinux. When the screen locker is active though, the
Hi,
thanks for your bug report!
I'll check and update the profiles accordingly (upstream even).
Cheers!
u.
Hi,
shirish शिरीष:
> On 17/10/2015, u <u...@451f.org> wrote:
>> shirish शिरीष:
>>
>>> Can you change or add .png images in addition or replacement of xpm
>>> so that torbrowser-launcher can show up in gnome-software.
> This is specifically running gnom
iled to load stock
> icon /usr/share/pixmaps/torbrowser80.xpm: Icon
> '/usr/share/pixmaps/torbrowser80.xpm' not present in theme (null)
Thanks for your bug report.
Is this specific to running Gnome Shell in Stretch?
On a Jessie installation I do not have this problem, the xmp icons show
up fine.
Cheers
u.
Ximin Luo:
> On 11/01/15 19:25, intrigeri wrote:
>> Ximin Luo wrote (11 Jan 2015 16:34:40 GMT) :
>>> I spoke to upstream (agl) at 31c3 and explained to him what
>>> Debian experimental is, and he is happy for it to be packaged
>>> there for now.
>>
>> Woohoo! \o/
>>
>
> Preliminary package is
In order to do so, run torbrowser-launcher --settings
* Can you run torbrowser-launcher from a terminal and send us the output
please?
* Do you use AppArmor?
Thanks!
u.
heya,
Holger Levsen:
>> And before we start fuddling around with this, we should migrate this
>> package to the new pkg-privacy-maintainers list, instead of
>> pkg-anonymity-tools. Aaaand i'd like to review the branch layout a bit,
>> too. Maybe i can do that this week, so we can start working on
Hi,
anarcat:
> On Sun, Sep 21, 2014 at 06:21:58PM +0000, u wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Ulrike Uhlig <u...@451f.org>
>>
>> * Package name: wnpp
>> Version: 0.4.0
>> Upstream Author: Mailpile Team <t...@mailpile.i
Hi,
the package has been updated but needs some more <3
https://lists.alioth.debian.org/pipermail/pkg-privacy-maintainers/Week-of-Mon-20150928/38.html
We are on it :)
cheers!
u.
signature.asc
Description: OpenPGP digital signature
1 - 100 of 223 matches
Mail list logo
