Source: linux
Version: 4.9.2-2
Hi! Please enable CONFIG_KEXEC on arm64. The userspace side landed in
unstable yesterday, and I verified that it works (at least in QEMU) w/
a Debian kernel rebuilt w/ CONFIG_KEXEC=y.
-dann
fyi, arm64 support was added in upstream 2.0.14.
On Mon, Dec 26, 2016 at 02:01:34PM +0100, Enrico Tassi wrote:
> Hum, I'm a bit lost here. 2.0.4 is fine, but does not work on arm64.
> What about 2.1-beta2 + fix allocator (as in message #35) ? Was it
> tested? Does it work? Should I upload it?
Hi Enrico,
Yes - I verified it, it does work on
Package: debconf
Version: 1.5.59
Severity: normal
The "owner" field for a "Multi-Arch: same" package differs depending on which
maintainer script sets it.
As an example, say we have foo_1-1_amd64.deb that is "Multi-Arch: same", with
a template "foo/bar". When set by config, "foo/bar" will owned
On Tue, Dec 13, 2016 at 11:04:46PM +0100, Michael Biebl wrote:
> Am 13.12.2016 um 18:22 schrieb Michael Biebl:
> > I've blocked the two bugs accordingly and forwarded the issue to
> > upstream.
>
> This is upstream's response
>
>
> Thomas Haller:
> > I don't think there is anything to do.
> >
Package: network-manager-openvpn
Version: 1.2.6-2
Severity: normal
After upgrading to openvpn 2.4~rc1-2, my VPN connection began to fail:
Dec 13 09:49:37 xps13 NetworkManager[738]: Options error: Unrecognized option
or missing or extra parameter(s) in [CMD-LINE]:1: tls-remote (2.4_rc1)
(Options
On Thu, Dec 08, 2016 at 10:03:07PM +, Ben Hutchings wrote:
> Control: severity -1 serious
>
> Raising severity; this should be a release blocker.
>
> On Fri, 18 Mar 2016 18:42:24 + Wookey wrote:
> > Source: luajit
> > Version: 2.1.0~beta2+dfsg-1
> > Severity:
On Mon, Oct 31, 2016 at 12:11:31PM +0100, Alexander Kurtz wrote:
> This becomes even more important if you try to fix #842683 [1], so I
> propose a scheme looking something like this:
>
> * There is only one arch:all package called "ovmf" containing the
>builds for all architectures.
>
>
The documentation requested describes an interface of libvirt, not of
OVMF. It would make more sense to me that this documentation be
maintained in the libvirt package so it can be kept up to date and in
sync with the interface itself.
=medium
+
+ * Enable --with-numactl on arm64 (Closes: #838949).
+
+ -- dann frazier <da...@debian.org> Mon, 26 Sep 2016 18:42:57 -0600
+
libvirt (2.2.0-1) unstable; urgency=medium
* [7772549] New upstream version 2.2.0~rc1
diff -Nru libvirt-2.2.0/debian/control libvirt-2.2.0/debian/c
Source: libvirt
Version: 2.2.0-1
arm64 is currently omitted from the list of architectures built with
numactl support. arm64 platforms with NUMA support are available and,
even on non-NUMA implementations, libvirt needs to have NUMA support
enabled to expose the necessary capabilities to nova to
I removed my $HOME/.gscan2pdf file, and that worked around the issue.
Here's my old one for reference.
downsample dpi = 150
default filename = %a %y-%m-%d
selection = 3
selection = 0
selection = 457
selection = 751
auto-open-scan-dialog = 1
libsane-perl version = 0.05
author =
thumb panel = 100
Package: gscan2pdf
Version: 1.5.0-1
Severity: normal
gscan2pdf fails to start for me:
dannf@fuller:~$ gscan2pdf
Gtk-Message **: Failed to load module "canberra-gtk-module" at
/usr/lib/x86_64-linux-gnu/perl5/5.22/Gtk2.pm line 126.
Can't use string ("gimp %i") as an ARRAY ref while "strict refs"
an/changelog flash-kernel-3.68/debian/changelog
--- flash-kernel-3.67/debian/changelog 2016-06-20 00:20:31.0 -0600
+++ flash-kernel-3.68/debian/changelog 2016-07-13 09:33:53.714642651 -0600
@@ -1,3 +1,9 @@
+flash-kernel (3.68) UNRELEASED; urgency=medium
+
+ * Add support for gzip-compre
/control: libcoroutine1.58-dev: Add missing dependency on
+libcoroutine1.58.0. Closes: #819090.
+
+ -- dann frazier <da...@debian.org> Thu, 09 Jun 2016 12:51:17 -0600
+
boost1.58 (1.58.0+dfsg-5) unstable; urgency=medium
* Build Coroutine shared lib. Closes: #802509.
diff -Nru boo
tine, to avoid empty packages.
+Closes: #808626.
+
+ -- dann frazier <da...@debian.org> Thu, 09 Jun 2016 11:43:41 -0600
+
boost1.58 (1.58.0+dfsg-5) unstable; urgency=medium
* Build Coroutine shared lib. Closes: #802509.
diff -Nru boost1.58-1.58.0+dfsg/debian/control boost1.58-1.58.0+d
fyi, I backported the upstream fix to 2.1.0~beta2+dfsg-3 (attached), and
verified that it no longer segfaults.
$ luajit
LuaJIT 2.1.0-beta2 -- Copyright (C) 2005-2016 Mike Pall. http://luajit.org/
JIT: OFF
>
From: Mike Pall
Date: Mon, 18 Apr 2016 10:57:49 +0200
Subject: [PATCH] Rewrite memory
Package: valgrind
Version: 1:3.11.0-1
Tags: patch
This adds a simple smoke test, that also serves as a regression test
for an issue found in Ubuntu on s390x.
>From 3a277679b92c5040c8a801c6b6a706256692a70e Mon Sep 17 00:00:00 2001
From: dann frazier <da...@debian.org>
Date: Sat, 2 Apr 2
I made an attempt at fixing the s390x port by cargo culting what has
been done for other architectures. With this patch, I can connect to
the server and start an icewm desktop. However, the screen is still
pretty corrupted - text is offset, etc. See the attached screenshot.
Index:
Package: quilt
Version: 0.63-3
Severity: minor
Tags: patch
See attached patch.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64
Kernel:
The problem is that ipmitool is using strdup w/ -std=c99, where it is
not defined:
log.c: In function 'log_init':
log.c:112:19: warning: implicit declaration of function 'strdup'
[-Wimplicit-function-declaration]
logpriv->name = strdup(name);
^
log.c:112:17: warning:
Package: perftest
Version: 3.0+0.16.gb2f2e82-1
Severity: important
Tags: patch
Please modify perftest to build on any linux architecture vs. a
hardcoded list. This prevents perftest in Debian from gaining new
architecture support when it is added upstream (e.g. arm64 & s390x).
Build failures on
Package: perftest
Version: 3.0+0.16.gb2f2e82-1
Severity: important
Tags: patch
In addition to the patch in #814537, the attached patch is needed to
fix building on s390x.
From: dann frazier <dann.fraz...@canonical.com>
Subject: [PATCH] perftest: Fix typos in s390x support
Commit 472171
9, 2016 at 04:17:32PM -0700, dann frazier wrote:
> > On Sun, Dec 13, 2015 at 03:50:01PM +0100, Philipp Kern wrote:
> > > On Tue, Dec 08, 2015 at 03:17:49PM -0700, dann frazier wrote:
> > > > diff -Nru s390-tools-1.32.0/debian/changelog
> > > > s390-tools-
On Sun, Dec 13, 2015 at 03:50:01PM +0100, Philipp Kern wrote:
> On Tue, Dec 08, 2015 at 03:17:49PM -0700, dann frazier wrote:
> > diff -Nru s390-tools-1.32.0/debian/changelog
> > s390-tools-1.32.0/debian/changelog
> > --- s390-tools-1.32.0/debian/changelog 2015-10-
On Mon, Dec 14, 2015 at 11:31:26AM +0100, Hendrik Brueckner wrote:
> On Mon, Dec 14, 2015 at 09:28:08AM +0100, Hendrik Brueckner wrote:
> > On Sun, Dec 13, 2015 at 03:50:01PM +0100, Philipp Kern wrote:
> > > On Tue, Dec 08, 2015 at 03:17:49PM -0700, dann frazier wrote:
>
c2a892d).
>From fee3c101820b71fe912a7c875473b6154523 Mon Sep 17 00:00:00 2001
From: dann frazier <dann.fraz...@canonical.com>
Date: Tue, 5 Jan 2016 16:04:19 -0700
Subject: [PATCH 1/6] New upstream release, for GICv3 support.
---
debian/changelog
diff --git a/debian/changelog
Package: s390-tools
Version: 1.32.0-1
Severity: normal
Tags: patch
The source package provides a dbginfo.sh tool that is not currently
included in the binary package.
=medium
+
+ * Add dbginfo.sh. (Closes: #807442)
+
+ -- dann frazier <da...@debian.org> Tue, 08 Dec 2015 22:33:52 +0100
+
s390-tools (1.32.0-1) unstable; urgency=medium
* New upstream release
diff -Nru s390-tools-1.32.0/debian/s390-tools.install s390-tools-1.32.0/debian/s390-tools.i
=medium
+
+ * Add lsluns. (Closes: #807440)
+
+ -- dann frazier <da...@debian.org> Tue, 08 Dec 2015 22:33:52 +0100
+
s390-tools (1.32.0-1) unstable; urgency=medium
* New upstream release
diff -Nru s390-tools-1.32.0/debian/control s390-tools-1.32.0/debian/control
--- s390-tools-1.32.0/
Package: s390-tools
Version: 1.32.0-1
Severity: normal
Tags: patch
The source package provides an lsluns tool that is not currently
included in the binary package.
On Fri, Nov 06, 2015 at 11:59:18AM +0300, Michael Tokarev wrote:
> 05.11.2015 22:57, Michael Tokarev wrote:
> > 05.11.2015 22:13, dann frazier wrote:
> >> Package: qemu
> >> Version: 1:2.4+dfsg-4
> >> Severity: wishlist
> >> Tags: patch
> >>
with older libtool versions to ease
+backporting to releases where libtool-bin wasn't yet split out.
+
+ -- dann frazier <da...@debian.org> Wed, 04 Nov 2015 17:40:57 -0700
+
qemu (1:2.4+dfsg-4) unstable; urgency=medium
* applied 3 patches from upstream to fix virtio-net
diff --git a/
On Fri, Oct 23, 2015 at 09:14:54AM +0200, Jérémy Lal wrote:
> 2015-10-23 2:32 GMT+02:00 dann frazier <da...@debian.org>:
>
> > Source: nodejs
> > Version: 4.0.0~dfsg-2
> > Severity: wishlist
> > Tags: patch
> >
> > Attached is a patch to add a coup
Source: nodejs
Version: 4.0.0~dfsg-2
Severity: wishlist
Tags: patch
Attached is a patch to add a couple simple autopkgtests to nodejs.
diff -urpN nodejs-4.0.0~dfsg.orig/debian/control nodejs-4.0.0~dfsg/debian/control
--- nodejs-4.0.0~dfsg.orig/debian/control 2015-09-09 08:10:12.0 -0600
On Thu, Oct 08, 2015 at 08:19:58PM +0300, Michael Tokarev wrote:
> 07.10.2015 02:22, dann frazier wrote:
> > Package: qemu-system-arm
> > Version: 1:2.4+dfsg-3
> > Severity: wishlist
> > Tags: patch
> >
> > ARM systems with GICv3 support (such as Cavium
.
+
+ -- dann frazier <da...@debian.org> Tue, 06 Oct 2015 17:05:20 -0600
+
qemu (1:2.4+dfsg-3) unstable; urgency=high
* ne2000-add-checks-to-validate-ring-buffer-pointers-CVE-2015-5279.patch
diff -Nru qemu-2.4+dfsg/debian/patches/arm_kvm-Do-not-assume-particular-GIC-type-in-kvm_arc.patch qe
Package: freeipmi-tools
Version: 1.4.9-1
root@arm64:~# dmesg -c > /dev/null
root@arm64:~# ipmi-locate
Probing KCS device using DMIDECODE..[260235.853662] Unhandled fault:
synchronous external abort (0x92000210) at
Source: libguestfs
Version: 1:1.29.50-1
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertag: arm64
libguestfs currently FTBFS on arm64 due to a missing build of lzop
(#759452). However, once that build-dep is satisfied, libguestfs will
continue to FTBFS on arm64 due to a
On Wed, Aug 26, 2015 at 04:01:00PM +0200, gregor herrmann wrote:
Dear maintainer,
I've prepared an NMU for flamethrower (versioned as 0.1.8-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
Great, thanks!
: dann frazier da...@debian.org
Date: Tue, 25 Aug 2015 13:04:16 -0600
Subject: [PATCH] qemu-efi: Switch to Intel BDS. This supports a fallback to
the removable media path (i.e. \EFI\BOOT\BOOTaa64.EFI) as required by the
Linaro VM Specification.
---
debian/changelog | 6 ++
debian/rules | 1
--- mysql-5.6-5.6.25.orig/debian/tests/sysbench 1969-12-31 17:00:00.0 -0700
+++ mysql-5.6-5.6.25/debian/tests/sysbench 2015-07-24 11:55:22.526624572 -0600
@@ -0,0 +1,57 @@
+#!/bin/sh
+set -ex
+
+# dep8 sysbench test for mysql-server
+# Author: dann frazier da...@debian.org
+#
+# This test should
Package: sysbench
Version: 0.4.12-1.1
Severity: minor
Tags: patch
The manpage contains the typo defaut several times.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures:
29b1a88..cac8ace 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+mariadb-10.0 (10.0.19-2) UNRELEASED; urgency=medium
+
+ * d/p/Fixes-MDEV-7658-MDEV-7026-fix-reintroduces-MDEV-6615.patch:
+ Fix data corruption on arm64 (Closes: #787221).
+
+ -- dann frazier da...@debian.org Fri
Package: mariadb-server-10.0
Version: 10.0.19-1
Severity: important
The memory model on arm64 makes it susceptible to a data corruption
bug. Upstream, this is MDEV-7658:
https://mariadb.atlassian.net/browse/MDEV-7658
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
Source: seccomp
Version: 2.1.1-1
Severity: wishlist
fyi, libseccomp upstream has support for arm64 as of release 2.2.0.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
/armhf (from Ubuntu).
+Closes: #472188, #536544, #621409.
+
+ -- dann frazier da...@debian.org Thu, 02 Apr 2015 13:34:56 -0400
+
vnc4 (4.1.1+X4.3.0-37.5) experimental; urgency=medium
* Non-maintainer upload.
only in patch2:
unchanged:
--- vnc4-4.1.1+X4.3.0.orig/debian/patches
Package: partman-efi
Version: 62
Severity: normal
Tags: d-i patch
If you boot an x86/mac in legacy BIOS mode with a pre-existing non-UEFI OS
installed, you will get the following warning:
This machine's firmware has started the installer in UEFI mode but it looks
like there may be existing
Package: libdebian-installer4
Version: 0.98
Severity: serious
Tags: d-i patch
The map_hardware[] table in src/system/subarch-arm-linux.c is no longer NULL
terminated. I believe this could lead to a segfault on armel/armhf platforms,
resulting in a failed install.
This bug was introduced back in
On Wed, Jan 28, 2015 at 06:10:49PM +0100, Cyril Brulebois wrote:
dann frazier da...@debian.org (2015-01-28):
Package: libdebian-installer4
Version: 0.98
Severity: serious
Tags: d-i patch
The map_hardware[] table in src/system/subarch-arm-linux.c is no longer NULL
terminated. I
Source: edk2
Version: 0~20131112.2590861a-3
Severity: wishlist
Tags: patch
EDK II currently provides the only way to boot an ARM KVM instance
that can chain into the bootloader/kernel installed in a VM disk
image. Otherwise you have to pass QEMU a kernel on the commandline,
which makes it a pain
-Debian: http://bugs.debian.org/771114
Author: dann frazier da...@debian.org
Last-Update: 2014-12-18
Applied-Upstream: commit:r15697
Index: edk2-0~20131112.2590861a/BaseTools/Scripts/gcc4.4-ld-script
===
--- edk2-0~20131112.2590861a.orig
Source: edk2
Version: 0~20131112.2590861a-2
Severity: serious
edk2 FTBFS in current unstable and testing. A tail of the buildlog
follows.
Symbol renaming not needed for
tags 773492 + patch
thanks
The attached cherry pick from upstream fixes this issue and, combined
with the patch in #771114, allows edk2 to build from source in
unstable again.
Description: Fix undefined behavior in VfrCompiler.
Origin: http://sourceforge.net/p/edk2-buildtools/code/2667/
Source: edk2
Version: 0~20131112.2590861a-2
Severity: serious
edk2 FTBFS in current unstable and testing. A tail of the buildlog follows.
Building ...
/tmp/buildd/edk2-0~20131112.2590861a/MdeModulePkg/Library/DxeNetLib/DxeNetLib.inf
[X64]
GenFw -o
-maintainer upload.
+ * Temporarily revert fix for #769891 to qualify for jessie unblock.
+ * powerpc-undef-pixel.patch: Fix FTBFS on powerpc (Closes: #769976).
+
+ -- dann frazier da...@debian.org Mon, 24 Nov 2014 15:44:08 -0700
+
+vnc4 (4.1.1+X4.3.0-37.3) unstable; urgency=medium
+
+ * Non
On Thu, Nov 13, 2014 at 09:08:21PM +0100, Ola Lundqvist wrote:
Hi Dann
If you start it with tightvncserver command. Does it start then?
Nah - invoking it like that silently fails. I used this instantiation
(basically what tightvncserver calls on the user's behalf) to be able
to expose the
.
/ Ola
Inguza Technology AB
Sent from a phone
Den 14 nov 2014 01:30 skrev dann frazier da...@debian.org:
tags 769490 + patch
thanks
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
I'm working on an NMU for vnc4, so I tried out the proposed patch to
see if it was sufficient to get vnc4server built and running on
ppc64el. I did confirm that the build succeeds but, unfortunately, it
doesn't seem to function. Clients can authenticate, but then are
immediately disconnected w/ an
Source: vnc4
Version: 4.1.1+X4.3.0-37.1
Severity: important
vnc4 fails to build on arm64:
https://buildd.debian.org/status/fetch.php?pkg=vnc4arch=arm64ver=4.1.1%2BX4.3.0-37.1stamp=1410251248
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
tags 769490 + patch
thanks
Description: Add arm64 support
Author: dann frazier da...@debian.org
Last-Update: 2014-11-13
diff -urpN vnc4-4.1.1+X4.3.0.orig/unix/xc/config/cf/Imake.cf vnc4-4.1.1+X4.3.0/unix/xc/config/cf/Imake.cf
--- vnc4-4.1.1+X4.3.0.orig/unix/xc/config/cf/Imake.cf 2003-02-18 16:51
Package: tightvncserver
Version: 1.3.9-6.5
Severity: important
tightvncserver dumps core on startup on arm64:
dannf@mustang:~$ Xtightvnc :1 -desktop X -auth /home/dannf/.Xauthority
-geometry 1024x768 -depth 24 -rfbwait 12 -rfbport 5901 -fp
Package: lshw
Version: 02.17-1
Severity: important
Tags: patch
On HP Moonshot cartridges (ARM and x86) that have PCI-attached
Mellanox controllers, lshw reports only one of the two physical NICs,
and with the wrong MAC address.
This appears to be due to some code intended to avoid duplicates -
Package: lshw-gtk
Version: 02.17-1
The menu file still points to a .xpm file, whereas lshw-gtk is now
landing a .svg file:
dannf@fluid:~$ tr ' ' '\n' /usr/share/menu/lshw-gtk | grep icon
icon=/usr/share/pixmaps/lshw-gtk.xpm
dannf@fluid:~$ file /usr/share/pixmaps/lshw-gtk.xpm
Package: lshw-gtk
Version: 02.17-1
Severity: important
According to the Debian Menu System manual, section 3.7, menu icons
should be in xpm format:
https://www.debian.org/doc/packaging-manuals/menu.html/ch3.html#s3.7
Version 02.17-1 switched to an svg. Lintian has a test for this, but
it is
Source: llvm-toolchain-3.3
Version: 1:3.3-16
Severity: important
Tags: patch
The current debian/copyright file is missing several copyrights that
can be found w/ a grep - and some of the referenced paths are no
longer accurate due to file moves, etc. Attached is my attempt at a
more accurate
Source: crash
Version: 7.0.7-1
Severity: wishlist
crash has arm64 support, and the package builds/works on arm64 (at
least ps and bt). Please add arm64 to the list of architectures :)
(wishlist because arm64 isn't part of the official archive yet)
--
To UNSUBSCRIBE, email to
Package: lshw
Version: 02.16-2
Tags: patch
lshw currently assumes memory described by device-tree is DDR2, which
makes assumptions invalid for DDR3.
Specifically, it is unable to detect ecc and spd capabilities.
This is fixed upstream here:
http://ezix.org/project/changeset/2534/
--
To
tags 756921 + patch
thanks
Description: Add DDR3 support for systems described by device-tree
Origin: http://ezix.org/project/changeset/2534/
Bug-Debian: http://bugs.debian.org/756921
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1351921
diff --git a/src/core/device-tree.cc
Package: freeipmi-tools
Version: 1.1.5-4
Severity: normal
freeipmi-tools doesn't currently support the SSIF interface provided
on ARM-based HP moonshot cartridges:
$ sudo bmc-info --no-probing --driver-type=SSIF --driver-address=0x10
--driver-device=/dev/i2c-2 --get-device-id --debug
tags 754807 + patch
thanks
Description: Retry ssif reads as needed
Bug-Debian: http://bugs.debian.org/754807
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1324992
Author: Shashi Dande shashi.da...@hp.com
Last-Update: 2014-05-30
Applied-Upstream:
Package: lshw
Version: 02.16-2
device-tree data is defined as always being big-endian, but lshw
performs no conversion when running on a little-endian system like
armhf.
This has been fixed upstream:
http://ezix.org/project/ticket/645
--
To UNSUBSCRIBE, email to
tags 746616 + patch
thanks
diff -urpN lshw-02.16.orig/debian/patches/fix-645-endianness-problem-in-dev-tree-parsing.patch lshw-02.16/debian/patches/fix-645-endianness-problem-in-dev-tree-parsing.patch
--- lshw-02.16.orig/debian/patches/fix-645-endianness-problem-in-dev-tree-parsing.patch
Package: lshw
Version: 02.16-2
Severity: wishlist
Tags: patch
lshw, when executed as root, will troll through /dev/mem looking for
an smbios table. This causes an oops on some arm64 hardware.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
diff -u lshw-02.16/debian/changelog lshw-02.16/debian/changelog
--- lshw-02.16/debian/changelog
+++ lshw-02.16/debian/changelog
@@ -1,3 +1,10 @@
+lshw (02.16-3) UNRELEASED; urgency=medium
+
+ * Closes: #740034
+- Disable /dev/mem access for SMBIOS on aarch64 systems
+
+ -- dann frazier da
Package: numactl
Version: 2.0.9~rc5-1
Severity: wishlist
Please enable the arm64 and ppc64el architectures in debian/control.
The existing source package is known to build fine on these
architectures in Ubuntu:
https://launchpad.net/ubuntu/+source/numactl/2.0.9~rc5-1ubuntu1/+build/5603355
On Sat, Feb 15, 2014 at 08:50:50AM -0700, dann frazier wrote:
This may also fix LP: #545723.
s/LP://
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
) UNRELEASED; urgency=low
+
+ * Use dh-autoreconf to fix FTBFS on arm64
+
+ -- dann frazier da...@debian.org Sat, 15 Feb 2014 08:30:07 -0700
+
nis (3.17-32) unstable; urgency=low
* Fix postinst version comparison (closes: #610618).
diff -u nis-3.17/debian/control nis-3.17/debian/control
--- nis
On Thu, Dec 05, 2013 at 02:01:37PM +1100, Peter Chubb wrote:
dann == dann frazier da...@debian.org writes:
dann I've got a zx6000 here, but I'm unable to reproduce. Are we
dann using the same versions of firmware/elilo? I'm using the serial
dann console.
I'm using the serial console via
Source: efibootmgr
Version: 0.5.4-7
Severity: wishlist
Please add arm64 as a valid build target for efibootmgr. I've used an
Ubuntu trusty/arm64 chroot to verify that it does both build, install,
run w/o crashing - which is about as far as I can go w/o actual
EFI/arm64 hardware.
--
To
Source: tightvnc
Version: 1.3.9-6.4
Severity: minor
It doesn't appear to have any real effect, but note that
30-ftbfs-mips.patch typoes one instance of MipselArchitecture as
MipselArchitecure.
diff --git a/Xvnc/config/cf/linux.cf b/Xvnc/config/cf/linux.cf
index 1769a58..ec04b4d 100644
---
I've got a zx6000 here, but I'm unable to reproduce. Are we using the
same versions of firmware/elilo? I'm using the serial console.
Like Martin, my system is also a Madison - but clocked at 1.3GHz
vs. his 1.4.
EFI Boot Manager ver 1.10 [14.61] Firmware ver 2.31 [4411]
Please select a boot
Source: udisks
Version: 1.0.4-8
Severity: wishlist
udisks would fail to build on arm64 due to out-dated config.{sub,guess}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
; urgency=low
+
+ * Use dh-autoreconf to update config.{sub,guess} to fix FTBFS on arm64.
+(Closes: #725310)
+
+ -- dann frazier da...@debian.org Thu, 03 Oct 2013 20:06:43 -0600
+
udisks (1.0.4-8) unstable; urgency=low
* debian/patches/14-test-for-pci-db.patch: In newer versions of udev, pci
Source: libatasmart
Version: 0.19-2
Severity: wishlist
The build-aux/config.{sub,guess} files need updating to successfully
build on arm64.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Source: djvulibre
Version: 3.5.25.4-1
Severity: wishlist
djvulibre needs updated config.{sub,guess} files to build on arm64.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
) UNRELEASED; urgency=low
+
+ * Update config.{sub,guess} to fix FTBFS on arm64 (Closes: #722525)
+
+ -- dann frazier da...@debian.org Wed, 11 Sep 2013 17:58:28 -0600
+
djvulibre (3.5.25.4-1) unstable; urgency=low
* new upstream release
diff -Nru djvulibre-3.5.25.4/debian/patches/series
On Tue, Sep 03, 2013 at 11:04:25AM +0200, Jan Wagner wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
Am 01.09.13 23:47, schrieb dann frazier:
Source: linux Source-Version: 3.2.46-1+deb7u1
We believe that the bug you reported is fixed in the latest version
of linux
) UNRELEASED; urgency=low
+
+ [ Matthias Klose ]
+ * Update config.{guess,sub} for Aarch64.
+
+ [ dann frazier ]
+ * Move dh_quilt_apply into configure step so that config.{sub,guess}
+patches get applied before running configure. (Closes: 721203)
+
+ -- dann frazier da...@debian.org Thu, 29 Aug
Source: memcached
Version: 1.4.13-0.2
Severity: wishlist
Please update config.{sub,guess} in the source to allow building on
arm64. Note that, the way the package is currently structured,
configure is executed while quilt patches are unapplied. We could
update the source package in place, or
Package: dh-exec
Version: 0.9
Severity: serious
libpaper_1.1.24+nmu2 currently fails to build in sid. A tail of the
buildlog is below. These failures occur with dh-exec 0.9 and 0.10, but
going back to 0.8 works fine. From what I can tell, libpaper is using
dh-exec in a correct manner, so I'm
As mentioned in #720418, this started occurring after dh-exec 0.9, so
it might be a regression in that package.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Oops, apparently this is a dup w/ 711937 - looked at the wrong bug
page (libpaper vs src:libpaper) when searching for it. Will close
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: bonnie++
Version: 1.97.1
Severity: wishlist
Tags: patch
Please include this simple smoke test, in the current dep8 draft[*]
format, for use with autopkgtest.
[*] http://dep.debian.net/deps/dep8/
diff -urpN bonnie++-1.97.1.orig/debian/control bonnie++-1.97.1/debian/control
---
dannf@fluid:~$ svn diff -c2520 http://ezix.org/source/packages/lshw/development
Index: src/core/dmi.cc
===
--- src/core/dmi.cc (revision 2519)
+++ src/core/dmi.cc (revision 2520)
@@ -1752,8 +1752,8 @@
u16 dmimaj = 0, dmimin
dannf@fluid:~$ svn diff -c2521 http://ezix.org/source/packages/lshw/development
Index: src/core/device-tree.cc
===
--- src/core/device-tree.cc (revision 2520)
+++ src/core/device-tree.cc (revision 2521)
@@ -193,7 +193,8 @@
Package: lshw
Version: 02.16-1
Tags: patch
Severity: important
lshw may detect only 1 cpu core on devicetree-based platforms with 1
core. I've reported this upstream:
http://ezix.org/project/ticket/626
Attached is the patch I've provided, which is pending moderation
upstream.
---
/changelog 2013-05-01 18:19:56 +
@@ -1,3 +1,9 @@
+lshw (02.16-2) UNRELEASED; urgency=low
+
+ * Disable SMBIOS probe on ARM (LP: #1173672)
+
+ -- dann frazier da...@debian.org Wed, 01 May 2013 12:13:36 -0600
+
lshw (02.16-1) unstable; urgency=low
* New upstream release
=== added file
hey Dmitrijs!
I prepared a similar fix for this a couple of weeks ago that has been
in testing at a customer site. Looks like we crossed paths, but our
fixes are very similar. My patch has been working well for my test
case, and I've verified yours does too. However, I've a question on
your patch
On Fri, Sep 07, 2012 at 10:35:20AM -0700, Steve Lane wrote:
Hi Ben,
Is anything happening with this bug e.g. getting the patches into the
Debian stable kernel package (2.6.32) and a new version pushed out?
We had another meltdown at the end of August and it would be really
helpful to have
201 - 300 of 2273 matches
Mail list logo