Your message dated Tue, 12 Mar 2024 05:55:24 +
with message-id
and subject line Bug#1065954: fixed in tcltrf 2.1.4-dfsg3-3
has caused the Debian Bug report #1065954,
regarding tcltrf: FTBFS on arm{el,hf}:
to be marked as done.
This means that you claim that the problem has been dealt with.
Dear maintainer,
This bug is (apparently?) currently preventing the amd64 build of 1.20.1-6. I
apologize if this is already understood (by the way, is there somewhere on [1]
or elsewhere to see if the build is being retried?). I'm also assuming I am not
authorized to "give back" and trigger
Source: ntfs-3g
Version: 1:2022.10.3-1.1
Severity: serious
Tags: d-i
Justification: broken shlibs
X-Debbugs-Cc: debian-b...@lists.debian.org, Benjamin Drung
Hi,
Here's what debian/libntfs-3g89t64/DEBIAN/shlibs looks like after
a build:
libntfs-3g 89 libntfs-3g89
udeb: libntfs-3g 89
Your message dated Tue, 12 Mar 2024 00:33:53 +
with message-id
and subject line Bug#1060981: fixed in libreswan 4.12-2
has caused the Debian Bug report #1060981,
regarding libreswan: FTBFS: plutomain.c:1724:9: error: ignoring return value of
‘capng_apply’ declared with attribute
Your message dated Tue, 12 Mar 2024 00:30:54 +
with message-id
and subject line Bug#1065610: fixed in libguestfs 1:1.52.0-3
has caused the Debian Bug report #1065610,
regarding libguestfs0t64: All appliance dependencies lost during time_t
transition
to be marked as done.
This means that you
Your message dated Tue, 12 Mar 2024 00:30:54 +
with message-id
and subject line Bug#1065189: fixed in libguestfs 1:1.52.0-3
has caused the Debian Bug report #1065189,
regarding libguestfs: missing build-dep on libtirpc-dev (and also rpcsvc-proto)
to be marked as done.
This means that you
Your message dated Tue, 12 Mar 2024 01:26:00 +0100
with message-id
and subject line Re: Bug#1066070: libpng1.6: hardcodes wrong udeb in shlibs,
making udebs uninstallable
has caused the Debian Bug report #1066070,
regarding libpng1.6: hardcodes wrong udeb in shlibs, making udebs uninstallable
to
Source: mtdev
Version: 1.1.6-1.1
Severity: serious
Tags: d-i
Justification: broken shlibs
X-Debbugs-Cc: debian-b...@lists.debian.org, Benjamin Drung
Hi,
Your NMU broke this package's shlibs.
Before:
libmtdev 1 libmtdev1
udeb: libmtdev 1 libmtdev1-udeb
After:
libmtdev 1
Source: libpng1.6
Version: 1.6.43-3
Severity: serious
Tags: d-i
Justification: broken shlibs
X-Debbugs-Cc: debian-b...@lists.debian.org
Hi,
Your debian/rules includes this:
override_dh_makeshlibs:
dh_makeshlibs --add-udeb=libpng16-16-udeb -a
and that's indeed the package that's
Your message dated Tue, 12 Mar 2024 00:13:52 +
with message-id
and subject line Bug#1065713: fixed in directfb 1.7.7-12
has caused the Debian Bug report #1065713,
regarding directfb: FTBFS on arm{el,hf}: error: ‘const struct input_event’ has
no member named ‘time’
to be marked as done.
This
Source: libpng1.6
Version: 1.6.43-3
Severity: serious
Tags: d-i
Justification: broken shlibs
X-Debbugs-Cc: debian-b...@lists.debian.org
Hi,
Your debian/rules includes this:
override_dh_makeshlibs:
dh_makeshlibs --add-udeb=libpng16-16-udeb -a
and that's indeed the package that's
Source: cl-plus-ssl
Version: 20220328.git8b91648-4
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
cl-plus-ssl hardcodeds a dependency on libssl3. Due to the time_t
transition, the package name changed and the dependency needs to be
updated.
Cheers
--
Sebastian Ramacher
Source: libvformat
Version: 1.13-12.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=libvformat=armhf=1.13-12.1=1709167815=0
libtool: compile: gcc
Let's wait for boost 1.84 to become available in Debian then.
Your message dated Mon, 11 Mar 2024 21:32:35 +
with message-id
and subject line Bug#1065794: fixed in xen 4.17.3+36-g54dacb5c02-1
has caused the Debian Bug report #1065794,
regarding xen: FTBFS on armhf: xenstored_control.c:646:70: error: format ‘%ld’
expects argument of type ‘long int’, but
Your message dated Mon, 11 Mar 2024 21:20:56 +
with message-id
and subject line Bug#1065771: fixed in dcap 2.47.14-2
has caused the Debian Bug report #1065771,
regarding dcap: FTBFS on arm{el,hf}: dcap.h:56:21: error: conflicting types for
‘dc_readdir64’; have ‘struct dirent *(DIR *)’
to be
Hi,
On Mon, Mar 11, 2024 at 05:55:31PM +0100, Sebastian Andrzej Siewior wrote:
> On 2024-03-11 00:05:54 [+], Amin Bandali wrote:
> > Hi Sebastian, all,
> Hi,
>
> > Will this fix be enough for addressing all cases, though?
>
> I think so. Do you have a test case for me to check?
Not about
Processing control commands:
> affects -1 + libhalide17-0-dev
Bug #1066057 [libhalide17-1-dev] libhalide17-1-dev has an undeclared file
conflict
Added indication that 1066057 affects libhalide17-0-dev
--
1066057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066057
Debian Bug Tracking
Package: libhalide17-1-dev
Version: 17.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libhalide17-0-dev
libhalide17-1-dev has an undeclared file conflict. This may result in an
unpack error from dpkg.
The files
*
close 1066051
thanks
Fab Stz dixit:
>I usually install openjdk-8 from unstable on bookworm.
This has never been officially supported. I’ve had an entire
discussion around that last month, which I will quote parts
from below, for context.
>However this is not possible anymore because now it
Processing commands for cont...@bugs.debian.org:
> forwarded 1066046 https://github.com/uqfoundation/mystic/issues/232
Bug #1066046 [src:mystic] mystic: fails autopkgtests on i386, armel, armhf,
ppc64el
Set Bug forwarded-to-address to
'https://github.com/uqfoundation/mystic/issues/232'.
>
Source: spacearyarya
Version: 1.0.2-8
Severity: serious
Tags: ftbfs
Due to the time64 transition, -Werror=-implicit-function-declaration was
enabled in default build flags and this makes spacearyarya FTBFS: Please
include the time.h header.
| gcc -DPACKAGE_NAME=\"SpaceAryarya-KXL\"
Source: sgrep
Version: 1.94a-5
Severity: serious
Tags: ftbfs
Due to the time64 transition, default build flags now include
-Werror=implicit-function-declaration. This happens to cause a build
failure for sgrep:
| gcc -DHAVE_CONFIG_H -I. -DDATADIR="\"/usr/share/sgrep\""
-DSYSCONFDIR="\"/etc\""
Processing commands for cont...@bugs.debian.org:
> retitle 1064762 Parsing of vtk files fails for files that worked previously
> (e.g. in bookworm)
Bug #1064762 [vtk9] dune-grid: FTBFS: make[1]: ***
[/usr/share/dune/dune-debian.mk:39: override_dh_auto_test] Error 1
Changed Bug title to 'Parsing
Processing commands for cont...@bugs.debian.org:
> reassign 1064762 vtk9
Bug #1064762 [src:dune-grid] dune-grid: FTBFS: make[1]: ***
[/usr/share/dune/dune-debian.mk:39: override_dh_auto_test] Error 1
Bug reassigned from package 'src:dune-grid' to 'vtk9'.
No longer marked as found in versions
Processing control commands:
> tags -1 upstream
Bug #1064921 {Done: Paul Gevers } [src:r-cran-estimatr]
src:r-cran-estimatr: fails to migrate to testing for too long: autopkgtest
regression on i386
Added tag(s) upstream.
> forwarded -1 https://github.com/DeclareDesign/estimatr/issues/407
Bug
Control: tags -1 upstream
Control: forwarded -1 https://github.com/DeclareDesign/estimatr/issues/407
Control: reopen -1
thanks
I have forwarded this problem upstream.
I've also reopened this bug to make sure it will show up on our sentinel
Kind regards
Andreas.
--
http://fam-tille.de
Your message dated Mon, 11 Mar 2024 19:49:15 +
with message-id
and subject line Bug#1060076: fixed in alberta 3.0.3-2
has caused the Debian Bug report #1060076,
regarding alberta: FTBFS on ppc64el: error: incompatible function pointer types
passing 'int (char *, char *, int)' to parameter of
Processing control commands:
> tags -1 upstream
Bug #1064922 {Done: Paul Gevers } [src:r-cran-gbm]
src:r-cran-gbm: fails to migrate to testing for too long: autopkgtest regression
Added tag(s) upstream.
> forwarded -1 https://github.com/gbm-developers/gbm/issues/78
Bug #1064922 {Done: Paul
Control: tags -1 upstream
Control: forwarded -1 https://github.com/gbm-developers/gbm/issues/78
Control: reopen -1
thanks
I have forwarded this bug upstream. I've also re-opened the bug to make
sure it appears on our list of bugs.
--
http://fam-tille.de
Your message dated Mon, 11 Mar 2024 19:20:12 +
with message-id
and subject line Bug#1064967: fixed in fontforge 1:20230101~dfsg-1.1
has caused the Debian Bug report #1064967,
regarding fontforge: CVE-2024-25081 CVE-2024-25082
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 11 Mar 2024 18:07:24 +
with message-id
and subject line Bug#1065975: fixed in libnet-nis-perl 0.44-3
has caused the Debian Bug report #1065975,
regarding libnet-nis-perl: FTBFS on arm{el,hf}: NIS.xs:499:11: error: implicit
declaration of function ‘yp_maplist’; did you
Axel Beckert wrote...
> Citing from https://buildd.debian.org/status/package.php?p=aptitude:
(...)
> /usr/include/cppunit/TestAssert.h:161:6: note: template argument
> deduction/substitution failed:
> ../../tests/test_misc.cc:187:5: note: deduced conflicting types for
> parameter ‘const T’
Processing control commands:
> tag -1 pending
Bug #1065975 [src:libnet-nis-perl] libnet-nis-perl: FTBFS on arm{el,hf}:
NIS.xs:499:11: error: implicit declaration of function ‘yp_maplist’; did you
mean ‘xdr_pmaplist’? [-Werror=implicit-function-declaration]
Added tag(s) pending.
--
1065975:
Control: tag -1 pending
Hello,
Bug #1065975 in libnet-nis-perl 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 2024-03-11 00:05:54 [+], Amin Bandali wrote:
> Hi Sebastian, all,
Hi,
> Will this fix be enough for addressing all cases, though?
I think so. Do you have a test case for me to check?
> I'm thinking specifically of cases where tarball repacking
> is involved, for example when using
Source: mystic
Version: 0.4.2-1
Severity: serious
Tags: upstream
The autopkgtests are failing on mystic/tests/test_collapse.py, line
177.
Making this bug report to track progress.
Your message dated Mon, 11 Mar 2024 16:35:24 +
with message-id
and subject line Bug#1065788: fixed in liblocale-hebrew-perl 1.05-4
has caused the Debian Bug report #1065788,
regarding liblocale-hebrew-perl: FTBFS on arm{el,hf}: Hebrew.xs:26:5: error:
implicit declaration of function
Processing control commands:
> tag -1 pending
Bug #1065788 [src:liblocale-hebrew-perl] liblocale-hebrew-perl: FTBFS on
arm{el,hf}: Hebrew.xs:26:5: error: implicit declaration of function ‘bidimain’
[-Werror=implicit-function-declaration]
Added tag(s) pending.
--
1065788:
Control: tag -1 pending
Hello,
Bug #1065788 in liblocale-hebrew-perl 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:
Your message dated Mon, 11 Mar 2024 16:05:24 +
with message-id
and subject line Bug#1065805: fixed in mypy 1.9.0-2
has caused the Debian Bug report #1065805,
regarding mypy: FTBFS: FAILED
mypy/test/teststubtest.py::StubtestUnit::test_runtime_typing_objects
to be marked as done.
This means
Processing control commands:
> tag -1 pending
Bug #1065805 [src:mypy] mypy: FTBFS: FAILED
mypy/test/teststubtest.py::StubtestUnit::test_runtime_typing_objects
Added tag(s) pending.
--
1065805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065805
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1065805 in mypy 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:
Hi,
these tests write out vtk files and read them in using python3-vtk9.
If parsing of the file succeeds then the test was successful.
How the files are written did not change between Debian stable and Debian sid.
I have verified that the files are the same.
Attached is a small test case in
Your message dated Mon, 11 Mar 2024 15:22:19 +
with message-id
and subject line Bug#1066039: fixed in virt-firmware 24.1.1-2
has caused the Debian Bug report #1066039,
regarding virt-firmware: autopkgtest are failing on debci
to be marked as done.
This means that you claim that the problem
Source: virt-firmware
Version: 24.1.1-1
Severity: grave
Dear Maintainer,
The autodep8 autopkgtest suite is failing and has never worked, which
is stopping virt-firmware from migrating to testing (hence severity).
The fix is trivial and attached, the test simply needs a hint on which
modules to
it would be more logical to invert the provides, having gdb provide
gdb-minimal, and have packages depend on gdb-minimal where it's
sufficient. currently, such packages express it by depending on
"gdb-minimal | gdb".
Processing commands for cont...@bugs.debian.org:
> forwarded 1065724 https://github.com/epics-base/epics-base/issues/466
Bug #1065724 [src:epics-base] epics-base: FTBFS on amd64: Tests failed
Set Bug forwarded-to-address to
'https://github.com/epics-base/epics-base/issues/466'.
> thanks
Stopping
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
Hi,
I can just confirm that whatever was done breaks usage of gbp import-
orig --uscan.
Cheers,
J.Puydt
Thanks, you are right.
Take care,
Aurelien Jarno writes:
> Hi,
>
> On 2024-03-10 11:20, Camm Maguire wrote:
>> Greetings! For now I am adding a libnsl-dev dependency to the gcl
>> package to restore the old behavior. A small fix to the fricas package
>> will eventually make this obsolete.
>
Your message dated Mon, 11 Mar 2024 12:38:57 +
with message-id
and subject line Bug#1065763: fixed in libmawk 1.0.4-1
has caused the Debian Bug report #1065763,
regarding libmawk: FTBFS on arm{el,hf}:
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> severity 1060318 important
Bug #1060318 [src:silx] silx: autopkgtest failure with Python 3.12
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1060318:
On Wed, 31 Jan 2024 14:54:08 + =?utf-8?q?Lukas_M=C3=A4rdian?=
wrote:
> Source: glw
> Version: 8.0.0-1.1
> Severity: serious
> Tags: patch pending
> Justification: library ABI skew on upgrade
> User: debian-...@lists.debian.org
> Usertags: time-t
>
> Dear maintainer,
>
> As part of the
Processing commands for cont...@bugs.debian.org:
> forwarded 1060318 https://github.com/pocl/pocl/issues/1435
Bug #1060318 [src:silx] silx: autopkgtest failure with Python 3.12
Set Bug forwarded-to-address to 'https://github.com/pocl/pocl/issues/1435'.
> severity -1 important
Failed to set
Source: pygobject
Version: 3.47.0-3
Severity: serious
Tags: unstable trixie ftbfs
User: debian-...@lists.debian.org
Usertags: time-t
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
Processing commands for cont...@bugs.debian.org:
> affects 1065751 + src:devscripts
Bug #1065751 [pristine-tar] Incomplete fix for xz -T1
Added indication that 1065751 affects src:devscripts
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1065751:
Your message dated Mon, 11 Mar 2024 11:46:39 +
with message-id
and subject line Bug#1065816: fixed in weston 13.0.0-5
has caused the Debian Bug report #1065816,
regarding weston: Dependency neatvnc found: NO found 0.8.0 but need: '< 0.8.0'
; matched: '>= 0.7.0'
to be marked as done.
This
Your message dated Mon, 11 Mar 2024 10:51:16 +
with message-id
and subject line Bug#1055136: fixed in nvidia-graphics-drivers 535.129.03-1
has caused the Debian Bug report #1055136,
regarding nvidia-graphics-drivers: CVE-2023-31022
to be marked as done.
This means that you claim that the
Dear all,
I was able to fix the FTBFS by backporting two upstream patches.
You can find my changes in MR [1]. Note that this also adds the
changes for the 64bit time_t transition made in version 3.0.3-1.1
to the repository.
As I am not Debian Developer and not maintaining the alberta, Hence
POCL_WORK_GROUP_METHOD=cbs python3 test.py
make it works
$ POCL_WORK_GROUP_METHOD=cbs python3 test.py
[SubCFG] Form SubCFGs in bsort_all
[SubCFG] Form SubCFGs in bsort_horizontal
[SubCFG] Form SubCFGs in bsort_vertical
[SubCFG] Form SubCFGs in bsort_book
[SubCFG] Form SubCFGs in bsort_file
With latest version (PAS OK)
$ dpkg -l | grep pocl
ii libpocl2-common5.0-2.1
all common files for the pocl library
ii libpocl2t64:amd64 5.0-2.1
Debian12 (OK)
$ dpkg -l | grep pocl
ii libpocl2:amd64 3.1-3+deb12u1
amd64Portable Computing Language library
ii libpocl2-common 3.1-3+deb12u1
all
On Debian12 it works out of the box
$ POCL_DEBUG=1 python3 test.py
[2024-03-11 10:05:31.837738936]POCL: in fn pocl_install_sigfpe_handler at line
229:
| GENERAL | Installing SIGFPE handler...
[2024-03-11 10:05:31.868890390]POCL: in fn POclCreateCommandQueue at line 98:
| GENERAL |
Hi Flavien,
* Flavien Bridault [2024-03-07 08:07]:
I just cloned the repository to open the MR but then I realized there
is already a branch opened two weeks ago exactly with the fix I
proposed... So I guess it is on its way ?
I guess you mean:
On Mon, Mar 11, 2024 at 12:05:54AM +, Amin Bandali wrote:
> I believe there are also some cases where git-buildpackage
> itself does repacking
E.g. `gbp import-orig --filter`
--
WBR, wRAR
signature.asc
Description: PGP signature
66 matches
Mail list logo
