Your message dated Fri, 9 Jun 2023 10:44:44 +0200 with message-id <[email protected]> and subject line Fixed in 1.1.19 has caused the Debian Bug report #1027702, regarding plocate: "Try `ulimit -n 262144' or similar (current limit is 0)." to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1027702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027702 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: plocate Version: 1.1.17-2 I saw this in an error message sent by cron: Hint: Try `ulimit -n 262144' or similar (current limit is 0). The number in parentheses in wrong of course. This is likely related to these compiler warnings: ../updatedb.cpp:710:81: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘rlim_t’ {aka ‘long long unsigned int’} [-Wformat=] ../updatedb.cpp:710:115: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘rlim_t’ {aka ‘long long unsigned int’} [-Wformat=] https://buildd.debian.org/status/fetch.php?pkg=plocate&arch=i386&ver=1.1.17-2&stamp=1669458499&raw=0 -- System Information: Architecture: i386 Versions of packages plocate depends on: ii libc6 2.36-7 ii libgcc-s1 12.2.0-11 ii libstdc++6 12.2.0-11 ii liburing2 2.3-2 ii libzstd1 1.5.2+dfsg2-3 ii adduser 3.130 -- Jakub Wilk
--- End Message ---
--- Begin Message ---Version: 1.1.19-1 Forgot to mark these in the changelog, so closing them manually. /* Steinar */ -- Homepage: https://www.sesse.net/
--- End Message ---
