Your message dated Tue, 10 Sep 2024 06:55:22 +
with message-id
and subject line Bug#1080284: fixed in python-xstatic 1.0.3-3
has caused the Debian Bug report #1080284,
regarding FTBFS with setuptools >= 72: error: invalid command 'test'
to be marked as done.
This means that you claim that the
Hi,
I've uploaded a fixed package to DELAYED/3.
Please let me know if I should delay further.
The debdiff is attached. Please include that in your next upload.
Regards,
Michael
diff -Nru snapper-0.10.6/debian/changelog snapper-0.10.6/debian/changelog
--- snapper-0.10.6/debian/changelog
Your message dated Tue, 10 Sep 2024 08:43:01 +0200
with message-id
and subject line Re: Bug#1081222: yubikey-manager: python3-pyscard 2.1.0 seems
to break yubikey-manager
has caused the Debian Bug report #1081222,
regarding yubikey-manager: python3-pyscard 2.1.0 seems to break yubikey-manager
to
Processing control commands:
> tag -1 pending
Bug #1080284 [src:python-xstatic] FTBFS with setuptools >= 72: error: invalid
command 'test'
Added tag(s) pending.
--
1080284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pr
Control: tag -1 pending
Hello,
Bug #1080284 in python-xstatic 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/openstack-team/xstatic/python-xstatic/-/commit/1b7
Your message dated Tue, 10 Sep 2024 07:35:41 +0100
with message-id
and subject line Re: ddcui: FTBFS on all archs, unmaintained
has caused the Debian Bug report #1081112,
regarding ddcui: FTBFS on all archs, unmaintained
to be marked as done.
This means that you claim that the problem has been d
Processing commands for cont...@bugs.debian.org:
> fixed 1081112 0.5.4-1
Bug #1081112 [src:ddcui] ddcui: FTBFS on all archs, unmaintained
Marked as fixed in versions ddcui/0.5.4-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1081112: https://bugs.debian.org/cg
Your message dated Tue, 10 Sep 2024 06:22:02 +
with message-id
and subject line Bug#1080230: fixed in python-django-swapper 1.3.0-2
has caused the Debian Bug report #1080230,
regarding FTBFS with setuptools 72: django.core.exceptions.ImproperlyConfigured
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> affects 1081252 libmptcpd3 mptcpd mptcpd-plugins
Bug #1081252 [libell0] [libell0] missing symbol breaks iwd
Added indication that 1081252 affects libmptcpd3, mptcpd, and mptcpd-plugins
> thanks
Stopping processing here.
Please contact me if you n
On Fri, 12 Jul 2024 23:36:31 + Daniel Markstedt
wrote:
>
> Apologies for the hold-up. Over the last several weeks, I have worked
on a release in Salsa that addresses this bug, and others.
> Currently putting the final touches, after which I expect my co-
maintainer to sign off on and upload
Hi!
To allow testing-migration, I did a followup no-changes source-only upload.
debdiff is attached.
Regards,
Michael
diff -Nru nut-2.8.1/debian/changelog nut-2.8.1/debian/changelog
--- nut-2.8.1/debian/changelog 2024-08-17 20:08:31.0 +0200
+++ nut-2.8.1/debian/changelog 2024-09-10 08:
Have filed upstream issue here:
https://github.com/santhoshtr/sfst/issues/31
Source: libreoffice
Version: 4:24.2.6-1
Severity: serious
Tags: FTBFS, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear libreoffice Maintainer,
The package libreoffice build failed on arch riscv64 . The crucial buildd
log below:
```
test
Your message dated Tue, 10 Sep 2024 03:19:30 +
with message-id
and subject line Bug#1074925: fixed in dvi2dvi 2.0alpha-12
has caused the Debian Bug report #1074925,
regarding dvi2dvi: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
My dev machine is currently DOA, and I'm still working on rebuilding it.
On Sat, Sep 7, 2024 at 3:39 AM Salvatore Bonaccorso
wrote:
> Hi Jeremy,
>
> On Thu, Aug 01, 2024 at 07:22:34AM +0200, Salvatore Bonaccorso wrote:
> > Hi Jeremy,
> >
> > On Sun, Jun 30, 2024 at 02:47:41PM +0200, Salvatore Bo
Package: libell0
Version: 0.69-1
Severity: critical
I just updated my Sid install, wifi (iwd based) was broken afterwards.
Found the following in journalctl indicating that the libell0 update
was responsible. Booted a recovery disc and had to downgrade both
libell0 and iwd to versions from testing
Your message dated Mon, 09 Sep 2024 23:50:12 +
with message-id
and subject line Bug#1080280: fixed in python-flask-seeder 1.2.0-4
has caused the Debian Bug report #1080280,
regarding FTBFS with setuptools >= 72: error: invalid command 'test'
to be marked as done.
This means that you claim tha
Processing control commands:
> tag -1 pending
Bug #1080280 [src:python-flask-seeder] FTBFS with setuptools >= 72: error:
invalid command 'test'
Added tag(s) pending.
--
1080280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080280
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Your message dated Mon, 09 Sep 2024 23:34:09 +
with message-id
and subject line Bug#1081025: fixed in epoptes 23.08-2
has caused the Debian Bug report #1081025,
regarding epoptes: implicit dependency on removed python3-distutils
to be marked as done.
This means that you claim that the problem
Control: tag -1 pending
Hello,
Bug #1080280 in python-flask-seeder 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/python-flask-seeder/-/co
Your message dated Tue, 10 Sep 2024 00:25:24 +0100
with message-id
and subject line Re: Bug#1071881: pyusid: FTBFS: unsatisfiable
build-dependencies
has caused the Debian Bug report #1071881,
regarding pyusid: FTBFS: unsatisfiable build-dependencies
to be marked as done.
This means that you clai
Your message dated Mon, 09 Sep 2024 23:20:08 +
with message-id
and subject line Bug#1074965: fixed in freecdb 0.78
has caused the Debian Bug report #1074965,
regarding freecdb: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Tue, 10 Sep 2024 00:17:09 +0100
with message-id
and subject line Re: Bug#1071880: python-rosettasciio: FTBFS: unsatisfiable
build-dependencies
has caused the Debian Bug report #1071880,
regarding python-rosettasciio: FTBFS: unsatisfiable build-dependencies
to be marked as done.
Package: python3-pyflow
Version: 1.1.20-5
Severity: grave
Tags: upstream
Justification: renders the package unusable
Control: forwarded -1 https://github.com/Illumina/pyflow/issues/20
Hi,
While working on #1080766, I attempted to introduce proper test
support in src:python-pyflow. Trying to get
Processing control commands:
> forwarded -1 https://github.com/Illumina/pyflow/issues/20
Bug #1081243 [python3-pyflow] python3-pyflow: helloWorld and other examples not
runnable, possibly since python2 dropped
Set Bug forwarded-to-address to 'https://github.com/Illumina/pyflow/issues/20'.
--
10
Control: retitle -1 freecontact: ftbfs: Illegal instruction error on armel
Control: tags -1 + unreproducible moreinfo
Control: severity -1 normal
Hi Lucas,
Relevant part of the build error in freecontact on armel looks
to be the below illegal instruction error:
> pod2man --utf8 -c 'User Commands
Processing control commands:
> retitle -1 freecontact: ftbfs: Illegal instruction error on armel
Bug #1069552 [src:freecontact] freecontact: FTBFS on armel: make[1]: ***
[Makefile:469: all-recursive] Error 1
Changed Bug title to 'freecontact: ftbfs: Illegal instruction error on armel'
from 'free
Hi Andreas
> That was a llvm-17 regresssion that got fixed today ;-)
> pocl just got built successfully on arm64 ;-)
brilliant news - thanks for the update
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@deb
On 9/9/24 22:23, Stuart Prescott wrote:
Another month has passed - is there something that others can help with
here?
That was a llvm-17 regresssion that got fixed today ;-)
pocl just got built successfully on arm64 ;-)
Andreas
Hi pocl maintainers!
Another month has passed - is there something that others can help with
here?
regards
Stuart
On 10/08/2024 17:05, Stuart Prescott wrote:
Hi pocl maintainers!
I see that 6.0-2 has failed to build on arm64 and therefore can't
migrate. It is also waiting for gcc-default
Your message dated Mon, 9 Sep 2024 22:13:44 +0200
with message-id <421d13f7-ea79-1bf9-d704-caf786f1d...@debian.org>
and subject line Re: Bug#1078750: pocl: FTBFS on arm64:
/usr/lib/llvm-17/bin/llc: error: unable to get target for 'unknown', see
--version and --triple.
has caused the Debian Bug re
Your message dated Mon, 09 Sep 2024 19:50:48 +
with message-id
and subject line Bug#1072402: fixed in blender 4.2.1+dfsg-1
has caused the Debian Bug report #1072402,
regarding blender: FTBFS with ffmpeg 7.0: FFMPEGReader.cpp:115:81: error:
‘struct AVCodecContext’ has no member named ‘channels
Your message dated Mon, 09 Sep 2024 19:34:13 +
with message-id
and subject line Bug#1073403: fixed in androguard 3.4.0~a1-15
has caused the Debian Bug report #1073403,
regarding androguard: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.12 3.11" returned exi
Your message dated Mon, 09 Sep 2024 19:34:13 +
with message-id
and subject line Bug#1072592: fixed in androguard 3.4.0~a1-15
has caused the Debian Bug report #1072592,
regarding androguard: FTBFS: module 'networkx' has no attribute 'write_gpickle'
to be marked as done.
This means that you cla
Your message dated Mon, 09 Sep 2024 19:36:27 +
with message-id
and subject line Bug#1060321: fixed in rust-secret-service 4.0.0-1
has caused the Debian Bug report #1060321,
regarding rust-secret-service: Depends: rust-aes-0.7 but rust-aes 0.8 is
available
to be marked as done.
This means tha
Your message dated Mon, 09 Sep 2024 19:12:10 +
with message-id
and subject line Bug#1075556: fixed in tcpspy 1.7d-16
has caused the Debian Bug report #1075556,
regarding tcpspy: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Mon, 09 Sep 2024 19:09:05 +
with message-id
and subject line Bug#1080146: fixed in kannel 1.4.5-18
has caused the Debian Bug report #1080146,
regarding kannel: FTBFS: configure: error: Couldnot find gethostbyname_r nor
gethostbyname functions
to be marked as done.
This mea
Your message dated Mon, 09 Sep 2024 18:35:04 +
with message-id
and subject line Bug#1074885: fixed in clipit 1.4.5+git20210313-3
has caused the Debian Bug report #1074885,
regarding clipit: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
Control: severity -1 important
Hi Sebastinas,
I think, it's rather unproductive to block newer LLVM versions from
testing, and now even actively removing them is not very cooperative. If
you keep out newer versions for the compiler out of testing, you reduce
the ability for users to test thes
Processing control commands:
> severity -1 important
Bug #1081194 [src:llvm-toolchain-19] llvm-toolchain-19: block migration to
testing: too many llvm-toolchain versions in testing
Severity set to 'important' from 'serious'
--
1081194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081194
D
Processing control commands:
> reassign -1 python3-nipype
Bug #1081079 [src:heudiconv] heudiconv: FTBFS: unsatisfiable build-depends
Bug reassigned from package 'src:heudiconv' to 'python3-nipype'.
No longer marked as found in versions heudiconv/1.1.6-1.
Ignoring request to alter fixed versions of
Control: reassign -1 python3-nipype
Control: retitle -1 python3-nipype: unsatisfiable dependency
Control: affects -1 heudiconv
Control: tags -1 + patch
Control: block -1 by 1064732
Hi,
The unsatisfiable build dependency python3-funcsigs originates
from the python3-nipype package. From quick insp
Your message dated Mon, 09 Sep 2024 16:32:08 +
with message-id
and subject line Bug#1072394: fixed in fcgiwrap 1.1.0-14+deb12u1
has caused the Debian Bug report #1072394,
regarding fcgiwrap: autopkgtest failures: The requested URL returned error: 500
to be marked as done.
This means that you
Your message dated Mon, 09 Sep 2024 16:32:09 +
with message-id
and subject line Bug#1076751: fixed in ikiwiki-hosting 0.20220716-2+deb12u1
has caused the Debian Bug report #1076751,
regarding ikiwiki-hosting: autopkgtest regression with git 2.45.2: dubious
ownership in repository at
'/var/li
Package: src:node-microsoft-fast
Version: 0~20240320+ds1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh bi
Your message dated Mon, 09 Sep 2024 16:04:10 +
with message-id
and subject line Bug#1080237: fixed in sphinxcontrib-programoutput 0.17-4
has caused the Debian Bug report #1080237,
regarding FTBFS with setuptools 72: error: invalid command 'test'
to be marked as done.
This means that you claim
Package: yubikey-manager
Version: 5.4.0-1
Severity: grave
X-Debbugs-Cc: hert...@debian.org
Control: forwarded -1 https://github.com/Yubico/yubikey-manager/issues/634
Hello, I am unable to use yubikey-manager in unstable right now...
$ ykman info
WARNING: Failed opening device
ERROR: Failed to con
Processing control commands:
> forwarded -1 https://github.com/Yubico/yubikey-manager/issues/634
Bug #1081222 [yubikey-manager] yubikey-manager: python3-pyscard 2.1.0 seems to
break yubikey-manager
Set Bug forwarded-to-address to
'https://github.com/Yubico/yubikey-manager/issues/634'.
--
10812
Your message dated Mon, 09 Sep 2024 15:24:47 +
with message-id
and subject line Bug#1080227: fixed in python-calmjs.types 1.0.1-4
has caused the Debian Bug report #1080227,
regarding FTBFS with setuptools 72: error: invalid command 'test'
to be marked as done.
This means that you claim that t
Your message dated Mon, 09 Sep 2024 15:24:39 +
with message-id
and subject line Bug#1080226: fixed in python-calmjs.parse 1.2.5-4
has caused the Debian Bug report #1080226,
regarding FTBFS with setuptools 72: error: invalid command 'test'
to be marked as done.
This means that you claim that t
Control: tag -1 pending
Hello,
Bug #1080237 in sphinxcontrib-programoutput 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/openstack-team/third-party/sphinxcon
Processing control commands:
> tag -1 pending
Bug #1080237 [src:sphinxcontrib-programoutput] FTBFS with setuptools 72: error:
invalid command 'test'
Added tag(s) pending.
--
1080237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080237
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Your message dated Mon, 09 Sep 2024 13:25:03 +
with message-id
and subject line Bug#1072607: fixed in python-django-test-migrations 1.3.0-3
has caused the Debian Bug report #1072607,
regarding python-django-test-migrations: FTBFS: FAIL Required test coverage of
100% not reached. Total coverag
The test failures with this symptom:
ResourceWarning: Unclosed
are related to the anyio bump to 4.4.0 - see:
https://github.com/encode/starlette/discussions/2603
no fix committed upstream yet.
Your message dated Mon, 9 Sep 2024 15:15:40 +0200
with message-id
and subject line Re: Bug#1079394: linux-image-6.10.6-amd64: causes cifs
regression, flatpak & ostree signature corruption
has caused the Debian Bug report #1079394,
regarding linux-image-6.10.6-amd64: causes cifs regression, flatpa
Processing control commands:
> fixed -1 3.4.0-4
Bug #1080514 [src:knot] knot: FTBFS on armel: insufficient atomics
Marked as fixed in versions knot/3.4.0-4.
--
1080514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
Control: fixed -1 3.4.0-4
I believe we managed to really fix this with upstream help in 3.4.0-4:
https://buildd.debian.org/status/logs.php?pkg=knot&ver=3.4.0-4&arch=armel
Cheers,
Jakub Ružička
Your message dated Mon, 09 Sep 2024 12:38:40 +
with message-id
and subject line Bug#1071057: fixed in sbws 1.9.0-2
has caused the Debian Bug report #1071057,
regarding sbws: prompting due to modified conffiles which were not modified by
the user: /etc/cron.d/sbws
to be marked as done.
This m
Processing control commands:
> severity -1 normal
Bug #1081014 [python3-zipp] Should python3-zipp be dropped in trixie?
Severity set to 'normal' from 'serious'
> tags -1 wontfix
Bug #1081014 [python3-zipp] Should python3-zipp be dropped in trixie?
Added tag(s) wontfix.
--
1081014: https://bugs.d
Control: severity -1 normal
Control: tags -1 wontfix
On Fri, Sep 06, 2024 at 11:39:44PM +0300, Adrian Bunk wrote:
> Looking at CVE-2024-5569 and the potential of future CVEs,
> I wonder whether there is any reason why reverse dependencies
> still need this package or whether they could use the ver
Processing commands for cont...@bugs.debian.org:
> close 1076875
Bug #1076875 [src:eclipse-jdt-debug] eclipse-jdt-debug: FTBFS: error: cannot
find symbol ID_RES_NAV
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1076875: https://bugs.debian.or
Your message dated Mon, 09 Sep 2024 11:49:08 +
with message-id
and subject line Bug#1076534: fixed in importlib-resources 6.4.4-1
has caused the Debian Bug report #1076534,
regarding src:importlib-resources: fails to migrate to testing for too long:
autopkgtest regression on s390x
to be marke
Your message dated Mon, 09 Sep 2024 11:00:06 +
with message-id
and subject line Bug#1080420: fixed in selinux-gui 3.7-2
has caused the Debian Bug report #1080420,
regarding python3-sepolicy has an undeclared file conflict
to be marked as done.
This means that you claim that the problem has be
Processing commands for cont...@bugs.debian.org:
> fixed 1076875 4.29-1
Bug #1076875 [src:eclipse-jdt-debug] eclipse-jdt-debug: FTBFS: error: cannot
find symbol ID_RES_NAV
Marked as fixed in versions eclipse-jdt-debug/4.29-1.
> thanks
Stopping processing here.
Please contact me if you need assis
Processing commands for cont...@bugs.debian.org:
> close 1076876
Bug #1076876 [src:eclipse-jdt-ui] eclipse-jdt-ui: FTBFS: error: cannot find
symbol ID_RES_NAV
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1076876: https://bugs.debian.org/cgi-
Processing commands for cont...@bugs.debian.org:
> fixed 1076876 4.29-1
Bug #1076876 [src:eclipse-jdt-ui] eclipse-jdt-ui: FTBFS: error: cannot find
symbol ID_RES_NAV
Marked as fixed in versions eclipse-jdt-ui/4.29-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
On Mon, Sep 09, 2024 at 11:15:58AM +0100, Colin Watson wrote:
> I've prepared an NMU for python-autopage (versioned as 0.4.0-3.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I should delay
> it longer.
This is also
https://salsa.debian.org/openstack-team/python/python-autopage/
Control: tags 1080278 + patch
Control: tags 1080278 + pending
Dear maintainer,
I've prepared an NMU for python-autopage (versioned as 0.4.0-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I should delay
it longer.
Regards,
--
Colin Watson (he/him)
Processing control commands:
> tags 1080278 + patch
Bug #1080278 [src:python-autopage] FTBFS with setuptools >= 72: error: invalid
command 'test'
Added tag(s) patch.
> tags 1080278 + pending
Bug #1080278 [src:python-autopage] FTBFS with setuptools >= 72: error: invalid
command 'test'
Added tag(s
Your message dated Mon, 09 Sep 2024 10:06:25 +
with message-id
and subject line Bug#1081191: fixed in knot 3.4.0-3
has caused the Debian Bug report #1081191,
regarding knot-exporter: there must be no subdirectories in /usr/sbin
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 09 Sep 2024 10:01:09 +
with message-id
and subject line Bug#1067790: fixed in nut 2.8.1-3.2
has caused the Debian Bug report #1067790,
regarding nut: move files to /usr (DEP17) and partially revert time64
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 09 Sep 2024 10:01:09 +
with message-id
and subject line Bug#1064670: fixed in nut 2.8.1-3.2
has caused the Debian Bug report #1064670,
regarding nut: flaky autopkgtest: Test daemons using PID files ... FAIL
to be marked as done.
This means that you claim that the probl
Your message dated Mon, 09 Sep 2024 09:52:35 +
with message-id
and subject line Bug#1081192: fixed in llvm-toolchain-19 1:19.1.0~++rc4-5
has caused the Debian Bug report #1081192,
regarding libllvm19: declares itself as MA: same but is not co-installable
to be marked as done.
This means that
Package: src:tuigreet
Version: 0.9.1-1
Severity: serious
Tags: sid trixie patch
[...]
dh_auto_test -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8']
[] ['-j8'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
d
Package: libc6-dev-amd64-cross
Version: 2.39-4cross1
Severity: serious
X-Debbugs-Cc: debian-cr...@lists.debian.org
Hi,
while trying to cross-build the next upload of my source package pico-sdk for
amd64 on my arm64 box in a clean unstable chroot with sbuild, I ran into the
following problem:
Ins
Upstream 6.10.9 does indeed seem to fix it.
Half a dozen runs of my reproducers yielded nothing but correct behavior.
Processing commands for cont...@bugs.debian.org:
> block 1078750 by 1077068
Bug #1078750 [src:pocl] pocl: FTBFS on arm64: Clang link test FAILED.
1078750 was not blocked by any bugs.
1078750 was blocking: 1079721
Added blocking bug(s) of 1078750: 1077068
>
End of message, stopping processing here.
Package: crowdsec
Version: all
Severity: critical
In the latest openssh-server package (testing & unstable),
"sshd-session" is used for many log messages, which breaks
crowdsec/hub/parsers/s01-parse/crowdsecurity/sshd-logs.yaml
filter: "evt.Parsed.program == 'sshd'"
As to the above snippet,
Hi,
On 2024-08-15 10:46, Andreas Beckmann wrote:
> /usr/lib/llvm-17/include/clang/Basic/TokenKinds.def:23:26: error: pasting
> "kw_" and "[" does not give a valid preprocessing token
>23 | #define KEYWORD(X,Y) TOK(kw_ ## X)
This is a LLVM 17 / GCC 14 regression:
https://bugs.debian.org/10770
Processing commands for cont...@bugs.debian.org:
> found 1081191 3.3.9-1
Bug #1081191 [knot-exporter] knot-exporter: there must be no subdirectories in
/usr/sbin
Marked as found in versions knot/3.3.9-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1081191: ht
Processing commands for cont...@bugs.debian.org:
> # Also affects testing
> found 1081191 3.3.9
Bug #1081191 [knot-exporter] knot-exporter: there must be no subdirectories in
/usr/sbin
There is no source info for the package 'knot-exporter' at version '3.3.9' with
architecture ''
Unable to make
Control: clone -1 -2
Control: reopen -2
Control: reassign -2 src:llvm-toolchain-19 1:19.1.0~++rc4-2
Control: retitle -2 llvm-toolchain-19: block migration to testing: too many
llvm-toolchain versions in testing
On 2024-04-14 12:49:40 +0200, Sebastian Ramacher wrote:
> Source: llvm-toolchain-18
>
Processing control commands:
> clone -1 -2
Bug #1068961 {Done: Sebastian Ramacher }
[src:llvm-toolchain-18] llvm-toolchain-18: block migration to testing: to many
llvm-toolchain versions in testing
Bug 1068961 cloned as bug 1081194
1081194 was blocked by: 1050069
1081194 was not blocking any bug
> libartbase/base/strlcpy.h:31:22: error: static declaration of 'strlcpy'
> follows non-static declaration
I just checked the build on arm64 porterbox: amdahl
Now the error string changed from above to the following below.
Seems like it's not so easy to fix this.
In file included from libar
Processing commands for cont...@bugs.debian.org:
> unarchive 1068961
Bug #1068961 {Done: Sebastian Ramacher }
[src:llvm-toolchain-18] llvm-toolchain-18: block migration to testing: to many
llvm-toolchain versions in testing
Unarchived Bug 1068961
> thanks
Stopping processing here.
Please contac
Processing control commands:
> clone -1 -2
Bug #1076131 {Done: Sylvestre Ledru } [libllvm18]
libllvm18: declares itself as MA: same but is not co-installable
Bug 1076131 cloned as bug 1081192
> reopen -2
Bug #1081192 {Done: Sylvestre Ledru } [libllvm18]
libllvm18: declares itself as MA: same but
Control: clone -1 -2
Control: reopen -2
Control: reassign -2 libllvm19 1:19.1.0~++rc4-4
Control: retitle -2 libllvm19: declares itself as MA: same but is not
co-installable
On 2024-07-11 10:34:08 +0200, Sebastian Ramacher wrote:
> Package: libllvm18
> Version: 1:18.1.8-2
> Severity: serious
> X-D
Processing commands for cont...@bugs.debian.org:
> unarchive 1076131
Bug #1076131 {Done: Sylvestre Ledru } [libllvm18]
libllvm18: declares itself as MA: same but is not co-installable
Unarchived Bug 1076131
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1076131:
88 matches
Mail list logo
