Processing control commands:
> close -1 23.0.0-4
Bug #1056633 [src:gprconfig-kb] src:gprconfig-kb: fails to migrate to testing
for too long: autopkgtest regression
Marked as fixed in versions gprconfig-kb/23.0.0-4.
Bug #1056633 [src:gprconfig-kb] src:gprconfig-kb: fails to migrate to testing
Source: gprconfig-kb
Version: 23.0.0-3
Severity: serious
Control: close -1 23.0.0-4
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30
close 1052949
thanks
Processing commands for cont...@bugs.debian.org:
> close 1052949
Bug #1052949 [src:gap-polymaking] gap-polymaking: FTBFS: polymake: ERROR:
"/usr/share/polymake/perllib/Polymake/Core/CPlusPlus.pm", line 1785: Can't load
shared module /usr/lib/polymake/lib/ideal.so:
close 1052949 jzo...@heute-morgen.de
thanks
Your message dated Fri, 24 Nov 2023 03:04:18 +
with message-id
and subject line Bug#1055862: fixed in node-proxy-agents 0~2023071921-3
has caused the Debian Bug report #1055862,
regarding node-http-proxy-agent: missing Breaks+Replaces:
node-https-proxy-agent (<< 7)
to be marked as done.
Your message dated Fri, 24 Nov 2023 03:04:18 +
with message-id
and subject line Bug#1056599: fixed in node-proxy-agents 0~2023071921-3
has caused the Debian Bug report #1056599,
regarding node-proxy-agents: FTBFS with internet disabled
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #1056599 [src:node-proxy-agents] node-proxy-agents: FTBFS with internet
disabled
Added tag(s) pending.
--
1056599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1056599 in node-proxy-agents 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:
Processing control commands:
> tag -1 pending
Bug #1055862 [node-http-proxy-agent] node-http-proxy-agent: missing
Breaks+Replaces: node-https-proxy-agent (<< 7)
Added tag(s) pending.
--
1055862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055862
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1055862 in node-proxy-agents 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:
Processing control commands:
> affects -1 + cython3-dbg
Bug #1056627 [cython3] cython3 has an undeclared file conflict
Added indication that 1056627 affects cython3-dbg
--
1056627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056627
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Package: cython3
Version: 0.29.36-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + cython3-dbg
cython3 has an undeclared file conflict. This may result in an unpack
error from dpkg.
The files
*
Your message dated Thu, 23 Nov 2023 23:06:51 +
with message-id
and subject line Bug#1054718: fixed in ruby-uc.micro-rb 1.0.6-1
has caused the Debian Bug report #1054718,
regarding ruby-uc.micro-rb: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error:
require 'pry-byebug'
to be marked as done.
Package: reportbug
Version: 12.0.0
Severity: serious
Justification: Please do not redirect bugs to third party sites
Dear Maintainer,
pkg chromium is redirecting bugs through reportbug to http://www.crbug.com
$ apt policy chromium
chromium:
Installed: 119.0.6045.159-1~deb12u1
I do not
Processing control commands:
> severity -1 important
Bug #1056580 [src:llvm-toolchain-17] LLVM-17's autopkg tests fail (command1)
Severity set to 'important' from 'serious'
--
1056580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056580
Debian Bug Tracking System
Contact
Control: severity -1 important
lowering priority, technically it's not a regression (new package).
Quoting Ilias Tsitsimpis (2023-11-23 21:10:36)
> On Fri, Nov 17, 2023 at 09:28AM, Ilias Tsitsimpis wrote:
> > On Thu, Nov 16, 2023 at 10:16PM, Jonas Smedegaard wrote:
> > > Quoting John MacFarlane (2023-11-16 19:25:17)
> > > > Removing lua support would be most unfortunate! If you need help from
Package: timeshift
Version: 22.11.2-1
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: truescore149...@gmail.com
Dear Maintainer,
User cant make BTRFS snapshots without "@" subvolume (debian uses "@rootfs"),
but user can make RSYNC snapshot. The problem is that when you
On Fri, Nov 17, 2023 at 09:28AM, Ilias Tsitsimpis wrote:
> On Thu, Nov 16, 2023 at 10:16PM, Jonas Smedegaard wrote:
> > Quoting John MacFarlane (2023-11-16 19:25:17)
> > > Removing lua support would be most unfortunate! If you need help from
> > > upstream in getting things to work, let me know.
Your message dated Thu, 23 Nov 2023 19:03:55 +
with message-id
and subject line Bug#1052975: fixed in assess-el 0.6+git20231120.2399936-1
has caused the Debian Bug report #1052975,
regarding assess-el: FTBFS: make: *** [debian/rules:4: binary] Error 25
to be marked as done.
This means that
Source: node-proxy-agents
Version: 0~2023071921-1
Severity: serious
Hello, looks like the package tries to do calls to internet during build.
+ jest --testTimeout 5 --env node --moduleDirectories node_modules
--testRegex test/dnsDomainIs.test.ts test/dnsDomainLevels.test.ts
Le 2023-11-23 à 11 h 20, Steve McIntyre a écrit :
AFAICS in a non-interactive environment, USER isn't required to be set
but LOGNAME is; see
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html
Alternatively, the tets should probably be calling get(e)uid and
getpwent()
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:assess-el
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package dracut
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting
close 1052949 jzo...@heute-morgen.de
Should be fixed in polymake 4.11-1
Source: mat2
Version: 0.13.4-2
Severity: serious
Tags: upstream patch ftbfs
Justification: fails to build from source (but built successfully in the past)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Currently mat2's test suite fails, maybe due to newer libimage-exiftool-perl
releases. This
On Thu, Nov 23, 2023 at 10:46:34AM -0500, Nicolas Mora wrote:
>Le 2023-11-23 à 09 h 46, Steve McIntyre a écrit :
>>
>> Ah, apologies - that version is bogus, it's just the version on the
>> bullseye machine I ran reportbug from.
>>
>> The tests are failing on current unstable source.
>>
>
>OK,
Le 2023-11-23 à 09 h 46, Steve McIntyre a écrit :
Ah, apologies - that version is bogus, it's just the version on the
bullseye machine I ran reportbug from.
The tests are failing on current unstable source.
OK, makes more sense then.
Nevertheless I'm wondering about the seriousness of the
Your message dated Thu, 23 Nov 2023 15:08:38 +
with message-id
and subject line Bug#1056396: fixed in orthanc-webviewer 2.8-4
has caused the Debian Bug report #1056396,
regarding orthanc-webviewer: autopkgtest failure on !x86
to be marked as done.
This means that you claim that the problem
Hi,
Le mercredi 22 novembre 2023 à 18:48 +0100, Gianfranco Costamagna a
écrit :
> control: tags -1 patch
>
> Hello, not sure why and how, but this upstream commit
> fbe9e28b667e795a5ceb41bd7784bd2ea7ab10bf
>
>
On Thu, Nov 23, 2023 at 09:20:37AM -0500, Nicolas Mora wrote:
>Hello,
>
>On Tue, 21 Nov 2023 13:30:31 + Steve McIntyre wrote:
>> Source: libssh2
>> Version: 1.9.0-2
>> Severity: serious
>> Tags: ftbfs patch
>>
>> Hi!
>>
>> Building libssh2 using debuild in a clean local chroot, I get test
Control: tag -1 pending
Hello,
Bug #1056396 in orthanc-webviewer 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:
Processing control commands:
> tag -1 pending
Bug #1056396 [src:orthanc-webviewer] orthanc-webviewer: autopkgtest failure on
!x86
Added tag(s) pending.
--
1056396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> forwarded 1056580 https://github.com/llvm/llvm-project/issues/73244
Bug #1056580 [src:llvm-toolchain-17] LLVM-17's autopkg tests fail (command1)
Set Bug forwarded-to-address to
'https://github.com/llvm/llvm-project/issues/73244'.
> forwarded
Processing control commands:
> severity 1039001 wishlist
Bug #1039001 [src:hera] hera: Updating to version 2.0.0
Severity set to 'wishlist' from 'serious'
--
1039001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: hera
Version: 1.0.0+dfsg-2
Followup-For: Bug #1039001
Control: severity 1039001 wishlist
Uploading catch2 v3 also made hera FTBFS (#1054686), and it is not clear
whether the catch2 package will provide backwards-compatible headers
(#1055237). Since updating hera is not entirely trivial,
Hello,
On Tue, 21 Nov 2023 13:30:31 + Steve McIntyre wrote:
Source: libssh2
Version: 1.9.0-2
Severity: serious
Tags: ftbfs patch
Hi!
Building libssh2 using debuild in a clean local chroot, I get test
failures and even a core dump!
Thanks for reporting the bug, although I have concerns
On Fri 27 Oct 2023, Lucas Nussbaum wrote:
> Source: pixmap
> Version: 2.6.6-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20231027 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
>
On 2023-11-23 08:43:16 -0500, Jeremy Bícha wrote:
> On Sat, Nov 11, 2023 at 5:09 AM Sebastian Ramacher
> wrote:
> > Package: libamtk-5-dev
> > Version: libamtk-5-dev
> > Severity: serious
> > Tags: sid trixie
> > X-Debbugs-Cc: sramac...@debian.org
> >
> …
> > The following packages have unmet
Source: kaidan
Version: 0.9.1-2
Severity: serious
Hello, the package FTBFS trying to call search.jabber.network, something
forbidden by policy.
6: QWARN : GroupChatTest::test_GroupChatSearchManager_GroupChatModel()
public-group-chat.search: Search request error: Host search.jabber.network
On Sat, Nov 11, 2023 at 5:09 AM Sebastian Ramacher wrote:
> Package: libamtk-5-dev
> Version: libamtk-5-dev
> Severity: serious
> Tags: sid trixie
> X-Debbugs-Cc: sramac...@debian.org
>
…
> The following packages have unmet dependencies:
> libamtk-5-dev : Depends: gir1.2-amtk-5 (= 5.6.1-2) but
Processing commands for cont...@bugs.debian.org:
> unarchive 1053956
Bug #1053956 {Done: Paul Gevers } [src:alsa-lib]
src:alsa-lib: fails to migrate to testing for too long: unresolved RC bugs
Unarchived Bug 1053956
> block 1053956 by 1054896
Bug #1053956 {Done: Paul Gevers } [src:alsa-lib]
Your message dated Thu, 23 Nov 2023 13:21:26 +
with message-id
and subject line Bug#1056312: fixed in zlib 1:1.3.dfsg-3
has caused the Debian Bug report #1056312,
regarding zlib1g makes tex-common fail to install due to fmtutil failing
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> block 1053956 by 1054896
Failed to set blocking bugs of 1053956: Not altering archived bugs; see
unarchive.
> merge 1054896 1051901
Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386
Unable to merge bugs because:
blocks of
Processing commands for cont...@bugs.debian.org:
> block 1054896 by 1053956
Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386
No valid blocking bug(s) given; not doing anything
Failed to set blocking bugs of 1054896: Unknown/archived blocking
bug(s):1053956.
> merge 1054896
Processing commands for cont...@bugs.debian.org:
> severity 1054896 serious
Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386
Severity set to 'serious' from 'grave'
> block 1054896 1053956
Unknown command or malformed arguments to command.
> merge 1054896 1051901
Bug #1054896
Processing commands for cont...@bugs.debian.org:
> severity serious 1054896
Unknown command or malformed arguments to command.
> tags 1054896 fixed-upstream upstream
Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386
Added tag(s) fixed-upstream and upstream.
> forwarded 1054896
Package: src:llvm-toolchain-17
Version: 1:17.0.5-1
Severity: serious
Tags: sid trixie
[...]
231s clang++-$VERSION -std=c++14 -stdlib=libc++ foo.cpp
-lc++experimental -o o
233s /usr/bin/ld: cannot find -lc++experimental: No such file or directory
233s clang++-17: error: linker command failed
On 2023-11-23 12:22:05 +0100, Matthias Klose wrote:
> Control: tags -1 + moreinfo
>
> I'm not looking into that, CCing the ports maintainers. Sure, we can
> disable running the tests on mips64el.
It used to be no problem while the faster mips64el buildds were
available. But currently we only
Your message dated Thu, 23 Nov 2023 11:49:03 +
with message-id
and subject line Bug#1055669: fixed in bcftools 1.18-2
has caused the Debian Bug report #1055669,
regarding bcftools: test_vcf_merge failures on armhf: Bus error
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 23 Nov 2023 12:37:43 +0100
with message-id
and subject line fixed for LLVM 17
has caused the Debian Bug report #1041838,
regarding libclang-rt-17-dev: undeclared file conflict with
libclang-rt-17-dev-wasm{32,64} on
this is fixed:
$ dpkg -L libclang-rt-17-dev|grep -c wasi
0
Processing control commands:
> tags -1 + moreinfo
Bug #1056238 [src:gcc-13] gcc-13: FTBFS on mips64el: E: Build killed with
signal TERM after 150 minutes of inactivity
Added tag(s) moreinfo.
--
1056238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056238
Debian Bug Tracking System
Control: tags -1 + moreinfo
I'm not looking into that, CCing the ports maintainers. Sure, we can
disable running the tests on mips64el.
On 19.11.23 11:18, Sebastian Ramacher wrote:
Source: gcc-13
Version: 13.2.0-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but
Processing control commands:
> tag -1 pending
Bug #1055669 [src:bcftools] bcftools: test_vcf_merge failures on armhf: Bus
error
Added tag(s) pending.
--
1055669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1055669 in bcftools 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 Thu, 23 Nov 2023 10:49:01 +
with message-id
and subject line Bug#1056569: fixed in brotli 1.1.0-2
has caused the Debian Bug report #1056569,
regarding libbrotli-dev: libbrotlidec.a corrupted due to c-p error in
0001-build-static-libraries-by-default.patch
to be marked as
Processing control commands:
> severity -1 serious
Bug #1056569 [libbrotli-dev] libbrotli-dev: libbrotlidec.a corrupted due to c-p
error in 0001-build-static-libraries-by-default.patch
Severity set to 'serious' from 'normal'
> tags -1 patch pending
Bug #1056569 [libbrotli-dev] libbrotli-dev:
Hi.
Two notes:
1) This doesn't just fail on rscv64 but also on amd64 and i386 with
the same error as in the linked build log from the original report:
[...]
[ RUN ] LPETest.MeasureSegments_multi_px_1_0_2
add_actions_edit_document: no app!
add_actions_pages: no app!
add_actions_undo: no
Your message dated Thu, 23 Nov 2023 09:33:57 +
with message-id
and subject line Bug#1050066: fixed in adequate 0.15.9
has caused the Debian Bug report #1050066,
regarding adequate: autopkgtest fails on !amd64
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 23 Nov 2023 09:19:05 +
with message-id
and subject line Bug#1042298: fixed in node-wikibase-cli 15.15.4-5
has caused the Debian Bug report #1042298,
regarding node-wikibase-cli: FTBFS: TypeError: Cannot read properties of
undefined (reading 'Q11')
to be marked as
Dear Maintainer,
After moving conftest.py from package root to tests/ (as upstream did), your
package builds fine in a sid chroot environment and all tests pass as well.
Kind Regards
63 matches
Mail list logo
