Control: severity -1 normal
On Tue, 14 May 2024 at 18:41:01 +0100, Simon McVittie wrote:
> On Tue, 14 May 2024 at 17:12:29 +0100, Simon McVittie wrote:
> > I'm testing a patch to make g-ir-scanner explicitly disable
> > -Wl,--as-needed, so that the SONAMEs can be ext
On Tue, 14 May 2024 at 17:12:29 +0100, Simon McVittie wrote:
> I'm testing a patch to make g-ir-scanner explicitly disable
> -Wl,--as-needed, so that the SONAMEs can be extracted reliably.
This successfully mitigates the libkkc issue, and we need it anyway for
ibus-anthy. After upl
Control: tag -1 pending
Hello,
Bug #1060953 in gobject-introspection reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1060951 in gobject-introspection reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: reassign -1 src:gobject-introspection 1.78.1-17
Control: affects -1 src:ibus-anthy
This looks like almost the same situation as #1060951, except that
in #1060951, I think libkkc is probably using g-ir-scanner incorrectly
(cloned as #1071116), whereas in #1060953 I don't see anything that
Control: clone -1 -2
Control: retitle -1 gobject-introspection: multiarch g-ir-scanner doesn't find
recursive library dependencies
Control: retitle -2 libkkc: likely shouldn't add recursive dependencies to
Marisa_gir_SCANNERFLAGS
Control: reassign -2 libkkc 0.3.5-8
Control: tags -2 + upstream
On Wed, 08 May 2024 at 03:48:21 +, unfathomabl...@protonmail.com wrote:
> Latest upgrade from 2.74.6-2 to 2.74.6-2+deb12u1 broke input of Japanese
> characters GTK programs (such as firefox, gedit etc).
For users of testing/unstable, this will be fixed as soon as I can,
probably by version
Control: tag -1 pending
Hello,
Bug #1070745 in glib2.0 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1070745 in glib2.0 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: reassign -1 libglib2.0-0 2.74.6-2+deb12u1
Control: affects -1 + gnome-shell
On Wed, 08 May 2024 at 11:42:10 +0200, pham...@bluewin.ch wrote:
> After today's update, the dead keys on my keyboard no longer work
This is a regression in GLib triggered by fixing CVE-2024-34397. I'm
testing a
Control: severity 1070706 normal
Control: severity 1070714 normal
On Tue, 07 May 2024 at 22:53:33 +0200, Cyril Brulebois wrote:
> Simon McVittie (2024-05-07):
> > do the release/installer teams consider udeb dependencies
> > on non-udeb packages, by udebs that d-i does not curren
On Tue, 07 May 2024 at 22:02:12 +0200, Paul Gevers wrote:
> On 07-05-2024 7:49 p.m., Simon McVittie wrote:
> > The version in testing, 4.12.5+ds-3, has the same dependencies, so this
> > is not a regression.
>
> Is it? It seems that the version in unstable depends on libpng
Control: tags -1 + d-i
Control: found -1 4.12.5+ds-3
Control: retitle -1 gtk4 udeb has unsatisfiable dependencies
Control: clone -1 -2
Control: retitle -2 libvte-2.91-0-udeb depends on both GTK 3 and GTK 4
Control: reassign -2 src:vte2.91 0.75.92-1
On Tue, 07 May 2024 at 15:44:02 +0100, Peter
.
Closes: #1070016
Signed-off-by: Simon McVittie
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1070016
On Mon, 29 Apr 2024 at 17:12:05 +0200, Sebastian Ramacher wrote:
> It will also help dak to decruft the pre-t64 from unstable and render
> game-data-packages as good on the transition trackers.
OK. Would it be OK to make these dependencies be of the form
"libasound2t64 | libasound2" and so on, or
On Sun, 28 Apr 2024 at 17:27:21 +0200, Sebastian Ramacher wrote:
> quake4 has hard-coded dependencies on shared libraries (at least
> libasound2) that were renamed as part of the t64 transition. Please
> update the dependencies accordingly.
quake4 is i386-only, and i386 has Provides for the old
Control: retitle -1 python-icalendar: FTBFS with tzdata 2024a:
UnknownTimeZoneError: 'America/Godthab'
On Thu, 25 Apr 2024 at 18:27:15 +0200, Santiago Vila wrote:
> E pytz.exceptions.UnknownTimeZoneError: 'America/Godthab'
This was presumably triggered by this change in tzdata
Control: retitle -1 ruby-curb: test regression with curl 8.7.1: client read
function EOF fail, only only 4/5 of needed bytes read
User: debian...@lists.debian.org
Usertags: breaks needs-update
On Thu, 18 Apr 2024 at 22:42:11 +0200, Sebastian Ramacher wrote:
> Error:
Control: retitle -1 nautilus: FTBFS on arm64:
test-nautilus-search-engine-tracker timed out
(cc'ing Lucas in case whatever heuristics are parsing the log can be
improved)
On Sat, 20 Apr 2024 at 14:09:18 +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > (tracker-miner-fs-3:3061640):
Control: retitle -1 libgweather4: FTBFS on arm64: Location 'Greenland' has
invalid timezone 'America/Godthab'
On Sat, 20 Apr 2024 at 14:06:28 +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > # GLib-GIO-DEBUG: Failed to initialize portal (GNetworkMonitorPortal) for
> >
Control: tag -1 pending
Hello,
Bug #1067677 in clutter-gst-3.0 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Source: plank
Version: 0.11.89-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Thanks for trying to address #1067764, but unfortunately the version that
was uploaded fails to build on all of the per-architecture buildds:
>
Source: clutter-gst-3.0
Version: 3.0.27-3
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1
The build-dependency on libglib2.0-0 is no longer satisfiable in unstable
due to the 64-bit time_t
Source: gpick
Version: 0.2.6-1
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1
gpick Build-Depends on:
debhelper-compat (= 13),
cmake,
libcairo2 (>=1.6),<---
On Sun, 24 Mar 2024 at 23:06:18 +0500, Andrey Rakhmatullin wrote:
> GLX/input_device_linuxevent.cpp: In member function ‘virtual void
> CL_InputDevice_LinuxEvent::keep_alive()’:
> GLX/input_device_linuxevent.cpp:269:72: error: ‘struct input_event’ has no
> member named ‘time’
> 269 |
>
Package: debhelper
Version: 13.15
Severity: grave
Justification: renders package unusable
Control: block 1036884 by -1
debhelper 13.14.1 has:
Depends: autotools-dev, dh-autoreconf (>= 17~), dh-strip-nondeterminism (>=
0.028~), dpkg (>= 1.18.0~), dpkg-dev (>= 1.18.2~), dwz (>= 0.12.20190711),
Control: retitle -1 pulseaudio: FTBFS on x86: cpu-volume-test fails, segfault
in svolume_orc_test
Control: reassign -1 src:orc 1:0.4.38-1
Control: forwarded -1 https://gitlab.freedesktop.org/gstreamer/orc/-/issues/66
Control: tags 1067458 + ftbfs sid trixie
Control: merge 1067458 -1
Control:
Control: tags -1 + moreinfo
On Thu, 21 Mar 2024 at 15:00:52 +0100, Christian Marillat wrote:
> I noticed this bug with the libopenshot-audio source and with
> armel, armh and powerpc architectures from buildd logs and my rebuild.
>
> I didn't pay attention for others sources, but I noticed that
On Wed, 20 Mar 2024 at 20:00:32 +, Thorsten Glaser wrote:
> Unfortunately, as with umockdev, I have no idea what is going on
> here… does it #undef _FILE_OFFSET_BITS or something?
Yes it does. padsp(1) is based on a LD_PRELOAD module similar to those
used in fakeroot, fakechroot, umockdev and
On Thu, 21 Mar 2024 at 14:13:38 +0500, Andrey Rakhmatullin wrote:
> On Wed, Mar 20, 2024 at 03:05:34AM +, Thorsten Glaser wrote:
> > cc -Ilibumockdev-preload.so.0.0.0.p -I. -I.. -fdiagnostics-color=always
> > -Wall -Winvalid-pch -std=gnu11 -Werror=missing-prototypes
> >
On Thu, 21 Mar 2024 at 15:45:13 +0500, Andrey Rakhmatullin wrote:
> On Wed, Mar 13, 2024 at 08:23:07AM +0100, Helge Deller wrote:
> > The patch below builds for me on the hppa platform.
> Unfortunately tests fail here with it in an armhf chroot, I don't know if
> it's generic or because the chroot
Control: retitle -1 gstreamer1.0: FTBFS: tests/check/libs/gstharness.c:
Received signal 11 (Segmentation fault)
On Wed, 13 Mar 2024 at 16:11:03 +0100, Lucas Nussbaum wrote:
> gstreamer1.0: FTBFS: gst-validate-1.0 Failed to execute child process
> ?gst-validate-1.0? (No such file or directory)
On Tue, 19 Mar 2024 at 22:55:31 +0100, Matthias Klumpp wrote:
> Am Di., 19. März 2024 um 22:25 Uhr schrieb Simon McVittie :
> > Yes, the library is renamed on all architectures. (On architectures where
> > the ABI didn't actually break, like amd64, it Provides the old name.)
>
On Tue, 19 Mar 2024 at 22:14:12 +0100, Matthias Klumpp wrote:
> Am Di., 19. März 2024 um 21:42 Uhr schrieb Simon McVittie :
> > libgtkd-3-0 has a hard-coded dependency on libgtk-3-0, which will need
> > to be replaced by libgtk-3-0t64 after checking that the functions that
> >
Package: meld
Version: 3.22.1-1
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1
meld is an Architecture: all package, but has a direct dependency on
libgtk-3-0, as well as an indirect dependency
Source: gtk-d
Version: 3.10.0-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1
libgtkd-3-0 has a hard-coded dependency on libgtk-3-0, which will need
to be replaced by libgtk-3-0t64 after
Package: gnome-subtitles
Version: 1.8-1
Severity: serious
Justification: 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
gnome-subtitles has a hard-coded dependency on libgtk-3-0, which needs to
be replaced with libgtk-3-0t64 as part of the 64-bit time_t transition.
Package: timekpr-next
Version: 0.5.4-1
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1
timekpr-next is an Architecture: all package, but has a direct dependency
on libgtk-3-0, as well as an
Package: syncthing-gtk
Version: 0.9.4.4+ds+git20221205+12a9702d29ab-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1
syncthing-gtk is an Architecture: all package, but has a direct dependency
on
Package: exaile
Version: 4.1.3+dfsg-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1
exaile is an Architecture: all package, but has a direct dependency on
libgtk-3-0, as well as an indirect
Package: cpupower-gui
Version: 0.7.2-2.1
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
cpupower-gui is an Architecture: all package, but has a direct dependency
on libgtk-3-0, as well as an indirect dependency on
Package: clearlooks-phenix-theme
Version: 7.0.1-3
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
clearlooks-phenix-theme is an Architecture: all package, but has a
direct (versioned) dependency on libgtk-3-0.
On the
Package: bleachbit
Version: 4.6.0-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1
bleachbit is an Architecture: all package, but has a direct dependency on
libgtk-3-0, as well as an indirect
Package: 0install
Version: 2.18-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1
Versions of 0install that have been rebuilt for the 64-bit time_t
transition (for example on amd64) have
Control: tag -1 pending
Hello,
Bug #1066032 in gobject-introspection reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1066032 in gobject-introspection reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Mon, 18 Mar 2024 at 09:12:36 +0100, Sebastian Ramacher wrote:
> arm-linux-gnueabihf-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
> -Werror=implicit-function-declaration -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2
>
Control: tag -1 pending
Hello,
Bug #1061703 in gnome-characters reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tags -1 + moreinfo help
Control: severity -1 important
On Sun, 21 Jan 2024 at 13:17:45 +, Simon McVittie wrote:
> On Tue, 16 Jan 2024 at 20:37:49 +0100, Lucas Nussbaum wrote:
> > > 26/28 xdg-desktop-portal:pytest / pytest test_inputcaptureFAIL
> > &
Package: libruby
Version: 1:3.1
Severity: serious
Justification: blocker for 64-bit time_t transition
X-Debbugs-Cc: z...@debian.org, debian-...@lists.debian.org
Control: affects -1 + src:graphviz src:vala
Now that libruby3.1t64 has reached unstable, libruby is uninstallable on
the architectures
#1066821.
smcv
>From e36a8c4784278ccfb32d112b57cd2260fedb2e3c Mon Sep 17 00:00:00 2001
From: Simon McVittie
Date: Sun, 17 Mar 2024 13:21:29 +
Subject: [PATCH 2/3] d/libaprutil1t64.symbols: Fix name of t64 binary package
It's libaprutil1t64 (with the "t"), not libaprutil164.
Close
Control: tag -1 pending
Hello,
Bug #1066306 in gmpc-plugins reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1066611 in gmpc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1066904 in glib2.0 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1066900 in gobject-introspection reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: clone -1 -2
Control: retitle -2 gi-compile-repository: generates incorrect typelib when
cross-compiling with different type sizes
Control: reassign -2 libglib2.0-dev 2.79.3-1
Control: tags -2 = experimental
On Fri, 15 Mar 2024 at 07:48:17 +, Simon McVittie wrote:
> When it conve
Package: gobject-introspection
Version: 1.78.1-16
Severity: serious
Justification: results in misbuilt packages
X-Debbugs-Cc: debian-cr...@lists.debian.org
When it converts GIR XML to binary typelib files, g-ir-compiler replaces
abstract types such as int and gsize (size_t) with concrete types
On Sun, 25 Feb 2024 at 20:36:58 +0100, Lucas Nussbaum wrote:
> > FAIL: test_black (devscripts.test.test_black.BlackTestCase.test_black)
> > Test: Run black code formatter on Python source code.
I think lint checks like this one should be run by contributors and CI
when targeting the main branch,
On Mon, 11 Mar 2024 at 08:13:30 -0400, Jeremy Bícha wrote:
> Although Debian has not yet gotten to pygobject in the time_t
> transition for armel/armhf, Ubuntu has and experienced a build test
> failure in test_gi.py for the test_time_t tests which I believe are
> using functions in glib2.0. I
On Sat, 09 Mar 2024 at 12:29:26 +0100, Sebastian Ramacher wrote:
> linux_input.c: In function ‘translate_event’:
> linux_input.c:761:28: error: ‘const struct input_event’ has no member named
> ‘time’
> 761 | devt->timestamp = levt->time;
> |^~
This seems
Control: retitle -1 librsvg: reftest regression for rtl-tspan with pango1.0
1.52.1: 2655 pixels differ from reference
Control: severity -1 important
On Sun, 10 Mar 2024 at 14:45:24 +, Simon McVittie wrote:
> For now, I'm testing an upload that will temporarily disable this test,
>
Control: tags -1 + pending
On Sun, 10 Mar 2024 at 14:03:18 +, Simon McVittie wrote:
> On Sun, 10 Mar 2024 at 13:12:57 +0100, Sebastian Ramacher wrote:
> > rtl-tspan: 2655 pixels changed with maximum difference of 112
>
> This appears to have been caused by upgrading pango
On Sun, 10 Mar 2024 at 13:12:57 +0100, Sebastian Ramacher wrote:
> rtl-tspan: 2655 pixels changed with maximum difference of 112
This appears to have been caused by upgrading pango1.0 from 1.52.0
to 1.52.1. The librsvg test suite is unfortunately very sensitive to
differences in the exact version
Control: block 1036884 by -1
On Sun, 10 Mar 2024 at 10:37:51 +0100, Aurelien Jarno wrote:
> weston fails to build in unstable since the upload of neatvnc in version
> 8.0. From my build log on amd64:
...
> | Dependency neatvnc found: NO found 0.8.0 but need: '< 0.8.0' ; matched: '>=
> 0.7.0'
object
On Sun, 04 Feb 2024 at 12:31:35 +, Simon McVittie wrote:
> When I try the command above, on GNOME in Wayland mode, I get what
> appears to be a different crash
Now reported separately as #1065709, which I now see was a duplicate
of #1057620 (I'll merge them).
> which makes
Control: reassign -1 aptitude,libgtk2.0-0t64
Control: tags -1 + moreinfo
On Thu, 07 Mar 2024 at 16:10:17 +0100, Vincent Lefevre wrote:
> During an upgrade with aptitude:
>
> dpkg: dependency problems prevent removal of libgtk2.0-common:
> libgtk2.0-bin depends on libgtk2.0-common.
>
Control: tag -1 pending
Hello,
Bug #1065494 in gtk+3.0 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1065493 in gtk+2.0 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: severity -1 important
On Tue, 20 Feb 2024 at 23:15:09 +0100, Matthias Klose wrote:
> On 20.02.24 22:50, Simon McVittie wrote:
> > If gobject-introspection explicitly depended on gobject-introspection-bin
> > by name (not just via a virtual package), would that hel
Control: tag -1 pending
Hello,
Bug #1065022 in glib2.0 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tags -1 + pending
On Sat, 02 Mar 2024 at 11:51:26 +0100, Sebastian Ramacher wrote:
> Please add dpkg-dev (>= 1.22.5) to Build-Depends
This is already fixed in git, but we were told not to upload that version
yet, to avoid interfering with the migration of the NMU currently
in unstable
On Thu, 29 Feb 2024 at 14:00:02 +0100, Christoph Anton Mitterer wrote:
> So the advise for "end users" is to simply re-install one package of
> both groups and everything should be cleaned up again?
The advice for "end users" would be don't run unstable or experimental,
and wait for maintainers
On Thu, 29 Feb 2024 at 08:40:28 -0300, Leandro Cunha wrote:
> Jeremy uploaded glib 2.0 to experimental which fixes such problems
libglib2.0-0t64 in experimental does not contain any changes that would
intentionally fix this.
Upgrading to the experimental libglib2.0-0t64 probably fixes this as a
On Thu, 29 Feb 2024 at 10:33:17 +, Simon McVittie wrote:
> Yes, the workaround for this is to reinstall any package that carries
> GSettings schemas. gsettings-desktop-schemas is a common one, but actually
> any package that has files in /usr/share/glib-2.0/schemas/ should be
>
Control: retitle -1 libglib2.0-0t64: transition from libglib2.0-0 breaks
GSettings, GIO modules
Ash Joubert wrote:
> Workaround for me was to reinstall gsettings-desktop-schemas:
>
> # apt-get reinstall gsettings-desktop-schemas
Yes, the workaround for this is to reinstall any package that
On Tue, 27 Feb 2024 at 23:07:33 +0100, Matthias Klose wrote:
> On 23.02.24 22:10, Jeremy Bícha wrote:
> > Since glib and gobject-introspection have migrated out of
> > noble-proposed, is there still a need to keep this bug open?
>
> Suppose you would start again building glib2.0 (and depending
(Sorry, I thought I had sent this earlier.)
On Tue, 27 Feb 2024 at 08:39:05 -0500, Jeremy Bícha wrote:
> On Tue, Feb 27, 2024 at 5:33 AM Simon McVittie wrote:
> > If that's the case, then we should have transitional packages with those
> > names that just depend on libpro
Control: tag -1 pending
Hello,
Bug #1064889 in libproxy reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Source: libproxy
Version: 0.5.4-1
Severity: serious
Justification: breaks debian-edu-config dependencies
It looks as though the new libproxy1v5 has absorbed all of the
functionality of the older libproxy plugins:
- libproxy1-plugin-gsettings replaced by config-gnome internal to the library
-
Control: tags -1 + confirmed
Context for Mesa maintainers: gtk4 passed its build-time tests on
2024-01-29, but is now failing in a test rebuild. I can reproduce this,
and I think it's a regression triggered by Mesa changes (see also
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10293
On Tue, 20 Feb 2024 at 23:15:09 +0100, Matthias Klose wrote:
> On 20.02.24 22:50, Simon McVittie wrote:
> > What is the situation that is going wrong in autopkgtest? Can you perhaps
> > provide a log?
>
> see
> https://autopkgtest.ubuntu.com/packages/m/meson/noble/ppc64e
Control: tags -1 + moreinfo
On Tue, 20 Feb 2024 at 22:15:21 +0100, Matthias Klose wrote:
> The package had in the past dependencies of the form
>
> python3 (<< 3.12), python3 (>= 3.11~), python3:any
>
> the new one just
>
> python3:any
>
> This leads to badly triggered autopkg tests, with
Control: tag -1 pending
Hello,
Bug #1064042 in gsettings-desktop-schemas reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: retitle -1 krb5: FTBFS on IPv6-only buildds: "Can't resolve hostname"
in dh_auto_test
Control: tags -1 + ipv6
On Sun, 11 Feb 2024 at 23:40:34 +0000, Simon McVittie wrote:
> It might be relevant that according to #972151, arm-conova-03 (and
> perhaps other *-conova-* b
On Sun, 11 Feb 2024 at 13:53:56 -0800, Benjamin Kaduk wrote:
> On Sat, Feb 10, 2024 at 01:33:15PM +0100, Johannes Schauer Marin Rodrigues
> wrote:
> > there as a binNMU "Rebuild to sync binNMU versions" for krb5 and that
> > failed for arm64, armel and ppc64el:
> >
> >
On Thu, 08 Feb 2024 at 10:37:33 +, Simon McVittie wrote:
> Package: libmozjs-115-dev
> Justification: makes gjs FTBFS (#1063433)
I believe mozjs115_115.7.0-3 should fix this.
wb-team: Please could someone with wanna-build access schedule gjs
on mips64el to be built after the fixed v
Control: tag -1 pending
Hello,
Bug #1063446 in mozjs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Thu, 08 Feb 2024 at 10:37:33 +, Simon McVittie wrote:
> Simplified steps to reproduce:
> Try to compile the attached, with:
> g++ test.cpp -o test $(pkgconf --cflags --libs mozjs-115)
Oops, really attached now.
> I'm preparing a possible patch (but it will take a long
Package: libmozjs-115-dev
Version: 115.7.0-2
Severity: serious
Tags: upstream
Justification: makes gjs FTBFS (#1063433)
X-Debbugs-Cc: debian-m...@lists.debian.org
User: debian-m...@lists.debian.org
Usertags: mips64el
Control: block 1063433 by -1
Original steps to reproduce:
Try to compile gjs
On Tue, 06 Feb 2024 at 10:20:46 +0100, Yves Le Berre wrote:
> I am not familiarized with building debian debug packages.
> do doomsday and libsdl2 packages need to be rebuilt or do they exist
> somewhere ?
Their detached debug symbols should already be provided in Debian, so you
don't need to
On Mon, 05 Feb 2024 at 14:06:16 -0300, Lucas Kanashiro wrote:
> we have identified
> pangomm2.48 as a source package shipping runtime libraries whose ABI
> either is affected by the change in size of time_t, or could not be
> analyzed via abi-compliance-checker (and therefore to be on the safe
>
Control: reassign -1 doomsday,src:libsdl2
Control: found -1 doomsday/2.3.1+ds1-1
Control: found -1 libsdl2/2.30.0+dfsg-1
On Sun, 04 Feb 2024 at 09:18:27 +0100, Yves Le Berre wrote:
> * What led up to the situation?
>
> loading wad file (doom /doom2/heretic/...)
Please assume that I'm
On Mon, 29 Jan 2024 at 23:45:11 +, Steve Langasek wrote:
> Dear maintainer,
(I am a games team member but not a maintainer of this particular package)
> diff -Nru allegro4.4-4.4.3.1/debian/liballeggl4.4t64.4.install
> allegro4.4-4.4.3.1/debian/liballeggl4.4t64.4.install
> ---
On Sun, 28 Jan 2024 at 22:49:37 +0100, Alexandre Detiste wrote:
> Le jeu. 25 janv. 2024 à 11:15, Simon McVittie a écrit :
> > I also don't understand where these new upstream releases are coming from,
> > because https://github.com/renpy/pygame_sdl2 only has tags for 8.1.0,
>
Control: affects -1 + src:renpy
On Tue, 16 Jan 2024 at 20:43:34 +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> > src/pygame_sdl2/rwobject.pyx:336:22: Cannot assign type 'Sint64 (SDL_RWops
> > *) except? -1 nogil' to 'Sint64
Control: retitle -1 xdg-desktop-portal: FTBFS: test_inputcapture: Timed out
waiting for response from SetPointerBarriers
Control: tags -1 + unreproducible
On Tue, 16 Jan 2024 at 20:37:49 +0100, Lucas Nussbaum wrote:
> > 26/28 xdg-desktop-portal:pytest / pytest test_inputcaptureFAIL
Control: retitle -1 libshumate: FTBFS: Couldn't find include 'GObject-2.0.gir'
On Tue, 16 Jan 2024 at 20:43:20 +0100, Lucas Nussbaum wrote:
> > Couldn't find include 'GObject-2.0.gir' (search path:
> > '['/usr/share/gir-1.0', '/usr/lib/x86_64-linux-gnu/gir-1.0',
> >
On Sun, 14 Jan 2024 at 08:39:52 +0100, Paul Gevers wrote:
> The Release Team considers packages that are out-of-sync between testing and
> unstable for more than 30 days as having a Release Critical bug in testing
> [1]. Your package src:mesa has been trying to migrate for 31 days [2].
> Hence, I
Source: mesa
Version: 23.3.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: armel
Control: block 1060779 by -1
The armel baseline does not have
Control: severity -1 important
On Sat, 13 Jan 2024 at 19:32:58 +, Simon McVittie wrote:
> On Sat, 13 Jan 2024 at 16:21:46 +0000, Simon McVittie wrote:
> > On Sat, 13 Jan 2024 at 15:21:02 +0000, Simon McVittie wrote:
> > > I recently uploaded a snapshot of GLib 2.79
1 - 100 of 2135 matches
Mail list logo
