On 12/18/23, David Wright wrote:
> Another problem in what you posted is that you sometimes run date
> in your local timezone (generally for the "now" times), but you
> append +00:00 as the timezone for those --date strings that you
> construct from several substrings. You need to use UT
On Mon 18 Dec 2023 at 01:11:26 (+), Albretch Mueller wrote:
> On 12/18/23, David Wright wrote:
> > When you write dt00=$(date +%Y%m%d%H%M%S)
> > that's /your/ format, not coreutils'.
>
> I (erroneously?) thought coreutils was maintaining Linux date, so if
> they tell you on their --help
>> That was a typo. it's `/var/cache/plocate/plocate.db`, sorry.
> My plocate.db is in /var/lib/plocate/, as is bookworm's.
> Is that changing in the future?
Hmm... I could swear that I saw it in /var/cache but every machine
I look at has it in /var/lib, indeed.
[ GNU locate puts its DB in
On Sun, Dec 17, 2023 at 09:42:19PM -0500, Cindy Sue Causey wrote:
> dpkg-deb: error: failed to read archive
> '/var/cache/apt/archives/dpkg_1.22.1_amd64.deb': Too many levels of
> symbolic links
> dpkg: error: parsing file '/var/lib/dpkg/status' near line 2 package 'dpkg':
> 'Version' field value
On 12/16/23, Pocket wrote:
>
> On 12/16/23 08:45, Stephen P. Molnar wrote:
>> I am running Bookworm on my Debian computer. When I installed the OS I
>> selected the option for separate /var etc, and selected the default
>> sizes of the partitions.
>>
>> When I ran sudo apt update this morning I
On 18/12/2023 06:00, Albretch Mueller wrote:
On 12/17/23, Andy Smith wrote:
how on earth would that not always produce an accurate duration?
All this paranoia, but in computer time you trust?
Falsehoods programmers believe about time
On 12/18/23, David Wright wrote:
> When you write dt00=$(date +%Y%m%d%H%M%S)
> that's /your/ format, not coreutils'.
I (erroneously?) thought coreutils was maintaining Linux date, so if
they tell you on their --help instructions to use certain options
(including cobbling them together to your
On Sun 17 Dec 2023 at 15:33:30 (-0500), Stefan Monnier wrote:
> >> That seems similar to things like `locate` failing if you remove
> >> `/var/log/plocate/plocate.db` (until that DB is rebuilt).
> >
> > It's tricky to discern your point as /var/log/ is not involved.
>
> That was a typo. it's
Olá pessoal,
Antes de 2023 acabar, estamos trazendo boas notícias para o próximo ano!
De 27 a 30 de abril acontecerá a MiniDebConf Belo Horizonte 2024 no
Campus Pampulha da UFMG - Universidade Federal de Minas Gerais.
Após 4 edições que aconteceram em Curitiba (2016, 2017 e 2018) e em
On Sun 17 Dec 2023 at 23:00:37 (+), Albretch Mueller wrote:
> On 12/17/23, Andy Smith wrote:
> > All this paranoia, but in computer time you trust?
> > Falsehoods programmers believe about time
> > https://gist.github.com/timvisee/fcda9bbdff88d45cc9061606b4b923ca
>
> and how does
On 12/17/23, Andy Smith wrote:
>> how on earth would that not always produce an accurate duration?
>
> All this paranoia, but in computer time you trust?
> Falsehoods programmers believe about time
> https://gist.github.com/timvisee/fcda9bbdff88d45cc9061606b4b923ca
and how does my
Well, yes, "date --date= ..." doesn't work in the way I would wish
("logically" think about it):
https://www.gnu.org/software/coreutils/manual/html_node/General-date-syntax.html
parsing any format allowed by date:
Saludos a todos. He heredado una HP Envy con I7 SSD y varios chiches
más, gracias a que al dueño se le quebró parte del monitor y ya no la
quiere. En fin, la consulta es la siguiente: estuve buscando en la web
qué tal va la compatibilidad con debian (es el SO que uso hace años y
no quisiera
>> That seems similar to things like `locate` failing if you remove
>> `/var/log/plocate/plocate.db` (until that DB is rebuilt).
>
> It's tricky to discern your point as /var/log/ is not involved.
That was a typo. it's `/var/cache/plocate/plocate.db`, sorry.
Stefan
On Sun 17 Dec 2023 at 01:06:28 (-0500), Stefan Monnier wrote:
> > Some packages will stay the same for years, but in the past week
> > I can see four occasions when changes in list contents have occurred
> > on oldstable. So there's little similarity.
>
> The question is not really whether
On Sun 17 Dec 2023 at 15:28:58 (+), Albretch Mueller wrote:
> On 12/17/23, to...@tuxteam.de wrote:
> > On Sun, Dec 17, 2023 at 10:12:11AM +, Albretch Mueller wrote:
> >> dt00=$(date +%Y%m%d%H%M%S)
> Actually, my basic idea is if you can encode a date using formatting
> options this
On Sun, Dec 17, 2023 at 03:28:58PM +, Albretch Mueller wrote:
> On 12/17/23, Greg Wooledge wrote:
> > On Sun, Dec 17, 2023 at 10:12:11AM +, Albretch Mueller wrote:
> >> ... after some long processing for which seconds would be exact
> >> enough, then I would like to get the seconds
Hello,
On Sun, Dec 17, 2023 at 03:28:58PM +, Albretch Mueller wrote:
> On 12/17/23, Andy Smith wrote:
> > subtracting one epoch time from another doesn't always produce
> > an accurate duration.
[…]
> how on earth would that not always produce an accurate duration?
All this paranoia, but
On 2023-12-17, Max Nikulin wrote:
> On 16/12/2023 22:46, Stephen P. Molnar wrote:
>>
>> I'll add 'sudo apt-get autoclean to' my update bat file.
>
> I have
>
> APT::Keep-Downloaded-Packages "false";
I thought that was the default now for apt. But then he said "sudo apt" in the
OP and
On Sun, Dec 17, 2023 at 03:28:58PM +, Albretch Mueller wrote:
> On 12/17/23, to...@tuxteam.de wrote:
[...]
> > You wouldn't expect bash to intuit such a crooky arithmetic as
> > Gregorian datetime [...]
> Actually, my basic idea is if you can encode a date using formatting
> options this
On Sun, Dec 17, 2023 at 03:28:58PM +, Albretch Mueller wrote:
> On 12/17/23, to...@tuxteam.de wrote:
> > On Sun, Dec 17, 2023 at 10:12:11AM +, Albretch Mueller wrote:
> >> dt00=$(date +%Y%m%d%H%M%S)
> >> echo "// __ \$dt00: |${dt00}|"
> >>
> >> ... after some long processing for which
On 12/17/23, to...@tuxteam.de wrote:
> On Sun, Dec 17, 2023 at 10:12:11AM +, Albretch Mueller wrote:
>> dt00=$(date +%Y%m%d%H%M%S)
>> echo "// __ \$dt00: |${dt00}|"
>>
>> ... after some long processing for which seconds would be exact
>> enough, then I would like to get the seconds elapsed
Hello,
On Sun, Dec 17, 2023 at 09:16:49AM -0500, Cindy Sue Causey wrote:
> That points you to an amazingly long list of Debian releases:
>
> https://linuxcollections.com/products/debian/debian.htm
Though if I wanted an image for an old Debian release I'd just
download it from:
On 12/17/23, Andy Smith wrote:
> On Sun, Dec 17, 2023 at 06:10:49AM -0500, Timothy M Butterworth wrote:
>> On Sat, Dec 16, 2023 at 7:45 PM Tixy wrote:
>> > Just announced today [1] it looks like Debian will drop i386 installs
>> > for the next release.
>> >
>> > [1]
>> >
On Sun, Dec 17, 2023 at 10:12:11AM +, Albretch Mueller wrote:
> ... after some long processing for which seconds would be exact
> enough, then I would like to get the seconds elapsed since dt00
Are you working in bash, or sh? It makes a difference here.
Others have already mentioned using
Hola,
Pues eso... no hay fecha pero cuando el río suena, llega el torrente
:-/
Debian Likely Moving Away From i386 In The Near Future
https://www.phoronix.com/news/Debian-Plans-Cease-i386
Personalmente pienso que ni un plazo de 5-8 años me parecería razonable
para abandonar los 32 bits, lo
Hello,
On Sun, Dec 17, 2023 at 06:10:49AM -0500, Timothy M Butterworth wrote:
> On Sat, Dec 16, 2023 at 7:45 PM Tixy wrote:
> > Just announced today [1] it looks like Debian will drop i386 installs
> > for the next release.
> >
> > [1]
* 2023-12-17 10:58:28+, Andy Smith wrote:
> On Sun, Dec 17, 2023 at 10:12:11AM +, Albretch Mueller wrote:
>> you get seconds in dt00 and dt02 and then the difference. You can't
>> go: $(( dt02 - dt00 )) because bash Arithmetic is 10-based.
>
> Why don't you just get the time as epoch time
On Sat, Dec 16, 2023 at 7:45 PM Tixy wrote:
> On Thu, 2023-12-14 at 18:19 -0500, Greg Wooledge wrote:
> > https://en.wikipedia.org/wiki/Sandy_Bridge
> >
> > Instruction set x86-64
> > Instructionsx86, x86-64
> >
> > You could run amd64 on this machine. Right now, you have a choice
> >
On Sun, Dec 17, 2023 at 10:58:28AM +, Andy Smith wrote:
[...]
> ¹ Pedants at this point may feel the need to launch launch into a
> sub-thread about how subtracting one epoch time from another doesn't
> always produce an accurate duration. I can't stop you, but it won't
> be news to me.
On Sun, Dec 17, 2023 at 10:12:11AM +, Albretch Mueller wrote:
> dt00=$(date +%Y%m%d%H%M%S)
> echo "// __ \$dt00: |${dt00}|"
>
> ... after some long processing for which seconds would be exact
> enough, then I would like to get the seconds elapsed since dt00, like
> this:
>
> dt02=$(date
Hello,
On Sun, Dec 17, 2023 at 10:12:11AM +, Albretch Mueller wrote:
> dt00=$(date +%Y%m%d%H%M%S)
> echo "// __ \$dt00: |${dt00}|"
>
> ... after some long processing for which seconds would be exact
> enough, then I would like to get the seconds elapsed since dt00, like
> this:
>
>
Hi,
please ignore the previous message
It seems that upgrading from 6-0-1 to 6-0-5 fix the problem (that or
autoremove)
regards,
Laurent
Le dim. 17 déc. 2023 à 10:44, Laurent Debian a
écrit :
> Dear All,
> I am running debian Testing,
> I did two things recently, upgrading the debian and
dt00=$(date +%Y%m%d%H%M%S)
echo "// __ \$dt00: |${dt00}|"
... after some long processing for which seconds would be exact
enough, then I would like to get the seconds elapsed since dt00, like
this:
dt02=$(date +%Y%m%d%H%M%S)
echo "// __ \$dt02: |${dt02}|"
you get seconds in dt00 and dt02 and
34 matches
Mail list logo
