On Wed 10 Apr 2019 at 13:26:39 (+0200), Vincent Lefevre wrote:
> On 2019-04-09 13:28:40 -0500, David Wright wrote:
> > On Tue 09 Apr 2019 at 15:38:43 (+0200), 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
>
On 2019-04-09 13:28:40 -0500, David Wright wrote:
> On Tue 09 Apr 2019 at 15:38:43 (+0200), 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
> >
> >
On Tue 09 Apr 2019 at 20:07:37 (-), Curt wrote:
> On 2019-04-09, Étienne Mollier wrote:
> >
> > The output may differ depending on you operating system level,
> > given Reco's observations. Feel free to have à look at
> > /usr/share/zoneinfo/, to have an idea of the available
> > locations.
On 2019-04-09, Étienne Mollier wrote:
>
> The output may differ depending on you operating system level,
> given Reco's observations. Feel free to have à look at
> /usr/share/zoneinfo/, to have an idea of the available
> locations.
I took a look.
I was confused to note the presence of the UCT
On Tue 09 Apr 2019 at 14:55:37 (-0400), Greg Wooledge wrote:
> On Tue, Apr 09, 2019 at 01:28:40PM -0500, David Wright wrote:
> > My question about the OP's issue is whether I'm going to have to
> > change something to keep what I get in jessie and stretch, or is
> > this just a temporary bug in
On Tue 09 Apr 2019 at 20:46:53 (+0200), Étienne Mollier wrote:
> On 4/9/19 8:39 PM, David Wright wrote:
> > We avoided the problem when I went to sea by using the letter codes,
> > Z(ulu), A(lpha), B(ravo) etc. because there are no civil timezones,
> > daylight savings times or anything else.
>
On Tuesday 09 April 2019 14:39:19 David Wright wrote:
> On Tue 09 Apr 2019 at 14:03:08 (-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
> > >
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 Tuesday 09 April 2019 14:28:18 Michael Stone wrote:
> 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
> >> >
On Tue, Apr 09, 2019 at 01:28:40PM -0500, David Wright wrote:
> My question about the OP's issue is whether I'm going to have to
> change something to keep what I get in jessie and stretch, or is
> this just a temporary bug in buster. Or has the US format been
> wrong all along? (As an expat, I'm
On 4/9/19 8:39 PM, David Wright wrote:
> We avoided the problem when I went to sea by using the letter codes,
> Z(ulu), A(lpha), B(ravo) etc. because there are no civil timezones,
> daylight savings times or anything else.
You mean, like this ?
$ TZ=Zulu date
Tue Apr 9 18:46:20
On Tue 09 Apr 2019 at 14:03:08 (-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
> >
> >
Gene Heskett, on 2019-04-09 :
> On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote:
> > This is unrelated to your issue, but note that the correct TZ string
> > for UTC is "UTC0", not "UTC". See
> >
> > http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.htm
> > l
>
> Yikes.
On Tue 09 Apr 2019 at 15:38:43 (+0200), 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 your issue, but note that the correct TZ string
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 Tue, Apr 09, 2019 at 02:03:08PM -0400, Gene Heskett wrote:
> Yikes. Can that be actually put into English?
"Use date -u instead."
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 your issue, but note that the correct TZ string
> for
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 your issue, but note that the correct TZ string
for UTC is "UTC0", not "UTC". See
I managed to build a locale with a customized LC_TIME setting under
buster. It's not documented in a straightforward manner anywhere I
could find, so I'm going to spell it all out here.
Step 1: Start with an existing locale definition.
In my case, I am starting with Debian buster's en_US
Cindy-Sue Causey, on 2019-04-08 :
> Found this over at Tecmint:
>
> https://www.tecmint.com/set-system-locales-in-linux/
>
> locale -k LC_TIME
>
> Very coo AND further implies *WHAT ELSE can that little puppy do*, but
> my brain's already cognitively sundowning so am passing the baton on
> for
Hi.
On Mon, Apr 08, 2019 at 07:10:50PM +0200, Étienne Mollier wrote:
> > My question is - can anyone suggest me appropriate LC_TIME setting that
> > can show buster's date in stretch's format?
>
> $ LC_TIME=en_US.UTF-8 TZ=UTC date
> Mon 08 Apr 2019 05:07:44 PM UTC
>
>
Hi,
Cindy Sue Causey wrote:
> I'd like mine to be in the '2009.04.08' format.
$ date +'%Y.%m.%d'
2019.04.08
Have a nice day :)
Thomas
On 4/8/19, Étienne Mollier wrote:
> On 4/8/19 5:26 PM, Reco wrote:
>> Dear list,
>>
>> the following thing got my attention recently:
>>
>> 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
>>
>> It's not that I depend on certain
On 4/8/19 5:26 PM, Reco wrote:
> Dear list,
>
> the following thing got my attention recently:
>
> 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
>
> It's not that I depend on certain date format in scripts, but I got used
> to
Dear list,
the following thing got my attention recently:
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
It's not that I depend on certain date format in scripts, but I got used
to this 24-hour time format after all these years. And
25 matches
Mail list logo
