Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Sven Joachim]

On 2023-01-08 02:56 +0100, Vincent Lefevre wrote:

> On 2023-01-07 20:05:59 +0100, Sven Joachim wrote:
>> >> If not, you may have been bitten by bug #1019554 in
>> >> anacron which needs manual restore as mentioned in
>> >> https://lists.debian.org/debian-devel-announce/2022/11/msg1.html.
>> >
>> > 2022-07-14 20:57:59 upgrade anacron:amd64 2.3-32 2.3-33
>> > 2022-07-14 20:57:59 status half-configured anacron:amd64 2.3-32
>> > 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-32
>> > 2022-07-14 20:57:59 status half-installed anacron:amd64 2.3-32
>> > 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-33
>> 
>> Note that the anacron bug only makes itself apparent after the upgrade
>> to a later version, since that would run the faulty postrm from 2.3-33.
>
> I track the diffs in etc, and it seems that 2.3-33 and later did
> nothing wrong.

This assumption is incorrect, see #1019554 and siblings.

> Dangling symlinks were removed after the upgrade
> to anacron 2.3-34, but these were *dangling* symlinks, so that
> this should have no effect. See the bug I reported:
>
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993348
>
> Dangling symlinks are bad as they can break other tools
> (e.g. checkrestart, which was the reason I reported this bug).

I do not like dangling symlinks either, however systemd works fine with
them.  Even if the unit is below /usr/lib/systemd/system and the symlink
in /etc points to a file below /lib/systemd/system, systemd still
activates the unit to accommodate system without a merged /usr.

>> What does "systemctl status anacron.service" print?
>
> ○ anacron.service - Run anacron jobs
>  Loaded: loaded (/lib/systemd/system/anacron.service; disabled; preset: 
> enabled)
>  Active: inactive (dead)
>Docs: man:anacron
>  man:anacrontab
>
> And anacron is no longer in the timers (systemctl list-timers).

That is your problem, you need to reenable and restart these units.

# systemctl enable anacron.service anacron.timer
# systemctl start anacron.service anacron.timer

See the d-d-a link I gave in my first reply,
https://lists.debian.org/debian-devel-announce/2022/11/msg1.html.

Cheers,
   Sven

Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Vincent Lefevre]

On 2023-01-07 20:05:59 +0100, Sven Joachim wrote:
> >> If not, you may have been bitten by bug #1019554 in
> >> anacron which needs manual restore as mentioned in
> >> https://lists.debian.org/debian-devel-announce/2022/11/msg1.html.
> >
> > 2022-07-14 20:57:59 upgrade anacron:amd64 2.3-32 2.3-33
> > 2022-07-14 20:57:59 status half-configured anacron:amd64 2.3-32
> > 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-32
> > 2022-07-14 20:57:59 status half-installed anacron:amd64 2.3-32
> > 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-33
> 
> Note that the anacron bug only makes itself apparent after the upgrade
> to a later version, since that would run the faulty postrm from 2.3-33.

I track the diffs in etc, and it seems that 2.3-33 and later did
nothing wrong. Dangling symlinks were removed after the upgrade
to anacron 2.3-34, but these were *dangling* symlinks, so that
this should have no effect. See the bug I reported:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993348

Dangling symlinks are bad as they can break other tools
(e.g. checkrestart, which was the reason I reported this bug).

> > but I get mail from failing cron scripts.
> 
> What does "systemctl status anacron.service" print?

○ anacron.service - Run anacron jobs
 Loaded: loaded (/lib/systemd/system/anacron.service; disabled; preset: 
enabled)
 Active: inactive (dead)
   Docs: man:anacron
 man:anacrontab

And anacron is no longer in the timers (systemctl list-timers).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1028067: Removed package(s) from unstable

[Debian FTP Masters]

Version: 1.3.3-9+rm

Dear submitter,

as the package sleekxmpp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1028067

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Bug#1028067: Removed package(s) from unstable

[Debian FTP Masters]

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python3-sleekxmpp |1.3.3-9 | all
 sleekxmpp |1.3.3-9 | source

--- Reason ---
RoQA; RC-buggy (non-free); orphaned; maintained fork available
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1028...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1028067

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Bug#1028066: marked as done (sleekxmpp: contains non-free fonts)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 23:55:35 +
with message-id 
and subject line Bug#1028067: Removed package(s) from unstable
has caused the Debian Bug report #1028066,
regarding sleekxmpp: contains non-free fonts
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 ow...@bugs.debian.org
immediately.)


