Bug#1093859: release.debian.org: mips64el vs. librsvg needs resolving for trixie

2025-04-11 Thread Sebastian Ramacher
Control: severity -1 serious [Raising the severity to serious so that it appears on our radar.] Dear mips64el porters, On 2025-01-27 20:32:20 +0100, Emilio Pozuelo Monfort wrote: > On 23/01/2025 15:32, Simon McVittie wrote: > > Package: release.debian.org > > Severity: normal > > Tags: trixie >

Processed: Re: Bug#1093859: release.debian.org: mips64el vs. librsvg needs resolving for trixie

2025-04-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1093859 [release.debian.org] release.debian.org: mips64el vs. librsvg needs resolving for trixie Severity set to 'serious' from 'normal' -- 1093859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093859 Debian Bug Tracking System Conta

Bug#1093859: release.debian.org: mips64el vs. librsvg needs resolving for trixie

2025-01-27 Thread Emilio Pozuelo Monfort
Hi, On 23/01/2025 15:32, Simon McVittie wrote: Package: release.debian.org Severity: normal Tags: trixie X-Debbugs-Cc: debian-m...@lists.debian.org, debian-gtk-gn...@lists.debian.org, debian-b...@lists.debian.org The current version of librsvg is not migrating to testing because it FTBFS on mi

Bug#1093859: release.debian.org: mips64el vs. librsvg needs resolving for trixie

2025-01-23 Thread Chris Hofstaedtler
* Simon McVittie [250123 15:33]: > This seems to have been happening for about 6 months (since 2024-08-15), > although until recently it was possible to mitigate it by retrying builds > until they got scheduled on a buildd that happened to be using a buster > kernel. Retrying this for git was sup

Bug#1093859: release.debian.org: mips64el vs. librsvg needs resolving for trixie

2025-01-23 Thread Simon McVittie
Package: release.debian.org Severity: normal Tags: trixie X-Debbugs-Cc: debian-m...@lists.debian.org, debian-gtk-gn...@lists.debian.org, debian-b...@lists.debian.org The current version of librsvg is not migrating to testing because it FTBFS on mips64el. This appears to be caused by a kernel or h