On Tue, Jun 4, 2019 at 4:12 AM Yves-Alexis Perez wrote:
> My gut feeling is that light-locker just uses codepaths not really used
> otherwise, like vt-switch at the same time as suspend/resume or screen off/on.
> Unfortunately debugging i915 is completely out of my league (and I already
> tried mu
control: severity -1 grave
Dear kernel maintainers,
Buster will be released with 4.19.37 kernel. That's fine
and it doesn't break ZFS. However, the changes introduced
in 4.19.38 and linux 5.0 break ZFS. That means the current
0.7.12-2 will fail to build everywhere after the first
Buster point rel
On Jun 03, Daniel Lange wrote:
> It is a data point to prove your "we do not have forged email issues" wrong.
By "forged email issues" I mean phishing attacks, not garden variety
malware which can be blocked in other ways.
--
ciao,
Marco
signature.asc
Description: PGP signature
Email Template
Dear ,
OVERVIEW
Weizmann Forex is a part of the INR 45 billion Weizmann Group, with business
interests in textile manufacturing and exports, hydro and wind-power
generation, as well as foreign exchange transactions and inward money transfer.
Who we
Am 03.06.19 um 22:32 schrieb Marco d'Itri:
On Jun 03, Daniel Lange wrote:
> > -all would stop some forged emails, but we do not have forged email
> > issues.
> We do. 4% of this year's spam in my spam traps have originated as fake
> @debian.org. Unfortunately we even nicely relay them as we ca
On Jun 03, Daniel Lange wrote:
> > -all would stop some forged emails, but we do not have forged email
> > issues.
> We do. 4% of this year's spam in my spam traps have originated as fake
> @debian.org. Unfortunately we even nicely relay them as we can't tell
This is not a meaningful figure unles
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-06-03 at 12:59 -0700, Russ Allbery wrote:
> Ah, good call. I was also seeing other problems with the Intel driver in
> combination with light-locker where the monitor resolution would be set to
> some incorrect value after restore from
Yves-Alexis Perez writes:
> Actually it seems to me that the bug is a bad interaction with light-
> locker/lightdm locking system (which relies on vt switch) and the Intel
> driver. It only seems to happens on this driver, and I think it's also
> been reproduced just by doing vt-switches (but can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-06-03 at 21:55 +0200, Yves-Alexis Perez wrote:
> I noted Andreas raised the severity, but I hope someone has an idea how to fix
> that because I don't.
Also, since it was posted on -devel, I guess there's a bit of exposure: if
some peop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-05-31 at 18:32 -0700, Russ Allbery wrote:
> This appears to be a bug in light-locker specifically, which is the
> default screen lock program with XFCE with lightdm. See, for instance:
>
> https://github.com/the-cavalry/light-locker/is
Hi.
Thanks for bringing up this issue originally.
I think it has started some good discussion with the Debian zfs
maintainers.
However, I think this particular subthread about zfs has served its
purpose.
I cannot find anything in your message that is on topic for the
debian-devel mailing list.
Am 03.06.19 um 18:09 schrieb Marco d'Itri:
-all would stop some forged emails, but we do not have forged email
issues.
We do. 4% of this year's spam in my spam traps have originated as fake
@debian.org. Unfortunately we even nicely relay them as we can't tell
legitimate and fake Debian email a
Hi Mo and Theodore,
On Sun, Jun 2, 2019 at 4:04 AM Theodore Ts'o wrote:
> Also, it's not accurate that "linux developers didn't accept". Ryan
> sent a query to Linus, and Linus didn't respond. I don't know if he
> sent a single message, or whether he retried a couple of times. A
> failure to
On 2019-06-03 11:37:39 [-0400], Sam Hartman wrote:
> I'd much rather pay money and allow members who do want to use their own
> infrastructure to do so rather than set up an SPF record and force
> everyone to go through the debian mxes.
With my kernel.org address I get mail forwarding and a SMTP s
> "Daniele" == Daniele Nicolodi writes:
Daniele> On 03/06/2019 09:37, Sam Hartman wrote:
>> I'd much rather pay money and allow members who do want to use their own
>> infrastructure to do so rather than set up an SPF record and force
>> everyone to go through the debian mxes.
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller
* Package name: pizzly
* URL : http://github.com/pmeisted/pizzly
* License : BSD
Programming Lang: C++
Description : gene-fusion detection with kallisto
Team-maintained on https://salsa.debian.org/med-team/pi
On 03/06/2019 09:37, Sam Hartman wrote:
> I'd much rather pay money and allow members who do want to use their own
> infrastructure to do so rather than set up an SPF record and force
> everyone to go through the debian mxes.
Pay money for which service exactly? I am not aware of any widely
deploy
Marco d'Itri writes:
> On Jun 03, Russ Allbery wrote:
>> A possibly useful compromise is to do what Marco suggested: publish SPF
>> records for domains like lists.debian.org, where all the mail is coming
>> from Debian infrastructure. That can easily be -all. And then at
>> least we have the o
On Jun 03, Russ Allbery wrote:
> A possibly useful compromise is to do what Marco suggested: publish SPF
> records for domains like lists.debian.org, where all the mail is coming
> from Debian infrastructure. That can easily be -all. And then at least
> we have the option of moving some of the
Hi,
On 2019-06-03 14:47, Mo Zhou wrote:
> It seems that persuading the kernel team to patch the kernel
> specifically for ZFS is impossible -- that's an dead end.
I made a mistake at this point. There is no SIMD bug in zfs
0.7.12-2. The true bug lies in the stable kernel update that
breaks stuff.
On Mon, Jun 03, 2019 at 10:40:26AM +0200, Daniel Lange wrote:
We (debian/DSA) do not provide email hosting. We provide email
forwarding.
DSA should re-evaluate that.
I'm not sure I would want the existing DSA resource, spread as thin as it is,
allocated to running a mail hosting service. At l
On Jun 03, Sam Hartman wrote:
> But more than that, you don't need the SPF record.
(Here comes a short lesson on email authentication...)
The most useful way to think about SPF and DKIM is that they allow to
move reputation considerations for a message from the sender IP address
to the sender d
In this thread I'm speaking as an individual.
Other than approving DSA expendatures related to email, the DPL does not
set Debian's email policy.
> "Ian" == Ian Jackson writes:
Ian> Sam Hartman writes ("Re: @debian.org mail"):
>> But more than that, you don't need the SPF record.
Sam Hartman writes:
>> "Daniel" == Daniel Lange writes:
> Daniel> To do better, we should really offer SMTP submission/IMAP
> Daniel> services for @debian.org as soon as possible and - after a
> Daniel> grace period - publish a mx -all SPF record.
> Actually publishing the SPF r
Le 03/06/2019 à 17:21, Sam Hartman a écrit :
>> "Daniel" == Daniel Lange writes:
>
> Daniel> Hence I'd like us to offer email services to project members.
> That's
> Daniel> an offer. Not a requirement. If DDs use the Debian infra or
> continue
> Daniel> using their current setu
Sam Hartman writes ("Re: @debian.org mail"):
> But more than that, you don't need the SPF record. Debian could pay
> to get on one of the white lists, we could use some services like
> Amazon SES, we could possibly get a good enough dkim reputation that
> we don't need to do any of the above.
Deb
Jonathan Dowland writes:
> On Sat, Jun 01, 2019 at 09:20:48PM +0200, gregor herrmann wrote:
>> I can't reproduce this in a quick test:
>>
>> Terminal 1: sleep 5 ; notify-send foo
>> Terminal 2: xscreensaver-command -lock
>>
>> No "foo" notification pops up over the screensaver image.
>>
>> (This
> "Daniel" == Daniel Lange writes:
Daniel> Hence I'd like us to offer email services to project members. That's
Daniel> an offer. Not a requirement. If DDs use the Debian infra or continue
Daniel> using their current setup, all fine for me.
We're agreed so far.
Daniel> Yes,
> "Paul" == Paul Wise writes:
Paul> On Fri, May 31, 2019 at 5:32 AM Holger Levsen wrote:
>> LTS is accepted by the Debian community.
Paul> I'm not entirely sure this fully represents the range of feelings
Paul> about the LTS efforts.
Paul> There are a few things that are
On Mon, Jun 03, 2019 at 02:37:48PM +0200, Marco d'Itri wrote:
> On Jun 03, Bastian Blank wrote:
>
> > Does anyone know what RHEL8 (which should have this problem as well)
> > does to "fix" this problem?
> RHEL8 enables by default rngd from rng-tools, which looks much better to
> me than haveged.
Hi Dan and Jonathan,
On 2019-05-28 18:49, Jonathan Carter wrote:
> On 2019/05/28 18:43, Dan wrote:
>> ZFS 0.8 has been released with lots of improvements, notably encryption.
> Yep, it's an exciting feature.
I've already uploaded ZFS 0.8 to experimental. But beware, the original
0.8.0 release has
Hi Sam,
Am 03.06.19 um 13:29 schrieb Sam Hartman:
1) You're asking all DDs to use this infrastructure you set up.
Currently everybody routes inbound mail via two Debian servers (as they
are the only MXs for debian.org).
Everybody who needs to make sure they can reach @gmail.com / GApps user
On Mon, 2019-06-03 at 12:44 +, Holger Levsen wrote:
> On Mon, Jun 03, 2019 at 01:09:29PM +0100, Steve McIntyre wrote:
> > d-i is using haveged now, and that's working well AFAICS.
>
> are you sure? #923675 is still open...
I'm curious, what about #923675 concerns you?
-Jim P.
On Jun 03, Bastian Blank wrote:
> Does anyone know what RHEL8 (which should have this problem as well)
> does to "fix" this problem?
RHEL8 enables by default rngd from rng-tools, which looks much better to
me than haveged.
--
ciao,
Marco
signature.asc
Description: PGP signature
Control: severity -1 grave
Hi,
I've set the severity of this bug to grave. It has turned out that in
combination with xfce light-locker leaves the user with a black screen
leading normal users to the assumption that the computer is frozen. I
have observed users pressing power button of their la
On Mon, Jun 03, 2019 at 01:09:29PM +0100, Steve McIntyre wrote:
> d-i is using haveged now, and that's working well AFAICS.
are you sure? #923675 is still open...
--
tschau,
Holger
---
holger@(de
On Mon, Jun 03, 2019 at 12:36:25PM +0200, Bastian Blank wrote:
>Hi folks
>
>We have the famous random stall problem in our cloud images as well.
>cloud-init and our other provisioning tools will generate ssh keys and
>need randomness for that, so block for several minutes on initial boot.[1]
>
>For
> "Daniel" == Daniel Lange writes:
Daniel> To do better, we should really offer SMTP submission/IMAP services
for
Daniel> @debian.org as soon as possible and - after a grace period -
publish a
Daniel> mx -all SPF record.
Actually publishing the SPF record seems fairly problemat
On Jun 03, Daniel Lange wrote:
> The default reply for missing wafer confirmation emails (the software
> running debconf19.debconf.org) and missing salsa password reset emails is
> "check your Spam folder". Debian.org doesn't have a SPF record so mail
> submitted from such Debian machines is a bi
Hi folks
We have the famous random stall problem in our cloud images as well.
cloud-init and our other provisioning tools will generate ssh keys and
need randomness for that, so block for several minutes on initial boot.[1]
For now we have two recipes against this:
- amd64 trusts RDRAND, but the
Hi,
On Mon, 03 Jun 2019, Paul Wise wrote:
> There are a few things that are possibly concerning:
Thanks for sharing those. Let me answer them.
> Freexian is essentially the only available-to-hire provider of
> services for Debian LTS, as the Freeside link doesn't lead anywhere
> useful. This mea
On 2019/06/03 10:40, Daniel Lange wrote:
> Mail submitted from DD's private IPs frequently gets flagged as spam
> regardless of content by all three big players and - if submitted via
> IPv6 - refused directly by Google. Microsoft and Yahoo still run their
> MXs IPv4 only. But we can expect a simil
We (debian/DSA) do not provide email hosting. We provide email
forwarding.
DSA should re-evaluate that.
We run into more and more problems sending from @debian.org email
addresses as the three big players in email ratchet up their anti-spam
measures.
They are hosting a huge share of our use
On Sat, Jun 01, 2019 at 09:20:48PM +0200, gregor herrmann wrote:
I can't reproduce this in a quick test:
Terminal 1: sleep 5 ; notify-send foo
Terminal 2: xscreensaver-command -lock
No "foo" notification pops up over the screensaver image.
(This is with awesome, maybe the story is different fo
44 matches
Mail list logo
