Processing commands for cont...@bugs.debian.org:
> retitle 1052232 FTBFS with recent context
Bug #1052232 [src:mlpost] FTBFS with OCaml 4.14.1
Changed Bug title to 'FTBFS with recent context' from 'FTBFS with OCaml 4.14.1'.
> thanks
Stopping processing here.
Please contact me if you need
Processing control commands:
> block 1052232 by -1
Bug #1052232 [src:mlpost] FTBFS with OCaml 4.14.1
1052232 was not blocked by any bugs.
1052232 was not blocking any bugs.
Added blocking bug(s) of 1052232: 1052298
--
1052232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052232
1052298:
Processing control commands:
> severity -1 serious
Bug #1052232 [src:mlpost] FTBFS with OCaml 4.14.1
Severity set to 'serious' from 'important'
--
1052232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> affects 1051933 + src:pysmi
Bug #1051933 [python3-pysnmp-pysmi] python3-pysnmp-pysmi has an undeclared file
conflict
Added indication that 1051933 affects src:pysmi
> found 1051933 1.0.4-2
Bug #1051933 [python3-pysnmp-pysmi] python3-pysnmp-pysmi
Processing commands for cont...@bugs.debian.org:
> severity 1052231 serious
Bug #1052231 [src:gmetadom] FTBFS with OCaml 4.14.1
Severity set to 'serious' from 'important'
> severity 1052236 serious
Bug #1052236 [src:otags] FTBFS with OCaml 4.14.1
Severity set to 'serious' from 'important'
>
Package: inkscape
Version: 1.3+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to
Processing control commands:
> severity -1 normal
Bug #1049380 [src:gliv] RM: gliv -- RoQA; unmaintained; depends on gtk2
Severity set to 'normal' from 'serious'
> reassign -1 ftp.debian.org
Bug #1049380 [src:gliv] RM: gliv -- RoQA; unmaintained; depends on gtk2
Bug reassigned from package
Processing control commands:
> severity -1 normal
Bug #1044138 [src:pcmanx-gtk2] RM: pcmanx-gtk2 -- RoQA; dead upstream; depends
on gtk2
Severity set to 'normal' from 'serious'
> reassign -1 ftp.debian.org
Bug #1044138 [src:pcmanx-gtk2] RM: pcmanx-gtk2 -- RoQA; dead upstream; depends
on gtk2
Control: severity -1 normal
Control: reassign -1 ftp.debian.org
Please remove gliv. It is unmaintained both upstream and in Debian.
Also, it depends on the deprecated gtk2.
Control: severity -1 normal
Control: reassign -1 ftp.debian.org
Please remove pcmanx-gtk2. It is dead upstream, unmaintained in Debian,
and depends on the deprectated gtk2.
Package: nwchem
Version: 7.0.2-4
Followup-For: Bug #1042034
The problem seems to be specific to mpich, which is a bit peculiar.
The openmpi build remains successful.
Apologies. It seems that usrmerge had not successfully performed the merge
(another issue). It was installed, as can be seen in my first message, but
running /usr/lib/usrmerge/convert-usrmerge manually did the trick. It also
merges /lib*.
Thank you and with my best regards,
On Tue, Sep 19,
Quoting Alexandru Mihail (2023-09-19 23:41:05)
> > do you have an estimate when you think you can upload this? This bug has
> > now blocked part of my work in Debian for two weeks and I'm unable to do
> > another release for my package until this bug gets fixed.
> I'm planning to release no later
Hello,
> do you have an estimate when you think you can upload this?
>
> This bug has now blocked part of my work in Debian for two weeks and
> I'm unable
> to do another release for my package until this bug gets fixed.
>
I'm planning to release no later than Friday. I'm also tackling #491078
On Mon, Sep 18, 2023 at 07:56:09PM -0400, Philippe Grégoire wrote:
> As such, I can no longer install or remove packages since my system is
> partitioned. I'd like to point out that the above link does not specifically
> mention disk partitioning, but only how files are placed on disk.
>
>
Processing commands for cont...@bugs.debian.org:
> Severity 1051146 serious
Bug #1051146 [rust-laurel] rust-laurel, upcoming rust-bindgen update.
Severity set to 'serious' from 'normal'
> Thanks
Stopping processing here.
Please contact me if you need assistance.
--
1051146:
Control: reopen -1
On 15/09/2023 01.18, Debian Bug Tracking System wrote:
dpkg: error processing archive […]/php-psr-log-test_1.1.0-1_all.deb
(--unpack):
trying to overwrite […] which is also in package php-fig-log-test
1.1.0-1
Seems like a false positive: a package trying to
Processing control commands:
> reopen -1
Bug #1051967 {Done: David Prévot } [php-fig-log-test]
php-fig-log-test: ships /usr/share/php/Psr/Log/Test/*.php, already in
php-psr-log-test
Bug reopened
Ignoring request to alter fixed versions of bug #1051967 to the same values
previously set
--
Source: python-unicodedata2
Version: 14.0.0+ds2-1
Severity: serious
Tags: ftbfs sid trixie upstream
Forwarded: https://github.com/fonttools/unicodedata2/issues/60
python-unicodedata2 fails to build with unicode-data 15.1.0, now in Unstable.
A brief outline of needed changes is provided in the
Hello,
the new Bullseye version of xrdp is identical to the version in Bookworm. Thus
the underlying problem is probably more complex and I don't suspect that
something is wrong with xrdp itself but more likely with a configuration option
or related software packages which do something different
Hello,
The bug is also reported upstream:
https://github.com/neutrinolabs/xrdp/issues/2796
the xorgxrdp package must be updated in sync for the xrdp version
Emmanuel Blindauer
Processing commands for cont...@bugs.debian.org:
> close 1052284
Bug #1052284 [src:pdm] pdm: Please replace python3-pep517 with
python3-pyproject-hooks in Depends/Build-Depends
Marked Bug as done
> unblock 1043255 by 1052284
Bug #1043255 [ftp.debian.org] RM: pep517 -- ROM; Obsolete, replaced by
Processing commands for cont...@bugs.debian.org:
> clone 1043002 -1 -2
Bug #1043002 [src:pdm] pdm: Please replace python3-pep517 with
python3-pyproject-hooks in Depends/Build-Depends
Bug 1043002 cloned as bugs 1052284-1052285
1043255 was blocked by: 1043002 1042869 1042965
1043255 was not
Source: mythtv-status
Version: 1.1.0-1
Severity: serious
Tags: ftbfs
mythtv-status fails to build from source when built with the nocheck
build profile and option. Since trixie such a failure is considered
release critical, because the autoremover relies on correct nocheck
annotations. A build
X-Debbugs-CC: ma...@debian.org
On Sat, 09 Sep 2023 16:04:38 -0400 Boyuan Yang wrote:
> Source: jpeg-xl
> X-Debbugs-Cc: by...@debian.org
> Version: 0.7.0-10
> Severity: serious
> Tags: ftbfs sid trixie
>
> Dear Maintainer,
>
> For jpeg-xl/0.7.0-10, it currently fails to build from source in
Hi Andreas,
I have decided to restore the non-SIMD binaries. I have just written code
to do that, and will release a new version once some large-scale test runs
complete successfully.
Thanks,
Thomas Wu
On Tue, Sep 19, 2023 at 8:48 AM Thomas Wu wrote:
>
> Hi Andreas,
>
> The GMAP package
Control: tag -1 pending
Hello,
Bug #1051880 in faust 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 #1051880 [src:faust] faust: FTBFS with llvm-toolchain-16 as default
Added tag(s) pending.
--
1051880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi,
Please update to version 2.2.6.8, have critical bug fix for Unix/Linux
system (enable able to manipulate non latin char like japan char)
alpha_one_x86/BRULE Herman
Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server
management
IT, OS, technologies, research &
Your message dated Tue, 19 Sep 2023 20:30:43 +0200
with message-id
and subject line Re: pysolfc does not start any more
has caused the Debian Bug report #1039723,
regarding pysolfc does not start any more
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Tue, 6 Sep 2022 10:10:30 -0300 Athos Ribeiro wrote:
As I commented in a similar bug in Ubuntu [1], while the fix for this
issue is available upstream and seems technically straightforward, it
injects a deprecated python module in its code base and re-licenses it
as CC0.
Only the changes to
Your message dated Tue, 19 Sep 2023 18:00:12 +
with message-id
and subject line Bug#1052177: fixed in pg-gvm 22.6.2-1
has caused the Debian Bug report #1052177,
regarding Provides a PostgreSQL extension without depending on the correct
server version
to be marked as done.
This means that
On Fri, 15 Sep 2023 14:35:08 +0200 "Farblos"
wrote:
> Not sure whether this is still relevant or just bad luck or whatever ... my
> unattended-upgrade failed today because of this issue. Logs available
> on request. Work-around was to remove version 3.20+dfsg-7, retrigger
> the unattended
Package: librust-pkcs5-dev
Version: 0.7.1-1+b1
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
librust-pkcs5-dev depends on missing package librust-scrypt-0.11-dev
-BEGIN PGP SIGNATURE-
Processing control commands:
> found -1 1:1.4.15+dfsg-2
Bug #1051797 {Done: Sergei Golovan } [libtk-img-doc]
libtk-img-doc: dpkg extraction error during upgrading
Marked as found in versions libtk-img/1:1.4.15+dfsg-2; no longer marked as
fixed in versions libtk-img/1:1.4.15+dfsg-2 and reopened.
Followup-For: Bug #1051797
Control: found -1 1:1.4.15+dfsg-2
Removing the readme from the -doc package is not sufficient, you also
need to add
Breaks+Replaces: libtk-img-doc (<< 1:1.4.15+dfsg-2)
to libtk-img in order to properly take over the file on upgrades from
1:1.4.15+dfsg-1 or before.
Processing control commands:
> found -1 0.0~git20220819.8ec7bd9-3
Bug #1052260 [libcpuinfo-dev,libtorch-cuda-dev,libtorch-dev]
libcpuinfo-dev,libtorch-cuda-dev,libtorch-dev: all ship /usr/include/clog.h
There is no source info for the package 'libtorch-cuda-dev' at version
Package: libcpuinfo-dev,libtorch-cuda-dev,libtorch-dev
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Control: found -1 0.0~git20220819.8ec7bd9-3
Control: found -1 2.0.1+dfsg-4
Hi,
during a test with piuparts I noticed your package failed to install
because it
Hi Andreas,
The GMAP package should compile on both Intel and Apple architectures. I
think we are now requiring SIMD or its equivalent Neon, though, which is
why we are no longer building the *.nosimd binaries. I don't think that's
a problem since every modern computer supports SIMD or Neon.
Processing commands for cont...@bugs.debian.org:
> found 1051889 3.18.0+ds2-1
Bug #1051889 [src:freeimage] freeimage: CVE-2020-22524
Marked as found in versions freeimage/3.18.0+ds2-1.
> found 1051738 3.18.0+ds2-1
Bug #1051738 [src:freeimage] freeimage: CVE-2020-21428
Marked as found in versions
Control: tags -1 + patch fixed-upstream
Hi again,
On Wed, 13 Sep 2023 16:17:59 +0200 Timo Röhling wrote:
Unfortunately, this bug is *not* resolved; it looks like this is
not a false positive but the subclass case which is explicitly
mentioned in the documentation:
Upstream has fixed this by
Processing control commands:
> tags -1 + patch fixed-upstream
Bug #1051435 [src:python-pytest-asyncio] python-pytest-asyncio: failing
autopkgtest
Added tag(s) patch and fixed-upstream.
--
1051435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051435
Debian Bug Tracking System
Contact
On 9/19/23 17:02, Bo YU wrote:
hmm, I try the patch again, but it seems it works on amd64.
`apt source ceph` to get ceph_16.2.11+ds-2 and debdiff-apply the patch.
I guess maybe you apply the patch on salsa repo.
Yes, I did.
Also, you might have missed that I prepared the next version in the
Control: tag -1 pending
Hello,
Bug #1037602 in ceph 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 #1037602 [src:ceph] ceph: ftbfs with GCC-13
Added tag(s) pending.
--
1037602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> fixed 1051738 3.18.0+ds2-10
Bug #1051738 [src:freeimage] freeimage: CVE-2020-21428
The source 'freeimage' and version '3.18.0+ds2-10' do not appear to match any
binary packages
Marked as fixed in versions freeimage/3.18.0+ds2-10.
> fixed 1051889
Hi!
On Tue, Sep 19, 2023 at 3:45 PM Thomas Goirand wrote:
>
> On 9/18/23 13:03, Bo YU wrote:
> > Source: ceph
> > Followup-For: Bug #1037602
> > Tags: patch
> > User: debian-ri...@lists.debian.org
> > Usertags: riscv64
> > X-Debbugs-Cc: debian-ri...@lists.debian.org
> >
> > Dear Maintainer,
> >
Processing control commands:
> tags -1 upstream
Bug #1041451 [src:gmap] gmap: FTBFS on all !amd64 archs
Added tag(s) upstream.
> forwarded -1 Thomas Wu , Colin K. Watanabe
Bug #1041451 [src:gmap] gmap: FTBFS on all !amd64 archs
Set Bug forwarded-to-address to 'Thomas Wu , Colin K. Watanabe
'.
Control: tags -1 upstream
Control: forwarded -1 Thomas Wu , Colin K. Watanabe
Hi Thomas and Colin,
the Debian packaged gmap fails to build since version 2023-06-01 for all
release architectures besides amd64. You can read about this bug on our
bug tracker[1]. I think the analysis from
Processing control commands:
> severity -1 normal
Bug #1043510 [src:rox] RM: rox -- RoQA; dead upstream; depends on gtk2
Severity set to 'normal' from 'serious'
> reassign -1 ftp.debian.org
Bug #1043510 [src:rox] RM: rox -- RoQA; dead upstream; depends on gtk2
Bug reassigned from package
Control: severity -1 normal
Control: reassign -1 ftp.debian.org
Please remove rox. It is orphaned and dead upstream.
It also depends on the deprecated gtk2, which will obviously not be fixed.
Nobody chimed in on the RM announcement to keep it in Debian.
Your message dated Tue, 19 Sep 2023 13:06:03 +
with message-id
and subject line Bug#1052219: fixed in libgcrypt20 1.10.2-3
has caused the Debian Bug report #1052219,
regarding unrecognized option '--insert-timestamp=1686475264'
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> tags 1052219 - moreinfo
Bug #1052219 [src:libgcrypt20] unrecognized option
'--insert-timestamp=1686475264'
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1052219:
On 2023-09-19 Shengjing Zhu wrote:
> On Tue, Sep 19, 2023 at 5:08 PM Andreas Metzler wrote:
[...]
> > Looking at the changelog entry
> > * Drop specify-timestamp.patch, applied upstream in binutils 2.41
> > (Closes: #1042734)
> > changing the rdeps does not make any sense at all, since the
Package: dkms
Version: 3.0.11-3
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
* What led up to the situation?
Enrolled my own secureboot key chain (PK, KEK, db) and wanted dkms to sign
kernel modules automatically.
* What exactly did you do (or not do) that was
Control: tags -1 pending
On Wed, 26 Jul 2023 22:20:02 +0200 Lucas Nussbaum
wrote:
> Source: dnf
> Version: 4.14.0-4
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230726 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages
Processing commands for cont...@bugs.debian.org:
> retitle 1052223 insighttoolkit5: Use full ::itk namespace in itkMacro.h
Bug #1052223 [src:insighttoolkit5] sight: FTBFS:
/<>/libs/io/itk/helper/ProgressItkToFw.hxx:48:5: error: ‘::Create’
has not been declared
Changed Bug title to
Processing control commands:
> tags -1 pending
Bug #1042338 [src:dnf] dnf: FTBFS: dh_auto_test: error: cd build && make -j8
test ARGS\+=--verbose ARGS\+=-j8 ARGS=-VV returned exit code 2
Added tag(s) pending.
--
1042338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042338
Debian Bug
Processing control commands:
> clone -1 -2
Bug #1039529 [src:sight] sight: FTBFS:
/<>/libs/io/itk/helper/ProgressItkToFw.hxx:48:5: error: ‘::Create’
has not been declared
Bug 1039529 cloned as bug 1052223
> reassign -2 src:insighttoolkit5 5.3.0-5
Bug #1052223 [src:sight] sight: FTBFS:
Control: clone -1 -2
Control: reassign -2 src:insighttoolkit5 5.3.0-5
Hi Flavien
On Mon, 18 Sept 2023 at 14:24, Flavien Bridault
wrote:
>
> My message was maybe missed during the summer, I give a new attempt... I can
> offer a hand to provide the ITK patch if that can help...
Let me try
On Tue, Sep 19, 2023 at 5:08 PM Andreas Metzler wrote:
>
> Control: tags 1052219 moreinfo
>
> On 2023-09-19 Shengjing Zhu wrote:
> > On Tue, Sep 19, 2023 at 2:57 PM Shengjing Zhu wrote:
> > > Package: binutils-mingw-w64-i686
> > > Version: 2.41-4+11+nmu1
> [...]
> >> The NMU
Processing control commands:
> tags 1052219 moreinfo
Bug #1052219 [src:libgcrypt20] unrecognized option
'--insert-timestamp=1686475264'
Added tag(s) moreinfo.
--
1052219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags 1052219 moreinfo
On 2023-09-19 Shengjing Zhu wrote:
> On Tue, Sep 19, 2023 at 2:57 PM Shengjing Zhu wrote:
> > Package: binutils-mingw-w64-i686
> > Version: 2.41-4+11+nmu1
[...]
>> The NMU binutils-mingw-w64/11+nmu1 drops specify-timestamp.patch.
>> It causes libgcrypt20,
Processing commands for cont...@bugs.debian.org:
> # built with gcc-13 as default on the buildds
> close 1037604 116.0.5845.140-1
Bug #1037604 {Done: Timothy Pearson }
[src:chromium] chromium: ftbfs with GCC-13
Marked as fixed in versions chromium/116.0.5845.140-1.
Bug #1037604 {Done: Timothy
Processing control commands:
> reassign -1 src:libgcrypt20 1.10.2-2
Bug #1052219 [binutils-mingw-w64-i686] unrecognized option
'--insert-timestamp=1686475264'
Bug reassigned from package 'binutils-mingw-w64-i686' to 'src:libgcrypt20'.
No longer marked as found in versions
Control: reassign -1 src:libgcrypt20 1.10.2-2
Control: clone -1 -2
Control: reassign -2 src:gcc-mingw-w64 25.2
On Tue, Sep 19, 2023 at 2:57 PM Shengjing Zhu wrote:
>
> Package: binutils-mingw-w64-i686
> Version: 2.41-4+11+nmu1
> Severity: serious
> Tags: ftbfs
> X-Debbugs-Cc: ol...@debian.org,
On 9/18/23 13:03, Bo YU wrote:
Source: ceph
Followup-For: Bug #1037602
Tags: patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear Maintainer,
I found these commits that was trying to fix the issue but it looks like
they not done yet. I
Processing commands for cont...@bugs.debian.org:
> affects 1052219 + libgcrypt20 gcc-mingw-w64
Bug #1052219 [binutils-mingw-w64-i686] unrecognized option
'--insert-timestamp=1686475264'
Added indication that 1052219 affects libgcrypt20 and gcc-mingw-w64
> thanks
Stopping processing here.
Please
Package: binutils-mingw-w64-i686
Version: 2.41-4+11+nmu1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: ol...@debian.org, z...@debian.org
The NMU binutils-mingw-w64/11+nmu1 drops specify-timestamp.patch.
It causes libgcrypt20, gcc-mingw-w64 FTBFS.
These packages use options like
Processing commands for cont...@bugs.debian.org:
> tags 1052139 + sid trixie
Bug #1052139 [src:morty] dead upstream, popcon <10
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1052139:
70 matches
Mail list logo
