Hi Helmut,
* Helmut Grohne [2022-11-01 06:08]:
Package: systemd
Version: 252-1
Severity: serious
systemd fails to install in unstable:
mmdebstrap --verbose --variant apt --include systemd unstable /dev/null
| Setting up systemd (252-1) ...
| Created symlink
Processing commands for cont...@bugs.debian.org:
> forwarded 1022806 https://gitlab.freedesktop.org/drm/amd/-/issues/2237
Bug #1022806 [src:linux] linux-image-5.10.0-19-amd64: amggpu unbootable problem
persists
Set Bug forwarded-to-address to
Package: systemd
Version: 252-1
Severity: serious
systemd fails to install in unstable:
mmdebstrap --verbose --variant apt --include systemd unstable /dev/null
| Setting up systemd (252-1) ...
| Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service →
Processing control commands:
> reassign -1 t-coffee 13.45.0.4846264+dfsg-1
Bug #1023230 [src:t-coffee, src:libbio-tools-run-alignment-tcoffee-perl]
t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: test times
out after 2:47 hours
Bug reassigned from package 'src:t-coffee,
Control: reassign -1 t-coffee 13.45.0.4846264+dfsg-1
On Tue, 01 Nov 2022 09:12:43 +0900, Charles Plessy wrote:
> Le Mon, Oct 31, 2022 at 09:27:47PM +0100, Paul Gevers a écrit :
> >
> >
Your message dated Tue, 01 Nov 2022 02:34:48 +
with message-id
and subject line Bug#1022046: fixed in git 1:2.38.1-1
has caused the Debian Bug report #1022046,
regarding git: CVE-2022-39253 CVE-2022-39260
to be marked as done.
This means that you claim that the problem has been dealt with.
On 31/10/2022 16:17, Jonas Smedegaard wrote:
Quoting Peter Green (2022-10-31 03:39:28)
src:rust-rustls: fails to migrate to testing for too long: blocked by build
dependency
Specifically rust-async-std has taken some time to package, because of the
large number
of dependencies. There has
Le Mon, Oct 31, 2022 at 09:27:47PM +0100, Paul Gevers a écrit :
>
> https://ci.debian.net/data/autopkgtest/testing/arm64/libb/libbio-tools-run-alignment-tcoffee-perl/27686780/log.gz
>
> autopkgtest [11:59:24]: ERROR: timed out on command "su -s /bin/bash debci
Hi all,
I think that t-coffee
Your message dated Tue, 01 Nov 2022 00:06:52 +
with message-id
and subject line Bug#1023135: Removed package(s) from unstable
has caused the Debian Bug report #1023093,
regarding dleyna-connector-dbus: transition to gssdp/gupnp 1.6.0
to be marked as done.
This means that you claim that the
Your message dated Tue, 01 Nov 2022 00:06:52 +
with message-id
and subject line Bug#1023135: Removed package(s) from unstable
has caused the Debian Bug report #1023093,
regarding dleyna-connector-dbus: transition to gssdp/gupnp 1.6.0
to be marked as done.
This means that you claim that the
Your message dated Tue, 01 Nov 2022 00:06:52 +
with message-id
and subject line Bug#1023135: Removed package(s) from unstable
has caused the Debian Bug report #1023093,
regarding dleyna-connector-dbus: transition to gssdp/gupnp 1.6.0
to be marked as done.
This means that you claim that the
Your message dated Tue, 01 Nov 2022 00:06:06 +
with message-id
and subject line Bug#1023134: Removed package(s) from unstable
has caused the Debian Bug report #1022011,
regarding dleyna-server: transition to gssdp/gupnp 1.6.0
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 01 Nov 2022 00:05:35 +
with message-id
and subject line Bug#1023133: Removed package(s) from unstable
has caused the Debian Bug report #1022010,
regarding dleyna-renderer: transition to gssdp/gupnp 1.6.0
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 01 Nov 2022 00:04:39 +
with message-id
and subject line Bug#1023128: Removed package(s) from unstable
has caused the Debian Bug report #922579,
regarding FTBFS against opencv 4.0.1 (exp)
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 01 Nov 2022 00:04:39 +
with message-id
and subject line Bug#1023128: Removed package(s) from unstable
has caused the Debian Bug report #1023173,
regarding freeture: not installable, depends on libaravis-0.6-0
to be marked as done.
This means that you claim that the
Your message dated Tue, 01 Nov 2022 00:03:39 +
with message-id
and subject line Bug#1023062: Removed package(s) from unstable
has caused the Debian Bug report #1018774,
regarding sockjs-client: Deprecated, replaced by node-sockjs
to be marked as done.
This means that you claim that the
Your message dated Tue, 01 Nov 2022 00:05:08 +
with message-id
and subject line Bug#1023131: Removed package(s) from unstable
has caused the Debian Bug report #1022009,
regarding dleyna-core: transition to gssdp/gupnp 1.6.0
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 01 Nov 2022 00:01:57 +
with message-id
and subject line Bug#1023033: Removed package(s) from unstable
has caused the Debian Bug report #1023030,
regarding pysha3: Affected by CVE-2022-37454, unmaintained, remove from Debian?
to be marked as done.
This means that you
Hello Paul,
thanks for reporting the issue, I've investigated and this is an Assimp
problem that I've reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023212
The big endian architecture may be the root of the issue, thanks for
pointing that out.
Best Regards,
François
https://github.com/kravietz/pam_tacplus/releases/tag/v1.7.0
libpam-tacplus (1.7.0-1) unstable; urgency=medium
* libtac: Refactored the complex and overengineered TACACS+ session
id generation,
replacing it with getrandom(2).
* libtac: gnulib now provides implementation of missing
Processing commands for cont...@bugs.debian.org:
> reassign 1021078 src:celery
Bug #1021078 [src:billiard, src:celery] billiard breaks celery autopkgtest: 48
failed
Bug reassigned from package 'src:billiard, src:celery' to 'src:celery'.
No longer marked as found in versions billiard/4.0.2-1 and
Processing commands for cont...@bugs.debian.org:
> retitle 1020100 projectile FTBFS with emacs 28
Bug #1020100 [src:projectile] projectile: FTBFS: make: *** [debian/rules:4:
binary] Error 25
Changed Bug title to 'projectile FTBFS with emacs 28' from 'projectile: FTBFS:
make: ***
On Fri, 28 Oct 2022 20:26:55 +0200 Gert wrote:
> 5.19.0-0.deb11.2-amd64 works fine at first glance.
I am also affected and i also tried this kernel and it works as you can
read here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042#160
I also filed a new drm bug here:
On Thu, 27 Oct 2022 19:12:43 + inasprecali
wrote:
> I think bug 1022806 is a recent one referring to 5.10.149-2
> specifically, which is about this same issue. I don't think there
> is a need to report yet another bug about it.
Ok, then i switch to 1022806 too. I already created a new drm
Processing commands for cont...@bugs.debian.org:
> forwarded 1020180
> https://github.com/abo-abo/swiper/commit/23bdb5ab7003694aa880655d092fa9c321a31bb3
Bug #1020180 [src:emacs-ivy] emacs-ivy: FTBFS: make: *** [debian/rules:4:
binary] Error 25
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> tags 1020189 + fixed-upstream
Bug #1020189 [src:helpful-el] helpful-el: FTBFS: make: *** [debian/rules:4:
binary] Error 25
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020189:
Processing control commands:
> block 1020178 by -1
Bug #1020178 {Done: Lev Lamberov } [src:esup-el] esup-el:
FTBFS: (file-missing "Cannot open load file" "No such file or directory"
"comp")
1020178 was not blocked by any bugs.
1020178 was not blocking any bugs.
Added blocking bug(s) of
Control: block 1020178 by -1
On Mon, Oct 31, 2022 at 09:04:04PM +0100, Paul Gevers wrote:
>...
> With a recent upload of esup-el the autopkgtest of esup-el fails in testing
> when that autopkgtest is run with the binary packages of esup-el from
> unstable. It passes when run with only packages
Processing control commands:
> severity -1 important
Bug #1023192 [src:linux] linux-image-6.0.0-2-amd64: Bluetooth no longer works:
hci0: Reading Intel version command failed (-110)
Severity set to 'important' from 'grave'
> tags -1 + moreinfo
Bug #1023192 [src:linux] linux-image-6.0.0-2-amd64:
Control: severity -1 important
Control: tags -1 + moreinfo
Hi Vincent,
On Mon, Oct 31, 2022 at 01:09:31PM +0100, Vincent Lefevre wrote:
> Package: src:linux
> Version: 6.0.5-1
> Severity: grave
> Justification: renders package unusable
>
> (Setting to grave because Bluetooth is a major
Package: dracut
Version: 056-3
Severity: critical
Tags: patch upstream
Justification: breaks the whole system
Forwarded:
https://github.com/dracutdevs/dracut/commit/79f9d9e1c29a9c8fc046ab20765e5bde2aaa3428
Dear Maintainer,
grep is missing failling with lvm main partition.
Could you apply patch
Your message dated Mon, 31 Oct 2022 21:19:41 +
with message-id
and subject line Bug#1023153: fixed in fq 0.0.9-2
has caused the Debian Bug report #1023153,
regarding fq FTBFS: missing build dependencies?
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:
> retitle 1022355 /usr/bin/msgfmt: cannot locate ITS rules for
> policy/org.freedesktop.color.policy.in
Bug #1022355 [src:colord] colord: FTBFS:
../src/sensors/argyll/cd-spawn.c:475:20: warning: Deprecated pre-processor
symbol: replace with
Processing control commands:
> fixed -1 1.0.2-1
Bug #1023238 [src:libdecaf] libdecaf please migrate to python3
Marked as fixed in versions libdecaf/1.0.2-1.
--
1023238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Source: libdecaf
Version: 1.0.1-2
Severity: serious
Justification: rt
Control: fixed -1 1.0.2-1
Dear maintainers,
If I didn't make a mistake, wand is keeping python2.7 in the key package
set because it (Build-)Depends on it. We're trying hard to remove
python2.7 before the bookworm release.
Source: openjdk-11
Version: 11.0.4+11-1
Severity: serious
Justification: should not migrate to testing or stable any more
openjdk-17 is now the default JDK, but openjdk-11 is still required for
bootstrapping JVM-based languages like Kotlin or Scala in unstable.
Therefore the package should no
Source: cimg
Version: 3.1.6+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package cimg, great. However,
it fails everywhere but on amd64. Currently this failure is blocking the
migration to
Source: t-coffee, libbio-tools-run-alignment-tcoffee-perl
Control: found -1 t-coffee/13.45.0.4846264+dfsg-1
Control: found -1 libbio-tools-run-alignment-tcoffee-perl/1.7.4-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
Processing control commands:
> found -1 t-coffee/13.45.0.4846264+dfsg-1
Bug #1023230 [src:t-coffee, src:libbio-tools-run-alignment-tcoffee-perl]
t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: test times
out after 2:47 hours
Marked as found in versions
Source: f3d
Version: 1.3.1+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of f3d the autopkgtest of f3d fails in testing when
that autopkgtest is run with the binary packages of f3d from unstable.
It passes when run with
Source: breezy
Version: 3.3.0+bzr7661-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of breezy the autopkgtest of breezy fails in
testing when that autopkgtest is run with the binary packages of breezy
from unstable. It
Source: pg-fact-loader
Version: 1.7.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of pg-fact-loader the autopkgtest of pg-fact-loader
fails in testing when that autopkgtest is run with the binary packages
of pg-fact-loader
Source: esup-el
Version: 0.7.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of esup-el the autopkgtest of esup-el fails in
testing when that autopkgtest is run with the binary packages of esup-el
from unstable. It passes
Source: strongswan
Version: 5.9.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of strongswan the autopkgtest of strongswan fails
in testing when that autopkgtest is run with the binary packages of
strongswan from unstable.
Source: python-xarray
Version: 2022.10.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of python-xarray the autopkgtest of python-xarray
fails in testing on s390x when that autopkgtest is run with the binary
packages of
Processing commands for cont...@bugs.debian.org:
> forwarded 1022681 https://github.com/yesodweb/clientsession/issues/37
Bug #1022681 [src:haskell-clientsession] haskell-clientsession build depends on
haskell-cipher-aes and haskell-cprng-aes
Set Bug forwarded-to-address to
Source: pd-flext
Version: 0.6.1-3
Severity: serious
Control: close -1 0.6.2-1
Tags: sid bookworm
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 60 days as
Processing control commands:
> close -1 0.6.2-1
Bug #1023220 [src:pd-flext] src:pd-flext: fails to migrate to testing for too
long: autopkgtest failure on armel and armhf
Marked as fixed in versions pd-flext/0.6.2-1.
Bug #1023220 [src:pd-flext] src:pd-flext: fails to migrate to testing for too
Processing control commands:
> close -1 3.0.18.12.dfsg1-1
Bug #1023219 [src:psychtoolbox-3] src:psychtoolbox-3: fails to migrate to
testing for too long: uploader built arch:all binaries
Marked as fixed in versions psychtoolbox-3/3.0.18.12.dfsg1-1.
Bug #1023219 [src:psychtoolbox-3]
Source: psychtoolbox-3
Version: 3.0.18.9.dfsg1-1
Severity: serious
Control: close -1 3.0.18.12.dfsg1-1
Tags: sid bookworm pending
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
Your message dated Mon, 31 Oct 2022 18:35:03 +
with message-id
and subject line Bug#945139: fixed in pipenv 2022.10.25+ds2-1
has caused the Debian Bug report #945139,
regarding pipenv: update to latest pipenv
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 31 Oct 2022 18:35:03 +
with message-id
and subject line Bug#1012124: fixed in pipenv 2022.10.25+ds2-1
has caused the Debian Bug report #1012124,
regarding pipenv: Pipenv 11.9.0-2 fails with python3.10, which is the default
python3 in sid
to be marked as done.
This
Your message dated Mon, 31 Oct 2022 18:35:03 +
with message-id
and subject line Bug#1019714: fixed in pipenv 2022.10.25+ds2-1
has caused the Debian Bug report #1019714,
regarding pipenv: Contains non-source file
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id
and subject line fixed
has caused the Debian Bug report #1021857,
regarding bpftrace: FTBFS: make[1]: *** [debian/rules:7:
override_dh_auto_configure] Error 2
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id
and subject line fixed
has caused the Debian Bug report #1021857,
regarding ccls: FTBFS: make[1]: *** [debian/rules:18:
override_dh_auto_configure] Error 2
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id
and subject line fixed
has caused the Debian Bug report #1021857,
regarding cvise: FTBFS: make[1]: *** [debian/rules:13:
override_dh_auto_configure] Error 2
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id
and subject line fixed
has caused the Debian Bug report #1021857,
regarding irony-mode: FTBFS: make: *** [debian/rules:8: binary] Error 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id
and subject line fixed
has caused the Debian Bug report #1021857,
regarding qt6-tools: FTBFS: The imported target "sancov" references the file
"/usr/lib/llvm-14/bin/sancov" but this file does not exist.
to be marked as done.
Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id
and subject line fixed
has caused the Debian Bug report #1021857,
regarding doxygen: FTBFS: The imported target "sancov" references the file
"/usr/lib/llvm-14/bin/sancov" but this file does not exist
to be marked as done.
This
Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id
and subject line fixed
has caused the Debian Bug report #1021857,
regarding iwyu: FTBFS: The imported target "sancov" references the file
"/usr/lib/llvm-14/bin/sancov" but this file does not exist
to be marked as done.
This
Your message dated Mon, 31 Oct 2022 19:28:59 +0100
with message-id
and subject line fixed
has caused the Debian Bug report #1021857,
regarding llvm-14-dev: CMake Error in LLVMExports.cmake: The imported target
"sancov" references the file "/usr/lib/llvm-14/bin/sancov" but this file does
not
Processing commands for cont...@bugs.debian.org:
> fixed 1021857 1:14.0.6-7
Bug #1021857 [llvm-14-dev] llvm-14-dev: CMake Error in LLVMExports.cmake: The
imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but
this file does not exist.
Bug #1022334 [llvm-14-dev]
fixed 1021857 1:14.0.6-7
thanks
I think the issue is fixed but if someone knows cmake well. please let
me know :)
Cheers
S
Processing commands for cont...@bugs.debian.org:
> severity 981938 serious
Bug #981938 [src:lombok-ast] lombok-ast: FTBFS with OpenJDK 17: module
jdk.compiler does not "opens com.sun.tools.javac.processing" to unnamed module
Severity set to 'serious' from 'important'
> severity 982026 serious
Your message dated Mon, 31 Oct 2022 17:35:44 +
with message-id
and subject line Bug#1019682: fixed in schleuder 4.0.3-6
has caused the Debian Bug report #1019682,
regarding schleuder: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect(error).to be_empty
to be
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:cypari2
> # 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:
> tags 1019682 + pending
Bug #1019682 [src:schleuder] schleuder: FTBFS with ruby3.1: ERROR: Test
"ruby3.1" failed: Failure/Error: expect(error).to be_empty
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you
Processing control commands:
> retitle -1 libow-php7: misnomer
Bug #1003472 [src:owfs] owfs: fails to build with php8.1
Changed Bug title to 'libow-php7: misnomer' from 'owfs: fails to build with
php8.1'.
> tags -1 - ftbfs
Bug #1003472 [src:owfs] libow-php7: misnomer
Removed tag(s) ftbfs.
>
Control: retitle -1 libow-php7: misnomer
Control: tags -1 - ftbfs
Control: severity -1 minor
The package should build with swig 4.1.0.
But with a build based on PHP 8, the libow-php7 package is a misnomer.
Quoting Peter Green (2022-10-31 03:39:28)
> > src:rust-rustls: fails to migrate to testing for too long: blocked by build
> > dependency
>
> Specifically rust-async-std has taken some time to package, because of the
> large number
> of dependencies. There has been effort on this front both by
Your message dated Mon, 31 Oct 2022 16:11:37 +
with message-id
and subject line Bug#1017223: fixed in xrayutilities 1.7.4-1
has caused the Debian Bug report #1017223,
regarding xrayutilities: FTBFS: distutils.errors.DistutilsError: Command
'['/usr/bin/python3.10', '-m', 'pip',
Your message dated Mon, 31 Oct 2022 16:04:53 +
with message-id
and subject line Bug#105: fixed in libxml2 2.9.14+dfsg-1.1
has caused the Debian Bug report #105,
regarding libxml2: CVE-2022-40304: dict corruption caused by entity reference
cycles
to be marked as done.
This means that
Your message dated Mon, 31 Oct 2022 16:04:53 +
with message-id
and subject line Bug#104: fixed in libxml2 2.9.14+dfsg-1.1
has caused the Debian Bug report #104,
regarding libxml2: CVE-2022-40303: Integer overflows with XML_PARSE_HUGE
to be marked as done.
This means that you claim
Your message dated Mon, 31 Oct 2022 15:40:59 +
with message-id
and subject line Bug#1022333: fixed in zookeeper 3.8.0-9
has caused the Debian Bug report #1022333,
regarding zookeeper: FTBFS: make[1]: *** [debian/rules:20:
override_dh_auto_build-indep] Error 25
to be marked as done.
This
Your message dated Mon, 31 Oct 2022 15:39:12 +
with message-id
and subject line Bug#1023031: fixed in rust-async-std 1.12.0-6
has caused the Debian Bug report #1023031,
regarding rust-async-std: autopkgtest failure.
to be marked as done.
This means that you claim that the problem has been
Hi,
On 2022-10-30 06:31:27 -0700, Sean Whitton wrote:
> I've backported a couple of patches from upstream related to native
> compilation, now, so would you be able to test again with the latest
> upload? Thanks.
If you mean 1:28.2+1-3, I still got the same issue. But it seems
that after a
Package: sssd-ipa
Version: 2.7.4-1+b1
Severity: critical
Justification: breaks the whole system
After upgrade of samba-libs syslog has messages like
... sssd[448823]: /usr/libexec/sssd/sssd_pac: error while loading shared
libraries: libndr.so.2: cannot open shared object file: No such file or
Processing commands for cont...@bugs.debian.org:
> forwarded 1007026 https://github.com/rustwasm/weedle/issues/51
Bug #1007026 [rust-weedle] rust-weedle - needs nom 5
Set Bug forwarded-to-address to 'https://github.com/rustwasm/weedle/issues/51'.
> thanks
Stopping processing here.
Please contact
Processing control commands:
> forwarded -1
> https://github.com/supercollider/supercollider/commit/b9dd70c4c8d61c93d7a70645e0bd18fa76e6834e
Bug #1019995 [src:supercollider] supercollider: FTBFS: sndfile.h:356:33: error:
conflicting declaration ‘typedef struct sf_private_tag SNDFILE’
Set Bug
Control: forwarded -1
https://github.com/supercollider/supercollider/commit/b9dd70c4c8d61c93d7a70645e0bd18fa76e6834e
thanks
Dear Maintainer,
After applying upstream commit, I was able to build your package in a sid
chroot environment.
Kind Regards
Your message dated Mon, 31 Oct 2022 13:06:51 +
with message-id
and subject line Bug#1003479: fixed in swig 4.1.0-0.1
has caused the Debian Bug report #1003479,
regarding swig: Missing support for php8.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
I have uploaded the new version as NMU 4.1.0-0.1.
The source is also pushed to the git repo.
Your message dated Mon, 31 Oct 2022 12:49:14 +
with message-id
and subject line Bug#1022450: fixed in logbook 1.5.3-5.1
has caused the Debian Bug report #1022450,
regarding logbook: FTBFS: distutils.errors.DistutilsClassError: command class
must subclass Command
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> reopen 996130
Bug #996130 {Done: Tobias Frost } [src:clickhouse] clickhouse
FTBFS with gcc 11
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug
On 2022-10-31 13:09:31 +0100, Vincent Lefevre wrote:
> Package: src:linux
> Version: 6.0.5-1
> Severity: grave
> Justification: renders package unusable
>
> (Setting to grave because Bluetooth is a major component.)
>
> Bluetooth no longer works at all.
Bluetooth works again after downgrading
Package: src:linux
Version: 6.0.5-1
Severity: grave
Justification: renders package unusable
(Setting to grave because Bluetooth is a major component.)
Bluetooth no longer works at all.
zira:~> journalctl -b -g bluetooth
Oct 31 12:55:16 zira kernel: Bluetooth: Core ver 2.22
Oct 31 12:55:16 zira
Your message dated Mon, 31 Oct 2022 12:05:50 +
with message-id
and subject line Bug#1006049: fixed in botch 0.24-1
has caused the Debian Bug report #1006049,
regarding botch: FTBFS: ocamlfind: Package `dose3.doseparse' not found
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #1023040 [src:nbconvert] nbconvert: downloads artifacts during build
Ignoring request to alter tags of bug #1023040 to the same tags previously set
--
1023040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023040
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #1023040 in nbconvert 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:
Dear Florian,
On 18/10/2022 13:01, Florian Schlichting wrote:
On Mon, Oct 10, 2022 at 12:46:57PM +0200, Benno Overeinder wrote:
Unfortunately the problem persists after updating to davical 1.1.11-1. I see
the same messages in the Apache2 error.log as previously reported.
looking at your
Your message dated Mon, 31 Oct 2022 10:50:49 +
with message-id
and subject line Bug#1023026: fixed in gavodachs 2.6+dfsg-2
has caused the Debian Bug report #1023026,
regarding gavodachs: Fails it autopkgtest
to be marked as done.
This means that you claim that the problem has been dealt
close 1022487 3.5-2
thanks
--
Mit freundlichen GrüÃen,
Christoph Berg
--
Senior Consultant, Tel.: +49 2166 9901 187
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Geoff Richardson, Peter
Package: veusz
Version: 3.3.1-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: didi...@gmail.com
Dear Maintainer,
veusz does not start when launched from the GUI or from the CLI.
Here is the output of trying to run veusz from a terminal:
$ LANG=C veusz
Warning: Ignoring
Processing commands for cont...@bugs.debian.org:
> close 1022487 3.5-2
Bug #1022487 [src:pgq-node] pgq-node: FTBFS: Error: debian/control needs
updating from debian/control.in. Run 'pg_buildext updatecontrol'.
Marked as fixed in versions pgq-node/3.5-2.
Bug #1022487 [src:pgq-node] pgq-node:
Your message dated Mon, 31 Oct 2022 10:36:39 +
with message-id
and subject line Bug#1023147: fixed in python-asdf 2.13.0-2
has caused the Debian Bug report #1023147,
regarding python3-asdf: ships /usr/lib/python3/dist-packages/docs/Makefile etc.
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> tags 979101 + pending
Bug #979101 [devtodo] Legally problematic GPL-3+ readline dependency
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979101:
Processing control commands:
> tags -1 -moreinfo
Bug #1023124 [systemd] libsystemd-shared-251.so: cannot open shared object file
Removed tag(s) moreinfo.
> close -1
Bug #1023124 [systemd] libsystemd-shared-251.so: cannot open shared object file
Marked Bug as done
--
1023124:
Control: tags -1 -moreinfo
Control: close -1
On Sun, 30 Oct 2022 14:56:08 +0100 Salvo Tomaselli
wrote:
> systemd-machine-id-setup: /usr/bin/systemd-machine-id-setup
> /bin/systemd-machine-id-setup
> /usr/share/man/man1/systemd-machine-id-setup.1.gz
>
>
> stat /usr/bin/systemd-machine-id-setup
Source: microprofile
Version: 3.1+ds-2
Severity: serious
The files src/microprofile*.html contain JavaScript code from
https://gist.github.com/mjackson/5311256
which never got a license even though people have asked for it. So please
exclude them.
The fixed package is in unstable but testing migration is prevented by
gcc-12 FTBFS on mips64el (#1022991).
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
1 - 100 of 108 matches
Mail list logo
