Jonas Smedegaard:
> Quoting intrigeri (2017-08-01 16:38:06)
>> Jonas, what do you think?
> Please request removal - also of the reverse dependency.
Done: #870437
Package: ftp.debian.org
Severity: normal
Hi,
we (pkg-perl team) would like to remove this RC-buggy package and its
only reverse dependency (libical-parser-html-perl) from the archive.
Reference: https://bugs.debian.org/806544
Cheers,
--
intrigeri
intrigeri:
> that's a leaf package, with 2 votes on popcon,
And now: 1.
> that made it into one
> single stable release ⇒ unless I missed a compelling reason to keep
> it, I would simply get the package remove from sid.
There's a pull request opened since February
(https://github.c
intrigeri:
> I'll request the removal right away.
#870431
56
Cheers,
--
intrigeri
'll request the removal right away.
Cheers,
--
intrigeri
on this problem?
Would you mind if we removed this package from sid?
Cheers,
--
intrigeri
Niko Tyni:
> There's been no reaction on the upstream bug, and the last upstream
> release was in 2002. There are no reverse dependencies. I suggest
> removal unless somebody objects?
Requested: https://bugs.debian.org/870424
ead and request
the removal of this package + its reverse-dependency from sid, unless
someone is interested enough in this package to work on a fix (that
might be in DateTime-Event-Recurrence or elsewhere).
Jonas, what do you think?
Cheers,
--
intrigeri
://lists.debian.org/debian-perl/2016/06/msg00038.html
Cheers,
--
intrigeri
Package: libgnome2-gconf-perl
Severity: normal
User: pkg-perl-maintain...@lists.alioth.debian.org
Usertags: gnome2-removal
Control: blocked -1 by 870418
Control: blocked -1 by 870413
Yet another bug about removing pkg-perl packages that depend on
obsolete GNOME 2 technologies.
Package: libgnome2-wnck-perl
Severity: normal
User: pkg-perl-maintain...@lists.alioth.debian.org
Usertags: gnome2-removal
Control: blocked -1 by 870417
Control: blocked -1 by 870418
Yet another tracking bug about removing pkg-perl packages that depend on
obsolete GNOME 2 technologies.
Package: libgnome2-canvas-perl
Severity: normal
User: pkg-perl-maintain...@lists.alioth.debian.org
Usertags: gnome2-removal
Yet another blocking bug about removing pkg-perl packages that depend on
obsolete GNOME 2 technologies.
ips:
https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=gnome2-removal=pkg-perl-maintainers%40lists.alioth.debian.org
Cheers,
--
intrigeri
ct this fast :)
Cheers,
--
intrigeri
cycle?
Context: ideally I would like to sort this out during DebCamp, so
a quick answer would be appreciated. But of course I understand if you
can't react this fast :)
For background information, see #868398.
Cheers,
--
intrigeri
David Paleino:
> please proceed in removing it!
Thanks for the lightning fast answer!
I'll proceed then.
.
Cheers,
--
intrigeri
this out during DebCamp, so
a quick answer would be appreciated. But of course I understand if you
can't react this fast :)
Cheers,
--
intrigeri
like to sort this out during DebCamp, so
a quick answer would be appreciated. But of course I understand if you
can't react this fast :)
Cheers,
--
intrigeri
INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
Anything else I should try? Something about $GPG_TTY, or starting
Seahorse from GNOME Terminal (instead of the GNOME Overview), perhaps?
Cheers,
--
intrigeri
wise it errors on many other files in that folder. That
> fixed the mesa cache problem.
Thanks. I've updated my merge request upstream (already applied in
testing/sid) with this rule:
https://code.launchpad.net/~intrigeri/apparmor-profiles/+git/apparmor-profiles/+merge/310120
> Then I added this
future: I'll do this work for Tails anyway,
and I'd rather do it directly in Debian than maintaining a delta. Now,
the outcome of this work is not good enough and you prefer to drop
AppArmor support, well, so be it, that's obviously your call.
Cheers,
--
intrigeri
future: I'll do this work for Tails anyway,
and I'd rather do it directly in Debian than maintaining a delta. Now,
the outcome of this work is not good enough and you prefer to drop
AppArmor support, well, so be it, that's obviously your call.
Cheers,
--
intrigeri
I believe that this bug report is moot on Stretch and newer, and could
be closed: the (incomplete) GnuPG agent implementation provided by
GNOME Keyring was removed in 3.17.91-1.
lib2.0-0 2.52.3-1
ii libgpg-error0 1.27-3
ii libgtk2.0-02.24.31-2
ii libncursesw5 6.0+20170715-2
ii libsecret-1-0 0.18.5-3.1
ii libtinfo5 6.0+20170715-2
pinentry-gtk2 recommends no packages.
Versions of packages pinentry-gtk2 suggests:
pn pinentry-doc
-- no debconf information
--
intrigeri
Hi shirish!
> I purged and reinstalled amd getting the same error -
Do you mean you purged the package, or also ~/.local/share/torbrowser/?
Jens Reyer:
> This bug is still marked as unreproducible. Did you (or anyone else)
> try to reproduce with my previously described steps (see below)?
I did that a while ago, but it was on Tails (based on Jessie back
then): https://labs.riseup.net/code/issues/10797
Control: tag -1 + moreinfo
Hi!
Elia Argentieri:
> This is what I get with `sudo tail /var/log/audit/audit.log -f | grep DENIED`
> when I open any video:
Thank you for reporting this. I cannot reproduce this locally: Totem
works just fine with this AppArmor policy on my up-to-date sid system.
Control: tag -1 + moreinfo
Hi!
Elia Argentieri:
> This is what I get with `sudo tail /var/log/audit/audit.log -f | grep DENIED`
> when I open any video:
Thank you for reporting this. I cannot reproduce this locally: Totem
works just fine with this AppArmor policy on my up-to-date sid system.
t "u") because for whatever reason I don't fully get,
either "u" or "U" triggers the breakage this bug report is about,
and anyway "i" gives us a better defined confinement than "u"
Care to submit a patch (with a suitable header/description) against
the packaging?
Cheers,
--
intrigeri
4. shutter & yarssr:
Can be removed IMO, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868398#15 for details.
Cheers,
--
intrigeri
maintainer wrote "I’d rather drop it than patch it. So when it is
time to RM gnome-vfs, feel free to RM yarssr as well."
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868410#10
Cheers,
--
intrigeri
mmend using the GPL. Please mail suggestions or
modifications to the appar...@lists.ubuntu.com mail list:
https://lists.ubuntu.com/mailman/listinfo/apparmor
So downgrading severity accordingly.
Cheers,
--
intrigeri
Guido Günther:
> Negligence on my part, sorry. Fixed in git since early March.
Amazing, thanks :)
> I wonder if we can make it any simpler to check current git besides
> gbp clone vcsgit:virt-manager
I honestly don't know why I did `apt-get source' while I would usually
debcheckout the
rop the moreinfo tag?
Cheers,
--
intrigeri
out another debugging/hardening option
(ASan and friends).
> (etc.)
Maybe :)
Cheers,
--
intrigeri
The Mutter 3.24.4 announcement says that
https://bugzilla.gnome.org/show_bug.cgi?id=784223 has been fixed.
I suspect this is the same bug as this one.
So anyone affected: please try to reproduce once Mutter 3.24.4 is in
Debian :) Thanks in advance!
Package: virt-manager
Version: 1:1.4.0-5
Severity: wishlist
Hi!
gconf2 has been deprecated for ages, and last time we (at Tails) tried
to get a patch in there, the answer we got was: "Thanks for sharing
the patch here but as gconf has been deprecated and unmaintained for
years I'm afraid that
Peter Palfrader:
> Is this still something we want to do?
Yes, I think it would be a valuable improvement :)
Cheers,
--
intrigeri
usr/bin/obfs4proxy pix,
Full disclosure: I've just noticed that we've been setting
NoNewPrivileges=no in Tails for a year to fix this very problem, but
apparently I totally failed at reporting this upstream back then.
Sorry! :(
Cheers,
--
intrigeri
Jan Luca Naumann:
> there was the problem that the aufs module for 4.11 had some problems.
> There is a version for 4.11.7+ now available upstream but in Debian the
> current kernel version is 4.11.6. I will try to package a new version as
> soon as 4.11.7+ is uploaded.
Great, thanks for the
Hi,
Jan Luca Naumann:
> thank you for the trigger, it seems that I missed the point where 4.11
> was uploaded to sid. I will update the aufs package over the weekend.
Do you have an updated timeline for this?
Cheers,
--
intrigeri
me. Sorry, no time to investigate right now.
Cheers,
--
intrigeri
pdates).
And then we can revert this once #702030 is done, or once AppArmor is
enabled by default, whichever happens first :)
Cheers,
--
intrigeri
ps they would send their
proposed changes directly upstream if instructed to do so in the
first place)
I have to say I'm torn between these two options. What do my fellow
team-mates think?
Cheers,
--
intrigeri
Control: tag -1 + unreproducible
Hi,
intrigeri:
> Control: tag -1 + moreinfo
> Hi Jean-Michel!
>> [] Starting AppArmor profiles:[] Mounting securityfs on
>> /sys/kernel/security...[info] Insufficient privileges to change profiles..
>> failed!
> Is AppAr
,
> AppArmor is not enabled by default in Debian
Indeed, this totally makes sense to me.
> and likely never will,
I beg to disagree but that's another discussion :)
Cheers,
--
intrigeri
Antoine Beaupré:
> PS: seems to me like a good example why profiles-extra should be
> deployed straight to /etc :p
One step at a time: I'd rather see AppArmor enabled by default with
a small, robust policy first. And then we can think of extending this
policy :)
Cheers,
--
intrigeri
dev/apparmor-profiles/+git/apparmor-profiles
* Ulrike was kind enough to document how to prepare and send merge
requests upstream:
https://wiki.debian.org/AppArmor/Contribute/Upstream#Quick_howto_contribute_to_upstream_AppArmor_profiles_using_Git
Cheers,
--
intrigeri
d not find any such thing in a Stretch chroot after installing
apparmor-profiles. I've looked in
/usr/share/doc/apparmor-profiles/extras/ and in /etc/apparmor.d/.
Perhaps you copied stuff from /usr/share/doc/apparmor-profiles/extras/
to /etc/apparmor.d/ in the past and your own copy needs an update?
Cheers,
--
intrigeri
an email notification about it :)
And if you want to test the attached profile yourself, great!
Then these instructions should be helpful:
https://wiki.debian.org/AppArmor/HowToUse
Let me know if you have any question.
Cheers,
--
intrigeri
>From 4aeef2a074b6cebc5a5e7dfe67d71d4849bd1c57 Mon
Control: forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=89768
Control: tag -1 + upstream
Hi Santiago,
Santiago Vila:
> t/08-f-errors.t(Wstat: 0 Tests: 39 Failed: 2)
This looks very much like
https://rt.cpan.org/Public/Bug/Display.html?id=89768.
Cheers!
upstream AppArmor mailing list, as I think it is not
Debian-specific.
Logs are at https://bugs.debian.org/865206.
Cheers,
--
intrigeri
Control: tag -1 - patch
Hi,
intrigeri:
> Can you please ensure the tags for #862552 are correct? I see no
> indication that it's fixed upstream, and I can't find the patch.
Thanks for removing the buggy "fixed-upstream" tag.
I still see no patch, so I'm removing the "pa
Hi,
Holger Levsen:
> On Thu, Jun 29, 2017 at 02:05:08PM +0200, intrigeri wrote:
>> Holger Levsen:
>> > Process: 375 ExecStart=/usr/sbin/haveged --Foreground --verbose=1
>> > $DAEMON_ARGS (code=exited, status=226/NAMESPACE)
>>
>> 226/NAMESPACE suggests
Holger Levsen:
> Process: 375 ExecStart=/usr/sbin/haveged --Foreground --verbose=1
> $DAEMON_ARGS (code=exited, status=226/NAMESPACE)
226/NAMESPACE suggests it's a problem with the hardening we do in the
systemd unit file. Please try disabling all such hardening, and if it
fixes stuff,
eged: Couldn't initialize HAV"..., 42) = 42
> munmap(0xb3f59000, 2072576) = 0
> exit_group(1) = ?
> +++ exited with 1 +++
So the problem seems to be ENOMEM. Is that system seriously memory-constrained?
Cheers,
--
intrigeri
report to include this use case.
Cheers,
--
intrigeri
current applet, as soon as I've got
a working GNOME Shell extension. So, patches are welcome to fix
parcimonie-applet :)
> Here's the whole output of systemd-cgls:
> http://paste.debian.net/903788
Sadly, this is not available (anymore?): I see only "Entry not found".
Cheers,
--
intrigeri
Hi!
Jose Miguel Parrella Romero:
> On 6/24/2017 1:31 PM, intrigeri wrote:
> > Therefore, I intend to adopt this package under the umbrella of the
> > pkg-perl team if I get no reply before the beginning of DebConf17.
> You should move forward and adopt libdesktop-notify-
.
Cheers,
--
intrigeri
g-perl team if I get no reply before the beginning of DebConf17.
I'd be glad to co-maintain this package with you on that team whenever
you have some time for Debian maintenance :)
Cheers,
--
intrigeri
gregor herrmann:
> I just pushed a commit which builds the test libraries during
> autopkgtest. Please take a look, and feel free to improve/revert/...
Thanks a lot, this works fine for me ⇒ will upload :)
Package: libglib-object-introspection-perl
Version: 0.042-1
Severity: normal
I see this when running the autopkgtests:
autopkgtest [10:36:23]: test command1: /usr/share/pkg-perl-autopkgtest/runner
build-deps
autopkgtest [10:36:23]: test command1: [---
n-disk format and
installation methods, and hence wrt. the future of this package: this
will allow us to determine how suitable this package is for Buster.
Cheers,
--
intrigeri
kage unusable
on current sid.)
Cheers,
--
intrigeri
t works fine for us :)
Cheers,
--
intrigeri
> Can you tell us if this bug is present with Tor 0.2.9.x as well,
> i.e. it's a regression? Or is it a new problem in 0.3.0.x?
It's a regression.
It might be caused by:
* Replace CAP_DAC_OVERRIDE with CAP_DAC_READ_SEARCH in systemd's service
capability bounding set. Read access is
Hi,
Holger Levsen:
> On Mon, May 22, 2017 at 12:12:39PM +0200, intrigeri wrote:
>> Fundamentally, do you disagree with the main point this bug report is
>> about i.e. "Should not be part of Stretch"?
> yes, somewhat, but I acknowledge that it's not my call.
>>
e-security or
stable-updates?
Cheers,
--
intrigeri
rofile fixed this problem.
/var/lib/tor/hidden_service_onioncat is only readable by debian-tor;
I suspect that Tor might try to access it as root before changing uid.
Cheers,
--
intrigeri
tream commit 85af45f3c5cf10ec60f1301169ee94ac978c5b69 fixes the
problem for me. I'm assuming it's the same as the attached patch.
Cheers,
--
intrigeri
Hi Kjö,
thanks for cloning and retitling!
Can you please ensure the tags for #862552 are correct? I see no
indication that it's fixed upstream, and I can't find the patch.
Cheers,
--
intrigeri
Control: tag -1 + moreinfo
anonym:
> Versions before mutter 3.24 are affected by a bug making gnome-shell report
> the wrong x-coordinate of its elements via at-spi. For details, see:
It would be nice to sum up the impact of the bug here (e.g. for users
of universal access technologies), so
u:
> This will also allow adding some upstream modifications that were made
> recently.
Great! (assuming they satisfy the criteria for freeze exception at
this very late stage of the release process :)
ckages of "mine"), but IMO this shouldn't block the Stretch
release, so a stretch-ignore tag would seem suitable to me.
Cheers,
--
intrigeri
he control port of a system-wide Tor,
and point onionshare to it
… which would allow us to ship onionshare in Stretch, with sub-optimal
usability, sure, but still better than not having it at all IMO.
What do you think? Sounds doable?
Cheers,
--
intrigeri
let me know :)
Cheers,
--
intrigeri
Hi,
Antoine Musso:
> python-jenkins 0.4.11 is partly broken.
At least the jenkins-job-builder use case works fine for me on current
Stretch, and the bug report says "partly", so I'm not sure this bug
should really be RC.
Cheers,
--
intrigeri
.
Cheers!
--
intrigeri
Hi,
u:
> As you might know, the version in Jessie is 1.9.x - very outdated and
> one should always use the version from jessie-backports.
I (mistakenly) thought that the plan was to fix the package in Jessie
at some point, so thanks for the update!
Now, this makes me wonder:
If there's any
intrig...@debian.org:
> I'm attaching the output of `sh -x /lib/bilibop/test /dev/sda 2>&1'
> to this bug report.
For real, this time.
+ set -e
+ . /lib/bilibop/common.sh
+ [ = true ]
+ DEBUG=false
+ has_udevadm=false
+ IFS=:
+ echo /usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin
+
provide additional info to help pinpoint
the problem.
Thanks in advance!
Cheers,
--
intrigeri
e this bug open and will get back to it later.
Sure, that's only a wishlist bug after all :) It shouldn't be blocking
the more important work you're on.
Cheers!
--
intrigeri
sad outcome wrt. UX; I _personally_ prefer to
live with #858034 being unfixed (until someone tries to fix it in
a nicer way) than to add these requirements to all users of TorBirdy
in Debian. YMMV :)
Sorry if I missed something!
Cheers!
--
intrigeri
n-dogtail suggests no packages.
-- no debconf information
--
intrigeri
since then somehow? If not, may you please
report it as a separate bug, since it already affects Stretch and is
somewhat off-topic on a bug report that's about "Enable a Puppet
master to connect to PuppetDB"?
Cheers,
--
intrigeri
t; both Jessie and Stretch. Also, for the puppet-terminus-puppetdb package
> I'm using PuppetDB's version numbers (and not the puppet source
> version), so that the package can be taken over by the puppetdb source
> when the latter is ready for Debian.
I really like this plan. Is it still up-to-date?
Cheers,
--
intrigeri
Hi,
intrigeri:
> I might try to come up with a hackish PoC for Tails soon
Here we go! Installing the four following files (slightly adapted to
drop a couple Tails-specific bits) on a Stretch system seems to do the
job. I hope it can allow interested people to validate this appro
/Software/systemd/RootStorageDaemons/
* systemd-shutdown(8)
Cheers,
--
intrigeri
Hi,
Vincas Dargis:
> 2017.04.04 08:26, intrigeri rašė:
>> Thanks! But it ships disabled (or in complain mode) by default, right?
> Yes it's disabled, and it's from firefox package.
Thanks!
>> OK. So these improvements shall be upstreamed.
>>> Or "fixed" o
Hi,
Vincas Dargis:
> 2017.03.20 11:23, intrigeri rašė:
> Yes, they have profile in firefox package [0].
Thanks! But it ships disabled (or in complain mode) by default, right?
>> 1. Find out which profile (if there are several, e.g. a non-upstream
>>one shipped in Ubuntu
intrigeri:
> I'll file an unblock request once it has built on all
> relevant architectures.
Niels already unblocked + aged it, so I didn't even have to file such
a request :)
Cheers,
--
intrigeri
ay
that makes it work cross-distro (Closes: #742829).
Hopefully this is addressed upstream at some point, and then we can
ship this profile again :)
Cheers,
--
intrigeri
Michael Biebl:
> Feel free to go upload without delay.
Thanks!
Uploaded, debdiff attached (I don't think I have access to the Vcs-Svn.)
I'll file an unblock request once it has built on all
relevant architectures.
Cheers,
--
intrigeri
diff -Nru seahorse-3.20.0/debian/changelog seaho
in Stretch IMO.
So I'd like to do an NMU that cherry-picks the minimal fix that
upstream has already applied (and I'll request an unblock to the
release team). Is it OK with you, or do you prefer to handle
it differently?
If I don't hear from you in the next few days, I'll upload to
DELAYED/10.
Cheers,
--
intrigeri
intrigeri:
> Hi dear Seahorse maintainers,
Sorry for the noise! This was meant for #859336, forget it.
upstream has already applied (and I'll request an unblock to the
release team). Is it OK with you, or do you prefer to handle
it differently?
If I don't hear from you in the next few days, I'll upload to
DELAYED/10.
Cheers,
--
intrigeri
't ensure that busybox is installed when the cryptsetup hook
needs it though. But that's another problem, and as Guilhem pointed
out it's well tracked elsewhere already.
Cheers,
--
intrigeri
1101 - 1200 of 3755 matches
Mail list logo
