Bug 12790

Summary: "location dump" does not output networks in libloc 0.9.11
Product: Location Database Reporter: Peter Müller <peter.mueller>
Component: liblocAssignee: Michael Tremer <michael.tremer>
Status: CLOSED FIXED QA Contact: Peter Müller <peter.mueller>
Severity: Minor Usability    
Priority: Will only affect a few users    
Version: unspecified   
Hardware: all   
OS: All   

Description Peter Müller 2022-03-04 16:27:06 UTC 
With libloc 0.9.10, dumping the entire database as one big plain text file for whatever reasons worked fine (it is safe to assume this worked albeit we currently ship location 0.9.9, since 0.9.10 was running on location01 until yesterday, working fine):

[root@maverick tmp]# location --version
location 0.9.9
[root@maverick tmp]# location version
Fri, 04 Mar 2022 05:52:50 GMT
[root@maverick tmp]# time location --database database.db dump > dump.txt

real	0m39.690s
user	0m32.142s
sys	0m7.194s
[root@maverick tmp]# wc -l dump.txt 
5124933 dump.txt

However, running the "dump" command with libloc 0.9.11 produces a significantly smaller file:

root@location01:/tmp# location --version
location 0.9.11
root@location01:/tmp# location version
Fri, 04 Mar 2022 05:52:50 GMT
root@location01:/tmp# time location --database database.db dump > dump.txt

real    0m0.628s
user    0m0.568s
sys     0m0.060s
root@location01:/tmp# wc -l dump.txt 
273329 dump.txt

This is because the file lacks all network data objects.

libloc users actually using the database are not affected, as the database itself appears to be generated correctly. The only ones affected by this are people scraping the data from the dumped txt file - therefore, I will write an e-mail to the location mailing list as well.

Kindly have a look at this. It should be easy to reproduce, as far as I am concerned. :-)