Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029885,
regarding plasma-desktop: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029884,
regarding plymouth-kcm: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029878,
regarding khotkeys: Wait for the resolution of the libkscreen transition before
migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029882,
regarding plasma-workspace: Wait for the resolution of the libkscreen
transition before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029880,
regarding kgamma5: Wait for the resolution of the libkscreen transition before
migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029879,
regarding kactivitymanagerd: Wait for the resolution of the libkscreen
transition before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029876,
regarding layer-shell-qt: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029875,
regarding plasma-sdk: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029874,
regarding plasma-discover: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029873,
regarding plasma-systemmonitor: Wait for the resolution of the libkscreen
transition before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029871,
regarding powerdevil: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029870,
regarding plasma-remotecontrollers: Wait for the resolution of the libkscreen
transition before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029869,
regarding kscreen: Wait for the resolution of the libkscreen transition before
migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029868,
regarding plasma-integration: Wait for the resolution of the libkscreen
transition before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029867,
regarding plasma-browser-integration: Wait for the resolution of the libkscreen
transition before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029866,
regarding plasma-thunderbolt: Wait for the resolution of the libkscreen
transition before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029865,
regarding plasma-pa: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029864,
regarding plasma-nano: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029863,
regarding plasma-workspace-wallpapers: Wait for the resolution of the
libkscreen transition before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029862,
regarding kdecoration: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029858,
regarding polkit-kde-agent-1: Wait for the resolution of the libkscreen
transition before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029861,
regarding breeze-grub: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029860,
regarding kwin: Wait for the resolution of the libkscreen transition before
migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not t
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029859,
regarding plasma-vault: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029857,
regarding breeze-plymouth: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029888,
regarding plasma-firewall: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029856,
regarding plasma-nm: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029855,
regarding plasma-disks: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029854,
regarding kwayland-integration: Wait for the resolution of the libkscreen
transition before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029853,
regarding bluedevil: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029890,
regarding milou: Wait for the resolution of the libkscreen transition before
migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029881,
regarding sddm-kcm: Wait for the resolution of the libkscreen transition before
migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029877,
regarding ksystemstats: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated
with message-id
and subject line
has caused the Debian Bug report #1029872,
regarding ksshaskpass: Wait for the resolution of the libkscreen transition
before migrating to testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Processing control commands:
> tag -1 pending
Bug #1027882 [src:rapiddisk] rapiddisk: please switch to B-D: dh-sequence-dkms
(or dh-dkms)
Added tag(s) pending.
> tag 1029266 pending
Bug #1029266 [rapiddisk-dkms] rapiddisk-dkms: module fails to build for Linux
6.1: error: ‘struct dm_io_request’ h
Your message dated Tue, 31 Jan 2023 13:32:52 +
with message-id
and subject line Bug#1030109: fixed in zfp 1.0.0-6
has caused the Debian Bug report #1030109,
regarding zfp: misses versioned dependencies on numpy
to be marked as done.
This means that you claim that the problem has been dealt wi
On Tue, 31 Jan 2023 13:23:12 +0100 gus wrote:
Related: caused by a bug in python3-sip 6.7.6:
https://www.riverbankcomputing.com/pipermail/pyqt/2023-January/045137.html
https://www.riverbankcomputing.com/pipermail/pyqt/2023-January/045138.html
On 31/01/2023, Jakub Wilk wrote:
> Package: python
Your message dated Tue, 31 Jan 2023 13:24:02 +
with message-id
and subject line Bug#1029443: fixed in nbsdgames 5-4
has caused the Debian Bug report #1029443,
regarding nbsdgames: Error when purging the package
to be marked as done.
This means that you claim that the problem has been dealt wi
Processing commands for cont...@bugs.debian.org:
> forwarded 1029570 https://github.com/andmarti1424/sc-im/issues/50
Bug #1029570 [sc-im] sc-im: debian/copyright file seems to be inaccurate
Set Bug forwarded-to-address to
'https://github.com/andmarti1424/sc-im/issues/50'.
> thanks
Stopping proces
Your message dated Tue, 31 Jan 2023 12:57:26 +
with message-id
and subject line Bug#1028838: fixed in maven-remote-resources-plugin 3.0.0-1
has caused the Debian Bug report #1028838,
regarding maven-remote-resources-plugin: FTBFS: make: *** [debian/rules:6:
build] Error 25
to be marked as don
Package: ca-certificates-java
Version: 20230103
Severity: serious
ca-certificates-java fails to install with all dependencies fullfilled:
| Setting up ca-certificates-java (20230103) ...
| Exception in thread "main" java.lang.InternalError: Error loading
java.security file
| at java.base/j
On 31/01/2023 11:22, Andreas Tille wrote:
Dear Emmanuel,
could you simply push your patch and we can see the build log in
Salsa CI?
I just pushed both (VTK9 compatibility and dicom component disability)
to salsa (in the main branch, hopefully that's ok)
Kind regards
Processing commands for cont...@bugs.debian.org:
> forwarded 1029266 https://github.com/pkoutoupis/rapiddisk/pull/145
Bug #1029266 [rapiddisk-dkms] rapiddisk-dkms: module fails to build for Linux
6.1: error: ‘struct dm_io_request’ has no member named ‘bi_op’
Set Bug forwarded-to-address to
'http
Your message dated Tue, 31 Jan 2023 12:22:06 +
with message-id
and subject line Bug#1027440: fixed in kamailio 5.6.3-1
has caused the Debian Bug report #1027440,
regarding kamailio: FTBFS with Python 3.11 as default version
to be marked as done.
This means that you claim that the problem has
Related: caused by a bug in python3-sip 6.7.6:
https://www.riverbankcomputing.com/pipermail/pyqt/2023-January/045137.html
https://www.riverbankcomputing.com/pipermail/pyqt/2023-January/045138.html
On 31/01/2023, Jakub Wilk wrote:
> Package: python3-opensnitch-ui
> Version: 1.5.3-1
> Severity: gr
Control: tag -1 pending
Hello,
Bug #1028838 in maven-remote-resources-plugin 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:
https://salsa.debian.org/java-team/maven-remote-resources-p
Processing control commands:
> tag -1 pending
Bug #1028838 [src:maven-remote-resources-plugin] maven-remote-resources-plugin:
FTBFS: make: *** [debian/rules:6: build] Error 25
Added tag(s) pending.
--
1028838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028838
Debian Bug Tracking System
Your message dated Tue, 31 Jan 2023 12:19:45 +
with message-id
and subject line Bug#1028471: fixed in cmucl 21d-2
has caused the Debian Bug report #1028471,
regarding FTBFS: error: variable length array declaration not allowed at file
scope
to be marked as done.
This means that you claim tha
Processing commands for cont...@bugs.debian.org:
> tags 1027203 + ftbfs
Bug #1027203 [src:qiskit-terra] qiskit-terra: autopkgtest fail with numpy/1.24.1
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027203: https://bugs.debian.org/cgi-bin/bu
Package: thunderbird
Followup-For: Bug #1030112
Dear Maintainer,
I just confirm that rolling back to v.102.6.0-1 solves the problem, by now:
$ sudo dpkg -i --force-depends ./thunderbird_102.6.0-1~deb10u1_amd64.deb
./thunderbird-l10n-it_102.6.0-1~deb10u1_all.deb ./libffi6_3.2.1-9_amd64.deb
Matt
Processing control commands:
> tag -1 pending
Bug #1028871 [src:djangorestframework] djangorestframework: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10
3.11" returned exit code 13
Added tag(s) pending.
--
1028871: https://bugs.debian.org/cgi-bin/bugreport
Control: tag -1 pending
Hello,
Bug #1028871 in djangorestframework 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:
https://salsa.debian.org/python-team/packages/djangorestframework/-/co
Your message dated Tue, 31 Jan 2023 11:54:53 +
with message-id
and subject line Bug#1002983: fixed in hol-light 20230128-1
has caused the Debian Bug report #1002983,
regarding FTBFS with camlp5 8.00.02
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Tue, 31 Jan 2023 11:02:32 +
with message-id
and subject line Bug#1022180: fixed in shim 15.7-1
has caused the Debian Bug report #1022180,
regarding shim: non-standard gcc used for build (gcc-10)
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 31 Jan 2023 10:53:40 +
with message-id
and subject line Bug#1029960: fixed in feh 3.9.1-2
has caused the Debian Bug report #1029960,
regarding feh: autopkgtest failure: Can't locate X11/GUITest.pm
to be marked as done.
This means that you claim that the problem has bee
Hi Dominik,
thanks for your attempt to track this down. I'm wondering what might
happen if I refresh the pufferfish code in debian/external which I tried
in my last commit. Unfortunately this failed as well:
https://salsa.debian.org/med-team/salmon/-/jobs/3876351
Kind regards
Andreas.
A
Dear Emmanuel,
could you simply push your patch and we can see the build log in
Salsa CI?
Kind regards
Andreas.
Am Tue, Jan 31, 2023 at 08:28:12AM +0100 schrieb Emmanuel Promayon:
> Dear Andreas,
>
> I managed to patch the current CamiTK 5.0.2version to build with VTK9
> (vtk9-compatibility
Package: python3-opensnitch-ui
Version: 1.5.3-1
Severity: grave
Control: forwarded -1 https://github.com/evilsocket/opensnitch/issues/821
opensnitch-ui does not start:
$ opensnitch-ui
Themes not available. Install qt-material if you want to change GUI's
appearance: pip3 install qt-materia
Processing control commands:
> forwarded -1 https://github.com/evilsocket/opensnitch/issues/821
Bug #1030115 [python3-opensnitch-ui] opensnitch-ui: AttributeError: module
'PyQt5.Qt' has no attribute 'QItemDelegate'
Set Bug forwarded-to-address to
'https://github.com/evilsocket/opensnitch/issues/
Sebastian Andrzej Siewior dixit:
>It is bpo but if you look I'd you look at the files for the same
>version in bpo and sid you will see that sid skipped a few man pages
>while bpo created them.
Ouch!
That adds to the problems, of course. That makes fully resolving
this in all possible combinatio
Processing commands for cont...@bugs.debian.org:
> unarchive 988462
Bug #988462 {Done: Bastian Germann } [trac] trac: not ready
for Debian 11
Unarchived Bug 988462
> reopen 988462
Bug #988462 {Done: Bastian Germann } [trac] trac: not ready
for Debian 11
Bug reopened
Ignoring request to alter fix
On 31 January 2023 08:00:23 UTC, Thorsten Glaser wrote:
>Sebastian Andrzej Siewior dixit:
>
>>Then I will update the versions as suggested. My understanding was the
>>problem persists because the bpo version was not yet updated. The
>>version in sid did not ship the man-pages.
>
>The bpo version w
Package: thunderbird
Version: 1:102.7.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after last update from v.102.6.0-1 to v.102.7.1-1 OAuth 2.0 authentication
stopped working. When it tries to authenticate it gets error "OAuth 2.0
authentication server returned: {}
Sebastian Andrzej Siewior dixit:
>Then I will update the versions as suggested. My understanding was the
>problem persists because the bpo version was not yet updated. The
>version in sid did not ship the man-pages.
The bpo version was once in both sid and testing and this
is therefore a problem
101 - 164 of 164 matches
Mail list logo
