-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 28 Feb 2017 07:32:32 +
Source: willow
Binary: python-willow python-willow-doc
Architecture: source
Version: 0.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 28 Feb 2017 12:18:00 +0500
Source: pyvenv-el
Binary: elpa-pyvenv
Architecture: source all
Version: 1.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 28 Feb 2017 07:56:18 +0100
Source: josm
Binary: josm josm-l10n
Architecture: source all
Version: 0.0.svn11639+dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 28 Feb 2017 07:56:50 +0100
Source: josm-plugins
Binary: josm-plugins
Architecture: source all
Version: 0.0.svn33172+ds-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project
On Mon, 2017-02-27 at 19:30 -0800, Russ Allbery wrote:
> Ben Hutchings writes:
> > On Mon, 2017-02-27 at 16:09 -0800, Russ Allbery wrote:
> > > Daniel Pocock writes:
> > > > However, at the time when I ran ntpdate, ntp was not running. I had
> > > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 28 Feb 2017 04:35:07 +
Source: linux-signed
Binary: kernel-image-4.9.0-2-amd64-di nic-modules-4.9.0-2-amd64-di
nic-wireless-modules-4.9.0-2-amd64-di nic-shared-modules-4.9.0-2-amd64-di
serial-modules-4.9.0-2-amd64-di
Package: wnpp
Severity: wishlist
Owner: =?utf-8?b?Q2hhbmdaaHVvIENoZW4gKOmZs+aYjOWArCk=?=
* Package name: kanboard-cli
Version : 0.0.2
Upstream Author : Copyright (c) 2016 Frederic Guillot
* URL : https://github.com/kanboard/kanboard-cli
* License
Ben Hutchings writes:
> On Mon, 2017-02-27 at 16:09 -0800, Russ Allbery wrote:
>>> Daniel Pocock writes:
>>> However, at the time when I ran ntpdate, ntp was not running. I had
>>> brought up the network manually due to an interface renaming issue on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 20:01:43 -0600
Source: r-base
Binary: r-base r-base-core r-base-dev r-mathlib r-base-html r-doc-pdf
r-doc-html r-doc-info r-recommended r-base-core-dbg
Architecture: source amd64 all
Version: 3.3.2.20170227-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 27 Feb 2017 19:34:24 -0700
Source: haskell-raaz
Binary: libghc-raaz-dev libghc-raaz-prof libghc-raaz-doc
Architecture: source
Version: 0.1.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Haskell Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 28 Feb 2017 02:30:38 +0100
Source: file-roller
Binary: file-roller
Architecture: source
Version: 3.22.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
On Mon, 2017-02-27 at 16:09 -0800, Russ Allbery wrote:
> > Daniel Pocock writes:
>
> > However, at the time when I ran ntpdate, ntp was not running. I had
> > brought up the network manually due to an interface renaming issue on
> > the first boot. Maybe when somebody runs
Ben Hutchings writes:
> On Mon, 2017-02-27 at 11:18 -0800, Russ Allbery wrote:
>> The much simpler systemd-timesyncd doesn't set the hardware clock for
>> reasons that one may or may not agree with (I honestly haven't
>> researched it in any depth),
> It looks like it does
Daniel Pocock writes:
> However, at the time when I ran ntpdate, ntp was not running. I had
> brought up the network manually due to an interface renaming issue on
> the first boot. Maybe when somebody runs ntpdate in a scenario like
> that the kernel is not sending the new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 06:00:37 -0600
Source: quantlib
Binary: libquantlib0v5 libquantlib0-dev quantlib-examples
Architecture: source amd64
Version: 1.9.2-1
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 28 Feb 2017 01:01:32 +0100
Source: fping
Binary: fping
Architecture: source amd64
Version: 4.0~rc3-1
Distribution: experimental
Urgency: low
Maintainer: Axel Beckert
Changed-By: Axel Beckert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 23:15:30 +0100
Source: libquicktime
Binary: libquicktime2 libquicktime-dev libquicktime-doc quicktime-utils
quicktime-x11utils
Architecture: source
Version: 2:1.2.4-10
Distribution: unstable
Urgency: medium
On Mon, Feb 27, 2017 at 03:18:04PM +, Jeremy Stanley wrote:
> It's not packaged for Debian yet nor do I see any RFP/ITP, but I've
> been happily using https://github.com/tehmaze/diagram for a few
> years (installable from PyPI via pip so probably easy enough to
> package). Its default mode
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 23:20:27 +0100
Source: yade
Binary: yade libyade python-yade yade-doc
Architecture: source
Version: 2017.01a-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 27 Feb 2017 21:23:25 +0100
Source: lmdb
Binary: lmdb-utils liblmdb0 liblmdb-dev lmdb-doc
Architecture: source
Version: 0.9.19-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Berkeley DB Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 27 Feb 2017 15:58:07 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-2 linux-doc-4.9 linux-manual-4.9
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9
libusbip-dev usbip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 20:07:41 +0100
Source: libvirt
Binary: libvirt-clients libvirt-daemon libvirt-daemon-system libvirt0
libvirt-doc libvirt-dev libvirt-sanlock libnss-libvirt
Architecture: source
Version: 3.0.0-3
Distribution:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 21:10:29 +0100
Source: libebur128
Binary: libebur128-dev libebur128-1
Architecture: source
Version: 1.2.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 27 Feb 2017 14:01:13 -0600
Source: fwupd
Binary: libfwupd1 libdfu1 libebitdo1 fwupd fwupd-doc libfwupd-dev
gir1.2-fwupd-1.0 libdfu-dev libebitdo-dev
Architecture: source amd64 all
Version: 0.8.1-2
Distribution: unstable
On 27/02/17 20:18, Russ Allbery wrote:
> Daniel Pocock writes:
>
>> I've observed a system that had a wildly incorrect hardware clock (when
>> it was first unboxed), I ran ntpdate to sync the kernel clock but after
>> a shutdown and startup again it had a wacky time again.
>
On Mon, 2017-02-27 at 11:18 -0800, Russ Allbery wrote:
> > Daniel Pocock writes:
>
> > I've observed a system that had a wildly incorrect hardware clock (when
> > it was first unboxed), I ran ntpdate to sync the kernel clock but after
> > a shutdown and startup again it had a
Daniel Pocock writes:
> I've observed a system that had a wildly incorrect hardware clock (when
> it was first unboxed), I ran ntpdate to sync the kernel clock but after
> a shutdown and startup again it had a wacky time again.
> I came across the discussion about how the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 20:23:59 +0100
Source: libinput
Binary: libinput10 libinput-bin libinput10-udeb libinput-dev libinput-tools
Architecture: source
Version: 1.6.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 27 Feb 2017 19:39:57 +0100
Source: mdocml
Binary: mandoc
Architecture: source
Version: 1.14.1-2
Distribution: experimental
Urgency: medium
Maintainer: Bdale Garbee
Changed-By: Michael Stapelberg
Package: wnpp
Severity: wishlist
Owner: =?utf-8?q?F=C3=A9lix_Sipma?=
* Package name: imm
Version : 1.1.0.0
Upstream Author : k0ral
* URL : https://github.com/k0ral/imm
* License : Public domain
Programming Lang:
On Mon, Feb 27, 2017 at 05:59:53PM +0100, Daniel Pocock wrote:
> Can anybody make any suggestions or add anything to the wiki?
My old Mac Mini had a crazy clock and ntp was not enough to sanitize it.
I fixed it by using adjtimex in addition to ntp.
As an example, my clock was off by 2890 parts
Andrey Rahmatullin writes ("Re: sane chromium default flags - include
--enable-remote-extensions"):
> [Ian Jackson:]
> > Can we not make the updates work for non-Debian-packaged extensions,
> > while disabling them for Debian-packaged ones ?
> >
> > If we did that then there would no need to
Hi all,
I've observed a system that had a wildly incorrect hardware clock (when
it was first unboxed), I ran ntpdate to sync the kernel clock but after
a shutdown and startup again it had a wacky time again.
I came across the discussion about how the hardware clock is no longer
set at
On Mon, Feb 27, 2017 at 04:43:29PM +, Ian Jackson wrote:
> > > Do we know why this is ? Is this an unintended side effect of some
> > > other change ? Has someone done this deliberately and if so have they
> > > explained what they were trying to achieve ?
> > >
> > > I can see that the
Andrey Rahmatullin writes ("Re: sane chromium default flags - include
--enable-remote-extensions"):
> On Mon, Feb 27, 2017 at 03:14:08PM +, Ian Jackson wrote:
> > Do we know why this is ? Is this an unintended side effect of some
> > other change ? Has someone done this deliberately and if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 02 Feb 2017 13:23:41 +
Source: cloud-init
Binary: cloud-init
Architecture: source all
Version: 0.7.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cloud Team
Changed-By: Thomas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 27 Feb 2017 08:33:23 -0600
Source: fwupd
Binary: libfwupd1 libdfu1 libebitdo1 fwupd fwupd-doc libfwupd-dev
gir1.2-fwupd-1.0 libdfu-dev libebitdo-dev
Architecture: source amd64 all
Version: 0.8.1-1
Distribution: unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 05 Feb 2017 08:32:31 +0300
Source: bglibs
Binary: libbg2 libbg-dev libbg2-doc
Architecture: source
Version: 2.03+dfsg-2
Distribution: experimental
Urgency: medium
Maintainer: Debian QA Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 13 Feb 2017 21:19:07 +0100
Source: smplayer
Binary: smplayer smplayer-l10n
Architecture: source
Version: 17.2.0~ds0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers
On Mon, Feb 27, 2017 at 03:14:08PM +, Ian Jackson wrote:
> > It's not even about updating: the first version of chromium with this
> > build-time tweak simply disabled all already installed extensions for me
> > so they were not activated when I restarted chromium after that upgrade
> >
On 2017-02-25 18:24:33 +0100 (+0100), Adam Borowski wrote:
[...]
> It looks like no one made a histogram tool using high-resolution
> Braille yet, thus I'll add some features (like auto-scaling Y axis
> -- doing it manually is tedious, horizontal mode, etc) and package
> this part.
[...]
It's not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 15:50:54 +0100
Source: edtsurf
Binary: edtsurf
Architecture: source amd64
Version: 0.2009-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 12:23:46 +0100
Source: igtf-policy-bundle
Binary: igtf-policy-classic igtf-policy-mics igtf-policy-slcs igtf-policy-iota
igtf-policy-unaccredited igtf-policy-experimental
Architecture: source all
Version: 1.81-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 25 Feb 2017 15:20:24 +0100
Source: icinga-web
Binary: icinga-web icinga-web-config-icinga icinga-web-config-icinga2-ido-mysql
icinga-web-config-icinga2-ido-pgsql icinga-web-pnp
Architecture: source
Version: 1.13.1-2.1
Konstantin Khomoutov writes ("Re: sane chromium default flags - include
--enable-remote-extensions"):
> It's not even about updating: the first version of chromium with this
> build-time tweak simply disabled all already installed extensions for me
> so they were not activated when I restarted
Michael Gilbert writes ("Re: sane chromium default flags - include
--enable-remote-extensions [and 1 more messages]"):
> On Fri, Feb 24, 2017 at 10:05 AM, Ian Jackson wrote:
> > It seems likely to me that this is a bug, not some kind of
> > "ideological mistake".
>
> You basically nailed it,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 27 Feb 2017 11:35:15 +0100
Source: knot
Binary: knot libknot5 libzscanner1 libdnssec2 libknot-dev knot-dnsutils
knot-host knot-doc
Architecture: source
Version: 2.4.1-2
Distribution: unstable
Urgency: medium
Maintainer:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 20 Feb 2017 14:15:34 -0500
Source: libzypp
Binary: libzypp libzypp-dbg libzypp-dev libzypp-common libzypp-bin
libzypp-config libzypp-doc
Architecture: source amd64 all
Version: 16.4.3-1
Distribution: unstable
Urgency: medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 11:07:54 +0100
Source: ctpp2
Binary: ctpp2-utils ctpp2-doc libctpp2-2v5 libctpp2-2v5-dbg libctpp2-dev
Architecture: source all amd64
Version: 2.8.3-20.1
Distribution: sid
Urgency: medium
Maintainer: Vasudev Kamath
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 10:56:07 +0100
Source: latex-make
Binary: latex-make
Architecture: all source
Version: 2.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Vincent Danjean
Changed-By: Vincent Danjean
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2017 09:41:20 +
Source: clippoly
Binary: libclippoly0 libclippoly-dev
Architecture: source amd64
Version: 0.11-7
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 26 Feb 2017 19:53:00 -0300
Source: retroarch
Binary: retroarch
Architecture: source
Version: 1.4.1+dfsg1-1
Distribution: experimental
Urgency: low
Maintainer: Debian Games Team
The Wanderer writes:
> On 2017-02-26 at 09:01, Lars Wirzenius wrote:
>
>> * John Cuffs tells Lee to "shut the fuck up", and quotes a spam that
>> isn't visible (anymore?) in the bug log.
>
> Just to note: this almost certainly wasn't actually addressing any of
> the
53 matches
Mail list logo