-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 23:30:24 -0800
Source: rkhunter
Binary: rkhunter
Architecture: source all
Version: 1.4.6-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
Changed-By: Francois Marier
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 23:25:10 -0800
Source: reboot-notifier
Binary: reboot-notifier
Architecture: source all
Version: 0.8
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 23:12:55 -0800
Source: pdfresurrect
Binary: pdfresurrect pdfresurrect-dbgsym
Architecture: source amd64
Version: 0.15-2
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 23:19:00 -0800
Source: planetfilter
Binary: planetfilter
Architecture: source all
Version: 0.8.1-5
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 23:21:15 -0800
Source: pylibravatar
Binary: python-libravatar python3-libravatar
Architecture: source all
Version: 1.7-5
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 22:53:26 -0800
Source: node-libravatar
Binary: node-libravatar
Architecture: source all
Version: 2.0.0-6
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
hdhomerun-config - Configuration utility for Silicon Dust HD HomeRun
libhdhomerun-dev - Development library for Silicon Dust HD HomeRun
libhdhomerun4 - Library for Silicon Dust HD HomeRun
Changes:
libhdhomerun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 21:55:36 -0800
Source: email-reminder
Binary: email-reminder
Architecture: source all
Version: 0.7.8-5
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 22:29:25 -0800
Source: gnome3-emblems
Binary: nautilus-emblems
Architecture: source all
Version: 0.3.1-5
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 22:21:06 -0800
Source: git-secrets
Binary: git-secrets
Architecture: source all
Version: 1.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
git
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 22:11:45 -0800
Source: fcheck
Binary: fcheck
Architecture: source all
Version: 2.7.59-22
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
fcheck
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 22:17:27 -0800
Source: fuzzyocr
Binary: fuzzyocr
Architecture: source all
Version: 3.6.0-12
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
fuzzyocr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 22:15:36 -0800
Source: atool
Binary: atool
Architecture: source all
Version: 0.39.0-9
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
atool - tool
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 21:49:36 -0800
Source: atool
Binary: atool
Architecture: source all
Version: 0.39.0-8
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
atool - tool
I will unfortunately not be around for the meeting on Sunday, but here are
the topics that I would have liked to bring up, in order of urgency:
1. backups (DB and app)
2. automatic letsencrypt cert renewal
3. domain transfer
For #1, I wanted to ask what backups were in place today for the
libfko3 libfko3-dbgsym libfko3-dev
Architecture: source all amd64
Version: 2.6.10-2
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
fwknop-apparmor-profile - FireWall KNock OPerator - Apparmor profile
fwknop-client - FireWall KNock
The attached patch seems to fix the problem for me.
Francois
--
https://fmarier.org/
diff -u /usr/bin/ssl-cert-check ssl-cert-check
--- /usr/bin/ssl-cert-check 2019-02-26 21:24:00.0 -0800
+++ ssl-cert-check 2019-02-27 10:04:34.331729364 -0800
@@ -658,9 +658,9 @@
fi
if [
Package: ssl-cert-check
Version: 4.10-1
Severity: important
Tags: upstream
It appears that version 4.10 no longer supports checking the certificates of
servers that only support TLS 1.2, as recommended by Mozilla:
https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility
Here's
libfko3 libfko3-dbgsym libfko3-dev
Architecture: source all amd64
Version: 2.6.10-1
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
fwknop-apparmor-profile - FireWall KNock OPerator - Apparmor profile
fwknop-client - FireWall KNock
The updated package I am working on is here:
https://salsa.debian.org/debian/fwknop
Francois
--
https://fmarier.org/
Source: fwknop
Version: 2.6.9-2
Severity: wishlist
A new upstream version is available:
https://github.com/mrash/fwknop/releases/tag/2.6.10
Francois
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture:
As mentioned in bug #922989, the new upstream version avoids setting the
SENDER value to an invalid one and so this bug will be fixed once the
package is updated.
Francois
--
https://fmarier.org/
Package: ssl-cert-check
Version: 3.30-2
Severity: normal
The default sender address is set "postmaster@localhost.localdomain" and when
the destination emails are external to the local machine, that usually gets
flagged as spam.
This can be overriden with the `-E` flag, but ideally the default in
Package: ssl-cert-check
Version: 3.30-2
Severity: normal
A new upstream version of ssl-cert-check is available: 4.10
https://github.com/Matty9191/ssl-cert-check/blob/master/ssl-cert-check
In particular, it includes mail client fixes.
Francois
--
https://fmarier.org/
On 2019-02-22 at 09:05:01, Tristan Le Guern wrote:
> Thanks for your work. Is it possible to contribute directly to this
> repository or is it just a mirror ?
You can't contribute on GitHub (it's read-only), but it is possible to push
to branchable.com using git though you might need to be a wiki
Now that the big move has happened, there are a few things that can be done,
and they don't require access to the server or knowledge of the new
codebase.
So if you want to help:
- introduce the new team and codebase on the blog!
- wiki updates:
- document server setup
- add info on how to
I imagine that by now everybody here has noticed the change, but at the risk
of stating the obvious: the migration was successful!
Thank you to everyone who make this happen. I know it was an enormous amount
of work over the past few months and it warms my heart to see so many people
keen to keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 10 Feb 2019 13:13:24 -0800
Source: git-secrets
Binary: git-secrets
Architecture: source all
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
git
On 2019-02-07 at 11:43:47, clime wrote:
> I don't have access to the existing/old server. I would appreciate if
> somebody
> else could dump the data and store them at /mnt/data/... on the new server
> where
> I just fetch them and continue from there. The same for the certs.
Can we put ofalk in
Overall, that sounds good to me. Here are a few comments.
On 2019-02-06 at 19:45:27, clime wrote:
> There is section "Preparing the new server" in the beginning, which I would
> imagine happens on 17th Feb Sunday. What I need there is:
>
> 1) ssl httpd certificates copied to
On 2019-01-29 at 11:06:57, Tristan Le Guern wrote:
> They suggested either we create a new account with a dedicated
> @libravatar.org email address or the current owner creates a new
> organisation[1] under his account. The domain names will then need to be
> transferred to whatever we choose.
Based on the results from this survey:
https://framadate.org/6M4LoPdqn3VNHoun
I'd like to suggest that we schedule the migration for 18 Feb.
The only other date that works for clime, ofalk and myself is 10 Feb and
that's probably a bit too tight. Doing it on the 18th also gives us one more
On 2018-11-04 at 18:55:55, intrig...@debian.org wrote:
> This package depends on libgtk2-perl, that I intend to remove
> from testing soon after the Buster release, and then from sid at
> some later point during the Bullseye development cycle:
>
>https://bugs.debian.org/912860
>
> I notice
It looks like the experimental version of kmymoney is no longer installable
in sid:
$ LANG=C sudo apt install libkf5newstuffcore5
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
It looks like the experimental version of kmymoney is no longer installable
in sid:
$ LANG=C sudo apt install libkf5newstuffcore5
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
On 2019-01-21 at 15:48:29, Bernhard Übelacker wrote:
> this looks like a duplicate of bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919765
Indeed. Thanks for that.
--
https://fmarier.org/
Package: akregator
Version: 4:18.08.1-1
Severity: grave
Justification: renders package unusable
akregator doesn't start anymore. It exits with the following error message:
akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5:
undefined symbol:
Package: akregator
Version: 4:18.08.1-1
Severity: grave
Justification: renders package unusable
akregator doesn't start anymore. It exits with the following error message:
akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5:
undefined symbol:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 15 Jan 2019 08:33:45 -0800
Source: git-secrets
Binary: git-secrets
Architecture: source all
Version: 1.2.1+c11c229-2
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 14 Jan 2019 12:40:14 -0800
Source: git-secrets
Binary: git-secrets
Architecture: source amd64
Version: 1.2.1+c11c229-1
Distribution: unstable
Urgency: low
Maintainer: Francois Marier
Changed-By: Francois Marier
Description
Package: wnpp
Severity: wishlist
Owner: Francois Marier
* Package name: git-secrets
Version : 1.2.1
Upstream Author : Michael Dowling
* URL : https://github.com/awslabs/git-secrets
* License : Apache 2.0
Programming Lang: Bash
Description : Prevents
+git20180626.aebd88e-1
ii openssh-client 1:7.9p1-4
ii procps 2:3.3.15-2
chkrootkit recommends no packages.
chkrootkit suggests no packages.
-- debconf information:
chkrootkit/diff_mode: false
chkrootkit/run_daily_opts: -q
* chkrootkit/run_daily: false
Author: Francois Marier
Quoting the libinput FAQ [0], this is generally due to a slow/overloaded
Xorg/Wayland client:
"What causes the “timer offset negative” warning?
libinput relies on the caller to call libinput_dispatch() whenever data is
available on the epoll-fd. Doing so will process the state of all devices
and
On 2018-12-29 at 22:58:06, clime wrote:
> are we allowed to use the current libravatar's wiki for the new instance?
I think that's what it's for, yes :) d...@libravatar.org is the admin account
for the wiki.
All I would ask however is that the pages that are entirely obsolete (e.g.
server setup)
On 2018-12-28 at 20:31:46, clime wrote:
> Currently, ofalk's mailgun account is used but I assume it is only
> temporary? Do we want to use mailgun or just standard SMTP? I think,
> SMTP would be good enough. Should we configure Lars' email server
> as the outgoing SMTP server for server emails
On 2018-12-28 at 16:02:53, clime wrote:
> on Contact page, there is the following text under Email:
>
> Finally, if you need to email us: d...@libravatar.org
>
> Will we have this email address available after launch? Thanks for taking a
> look at this.
Yes, that alias is now setup on Lars'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 08 Dec 2018 11:22:30 -0800
Source: txlibravatar
Binary: python-txlibravatar
Architecture: source all
Version: 1.1-14
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 08 Dec 2018 11:20:29 -0800
Source: safe-rm
Binary: safe-rm
Architecture: source all
Version: 0.12-7
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
safe-rm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 08 Dec 2018 11:14:30 -0800
Source: pylibravatar
Binary: python-libravatar python3-libravatar
Architecture: source all
Version: 1.7-4
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 08 Dec 2018 11:12:48 -0800
Source: planetfilter
Binary: planetfilter
Architecture: source all
Version: 0.8.1-4
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description
Here are my thoughts.
On 2018-11-23 at 11:16:54, Tristan Le Guern wrote:
> + ivatar returns an HTML document, the home page ;
> + libravatar and libravatar.cgi both return the file nobody.png.
In general, I think we should always return an image. That's what the
clients are expecting.
> *
Package: devscripts
Version: 2.18.7
Severity: normal
Tags: patch
When running uscan, I get the following warning message:
$ mkdir test
$ cd test
$ uscan --report
Useless use of concatenation (.) or string in void context at
/usr/share/perl5/Devscripts/Uscan/Downloader.pm line 106.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 16 Oct 2018 18:10:38 -0700
Source: workrave
Binary: workrave workrave-data
Architecture: source all amd64
Version: 1.10.23-2
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
On 2018-10-15 at 09:03:54, wim wrote:
> in about 80% of the cases, whenever workrave tries to "intervene" with a
> break or other notice,
> the desktop flickers and needs reloading,
> sometimes the desktop needs to be restarted
>
> this could be related to #503684 ?
I just closed that old bug.
On 2018-10-12 at 01:25:47, clime wrote:
> I believe, the next steps should be to move production data there and test
> it.
Do we have a plan for importing the data?
I vaguely remember hearing that the new codebase doesn't use the same DB
schema, so it's not going to be as simple as pg_dump &
Source: etbemon
Version: 1.3.3-3
Severity: normal
Tags: patch
The sample config in README.monitors under the "freespace.monitor" section
is invalid and I suspect now outdated.
Here's a fix for it:
--- README.monitors 2018-10-10 08:28:58.426445460 -0700
+++ README.monitors.fixed
Source: etbemon
Version: 1.3.3-3
Severity: important
After installing mon, I got the following tiger warning email:
# Checking listening processes
NEW: --WARN-- [lin003w] The process `mon' is listening on socket 2583 (UDP on
every interface) is run by mon.
I realized that the fix for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 01 Oct 2018 22:53:00 -0700
Source: workrave
Binary: workrave workrave-data
Architecture: source all amd64
Version: 1.10.23-1
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 01 Oct 2018 10:48:07 -0700
Source: cowsay
Binary: cowsay cowsay-off
Architecture: source all
Version: 3.03+dfsg2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Francois Marier
Description
Thanks for bringing this up on the list Oliver.
The first two things I want to say are:
1. My opinion on the name should not matter much here because it should be
up to the people stepping up to take the project in the direction they
want.
2. There is no question that I will transfer the
On 2018-09-30 at 17:52:27, Lars Kruse wrote:
> yes, this is today :)
I have to send my apologies since I won't be able to make the meeting today.
The only thing left on my plate is to move the server backups away from
Amazon S3 and then the incoming @libravatar.org emails away from Google
Apps.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 20 Sep 2018 14:21:01 -0700
Source: rkhunter
Binary: rkhunter
Architecture: source all
Version: 1.4.6-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
Changed-By: Francois Marier
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 08 Sep 2018 11:16:28 -0700
Source: workrave
Binary: workrave workrave-data
Architecture: source all amd64
Version: 1.10.21-1
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
On 2018-09-01 at 14:44:16, Till Kamppeter wrote:
> Bernhard, thank for the patch. I have applied it now (and also done an
> additional fix for DomainSocket) and committed it to the upstream GIT repo.
>
> Please test.
Happy to test things. Just to be clear, do you want me to clone the repo,
build
I installed systemd-coredump and this is what I see in my logs now:
Aug 27 23:04:37 hostname systemd[1]: Listening on Process Core Dump Socket.
Aug 27 23:05:34 hostname cups-browsed[29428]: munmap_chunk(): invalid pointer
Aug 27 23:05:34 hostname systemd[1]: Created slice
Package: cups
Version: 2.2.8-5
Severity: normal
Once a day, I get a message like this in my logs:
Aug 27 00:00:02 hostname cups-browsed[6122]: munmap_chunk(): invalid pointer
Aug 27 00:00:02 hostname systemd[1]: cups-browsed.service: Main process
exited, code=dumped, status=6/ABRT
Aug 27
Package: tor
Version: 0.3.3.9-1
Severity: normal
I get the following error in my logs approximately every 2 hours:
Aug 26 05:05:01 hostname Tor[25963]: TLS error while constructing a TLS
context: dh key too small (in SSL routines:ssl3_ctx_ctrl:---)
I tried upgrading to the version in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 23 Aug 2018 23:38:32 -0700
Source: fcheck
Binary: fcheck
Architecture: source all
Version: 2.7.59-21
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
fcheck
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 21 Aug 2018 20:39:31 -0700
Source: libhdhomerun
Binary: hdhomerun-config libhdhomerun4 libhdhomerun-dev
Architecture: source amd64
Version: 20180817-1
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed
tags 902875 +patch
thanks
According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902413#12,
all that's needed is to change `/var/run/` to `/run/` in
/usr/lib/tmpfiles.d/postgresql.conf.
I've attached a patch.
Francois
--
https://fmarier.org/
diff --git
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 09 Aug 2018 19:57:22 -0700
Source: rkhunter
Binary: rkhunter
Architecture: source all
Version: 1.4.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
Changed-By: Francois Marier
Description
I took a look at the details of the diversion that the latest version of
dash sets up and it's really quite complicated. It's not clear that I could
easily get it right, even copying that code, and the consequences of getting
it wrong could be disastrous.
So instead I went for an easier approach:
I took a look at the details of the diversion that the latest version of
dash sets up and it's really quite complicated. It's not clear that I could
easily get it right, even copying that code, and the consequences of getting
it wrong could be disastrous.
So instead I went for an easier approach:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 04 Aug 2018 13:25:52 -0700
Source: safe-rm
Binary: safe-rm
Architecture: source all
Version: 0.12-6
Distribution: unstable
Urgency: high
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
safe-rm
On 2018-04-03 at 09:07:35, Francois Marier wrote:
> The official announcement is here:
> https://blog.libravatar.org/posts/Libravatar.org_is_shutting_down_on_2018-09-01/
I have just posted an update to the above post:
https://blog.libravatar.org/posts/Libravatar.org_is_not_goin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 27 Jul 2018 11:02:58 -0700
Source: safe-rm
Binary: safe-rm
Architecture: source all
Version: 0.12-5
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
safe-rm
Package: units
Version: 2.17-1
Severity: normal
It looks like /var/lib/units/currency.units is updated on cron once a day.
This means that this file no longer matches the checksum that was generated
at package creation time and so tools like reportbug and debsums will warn
about it:
System
Package: postgresql-common
Version: 191
Severity: normal
Once a day, I get the following systemd warning message in my logs:
Jul 1 20:50:01 hostname systemd-tmpfiles[21472]:
[/usr/lib/tmpfiles.d/postgresql.conf:2] Line references path below legacy
directory /var/run/, updating
Package: postgresql-common
Version: 191
Severity: normal
Once a day, I get the following systemd warning message in my logs:
Jul 1 20:50:01 hostname systemd-tmpfiles[21472]:
[/usr/lib/tmpfiles.d/postgresql.conf:2] Line references path below legacy
directory /var/run/, updating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 09 Jun 2018 15:07:47 -0700
Source: safe-rm
Binary: safe-rm
Architecture: source all
Version: 0.12-4
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Description:
safe-rm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 20 May 2018 15:02:32 -0700
Source: atool
Binary: atool
Architecture: source all
Version: 0.39.0-7
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Francois Marier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 18 May 2018 22:32:05 -0700
Source: planetfilter
Binary: planetfilter
Architecture: source all
Version: 0.8.1-3
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Fr
https://bugs.kde.org/show_bug.cgi?id=199232
Francois Marier <franc...@fmarier.org> changed:
What|Removed |Added
CC||franc...@fmari
https://bugs.kde.org/show_bug.cgi?id=199232
Francois Marier <franc...@fmarier.org> changed:
What|Removed |Added
CC||franc...@fmari
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 14 May 2018 19:16:45 -0700
Source: pdfresurrect
Binary: pdfresurrect
Architecture: source amd64
Version: 0.15-1
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Fr
Is there an alternative for decoding QR codes in Debian?
The closest thing I could find was dmtx-utils but that looks like a
different kind of code and it's also dead upstream
(https://web.archive.org/web/20150808104301/http://www.libdmtx.org:80/).
It seems like everything that decodes QR codes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 10 May 2018 20:29:19 -0700
Source: txlibravatar
Binary: python-txlibravatar
Architecture: source all
Version: 1.1-13
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 10 May 2018 20:19:32 -0700
Source: safe-rm
Binary: safe-rm
Architecture: source all
Version: 0.12-3
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Francois Marier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 10 May 2018 08:56:16 -0700
Source: reboot-notifier
Binary: reboot-notifier
Architecture: source all
Version: 0.7
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 10 May 2018 09:56:31 -0700
Source: renameutils
Binary: renameutils
Architecture: source amd64
Version: 0.12.0-6
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 06 May 2018 15:25:21 -0700
Source: planetfilter
Binary: planetfilter
Architecture: source all
Version: 0.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 06 May 2018 15:37:37 -0700
Source: pylibravatar
Binary: python-libravatar python3-libravatar
Architecture: source all
Version: 1.7-3
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 06 May 2018 15:13:35 -0700
Source: pdfresurrect
Binary: pdfresurrect
Architecture: source amd64
Version: 0.14-2
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 06 May 2018 15:04:13 -0700
Source: node-libravatar
Binary: node-libravatar
Architecture: source all
Version: 2.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 06 May 2018 14:57:50 -0700
Source: gnome3-emblems
Binary: nautilus-emblems
Architecture: source all
Version: 0.3.1-4
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 06 May 2018 14:42:04 -0700
Source: fuzzyocr
Binary: fuzzyocr
Architecture: source all
Version: 3.6.0-11
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Francois
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 06 May 2018 14:34:56 -0700
Source: fcheck
Binary: fcheck
Architecture: source all
Version: 2.7.59-20
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Francois Marier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 06 May 2018 14:17:03 -0700
Source: email-reminder
Binary: email-reminder
Architecture: source all
Version: 0.7.8-4
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 06 May 2018 13:58:07 -0700
Source: atool
Binary: atool
Architecture: source all
Version: 0.39.0-6
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier <franc...@debian.org>
Changed-By: Francois Marier
On 09/04/18 07:25 PM, Francois Marier wrote:
> We intend to ship same-site cookies in Firefox 61.
This has now been uplifted and will be shipping in Firefox 60.
Status can be tracked on https://wiki.mozilla.org/Security/SameSiteCookies.
Franc
301 - 400 of 2859 matches
Mail list logo