-- 
1028066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: sleekxmpp
Version: 1.3.3-9
Severity: serious

sleekxmpp contains two versions of the non-free Museo Slab font: 
https://www.exljbris.com/museoslab.html
Please replace to get rid of them.
--- End Message ---
--- Begin Message ---
Version: 1.3.3-9+rm

Dear submitter,

as the package sleekxmpp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1028067

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

guessnet_0.58_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 16:53:56 -0300
Source: guessnet
Architecture: source
Version: 0.58
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Marcos Talau 
Closes: 984163
Changes:
 guessnet (0.58) unstable; urgency=medium
 .
   * QA upload.
   * Fix FBTFS with GCC-11. Remove dynamic exception specs. (Closes: #984163)
   * debian/control: Add version (>= 1.1-3) to "libwibble-dev".
Checksums-Sha1:
 5e2d77b579b387f4bd7930a4cac5b76593d90a73 1654 guessnet_0.58.dsc
 ed49ab9803585cbdf1177e8b531b8fffe25c3563 150768 guessnet_0.58.tar.xz
 29b4fd3ec4f3e0e4927eb3c480afa79246aea409 6874 guessnet_0.58_source.buildinfo
Checksums-Sha256:
 9b490b9a971bc58c1b81c7c1edda066d1017dd2bc7c118643e61b6fbe762f8ec 1654 
guessnet_0.58.dsc
 6c5ec1b2cacc7064e63a4cb8aab0bee89b8ab94ed7322e5bab8a8efad5135d7b 150768 
guessnet_0.58.tar.xz
 36e628959aa89432fdd9ef2ca42a7d01b322ba0f18374a116db5de69be938846 6874 
guessnet_0.58_source.buildinfo
Files:
 495a7ef6d4446d9386cae9f13bb17989 1654 net optional guessnet_0.58.dsc
 645676c7f3ef34ceeb139686f2cc8f32 150768 net optional guessnet_0.58.tar.xz
 21b00e99d553f13d5829722dd16d9a6a 6874 net optional 
guessnet_0.58_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmO5zkMACgkQ9LqqgNso
ukwU7g//cSFNQ61Xj2kng/KEoqK5QTC9HTNGUn54rbfBMGD7HocK8DIxZ39zXpIq
2zult3kMfd2cZzxGBYq7K+1ibhjdXchHkHB2a6b5Ow/29lYcpw4qY83phUYuzORc
D9Vsj0oJ/FXiYl8KhuKDaR4FTH6NArWb3grSzBH5DBu3oTBK8CwOv3gfw4g47mD3
rE+MIzdH1hCkrQKApZBjlF7NWJ4ofoja7Zkn7hw2cFCtcOhyTLiaX/7PtvxDVoW8
pl9mg3yKpJ5H5wH+wyu78xouelEIfjfhwXH5hIpLuVtCI2O4072TsXbrKc9cDKyy
apHvH2TAjkUv5EcWal15Z1INXdgYxJ/N4Ky1fYEkMSFU56MJMXaNnnSaKQwIDl2U
QZQ12aA/QJJl4+Uso7MnRwAvgnT2VeaGvfT8LyUVnN15HjCiDRwt1p1L2OAKt5PB
nJnVlJ9S/QTsO0W7kWQ4C1LfoFeXIbwVNVtcZPwCtYDZDc/HbgQ0H/a5NYfClFGD
+hmkhKHjzvzdWE3g4QjmQtN/pCmTU47332/xI6bb9kflPXwWmOAecD8+m5tGgZU2
Is889uC0ycUOu8aYQIzdGE1zSULxNhcykoZYoDHumAYSzMC4+F1KkXe6Q2HPKRqX
+SApwXIZVLboQrDmkcRZbdalXwKvCH1xzH7DYFN3ep7+JYFnAZs=
=DV9B
-END PGP SIGNATURE-

Bug#984163: marked as done (guessnet: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 21:09:35 +
with message-id 
and subject line Bug#984163: fixed in guessnet 0.58
has caused the Debian Bug report #984163,
regarding guessnet: ftbfs with GCC-11
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 ow...@bugs.debian.org
immediately.)


