Bug#863710: journald's most recent entries

2017-07-08 Thread defanor
Apparently it's fine with v232, wasn't able to reproduce on Debian 9.

Bug#866393: foxtrotgps: Missing info directory entry

2017-06-29 Thread defanor
Package: foxtrotgps Version: 1.2.0-1+b2 Severity: minor Dear Maintainer, Once installed from Debian repositories, there's no FoxtrotGPS entry in the default info directories, though the info manual is present and can be accessed (checked with the regular `info` viewer, as well as with the emacs i

Bug#863710: journald's most recent entries

2017-06-04 Thread defanor
> There were lots of changes regarding the journal between v215 and v232 > (which is the version in the upcoming stretch release). > > Would be great if you can try and reproduce the problem with that > version. If it still happens, this should be taken upstream. I've reproduced it with a shell sc

Bug#863710: journald's most recent entries

2017-06-01 Thread defanor
With the direction being reversed in the test program (i.e., using sd_journal_seek_head, sd_journal_next_skip, sd_journal_previous), it works fine (as does journalctl with no -n option). With `journalctl OBJECT_ID=50482 -r`, journalctl only prints those "" messages (as did the first version of the

Bug#863710: journald's most recent entries

2017-06-01 Thread defanor
Reproduced the journalctl behaviour by using sd_journal_previous_skip and sd_journal_next. Apparently it skips some entries when goes backward (from the newest to the oldest entries), but not when goes forward.

Bug#863710: journald's most recent entries

2017-06-01 Thread defanor
Tried to debug it a bit more, with the attached test program. It has printed the first message from each 4-hour chunk of messages (mentioned as "" in the original report), but nothing else -- though there are others that match ("" and so on), including the ones written by the same process as those

Bug#863710: journald's most recent entries

2017-05-30 Thread defanor
> I don't quite see the issue here. Can you please elaborate? Note the timestamps. In the first example, the last entry was from May 29 23:05:13 when the last 14 entries were requested, but from May 30 07:05:03 when the last 12 were. The expected behaviour is that the last entry is always the same

Bug#863710: journald's most recent entries

2017-05-30 Thread defanor
Package: systemd Version: 215-17+deb8u6 Severity: normal Dear Maintainer, I have tried to retrieve recent journal entries (with matching fields), but the retrieved entries were not the most recent ones: $ journalctl OBJECT_ID=50483 -n 15 | tail -n 1 | cut -c 1-15 May 29 23:05:13 $ journalctl OBJ