On Wed, May 22, 2019 at 06:44:40AM -0400, Steeve McCauley wrote:
--iso seems to be an undocumented equivalent to the --iso-8601 date format,
that gives you -MM-DD as the default format.
You seem to have fallen on a bug in that either,
1) date string is corrupt and doesn't emit an error
2)
On Tue, May 14, 2019 at 12:11:17PM -0700, David Christensen wrote:
On 5/14/19 4:23 AM, Michael Stone wrote:
On Thu, May 09, 2019 at 10:48:31PM -0700, David Christensen wrote:
2019-05-09 22:00:27 root@po /mnt/scratch
# time dd if=/dev/urandom of=foo bs=1M count=1K conv=fsync
don't bother
On Mon, May 13, 2019 at 10:58:45AM +0200, Lothar Schilling wrote:
Am 13.05.2019 um 10:51 schrieb Tixy:
On Mon, 2019-05-13 at 10:30 +0200, Lothar Schilling wrote:
[...]
# uname -a
Linux [my.server.com] 4.9.0-9-686-pae #1 SMP Debian 4.9.168-1
(2019-04-12) i686 GNU/Linux
So you're running a
On Thu, May 09, 2019 at 10:48:31PM -0700, David Christensen wrote:
2019-05-09 22:00:27 root@po /mnt/scratch
# time dd if=/dev/urandom of=foo bs=1M count=1K conv=fsync
don't bother doing this, urandom will be the bottleneck and it will just
confuse things
On Fri, May 10, 2019 at 05:42:45PM +0200, Marc Haber wrote:
On Fri, 10 May 2019 07:42:52 -0400, Michael Stone
wrote:
This is really not a property worth preserving.
I disagree. I frequently unpack .debs on .rpm Systems, especially when
I want to see how the rather nice behavior that I find
On Fri, May 10, 2019 at 05:18:18AM +0200, Guillem Jover wrote:
be updated anyway to support any new format. It also destroys some of the
nice properties of the 2.x format, namely:
- Not requiring special tools to build/extract.
This is really not a property worth preserving. I think it would
On Fri, May 10, 2019 at 05:18:18AM +0200, Guillem Jover wrote:
be updated anyway to support any new format. It also destroys some of the
nice properties of the 2.x format, namely:
- Not requiring special tools to build/extract.
This is really not a property worth preserving. I think it would
On Thu, May 09, 2019 at 07:37:55AM +0800, Paul Wise wrote:
On Thu, May 9, 2019 at 1:38 AM Adam Borowski wrote:
Thus, even though we'd want to stick with xz for the official archive, speed
gains from zstd are so massive that it's tempting to add support for it,
at least for non-official uses,
On Wed, May 08, 2019 at 08:34:36PM +0100, André Rodier wrote:
On Wed, 2019-05-08 at 21:57 +0300, Mindaugas Celiesius wrote:
Did you check this?
https://packages.debian.org/stretch/geoip-bin
> Hi,
>
> Is there any way - or Debian package - to know the timezone from an IP
> address, or at least
On Wed, May 08, 2019 at 07:43:58PM +0100, André Rodier wrote:
Is there any way - or Debian package - to know the timezone from an IP
address, or at least from a country? I have successfully used the geoip
databases to get the country, so I could use the main city as an
approximation.
I would
On Sat, May 04, 2019 at 08:46:26AM +0100, Jonathan Dowland wrote:
On Fri, May 03, 2019 at 02:22:21PM -0700, Jimmy Johnson wrote:
Debian knows what I'm talking about.
This Debian developer hasn't the foggiest.
Don't encourage it.
On Tue, Apr 30, 2019 at 02:12:51PM +0200, Pascal Hambourg wrote:
Le 30/04/2019 à 07:35, Ben Finney a écrit :
You can see them sorted by size with:
$ du --max-depth=1 /var | sort --numeric-sort
The ‘-h’ (‘--human-readable’) is useful as its name implies; but it has
the disadvantage of
On Mon, Apr 22, 2019 at 12:12:26PM -0700, you wrote:
On Mon, Apr 22, 2019 at 02:59:22PM -0400, Michael Stone wrote:
On Mon, Apr 22, 2019 at 11:41:27AM -0700, Steve Langasek wrote:
> In Ubuntu, we have applied the attached patch to include autopkgtests in the
> coreutils package. As
On Mon, Apr 22, 2019 at 11:41:27AM -0700, Steve Langasek wrote:
In Ubuntu, we have applied the attached patch to include autopkgtests in the
coreutils package. As a core package, it is useful to have autopkgtests in
order to detect regressions (however unlikely) introduced by the
dependencies
On Thu, Apr 18, 2019 at 10:41:18AM -0400, Celejar wrote:
Alternatively, for internal-only stuff, you can use ULAs. IPv6
The context of our discussion is seamless and collision-free host access
across a VPN, not "internal-only stuff" - unless your directions below
are going to work even when
On Thu, Apr 18, 2019 at 10:00:28AM -0400, Celejar wrote:
Can you point me to such documenation? You've said that it's a trivial,
straightforward change: what, exactly, do I do to start using IPv6?
Find an IPv6 provider. There's not much debian can document about that.
Alternatively, for
On Thu, Apr 18, 2019 at 08:12:04AM -0500, Nicholas Geovanis wrote:
But isn't it irrelevant whether they pick the same prefix or not? Routers that
respect ULA and RFC1918 shouldn't route any traffic destined to them off the
logical subnet. Right?
If it didn't matter, people wouldn't keep
On Wed, Apr 17, 2019 at 08:06:05PM -, Curt wrote:
On 2019-04-17, Pascal Hambourg wrote:
Le 17/04/2019 à 18:42, Michael Stone a écrit :
On Wed, Apr 17, 2019 at 12:38:11PM -0400, Celejar wrote:
On Wed, 17 Apr 2019 12:10:56 -0400 Michael Stone
wrote:
On Wed, Apr 17, 2019 at 11:57:43AM
On Wed, Apr 17, 2019 at 09:37:36PM +0200, Pascal Hambourg wrote:
Le 17/04/2019 à 18:42, Michael Stone a écrit :
On Wed, Apr 17, 2019 at 12:38:11PM -0400, Celejar wrote:
On Wed, 17 Apr 2019 12:10:56 -0400 Michael Stone
wrote:
On Wed, Apr 17, 2019 at 11:57:43AM -0400, Celejar wrote:
I
On Wed, Apr 17, 2019 at 08:45:50PM -0400, Celejar wrote:
You make it sound like it's a trivial, straightforward change. Is it?
Pretty much.
Will all my applications work correctly over IPv6 without much work?
Unless you've written something yourself (badly) IPv6 has "just worked"
in
On Wed, Apr 17, 2019 at 06:11:43PM -0400, Celejar wrote:
In other words, with IPv4, there's no *practical* solution, since a
typical end user isn't going to get arbitrary numbers of IP addresses.
So use IPv6.
On Wed, Apr 17, 2019 at 12:38:11PM -0400, Celejar wrote:
On Wed, 17 Apr 2019 12:10:56 -0400 Michael Stone wrote:
On Wed, Apr 17, 2019 at 11:57:43AM -0400, Celejar wrote:
>Thanks. When I first set up the VPN, I did some reading about this, and
>I was rather shocked
On Wed, Apr 17, 2019 at 11:57:43AM -0400, Celejar wrote:
Thanks. When I first set up the VPN, I did some reading about this, and
I was rather shocked to see that there was no definitive solution to
avoid address collisions
Sure there is--globally unique IPs.
On Tue, Apr 16, 2019 at 03:00:04PM -0400, Gene Heskett wrote:
if you are damned carefull, I had it destroy 3 installs already, so badly
I had to do a full reinstall.
You have to really try, since it tells you what it's going to do before
it does anything. But you have a history of odd
On Tue, Apr 16, 2019 at 06:27:34PM +0100, Paul Sutton wrote:
There are 3 main ways to install packages, I have tried to explain this
in the presentation as
Apt - 1.8.0 - command line tool (universal)
Gnome-packagekit - used for gnome desktop environment
Synaptic - 0.84.5 used for most other
On Fri, Apr 12, 2019 at 01:13:49PM -0400, rhkra...@gmail.com wrote:
It looks like I am writing something like 20 GB per day
That's basically nothing for a reasonably sized modern SSD.
On Wed, Apr 10, 2019 at 10:18:23AM -0400, rhkra...@gmail.com wrote:
Maybe, but I've bought things that I think are (5-port) switches (advertised
as such) for in the range of $10 in various sales or on ebay, and so far, have
no reason to doubt them.
I guess I'll have to really test in the near
On Wed, Apr 10, 2019 at 03:01:51PM +0200, Peter Wiersig wrote:
I strive for local networks that would have single digit drops in 47m
packets and I'm willing to spend the money for the equipment to achieve
that. My quoted ifconfig output comes from a rented server in some
datacenter where I
is insignificant, and you're having him waste his time
chasing something that isn't a problem.
Michael Stone
On Tue, Apr 09, 2019 at 03:11:27PM -0400, Gene Heskett wrote:
The point I was trying to make Mike, is, if thats to be a std, its an
extremely obtuse way of writing that std. Consequently I suspect it will
be 100% ignored. And folks will continue to muddle along just fine. :)
It reads fine to
On Tue, Apr 09, 2019 at 02:03:08PM -0400, Gene Heskett wrote:
On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote:
On 2019-04-08 18:26:23 +0300, Reco wrote:
> stretch$ TZ=UTC date
> Mon Apr 8 15:22:02 UTC 2019
> buster$ TZ=UTC date
> Mon 08 Apr 2019 03:22:04 PM UTC
This is unrelated to
On Fri, Mar 22, 2019 at 04:14:50PM -0600, ghe wrote:
But when I'm looking to connect a cable, the location of the port on the
outside of the box is much more useful to me than the address number on
the bus.
Unfortunately, the software doesn't know what was written on the outside
of the box.
On Fri, Mar 22, 2019 at 04:23:32PM -0400, deb wrote:
On 3/22/19 4:07 PM, Michael Stone wrote:
On Fri, Mar 22, 2019 at 03:00:23PM -0500, David Wright wrote:
If you're really worried, first remount the partitions readonly, which
will fail if they're in use. Then unmount them and disconnect
On Fri, Mar 22, 2019 at 03:00:23PM -0500, David Wright wrote:
If you're really worried, first remount the partitions readonly, which
will fail if they're in use. Then unmount them and disconnect.
Just unmount--that will fail if the partition is in use unless extra
options are added.
Mike
On Fri, Mar 22, 2019 at 11:23:29AM -0400, deb wrote:
a. Has anyone used iotop? thoughts?
(I did -- it's CLI-based. I was underwhelmed. Hard-ish to use; can't easily
pinpoint processes accessing the drives)
Well, it's hard to say what would work better if you can't explain what
the problem
On Thu, Mar 21, 2019 at 11:13:11AM +0100, Erik Auerswald wrote:
More general, table headers are useful for interactive use, but often need
to be ignored when the tool output is used programmatically.
For a utility like df, which is in concept a tool for interactive use
and has a wide range of
On Mon, Mar 18, 2019 at 09:30:13AM -0400, rhkra...@gmail.com wrote:
Is anyone (reading this list) using USB Flash / Pendrives or [micro]SD cards
for backup?
I've thought about doing that, especially as they continue to come down in
price, but my experience with them at least in some cases has
On Mon, Mar 18, 2019 at 12:56:20PM -, Dan Purgert wrote:
I'm bad with the FHS, but shouldn't say your shark-attack movies be
somewhere in /usr(/local) ? maybe /srv if you're running a media
server?
Or is there some caveat that allows for mounting new partitions into
the root directory,
On Sat, Mar 09, 2019 at 12:02:05AM +0200, Adrian Bunk wrote:
On Fri, Mar 08, 2019 at 02:38:07PM -0500, Michael Stone wrote:
On Fri, Mar 08, 2019 at 08:01:35PM +0100, Christian Kastner wrote:
> I intended to post a transition proposal here soon, but it's not ready
> yet... but long story
On Fri, Mar 08, 2019 at 08:01:35PM +0100, Christian Kastner wrote:
I intended to post a transition proposal here soon, but it's not ready
yet... but long story short: I believe we would be far better off moving
to cronie than maintaining our old fork.
One question worth asking is which
On Thu, Mar 07, 2019 at 01:49:42PM -0700, Cousin Stanley wrote:
David Wright wrote:
All that stuff in /dev/disk/ is just an ephemeral
bunch of convenient symbolic links, presumably conjured
up by udev or somesuch, if not the linux kernel
But are they not accurate after boot
for particular
On Thu, Mar 07, 2019 at 09:02:23PM +0100, Holger Wansing wrote:
I'm actually wondering if this is a good idea..
There are lot of other packages installing cronjobs and people, I would
assume, expect that they will run.
I would personally revert his patch as long as all the cronjobs have not
a
On Thu, Mar 07, 2019 at 09:59:43AM -0700, Cousin Stanley wrote:
Michael Stone wrote:
On Thu, Mar 07, 2019 at 07:11:36AM -0700, Cousin Stanley wrote:
Stephen P. Molnar wrote:
and my fstab is:
# /etc/fstab: static file system information.
I've found that labeling my disk
On Thu, Mar 07, 2019 at 07:11:36AM -0700, Cousin Stanley wrote:
Stephen P. Molnar wrote:
and my fstab is:
# /etc/fstab: static file system information.
I've found that labeling my disk partitions
and using /dev/disk/by-label/xyzzy lines
in the /etc/fstab file seems to be
64)
>
>Kernel: Linux 4.14.104+ (SMP w/4 CPU cores)
>Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C
>(charmap=UTF-8)
>Shell: /bin/sh linked to /bin/dash
>Init: systemd (via /run/systemd/system)
>
>-- no debconf information
What happens if you rebuild -1?
--
Michael Stone
(From phone, please excuse typos)
On Fri, Mar 01, 2019 at 02:12:06PM -0300, Bruno Schneider wrote:
My system started using swap space even when there is available RAM:
$ free -m
totalusedfree shared buff/cache available
Mem: 388210042303 63 573
On Fri, Mar 01, 2019 at 07:30:15AM +, Dekks Herton wrote:
David Wright writes:
I always add an explicit rw or ro under options, along with defaults.
With systemd, I add nofail to any filesystems that aren't vital for
the system to run, which means the system will still boot fully
without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 28 Feb 2019 10:30:31 -0500
Source: coreutils
Binary: coreutils coreutils-dbgsym
Architecture: source amd64
Version: 8.30-3
Distribution: unstable
Urgency: medium
Maintainer: Michael Stone
Changed-By: Michael Stone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 26 Feb 2019 07:15:19 -0500
Source: coreutils
Binary: coreutils coreutils-dbgsym
Architecture: source amd64
Version: 8.30-2
Distribution: unstable
Urgency: medium
Maintainer: Michael Stone
Changed-By: Michael Stone
On Mon, Feb 25, 2019 at 03:53:09PM +, Ben Hutchings wrote:
The major input into the new seed file contents is the old seed file
contents.
Yes, I'd just drop the seed file once used, then have a scheduled job
write a new one at some point in the future if the random quality is
high enough.
On Sat, Feb 23, 2019 at 05:37:06PM -0500, Felix Miata wrote:
Depends on context. In a fully automated context, UUIDs do indeed work great,
when humans are
working with them, not so great. Most humans cannot remember 32 character or
longer strings of
randomly generated characters for
On Sat, Feb 23, 2019 at 06:51:12PM +0100, Pascal Hambourg wrote:
Le 23/02/2019 à 17:10, Michael Stone a écrit :
On Sat, Feb 23, 2019 at 06:57:05AM -0500, songbird wrote:
i've hated UUIDs since they arrived so i've
always used LABELS instead. for people with a simple
layout it makes so much
On Sat, Feb 23, 2019 at 09:41:27AM -0500, rhkra...@gmail.com wrote:
On Saturday, February 23, 2019 07:53:23 AM Pascal Hambourg wrote:
Le 23/02/2019 à 08:53, David Christensen a écrit :
> Understand that if you disconnect the power cable to a motherboard,
> drive, peripheral, etc., but not all
On Sat, Feb 23, 2019 at 06:57:05AM -0500, songbird wrote:
David Christensen wrote:
...
On 2/22/19 6:19 AM, Stephen P. Molnar wrote:
> The OS is on dev/sda. The disk I changing is /dev/sdc
As other readers have noted, device nodes for drives are unpredictable.
i've hated UUIDs since they
On Fri, Feb 22, 2019 at 11:36:28AM -0500, Stephen P. Molnar wrote:
Before disconnection the power to the drives, I edited out their lines
in fstab. I disconnecting the power to sdb and sdc and started the
computer. It booted for a few lines until it encountered the line
starting with 'start
On Fri, Feb 22, 2019 at 07:20:52AM +1100, Sam Varghese wrote:
I would value feedback from anyone on this list who has been running
Debian on an AMD Ryzen system. I have gone back through list posts for a
year and cannot find anything on this subject.
I am running the testing stream and am
On Wed, Feb 13, 2019 at 01:14:36PM -0800, David Christensen wrote:
AFAIK over-provisioning has no effect on longevity -- longevity is
proportional to total number of cells times rated erase/ write cycles
per cell divided by write throughput.
In the absence of trim, restricting the logical
On Wed, Feb 13, 2019 at 08:41:33AM -0500, deb wrote:
#1 Given that it's not great to pound the same area of a SSD with
writes; is it indeed still best practice to go with a swap partition
on a SSD rather than a swap FILE?
That's not a thing: the SSD will balance writes physically across the
On Thu, Feb 07, 2019 at 10:21:49PM +0100, Ansgar wrote:
(And you get 24-hour time, but very strange Endian in C.UTF-8:
WEEKDAY MMM DD HH:MM:SS TZ
while en_US.UTF-8 has at least DD MMM ... Having
-MM-DD HH:MM:SS[+]
instead would be much nicer if we were to create an arbitrary
On Thu, Feb 07, 2019 at 10:21:49PM +0100, Ansgar wrote:
(And you get 24-hour time, but very strange Endian in C.UTF-8:
WEEKDAY MMM DD HH:MM:SS TZ
while en_US.UTF-8 has at least DD MMM ... Having
-MM-DD HH:MM:SS[+]
instead would be much nicer if we were to create an arbitrary
On Thu, Feb 07, 2019 at 10:21:49PM +0100, Ansgar wrote:
(And you get 24-hour time, but very strange Endian in C.UTF-8:
WEEKDAY MMM DD HH:MM:SS TZ
while en_US.UTF-8 has at least DD MMM ... Having
-MM-DD HH:MM:SS[+]
instead would be much nicer if we were to create an arbitrary
On Thu, Feb 07, 2019 at 09:20:07PM +0100, Ondřej Surý wrote:
en_DK.UTF-8 is a good default locale?
I think the suggestion of just "en" made the most sense--specify the
language and an arbitrary set of rules that aren't tied to a specific
country.
Per the standard, the C locale is supposed to be a synonym for the POSIX
locale. Can someone give a quick explanation for why in debian the C
locale definition is 162k and the POSIX locale is 8k? Shouldn't they be
identical?
On Thu, Feb 07, 2019 at 04:08:21PM +0100, Ansgar wrote:
On Thu, 2019-02-07 at 09:59 -0500, Michael Stone wrote:
On Thu, Feb 07, 2019 at 02:40:06PM +, Simon McVittie wrote:
> How would this locale differ from C.UTF-8? Is the only difference
> that C.UTF-8 has strict lexicographical s
On Thu, Feb 07, 2019 at 04:08:21PM +0100, Ansgar wrote:
On Thu, 2019-02-07 at 09:59 -0500, Michael Stone wrote:
On Thu, Feb 07, 2019 at 02:40:06PM +, Simon McVittie wrote:
> How would this locale differ from C.UTF-8? Is the only difference
> that C.UTF-8 has strict lexicographical s
On Thu, Feb 07, 2019 at 04:08:21PM +0100, Ansgar wrote:
On Thu, 2019-02-07 at 09:59 -0500, Michael Stone wrote:
On Thu, Feb 07, 2019 at 02:40:06PM +, Simon McVittie wrote:
> How would this locale differ from C.UTF-8? Is the only difference
> that C.UTF-8 has strict lexicographical s
On Thu, Feb 07, 2019 at 02:40:06PM +, Simon McVittie wrote:
How would this locale differ from C.UTF-8? Is the only difference
that C.UTF-8 has strict lexicographical sorting, whereas "en" would have
case-insensitive sorting like en_GB.utf8 does? (If that's the only
difference, then perhaps
On Thu, Feb 07, 2019 at 02:40:06PM +, Simon McVittie wrote:
How would this locale differ from C.UTF-8? Is the only difference
that C.UTF-8 has strict lexicographical sorting, whereas "en" would have
case-insensitive sorting like en_GB.utf8 does? (If that's the only
difference, then perhaps
On Thu, Feb 07, 2019 at 02:40:06PM +, Simon McVittie wrote:
How would this locale differ from C.UTF-8? Is the only difference
that C.UTF-8 has strict lexicographical sorting, whereas "en" would have
case-insensitive sorting like en_GB.utf8 does? (If that's the only
difference, then perhaps
Package: unbound
Version: 1.9.0-1
Severity: grave
Justification: renders package unusable
Immediately after installing 1.9.0-1, unbound refused to run after restart.
System logs contained:
Feb 6 11:00:24 annuminas package-helper[6142]: /var/lib/unbound/root.key has
content
Feb 6 11:00:24
Package: unbound
Version: 1.9.0-1
Severity: grave
Justification: renders package unusable
Immediately after installing 1.9.0-1, unbound refused to run after restart.
System logs contained:
Feb 6 11:00:24 annuminas package-helper[6142]: /var/lib/unbound/root.key has
content
Feb 6 11:00:24
On Wed, Feb 06, 2019 at 10:47:12AM +0100, Johannes Schauer wrote:
On Wed, 30 Jan 2019 12:07:37 +0100 Jonas Smedegaard wrote:
Jus a friendly nudge: It would be great if this bug was fixed in time for
Buster.
Do you think you can find the time to have a look at the patches
provided by Josch?
On Mon, Feb 04, 2019 at 12:05:08AM +0500, Alexander V. Makartsev wrote:
Turns out you are right. Modern 2.5" HDDs are made to be more demanding,
according to hardware specs available on web sites of WD and Seagate. Only
exception are 2.5" L200 series drives from Toshiba. They require <500mA to
On Thu, Jan 31, 2019 at 07:04:02PM +0100, Harald Welte wrote:
The problem is that there's basically no alternative to the net6501 on the
market
if you require 1U, fanless, small (short 1U enclosure), and a single PCIe slot.
There are actually a lot more options these days for those
of thing that should
be sorted out when a package is ITP'd and discussed, not done and then
declared a fait accompli.)
--
Michael Stone
of thing that should
be sorted out when a package is ITP'd and discussed, not done and then
declared a fait accompli.)
--
Michael Stone
On Wed, Jan 23, 2019 at 05:19:13AM -0500, Henrique de Moraes Holschuh wrote:
On Mon, Jan 21, 2019, at 10:36, Michael Stone wrote:
Yes, but most of those features are obsolescent at best. I'm not clear
on what functionality is actually being used. (I'm hesitant to remove
"old"
On Wed, Jan 23, 2019 at 05:19:13AM -0500, Henrique de Moraes Holschuh wrote:
On Mon, Jan 21, 2019, at 10:36, Michael Stone wrote:
Yes, but most of those features are obsolescent at best. I'm not clear
on what functionality is actually being used. (I'm hesitant to remove
"old"
On Wed, Jan 23, 2019 at 05:46:39AM -0500, Henrique de Moraes Holschuh wrote:
On Sun, Jan 20, 2019, at 14:06, Thorsten Glaser wrote:
But you’re not in a situation to command either, considering
hmh is the ONLY maintainer of rng-tools so we WILL need his
input on this (or do an NMU).
Anything
On Wed, Jan 23, 2019 at 05:46:39AM -0500, Henrique de Moraes Holschuh wrote:
On Sun, Jan 20, 2019, at 14:06, Thorsten Glaser wrote:
But you’re not in a situation to command either, considering
hmh is the ONLY maintainer of rng-tools so we WILL need his
input on this (or do an NMU).
Anything
On Mon, Jan 21, 2019 at 04:47:51PM +0100, Diederik de Haas wrote:
On maandag 21 januari 2019 13:34:19 CET Michael Stone wrote:
On Mon, Jan 21, 2019 at 01:15:13PM +0100, Diederik de Haas wrote:
>On zondag 20 januari 2019 16:59:11 CET Thorsten Glaser wrote:
>> I’m very much against ju
On Mon, Jan 21, 2019 at 04:47:51PM +0100, Diederik de Haas wrote:
On maandag 21 januari 2019 13:34:19 CET Michael Stone wrote:
On Mon, Jan 21, 2019 at 01:15:13PM +0100, Diederik de Haas wrote:
>On zondag 20 januari 2019 16:59:11 CET Thorsten Glaser wrote:
>> I’m very much against ju
On Mon, Jan 21, 2019 at 01:15:13PM +0100, Diederik de Haas wrote:
On zondag 20 januari 2019 16:59:11 CET Thorsten Glaser wrote:
I’m very much against just saying this package
“should not exist”
I'm inclined to agree with this as the source (+ features/parameters) for this
package is
On Mon, Jan 21, 2019 at 01:15:13PM +0100, Diederik de Haas wrote:
On zondag 20 januari 2019 16:59:11 CET Thorsten Glaser wrote:
I’m very much against just saying this package
“should not exist”
I'm inclined to agree with this as the source (+ features/parameters) for this
package is
On Sun, Jan 20, 2019 at 03:59:11PM +, Thorsten Glaser wrote:
• keep rng-tools5 and rng-tools-debian in testing
FWIW, I'd much rather call this rng-tools2 or rng-tools-legacy or
something other than rng-tools-debian (which implies that for some
reason this version is more "debian" than
On Sun, Jan 20, 2019 at 03:59:11PM +, Thorsten Glaser wrote:
Please don’t understand me wrong, I’m not against a sensible solution
out of this mess, but I’m very much against just saying this package
“should not exist” without one.
Once it's in stable, this mess is a lot harder to fix, so
On Sun, Jan 20, 2019 at 04:05:09PM +, Thorsten Glaser wrote:
Michael Stone dixit:
So use the epoch. They're invented for fixing collosal errors like
this. Except this time, have the appropriate discussion on -devel
instead of just uploading something without coordination.
Sounds like
On Sun, Jan 20, 2019 at 04:05:09PM +, Thorsten Glaser wrote:
Michael Stone dixit:
So use the epoch. They're invented for fixing collosal errors like
this. Except this time, have the appropriate discussion on -devel
instead of just uploading something without coordination.
Sounds like
On Sun, Jan 20, 2019 at 03:41:22PM +, Thorsten Glaser wrote:
Michael Stone dixit:
Please upload a fixed version of rng-tools instead, reverting the erroneous
change.
That is impossible because the version changed.
In the tool I’m using, I have a hard version requirement on
rng-tools
On Sun, Jan 20, 2019 at 03:41:22PM +, Thorsten Glaser wrote:
Michael Stone dixit:
Please upload a fixed version of rng-tools instead, reverting the erroneous
change.
That is impossible because the version changed.
In the tool I’m using, I have a hard version requirement on
rng-tools
Package: rng-tools-debian
I don't entirely understand why this package was ever uploaded, and as
far as I can tell, with no ITP. It should not be included in buster.
Package: ftp.debian.org
This package was uploaded as part of a series of uncoordinated changes
to various rng-tools packages. It would be best that it not enter a
stable release, and it isn't clear that the package is needed at all. I
can't find an ITP dicussing this package or how it should
On Sun, Jan 20, 2019 at 03:25:12PM +, Thorsten Glaser wrote:
Michael Stone dixit:
No, that's something else that shouldn't have happened
It’s important to me because the upload of rng-tools (>> 2)
broke things on unstable.
So that should be fixed--the problem should not be made
On Sun, Jan 20, 2019 at 03:25:12PM +, Thorsten Glaser wrote:
Michael Stone dixit:
No, that's something else that shouldn't have happened
It’s important to me because the upload of rng-tools (>> 2)
broke things on unstable.
So that should be fixed--the problem should not be made
On Sun, Jan 20, 2019 at 03:01:18PM +0100, Diederik de Haas wrote:
On Fri, 11 Jan 2019 14:51:05 -0500 Michael Stone wrote:
On Fri, Jan 11, 2019 at 01:57:28PM -0500, Michael Stone wrote:
>There never should have been an NMU simply replacing rng-tools with
>rng-tools5. I did not
On Sun, Jan 20, 2019 at 03:01:18PM +0100, Diederik de Haas wrote:
On Fri, 11 Jan 2019 14:51:05 -0500 Michael Stone wrote:
On Fri, Jan 11, 2019 at 01:57:28PM -0500, Michael Stone wrote:
>There never should have been an NMU simply replacing rng-tools with
>rng-tools5. I did not
On January 14, 2019 11:56:20 AM EST, "W. Martin Borgert"
wrote:
>Quoting Michael Stone :
>> Unless the cpu supports rdrand/rdseed, installing rng-tools5 won't
>> really change anything. If it does support those, it probably makes
>> more sen
On Mon, Jan 14, 2019 at 12:55:09PM +0100, Marco d'Itri wrote:
Agreed. I think that d-i should install rngd (or haveged? And why?) if
it detects a virtualized environment without virtio-rng.
Unless the cpu supports rdrand/rdseed, installing rng-tools5 won't
really change anything. If it does
On Fri, Jan 11, 2019 at 04:56:07PM -0800, Patrick Bartek wrote:
On Fri, 11 Jan 2019 07:13:30 -0500 Michael Stone wrote:
On Thu, Jan 10, 2019 at 03:53:11PM -0800, Patrick Bartek wrote:
>Plus, I
>want to have a common-shared /boot partition for possible future
>upgrades or e
On Fri, Jan 11, 2019 at 01:57:28PM -0500, Michael Stone wrote:
There never should have been an NMU simply replacing rng-tools with
rng-tools5. I did not notice that this had happened.
Also, the correct fix for buster is an upload to put things back the way
they were, which is going to be ugly.
601 - 700 of 4126 matches
Mail list logo
