Can the fix in the salsa repository be uploaded to the archive to avoid
torbrowser-launcher being autoremoved from testing?
Thanks
signature.asc
Description: This is a digitally signed message part.
A fix [1] for the IO_PAGE_FAULT went into xen 4.20 which is now available in
testing and unstable.
The 4.20.0-1 Debian source package can also be compiled for bookworm if you
have a bookworm system running and want to test there. Please not that qemu
also needs to be recompiled for this xen vers
Package: binutils-x86-64-linux-gnu
Version: 2.43.90.20250122-2
Severity: serious
X-Debbugs-Cc: m...@daemonizer.de
Control: affects -1 + src:xen
With the current version (2.43.90.20250122-2) of binutils in unstable xen
FTBFS (see [1]) with:
[...]
objcopy -I ihex -O binary arch/x86/efi/buildid.ihe
Control: tags -1 + patch
The attached patch fixes compilation with Sphinx 8.0.--- a/docs/conf.py
+++ b/docs/conf.py
@@ -265,6 +265,6 @@ man_pages = [
# Example configuration for intersphinx: refer to the Python standard library.
-intersphinx_mapping = {'/usr/share/doc/python3-doc/html': None}
Control: severity -1 normal
Hi Elliott,
I am changing the severity back to normal as the xen package works fine for
many people without any serious issues. From your last message it also seems
you found a workaround for your problem. Please don't change the bug severity
without at least giving
Control: tags -1 + pending
On Fri, 21 Jun 2024 09:01:02 +0200 Stéphane Glondu wrote:
> > Your package FTBFS with OCaml 5.2.0 for the following reason:
> >
> > Problem in C stubs
>
> Attached is a patch that fixes the issues. It should also work with the
> version of OCaml currently in unstab
Control: tags -1 + pending
This is planned to be fixed with the xen 4.19 upload (will go to experimental
first) by moving xenstore-control from xenstore-utils to xen-utils-common.
signature.asc
Description: This is a digitally signed message part.
Control: tags -1 + pending
Hi Sebastian,
Thanks for your report. We (the Debian xen team) are aware of this issue and
are currently preparing an upload fixing this problem. It should be uploaded
to the archive soon.
Maxi
signature.asc
Description: This is a digitally signed message part.
Control: found -1 4.17.2+76-ge1f9cb16e2-1
Hi Steve,
Thanks for taking care about the 64-bit time_t transition.
Unfortunately your attached patch looks a bit strange to me. It adds
autogenerated files, but especially FTBFS in your experimental upload.
You can find an updated patch attached to t
Control: tags -1 +fixed-upstream
Hi,
this issue has been fixed upstream by
https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=40be6307ec005539635e7b8fcef67e989dc441f6
and was backported to the upstream stable-4.17 branch in
https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=4000522008711b132
This commit got also included in the upstream stable-4.17 branch:
https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=a91b946345b0c0550d0ee28816a15d3fc16abc50
signature.asc
Description: This is a digitally signed message part.
Control: retitle -1 xenstore-utils: broken symlink /usr/bin/xenstore-control
This is a bit more complicated:
Up to bullseye the binaries in the xenstore-utils package were independent of
the running xen version (as the xenstore interface is more or less supposed to
be stable).
Starting with bo
Ping to avoid autoremoval. The NMU from Adrian Bunk should hit the archive
within one day now.
signature.asc
Description: This is a digitally signed message part.
Control: tags -1 + patch
Attached is a simple patch fixing this issue in my local test build.
Adrian Bunk, you marked this bug as pending, are you planning to upload a
fixed version or has this been a mix up in bug numbers like in your other mail
in this bug?
Thanks,
Maxidiff -ur pyramid-jinja
This bug is still open but has been marked as fixed in the versions currently
in testing/unstable and stable. It also has been fixed in oldstable-security.
Should it be closed or is there any reason to still keep it open?
signature.asc
Description: This is a digitally signed message part.
Hi,
I had a quick look at this bug and notices the upstream parameters for
launching the test command changed in [1]. Maybe it's enough to adjust the
commands in 'debian/tests/freecadtest' [2] from
freecadcmd -t 1
freecadcmd -t 2
to
freecadcmd -t 0
However I currently don't have a pro
On Dienstag, 25. April 2017 00:08:20 CEST Ivar Smolin wrote:
> On Tue, 18 Apr 2017 17:34:15 + Ian Jackson
>
> wrote:
> > Source: xen
> > Source-Version: 4.8.1-1
> >
> > We believe that the bug you reported is fixed in the latest version of
> > xen, which is due to be installed in the Debian
Hi,
I created a patch for amarok that switches to using mariadb. I don't see how
the current mysql-defaults system can be used in amarok, as there is no
default-mysqld-dev package.
$ diff -u debian.orig/amarok-2.8.0/debian/control
debian/amarok-2.8.0/debian/control
--- debian.orig/amarok-2.8.0
Package: macchanger
Version: 1.7.0-3.2
Severity: grave
Trying to randomize the MAC address of an interface toggles between two MAC
addresses instead of setting a random MAC address. See the following example:
$ macchanger -A wlan8
Current MAC: 00:05:01:98:56:c3 (CISCO SYSTEMS, INC.)
Permanent
Source: kicad
Version: 0.20140224+bzr4027-3
Severity: serious
Hello,
kicad currently FTBFS on all architectures.
See here for the build logs:
https://buildd.debian.org/status/package.php?p=kicad
Maxi
signature.asc
Description: This is a digitally signed message part.
Hello,
according to bugzilla this bug is fixed in version 2.4.3-20050321+2, but
debian sarge still has version 2.4.3-20050321+1 affected by this bug.
Could you please upload a fixed version to sarge?
Maxi
signature.asc
Description: This is a digitally signed message part
21 matches
Mail list logo