-- 
984163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:guessnet
Version: 0.56
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/guessnet_0.56_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking whether byte ordering is bigendian... no
checking whether gcc and cc understand -c and -o together... yes
checking for ranlib... ranlib
checking for flex... no
checking for lex... no
checking for bison... no
checking for byacc... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBWIBBLE... yes
checking for libnet-config... /usr/bin/libnet-config
checking for libnet libraries... found
checking pcap.h usability... yes
checking pcap.h presence... yes
checking for pcap.h... yes
checking for pcap_open_live in -lpcap... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking for pthread_create in -lpthread... yes
checking for iw_scan in -liw... yes
checking for sh... /bin/sh
checking for ifconfig... /sbin/ifconfig
checking for grep... (cached) /bin/grep
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating scripts/Makefile
config.status: creating tests/Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode, 
--disable-silent-rules
touch debian/stamp-autotools
/usr/bin/make -C . 
make[1]: Entering directory '/<>'
/usr/bin/make  all-recursive
make[2]: Entering directory '/<>'
Making all in src
make[3]: Entering directory '/<>/src'
g++ -DHAVE_CONFIG_H -I. -I.. -D_BSD_SOURCE -D__BSD_SOURCE -D__FAVOR_BSD 
-DHAVE_NET_ETHERNET_H  -DSCRIPTDIR=\"/usr/share/guessnet/test\"  -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o nettypes.o 
nettypes.cc
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/string.h:26,
 from nettypes.h:29,
 from nettypes.cc:23:
/usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
In file included from nettypes.cc:23:
nettypes.h:95:43: error: ISO C++17 does not allow dynamic exception 
specifications
   95 | IPAddress(const std::string& st

Processing of guessnet_0.58_source.changes

[Debian FTP Masters]

guessnet_0.58_source.changes uploaded successfully to localhost
along with the files:
  guessnet_0.58.dsc
  guessnet_0.58.tar.xz
  guessnet_0.58_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

libwibble_1.1-3_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 15:20:39 -0300
Source: libwibble
Architecture: source
Version: 1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Marcos Talau 
Closes: 984211
Changes:
 libwibble (1.1-3) unstable; urgency=medium
 .
   * QA upload.
   * debian/patches/ftbfs-gcc11.patch: New. Remove dynamic exception
 specifications (Closes: #984211).
Checksums-Sha1:
 a38a20c81de775657f39f5eefe9bce2d135eb55b 1692 libwibble_1.1-3.dsc
 ecc12b0e31af439ab5564e387b041cd0137cdffb 9072 libwibble_1.1-3.debian.tar.xz
 841949b00108384adc70de064b93f8c3ad175377 7118 libwibble_1.1-3_source.buildinfo
Checksums-Sha256:
 5c47ca7c691ea46fb13019573e2fb0adf0c70a4a2a0988de0c2bc20faf3f7fbc 1692 
libwibble_1.1-3.dsc
 135d9b5b5e6b49fa297224b809838810f66957ae716b2b7a20a9ca5ad09e009c 9072 
libwibble_1.1-3.debian.tar.xz
 a555baabf369680e88a25b9234ed13de74a3e13649ea1649bef3ae15f86e7b6b 7118 
libwibble_1.1-3_source.buildinfo
Files:
 4611acab544b96a69238b93a85aec01f 1692 libdevel optional libwibble_1.1-3.dsc
 0d0ccda9a1fce830be0947508c2df0ca 9072 libdevel optional 
libwibble_1.1-3.debian.tar.xz
 5c09b9c966df2280bf2fad4751c13eda 7118 libdevel optional 
libwibble_1.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmO5ucEACgkQ9LqqgNso
ukyZGA/9HDOLVgZ5W7SOsq4kSYl1TzdiTFWa/R/53Y3kZYnh+t8iYmmMDiKA7eap
J0vQAuq9CQ+IJhmAqo4oWhUTgD0ZpT23HDboD1/WFSY/ptIWrw6FuWEP6gH4w1hE
v6VEY4DrJ3lYdPspC/0dL5+pm3vogCKtmN20fryk6LJJRJ/Uy99hegcMBLvSdpFt
fqlB4nxWDhs99qJ+AG+3TW1q5/+bhHSqNmmM3RsnkHDBY/f3bL9W4Ihb9OMK0Nqj
EWX+5vAIamSjTkiFyGBCSxTpqqIOUC/a5v3ngg7tbe5xYe0YCA8fT8/HKXzvbowZ
XP6IYNZ+uGsFDdhoozzLlpe1DOXL8+m0IAgTetouf2J3KBOtprBDxdnwfgXAwipM
90MtGOUWSWb0HVMiwspfBr1N60E/MfSusvyZKNXUx8iOj6WdIDLVycBbAXCI26eW
ZAD9v83u0r40bFOMptCr9hxxAhZsVY5UU4yVt1JJy/0w2y6D2g4D1/PifyAb8Mm9
5yH0SIsUCsXWZKYuf6JsW2SDZ3dwLaKMXmYztJ1Dxpc0kLo/ZxTIRLrWKoJ1U+zk
yNA2sRX6s47zTiXOnhOvd4skYk1Q3m6281w0/hzETwQl7k4rqyEQeCLKQAHQuYP0
xVf+rwGFeOsb1T0+7K6LR+CCEaxj4tvt6FcmVYwtMzMjMWETEWY=
=gsEU
-END PGP SIGNATURE-

Bug#984211: marked as done (libwibble: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 07 Jan 2023 19:29:23 +
with message-id 
and subject line Bug#984211: fixed in libwibble 1.1-3
has caused the Debian Bug report #984211,
regarding libwibble: ftbfs with GCC-11
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 ow...@bugs.debian.org
immediately.)


-- 
984211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libwibble
Version: 1.1-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libwibble_1.1-2_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
make  -f wibble/CMakeFiles/wibble.dir/build.make 
wibble/CMakeFiles/wibble.dir/build
make[4]: Entering directory '/<>/debian/build'
[  1%] Building CXX object wibble/CMakeFiles/wibble.dir/exception.o
[  2%] Building CXX object wibble/CMakeFiles/wibble.dir/string.o
[  3%] Building CXX object wibble/CMakeFiles/wibble.dir/regexp.o
cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. 
-I/<>/debian/build/wibble/.. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o 
CMakeFiles/wibble.dir/exception.o -c /<>/wibble/exception.cpp
cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. 
-I/<>/debian/build/wibble/.. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o 
CMakeFiles/wibble.dir/string.o -c /<>/wibble/string.cpp
cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. 
-I/<>/debian/build/wibble/.. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o 
CMakeFiles/wibble.dir/regexp.o -c /<>/wibble/regexp.cpp
[  4%] Building CXX object wibble/CMakeFiles/wibble.dir/test.o
cd /<>/debian/build/wibble && /usr/bin/c++ -DHAVE_CONFIG_H -DPOSIX 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/<>/wibble/.. 
-I/<>/debian/build/wibble/.. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o 
CMakeFiles/wibble.dir/test.o -c /<>/wibble/test.cpp
In file included from /<>/wibble/regexp.cpp:21:
/<>/wibble/../wibble/regexp.h:66:77: error: ISO C++17 does not 
allow dynamic exception specifications
   66 | Regexp(const std::string& expr, int match_count = 0, int flags 
= 0) throw (wibble::exception::Regexp);
  | 
^
/<>/wibble/../wibble/regexp.h:69:59: error: ISO C++17 does not 
allow dynamic exception specifications
   69 | bool match(const std::string& str, int flags = 0) throw 
(wibble::exception::Regexp);
  |   ^
/<>/wibble/../wibble/regexp.h:75:41: error: ISO C++17 does not 
allow dynamic exception specifications
   75 | std::string operator[](int idx) throw 
(wibble::except

Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Sven Joachim]

On 2023-01-07 19:48 +0100, Vincent Lefevre wrote:

> On 2023-01-07 19:20:56 +0100, Sven Joachim wrote:
>> On 2023-01-07 18:53 +0100, Vincent Lefevre wrote:
>> > zira:~> ll /var/lib/dlocate
>> > total 109172
>> > -rw-r--r-- 1 root root 55750318 2022-11-25 00:27:44 dlocatedb
>> > -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
>> > -rw-r--r-- 1 root root   105318 2022-11-25 00:27:44 dlocatedb.stamps
>> > -rw-r--r-- 1 root root   299199 2022-11-25 00:27:44 dpkg-list
>
> Same issue my other machine.
>
>> That could have been the case for much longer actually.  At installation
>> time, the postinst script runs "update-dlocatedb -b" which seems to have
>> been successful.
>
> I suppose that explains the
>
>> > -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
>
>> > The cron file /etc/cron.daily/dlocate is there, though:
>> >
>> > #!/bin/sh
>> >
>> > # update databases for both files and packages.
>> > if [ -x /usr/sbin/update-dlocatedb ] ; then
>> >   /usr/sbin/update-dlocatedb -b
>> > fi
>>
>> But apparently it is never executed.  Are any other cron jobs being run
>> on your system?
>
> In the logs I can see for today:
>
> Jan 07 06:25:01 zira CRON[1843444]: (root) CMD (test -x
> /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
>
> and
>
> Jan 07 14:38:01 zira CRON[1857920]: (root) CMD ( test -x
> /etc/cron.daily/popularity-contest &&
> /etc/cron.daily/popularity-contest --crond)
>
> So it seems to be OK, though I don't know what leads to the logging
> of popularity-contest only.

Most likely the script /etc/cron.d/popularity-contest, I get the same
messages.

>> If not, you may have been bitten by bug #1019554 in
>> anacron which needs manual restore as mentioned in
>> https://lists.debian.org/debian-devel-announce/2022/11/msg1.html.
>
> 2022-07-14 20:57:59 upgrade anacron:amd64 2.3-32 2.3-33
> 2022-07-14 20:57:59 status half-configured anacron:amd64 2.3-32
> 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-32
> 2022-07-14 20:57:59 status half-installed anacron:amd64 2.3-32
> 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-33

Note that the anacron bug only makes itself apparent after the upgrade
to a later version, since that would run the faulty postrm from 2.3-33.

> but I get mail from failing cron scripts.

What does "systemctl status anacron.service" print?

Cheers,
   Sven

Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Vincent Lefevre]

On 2023-01-07 19:48:17 +0100, Vincent Lefevre wrote:
> In the logs I can see for today:
> 
> Jan 07 06:25:01 zira CRON[1843444]: (root) CMD (test -x /usr/sbin/anacron || 
> { cd / && run-parts --report /etc/cron.daily; })
> 
> and
> 
> Jan 07 14:38:01 zira CRON[1857920]: (root) CMD (   test -x 
> /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
> --crond)
> 
> So it seems to be OK, though I don't know what leads to the logging
> of popularity-contest only.

This is actually because of /etc/cron.d.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processing of libwibble_1.1-3_source.changes

[Debian FTP Masters]

libwibble_1.1-3_source.changes uploaded successfully to localhost
along with the files:
  libwibble_1.1-3.dsc
  libwibble_1.1-3.debian.tar.xz
  libwibble_1.1-3_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Vincent Lefevre]

