Control: tag -1 - patch
Apparently this is not so simple. As per upstream,
https://mail.coreboot.org/pipermail/seabios/2018-July/012353.html
- they say only particular versions of IASL produce correct code,
more recent IASL produces instructions not understood by older
OSes (which is what qemu abo
23.11.2016 05:34, NeilBrown wrote:
> On Tue, Nov 22 2016, Andy Smith wrote:
>
>> Hi Neil,
>>
>> On Tue, Nov 22, 2016 at 09:56:28AM +1100, NeilBrown wrote:
>>> Thanks. Sorry this is taking a lot of back-and-forth...
>>
>> No worries. This is very interesting to me and I'd also like to know
>> what
Control: notfound -1 1:3.1+dfsg-4
16.02.2019 15:41, Moritz Muehlenhoff wrote:
Source: qemu
Severity: grave
Tags: security
When rdma was enabled in -3, this also made a fix for CVE-2018-20124 necessary:
Yes indeed.
But since this code has a ton of bugs (not only security) and is generally
qui
01.01.2019 23:14, Laurent Bigonville wrote:
On Mon, 24 Dec 2018 09:34:16 +0300 Michael Tokarev wrote:
> it doesn't really break the package in question. All these
> packages will be of the same version anwyway, upgraded in
> one go, at the very max there will be some docs mi
Control: severity -1 minor
02.01.2019 1:03, Laurent Bigonville wrote:
Le 1/01/19 à 21:35, Michael Tokarev a érit :
[]>>> Well this bug has been reopened that mean that the package will never
migrate
That's sort of unfortunate...
Indeed, it would be unfortunate to not have
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
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
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
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
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
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,
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
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, 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
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
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
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
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
Control: tag -1 + moreinfo
Control: severity -1 normal
26.12.2020 15:10, Charles Malaheenee wrote:
Package: qemu-system-x86
Version: 1:5.2+dfsg-2
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: malahee...@gmx.fr
Dear Maintainer,
Not sure is it related with
05.01.2021 13:44, Gianfranco Costamagna wrote:
Source: libcacard
Version: 1:2.8.0-1
Severity: serious
Hello, libglib2.0-dev looks missing on -dev package?
pkg-config --short-errors --print-errors --cflags --libs "libcacard >= 2.5.1"
Package 'glib-2.0', required by 'libcacard', not found
I gue
05.01.2021 13:44, Gianfranco Costamagna wrote:
...
after installing it looks still missing
Package 'libpcsclite', required by 'libcacard', not found
Oh. I missed this one. Will do another upload.
/mjt
23.10.2020 19:50, Sebastian Ramacher wrote:
Source: qemu
Version: 1:5.1+dfsg-4
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
binNMUs of qemu for the libbrlapi transition failed to build on armel
and armhf:
| /<>/lin
30.11.2020 23:27, Paul Gevers wrote:
Hi all, Christian,
On Tue, 8 Sep 2020 15:40:11 +0200 Christian Ehrhardt
wrote:
Signed-off-by: Christian Ehrhardt
---
...raseReserved-override-driver-queue_p.patch | 74
...BlockEraseReserved-skip-unless-iSCSI.patch | 39
...e-Write-ove
Control: severity -1 wishlist
Control: tag -1 wishlist
09.12.2020 11:59, Lucas Nussbaum wrote:
Source: edk2
Version: 2020.08-1
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
Hi,
During a rebuild of all packages i
Control: severity -1 normal
Control: reassign -1 qemu-system-x86
02.01.2017 02:54, Kyle Gordon wrote:
> Package: qemu-kvm
> Version: 1:2.1+dfsg-12+deb8u6
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> Over the course of the past few weeks, a guest KVM inst
Control: severity -1 serious
23.01.2017 15:40, Charles Malaheenee wrote:
> Package: ipxe-qemu
> Version: 1.0.0+git-20161027.b991c67-1
> Severity: normal
> Tags: upstream
>
> Dear Maintainer,
>
> It's not possible to PXE boot in QEMU at all. When we choose --pxe option in
> virt-install (or virt
Control: severity -1 normal
02.02.2017 19:13, Steven Gawroriski wrote:
> Package: qemu
> Version: 1:2.8+dfsg-2
> Severity: critical
> Justification: breaks unrelated software
>
> Dear Maintainer,
>
> For QEMU user mode, attempting to run i386 executables on a PowerPC
> host fails.
>
> Running e
Control: tag -1 + moreinfo unreproducible
21.10.2016 16:30, Lucas Nussbaum wrote:
> Source: seabios
> Version: 1.8.2-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161021 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of
Control: tag -1 - moreinfo unreproducible + confirmed
25.10.2016 14:44, Lucas Nussbaum wrote:
[]
Compile checking build/bios/src/stacks.o
src/stacks.c: Assembler messages:
src/stacks.c:635: Error: found '(', expected: ')'
src/stacks.c:635: Error: junk `(%ebp))' after expressi
25.10.2016 11:31, Adrian Bunk wrote:
> -LD_REL := $(CC) -nostdlib -Wl,-r $(LD_REL_FLAGS)
> +LD_REL := $(CC) -nostdlib -r $(LD_REL_FLAGS)
Adrian, can you elaborate on this a bit please?
I'm not sure of the possible consequences of this.
Is this change good to be used upstream?
Does it work the sam
20.05.2019 16:07, Salvatore Bonaccorso wrote:
Hi
FTR, https://salsa.debian.org/qemu-team/qemu/merge_requests/6 for the
related changes in unstable (and to target buster).
Yeah, I comitted it the same day this issue popped up,
but forgot to push it (done now).
Thanks!
/mjt
Package: samba
Version: 2:4.13.13+dfsg-1~deb11u2
Severity: critical
Tags: patch upstream
Please see https://lists.samba.org/archive/samba/2022-February/239548.html and
https://lists.samba.org/archive/samba/2022-February/239577.html for the
description of the problem and how serious can it be, this
On Sat, 14 Aug 2021 08:28:41 + Roman Fiedler
wrote:
Package: bridge-utils
Version: 1.7-1
Severity: serious
When running "brctl addbr" and "ip link set [if] address" immediately
afterwards, the second command will fail to apply the address
change. This is somehow annoying as the MAC would b
04.09.2021 14:33, Vincent Bernat wrote:
> Package: qemu-user-static
> Version: 1:6.1+dfsg-4
> Severity: critical
>
Hey!
Since 6.0, qemu-user-static does not seem to work properly through
binfmt. I am a bit lost on how to diagnose that:
...
When invoked through binfmt, the binaries seem to go f
23.03.2022 16:38, Diederik de Haas wrote:
On woensdag 23 maart 2022 06:54:57 CET Axel Beckert wrote:
Gian Piero Carrubba wrote:
Init: sysvinit (via /sbin/init)
Diederik de Haas wrote:
I do not have a /run/samba/ directory on my Bookworm system/server.
I don't think it's relevant, but it (sti
ld be addressed later. Closes: #1008638
+
+ -- Michael Tokarev Thu, 07 Apr 2022 16:03:29 +0300
+
ldns (1.7.1-2) unstable; urgency=low
* Team upload.
diff -Nru ldns-1.7.1/debian/patches/series ldns-1.7.1/debian/patches/series
--- ldns-1.7.1/debian/patches/series2020-06-03 23:55:03.
ython (3.10) and allows the python3.10 transition to
+happen, but it is not fixing the actual issiue with ldns using
+distutils which should be addressed later. Closes: #1008638
+
+ -- Michael Tokarev Thu, 07 Apr 2022 16:03:29 +0300
+
ldns (1.7.1-2) unstable; urgency=low
* Team u
13.04.2022 09:50, Daniel Kahn Gillmor wrote:
Control: reassign 1009385 libldns3 1.7.1-2.1
Control: retitle 1009385 libldns3 1.7.1-2.1 changes output of ldns-key2ds,
causing FTBFS on dns-root-data
Control: affects 1009385 + dns-root-data
X-Debbugs-Cc: Michael Tokarev
Control: tags 1009385
13.04.2022 10:09, Michael Tokarev wrote:
..
But let's try.
How this utility is used in building of dns-root-data? Lemme take a look
at this package. If you can provide me some minimal testcase to produce
just the DS record which differs, it will be nice.
I don't have time for
[Just a quick follow-up]
On 13.04.2022 15:52, Santiago Ruano Rincón wrote:
[...]
It seems it was fixed on 1.8.0.
https://github.com/NLnetLabs/ldns/commit/4d2057f0b5220487882be1b19c302833b84cffe3
Wonderful.. :) Thank you Santiago!
So, the prob should've be there after just any
recompile of ldn
On 13.04.2022 16:44, Santiago Ruano Rincón wrote:
..
So what do we do now? I think the best is to include
this fix as 1.7.1-3 (provided it actually fixes the
issue) for now, instead of uploading 1.8.
Why just don't uploading 1.8.1?
Well, we know 1.7 (sort of) works while 1.8 might cause
surp
Control: severity -1 normal
Lowering severity of this bug to normal. It definitely is not grave
in my book, - this is a regular emulation bug which can't emulate
some specific code. Or else every emulation bug should be marked
"grave" as it affects "other software".
BTW, I for one can't reprodu
Control: severity -1 normal
Control: tag -1 + moreinfo
12.01.2020 18:37, peter green wrote:
> Package: qemu-block-extra
> Version: 1:4.2-1
> Severity: serious
>
> The binary packages built from the ceph source package were recently removed
> from mipsel, because the new version of ceph runs out
Control: severity -1 normal
On Mon, 08 Oct 2018 08:07:39 + Theo wrote:
Package: qemu-user-static
Dear Maintainer,
I'm trying to run Stretch 386 binaries on a PogoPlug E02, which is currently
running an Arch Linux system. I populated a directory using debootstrap.
Can you please try out
24.12.2018 6:00, Andreas Beckmann wrote:
Followup-For: Bug #916279
Control: found -1 1:3.1+dfsg-2
Hi,
you are missing a
Breaks: qemu-system-data (<< 1:3.1+dfsg-1~)
to match the Replaces, otherwise you are permitting partial
upgrade/downgrade paths where files are disappearing whil
dpkg consi
10.11.2018 00:34, Thorsten Glaser wrote:
> reopen 913336
> thanks
>
> Michael Tokarev dixit:
>
>>> pn qemu-system-gui
>>
>> Ditto as for #913336.
>
> Nope.
>
> 1. I still get “Display 'sdl' is not available.” if I select it.
*if*
01.11.2022 10:59, Michael Tokarev wrote:
..
And this revealed one more issue here, now with samba 4.17. Where, the
same libndr.so again, has changed soname from libndr.so.2 to libndr.so.3!
And it looks like *this* is what you're talking about now, once 4.17 with
this new libndr.so.3
Control: tag -1 + upstream
Original context was at http://bugs.debian.org/1013259 , but whole thing *now*
has is about completely unnecessary soname bump of libndr in 4.17 due to
debugging
refinements.
01.11.2022 11:07, Michael Tokarev wrote:
01.11.2022 10:59, Michael Tokarev wrote:
..
And
01.11.2022 13:14, Ralph Boehme wrote:
On 11/1/22 09:15, Michael Tokarev via samba-technical wrote:
Control: tag -1 + upstream
Original context was at http://bugs.debian.org/1013259 , but whole
thing *now* has is about completely unnecessary soname bump of libndr
in 4.17 due to debugging
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
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:
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
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
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
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: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
Control: tag -1 + pending
22.08.2022 17:11, L. van Belle wrote:
I can confirm the patch works.
I've tested on a Debian Bullseye build with
cifs-utils 7.0 from https://ftp.samba.org/pub/linux-cifs/cifs-utils/
I refreshed patch 001.
Added the patch shown buy Helmut.
And I builded against Debian
25.08.2022 11:49, L. van Belle wrote:
...
The shown fix, commit aeaa786aceb0ea781ded2c151fb68f6b34880ad4
is the patch I added.
and cifs-utils 7.0 also fails to build without that patch with parallel=1
It's difficult to follow.
Commit aeaa786aceb0ea781ded2c151fb68f6b34880ad4 is wrong by its own
27.08.2022 03:35, Santiago Vila пишет:
Hi. Now that this is finally fixed in sid, here is a proposed diff for
bullseye, including changelog.
Heh. The changelog includes entry by me.. it is not fair for your contribution,
I think.. :)
BTW, should we drop the .1 from -3.1+deb11u2 release numbe
13.04.2022 21:19, Daniel Kahn Gillmor wrote:
Hi Michael and Santiago--
I've now uploaded ldns 1.7.1-3 with the associated fix for 1009385. I'm
reviewing Michael's changes for 1.8.1, and they're looking good to me.
Thank you for all that work, Michael! I think we should consider
uploading 1.8.1
13.04.2022 21:29, Michael Tokarev wrote:
The only prob is that the master branch on the ldns repository is
seriously messed up.
Also you've made similar commits as I did, but in an incomplete way
(like the watch file update).
Thanks,
/mjt
13.04.2022 21:19, Daniel Kahn Gillmor wrote:
..
reviewed and i'll push that to salsa as a "debian/experimental" branch
later today, if either of you want to take a look at what i'm
considering for release.
The whole thing was ready, polished, everything addressed.
If you wanted another 1.7.1 up
Okay guys.
I thought about this a bit more.
One wrong action by one developer does not make the environment
unhealthy.
I fixed the mess done to the master branch.
I think - provided this wont happen again - it's okay to work
on this to fix the rest of the mess done.
I'm doing this right now.
Fixed my branch on the ldns repo, rebasing it on top of now-okay master.
If we ever need one more 1.7 release it will be easier to rebase now with
the conflicts resolved.
I have to review my branch again, I think something might not be right
there after the rebase on top of dkg's changes. I will
BTW, Daniel, please re-tag 1.7.1-3 - this is what's at the tip of master now.
I hope anyway :)
Thanks,
/mjt
[Resending whole thing. I think it is is important to have it publicly
available and to reach you, so adding it to the bugreport too.
Apparently team+dns@tracker.d.o isn't working and there's no archives]
I want to follow up on the todays ldns incident.
I think it was quite interesting.
The whol
nd on
+all pythons. Closes: #1009204
+
+ -- Michael Tokarev Mon, 18 Apr 2022 17:39:33 +0300
+
vdirsyncer (0.18.0-6) unstable; urgency=medium
* avoid checking flaky test test_fuzzing;
diff -Nru vdirsyncer-0.18.0/debian/tests/control
vdirsyncer-0.18.0/debian/tests/control
--- vdirsyncer-0
Control: severity -1 normal
On Wed, 8 May 2019 22:35:53 +0200 "Steinar H. Gunderson"
wrote:
On Wed, May 08, 2019 at 10:02:46PM +0200, Mathieu Parent wrote:
> Downgrading the severity as the AppArmor side is already fixed it seems in
sid.
serious and grave are of equal severity; serious is fo
05.05.2022 13:47, Paul Gevers wrote:
Hi all,
[CC-ing src:debian-edu and src:qemu as they pull in src:ipxe-qemu into the key
package set, so I consider them stakeholders in this RC bug.]
On Fri, 12 Mar 2021 19:29:55 +0100 (CET) Thorsten Glaser
wrote:
So we now know without fail that there’s
06.05.2022 19:49, Mike Gabriel wrote:
..
at least the bugtitle is far to unprecise. Here, I test Debian Edu bullseye
really heavily and integrate FAI in Debian Edu.
The FAI installer and also the diskless machines I very often boot via iPXE/QEMU. In Debian 11 (and probably beyond), PXE booting
Control: severity -1 normal
08.05.2022 02:18, Thorsten Glaser wrote:
..
In this bugreport, I see it is/was broken with -machine pc-1.1.
There's no indication if it is broken with other machine types. As
of qemu 5.2 (bullseye) machine types below pc-1.3 are deprecated, and
in 7.0 (current bookwo
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
On 26.09.2022 17:39, Justin Ossevoort wrote:
Package: qemu-system-data
Version: 1:5.2+dfsg-11+deb11u2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: deb...@internetionals.nl
Dear Maintainer,
The latest packages in Debian Bullseye Backports depend on
qemu-system-data
Control: tag -1 + confirmed
07.10.2022 11:38, Simon McVittie wrote:
...
# smbclient --help
smbclient: /usr/lib/x86_64-linux-gnu/libldb.so.2: version `LDB_2.2.4' not found
(required by /usr/lib/x86_64-linux-gnu/samba/libsamdb-common.so.0)
Workaround: also upgrade samba-libs to the version from t
07.10.2022 18:08, Michael Tokarev wrote:
...
Removing the symver LDB_2.2.4 from libldb.so.2 was an ABI break, so libldb2
should have versioned Breaks against dependent packages that use the old
symver. It looks as though only the samba and maybe sssd source packages
will be affected by this.
I
07.10.2022 18:53, Simon McVittie wrote:
On Fri, 07 Oct 2022 at 18:08:41 +0300, Michael Tokarev wrote:
In debian samba package, there's a strict versioned dependency of libldb2
for samba package - actually samba-dsdb-modules - the only package which
actually *uses* libldb.
I'm not s
16.10.2022 08:04, Adrian Bunk wrote:
...
With 0.10.3-1 vulkan is a new requirement, breaking the qemu build again:
https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A7.1%2Bdfsg-2%2Bb1&stamp=1665894634&raw=0
The complete list is currently:
$ pkg-config --cflags virglrenderer
P
18.10.2022 00:17, Michael Biebl wrote:
..
Patching the upstream provided .pc file in Debian feels odd, tbh.
Are you sure Requires.private is only relevant for static linking? Isn't this
what Libs.private is for.
Yes it feels odd indeed. The problem here is often due to lack of
understanding h
18.10.2022 09:41, Michael Tokarev wrote:
..
At least once I come across a case where pkgconfig --cflags were
actually needed - because this library's header file actually
included some other header file.
And iirc, it was an upstream bug, the dependency should have been
listed as non-pr
According to the FAQ at
https://people.freedesktop.org/~dbn/pkg-config-guide.html#faq :
My library z uses libx internally, but does not expose libx data types in its
public API.
What do I put in my z.pc file?
Again, add the module to Requires.private if it supports pkg-config. In this
ca
Ok. This package appears to lack some love. Bugs are never closed
(I just closed a few bugreports which were fixed years ago), migration
status apparently is never checked, bugs actually are not watched/handled
(these 2 bugs are here for quite some time already). I pinged the maintainer
but he did
23.10.2021 19:33, Lucas Nussbaum wrote:
Source: qemu
Version: 1:6.1+dfsg-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevan
Control: tag -1 + moreinfo
14.06.2018 19:23, Vivia Nikolaidou wrote:
> Package: seabios
> Version: 1.11.1-1
> Severity: serious
> Justification: Policy 2.1.2
>
> Dear Maintainer,
>
> I just noticed that the source tarball of seabios includes some compiled
> binaries:
[]
> They should not be ship
15.04.2018 05:19, Adam Borowski wrote:
> Hi!
> This FTBFS has been unresponded for 8 months, has a patch rotting for 6.
> Sounds like NMU time.
>
> Here's a debdiff that includes this and #833444. I'll upload to DELAYED/7,
> please yell if anything is wrong.
Oh. I haven't noticed this bugreport.
Control: severity -1 normal
Hmm.. I've no idea why this bug has severity Grave to start with.
/mjt
21.04.2018 16:06, Andreas Beckmann wrote:
> Package: qemu-user-static
> Version: 1:2.12~rc3+dfsg-2
> Severity: serious
>
> Hi,
>
> qemu-user-static fails to upgrade with binfmt-support from stretch
> installed since that does not know about --fix-binary:
Yeah, it requires a more recent binfmt-su
On Fri, 03 Jul 2020 18:45:07 +0900 Mike Hommey
wrote:
..
> Arguably, freetype2.pc shouldn't depend on libbrotlidec.pc except with a
> Required.private, assuming one doesn't actually need to include
> libbrotli headers or link against libbrotli library (presumably, that's
> the case).
The thing i
01.02.2020 18:53, Adam Borowski wrote:
> Package: qemu-system-ppc
> Version: 1:4.2-2
> Severity: grave
> Justification: renders package uninstallable
>
> Hi!
> Upon upgrading or a fresh install:
>
> Unpacking qemu-system-ppc (1:4.2-2) ...
> dpkg: error processing archive «TMP»/3-qemu-system-ppc_1
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
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: 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
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
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
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
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
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
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
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
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
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
1 - 100 of 408 matches
Mail list logo
