-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 06 Feb 2020 07:58:33 +0100
Source: python-fakeredis
Architecture: source
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Ondřej Kobližek
Changes:
python-fakeredis
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,
pkg-rust-maintain...@lists.alioth.debian.org
Package name: boringtun
Version: 0.2.0
Upstream Author: Cloudflare, Inc.
License: BSD-3-Clause
URL: https://github.com/cloudflare/boringtun
❦ 6 février 2020 09:50 +11, Dmitry Smirnov :
>> and 2) continuing to use rsyslog isn't an option if the default changes.
>
> No. I just don't want default to change. IMHO rationale for this is weak but
> everybody keeps arguing that it would not be a big deal. In time we will see
> how that
From where I stand it seems to me that you actually don’t care about free
software or DFSG or Debian and you only care about enforcing your worldview
upon others. You need to stop, go read DFSG and come back only if you and come
back with valid arguments how the DFSG is being violated. Or just
And yet you *demand* in a very aggressive way that others dedicate their
capacity on your misinterpretation of DFSG. Just stop.
Thanks,
--
Ondřej Surý
> On 6 Feb 2020, at 00:27, Dmitry Smirnov wrote:
>
> I would have done so if I had enough capacity.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 06 Feb 2020 07:19:22 +0100
Source: ocaml-sedlex
Architecture: source
Version: 2.1-5
Distribution: unstable
Urgency: high
Maintainer: Debian OCaml Maintainers
Changed-By: Stéphane Glondu
Changes:
ocaml-sedlex (2.1-5)
I think you should stop here and now. You are misinterpreting DFSG to make a
point. And instead of asking how you can help you just throw accusations. In
both you recent threads. We are all in this together and your style is not
helpful just hurtful.
Ondrej
--
Ondřej Surý
> On 6 Feb 2020, at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 06 Feb 2020 07:04:36 +0100
Source: poco
Architecture: source
Version: 1.10.0-3
Distribution: experimental
Urgency: medium
Maintainer: Krzysztof Burghardt
Changed-By: Jochen Sprickerhof
Changes:
poco (1.10.0-3) experimental;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 06 Feb 2020 07:14:50 +0100
Source: ocaml-result
Architecture: source
Version: 1.4-4
Distribution: unstable
Urgency: high
Maintainer: Debian OCaml Maintainers
Changed-By: Stéphane Glondu
Changes:
ocaml-result (1.4-4)
Spiritually I really would like to see a transparent workflow of the FTP
team. If it were a couple years ago I may stand in the same position as
you. But now I'd kindly invite you to review the FTP team workflow (I
joined the FTP team in order to review it), review the functionalities
of dak (at
On February 5, 2020 8:44:43 PM UTC, Dmitry Smirnov wrote:
>On Wednesday, 5 February 2020 11:01:08 AM AEDT Scott Kitterman wrote:
>> We just had a GR where the project voted it was just fine to systemd
>all
>> the things, so this sort of thing is to be expected.
>
>Are you suggesting that
On February 5, 2020 8:43:43 AM UTC, Bastian Blank wrote:
>Hi Scott
>
>On Wed, Feb 05, 2020 at 07:44:25AM +, Scott Kitterman wrote:
>> >> Of course the fact that I can't use all the tools available to
>> >manipulate text
>> >> files to follow or analyze logs is problematic. If I'm using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 23:11:57 -0600
Source: digikam
Architecture: source
Version: 4:6.4.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team
Changed-By: Steve M. Robbins
Closes: 950731
Changes:
digikam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 19:54:40 -0800
Source: zookeeper
Architecture: source
Version: 3.4.13-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers
Changed-By: tony mancill
Closes: 950755
Changes:
zookeeper
Hi Mo,
thanks for your interest in our projects.
> As you know, I cannot help to care about every topic about Debian + AI.
:-D You are doing already an incredible amount.
> For good wish, could you please make a list of packages involved in
> these projects, so I can inspect them and make sure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Feb 2020 11:59:39 +0800
Source: avogadrolibs
Architecture: source
Version: 1.93.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team
Changed-By: Drew Parsons
Changes:
avogadrolibs (1.93.0-1) unstable;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Feb 2020 00:49:31 -0300
Source: csoundqt
Architecture: source
Version: 0.9.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Felipe Sateler
Changes:
csoundqt (0.9.7-1)
On 2/5/20 7:36 PM, Paul Wise wrote:
> AFAICT from Debian's FHS
> documentation, since /srv is laid out differently on different hosts
> packages should not rely on a particular layout. My interpretation is
> of this is that packages should never touch /srv unless directed to do
> so by the
On Thu, Feb 06, 2020 at 09:50:36AM +1100, Dmitry Smirnov wrote:
On Thursday, 6 February 2020 9:04:33 AM AEDT Michael Stone wrote:
Nobody said "exclusively" except you!
It was suggested that default will change and I'm concerned about that.
And yet you said "exclusively" and generally argued
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 06 Feb 2020 08:53:34 +0700
Source: notary
Architecture: source
Version: 0.6.1~ds2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team
Changed-By: Arnaud Rebillout
Closes: 944346
Changes:
notary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 23:06:41 -0300
Source: pulseaudio
Architecture: source
Version: 13.0-5
Distribution: unstable
Urgency: medium
Maintainer: Pulseaudio maintenance team
Changed-By: Felipe Sateler
Closes: 950413
Changes:
This is not a disagreement with anything you write.
I've noticed that there is a lot more configuration that gets encoded in
the initramfs than I thought.
The most surprising for me is that if you want to control the names of
network devices or anything else set by the .link file,
that ends up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 06 Feb 2020 01:57:30 +0100
Source: reprotest
Architecture: source
Version: 0.7.13
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks
Changed-By: Holger Levsen
Changes:
reprotest (0.7.13) unstable;
Hi all,
In [1] there are several packages that reference /srv in their
maintainer scripts or debconf prompts. AFAICT from Debian's FHS
documentation, since /srv is laid out differently on different hosts
packages should not rely on a particular layout. My interpretation is
of this is that
Dmitry Smirnov writes:
> On Thursday, 6 February 2020 10:22:24 AM AEDT Russ Allbery wrote:
>> I can't speak for Bernd, but I haven't seen any evidence in this thread
>> that the built binary is not DFSG-compliant.
> So now you are going to nitpick on my language with all your eloquence? :(
Please! Not now!
I absolutely think that accountability and transparency for a couple of
delegated teams --and really for delegations in general--needs to be one
of the big issues for the next DPL. I think that's true whether it is
me or someone else.
Our delegates put a lot of time and energy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 06 Feb 2020 01:42:54 +0100
Source: debian-edu
Architecture: source
Version: 2.11.10
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers
Changed-By: Holger Levsen
Changes:
debian-edu (2.11.10) unstable;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 23:52:20 +
Source: gimplensfun
Architecture: source
Version: 0.2.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Evgeni Golov
Changed-By: Peter Michael Green
Closes: 950172
Changes:
gimplensfun
Hello,
I think your dispute goes down to the question if Debian's community
infrastructure should preferably using software packaged for Debian
(which salsa is doing) with the binaries Debian offers (which salsa is
not doing). I find this interesting. The two positions are
A) No idea why this
On Thursday, 6 February 2020 10:22:24 AM AEDT Russ Allbery wrote:
> I can't speak for Bernd, but I haven't seen any evidence in this thread
> that the built binary is not DFSG-compliant.
So now you are going to nitpick on my language with all your eloquence? :(
The first problem is that packaged
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Feb 2020 00:15:16 +0100
Source: toil
Architecture: source
Version: 3.23.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Steffen Moeller
Changes:
toil (3.23.1-1) unstable;
IMHO it is disturbing that one of the most essential processes in Debian
-- acceptance of new and modified packages -- operates almost in secrecy.
Unlike most Debian teams, ftp-masters communicate in private mail list.
I understand why security team might need to operate without full public
El 5/2/20 a las 21:25, Dmitry Smirnov escribió:
> On Tuesday, 26 February 2019 1:19:35 AM AEDT Inaki Malerba wrote:
>> [0] https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md
>
> Thank you for providing this useful service.
>
> My big concern though is that primary
On 2/6/20 12:13 AM, Dmitry Smirnov wrote:
> On Thursday, 6 February 2020 9:52:47 AM AEDT Bernd Zeimetz wrote:
>
>> Really don't care.
>
> I see that... :(
See, I prefer to spend my time on doing open source software. I use
tools I can use and that are provided by others, even if the build
Dmitry Smirnov writes:
> Sources are somewhere, true. But build (binary) is not DFSG-compliant.
> I feel like you are making your point by pretending not to understand...
> Why all this denial?
I can't speak for Bernd, but I haven't seen any evidence in this thread
that the built binary is not
On 2/5/20 5:05 PM, Dmitry Smirnov wrote:
> It should be on abuser
Saying "abuser" is inflammatory, especially as no abuse has been proven.
Please stop.
> to explain that it was not possible to build a
> service in a fully DFSG compliant manner
Why is the current solution not DFSG compliant?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 23:56:55 +0100
Source: r-cran-qtl
Architecture: source
Version: 1.45-11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Steffen Moeller
Changes:
r-cran-qtl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 23:54:28 +0100
Source: golang-1.14
Architecture: source
Version: 1.14~rc1-1
Distribution: unstable
Urgency: medium
Maintainer: Go Compiler Team
Changed-By: Dr. Tobias Quathamer
Closes: 950517
Changes:
On Thursday, 6 February 2020 9:52:47 AM AEDT Bernd Zeimetz wrote:
> Really don't care.
I see that... :(
> You are free to setup and run your own runner.
Just because you did not setup yours properly?
I do maintain my own runner but it is not for everybody due to capacity
constrains.
But
On Wed, 2020-02-05 at 22:42 +, Sudip Mukherjee wrote:
> On Wed, Feb 5, 2020 at 10:22 PM Christian Barcenas
> wrote:
> > Because this changes the versioning scheme from kernel releases
> > (libbpf-dev and libbpf0 currently are at 5.4.13-1 in sid) to libbpf
> > version numbers (0.0.6-1), the
On Thursday, 6 February 2020 9:53:09 AM AEDT Dmitry Smirnov wrote:
> On Thursday, 6 February 2020 9:25:29 AM AEDT intrigeri wrote:
> > I'd love if you would use wording less morally/emotionally loaded than
> > "excuse" here: for me at least, "excuse" is bound to the thought
> > framework of guilt,
On 2/5/20 11:52 PM, Bernd Zeimetz wrote:
> You are free to setup and run your own runner.
> Its even possible to share them for everybody.
> If you do, I'd suggest you add some appropriate tags so people can force
> their builds to run on a runner built from Debian source.
> (there is not
On Thursday, 6 February 2020 9:04:33 AM AEDT Michael Stone wrote:
> Nobody said "exclusively" except you!
It was suggested that default will change and I'm concerned about that.
> Either option has benefits and
> disadvantages, but for some reason you're arguing as though 1) only your
>
On Thursday, 6 February 2020 9:25:29 AM AEDT intrigeri wrote:
> I'd love if you would use wording less morally/emotionally loaded than
> "excuse" here: for me at least, "excuse" is bound to the thought
> framework of guilt, accusation, and absolute right vs. absolute wrong.
> Framing the
On 2/5/20 11:42 PM, Dmitry Smirnov wrote:
> Sources are somewhere, true. But build (binary) is not DFSG-compliant.
Why? Because it was not built in Debian?
> Don't you think it would be _better_ to use (only) components from "main"?
> Certainly there will be more integrity if you can do
Andrey Rahmatullin - 05.02.20, 22:17:14 CET:
> On Thu, Feb 06, 2020 at 07:44:43AM +1100, Dmitry Smirnov wrote:
> > > We just had a GR where the project voted it was just fine to
> > > systemd all the things, so this sort of thing is to be expected.
> >
> > Are you suggesting that voters fully
On Wed, Feb 5, 2020 at 10:22 PM Christian Barcenas
wrote:
>
> Because this changes the versioning scheme from kernel releases
> (libbpf-dev and libbpf0 currently are at 5.4.13-1 in sid) to libbpf
> version numbers (0.0.6-1), the epoch needs to be incremented to 1 I
> believe.
I had this doubt
On Thursday, 6 February 2020 9:11:07 AM AEDT Bernd Zeimetz wrote:
> They are not shipped in Debian, but they are free software,
> binaries with sources being available, as far as I can see all under a
> dfsg free license.
Sources are somewhere, true. But build (binary) is not DFSG-compliant.
I
Because this changes the versioning scheme from kernel releases
(libbpf-dev and libbpf0 currently are at 5.4.13-1 in sid) to libbpf
version numbers (0.0.6-1), the epoch needs to be incremented to 1 I
believe.
CC'ing debian-devel for discussion/consensus, per Debian Policy Manual 5.6.12.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 23:01:35 +0100
Source: glibc
Architecture: source
Version: 2.30-0experimental2
Distribution: experimental
Urgency: medium
Maintainer: GNU Libc Maintainers
Changed-By: Aurelien Jarno
Changes:
glibc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 16:54:09 -0500
Source: fcitx5-gtk
Architecture: source
Version: 0.0~git2019.6f9ef64-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team
Changed-By: Boyuan Yang
Changes:
fcitx5-gtk
Hi,
Dmitry Smirnov (2020-02-06):
> Now when we have a proper package for a while what excuse do you
> have to continue to use vendor binaries that could not be accepted
> to Debian?
I'd love if you would use wording less morally/emotionally loaded than
"excuse" here: for me at least, "excuse" is
On Thu, Feb 06, 2020 at 08:40:29AM +1100, Dmitry Smirnov wrote:
On Thursday, 6 February 2020 6:59:38 AM AEDT Nikolaus Rath wrote:
I would venture that for every user who is grateful that
/var/log/mail.log collects all the various mail-related logs, there is
another user that curses about non
Dmitry Smirnov writes:
> There are log readers like "lnav" and "multitail" that will become
> useless without traditional log files. "lnav" tails multiple logs by
> default and IMHO provides a very useful interface.
> Exclusively relying on systemd logging facilities limits ways in which
> we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 22:56:48 +0100
Source: nvidia-settings-legacy-340xx
Architecture: source
Version: 340.108-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers
Changed-By: Andreas Beckmann
Changes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 22:56:56 +0100
Source: poco
Architecture: source
Version: 1.10.0-2
Distribution: experimental
Urgency: medium
Maintainer: Krzysztof Burghardt
Changed-By: Jochen Sprickerhof
Changes:
poco (1.10.0-2) experimental;
On 2/5/20 10:33 PM, Dmitry Smirnov wrote:
> Upstream binaries are not DFSG compliant.
Why?
> Not only they use shitload of
> vendored libraries
That is how go works. The exact version is available, the source code also.
The way how the docker image is being built is actually in the sources,
On 2/5/20 2:52 PM, Nikolaus Rath wrote:
I think it's worth pointing out that this was an experimental feature
that users explicitly had to opt into. The original statement feels
misleading to me.
That's how it started, further looking (sorry, was replying from my
phone before) give things
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 16:37:00 -0500
Source: libime
Architecture: source
Version: 0.0~git20191230.5b6e890+ds2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team
Changed-By: Boyuan Yang
Changes:
libime
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 22:46:23 +0100
Source: gst-plugins-bad1.0
Binary: gstreamer1.0-plugins-bad-doc gstreamer1.0-plugins-bad
gstreamer1.0-opencv gstreamer1.0-plugins-bad-dbg libgstreamer-plugins-bad1.0-0
libgstreamer-opencv1.0-0
On Thursday, 6 February 2020 6:59:38 AM AEDT Nikolaus Rath wrote:
> I would venture that for every user who is grateful that
> /var/log/mail.log collects all the various mail-related logs, there is
> another user that curses about non being able to separate (out of the
> box) the logs from all the
Le mercredi, 5 février 2020, 21.44:43 h CET Dmitry Smirnov a écrit :
> On Wednesday, 5 February 2020 11:01:08 AM AEDT Scott Kitterman wrote:
> > We just had a GR where the project voted it was just fine to systemd all
> > the things, so this sort of thing is to be expected.
>
> Are you suggesting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 22:15:51 +0100
Source: ruby-friendly-id
Architecture: source
Version: 5.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Cédric Boutillier
Changes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 21:51:48 +0100
Source: nvidia-settings-tesla-418
Architecture: source
Version: 418.113-2
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers
Changed-By: Andreas Beckmann
Changes:
On Thursday, 6 February 2020 8:10:17 AM AEDT Bernd Zeimetz wrote:
> You are free not to use salsa or not to use the gitlab runners.
> You are also free to rewrite the gitlab runner in a free version, if I
> remember right the api is published, so this should not be hard.
What warrants such a
On Wed, Feb 5, 2020 at 3:03 PM Dmitry Smirnov wrote:
>
> Anyway the big disadvantage of changing default is that now random Debian
> systems will have no traditional logging interface (rsyslog) and we're all
> will be forced to adapt to the new interface in the absence of old one on
> some
On Thu, Feb 06, 2020 at 07:44:43AM +1100, Dmitry Smirnov wrote:
> > We just had a GR where the project voted it was just fine to systemd all
> > the things, so this sort of thing is to be expected.
>
> Are you suggesting that voters fully understood the implications?
> Is this OK now to replace
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 15:49:37 -0500
Source: pycangjie
Architecture: source
Version: 1.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team
Changed-By: Boyuan Yang
Closes: 949971
Changes:
pycangjie (1.3-2)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 21:52:25 +0100
Source: lv2file
Architecture: source
Version: 0.84-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Dennis Braun
Closes: 776244 852439
Changes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 18:41:16 +0200
Source: libcrcutil
Architecture: source
Version: 1.0-5.1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov
Changed-By: Adrian Bunk
Closes: 945546
Changes:
libcrcutil (1.0-5.1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 21:56:52 +0100
Source: deap
Architecture: source
Version: 1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Miriam Ruiz
Changed-By: Christian Kastner
Changes:
deap (1.3.1-1) unstable; urgency=medium
.
On 2/5/20 9:25 PM, Dmitry Smirnov wrote:
> On Tuesday, 26 February 2019 1:19:35 AM AEDT Inaki Malerba wrote:
>> [0] https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md
>
> Thank you for providing this useful service.
>
> My big concern though is that primary gitlab-runner
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 14:19:46 -0500
Source: fcitx5
Architecture: source
Version: 0.0~git20200128.9e3bc8d+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team
Changed-By: Boyuan Yang
Changes:
fcitx5
On Wednesday, 5 February 2020 11:01:08 AM AEDT Scott Kitterman wrote:
> We just had a GR where the project voted it was just fine to systemd all
> the things, so this sort of thing is to be expected.
Are you suggesting that voters fully understood the implications?
Is this OK now to replace
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 01 Feb 2020 15:35:39 +0100
Source: pyfai
Architecture: source
Version: 0.19.0+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Picca Frédéric-Emmanuel
Changes:
pyfai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 20:55:06 +0100
Source: pocl
Architecture: source
Version: 1.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers
Changed-By: Andreas Beckmann
Changes:
pocl (1.4-6) unstable;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 20:51:36 +0100
Source: nvidia-settings
Architecture: source
Version: 440.59-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers
Changed-By: Andreas Beckmann
Changes:
nvidia-settings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 20:58:18 +0100
Source: mda-lv2
Architecture: source
Version: 1.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Dennis Braun
Closes: 936998
Changes:
mda-lv2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 21:01:12 +0100
Source: jaaa
Architecture: source
Version: 0.9.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Dennis Braun
Changes:
jaaa (0.9.2-1) unstable;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 20:46:45 +0100
Source: japa
Architecture: source
Version: 0.9.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Dennis Braun
Changes:
japa (0.9.2-1) unstable;
On Feb 05 2020, Scott Kitterman wrote:
> On February 5, 2020 12:35:45 PM UTC, Ansgar wrote:
>>On Wed, 2020-02-05 at 07:44 +, Scott Kitterman wrote:
>>> Do syslog facilities really have to be addressed by number rather
>>than name? That seems like a horrible interface.
>>
>>Currently yes.
On Tuesday, 26 February 2019 1:19:35 AM AEDT Inaki Malerba wrote:
> [0] https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md
Thank you for providing this useful service.
My big concern though is that primary gitlab-runner 12.7.0 (HEAD)
on salsa-runner.debian.net f0fdd533 is not
On Feb 05 2020, Anthony DeRobertis wrote:
> On February 5, 2020 9:49:36 AM UTC, Nikolaus Rath wrote:
>>On Feb 04 2020, Anthony DeRobertis wrote:
>>> Google has at some point had results from
>>> Gmail in the web search results (no idea if they currently do).
>>
>>Would you have a reference for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 20:07:57 +0100
Source: intel-media-driver
Architecture: source
Version: 19.4.0r+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Changes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 20:37:48 +0100
Source: fomp
Architecture: source
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Dennis Braun
Closes: 943062
Changes:
fomp (1.2.0-1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 13:27:01 -0500
Source: ruby-gettext
Architecture: source
Version: 3.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Utkarsh Gupta
Changes:
ruby-gettext
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 12:22:22 -0600
Source: date
Architecture: source
Version: 1.2.39-1
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel
Changed-By: Dirk Eddelbuettel
Changes:
date (1.2.39-1) unstable;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 19:07:26 +0100
Source: libsereal-perl
Architecture: source
Version: 4.011-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Changed-By: gregor herrmann
Changes:
libsereal-perl (4.011-1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 17:47:13 +
Source: ruby-gettext-setup
Architecture: source
Version: 0.34-2
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers
Changed-By: Georg Faerber
Changes:
ruby-gettext-setup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 18:57:28 +0100
Source: stk
Architecture: source
Version: 4.6.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Changes:
stk (4.6.1+dfsg-3)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 14:40:04 -0300
Source: packit
Architecture: source
Version: 1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Joao Eriberto Mota Filho
Changed-By: Joao Eriberto Mota Filho
Closes: 287666
Changes:
packit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 12:20:57 -0500
Source: ruby-rbtrace
Architecture: source
Version: 0.4.11-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Utkarsh Gupta
Changes:
ruby-rbtrace
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 18:58:46 +0200
Source: libclc
Architecture: source
Version: 0.2.0+git20190827-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL team
Changed-By: Timo Aaltonen
Closes: 950032
Changes:
libclc
On February 5, 2020 9:49:36 AM UTC, Nikolaus Rath wrote:
>On Feb 04 2020, Anthony DeRobertis wrote:
>> Google has at some point had results from
>> Gmail in the web search results (no idea if they currently do).
>
>Would you have a reference for this please?
Here is a news report from when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 18:20:58 +0100
Source: puma
Architecture: source
Version: 3.12.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Daniel Leidert
Changes:
puma (3.12.0-3) unstable;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 19:27:55 +0200
Source: libxcb
Architecture: source
Version: 1.13.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force
Changed-By: Timo Aaltonen
Closes: 947499
Changes:
libxcb (1.13.1-4)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 17:41:38 +0100
Source: sbuild
Architecture: source
Version: 0.79.0-1
Distribution: unstable
Urgency: medium
Maintainer: sbuild maintainers
Changed-By: Ivo De Decker
Closes: 774856 920335 921675 922148 928366
On Wed, 2020-02-05 at 15:35:28 +0100, Ansgar wrote:
> On Wed, 2020-02-05 at 08:33 -0500, Sam Hartman wrote:
> > Steve, you're presuming that we would not create a new soname for
> > libc6 on architectures where we want a new time ABI.
>
> Isn't the libc ABI for some reason part of Debian's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2020 11:45:40 -0500
Source: ruby-mobile-fu
Architecture: source
Version: 1.4.0+github-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Utkarsh Gupta
Changes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 17:38:53 +0100
Source: mapnik-reference
Architecture: source
Version: 8.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Changes:
1 - 100 of 190 matches
Mail list logo
