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
be as if the date
command were executed at the time of the last modification date of the
file rather than the current time. When the LC_TIME locale category is
not set to the POSIX locale, a different format and order of
presentation of this field may be used.
Mike Stone
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?
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: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 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 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: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
Package: systemd
Version: 240-2
4.19.0-1 buster/sid
Since upgrading systemd to version 240-2, systemd-tmpfiles fails with error
message:-
Detected unsafe path transition
for every conf file in /usr/lib/tmpfiles.d.
Consequently, /tmp/.x11-unix is one of the paths NOT created which causes
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.
There never should have been an NMU simply replacing rng-tools with
rng-tools5. I did not notice that this had happened.
On Fri, Jan 11, 2019 at 07:21:49PM +0100, Andreas Henriksson wrote:
That has apparently failed to materialize well in time for buster.
Looking at the contents of the binary
Package: gnome-shell
Version: 3.30.1-2
Testing 4.19.0-1 (buster amd64)
Cannot boot my laptop. gnome-shell fills up syslog with these messages.
There may be some typo's as I had to write this down and go to the
local library.
gnome-shell[1458]: failed to bind to /tmp/.X11-unix/X1024: No such
nsible system.
>
>what is the status of this bug? Without this patch, the functionality
>of
>fakechroot and mmdebstrap in the next stable release will be hampered.
>If you
>don't have time, I could also NMU coreutils with the attached patch.
>
>What do you think?
>
>Thanks!
>
>cheers, josch
Please just wait
--
Michael Stone
(From phone, please excuse typos)
There's an ABI incompatibility between LLVM compiled with GCC and Clang:
https://bugs.llvm.org/show_bug.cgi?id=39427
So if you have a Clang-built libLLVM.so, and rustc's src/rustllvm is
built with GCC, then I think you may be hitting this problem.
documentation available at
https://www.gnu.org/software/make/manual/html_node/index.html
Which is much more likely to be useful to a user on a default debian
install.
Mike Stone
ay be useful to note that the netmask keyword is a
legacy/deprecated keyword that can be fully replaced with the current
address syntax.
Mike Stone
severity 909803 serious
thanks
There does not seem to be any logic in the freeipa-client package to
ensure a working time configuration after ntp is forced out in favor of
chrony. This implies that a freeipa client may become unusable after
upgrade once its clock has drifted far enough in the
Package: freeipa-client
Version: 4.7.0-1
Severity: normal
freeipa client does not technically require chrony (or, previously, ntp). The
ipa-client-install routine provides an option to not configure NTP, and the
ipa docs instruct that this option should be used if the administrator wants
to use a
will be correct regardless of what kind of filesystem object is at
${_DIRECTORY}.
--
Mike Stone
On Sat, Jul 21, 2018 at 02:35:59AM +0100, Ben Hutchings wrote:
I think you can do something like:
[...]
# postinst time: use link & rename to replace working version atomically.
It's technically possible, but AFAICT a policy violation.
Mike Stone
point to that.
Mike Stone
the usable and working version demands a coordinated libc package.
Mike Stone
of the memory used by the process;
if it's actually important to keep data from being written to persistent
storage, it should be set unswappable using mlock. I have no idea how
one would do this effectively in a shell script.)
Mike Stone
severity 902031 grave
done
I'm raising the severity of this so it doesn't enter testing before it
gets fixed. (The rationale is that the config file is used to blacklist
programs which shouldn't be restarted[killed] because doing so may cause
loss of work.)
Yeah, this is kinda important and somewhat dangerous. The config is
supposed to *not* restart things that might kill what the user is
working on, and that's currently broken.
On Thu, May 17, 2018 at 05:21:34PM +0200, Ferenc Wágner wrote:
Michael Stone <mst...@debian.org> writes:
On Thu, May 17, 2018 at 04:15:44PM +0200, you wrote:
Michael Stone <mst...@debian.org> writes:
It would not--POSIX does not disallow the . syntax.
(This is not my poin
On Thu, May 17, 2018 at 04:15:44PM +0200, you wrote:
Michael Stone <mst...@debian.org> writes:
It would not--POSIX does not disallow the . syntax.
(This is not my point, but in my reading
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/chown.html
does not allow it: "The
well as-is.
Mike Stone
anks,
> Jeremy Bicha
>
Whups, forgot about that. Yes, or at least orphaned. Upstream is the
same for both and development stopped quite some time ago. If someone
is interested in maintaining these, please pick them up.
--
Ciao,
al
---
A debconf function to prevent creating an unbootable system would still
be nice...
or version
string anyway, why use some complicated profile system instead of just
applying a patch? This seems overly complicated for simple cases and
overly fragile for complex cases.
Mike Stone
On Sun, Jan 07, 2018 at 07:49:15PM +0100, Hans van Kranenburg wrote:
On 01/07/2018 06:42 PM, Michael Stone wrote:
retitle 886491 linux-image-4.9.0-5-amd64: Does not boot as Xen guest in
PVH mode
thanks
HVM and PVH are two different modes. The fix suggested in this bug
report (commenting out
4.9.0-5 and a conf file that boots fine with -3.
Mike Stone
ternative, to the point that it's not
generally possible to assume that the real upstream version number can
be extracted from the debian version.
Mike Stone
just an fyi: packages have been put in for NEW queue processing
Source: libunwind
Severity: minor
Since I have not actively used or maintained this package in
quite a long time, there is no need for me to be included as
an Uploader; so, please remove "Al Stone <a...@debian.org>"
from the Uploaders list.
Thanks.
-- System Information:
Debian
Package: ftp.debian.org
Severity: normal
There is no need to retain this package in the archives. There
are very, very few users, and there is no upstream development
ongoing or planned.
statistics ( https://github.com/borgbackup/borg/issues/265 )
Regards,
Martin Stone
that's your choice.
Mike Stone
orked very well, but
if there are really people who use it perhaps that can be separated into a
different package so people who just want to IM don't have to increase the
attack surface of anything that uses gstreamer.
Mike Stone
On Tue, Oct 17, 2017 at 10:26:06PM +0200, Guus Sliepen wrote:
On Mon, Oct 16, 2017 at 10:21:10PM -0400, Michael Stone wrote:
On Tue, Oct 17, 2017 at 12:05:30AM +0200, Guus Sliepen wrote:
> despite fears of OpenBSD only caring about themselves, I have found that
> it is easier to c
if not
having that option was a conscious decision.
Mike Stone
either maintaining the entire LibreSSL package over a period of years,
or fork.
Mike Stone
cycle (not to mention debian LTS)? I think that in
practical terms that would leave us worse off than settling on a
compatability layer that's shared with other distributions.
Mike Stone
the problem,
it's actually using them once they're running. Probably also requires
running as a non-root user (I don't think nproc applies to root). So the
processes start fine as root, then setuid something else, then can not
fork subsequently.
Mike Stone
would result in a grub kernel command line with root=UUID=X
Mike Stone
I also vaguely remember
that there was a conscious decision that it was silly to distribute
sub-standard packages...
Mike Stone
to replace instances of @(br|eth) with
@(br|eth|eno|ens|enp|enx) or perhaps @(br|eth|en)
Mike Stone
For the record, I'll append what I said in 877582 so it's all in one
place:
You can call ls -N if desired or set QUOTING_STYLE=literal. I overrode
the default until such a time as a version of coreutils supporting all
of the new semantics/options reached stable, so that users could
configure
Package: common-lisp-controller
Version: 7.10
Followup-For: Bug #780947
Priority of this bug should be raised, as the transitional package is on its
way out, having been in both jessie and stretch stable releases. The bash
dependency seems similarly obsolete.
Mike Stone
Package: grml2usb
Version: 0.16.0
Severity: normal
The transition of realpath to coreutils happened for the jessie release, so it
should be possible to drop the dependency on the essential package coreutils.
Mike Stone
Package: dgit
Version: 3.12
Severity: normal
The transition of realpath to the essential package coreutils happened for
jessie, and the coreutils | realpath dependency should now be dropped.
Mike Stone
nal package is
going away and the dependency on the essential package coreutils should just be
dropped.
Mike Stone
Package: bootcd
Version: 5.09
Severity: normal
bootcd has a dependency on realpath | coreutils (>= 8.23-1) which should no
longer be needed as the appropriate version of coreutils has been an essential
package in multiple stable releases.
Mike Stone
Package: kopano-search
Version: 8.3.4-2
Severity: normal
kopano-search should no longer require dependencies on coreutils >= 5.93 or
mktemp >= 1.5, as these have been Essential packages for several releases.
The dependency on bash >= 3.0 is similarly redundant.
Mike Stone
On Mon, Oct 02, 2017 at 06:17:37PM +0100, Ian Jackson wrote:
Michael Stone writes ("Re: Bug#877174: coreutils: timeout should (optionally) emit
an error message when timeout reached"):
On Mon, Oct 02, 2017 at 02:21:37PM +0100, you wrote:
...
>Do you agree that these ad-hoc ru
On Mon, Oct 02, 2017 at 02:21:37PM +0100, you wrote:
Mike Stone:
It should grab the original exit status and then propagate it, no?
Oh, yes, sorry. I hadn't spotted that it didn't use set -e (which is
IMO poor practice).
Except, of course, if you need to muck about with return codes, no? I
concern raised
which can be ignored if desired.
I personally have an easier time coming up with use cases where I'd want
the return code to initiate further logic than cases where just printing
a message and doing nothing else is useful, but that's neither here nor
there.
Mike Stone
On Mon, Oct 02, 2017 at 01:51:15PM +0100, you wrote:
bugs (for example, your suggestion smashes the exit status with zero);
It should grab the original exit status and then propagate it, no?
Mike Stone
On Sat, Sep 30, 2017 at 01:08:18AM +0200, Manuel A. Fernandez Montecelo wrote:
2017-09-29 2:59 GMT+02:00 Michael Stone <mst...@debian.org>:
I'd rather have a standardized build option to skip the documentation than
something that sometimes builds man pages that don't match what's being
would
make timeout say something like "timeout elapsed, killing ...".
Try
ExecStart=/bin/sh -c 'timeout 120 flock /var/lock/ceph-disk-$(basename %f) /usr/sbin/ceph-disk --verbose --log-stdout trigger --sync %f ; RET=$? ; if [ $RET -eq 124 ] ; then echo "Timed out!" ; fi ; return $RET'
Mike Stone
of packages seems like a less-than-optimal
solution.
Mike Stone
Package: synaptic
Version: 0.84.2
Errors from syslog:-
Aug 28 23:30:52 roblaptop synaptic.desktop[6912]: No protocol specified
Aug 28 23:30:52 roblaptop synaptic.desktop[6912]: Unable to init
server: Could not connect: Connection refused
Aug 28 23:30:52 roblaptop synaptic[6914]: cannot open
On 07/24/2017 09:30 AM, Graham Inggs wrote:
> Source: libunwind
> Version: 1.1-4.1
> Severity: serious
> X-Debbugs-CC: a...@debian.org
>
> Hi Al
>
> As per #863770 and #868643, Matthieu Delahaye and Daigo Moriwaki are no
> longer maintaining libunwind. Al Stone,
low, but I'd also suggest a much higher default limit. It is not
clear to me what problem a limit of 10 solves that wouldn't be solved by a
limit of 1000, while a higher limit is much less likely to be hit through
legitimate use.
Mike Stone
for sha256.o on PPC to fix
+performance regression (Closes: #854053)
+
+ -- Michael Stone <mst...@debian.org> Wed, 22 Feb 2017 07:23:45 -0500
+
coreutils (8.26-2) unstable; urgency=low
* Fix regression in which specifying a TZ in date -d causes the
diff -Nru coreutils-8.26/debian/c
Can you confirm
https://people.debian.org/~mstone/coreutils_8.26-3_ppc64el.deb fixes the
problem?
I ended up with this:
Index: coreutils-8.26/Makefile.in
===
--- coreutils-8.26.orig/Makefile.in 2016-11-30 13:34:55.0
On Tue, Feb 07, 2017 at 06:16:10PM +, you wrote:
So, is my patch viable or not? If not, what would you then recommend to avoid
this?
Not as stands because it lacks the pieces to make it
architecture-specific.
Mike Stone
ut making it conditional on ppc
seems essential. Upstream would probably want some kind of compiler
based test. My understanding is that just adding this option to cflags
when building on the appropriate architecture wouldn't work, because it
would negatively impact other code, is that correct?
M
Package: reportbug
Version: 7.1.2
Output of uname -a
Linux roblaptop 4.9.0-1-amd64 #1 SMP Debian 4.9.2-2 (2017-01-12) x86_64
GNU/Linux
rob@roblaptop:~$ reportbug
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2233, in
main()
File "/usr/bin/reportbug", line 1107,
Package: acpi
Version: 1.7-1
These errors appear in syslog whilst booting up my laptop:-
Feb 2 00:07:51 roblaptop kernel: [ 16.159971] ACPI Error: Field
[B128] at 1152 exceeds Buffer [NULL] size 160 (bits)
(20160831/dsopcode-236)
Feb 2 00:07:51 roblaptop kernel: [ 16.160132] ACPI
and not know how to access
their stored data, right?
Mike Stone
(which seems to be working?) and explains the situation in
the README?
Mike Stone
) that enables
that functionality and pulls in the dependency tail--so users can make
an informed decision about what they want to do.
Mike Stone
On 01/15/2017 11:14 PM, Chris Lamb wrote:
>> Would you consider applying this patch and uploading?
>
> Friendly ping on this :)
>
>
> Best wishes,
>
Thanks. I have not forgotten, just busy.
--
Ciao,
al
---
Package: python-evtx
Version: 0.5.3b-2
Severity: important
> /usr/bin/evtxdump.py
Traceback (most recent call last):
File "/usr/bin/evtxdump.py", line 25, in
from Evtx.Evtx import FileHeader
File "/usr/lib/python2.7/dist-packages/Evtx/Evtx.py", line 28, in
from .Nodes import
Package: tcsh
Version: 6.20.00-1
Severity: critical
Justification: breaks unrelated software
/usr/bin/tcsh is no longer being provided by the tcsh package. This prevents
logins from users with a shell of /usr/bin/tcsh, and breaks active sessions in
various ways (when software attempts to use
to.
Mike Stone
solution for 8 years...
Mike Stone
reflects the hardware the
container is running on).
Mike Stone
turn value of a system call whose only semantic is that it returns
a stable value in some (not fully defined) case. Or just explain to
people how to use the options that already exist.
Mike Stone
On Wed, Sep 28, 2016 at 11:11:21PM +0200, Petter Reinholdtsen wrote:
[Michael Stone]
Other platforms have deprecated gethostid, that's the best way forward for
linux, IMO.
Which platforms is this? I find FreeBSD recommend to use sysctl and
KERN_HOSTID to get the hostid integer directly from
are from a vendor
that sets such a property*.
If you want something tied to the OS instance rather than the machine,
then use /etc/machine-id (and gnash your teeth at the misnomer) rather
than reinventing it.
Mike Stone
. If you have the lsof command installed (apt-get
install lsof) you can try something like lsof | grep -i del | grep
/megastorage
to identify deleted files and the process which has it open.
Mike Stone
Thanks for your reply.
lsof | grep -i del | grep /megastorage
shows nothing
You ran
have the lsof command installed (apt-get
install lsof) you can try something like
lsof | grep -i del | grep /megastorage
to identify deleted files and the process which has it open.
Mike Stone
Package: debtags
Version: 2.1
Severity: serious
Tags: d-i
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
It occurs each time I do
data files which can't be read by anythin
in debian.
Mike Stone
"Sun Mar 27 01:00:00 UTC 2016"
Sat Mar 26 21:00:00 EDT 2016
Seems broken to me...
Mike Stone
time because the system doesn't start rpc.gssd until after attemping the
nfs mounts. There should be some ordering to ensure that the mounts aren't
attempted until after the nfs-common startup is complete.
Mike Stone
-- Package-specific info:
-- rpcinfo --
program vers proto port service
On Wed, Feb 03, 2016 at 03:18:15PM +0100, Christoph Anton Mitterer wrote:
Though that could be fixed... a smart quoting algorithm could produce
something like.
o\'really
or
"o'really"
That acutally exists: see --quoting-style=c
also check out --quoting-style=escape
Mike Stone
Does anyone want to chime in with support for the change? I'm mostly
ambivalent, but then I don't have a lot of filenames that are actually
affected.
Mike Stone
101 - 200 of 1211 matches
Mail list logo