On 2023-01-07 19:20:56 +0100, Sven Joachim wrote:
> On 2023-01-07 18:53 +0100, Vincent Lefevre wrote:
> > zira:~> ll /var/lib/dlocate
> > total 109172
> > -rw-r--r-- 1 root root 55750318 2022-11-25 00:27:44 dlocatedb
> > -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
> > -rw-r--r-- 1 root root   105318 2022-11-25 00:27:44 dlocatedb.stamps
> > -rw-r--r-- 1 root root   299199 2022-11-25 00:27:44 dpkg-list

Same issue my other machine.

> That could have been the case for much longer actually.  At installation
> time, the postinst script runs "update-dlocatedb -b" which seems to have
> been successful.

I suppose that explains the

> > -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old

> > The cron file /etc/cron.daily/dlocate is there, though:
> >
> > #!/bin/sh
> >
> > # update databases for both files and packages.
> > if [ -x /usr/sbin/update-dlocatedb ] ; then
> >   /usr/sbin/update-dlocatedb -b
> > fi
> 
> But apparently it is never executed.  Are any other cron jobs being run
> on your system?

In the logs I can see for today:

Jan 07 06:25:01 zira CRON[1843444]: (root) CMD (test -x /usr/sbin/anacron || { 
cd / && run-parts --report /etc/cron.daily; })

and

Jan 07 14:38:01 zira CRON[1857920]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)

So it seems to be OK, though I don't know what leads to the logging
of popularity-contest only.

> If not, you may have been bitten by bug #1019554 in
> anacron which needs manual restore as mentioned in
> https://lists.debian.org/debian-devel-announce/2022/11/msg1.html.

