There is this upstream bug where some discussion is happening, and
there are concerns about the changes in existing data structures.
https://gitlab.com/NTPsec/ntpsec/-/issues/832
This one I actually prefer:
https://salsa.debian.org/sssd-team/sssd/-/merge_requests/36
We will "never" know why the login test was flaky, but this should
work always... (tests are running)
How about this?
https://salsa.debian.org/sssd-team/sssd/-/merge_requests/33/diffs
Tests still running...
On Tue, Dec 17, 2024 at 5:28 AM Michael Prokop wrote:
>
> Hi,
>
> * Chris Hofstaedtler [Wed Dec 11, 2024 at 11:50:21AM +0100]:
> > On Tue, Dec 03, 2024 at 05:02:30PM -0300
I'm proposing this patch for ubuntu:
Description: Replace deprecated GIT_OBJ_XXX references
Author: Andreas Hasenack
Origin: vendor
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084258
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/git-ubuntu/+bug/2091778
Last-Update:
Hello,
this is what I used to fix the FTBFS in ubuntu (just uploaded).
I also took the opportunity to rebuild with imagemagick 7:
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,7 @@ Uploaders: Debian Junior Maintainers
Build-Depends: debhelper-compat (= 13),
gettext,
Hi,
> The attached patch resolves the issue in (at least) the lxc autopkgtest
> environment.
I would suggest a lower range, as the gid mapping inside containers
(at least lxd in ubuntu) doesn't allow such a large range by default.
Since the ping command is executed by the "backuppc" user, which i
Sergio[1] got access to the actual container that failed to run this
test, and we tried to troubleshoot it a bit. We were pressed for time,
and didn't get very far.
What we did/tried:
- reproduced the problem at will, in every single test run, interactively
- verified that the ldap setup was sound
Hi,
On Mon, Dec 2, 2024 at 5:06 AM Michael Prokop wrote:
> So it sadly still doesn't seem to work on amd64. :(
> Quoting from
> https://ci.debian.net/packages/s/sssd/testing/amd64/54970410/:
>
> | test ldap-user-group-ldap-auth: test run
> | [...]
> | 86s + [ testuser1 ldapusers != testuser1 l
Is d/t/ldap-user-group-krb5-auth also flaky? Because it uses the same
expect script:
d/t/ldap-user-group-krb5-auth:
...
# tests begin here
run_common_tests
# login works with the kerberos password
echo "The Kerberos principal can login on a terminal"
kdestroy > /dev/null 2>&1 || /bin/true
/usr/bi
f it could interfere sometimes.
1. https://salsa.debian.org/ahasenack/sssd/-/jobs/6539986/viewer#L801
On Tue, Nov 5, 2024 at 2:38 PM Andreas Hasenack wrote:
>
> I wrote that test initially, and it has been passing in Ubuntu. Sounds
> like it's some difference in the infrastructure.
&
I wrote that test initially, and it has been passing in Ubuntu. Sounds
like it's some difference in the infrastructure.
I tried locally in a debian LXD container, and it passed just fine. Is
it also failing in salsa pipeline runners, or just in the migration by
britney?
The error seems to indicat
This patch from upstream fixes the build.
autofs-5.1.9 - Fix incompatible function pointer types in cyrus-sasl module
From: Florian Weimer
Add casts to SASL callbacks to avoid incompatible-pointer-types
errors. Avoids a build failure with stricter compilers.
Signed-off-by: Florian Weimer
Sign
I believe this is because the hns provider is not built on architectures
which have no "COHERENT_DMA":
-- Performing Test HAVE_COHERENT_DMA
-- Performing Test HAVE_COHERENT_DMA - Failed
(...)
-- Missing Optional Items:
-- Architecture NOT able to do coherent DMA (check util/udma_barrier.h)
some p
This fixes the build:
--- a/configure.ac
+++ b/configure.ac
@@ -852,6 +852,7 @@ fi
AC_CACHE_CHECK([if gettimeofday takes tz
argument],rsync_cv_HAVE_GETTIMEOFDAY_TZ,[
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[#include
+#include
#include ]], [[struct timeval tv; exit(gettimeofday(&tv,
NULL));]])],[
> 1. --- 0x2 != 0x1
>src/tests/cmocka/test_responder_cache_req.c:2505: error: Failure!
>
>assert_int_equal(test_ctx->result->count, 1);
>
> apparently there are 2 results returned while expected just one.
This is because of time_t now being 64bits and a "%lu" format string
is being used
...and 2.2.4 also fails to build:
https://github.com/savonet/liquidsoap/issues/3752
$ make
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
: warning: "_FORTIFY_SOURCE" redefined
: note: this is the location of the previous definition
: warning: "_FORT
Upstream fixed[1] this in 2.2.4. There are big commits that could be
used as patches, but it's probably best to just update to 2.2.4.
1. https://github.com/savonet/liquidsoap/issues/3750
attached fixes for the gcc-13 FTBFS
From e8d1d1486e3d9d8495af4c0903d6eb3e24a92094 Mon Sep 17 00:00:00 2001
From: Brecht Van Lommel
Date: Wed, 18 Jan 2023 13:42:55 +0100
Subject: [PATCH] Fix T103960: build issue with GCC 13 in Cycles thread code
---
intern/cycles/util/thread.cpp | 2 ++
1 file ch
Quick MP at
https://salsa.debian.org/python-team/packages/cachelib/-/merge_requests/1
The problem is that 1.6.19-1 is listening on ipv6 as well, and that
makes the test suite fail to start another copy due to "address
already in use":
@@__xproc_block_delimiter__@@
slab class 1: chunk size 96 perslab 10922
(...)
failed to listen on TCP port 11211: Address already in use
1.6.18-1 on
Hi,
any particular reason for not adopting the upstream patch, which fixes
the problem properly? Disabling the compiler/build flags that tripped
the error could have other consequences.
Hi,
we hit this bug in Ubuntu as well, and I created a salsa PR for it:
https://salsa.debian.org/science-team/netgen/-/merge_requests/12
Looks like it's a python bug: https://github.com/python/cpython/issues/91257
Upstream issue: https://github.com/tlsfuzzer/python-ecdsa/issues/285
Hi,
this is the root cause:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006147
There is a PR for it:
https://salsa.debian.org/pkg-debconf/debconf/-/merge_requests/10
Ubuntu is carrying this patch for now:
https://git.launchpad.net/ubuntu/+source/debconf/commit/?h=applied/ubuntu/devel
To
I believe these patches from upstream fix the build problem:
https://git.launchpad.net/ubuntu/+source/unbound/tree/debian/patches/python3.10.patch
https://git.launchpad.net/ubuntu/+source/unbound/tree/debian/patches/python3.10-2.patch
I filed this upstream bug
https://github.com/gluster/glusterfs/issues/2979 and am using this
patch in Ubuntu:
diff --git a/debian/rules b/debian/rules
index 0e28ea8e..7bfab4c1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,6 +4,12 @@ include /usr/share/dpkg/pkg-info.mk
export DEB_BUILD_MAINT
I filed an upstream bug at
https://github.com/cyrusimap/cyrus-sasl/issues/624 with the beginnings
of a patch, but the build then fails elsewhere and I didn't make much
more progress. Looks like some variables changed types.
I believe it was introduced in 5.8. The previous version we had was 5.7.3
and we didn't reproduce it there.
On Fri, Jun 26, 2020 at 6:18 PM Salvatore Bonaccorso
wrote:
> Hi Andreas,
>
> On Thu, Jun 25, 2020 at 06:31:13PM -0300, Andreas Hasenack wrote:
> > Hi,
> >
>
Hi,
we are not happy yet with those commits because they change a struct
without bumping the soname. We are investigating how impactful that is.
On Thu, Jun 25, 2020 at 6:27 PM Salvatore Bonaccorso
wrote:
> Hi,
>
> On Thu, Jun 25, 2020 at 10:29:20PM +0200, Salvatore Bonaccorso wrote:
> > Source
PR up at https://salsa.debian.org/samba-team/talloc/-/merge_requests/7
Upstream fixes, located by juliank:
https://github.com/ruby/ruby/commit/f234e6c3d3170f37508e214cdaef78d4b2584e5a
https://github.com/ruby/ruby/commit/1e0b49a293d3792826c67b7e05c5fcbd09c9ea6e
32 matches
Mail list logo
