From: dickey@invisible-island.net   
      
   On Sun, Feb 22, 2026 at 05:44:02PM +0100, Aurelien Jarno wrote:   
   > Hi,   
   >    
   > On 2026-02-22 11:32, Thomas Dickey wrote:   
   > > On Sun, Feb 22, 2026 at 05:17:07PM +0100, Aurelien Jarno wrote:   
   > > > Source: rcs-blame   
   > > > Version: 1.4+20240206-1   
   > >    
   > > that's old.  I've updated it a couple of times since that point.   
   > >    
   > > 20251006 is "current"   
   >    
   > Hmm, this still seems the newest available version:   
      
   sure - but I'm "upstream",   
   	- not a DD, and   
   	- would need a sponsor to do the work myself.     
       
   > $ rmadison rcs-blame   
   > rcs-blame  | 1.3.1-4.2         | oldoldstable   | source, amd64, arm64,   
   armhf, i386   
   > rcs-blame  | 1.3.1-4.2         | oldstable      | source, amd64, arm64,   
   armel, armhf, i386, mips64el, mipsel, ppc64el, s390x   
   > rcs-blame  | 1.4+20240206-1    | stable         | source, amd64, arm64,   
   armel, armhf, i386, ppc64el, riscv64, s390x   
   > rcs-blame  | 1.4+20240206-1    | testing        | source, amd64, armhf,   
   i386, ppc64el, riscv64, s390x   
   > rcs-blame  | 1.4+20240206-1    | unstable       | source, amd64, armhf,   
   i386, loong64, ppc64el, riscv64, s390x   
   > rcs-blame  | 1.4+20240206-1    | unstable-debug | source   
   > rcs-blame  | 1.4+20240206-1+b1 | testing        | arm64   
   > rcs-blame  | 1.4+20240206-1+b1 | unstable       | arm64   
   >    
   > > > Severity: important   
   > > > Tags: ftbfs upstream   
   > > > Justification: fails to build from source   
   > > > User: debian-glibc@lists.debian.org   
   > > > Usertags: glibc-2.43   
   > > >    
   > > > Dear maintainer(s),   
   > > >    
   > > > rcs-blame fails to build from source with glibc 2.43, currently in   
   > > > experimental. From the build log:   
   > >    
   > > ...but I'm not tracking experimental (it would help if this report started   
   > > from 20251006)   
   >    
   > Where is this packaged?   
   >    
   > > > The full build log is available here [1].   
   > > >    
   > > > The issue is due to ISO C23 declaration of bsearch, memchr, strchr,   
   > > > strpbrk, strrchr, strstr, wcschr, wcspbrk, wcsrchr, wcsstr and wmemchr,   
   > > > which now returns a pointer to a const-qualified type when the input   
   > > > argument is a pointer to a const-qualified type [2].   
   > >    
   > > fwiw, I'd used gcc 15.2.1 in October.   
   >    
   > This is not linked with GCC 15, but rather to a changed introduced in    
   > glibc 2.43 to support this ISO C23 feature.   
      
   I understand (have seen some unnecessary breakage due to this feature)   
      
   --    
   Thomas E. Dickey    
   https://invisible-island.net   
      
   -----BEGIN PGP SIGNATURE-----   
      
   iQGzBAABCgAdFiEEGYgtkt2kxADCLA1WzCr0RyFnvgMFAmmbOkkACgkQzCr0RyFn   
   vgOCMwv7BEQZw4hdCwPE8HiaiSAde1EtAXbnBO1wdqCJ5FBAHVXLRbVso/DlZlCU   
   Xu/xTfKlnNdeVnfowRvz1xbTDipVdVbUKEewZFWriJKtcEacCf+lL06DMDhiKv/g   
   WRx9rnWqold8cevyyub7qQ5uvabpYDKZbrNEm5kI108JPD6se6mBc64sjSiY8pWP   
   oIUx6a9JUF1RBcWC4hgyLyvvRytTXIWKCBD4eUncM3uzN0jMEgkKIQL3Lc9OqLki   
   mc8EQZRhodG84dYnlkpiv5wkO12gqqjfwy7p7szUWOysvKBUTYNhiVBF32KwHdK9   
   Xg3HReh3uYlfYUl6X8xWTCOyaWfEg9gHDSzTezoPOneUD2AgsJZuL9/RdlRWL2yc   
   tzdn6EulvEOYlQiAIbm9taN26N+62yXumFKWHTKwe+0Dnr25e7nO4qf+3xF1Fd9c   
   K0EuZ7tjw8ZodStRslFDFOgaipZ1Ja9C+BtVi6xhGcxL0KjkwhtXM8enqUDkIoBw   
   evBuvYJW   
   =pJTH   
   -----END PGP SIGNATURE-----   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)