Control: severity -1 normal
On Wed, 18 Jun 2025 10:24:11 +0200 Philipp Kern wrote:
On 6/18/25 10:14 AM, Michael Tokarev wrote:
> On 18.06.2025 11:02, Philipp Kern wrote:
> []
>> It'd be great if qemu could autodetect this, i.e. presumably use
>> getconf(PAGE_SIZE) for
Control: severity -1 wishlist
On 28.06.2025 15:41, Daniel Baumann wrote:
Package: qemu
Version: 1:10.0.2+ds-1
Severity: serious
Hi,
qemu can't be rebuild on trxie and sid for arm64 because it has build-
dependencies to packages that are only available on amd64 and i386:
builddeps:. : Depend
On 18.06.2025 11:02, Philipp Kern wrote:
[]
It'd be great if qemu could autodetect this, i.e. presumably use
getconf(PAGE_SIZE) for this.
As has been explained to me by the qemu ppc people, autodetecting this
is wrong because this way qemu will start with different configuration
on different ho
Control: tag -1 pending
Hello,
Bug #1106796 in busybox 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/installer-team/busybox/-/commit/ceee9cf346a0b8ab4c90edb46
On 29.05.2025 23:53, Aurelien Jarno wrote:
Package: qemu-user
Version: 1:9.1.0+ds-4
Severity: serious
Justification: Policy 7.8
Hm. I especially asked a few times about this one, and the
consensus was to change initial Built-Using: tag which were
there, to Static-Built-Using. That happened in
Control: severity -1 wishlist
Control: tag -1 + upstream confirmed
On 02.05.2025 10:54, Jacob Lifshay wrote:
Source: qemu
Version: 1:7.2+dfsg-7+deb12u12
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: programmerj...@gmail.com, Debian Security Team
Dear
Source: schleuder
Version: 5.0.0-7
Severity: serious
X-Debbugs-Cc: pkg-qemu-de...@lists.alioth.debian.org
The autopkgtests of scheduler fails on all architectures but
are marked as flaky. However, on riscv64, while the tests
fails the same way, it is not marked as flaky, and prevents
other packag
Control: tag -1 pending
Hello,
Bug #1101910 in freerdp3 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/debian-remote-team/freerdp3/-/commit/0d3effa8aa11f31d13f
Control: found -1 3.3.0+dfsg1-1
On Wed, 2 Apr 2025 08:26:18 +0200 Helmut Grohne wrote:
Package: libwinpr3-dev
Version: 3.14.1+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
libwinpr3-dev explicitly declares its ability to coinstall.
Unfortunately, that doesn't
07.04.2025 13:03, Miao Wang wrote:
I found the same bug in 1:10.0.0~rc2+ds-1. The symptom remains the same.
Indeed. I included the patch, but forgot to commit d/patches/series.
Lemme do another upload...
Thanks,
/mjt
20.03.2025 00:12, Timo van Roermund wrote:
Thanks for looking into this.
I'm not sure if it's relevant, but the printer that triggers the panic is using
an older protocol version (SMB2_02).
I don't have any printer which can access samba shares.
/mjt
Control: tag -1 + confirmed upstream
Control: forwarded -1 https://gitlab.com/qemu-project/qemu/-/issues/2891
30.03.2025 08:28, Miao Wang wrote:
qemu-system-x86 coredumps when executing ipxe selftests. The command to
reproduce
the failure is:
qemu-system-x86_64 -nographic -kernel tests.lkrn
Control: tag -1 pending
Hello,
Bug #1100604 in samba 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/samba-team/samba/-/commit/96c6ed68ac76f9dd0460f2ea9e1eaa737
17.03.2025 22:11, Etienne Dechamps wrote:
Same issue here. I can reproduce with 2:4.22.0+dfsg-1+b1 within
seconds just by playing some music with foobar2000 from a Windows 11
client, and it breaks playback.
I installed a win11 machine and installed foobar2000 within. Played
various music for
Control: tag -1 - moreinfo unreproducible
Control: tag -1 + confirmed upstream
Control: severity -1 normal
Control: forwarded -1 https://bugzilla.samba.org/show_bug.cgi?id=15830
17.03.2025 00:09, Joe wrote:
cifs: Bad value for 'password2'
...
Sorry, I don't know what password2 is. If it helps
15.03.2025 11:29, Michael Tokarev wrote:
I just tried to build 3.14 in a qemu/kvm VM with single CPU. It fails - just
like 3.13 did - in tests, in TestFreeRDPCodecH264 (SEGFAULT). Is it the same
failure as in your testing?
https://github.com/FreeRDP/FreeRDP/pull/11358 fixes this failure for
Control: tag -1 + moreinfo unreproducible
16.03.2025 13:41, Joe wrote:
Package: cifs-utils
Version: 2:7.2-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
On boot, no shares were mounted
Upgraded yesterday, next boot this morning
14.03.2025 13:41, Santiago Vila wrote:
Note 2: After fixing the build problem please consider fixing the failing test
that will happen afterwards as well, as it also fails 100% of the time here.
Admittedly, I should have filed a different bug for that. Please tell me: Can
you
(or anybody in t
Control: tag -1 = confirmed
12.01.2025 22:43, Michael Kümmling wrote:
dpkg: dependency problems prevent configuration of libtevent0t64:amd64:
libtevent0t64:i386 (2:0.16.1+samba4.21.3+dfsg-5) breaks libtevent0 (<<
2:4.21.3+dfsg-5) and is unpacked but not configured.
Aha. It is the version
Control: tag + moreinfo unreproducible
12.01.2025 21:07, Raphaël Halimi wrote:
Package: libtevent0t64
Version: 2:0.16.1+samba4.21.3+dfsg-5
Severity: critical
Dear fellow maintainers,
libtevent0t64:i386 2:0.16.1+samba4.21.3+dfsg-5 breaks libtevent0:amd64 (<< 2:4.21.3+dfsg-5), and vice-versa, re
Control: severity -1 wishlist
Control: tag + confirmed
Control: merge 1069367 -1
28.12.2024 19:34, Lucas Nussbaum wrote:
Source: qemu
Version: 1:9.2.0+ds-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20241228 ftbfs-trixie
Hi,
During a re
23.12.2024 20:49, Lucas Nussbaum wrote:
Maybe you need to request removal of binaries on armhf/armel/i386?
They were RMed already in the past, but someone re-introduced them,
despite upstream explicitly stated 32bit host is unsupported.
So we're waiting for the said someone to rm them again.
Control: tag -1 + confirmed pending
14.12.2024 02:14, Michael Biebl wrote:
Package: qemu-user-binfmt
Version: 1:9.2.0+ds-1
Severity: serious
File: /usr/lib/binfmt.d/qemu-cris.conf
After the latest upgrade I get
...> Dez 14 00:11:25 mars systemd-binfmt[412101]:
/usr/lib/binfmt.d/qemu-cris.conf
13.12.2024 18:24, Michael Tokarev wrote:
Control: tag + confirmed pending
13.12.2024 18:18, Sven Joachim wrote:
Package: postfix
Version: 3.9.1-5
Severity: grave
After upgrading from 3.9.1-4, the postfix instance failed to start.
Here are hopefully relevant excerpts from the journal
Control: tag + confirmed pending
13.12.2024 18:18, Sven Joachim wrote:
Package: postfix
Version: 3.9.1-5
Severity: grave
After upgrading from 3.9.1-4, the postfix instance failed to start.
Here are hopefully relevant excerpts from the journal:
,
| Dez 13 16:05:07 turtle postmulti[11589]: c
Control: severity -1 important
In samba, pipes python module is not used.
crypt python module is used, but only in selftests, which
are not run in debian samba (unfortunately). So this bug
actually does not affect samba in debian.
Lowering severity.
Thanks,
/mjt
On Fri, 6 Dec 2024 14:48:20 -0500 Andres Salomon wrote:
Hi,
For the time being you'll have to add bookworm-proposed-updates to your
/etc/apt/sources.list. For example the following line:
Even with bookworm-proposed-updates in place, installation of new
chromium requires some force, - it can'
* Add pkgconf dependency to d/tests/control (Closes: #1088863)
+
+ -- Michael Tokarev Tue, 03 Dec 2024 08:15:56 +0300
+
libosmo-sccp (1.9.0+dfsg1-3) unstable; urgency=medium
* upload to unstable
diff -Nru libosmo-sccp-1.9.0+dfsg1/debian/tests/control
libosmo-sccp-1.9.0+dfsg1/debian/tests/co
Source: libosmo-sccp
Version: 1.9.0+dfsg1-3
Severity: serious
Tags: patch
X-Debbugs-Cc: pkg-samba-ma...@lists.alioth.debian.org
your package uses pkg-config in d/tests/can-link, but does not
declare dependency of pkgconf.
So far, pkg-config were installed due to a wrong dependency
on pkg-config i
Package: samba
Version: 2:4.21.2+dfsg-1
Severity: grave
Package python3-ldb which is dropped in 2:4.21.2+dfsg-1
and resurrected immediately in 2:4.21.2+dfsg-2 is waiting
in NEW. Let's file a bug against 2:4.21.2+dfsg-1 to avoid
migration to testing until 2:4.21.2+dfsg-2 is accepted.
/mjt
29.10.2024 14:06, Marc Haber wrote:
On Sun, Aug 04, 2024 at 01:44:09PM +0200, Chris Hofstaedtler wrote:
On Sat, Aug 03, 2024 at 05:38:59PM +0200, Chris Hofstaedtler wrote:
We allow backslashes in adduser to cater for some samba corner
cases where a user named domain\user is needed.
I am kind o
On Tue, 22 Oct 2024 19:01:02 -0400 Andres Salomon wrote:
Package: libclang-rt-19-dev
Version: 1:19.1.2-1
libclang-rt-19-dev currently isn't built for armhf, which is keeping
chromium (which recently switched away from clang 16) from migrating to
trixie. When I asked on IRC about why it wasn't
Control: severity -1 normal
Control: tag -1 + moreinfo unreproducible
On Wed, 12 Jun 2024 15:13:25 +0200 Vincent Lefevre wrote:
Package: unbound
Version: 1.20.0-1
Severity: grave
Justification: renders package unusable
I've just installed unbound on a new machine to avoid bug 1070120.
With /e
25.09.2024 19:29, Simon McVittie wrote:
Package: qemu-system-misc
Version: 1:9.1.0+ds-4
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: open...@packages.debian.org
qemu-system-misc version 1:9.1.0+ds-4 has dependencies that include:
opensbi (>> 1.5.1-1)
where ">>" de
Adding -mno-unaligned-access to MESON_ARM_*_FLAGS fixes the
tests failure with a more recent qemu.
From the comments at https://gitlab.com/qemu-project/qemu/-/issues/2542
it looks like the only prob here is that the testsuite (which is designed
to run without any OS whatsoever, just as a bootload
I'm not an arm guru, my knowledge of arm is near non-existent.
The commit in qemu which I bisected this to yesterday, apparently,
is a bugfix, - previously qemu allowed an unaligned access here,
while real hardware does not. Now qemu behavior matches that of
the hardware.
So it might as well be
Control: severity -1 normal
On Tue, 9 Jul 2024 15:34:03 +0300 Michael Tokarev wrote:
09.07.2024 15:29, Christian Marillat пишет:
> On 09 juil. 2024 15:25, Michael Tokarev wrote:
>
>> 09.07.2024 15:23, Christian Marillat wrote:
>>> On 09 juil. 2024 13:18, M
Package: dput-ng
Version: 1.39
Severity: grave
The documentation (manpage) for `dcut cancel` states:
cancel
Cancel an upload entirely. The upload is referred to as a changes file
name existing remote in the incoming or deferred queues.
This is wrong, because cancel actually can
25.07.2024 18:42, Michael Tokarev wrote:
25.07.2024 18:33, Santiago Vila wrote:
Hi.
I see that you fixed this very quickly. Thanks!
I just wanted to point out that this was really a bug in dpkg-dev:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076863
Yeah. See https
25.07.2024 18:33, Santiago Vila wrote:
Hi.
I see that you fixed this very quickly. Thanks!
I just wanted to point out that this was really a bug in dpkg-dev:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076863
Yeah. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076863#69 ;)
On Wed, 24 Jul 2024 16:35:43 +0200 Guillem Jover wrote:
So there's something wrong with the variables evaluation,
- $(call dpkg_lazy_eval,DEB_VERSION_UPSTREAM,$$(dpkg_parsechangelog_run))
- $(call dpkg_lazy_eval,DEB_UPSTREAM_REVISION,$$(dpkg_parsechangelog_run))
Here was the wrong: varia
24.07.2024 23:26, Michael Tokarev wrote:
LDB_DEB_VERSION = 2:${LDB_VERSION}+samba${DEB_VERSION_UPSTREAM_REVISION}
This is #1076863 in dpkg-dev.
/mjt
24.07.2024 23:06, Aurelien Jarno wrote:
Source: samba
Version: 4.20.2+dfsg-8
Severity: serious
On 2024-07-24 18:50, Debian FTP Masters wrote:
Version check failed:
Your upload included the binary package ldb-tools, version 2:2.9.1+samba, for
riscv64,
however testing already has version 2:2.9
09.07.2024 15:29, Christian Marillat пишет:
On 09 juil. 2024 15:25, Michael Tokarev wrote:
09.07.2024 15:23, Christian Marillat wrote:
On 09 juil. 2024 13:18, Michael Tokarev wrote:
[...]
I don't know what "NIC support is missing" means. Qemu can't be built
without su
09.07.2024 15:23, Christian Marillat wrote:
On 09 juil. 2024 13:18, Michael Tokarev wrote:
[...]
I don't know what "NIC support is missing" means. Qemu can't be built
without support for networking. The -nic option is obsolete for a long
time, that's true, but
09.07.2024 13:18, Michael Tokarev wrote:
..>> -net nic,model=help should display a list of available network devices.
If you want this to happen, I suggest you to open bug report in the
upstream qemu issue tracker. I definitely wont add debian-specific
code to display help for an ob
09.07.2024 13:11, Christian Marillat wrote:
On 09 juil. 2024 12:53, Michael Tokarev wrote:
Control: tag -1 + moreinfo unreproducible
09.07.2024 12:09, Christian Marillat wrote:
Package: qemu-system-ppc
Version: 1:9.0.1+ds-1
Severity: serious
Dear Maintainer,
My working configuration with 1
Control: tag -1 + moreinfo unreproducible
09.07.2024 12:09, Christian Marillat wrote:
Package: qemu-system-ppc
Version: 1:9.0.1+ds-1
Severity: serious
Dear Maintainer,
My working configuration with 1:8.2.5+ds-2 was:
,
| -net nic,macaddr=52:54:00:12:34:67,model=virtio -net tap
`
Now w
Control: found -1
06.07.2024 00:35, Salvatore Bonaccorso wrote:
..
This is fixed by qemu uploaded earlier today.
Patches are already prepared for bookworm (for qemu 7.2.x series) and
already verified upstream and passed the tests.
Yes thanks, had only the 1:8.2.5+ds-2 initially to check.
Sur
On Sat, 16 Mar 2024 15:05:34 +0100 Bastian Germann wrote:
v3.1.44 should be the best upstream version for this.
why do you think this is the best version?
Thanks,
/mjt
--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 91
Package: gpu-burn
Version: 0+git20240115+ds-2
Severity: grave
gpu-burn package links with libcuda.so.1 and libcublas.so.11 but does not
list them in Depends. This results in a broken, entirely unusable package
after install:
gpu-burn: error while loading shared libraries: libcuda.so.1:
canno
03.05.2024 23:16, Andreas Beckmann wrote:
Package: samba-dev
Version: 2:4.20.0+dfsg-1~exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine i
Control: tag -1 + moreinfo unreproducible
02.05.2024 23:36, Michael Biebl wrote:
Control: reopen -1
Control: found -1 2:4.19.6+dfsg-3
So, I'm confused now. You reopened this for -3 which *fixed* both
issues mentioned by you as reasons for the reopen.
Does -3 actually fails for you?
Thanks,
02.05.2024 23:36, Michael Biebl wrote:
Control: reopen -1
Control: found -1 2:4.19.6+dfsg-3
On Thu, 2 May 2024 11:58:59 -0700 "Leo L. Schwab" wrote:
Did you fix this one, too?
---
Performing actions...
Setting up python3-samba (2:4.19.6+dfsg-2) ...
File "/usr/lib/python3/dist-packages/s
Ok,
I'm removing whole modutils from busybox udeb (besides depmod, this is
lsmod, insmod, rmmod, and modprobe). All these are provided by
kmod-udeb as far as I can see (as symlinks to kod).
--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E 9D8B
09.04.2024 16:48, Cyril Brulebois wrote:
Marco d'Itri (2024-04-09):
Yes. Nowadays kmod has many more features related to compressed modules
and verification of signatures.
Can we agree that kmod should provide these programs for d-i?
Or can the d-i maintainers just tell us what they want?
I m
20.04.2024 15:33, Lucas Nussbaum wrote:
[..]
This is part of a mass rebuild, first building on arm64 and then on
armhf and armel. So I'm not suggesting anything. :-)
Aha.
Is this failing because the build is trying to build arch:all packages,
that can only be built on amd64? If so, the bug se
Control: tag -1 + moreinfo
Control: found -1 1:4.2-2
20.04.2024 15:11, Lucas Nussbaum wrote:
Source: qemu
Version: 1:8.2.2+ds-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64
sbuild-build-depends-ma
Package: locales
Version: 2.37-16
Severity: grave
A fresh `debootstrap unstable' chroot plus `apt install locales`:
Preconfiguring packages ...
locales failed to preconfigure, with exit status 2
dpkg: error processing package locales (--configure):
installed locales package post-installation
07.04.2024 05:54, Peter Green wrote:
Ubuntu has already fixed this issue by removing the hardcoded
dependency on libgpgme11
I fixed it in git too, but forgot to upload.
http://launchpadlibrarian.net/720831431/riseup-vpn_0.21.11+ds1-5build3_0.21.11+ds1-5ubuntu1.diff.gz
While poking through t
On Sat, 30 Mar 2024 16:59:51 +0900 Kentaro HAYASHI wrote:
Source: sssd
Severity: serious
Tags: ftbfs
Control: found -1 2.9.4-1.1
X-Debbugs-Cc: ken...@xdump.org
Dear Maintainer,
sssd fails to build on armel, armhf.
Though test suite failure was already reported, but
target version is 1.11.5.1
05.03.2024 10:03, Andrey Rahmatullin wrote:
Breaks: qemu-system-common (<< 8.2.1+ds-3~),
Replaces: qemu-system-common (<< 8.2.1+ds-3~),
so... what's going on here? q-s-d 8.2.2 replaces files from q-s-c 8.2.1
Can it be simply because the package has an epoch and relations should
includ
05.03.2024 09:10, Andrey Rahmatullin wrote:
Package: qemu-system-data
Version: 1:8.2.2+ds-1
Severity: serious
Preparing to unpack .../qemu-system-data_1%3a8.2.2+ds-1_all.deb ...
Unpacking qemu-system-data (1:8.2.2+ds-1) over (1:8.2.1+ds-2) ...
dpkg: error processing archive /var/cache/apt/archi
Control: severity -1 important
03.03.2024 13:21, Eric Valette :
Package: libsmbclient0
Version: 2:4.19.5+dfsg-3
Severity: grave
Justification: renders package unusable
This is wrong, in my opinion. The effect of this bug on platforms unaffected
by time64_t transition is exactly the same as on
01.03.2024 17:24, Emanuele Rocca wrote:
Source: udns
Version: 0.4-1.1
Severity: serious
Tags: ftbfs
User: debian-de...@lists.debian.org
Usertags: time64
Dear Maintainer,
udns fails to build on both armhf and armel with the time64 build flags, which
are on by default. It builds fine without.
Sp
01.03.2024 19:05, Aurelien Jarno :
Source: samba
Version: 2:12.3.5-4
Is it really 12.3.5-4? :)
/mjt
09.02.2024 17:57, Thorsten Bonow :
dash << 'EOF' [15:28:53]
if $( (true) 2>/dev/null); then
echo "42"
fi
EOF
42
which only works in dash because of the added space between the command
substitution $(...) and the subshell (...).
Does dash think it ha
09.02.2024 16:58, ca...@allfreemail.net
Package: console-setup
Followup-For: Bug #1063518
Consider making all scripts provided by console-setup shellcheck-clean, there
are lots of tiny issues that can turn into big issues under the right
conditions.
Please do not do this. Shellcheck is a hug
06.02.2024 12:34, Helmut Grohne:
...
An option I see here is to provide ABI-duality for libselinux:
-extern int matchpathcon_filespec_add(ino_t ino, int specind, const char *file);
+typedef unsigned long libselinux_ino_t;
+typedef uint64_t libselinux_ino64_t;
+extern int matchpathcon_filespec_ad
07.02.2024 11:06, Helmut Grohne :
..
pam seems difficult:
| extern time_t pam_misc_conv_warn_time; /* time that we should warn user */
| extern time_t pam_misc_conv_die_time; /* cut-off time for input */
Attached is a sketch to make pam compatible.
I had a more complete and *tested* fi
06.01.2024 11:40, Helmut Grohne:
On Sat, Jan 06, 2024 at 09:01:12AM +0100, Helmut Grohne wrote:
I also recommend to establish QA for all udebs to automatically detect,
report and address such conflicts as they evidently cause undefined
behaviour otherwise. That can be as simple as collecting fil
Control: severity -1 normal
Control: merge 1060005 -1
FWIW, this is kernel bug, not cifs-utils bug, - guess it's 6.1.0-17 regression.
/mjt
On Sat, 16 Dec 2023 14:54:32 +0100 Wolfgang Rohdewald
wrote:
Package: docker.io
Version: 20.10.24+dfsg1-1+b3
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
* What led up to the situation?
installed docker.io with existing qemu guests in bridge mode, did not d
Control: tag -1 + moreinfo unreproducible
11.12.2023 14:51, Y :
Package: qemu-guest-agent
Version: 1:8.1.2+ds-1~bpo12+1
Severity: serious
Justification: 6
Dear Maintainer,
The problem arose after upgrading from bullseye to bookworm.
What did you upgrade, host or guest system?
All was OK on
Control: reassign -1 dak
11.09.2023 08:40, Christian Marillat wrote:
Package: qemu-system-ppc
Version: 1:8.0.4+dfsg-3+b1
Severity: serious
File: /usr/bin/qemu-system-ppc
Dear Maintainer,
sudo apt-get install qemu-system-ppc qemu-system-data
...
The following packages have unmet dependencies:
Control: tag -1 + moreinfo unreproducible
09.09.2023 15:03, Mikhail Gusarov:
Source: qemu
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: dotted...@debian.org
Some cross-compilers are not available in bookworm, so qemu c
09.09.2023 03:07, Peter Green:
async-tls has not switched upstream. On the other hand I don't
see any packages in Debian using it yet. ccing mjt to see what
the reason for packaging it was.
async-tls isn't my baby, count_omega (=werdahias, Cc'd) asked to sponsor it
on Jun-28 and I uploaded it,
On Sun, 13 Aug 2023 11:40:11 +0200 Aurelien Jarno wrote:
..
The solution to fix this is to use PYIMATH_OVERRIDE_PYTHON_INSTALL_DIR
to define the installation of the Python modules instead of relying on
autodetection.
Can't this be done at the cmake level instead of overriding this in each
pack
Hi everyone!
Somehow I missed this whole issue, - I didn't see it until now.
Will adjust my mail filters.
08.08.2023 00:49, Philip Hands wrote:
Steve McIntyre writes:
On Wed, Jul 12, 2023 at 11:15:57AM +0200, Cyril Brulebois wrote:
Hi Michael,
Cyril Brulebois (2023-06-28):
Control: reass
15.05.2023 20:50, Michael Tokarev wrote:
15.05.2023 19:49, Bastian Germann wrote:
the qemu-system-* binaries depends on libsasl2-2, which is licensed under CMU's BSD-3-Clause-Attribution license and covered by the RSA-MD license.
They have clauses in place, which are known to be incompa
15.05.2023 19:49, Bastian Germann wrote:
the qemu-system-* binaries depends on libsasl2-2, which is licensed under CMU's BSD-3-Clause-Attribution license and covered by the RSA-MD license.
They have clauses in place, which are known to be incompatible with GPL (as far as I can see the mentioned
Control: tag -1 + moreinfo
Control: found -1 1:3.0+dfsg-1
15.05.2023 19:49, Bastian Germann wrote:
Source: qemu
Version: 1:7.2+dfsg-6
Severity: serious
Hi,
the qemu-system-* binaries depends on libsasl2-2, which is licensed under CMU's BSD-3-Clause-Attribution license and covered by the RSA-MD
So, we tried to reproduce it on a different machine at IBM.
The problem doesn't show itself there.
I asked the debian admin team to reboot zelenka into 5.10.0-20 kernel
to verify, - there was no answer so far.
So I'm leaving this as it is now. If the next kernel update will
not fix the issue, I
In the build logs for libguestfs, I see last successful builds were done
on 5.10.0-20-s390x kernel, and on 5.10.0-21-s390x, all builds fails.
5.10.0-21-s390x is the one running on zelenka too.
It looks to me like a kernel issue..
/mjt
So, many previous versions behave the same, including bullseye.
However.
1. I was able to create a 512-bytes qcow2 file once in /home/mjt on zelenka.
And.
2. All versions always work fine in /tmp, on a tmpfs.
Is it possible that the tests were running on a tmpfs before?
/mjt
Control: tag -1 + help
Control: found -1 1:5.2+dfsg-11+deb11u2
05.02.2023 20:30, Michael Tokarev wrote:
..
The thing is: I can't find *any* working version of qemu-img, they all
hang like described. This includes 1:7.2+dfsg-1+b1 too.
There's more: I installed bullseye on zelenka,
04.02.2023 23:48, Hilko Bengen wrote:
..
Does 7.2+dfsg-1 work?
I don't have s390x environment so have no way to deal with this one.
No, it doesn't. On the porterbox (zelenka.debian.org) I was only able to
install 1:7.2+dfsg-1+b1 without rebuilding.
Oh, I forgot about zelenka. Tried that one
04.02.2023 23:19, Hilko Bengen wrote:
Package: src:qemu
Version: 1:7.2+dfsg-2
..
qemu-img create -f qcow2 -o preallocation=metadata blank-disk-1s.qcow2 512
would hang in what appears a tight loop (100% CPU).
Does 7.2+dfsg-1 work?
I don't have s390x environment so have no way to deal wi
Package: systemd
Version: 252.2-2~bpo11+1
Severity: serious
I just come across a situation where my notebook does not let me in while
I'm in a place where network is not available. This is entirely wrong.
After a painful debugging session, I found the debian-shipped file
/lib/systemd/system/rc-loc
19.12.2022 16:32, Michael Tokarev wrote:
..
Aargh. This is due to my attempts to upload security update without waiting
for the NEW processing. It *had* proper Breaks+Replaces, but I removed it all
in an attempt to clean up new package introduction.
Actually it's a lie, it has nothing
19.12.2022 14:29, Andreas Beckmann wrote:
Package: samba-ad-provision
Version: 2:4.17.3+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the u
On Fri, 16 Dec 2022 11:50:18 + debian user wrote:
Package: login
Version: 1:4.13+dfsg1-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: r...@localhost.lan, Debian Security Team
Dear Maintainer,
please uncomment the line in /etc/login.defs that currently sa
On Sat, 26 Nov 2022 12:43:12 -0800 Alex Relis wrote:
Package: nvidia-driver
Version: 470.103.01-1~bpo11+1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
About a week ago, linux-image-6.0.0-0.deb11.2-amd64 was introduced in
bullseye-backports. The problem is that the
08.11.2022 17:50, Michael Tokarev wrote:
08.11.2022 17:11, Guillem Jover wrote:
[..]
If you are really seeing samba linked against old liburing not working
with the new liburing, then we'd need to dig further to see what else
might be missing, but I'm currently not seeing it just
08.11.2022 16:44, Guillem Jover wrote:
Hi!
On Tue, 2022-11-08 at 16:32:25 +0300, Michael Tokarev wrote:
On Tue, 08 Nov 2022 15:51:17 +0300 Michael Tokarev wrote:
Source: liburing
Version: 2.3-1
Severity: grave
liburing 2.3 broke binary compatibility without bumping the soname.
Indeed
08.11.2022 17:11, Guillem Jover wrote:
[..]
If you are really seeing samba linked against old liburing not working
with the new liburing, then we'd need to dig further to see what else
might be missing, but I'm currently not seeing it just by a very quick
code staring.
Well. I already deleted m
On Tue, 08 Nov 2022 15:51:17 +0300 Michael Tokarev wrote:
Source: liburing
Version: 2.3-1
Severity: grave
liburing 2.3 broke binary compatibility without bumping the soname.
In liburing.h in 2.3, structures io_uring_cq and io_uring_sq changed
their sizes. Both of these structures are parts of
Source: liburing
Version: 2.3-1
Severity: grave
liburing 2.3 broke binary compatibility without bumping the soname.
In liburing.h in 2.3, structures io_uring_cq and io_uring_sq changed
their sizes. Both of these structures are parts of io_uring structure
which the main part of the API. Here's th
ng mdadm package did not help.
Downgrading busybox-static to 1.35.0-2 fixed the issue.
Now this is interesting. In -3, I included these changes:
commit ac478f88b64d5884d5e81bcd8f8344f0ec72df6a
Author: Michael Tokarev
Date: Mon Oct 17 12:52:23 2022 +0300
deb,static:
Hmm. Other sssd packages are also affected by this.
Not only sssd-ad but sssd-ipa and sssd-ad-common.
Added the Breaks for these in Bullseye (and also in Ubuntu Jammy, which
has exactly the same problem). Will be in the next upload.
/mjt
1 - 100 of 408 matches
Mail list logo