2022-07-14 20:57:59 upgrade anacron:amd64 2.3-32 2.3-33
2022-07-14 20:57:59 status half-configured anacron:amd64 2.3-32
2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-32
2022-07-14 20:57:59 status half-installed anacron:amd64 2.3-32
2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-33

but I get mail from failing cron scripts.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Sven Joachim]

On 2023-01-07 18:53 +0100, Vincent Lefevre wrote:

> Package: dlocate
> Version: 1.12
> Severity: grave
> Justification: renders package unusable
>
> dlocate cannot find recent files, so it is mostly useless.
>
> I suspect that since the upgrade to dlocate 1.12 on 2022-11-25,
> its database is no longer updated:
>
> zira:~> ll /var/lib/dlocate
> total 109172
> -rw-r--r-- 1 root root 55750318 2022-11-25 00:27:44 dlocatedb
> -rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
> -rw-r--r-- 1 root root   105318 2022-11-25 00:27:44 dlocatedb.stamps
> -rw-r--r-- 1 root root   299199 2022-11-25 00:27:44 dpkg-list

That could have been the case for much longer actually.  At installation
time, the postinst script runs "update-dlocatedb -b" which seems to have
been successful.

> The cron file /etc/cron.daily/dlocate is there, though:
>
> #!/bin/sh
>
> # update databases for both files and packages.
> if [ -x /usr/sbin/update-dlocatedb ] ; then
>   /usr/sbin/update-dlocatedb -b
> fi

But apparently it is never executed.  Are any other cron jobs being run
on your system?  If not, you may have been bitten by bug #1019554 in
anacron which needs manual restore as mentioned in
https://lists.debian.org/debian-devel-announce/2022/11/msg1.html.

Cheers,
   Sven

