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: 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
Source: gmpc
Severity: important
Tags: upstream wontfix
X-Debbugs-Cc: gmpc-plug...@packages.debian.org
It appears that gmpc no longer has any sort of upstream developer.
https://github.com/DaveDavenport/gmpc is specifically labelled as
unmaintained, https://repo.or.cz/w/gmpc.git hasn't been
On Thu, 14 Mar 2024 at 22:03:57 -0700, Otto Kekäläinen wrote:
> For example curl isn't building on armel/armhf now and numerous packages that
> depend of curl are not building on armel/armhf.
I believe a maintainer upload or NMU of #1066981 and #1066982 would
now be enough to unblock curl, which
and should be reverted when the transition has finished.
Thanks,
smcv
>From bc8cd5d7a40c8acaf2c164c538b6c0b07f2d3dab Mon Sep 17 00:00:00 2001
From: Simon McVittie
Date: Sat, 16 Mar 2024 11:36:05 +
Subject: [PATCH 2/3] Temporarily disable LDAP support on 32-bit non-x86
This makes offic
features that are unlikely to be
used by game engines. When I'm back at work I'd be happy to look at
contributing similar build-profiles to disable other optional bits if
there is interest.)
smcv
>From ae094c1e4b2b0ec943f39f2b6a6176091af20d33 Mon Sep 17 00:00:00 2001
From: Simon McVittie
D
Hi again,
I have uploaded a NMU with the patch below into DELAYED/10. Let me know
if you want to cancel it.
/Simon
Simon Josefsson writes:
> Hi Ruben, all,
>
> I have opened a merge request to resolve the bug below:
>
> https://salsa.debian.org/debian-mobcom-te
t automatically
extended, which is one solution.
/Simon
> Thanks!
>
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.5.0-21-generic (
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
freediameter, bug filed here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066848
I'm hoping we don't have to care about compatibility with oldstable.
/Simon
signature.asc
Description: PGP signature
Hi Ruben, all,
I have opened a merge request to resolve the bug below:
https://salsa.debian.org/debian-mobcom-team/freediameter/-/merge_requests/4
Are you able to merge and upload a new version?
If you agree, and add me to the Salsa group, I can merge it and prepare
the upload too.
/Simon
Package: freediameter
Version: 1.2.1-8
Tags: patch
Hi! I'd like to drop the transitional package 'libidn11-dev' as most
packages have already moved to use 'libidn-dev' which is in stable.
How about this patch?
/Simon
diff --git a/debian/control b/debian/control
index 335362a..2856eae 100644
atch. I've verified that it compiles
successfully in an armhf porterbox chroot (without ssh-askpass-gnome)
and on amd64 (with ssh-askpass-gnome), but I haven't otherwise tested it.
Thanks,
smcv
>From bbefe785a6ab567677af77ccd12b1fbb59a42d8d Mon Sep 17 00:00:00 2001
From: Simon McVittie
Date
Package: loudmouth
Version: 1.5.4-1
Tags: patch
Hi! I'd like to drop the transitional package 'libidn11-dev' as most
packages have already moved to use 'libidn-dev' which is in stable.
How about this patch?
/Simon
diff --git a/debian/control b/debian/control
index 853b197..963b1c3 100644
Package: at-spi2-core
Version: 2.51.90-3
Severity: important
X-Debbugs-Cc: debian-...@lists.debian.org
Tags: patch
at-spi2-core has a circular build-dependency on itself when tests are
enabled, which makes its build-dependencies unsatisfiable (libglib2.0-dev
depends on libglib2.0-0t64, but
On Sat, 18 Mar 2023 at 14:46:47 +0100, Andrea Bolognani wrote:
> In other words, upstream developers have retroactively added symbols
> (fuse_new_31) to existing symbol groups (FUSE_3.1).
...
> really this looks like an upstream
> bug in my opinion: even if the function was present in the source
>
On Tue, 12 Mar 2024 at 23:13:30 -0500, Steven Robbins wrote:
> I checked the build logs for cargo and noticed that most architectures have
> been built on the buildds. All release arches except armel & armhf. How is
> it that these two have build dep installability problems but others do not?
On Tue, 12 Mar 2024 at 22:30:01 +0100, Michael Biebl wrote:
> On Wed, 9 Aug 2023 04:05:43 +0200 Bertram Felgenhauer wrote:
> > My speculation is that this happened while satisfying dependencies for
> > a third party i386 application. That meant installing required 32 bit
> > libraries, and one of
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,
Control: block -1 by 1065787 1066049
One dependency chain that is blocking a lot of rebuilds right now is
this one:
... => curl -> stunnel4 -> python-cryptography => cargo => ...
key: => mandatory dependency
-> nocheck dependency
In the medium term, cargo needs
On Mon, 11 Mar 2024 at 20:09:06 +, Simon McVittie wrote:
> Thanks for proposing this, but I think these should be ifneq instead
> of ifeq
Actually, this patch also still allowed dh_auto_test to run on the
time64-affected architectures, which would presumably fail because the
Control: tags -1 + fixed-upstream
Control: block -1 by 1061616
Control: retitle 1061616 pixman: New upstream version 0.43.4
On Mon, 29 Jan 2024 at 10:23:45 +, Simon McVittie wrote:
> On Mon, 29 Jan 2024 at 05:13:59 +, Gayathri Berli wrote:
> > we found out that while
>
On Mon, 11 Mar 2024 at 19:54:00 +0100, Mattia Rizzolo wrote:
> +ifeq ($(DEB_HOST_ARCH_BITS)$(filter i386,$(DEB_HOST_ARCH_CPU)),32)
> execute_before_dh_auto_test:
> env PYTHONPATH='$(CURDIR)/debian/tests/python' \
> python3 -B -u -m struntime \
>
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,
>
Source: shared-mime-info
Version: 2.4-1
Severity: wishlist
Tags: patch
In my experience it is usually easier to work with source packages in a VCS
if their upstream source code is also present in the same VCS, and is
merged into the packaging branch (the same layout used by the GNOME,
Perl,
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'
Package: libneatvnc0
Version: 0.8.0+dfsg-1
Severity: important
Justification: Policy 8.6.2
Tags: upstream
X-Debbugs-Cc: wes...@packages.debian.org, way...@packages.debian.org
libneatvnc 0.8.0 removes a public function from its API/ABI:
│ -const char* nvnc_client_get_hostname(const struct
Control: forcemerge 1065709 1057620
On Sat, 09 Mar 2024 at 11:06:46 +, Simon McVittie wrote:
> In a GNOME Wayland session, with qtwayland5 installed:
>
> $ doomsday
> QSocketNotifier: Can only be used with threads started with QThread
> [1]381459 segmentation fau
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
Package: doomsday
Version: 2.3.1+ds1-1+b2
Severity: important
In a GNOME Wayland session, with qtwayland5 installed:
$ doomsday
QSocketNotifier: Can only be used with threads started with QThread
[1]381459 segmentation fault (core dumped) doomsday
Backtrace:
#0 0x7f9dc2c3ee83 in
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.
>
On Wed, 06 Mar 2024 at 21:40:10 +0100, Arnaldo Pirrone wrote:
> libgtk-3-0t64 3.24.41-1.1 is breaking libgtk-3-0
This is part of the ongoing 64-bit time_t transition (for details please
see a large proportion of recent traffic on the debian-devel mailing
list). Please be patient: sometimes
/-/commits/ogre-13.3/?ref_type=heads
I'm currently super short on time but will try to help you with any
technical problems if you open a MR for a patch
Best regards from Freiburg
Simon
Am 06.03.24 um 08:46 schrieb Flavien Bridault:
Dear maintainer(s),
I took a look at the latest version
On Sat, 02 Mar 2024 at 20:19:47 +, Simon McVittie wrote:
> I have proposed a change for glib2.0/experimental at
> https://salsa.debian.org/gnome-team/glib/-/merge_requests/32 which
> implements the "delete the old postrm" approach
An equivalent glib2.0 change
the existing
package that provides awk (and ideally keep the behaviour where awk is
marked auto-installed, since it is not explicitly requested).
Presumably, the auto flag on mawk is deduced because it is pulled in by
an essential package, that makes sense and should probably stay that
way.
Simon
On Mon, 04 Mar 2024 at 20:21:56 +, Markus Koller wrote:
> So it's trying to use the `DND_IN_DRAG` cursor at [1].
That's not a concrete cursor name, it's an alias in libmutter. Depending
on version of libmutter, it could end up referring to either "dnd-none"
(which is no longer provided) or
Copying context from elsewhere in the thread, Sam Hartman wrote:
> Are there solutions in the space of having glib2.0-0 continue to exist
> as a package depended on by glib2.0-0t64 or depending on the new library
> allowing you to replace the postrm?
to which I replied:
If libglib2.0-0 continues
Source: libphonenumber
Version: 8.12.57+ds-4.1
Severity: important
X-Debbugs-Cc: vor...@debian.org
After the time64 transition, libphonenumber8t64 Provides
libphonenumber8t64-protobuf with no version suffix. This appears to be
caused by the rename of libprotobuf32 to libprotobuf32t64: the regex
On Sun, 03 Mar 2024 at 17:34:25 +0100, Harald Dunkel wrote:
> I got a few messages in kern.log:
>
> 2024-03-03T17:10:55.375204+01:00 cecil kernel: traps: at-spi-bus-laun[2238]
> trap int3 ip:7f52523f5587 sp:7ffded761730 error:0 in
> libglib-2.0.so.0.7800.4[7f52523b1000+99000]
Please try
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
Package: low-memory-monitor
Version: 2.1-2
Severity: minor
low-memory-monitor appears to be an activatable D-Bus service with no
particular C/C++ ABI. If this is the case, then it could be marked
Multi-Arch: foreign (since D-Bus is normally an architecture-independent
protocol if the interface
On Sat, 02 Mar 2024 at 20:19:47 +, Simon McVittie wrote:
> I have proposed a change for glib2.0/experimental at
> https://salsa.debian.org/gnome-team/glib/-/merge_requests/32 which
> implements the "delete the old postrm" approach.
I've uploaded this to experimental, inc
Control: clone -1 -2
Control: reassign -2 gobject-introspection 1.78.1-15
Control: retitle -2 dh_girepository: generates unwanted dependency on
libgirepository1.0-dev if that package is installed
Control: severity -2 important
On Sun, 03 Mar 2024 at 00:40:52 +0100, Samuel Thibault wrote:
>
On Sat, 02 Mar 2024 at 20:19:50 +, Simon McVittie wrote:
> I am currently downloading all versions of libglib2.0-0 that have
> existed on amd64 as tracked by snapshot.d.o. My plan is to extract their
> DEBIAN/postrm, import them into a git branch and go back through the
> hist
undreds of thousands of systems, the expectation is that I must not
upload without sufficient testing. So, my intention is to do my best,
and then invite other developers to take responsibility for a better,
higher-version-numbered upload with different timing if they prefer.
On Fri, 01 Mar 2024 at 1
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 Fri, 01 Mar 2024 at 13:21:51 +0100, Christoph Berg wrote:
> > Possible solution: other ideas?
>
> Make glib2.0-t64 use a different cache filename?
I'm not happy about the idea of introducing long-term divergence in
the upstream code as a result of a Debian-specific packaging problem;
I think
Package: tech-ctte
Severity: normal
X-Debbugs-Cc: debian-d...@lists.debian.org, debian-gtk-gn...@lists.debian.org,
vor...@debian.org
I'm requesting advice from the tech-ctte (or anyone else with relevant
knowledge, e.g. the dpkg team or the drivers of the time64 transition)
on how to resolve
> against accidental backports with a wrong ABI.
Thanks - for how long will the dpkg-dev build-depends be necessary?
/Simon
signature.asc
Description: PGP signature
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
y have
worked, because it would have switched both apt and apt-utils to the new
version, and the remaining involved packages were automatically
installed as dependencies of the packages being upgraded).
Simon
d support for both.
>
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021292 and
> https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=8f5aca71c
also now implemented in blhc [1].
Best,
Simon
[1]:
https://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commitdiff;h=019d2b1c80b43bc7fa2a1df68ca
could add support for it.
>
> See https://bugs.debian.org/918914 and
> https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=11efff1bf
Thanks for the links. It's now implement in blhc [1].
Best,
Simon
[1]:
https://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commitdiff;h=f1ac73364a8d0a20e279328db6b
gt;
> |/usr/lib/ccache/c++ -std=gnu++20 -dM -E -c
> /usr/share/cmake-3.27/Modules/CMakeCXXCompilerABI.cpp|
This is now fixed in blhc [1] [2].
Best,
Simon
[1]:
https://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commitdiff;h=766e4499437c6e872cc5870a821c4d10d2d8a63b
[2]:
https://ruderich.org
-\S+/
> Modules/CMakeCXXCompilerABI\.cpp};
>
> https://ruderich.org/simon/gitweb/?p=blhc/
> blhc.git;a=commitdiff;h=32513c3cf648aab94fb011e488a79bb38c2fafd1[2]
>
> I am not a regular expression expert, and it seems that both of these ought
> to match
> against the line in question:
>
> /
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
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
-
On Sun, 25 Feb 2024 at 03:21:23 +0200, Jussi Pakkanen wrote:
> Meson comes with a tool that converts native and cross environments
> into cross files. It is run with `meson env2mfile`. It even has a mode
> to generate Debian package building scripts. Updating that to handle
> this case would
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 Mon, 26 Feb 2024 at 08:25:37 +, Gayathri Berli wrote:
> We are having a Debian unstable environment(sid) on s390x.. We think, it's
> better to reproduce the issue with git cloned repo instead of using “sbuild”
> method, so that we can get the commit history and see the code changes.
I see.
On Sat, 24 Feb 2024 at 11:19:48 +, Simon McVittie wrote:
> This unconditional use of restrict seems like a bug, I'll report it
> upstream.
https://gitlab.gnome.org/GNOME/sysprof/-/issues/114, fix proposed in
https://gitlab.gnome.org/GNOME/sysprof/-/merge_requests/88.
smcv
Control: tags -1 + wontfix
On Sat, 24 Feb 2024 at 02:10:45 -0800, Steve Langasek wrote:
> +sysprof (46~beta-1.1~exp1) experimental; urgency=medium
> +
> + * Non-maintainer upload.
> + * Rename libraries for 64-bit time_t transition.
I'm pretty sure this one is actually unnecessary...
> ---
Package: proton-caller
Version: 3.1.2-1
Severity: minor
proton-caller Suggests steam. Since Debian 12, the steam:i386 in contrib is
a transitional package which Depends on steam-installer.
Meanwhile, for users of Valve's .deb packages (official from Valve's
point of view, unofficial from
Package: gamehub
Version: 0.16.3-2-master+ds-1
Severity: minor
gamehub Suggests steam. Since Debian 12, the steam:i386 in contrib is
a transitional package which Depends on steam-installer.
Meanwhile, for users of Valve's .deb packages (official from Valve's
point of view, unofficial from
Package: protontricks
Version: 1.10.5-1
Severity: minor
protontricks Recommends steam. Since Debian 12, the steam:i386 in contrib
is a transitional package which Depends on steam-installer.
Meanwhile, for users of Valve's .deb packages (official from Valve's
point of view, unofficial from
On Wed, 21 Feb 2024 at 10:47:33 +0100, Johannes Schauer Marin Rodrigues wrote:
> I've just learned from Simon McVittie in #debian-devel that there is a way to
> cross-build packages using meson and gobject-introspection without this patch
> by configuring them with --cross-file. Here is a
On Tue, 20 Feb 2024 at 16:08:26 +, Gayathri Berli wrote:
> Please let us know if this bug still needs to be fixed.
I have never seen a s390x machine and probably never will, so you will
know much better than I do whether it's advantageous to our users for
mutter and gnome-shell to be
On Wed, 14 Feb 2024 at 16:47:23 +, Gayathri Berli wrote:
> In the current issue of gtk4 When I tried to reproduce
> the issue on s390x there are 1507 tests that are failing. Can you please
> suggest that version of dependency packages being used/issue reproduce steps/
> logs.
I'm sorry, I
ed first" or "alpha
first" or "red in the least significant byte of the first 32-bit word"
or "alpha in the least significant byte". Otherwise, you can't know
whether a change is actually correct, or whether it's a workaround for
the layer above or below also being wr
Control: forcemerge 1064438 -1
On Thu, 22 Feb 2024 at 12:25:53 -0500, David Mandelberg wrote:
> Upgrading gsettings-desktop-schemas from 45.0-2 to 46~beta-3 seems to have
> fixed the problem. So I think gnome-settings-daemon's dependency on
> gsettings-desktop-schemas (>= 42~) should be updated
On Thu, 22 Feb 2024 at 14:21:38 +, Daniel Thompson wrote:
> I assume this is a version skew problem caused by gnome-settings-daemon
> updating to GNOME 46 before other components
If you upgrade both gnome-settings-daemon and gsettings-desktop-schemas
to their versions from unstable, does that
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: ost...@packages.debian.org
* Package name: composefs
Version : 1.0.3
Upstream Contact: Alexander Larsson, Colin Walters
* URL : https://github.com/containers/composefs
* License : GPL-3.0-or-later AND
Would it make sense to change this to use an inclusive list of permitted
characters instead? How about checking the field names that is in use
today, and construct a regexp of permitted symbols out of that?
Starting point: [A-Za-z][A-Za-z0-9-_]*
/Simon
signature.asc
Description: PGP signature
On Wed, 21 Feb 2024 at 21:55:08 +0100, Niels Thykier wrote:
> On Mon, 18 Jun 2018 12:16:55 +0100 Simon McVittie wrote:
> > I hadn't intended that you'd add this mechanism for packages that
> > ship debhelper addons alongside other content, just the ones that have
> > littl
originally integrated in the owncloud-client
> source package. Upstream decided to extract them to create a new repo.
>
> The package will be maintained in the owncloud-team.
Hi - how about including 'owncloud' in the package name?
'owncloud-client-desktop-shell-integration-nautilus'? Or
'o
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
On Tue, 20 Feb 2024 at 21:05:55 +0100, Amy Kos wrote:
> latest change in 46~beta-4
> "Use a more minimal set of aliases as requested by upstream"
> is understandable from Gnome perpective.
I did try to get a more comprehensive set of aliases merged, but
the upstream maintainer refused, and I was
so
diffing changes was a bit difficult. Do you still have the 0.1.6-2 tag
locally? If so would be good if you could push that. Uploaded anyway,
and I forgot to add a 'New upstream release' changelog entry, although
that should be pretty obvious from the version number anyway.
/Simon
signature.as
run on new valgrind on
gss or gsasl which has triggered similar bugs before?
/Simon
signature.asc
Description: PGP signature
Control: forwarded -1
https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues/55
Control: tags -1 + upstream
On Fri, 16 Feb 2024 at 11:02:42 +0100, Jörg-Volker Peetz wrote:
> upgrading from version 45.0-2 to this version introduces a regression:
> with LC_TIME=en_GB.utf8 now a 12-hour
Package: adwaita-icon-theme
Version: 46~beta-1
Severity: important
Tags: upstream
Control: affects -1 firefox firefox-esr chromium libsdl2-2.0-0
Forwarded: https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues/278
adwaita-icon-theme 46~beta removed a lot of symlinks representing legacy
X11
-6_all.deb and
qemu-efi-arm_2023.11-6_all.deb fixes the issue, so the breakage is in -7
--
Simon John
Debian:12.5/stable [amd64])
Conf qtchooser (66-2 Debian:12.5/stable [amd64])
Conf qt5-qmake (5.15.8+dfsg-11 Debian:12.5/stable [amd64])
Conf qtbase5-dev-tools (5.15.8+dfsg-11 Debian:12.5/stable [amd64])
Conf qtbase5-gles-dev (5.15.8+dfsg-3 Debian:12.5/stable [amd64])
Conf qttranslations5-l10n (5.15.
Package: debuginfod
Version: 0.188-2.1
Severity: minor
Tags: upstream
Control: found -1 0.190-1
Related to the bug I recently opened regarding a missing dependency on
libarchive-tools, debuginfod(8) says:
-U Activate DEB/DDEB patterns in archive scanning. The default is
Package: debuginfod
Version: 0.188-2.1
Severity: important
Control: found -1 0.190-1
By default, debuginfod wants to unpack detached debug symbols and libraries
from Debian packages using bsdtar:
> Feb 12 13:14:46 REDACTED docker[2367192]: [Mon Feb 12 13:14:46 2024] (7/7):
> accepting archive
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:
> >
> >
Source: srt
Version: 1.5.3-1
Severity: important
Tags: ftbfs unreproducible
The srt_1.5.3-1+b1 binNMU initially failed to build on the i386 buildd
with this test failure:
> 100: Test command: /<>/build-gnutls/test-srt
> "--gtest_filter=Transmission.FileUpload"
> 100: Working Directory:
201 - 300 of 15490 matches
Mail list logo
