Bug#749061: graphviz: Fix typo to ensure autoconf files are updated forbuild
Package: graphviz
Version: 2.26.3-17
Severity: serious
Tags: patch
Justification: fails to build from source
User: debian-...@lists.debian.org
Usertag: arm64
Graphviz now uses dh_autoreconf and has stuff in the rules file to
update all three copies of config.{sub,guess} (hooray!), but a path
mistake meant that the copies in libltld/config were not being
replaced (instead a 4th set was added in the dir above).
This meant that the libltld suddir ./configure on any arch too new for
the shipped config.{sub,guess} failed. This failed on arm64 as they
are too old for that.
A more robust fix for this would probably be to simply use
dh_autotools-dev as well as dh_autoreconf to ensure that all copies
are updated, without having to maintain paths to a list of them in the
rules file. I don't know if the maintainer had a good reason for
trying to avoid the use of that helper?
Attached is the minimal fix that keeps the existing mechanism but I
don't actually think this is better. I'm happy to do a fix using
autotools-dev if the maintainer would prefer (and NMU it).
Graphviz is blocking a lot of package builds on arm64 so I'd
appreciate either an upload or request to NMU reasonably quickly. Cheers.
-- System Information:
Debian Release: 7.5
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-kvm-i386-20110111 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -Nru graphviz-2.26.3/debian/changelog graphviz-2.26.3/debian/changelog
--- graphviz-2.26.3/debian/changelog 2014-04-20 14:17:40.0 +
+++ graphviz-2.26.3/debian/changelog 2014-05-23 14:26:24.0 +
@@ -1,3 +1,9 @@
+graphviz (2.26.3-17+cfg) unreleased; urgency=low
+
+ * Correct typo in rules so config.{sub,guess} is actually updated.
+
+ -- Wookey Fri, 23 May 2014 14:25:42 +
+
graphviz (2.26.3-17) unstable; urgency=medium
* QA upload.
diff -Nru graphviz-2.26.3/debian/rules graphviz-2.26.3/debian/rules
--- graphviz-2.26.3/debian/rules 2014-02-12 02:45:51.0 +
+++ graphviz-2.26.3/debian/rules 2014-05-23 14:24:42.0 +
@@ -35,8 +35,8 @@
RUBY_PACKAGE = $(CURDIR)/debian/libgv-ruby
-CONFIG_SCRIPTS=config/config.guess lib/gd/config/config.guess libltdl/config.guess \
- config/config.sub lib/gd/config/config.sub libltdl/config.sub
+CONFIG_SCRIPTS=config/config.guess lib/gd/config/config.guess libltdl/config/config.guess \
+ config/config.sub lib/gd/config/config.sub libltdl/config/config.sub
# make's $(shell) doesn't use local variables, thus we need to define a
# custom command where DEB_LDFLAGS_MAINT_APPEND is passed.
Bug#749061: graphviz: diff for NMU version 2.26.3-17.1
tags 749061 + pending
thanks
Dear maintainer,
I've prepared an NMU for graphviz (versioned as 2.26.3-17.1)
fixing this issue, which unblocks a lot of packages for the arm64 port.
I've uploaded it to DELAYED/2. Please feel free to tell me that I
should delay it longer.
cheers
--
Wookey
diff -Nru graphviz-2.26.3/debian/changelog graphviz-2.26.3/debian/changelog
--- graphviz-2.26.3/debian/changelog 2014-04-20 15:17:40.0 +0100
+++ graphviz-2.26.3/debian/changelog 2014-06-06 18:17:05.0 +0100
@@ -1,3 +1,11 @@
+graphviz (2.26.3-17.1) unstable; urgency=low
+
+ * Non-maintainer upload
+ * Correct typo in rules so config.{sub,guess} is actually updated.
+(Closes: #749061)
+
+ -- Wookey Fri, 23 May 2014 14:25:42 +
+
graphviz (2.26.3-17) unstable; urgency=medium
* QA upload.
diff -Nru graphviz-2.26.3/debian/rules graphviz-2.26.3/debian/rules
--- graphviz-2.26.3/debian/rules 2014-02-12 02:45:51.0 +
+++ graphviz-2.26.3/debian/rules 2014-05-23 15:24:42.0 +0100
@@ -35,8 +35,8 @@
RUBY_PACKAGE = $(CURDIR)/debian/libgv-ruby
-CONFIG_SCRIPTS=config/config.guess lib/gd/config/config.guess libltdl/config.guess \
- config/config.sub lib/gd/config/config.sub libltdl/config.sub
+CONFIG_SCRIPTS=config/config.guess lib/gd/config/config.guess libltdl/config/config.guess \
+ config/config.sub lib/gd/config/config.sub libltdl/config/config.sub
# make's $(shell) doesn't use local variables, thus we need to define a
# custom command where DEB_LDFLAGS_MAINT_APPEND is passed.
Bug#727448: libxcrypt: diff for NMU version 1:2.4-3.1
tags 727448 + patch
tags 727448 + pending
thanks
Dear maintainer,
This bug has been pending for some time, and needs fixing for new
ports, including arm64 which is building now:
(http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid).
So I've prepared an NMU for libxcrypt (versioned as 1:2.4-3.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
delay it longer.
Discussion on debian-devel revealed consensus that the right way to
ensure successful builds on all new architectures was to autoreconf
packages, so that method has been used to fix this bug. This works for
all arches, even those that need libtool changes, and will continue to
work into the future without an update as each new arch comes along.
(Discussion at
https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread
starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html
As you can see this works fine on this package, and is a very simple
patch.
Regards.
diff -u libxcrypt-2.4/debian/changelog libxcrypt-2.4/debian/changelog
--- libxcrypt-2.4/debian/changelog
+++ libxcrypt-2.4/debian/changelog
@@ -1,3 +1,10 @@
+libxcrypt (1:2.4-3.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Use dh-autoreconf in build to support new architectures (closes: #727448)
+
+ -- Chen Baozi Thu, 05 Jun 2014 20:38:32 +0800
+
libxcrypt (1:2.4-3) unstable; urgency=low
* QA upload (see #679703). Skipping 1:2.4-2 to avoid archive filename
diff -u libxcrypt-2.4/debian/rules libxcrypt-2.4/debian/rules
--- libxcrypt-2.4/debian/rules
+++ libxcrypt-2.4/debian/rules
@@ -35,6 +35,7 @@
config.status: configure
dh_testdir
+ dh_autoreconf
# Add here commands to configure the package.
CFLAGS="$(CFLAGS)" ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info
@@ -64,7 +65,7 @@
#cp -f /usr/share/misc/config.guess config.guess
endif
-
+ dh_autoreconf_clean
dh_clean
install: build
diff -u libxcrypt-2.4/debian/control libxcrypt-2.4/debian/control
--- libxcrypt-2.4/debian/control
+++ libxcrypt-2.4/debian/control
@@ -2,7 +2,7 @@
Section: libs
Priority: optional
Maintainer: Debian QA Group
-Build-Depends: debhelper (>= 4.0.0), quilt
+Build-Depends: debhelper (>= 4.0.0), quilt, dh-autoreconf
Standards-Version: 3.6.0
Package: libxcrypt-dev
Bug#749061: graphviz: Fix typo to ensure autoconf files are updated forbuild
Hmm, apparently I failed to actually upload this. Trying again... Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140623165604.go10...@stoneboat.aleph1.co.uk
Bug#727949: proxsmtp: diff for NMU version 1.10-2.1
tags 727949 + patch tags 727949 + pending thanks Dear maintainer, This bug has been pending for some time, and needs fixing for new ports, including arm64 which is building now: (http://buildd.debian-ports.org/status/architecture.php?a=arm64&suite=sid). So I've prepared an NMU for proxsmtp (versioned as 1.10-2.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Discussion on debian-devel revealed consensus that the right way to ensure successful builds on all new architectures was to autoreconf packages, so that method has been used to fix this bug. This works for all arches, even those that need libtool changes, and will continue to work into the future without an update as each new arch comes along. (Discussion at https://lists.debian.org/debian-devel/2014/04/msg00383.html, thread starting at https://lists.debian.org/debian-devel/2014/04/msg00342.html As you can see this works fine on this package, and is a very simple patch. Regards. diff -u proxsmtp-1.10/debian/changelog proxsmtp-1.10/debian/changelog --- proxsmtp-1.10/debian/changelog +++ proxsmtp-1.10/debian/changelog @@ -1,3 +1,10 @@ +proxsmtp (1.10-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Use dh-autoreconf in build to support new architectures (Closes: #727949) + + -- Chen Baozi Fri, 06 Jun 2014 20:37:55 +0800 + proxsmtp (1.10-2) unstable; urgency=low * QA upload. diff -u proxsmtp-1.10/debian/control proxsmtp-1.10/debian/control --- proxsmtp-1.10/debian/control +++ proxsmtp-1.10/debian/control @@ -2,7 +2,7 @@ Section: mail Priority: optional Maintainer: Debian QA Group -Build-Depends: debhelper (>= 9), libcap-dev +Build-Depends: debhelper (>= 9), libcap-dev, dh-autoreconf Standards-Version: 3.9.1 Vcs-Browser: http://git.debian.org/?p=collab-maint/proxsmtp.git;a=summary Vcs-Git: git://git.debian.org/git/collab-maint/proxsmtp.git diff -u proxsmtp-1.10/debian/rules proxsmtp-1.10/debian/rules --- proxsmtp-1.10/debian/rules +++ proxsmtp-1.10/debian/rules @@ -3 +3 @@ - dh $@ + dh $@ --with autoreconf
Bug#759439: xplc: run dh-autoreconf to update for new architectures
Package: xplc Version: 0.3.13-4 Severity: normal User: debian-...@lists.debian.org Usertag: arm64 This package failed to build on arm64. Here is the buildd log: https://buildd.debian.org/status/fetch.php?pkg=xplc&arch=arm64&ver=0.3.13-4&stamp=1408246663. It is one of hundreds of packages which need autoconf updates in order to build on new architectures such as arm64, mips64el, ppc64el and or1k. Re-autoconfing is the recommended way to deal with the general case of this problem in Debian, as it works now and in the future, and ensures packages remain buildable from source. This page ( https://wiki.debian.org/Autoreconf ) contains information on this issue, and details for maintainers on how to update their packages: The porter teams are working hard to get the new architectures ready for jessie, and time is short, so do please try to fix this issue promptly. It's often trivial to do. -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.60-kvm-i386-20140609 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140827095601.24426.85192.report...@stoneboat.aleph1.co.uk
Bug#765231: libwfut: run dh-autoreconf to update for new architectures
Source: libwfut Version: 0.2.1-3 Severity: normal User: debian-...@lists.debian.org Usertag: arm64 This package failed to build on arm64. Here is the buildd log: https://buildd.debian.org/status/fetch.php?pkg=libwfut&arch=arm64&ver=0.2.1-3&stamp=1408643663 The problem appears to be out of date autoconf files (config.sub and guess). It is one of many packages which need autoconf updates in order to build on new architectures (such as arm64, mips64el, ppc64el and or1k). 'Autoreconf'ing is the recommended way to deal with this problem in Debian, as it works now and in the future, and ensures packages remain buildable from source. This page ( https://wiki.debian.org/Autoreconf ) contains information on this issue, and details for maintainers on how to update your packages: The arm64 and ppc64el porter teams are working hard to get these new architectures ready for jessie, and time is short, so do please try to fix this issue promptly. Unless the autofoo in the package is way out of date, it's often trivial to do. Please ignore/close this message if it is in error, and accept my apologies for the noise. It may have already been fixed, or a new upload done since the list was generated. Also the automated checks for characteristic log messages can sometimes produce false positives, despite our best efforts. -- System Information: Debian Release: jessie/sid APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141013212100.2235.25774.report...@kh.home.wookware.org
Bug#1031193: Acknowledgement (gthumb segfaults on startup)
On 2023-02-13 00:36 +, Debian Bug Tracking System wrote: Having upgraded 1.5Gb of packages since the 8th, and restarted X this issue has gone away. gthumb works fine now. I noticed a couple of other GUI apps that would not start (giving X errors): (therion and aven (survex)). Those use tcltk and wxwindows respectively. But plenty of things _were_ working. I guess there was something wrong in some library/package that has been superseded for Bookworm already so this bug can probably be closed unless a load of other people report the same issue. Wookey -- Principal hats: Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Bug#692344: wicd-curses dies when moving around a conference
Issue still present in v 1.7.2.4-4.1
(rebuilt from testing/unstable source on jessie)
The line-numbers have changed from the original report in 2012 but the error
seems to be identical.
Can we just take out the dbus assert for this as it seems to be inappropriate?
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
return func(*args, **kargs)
File "/usr/share/wicd/curses/wicd-curses.py", line 920, in update_status
if check_for_wired(wired.GetWiredIP(''), self.set_status):
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not
receive a reply. Possible causes include: the remote application did not send a
reply, the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: Digital signature
Bug#692344: wicd-curses dies when moving around a conference
+++ Axel Beckert [2016-03-11 11:52 +0100]: > Hi Wookey, > > Wookey wrote: > > Issue still present in v 1.7.2.4-4.1 > > (rebuilt from testing/unstable source on jessie) > > Are you sure about that version number? Testing/Unstable currently has > 1.7.4+tb2-1. 1.7.2.4-4.1 is the version in Jessie. Sorry. The version I have installed is 1.7.4+tb2-1, so I did test the right one. What I don't understand is why everyone isn't complaining about this. It's been affecting me at nearly every conference for 3-4 years... Does everyone else put up with it, or is there something odd about my setup that makes it possible to get a dbus message failure? > > Can we just take out the dbus assert for this as it seems to be > > inappropriate? > > I'll have a look. Thanks for the hint. I know nothing about dbus. It seems that the author thinks this should never happen. All I know is that it happens nearly every time I move between wifi zones (on an x200 thinkpad - amybe it's specific to the wifi chipset/driver). Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: Digital signature
Bug#692344: wicd-curses dies when moving around a conference
+++ Axel Beckert [2016-03-13 02:25 +0100]: > > What I don't understand is why everyone isn't complaining about > > this. It's been affecting me at nearly every conference for 3-4 > > years... Does everyone else put up with it, or is there something odd > > about my setup that makes it possible to get a dbus message failure? > > At least in my case, I usually run wicd-curses only if I need it and > don't have it running all the time. Good point - I guess most people use wicd-gtk, which doesn't have this issue. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: Digital signature