libapache2-mod-lisp_1.3.1-2_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Jan 2023 13:50:33 -0300
Source: libapache2-mod-lisp
Architecture: source
Version: 1.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Marcos Talau 
Closes: 965624 999213
Changes:
 libapache2-mod-lisp (1.3.1-2) unstable; urgency=medium
 .
   * QA upload.
   * Convert package to source format 3.0 (quilt). Consequently:
 - debian/source/format: New.
 - debian/patches/:
   ~ apache2.4-fixes.patch: Rename to "02_apache2.4-fixes.patch".
   ~ 01_APR_FTBS.patch: New. Patch extracted from "diff.gz"
   ~ 03_create_makefile.patch: New. Patch extracted from "diff.gz".
   ~ 04_create_modulesmk.patch: New. Patch extracted from "diff.gz".
   * Set maintainer to Debian QA Group . (see: #829682)
   * Using new DH level format. Consequently:
 - debian/compat: Remove.
 - debian/control: Change from 'debhelper' to 'debhelper-compat' in
   Build-Depends field and bump level to 13.
 - Closes: #965624.
   * debian/control:
 - Add Vcs-* fields.
 - Change Section from devel to httpd.
   * debian/libapache2-mod-lisp.debhelper.log: Remove. No longer need.
   * debian/libapache2-mod-lisp.preinst: Remove. No longer need.
   * debian/rules: Completely rewritten (Closes: #999213).
   * debian/salsa-ci.yml: Add to provide CI tests for Salsa.
   * debian/tests/*: Create autopkgtest.
Checksums-Sha1:
 6df3d4b862aef32bd03caa24580afc2397b9af15 1993 libapache2-mod-lisp_1.3.1-2.dsc
 84b006a73f6e2be5fad24e939f2294fc620c5509 5232 
libapache2-mod-lisp_1.3.1-2.debian.tar.xz
 31b54aa0851ffd48a78bda380ceba40b4e7841fa 7597 
libapache2-mod-lisp_1.3.1-2_source.buildinfo
Checksums-Sha256:
 044eaaa7dadf1c5d3828ec2f24b985e86b3d242fd5f4e0d5c0d291e6e2ea2d04 1993 
libapache2-mod-lisp_1.3.1-2.dsc
 6f9632236c208aeb8c8283089950156e05bfea53522745aa35fb6c9dd6e1a6fa 5232 
libapache2-mod-lisp_1.3.1-2.debian.tar.xz
 18a0af0d50ec5316b8a97edd488d2302f15a73512e7ce828c1c2f8719dd779ad 7597 
libapache2-mod-lisp_1.3.1-2_source.buildinfo
Files:
 cf649ee9f0cc5a15de706df95ed3dd4b 1993 httpd optional 
libapache2-mod-lisp_1.3.1-2.dsc
 2f455a0cd9cfc02c6799f6e8b820490d 5232 httpd optional 
libapache2-mod-lisp_1.3.1-2.debian.tar.xz
 247966ede4abcd4780694d3c7904aba9 7597 httpd optional 
libapache2-mod-lisp_1.3.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmO5o64ACgkQ9LqqgNso
ukwUtg//TyWEJZzzLK+IHBxH6BNNyfHAWMZhPHgVUNVftilL/dqyJDhwqxH2tvqz
dRg1HDatxeGM+DWmOy8uxj9oEafIm1bFhAQJik2/l0TouW8Zd1qE6fa3X+XhPtCS
YdhDS+Q79SF6dAf3Isma0621CwDYfFo9TV9NKu50qUw7YHD+LxIOApmLfqxq5be/
Yz3YaSYGPcgEYWCgyfQ8bzg0PQVyeprLuUuD+rhrbsRFLn5JnKI/fhf+6utNXFen
hkJd8q6xURrX4w0aP71CIX9OSf/bBXome4jHKV5lZ1N58ZmGAt75ZXS6oVNfyLZp
I1RMVKH794+fttbPIIuIC0VAmo+RKpGt3SAy+U/HLlP1r99VtsNNgUI3nZZZuywD
gGbyvNFZkDReHUToaRFizHkpHPl74Sr2h1JWKXjqd2AMvqp87+BOa8SXWM/cZv/C
j4lyvPLJERNEf7YVHYBce+Pt5mHg2FPj0OgYFi2elHKlAJvUYTsTRmPAzYlf5zw+
lSb/PoUDlugQAfujbuRR2Pa7B59/KTkdsxXn1uEa17tP8tn3T6WyiD2Jb5QnDL9e
9buB08/90H/myqivN/sfX7cmgF35AsS85l4OSMBqFQ4MOQFga5vbRDB7i7hrUG4G
wrwglsiEgGtIszem1wFD54KOmBis0rRM4GDZL/i1Ie9dA7WevvI=
=4X4b
-END PGP SIGNATURE-

Bug#1028142: dlocate: cannot find recent files - obsolete database?

[Vincent Lefevre]

Package: dlocate
Version: 1.12
Severity: grave
Justification: renders package unusable

dlocate cannot find recent files, so it is mostly useless.

I suspect that since the upgrade to dlocate 1.12 on 2022-11-25,
its database is no longer updated:

zira:~> ll /var/lib/dlocate
total 109172
-rw-r--r-- 1 root root 55750318 2022-11-25 00:27:44 dlocatedb
-rw-r--r-- 1 root root 55623054 2022-11-14 09:47:51 dlocatedb.old
-rw-r--r-- 1 root root   105318 2022-11-25 00:27:44 dlocatedb.stamps
-rw-r--r-- 1 root root   299199 2022-11-25 00:27:44 dpkg-list

The changelog doesn't mention any change:

dlocate (1.12) unstable; urgency=medium

  * QA upload.
  * Convert to 3.0 source format. Closes: #1007667

 -- Bastian Germann   Thu, 24 Nov 2022 00:10:50 +0100

The cron file /etc/cron.daily/dlocate is there, though:

#!/bin/sh

# update databases for both files and packages.
if [ -x /usr/sbin/update-dlocatedb ] ; then
  /usr/sbin/update-dlocatedb -b
fi

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dlocate depends on:
ii  dctrl-tools [grep-dctrl]  2.24-3+b1
ii  dpkg  1.21.17
ii  perl  5.36.0-6

Versions of packages dlocate recommends:
ii  supercat  0.5.7-1

dlocate suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processing of libapache2-mod-lisp_1.3.1-2_source.changes

[Debian FTP Masters]

libapache2-mod-lisp_1.3.1-2_source.changes uploaded successfully to localhost
along with the files:
  libapache2-mod-lisp_1.3.1-2.dsc
  libapache2-mod-lisp_1.3.1-2.debian.tar.xz
  libapache2-mod-lisp_1.3.1-2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)