Bug#1074523: python-sshoot: autopkgtest failure with Python 3.12

[Graham Inggs]

Source: python-sshoot
Version: 1.4.2-3
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

python-sshoot's autopkgtests fail with Python 3.12 [1].  I've copied
what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-sshoot/testing/amd64/


37s autopkgtest [01:06:51]: test command1: [---
37s
37s # Failed test 'Check return from 'sshoot' is 2'
37s # at debian/tests/sshoot.t line 9.
37s # got: '1'
37s # expected: '2'
37s
37s # Failed test 'bare command, stderr'
37s # at debian/tests/sshoot.t line 11.
37s # 'Traceback (most recent call last):
37s # File "/usr/bin/sshoot", line 33, in 
37s # sys.exit(load_entry_point('sshoot==1.4.2', 'console_scripts', 'sshoot')())
37s # ^^
37s # File "/usr/bin/sshoot", line 25, in importlib_load_entry_point
37s # return next(matches).load()
37s # 
37s # File "/usr/lib/python3.12/importlib/metadata/__init__.py", line
205, in load
37s # module = import_module(match.group('module'))
37s # 
37s # File "/usr/lib/python3.12/importlib/__init__.py", line 90, in
import_module
37s # return _bootstrap._gcd_import(name[level:], package, level)
37s # 
37s # File "", line 1387, in _gcd_import
37s # File "", line 1360, in _find_and_load
37s # File "", line 1310, in
_find_and_load_unlocked
37s # File "", line 488, in
_call_with_frames_removed
37s # File "", line 1387, in _gcd_import
37s # File "", line 1360, in _find_and_load
37s # File "", line 1331, in
_find_and_load_unlocked
37s # File "", line 935, in _load_unlocked
37s # File "", line 995, in exec_module
37s # File "", line 488, in
_call_with_frames_removed
37s # File "/usr/lib/python3/dist-packages/sshoot/__init__.py", line
3, in 
37s # from distutils.version import LooseVersion
37s # ModuleNotFoundError: No module named 'distutils'

Bug#1065937: python-sparkpost: Please drop dependencies on python3-distutils

[Graham Inggs]

Source: python-sparkpost
Version: 1.3.10-2
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

This package has dependencies, build-dependencies and/or autopkgtest
dependencies on python3-distutils.  The python3-distutils binary
package will soon be dropped from python3-stdlib-extensions.

In fact, there is no module for Python 3.12 in python3-distutils, so
these dependencies may already be unnecessary.

Regards
Graham

Bug#1065925: python-djvulibre: Please drop dependencies on python3-distutils

[Graham Inggs]

Source: python-djvulibre
Version: 0.9.0-3
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

This package has dependencies, build-dependencies and/or autopkgtest
dependencies on python3-distutils.  The python3-distutils binary
package will soon be dropped from python3-stdlib-extensions.

In fact, there is no module for Python 3.12 in python3-distutils, so
these dependencies may already be unnecessary.

Regards
Graham

Bug#1065915: pdfkit: Please drop dependencies on python3-distutils

[Graham Inggs]

Source: pdfkit
Version: 1.0.0-3
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

This package has dependencies, build-dependencies and/or autopkgtest
dependencies on python3-distutils.  The python3-distutils binary
package will soon be dropped from python3-stdlib-extensions.

In fact, there is no module for Python 3.12 in python3-distutils, so
these dependencies may already be unnecessary.

Regards
Graham

Bug#1065843: djvubind: Please drop dependencies on python3-distutils

[Graham Inggs]

Source: djvubind
Version: 1.2.1-5
Severity: important
Tags: ftbfs trixie sid
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

This package has dependencies, build-dependencies and/or autopkgtest
dependencies on python3-distutils.  The python3-distutils binary
package will soon be dropped from python3-stdlib-extensions.

In fact, there is no module for Python 3.12 in python3-distutils, so
these dependencies may already be unnecessary.

Regards
Graham

Bug#1062039: SyntaxWarning: invalid escape sequence

[Graham Inggs]

Control: tags -1 + patch

The patch below was applied in Ubuntu.

--- a/axi/__init__.py
+++ b/axi/__init__.py
@@ -51,8 +51,8 @@
 Read the "/etc/services"-style database of value indices
 """
 try:
-re_empty = re.compile("^\s*(?:#.*)?$")
-re_value = re.compile("^(\S+)\s+(\d+)(?:\s*#\s*(.+))?$")
+re_empty = re.compile(r"^\s*(?:#.*)?$")
+re_value = re.compile(r"^(\S+)\s+(\d+)(?:\s*#\s*(.+))?$")
 values: dict[str, int] = {}
 descs: dict[str, str] = {}
 for idx, line in enumerate(open(pathname)):

Bug#1064961: apt-xapian-index: fails with Python 3.12

[Graham Inggs]

Package: src:apt-xapian-index
Version: 0.54
Severity: important
Tags: patch
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

apt-xapian-index fails when Python 3.12 is the default.

$ axi-cache info
Traceback (most recent call last):
  File "/usr/bin/axi-cache", line 864, in 
sys.exit(ui.perform())
 
  File "/usr/bin/axi-cache", line 855, in perform
return f(self.args)
   
  File "/usr/bin/axi-cache", line 411, in do_info
import axi.indexer
  File "/usr/lib/python3/dist-packages/axi/indexer.py", line 27, in 
import imp
ModuleNotFoundError: No module named 'imp'

The patch below was applied in Ubuntu.

Regards
Graham


--- a/axi/indexer.py
+++ b/axi/indexer.py
@@ -23,7 +23,7 @@
 import axi
 import sys
 import os
-import imp
+from importlib.machinery import SourceFileLoader
 import socket, errno
 import fcntl
 import textwrap
@@ -59,7 +59,7 @@
 oldpath = sys.path
 try:
 sys.path.append(os.path.dirname(fname))
-self.module = imp.load_source("axi.plugin_" + self.name, fname)
+self.module = SourceFileLoader("axi.plugin_" + self.name,
fname).load_module()
 finally:
 sys.path = oldpath
 try:

Bug#1063222: obexftp: NMU diff for 64-bit time_t transition

[Graham Inggs]

Source: obexftp
Version: 0.24-9
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
obexftp as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for obexftp
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru obexftp-0.24/debian/changelog obexftp-0.24/debian/changelog
--- obexftp-0.24/debian/changelog   2022-12-20 02:01:53.0 +
+++ obexftp-0.24/debian/changelog   2024-02-05 18:27:16.0 +
@@ -1,3 +1,10 @@
+obexftp (0.24-9.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs   Mon, 05 Feb 2024 18:27:16 +
+
 obexftp (0.24-9) unstable; urgency=medium
 
   * QA upload.
diff -Nru obexftp-0.24/debian/control obexftp-0.24/debian/control
--- obexftp-0.24/debian/control 2022-12-20 02:01:53.0 +
+++ obexftp-0.24/debian/control 2024-02-05 18:27:16.0 +
@@ -42,7 +42,10 @@
  This is the command line front-end that fully uses the capabilities of
  libobexftp. It also includes obexfs, the FUSE backend.
 
-Package: libbfb0
+Package: libbfb0t64
+Provides: ${t64:Provides}
+Replaces: libbfb0
+Breaks: libbfb0 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends:
@@ -66,7 +69,7 @@
  libbfb-dev,
  libobexftp-dev (<< 0.22),
 Depends:
- libbfb0 (= ${binary:Version}),
+ libbfb0t64 (= ${binary:Version}),
  ${misc:Depends},
 Description: bfb protocol library - development files
  This library adds support for OBEX protocol over BFB/BFC, some Siemens
@@ -76,7 +79,10 @@
  .
  This package contains the development files.
 
-Package: libmulticobex1
+Package: libmulticobex1t64
+Provides: ${t64:Provides}
+Replaces: libmulticobex1
+Breaks: libmulticobex1 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends:
@@ -98,7 +104,7 @@
  libobexftp-dev (<< 0.22),
 Depends:
  libbfb-dev,
- libmulticobex1 (= ${binary:Version}),
+ libmulticobex1t64 (= ${binary:Version}),
  ${misc:Depends},
 Description: multi-protocol cable OBEX library - development files
  This library add support for making use of several ways to use OBEX
@@ -106,7 +112,10 @@
  .
  This package contains the development files.
 
-Package: libobexftp0
+Package: libobexftp0t64
+Provides: ${t64:Provides}
+Replaces: libobexftp0
+Breaks: libobexftp0 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends:
@@ -132,7 +141,7 @@
  libobexftp-dev (<< 0.22),
 Depends:
  libmulticobex1-dev,
- libobexftp0 (= ${binary:Version}),
+ libobexftp0t64 (= ${binary:Version}),
  libopenobex2-dev,
  ${misc:Depends},
 Description: object exchange file transfer library - development files
@@ -149,7 +158,7 @@
 Section: ruby
 Build-Profiles: 
 Depends:
- libobexftp0 (= ${binary:Version}),
+ libobexftp0t64 (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends},
  ${ruby:Depends},
@@ -173,7 +182,7 @@
 Section: perl
 Build-Profiles: 
 Depends:
- libobexftp0 (= ${binary:Version}),
+ libobexftp0t64 (= ${binary:Version}),
  ${misc:Depends},
  ${perl:Depends},
  ${shlibs:Depends},
diff -Nru obexftp-0.24/debian/libbfb0.install 
obexftp-0.24/debian/lib

Bug#1063213: nsync: NMU diff for 64-bit time_t transition

[Graham Inggs]

Source: nsync
Version: 1.26.0-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
nsync as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for nsync
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru nsync-1.26.0/debian/changelog nsync-1.26.0/debian/changelog
--- nsync-1.26.0/debian/changelog   2023-12-10 21:57:25.0 +
+++ nsync-1.26.0/debian/changelog   2024-02-05 17:59:48.0 +
@@ -1,3 +1,10 @@
+nsync (1.26.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs   Mon, 05 Feb 2024 17:59:48 +
+
 nsync (1.26.0-1) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru nsync-1.26.0/debian/control nsync-1.26.0/debian/control
--- nsync-1.26.0/debian/control 2023-12-10 21:54:19.0 +
+++ nsync-1.26.0/debian/control 2024-02-05 17:59:48.0 +
@@ -8,7 +8,10 @@
 Maintainer: Debian QA Group 
 Build-Depends: cmake, debhelper-compat (= 13)
 
-Package: libnsync1
+Package: libnsync1t64
+Provides: ${t64:Provides}
+Replaces: libnsync1
+Breaks: libnsync1 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -24,7 +27,10 @@
  .
  This package ships C shared object.
 
-Package: libnsync-cpp1
+Package: libnsync-cpp1t64
+Provides: ${t64:Provides}
+Replaces: libnsync-cpp1
+Breaks: libnsync-cpp1 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -44,8 +50,8 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libnsync-cpp1 (= ${binary:Version}),
- libnsync1 (= ${binary:Version}),
+Depends: libnsync-cpp1t64 (= ${binary:Version}),
+ libnsync1t64 (= ${binary:Version}),
  ${misc:Depends}
 Description: C library that exports various synchronization primitives (dev)
  nsync is a C library that exports various synchronization primitives:
diff -Nru nsync-1.26.0/debian/libnsync-cpp1.install 
nsync-1.26.0/debian/libnsync-cpp1.install
--- nsync-1.26.0/debian/libnsync-cpp1.install   2023-12-10 21:51:54.0 
+
+++ nsync-1.26.0/debian/libnsync-cpp1.install   1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/libnsync_cpp.so.*
diff -Nru nsync-1.26.0/debian/libnsync-cpp1.symbols 
nsync-1.26.0/debian/libnsync-cpp1.symbols
--- nsync-1.26.0/debian/libnsync-cpp1.symbols   2023-12-10 21:51:54.0 
+
+++ nsync-1.26.0/debian/libnsync-cpp1.symbols   1970-01-01 00:00:00.0 
+
@@ -1,93 +0,0 @@
-libnsync_cpp.so.1 libnsync-cpp1 #MINVER#
- _ZN5nsync12nsync_panic_EPKc@Base 1.20.1
- _ZN5nsync12nsync_wait_nEPvPFvS0_ES2_8timespeciPPNS_16nsync_waitable_sE@Base 
1.20.1
- _ZN5nsync12nsync_yield_Ev@Base 1.20.1
- _ZN5nsync13nsync_cv_initEPNS_11nsync_cv_s_E@Base 1.20.1
- _ZN5nsync13nsync_cv_waitEPNS_11nsync_cv_s_EPNS_11nsync_mu_s_E@Base 1.20.1
- _ZN5nsync13nsync_mu_initEPNS_11nsync_mu_s_E@Base 1.20.1
- _ZN5nsync13nsync_mu_lockEPNS_11nsync_mu_s_E@Base 1.20.1
- _ZN5nsync13nsync_mu_waitEPNS_11nsync_mu_s_EPFiPKvES3_PFiS3_S3_E@Base 1.20.1
- _ZN5nsync13nsync_time_msEj@Base 1.20.1
- _ZN5nsync13nsync_time_usEj

Bug#1063160: ncap: NMU diff for 64-bit time_t transition

[Graham Inggs]

Source: ncap
Version: 1.9.2-8
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
ncap as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for ncap
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru ncap-1.9.2/debian/changelog ncap-1.9.2/debian/changelog
--- ncap-1.9.2/debian/changelog 2022-09-12 04:28:32.0 +
+++ ncap-1.9.2/debian/changelog 2024-02-05 13:50:40.0 +
@@ -1,3 +1,10 @@
+ncap (1.9.2-8.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs   Mon, 05 Feb 2024 13:50:40 +
+
 ncap (1.9.2-8) unstable; urgency=medium
 
   * QA upload.
diff -Nru ncap-1.9.2/debian/control ncap-1.9.2/debian/control
--- ncap-1.9.2/debian/control   2020-09-12 20:47:14.0 +
+++ ncap-1.9.2/debian/control   2024-02-05 13:50:40.0 +
@@ -11,7 +11,10 @@
 Vcs-Browser: https://salsa.debian.org/debian/ncap
 Vcs-Git: https://salsa.debian.org/debian/ncap.git
 
-Package: libncap44
+Package: libncap44t64
+Provides: ${t64:Provides}
+Replaces: libncap44
+Breaks: libncap44 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -29,7 +32,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libncap44 (= ${binary:Version}), ${misc:Depends}
+Depends: libncap44t64 (= ${binary:Version}), ${misc:Depends}
 Description: static library and header files for libncap
  ncap is a network capture library like libpcap (on which it is based)
  and tcpdump. It produces binary data in its own ncap format, which can
diff -Nru ncap-1.9.2/debian/libncap44.install 
ncap-1.9.2/debian/libncap44.install
--- ncap-1.9.2/debian/libncap44.install 2020-09-12 20:44:16.0 +
+++ ncap-1.9.2/debian/libncap44.install 1970-01-01 00:00:00.0 +
@@ -1,2 +0,0 @@
-usr/lib/*/libncap*.so.*
-usr/share/man/man3/ncap.3
diff -Nru ncap-1.9.2/debian/libncap44.symbols 
ncap-1.9.2/debian/libncap44.symbols
--- ncap-1.9.2/debian/libncap44.symbols 2020-09-12 20:44:16.0 +
+++ ncap-1.9.2/debian/libncap44.symbols 1970-01-01 00:00:00.0 +
@@ -1,8 +0,0 @@
-libncap.so.44 libncap44 #MINVER#
-* Build-Depends-Package: libncap-dev
- ncap_addrule@Base 1.9.2
- ncap_asprintf@Base 1.9.2
- ncap_create@Base 1.9.2
- ncap_filter_dns@Base 1.9.2
- ncap_filter_icmp@Base 1.9.2
- ncap_vasprintf@Base 1.9.2
diff -Nru ncap-1.9.2/debian/libncap44t64.install 
ncap-1.9.2/debian/libncap44t64.install
--- ncap-1.9.2/debian/libncap44t64.install  1970-01-01 00:00:00.0 
+
+++ ncap-1.9.2/debian/libncap44t64.install  2020-09-12 20:44:16.0 
+
@@ -0,0 +1,2 @@
+usr/lib/*/libncap*.so.*
+usr/share/man/man3/ncap.3
diff -Nru ncap-1.9.2/debian/libncap44t64.lintian-overrides 
ncap-1.9.2/debian/libncap44t64.lintian-overrides
--- ncap-1.9.2/debian/libncap44t64.lintian-overrides1970-01-01 
00:00:00.0 +
+++ ncap-1.9.2/debian/libncap44t64.lintian-overrides2024-02-05 
13:50:40.0 +
@@ -0,0 +1 @@
+libncap44t64: package-name-doesnt-match-sonames libncap44
diff -Nru ncap-1.9.2/

Bug#1062521: lcm: NMU diff for 64-bit time_t transition

[Graham Inggs]

Source: lcm
Version: 1.3.1+repack1-7
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
lcm as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for lcm
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru lcm-1.3.1+repack1/debian/changelog lcm-1.3.1+repack1/debian/changelog
--- lcm-1.3.1+repack1/debian/changelog  2023-12-06 20:48:38.0 +
+++ lcm-1.3.1+repack1/debian/changelog  2024-02-01 18:25:16.0 +
@@ -1,3 +1,10 @@
+lcm (1.3.1+repack1-7.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs   Thu, 01 Feb 2024 18:25:16 +
+
 lcm (1.3.1+repack1-7) unstable; urgency=medium
 
   * QA upload.
diff -Nru lcm-1.3.1+repack1/debian/control lcm-1.3.1+repack1/debian/control
--- lcm-1.3.1+repack1/debian/control2023-12-06 00:27:57.0 +
+++ lcm-1.3.1+repack1/debian/control2024-02-01 18:25:16.0 +
@@ -12,7 +12,10 @@
 Vcs-Browser: https://salsa.debian.org/debian/lcm
 Rules-Requires-Root: no
 
-Package: liblcm1
+Package: liblcm1t64
+Provides: ${t64:Provides}
+Replaces: liblcm1
+Breaks: liblcm1 (<< ${source:Version})
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Lightweight Communications and Marshalling
@@ -26,7 +29,7 @@
 
 Package: liblcm-dev
 Architecture: any
-Depends: liblcm1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
+Depends: liblcm1t64 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
  liblcm-bin
 Description: Lightweight Communications and Marshalling
  LCM is a set of libraries and tools for message passing and data marshalling,
@@ -39,7 +42,7 @@
 
 Package: liblcm-bin
 Architecture: any
-Depends: liblcm1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
+Depends: liblcm1t64 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
 Description: Lightweight Communications and Marshalling
  LCM is a set of libraries and tools for message passing and data marshalling,
  targeted at real-time systems where high-bandwidth and low latency are
@@ -51,7 +54,7 @@
 
 Package: liblcm-java
 Architecture: any
-Depends: liblcm1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
+Depends: liblcm1t64 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
  liblcm-bin
 Description: Lightweight Communications and Marshalling
  LCM is a set of libraries and tools for message passing and data marshalling,
diff -Nru lcm-1.3.1+repack1/debian/liblcm1.install 
lcm-1.3.1+repack1/debian/liblcm1.install
--- lcm-1.3.1+repack1/debian/liblcm1.install2023-12-06 00:27:57.0 
+
+++ lcm-1.3.1+repack1/debian/liblcm1.install1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/*.so.*
diff -Nru lcm-1.3.1+repack1/debian/liblcm1t64.install 
lcm-1.3.1+repack1/debian/liblcm1t64.install
--- lcm-1.3.1+repack1/debian/liblcm1t64.install 1970-01-01 00:00:00.0 
+
+++ lcm-1.3.1+repack1/debian/liblcm1t64.install 2023-12-06 00:27:57.0 
+
@@ -0,0 +1 @@
+usr/lib/*/*.so.*
diff -Nru lcm-1.3.1+repack1/debian/liblcm1t64.lintian-overrides 
lcm-1.3.1+repack1/debian/liblcm1t64.lintian-overrides
--- lcm

Bug#1062516: lasi: NMU diff for 64-bit time_t transition

[Graham Inggs]

Source: lasi
Version: 1.1.3-2
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
lasi as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for lasi
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru lasi-1.1.3/debian/changelog lasi-1.1.3/debian/changelog
--- lasi-1.1.3/debian/changelog 2023-04-23 07:06:58.0 +
+++ lasi-1.1.3/debian/changelog 2024-02-01 18:17:35.0 +
@@ -1,3 +1,10 @@
+lasi (1.1.3-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs   Thu, 01 Feb 2024 18:17:35 +
+
 lasi (1.1.3-2) unstable; urgency=medium
 
   * QA Upload.
diff -Nru lasi-1.1.3/debian/control lasi-1.1.3/debian/control
--- lasi-1.1.3/debian/control   2023-04-23 06:45:05.0 +
+++ lasi-1.1.3/debian/control   2024-02-01 18:17:35.0 +
@@ -13,7 +13,10 @@
 Homepage: http://sourceforge.net/projects/lasi
 Rules-Requires-Root: no
 
-Package: liblasi0
+Package: liblasi0t64
+Provides: ${t64:Provides}
+Replaces: liblasi0
+Breaks: liblasi0 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends},
@@ -34,7 +37,7 @@
 Package: liblasi-dev
 Architecture: any
 Section: libdevel
-Depends: liblasi0 (= ${binary:Version}),
+Depends: liblasi0t64 (= ${binary:Version}),
  ${misc:Depends},
  libpango1.0-dev,
  libfreetype-dev
diff -Nru lasi-1.1.3/debian/liblasi0.install lasi-1.1.3/debian/liblasi0.install
--- lasi-1.1.3/debian/liblasi0.install  2023-04-23 04:50:23.0 +
+++ lasi-1.1.3/debian/liblasi0.install  1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/lib*.so.*
diff -Nru lasi-1.1.3/debian/liblasi0t64.install 
lasi-1.1.3/debian/liblasi0t64.install
--- lasi-1.1.3/debian/liblasi0t64.install   1970-01-01 00:00:00.0 
+
+++ lasi-1.1.3/debian/liblasi0t64.install   2023-04-23 04:50:23.0 
+
@@ -0,0 +1 @@
+usr/lib/lib*.so.*
diff -Nru lasi-1.1.3/debian/liblasi0t64.lintian-overrides 
lasi-1.1.3/debian/liblasi0t64.lintian-overrides
--- lasi-1.1.3/debian/liblasi0t64.lintian-overrides 1970-01-01 
00:00:00.0 +
+++ lasi-1.1.3/debian/liblasi0t64.lintian-overrides 2024-02-01 
18:17:35.0 +
@@ -0,0 +1 @@
+liblasi0t64: package-name-doesnt-match-sonames liblasi0

Bug#1062466: jaula: NMU diff for 64-bit time_t transition

[Graham Inggs]

Source: jaula
Version: 1.4.0-8
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
jaula as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for jaula
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru jaula-1.4.0/debian/changelog jaula-1.4.0/debian/changelog
--- jaula-1.4.0/debian/changelog2022-10-13 12:50:55.0 +
+++ jaula-1.4.0/debian/changelog2024-02-01 16:01:47.0 +
@@ -1,3 +1,10 @@
+jaula (1.4.0-8.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs   Thu, 01 Feb 2024 16:01:47 +
+
 jaula (1.4.0-8) unstable; urgency=medium
 
   * QA upload.
diff -Nru jaula-1.4.0/debian/control jaula-1.4.0/debian/control
--- jaula-1.4.0/debian/control  2022-10-13 12:50:55.0 +
+++ jaula-1.4.0/debian/control  2024-02-01 16:01:47.0 +
@@ -8,7 +8,10 @@
 Vcs-Git: https://salsa.debian.org/debian/jaula.git
 Rules-Requires-Root: no
 
-Package: libjaula1
+Package: libjaula1t64
+Provides: ${t64:Provides}
+Replaces: libjaula1
+Breaks: libjaula1 (<< ${source:Version})
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Suggests: libjaula-dev (= ${binary:Version})
@@ -22,7 +25,7 @@
 Package: libjaula-dev
 Section: libdevel
 Architecture: any
-Depends: libjaula1 (= ${binary:Version}), flex, ${misc:Depends}
+Depends: libjaula1t64 (= ${binary:Version}), flex, ${misc:Depends}
 Suggests: libjaula-doc
 Description: JSON parser/writer library for C++ (development files)
  This package contains headers and additional files for developing applications
diff -Nru jaula-1.4.0/debian/libjaula1.install 
jaula-1.4.0/debian/libjaula1.install
--- jaula-1.4.0/debian/libjaula1.install2022-10-13 12:50:55.0 
+
+++ jaula-1.4.0/debian/libjaula1.install1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/*.so.*
diff -Nru jaula-1.4.0/debian/libjaula1.shlibs 
jaula-1.4.0/debian/libjaula1.shlibs
--- jaula-1.4.0/debian/libjaula1.shlibs 2022-10-13 12:50:55.0 +
+++ jaula-1.4.0/debian/libjaula1.shlibs 1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-libjaula 1 libjaula1 (>= 1.3.0)
diff -Nru jaula-1.4.0/debian/libjaula1t64.install 
jaula-1.4.0/debian/libjaula1t64.install
--- jaula-1.4.0/debian/libjaula1t64.install 1970-01-01 00:00:00.0 
+
+++ jaula-1.4.0/debian/libjaula1t64.install 2022-10-13 12:50:55.0 
+
@@ -0,0 +1 @@
+usr/lib/*/*.so.*
diff -Nru jaula-1.4.0/debian/libjaula1t64.lintian-overrides 
jaula-1.4.0/debian/libjaula1t64.lintian-overrides
--- jaula-1.4.0/debian/libjaula1t64.lintian-overrides   1970-01-01 
00:00:00.0 +
+++ jaula-1.4.0/debian/libjaula1t64.lintian-overrides   2024-02-01 
16:01:47.0 +
@@ -0,0 +1 @@
+libjaula1t64: package-name-doesnt-match-sonames libjaula1
diff -Nru jaula-1.4.0/debian/libjaula1t64.shlibs 
jaula-1.4.0/debian/libjaula1t64.shlibs
--- jaula-1.4.0/debian/libjaula1t64.shlibs  1970-01-01 00:00:00.0 
+
+++ jaula-1.4.0/debian/libjaula1t64.shlibs  2024-02-01 16:01:47.0 
+
@@ -0,0 +1 @@
+libjaula 1 libjaula1t64 (>= 1.3.0)

Bug#1062341: highwayhash: NMU diff for 64-bit time_t transition

[Graham Inggs]

Source: highwayhash
Version: 0~git20200803.9490b14-4
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
highwayhash as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for highwayhash
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru highwayhash-0~git20200803.9490b14/debian/changelog 
highwayhash-0~git20200803.9490b14/debian/changelog
--- highwayhash-0~git20200803.9490b14/debian/changelog  2023-12-10 
21:46:41.0 +
+++ highwayhash-0~git20200803.9490b14/debian/changelog  2024-02-01 
05:55:07.0 +
@@ -1,3 +1,10 @@
+highwayhash (0~git20200803.9490b14-4.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs   Thu, 01 Feb 2024 05:55:07 +
+
 highwayhash (0~git20200803.9490b14-4) unstable; urgency=medium
 
   * Orphan this package. (See #1013208)
diff -Nru highwayhash-0~git20200803.9490b14/debian/control 
highwayhash-0~git20200803.9490b14/debian/control
--- highwayhash-0~git20200803.9490b14/debian/control2023-12-10 
21:46:17.0 +
+++ highwayhash-0~git20200803.9490b14/debian/control2024-02-01 
05:55:07.0 +
@@ -12,7 +12,7 @@
 Package: libhighwayhash-dev
 Section: libdevel
 Architecture: any
-Depends: ${misc:Depends}, libhighwayhash0 (= ${binary:Version})
+Depends: ${misc:Depends}, libhighwayhash0t64 (= ${binary:Version})
 Multi-Arch: same
 Description: Fast strong hash functions: SipHash/HighwayHash (development)
  Highwayhash provides three 'strong' (well-distributed and unpredictable)
@@ -33,7 +33,10 @@
  .
  This package ships the static library and development files.
 
-Package: libhighwayhash0
+Package: libhighwayhash0t64
+Provides: ${t64:Provides}
+Replaces: libhighwayhash0
+Breaks: libhighwayhash0 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
diff -Nru 
highwayhash-0~git20200803.9490b14/debian/libhighwayhash0t64.lintian-overrides 
highwayhash-0~git20200803.9490b14/debian/libhighwayhash0t64.lintian-overrides
--- 
highwayhash-0~git20200803.9490b14/debian/libhighwayhash0t64.lintian-overrides   
1970-01-01 00:00:00.0 +
+++ 
highwayhash-0~git20200803.9490b14/debian/libhighwayhash0t64.lintian-overrides   
2024-02-01 05:55:07.0 +
@@ -0,0 +1 @@
+libhighwayhash0t64: package-name-doesnt-match-sonames libhighwayhash0

Bug#1062338: hfsplus: NMU diff for 64-bit time_t transition

[Graham Inggs]

Source: hfsplus
Version: 1.0.4-17
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
hfsplus as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for hfsplus
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-15-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru hfsplus-1.0.4/debian/changelog hfsplus-1.0.4/debian/changelog
--- hfsplus-1.0.4/debian/changelog  2023-01-08 15:55:26.0 +
+++ hfsplus-1.0.4/debian/changelog  2024-02-01 05:47:50.0 +
@@ -1,3 +1,10 @@
+hfsplus (1.0.4-17.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs   Thu, 01 Feb 2024 05:47:50 +
+
 hfsplus (1.0.4-17) unstable; urgency=medium
 
   * QA upload.
diff -Nru hfsplus-1.0.4/debian/control hfsplus-1.0.4/debian/control
--- hfsplus-1.0.4/debian/control2023-01-08 15:44:44.0 +
+++ hfsplus-1.0.4/debian/control2024-02-01 05:47:50.0 +
@@ -7,7 +7,10 @@
 Vcs-Git: https://salsa.debian.org/debian/hfsplus.git
 Vcs-Browser: https://salsa.debian.org/debian/hfsplus
 
-Package: libhfsp0
+Package: libhfsp0t64
+Provides: ${t64:Provides}
+Replaces: libhfsp0
+Breaks: libhfsp0 (<< ${source:Version})
 Architecture: linux-any
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -33,7 +36,7 @@
 Package: libhfsp-dev
 Architecture: linux-any
 Section: libdevel
-Depends: libhfsp0 (= ${binary:Version}), libc6-dev, ${misc:Depends}
+Depends: libhfsp0t64 (= ${binary:Version}), libc6-dev, ${misc:Depends}
 Description: Library to access HFS+ formatted volumes
  HFS+ is a modernized version of Apple Computers HFS Filesystem.
  Nowadays, it is widely used with more recent versions of MacOS.
diff -Nru hfsplus-1.0.4/debian/libhfsp0.docs hfsplus-1.0.4/debian/libhfsp0.docs
--- hfsplus-1.0.4/debian/libhfsp0.docs  2021-12-28 01:51:52.0 +
+++ hfsplus-1.0.4/debian/libhfsp0.docs  1970-01-01 00:00:00.0 +
@@ -1,3 +0,0 @@
-doc/*.html
-NEWS
-README
diff -Nru hfsplus-1.0.4/debian/libhfsp0.install 
hfsplus-1.0.4/debian/libhfsp0.install
--- hfsplus-1.0.4/debian/libhfsp0.install   2021-12-28 01:51:52.0 
+
+++ hfsplus-1.0.4/debian/libhfsp0.install   1970-01-01 00:00:00.0 
+
@@ -1,2 +0,0 @@
-usr/lib/*-*/lib*.so.*
-
diff -Nru hfsplus-1.0.4/debian/libhfsp0.symbols 
hfsplus-1.0.4/debian/libhfsp0.symbols
--- hfsplus-1.0.4/debian/libhfsp0.symbols   2021-12-28 01:53:05.0 
+
+++ hfsplus-1.0.4/debian/libhfsp0.symbols   1970-01-01 00:00:00.0 
+
@@ -1,97 +0,0 @@
-libhfsp.so.0 libhfsp0 #MINVER#
- blockiter_curr@Base 1.0.4
- blockiter_init@Base 1.0.4
- blockiter_next@Base 1.0.4
- blockiter_skip@Base 1.0.4
- btree_check_nodealloc@Base 1.0.4
- btree_close@Base 1.0.4
- btree_init_cat@Base 1.0.4
- btree_init_extent@Base 1.0.4
- btree_insert_record@Base 1.0.4
- btree_key_by_index@Base 1.0.4
- btree_node_by_index@Base 1.0.4
- btree_readhead@Base 1.0.4
- btree_readnode@Base 1.0.4
- btree_remove_record@Base 1.0.4
- btree_reset@Base 1.0.4
- btree_writehead@Base 1.0.4
- btree_writenode@Base 1.0.4
- check_forkalloc@Base 1.0.4
- fast_unicode_compare@Base 1.0.4
- fscheck_btree@Base 1.0.4
- fscheck_create_extents_tree@Base

Bug#1061320: dblatex: FTBFS with Python 3.12

[Graham Inggs]

Control: tags -1 + patch

These two patches from Fedora[1] fix the FTBFS:

dblatex-0.3.12-replace-imp-by-importlib.patch
dblatex-0.3.12-adjust-submodule-imports.patch

I attach an additional patch that fixes several instances of
'SyntaxWarning: invalid escape sequence' that may be alarming to
users.


[1] https://src.fedoraproject.org/rpms/dblatex/tree/rawhide
Description: Fix several SyntaxWarnings
 Use raw strings to avoid invalid escape sequence
Author: Graham Inggs 
Last-Update: 2024-01-22

--- a/lib/dbtexmf/dblatex/grubber/texparser.py
+++ b/lib/dbtexmf/dblatex/grubber/texparser.py
@@ -31,7 +31,7 @@
 # Make a "foo|bar\*stub" list
 hooklist = [x.replace("*", "\\*") for x in self.hooks]
 
-pattern = "(?P%s)\*?"\
+pattern = r"(?P%s)\*?"\
   " *(\\[(?P[^\\]]*)\\])?"\
   " *({(?P[^{}]*)}|(?=[^A-Za-z]))"
 
--- a/lib/dbtexmf/dblatex/texcodec.py
+++ b/lib/dbtexmf/dblatex/texcodec.py
@@ -26,7 +26,7 @@
 l.append(unient.unicode_map[ord(c)])
 except KeyError:
 print("Missing character &#

Bug#1061320: dblatex: FTBFS with Python 3.12

[Graham Inggs]

Source: dblatex
Version: 0.3.12py3-2
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

dblatex FTBFS with Python 3.12.  I've copied what I hope is the
relevant part of the log below.

Regards
Graham


Traceback (most recent call last):
  File "/<>/setup.py", line 498, in 
version=get_version(),
^
  File "/<>/setup.py", line 475, in get_version
from dbtexmf.dblatex import dblatex
  File "/<>/lib/dbtexmf/dblatex/dblatex.py", line 8, in 
from dbtexmf.core.dbtex import DbTex, DbTexCommand
  File "/<>/lib/dbtexmf/core/dbtex.py", line 18, in 
import imp
ModuleNotFoundError: No module named 'imp'

Bug#1059664: python-fswrap: autopkgtest failure with Python 3.12

[Graham Inggs]

Source: python-fswrap
Version: 1.0.1-3
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

python-fswrap's autopkgtests fail with Python 3.12 [1].  I've copied
what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-fswrap/testing/amd64/


22s autopkgtest [20:11:10]: test autodep8-python3: [---
22s Testing with python3.12:
22s Traceback (most recent call last):
22s File "", line 1, in 
22s File "/usr/lib/python3/dist-packages/fswrap.py", line 14, in 
22s from distutils import dir_util
22s ModuleNotFoundError: No module named 'distutils'
22s autopkgtest [20:11:10]: test autodep8-python3: ---]

Bug#1024824: The software outputs: "No access to printer device file"

[Graham Inggs]

Control: severity -1 normal
Control: tags -1 + moreinfo

The severity of this bug keeps mtink out of testing, and needs more information.

Bug#1024301: redland-bindings: b-d on python3-all-dev, but not built for all supported Python3 versions

[Graham Inggs]

Source: redland-bindings
Version: 1.0.17.1+dfsg-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.11 python3-all-dev

Hi Maintainer

This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions.  This is seen
on the transition tracker for adding python3.11 support [1] and
creates false positives.

Please either replace the b-d python3-all-dev with python3-dev, or
build for all supported Python3 versions.  With the former solution
you get later exposure to a new python3 version, with the latter
solution you get early exposure.

Regards
Graham


[1] https://release.debian.org/transitions/html/python3.11-add.html

Bug#1002360: Package will now be considered for auto-removal

[Graham Inggs]

Hi Maintainer

The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].

This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.

Regards
Graham


[1] 
http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html
[2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi

Bug#997287: Package will now be considered for auto-removal

[Graham Inggs]

Hi Maintainer

The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].

This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.

Regards
Graham


[1] 
http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html
[2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi

Bug#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

[Graham Inggs]

Control: reopen -1

Hi Jonas

The build of link-grammar/5.8.0-3 has already failed on ppc64el [1]
(details below).

As fun as it is, please let's avoid the BTS sports and leave this bug
open until link-grammar builds and passes its autopkgtests reliably.

Regards
Graham


[1] 
https://buildd.debian.org/status/fetch.php?pkg=link-grammar=ppc64el=5.8.0-3=1609265548=0


FAIL: multi-thread
==

link-grammar: Info: Dictionary found at ../data/en/4.0.dict
link-grammar: Info: Dictionary found at ../data/ru/4.0.dict
link-grammar: Info: ru: Spell checker disabled.
double free or corruption (fasttop)
FAIL multi-thread (exit status: 134)

Bug#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails

[Graham Inggs]

Control: severity -1 serious

Hi Jonas

Happy Holidays!

On Sun, 27 Dec 2020 at 19:12, Jonas Smedegaard  wrote:
> I tightened the test checking - enabled them during build and made them
> more verbose (and explicitly passed environment variable "srcdata" which
> might have previously failed).
>
> Those changed was finalized and released today as 5.8.0-2, and I hope it
> can shed some light on what more detailed fails when it does.

Thanks for taking care of this package.

> To my surprise, the armhf failures are evidently no longer persistent
> even _before_ this latest release.  I therefore relax severity of this
> bug.

That was surprising.  :-)   On armhf [1], I see 142 failures for
version 5.8.0-1 and one pass on 2020-12-27 02:04:17 UTC. I also see
failures of 5.8.0-2 at least on amd64 [2], arm64 [3] and i386 [4].

As this is unsuitable for regression testing, I'm raising the severity
of this bug.

It's not clear to me whether it's just the test that is broken, in
which case skipping the multi-thread test is an option, or whether the
multi-threaded spell check feature is really broken in 5.8.0, in which
case reverting to 5.7.0 would be better.

Regards
Graham


[1] https://ci.debian.net/packages/l/link-grammar/testing/armhf/
[2] https://ci.debian.net/packages/l/link-grammar/unstable/amd64/
[3] https://ci.debian.net/packages/l/link-grammar/unstable/arm64/
[4] https://ci.debian.net/packages/l/link-grammar/testing/i386/

Bug#975696: link-grammar: multi-thread test fails

[Graham Inggs]

Source: link-grammar
Version: 5.8.0-1
Severity: serious
Tags: ftbfs
X-Debbugs-CC: pkg-sugar-de...@lists.alioth.debian.org, d...@jones.dk
Control: block 972670 by -1

Hi Abiword and Sugar Maintainers (since link-grammar is orphaned)

The upload of link-grammar 5.8.0-1 intermittently FTBFS on several
architectures, e.g. arm64 [1], armel [2] and ppc64 [3].  The failures
all happen during the multi-thread test with various errors:
double free or corruption (fasttop)
free(): invalid pointer
malloc_consolidate(): invalid chunk size
Segmentation fault
corrupted double-linked list

Giving back the builds eventually works, and link-grammar is currently
built on all release architectures.  However, this same test is run
during the autopkgtest and for some reason always fails on armhf [4].
This prevents the migration of link-grammar 5.8.0-1 to testing, and
will eventually cause the autoremoval of abiword and sugar from
testing.

Would you please have a look?

Regards
Graham


[1] 
https://buildd.debian.org/status/fetch.php?pkg=link-grammar=arm64=5.8.0-1%2Bb1=1606121733=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=link-grammar=armel=5.8.0-1%2Bb1=1605753701=0
[3] 
https://buildd.debian.org/status/fetch.php?pkg=link-grammar=ppc64=5.8.0-1%2Bb1=1606118399=0
[4] https://ci.debian.net/packages/l/link-grammar/testing/armhf/

Bug#909875: O: node-groove -- bindings to libgroove

[Graham Inggs]

Control: retitle -1 O: node-groove -- bindings to libgroove
Control: reassign -1 wnpp

Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]

[Graham Inggs]

On 13/01/2017 14:02, Andreas Beckmann wrote:

you could have done that QA upload yourself (even without filing a bug) :-)


Yeah, I know :( and I would have, seeing it is a QA package, but I 
thought it was too late for Stretch.

Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]

[Graham Inggs]

Thanks for the upload, Andreas!

If this bug had been tagged [1] like #811740 was, I might have seen it 
sooner.

I only saw it when I noticed nautic was not migrating in Ubuntu. :(


[1] 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-gcc-6;users=debian-...@lists.debian.org

Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]

[Graham Inggs]

Control: tags -1 patch

Hi

The attached patch fixes more narrowing conversions with GCC 6 on 
architectures where char is unsigned by default.


Regards
Graham

Description: Fix more narrowing conversions with GCC 6
 Needed for architectures where char is unsigned by default
Bug-Debian: https://bugs.debian.org/848917
Author: Graham Inggs <gin...@debian.org>
Last-Update: 2017-01-10
--- a/plant.h
+++ b/plant.h
@@ -30,7 +30,7 @@
   char maxargs;
   char max_harmonic[NARGS];
   char max_power_of_t;
-  char  *arg_tbl;
+  signed char  *arg_tbl;
   void  *lon_tbl;
   void  *lat_tbl;
   void  *rad_tbl;
@@ -1531,7 +1531,7 @@
  3,13,
 
 };
-static char  args[] = {
+static signed char  args[] = {
   0,  3,
   3,  4,  3, -8,  4,  3,  5,  1,
   2,  2,  5, -5,  6,  2,
@@ -4393,7 +4393,7 @@
 
 };
 
-static char  argsm[] = {
+static signed char  argsm[] = {
   0,  3,
   3,  4,  3, -8,  4,  3,  5,  1,
   2,  2,  5, -5,  6,  2,
@@ -5760,7 +5760,7 @@
  0,   119,
 
 };
-static char  argsl[] = {
+static signed char  argsl[] = {
   0,  1,
   3,  1, 10,  1, 12, -1, 11,  1,
   4,  2, 10,  2, 12, -1, 13, -1, 11,  0,
@@ -7455,7 +7455,7 @@
 
 };
 /* Mars*/
-static char  argsmr[] = {
+static signed char  argsmr[] = {
   0,  4,
   3,  4,  3, -8,  4,  3,  5,  2,
   3,  5,  2, -6,  3, -4,  4,  0,
@@ -8347,7 +8347,7 @@
 
 };
 
-static char  argsv[] = {
+static signed char  argsv[] = {
   0,  3,
   2,  2,  5, -5,  6,  0,
   3,  2,  2,  1,  3, -8,  4,  0,
@@ -9500,7 +9500,7 @@
 
 };
 
-static char  argsj[] = {
+static signed char  argsj[] = {
   0,  6,
   3,  2,  5, -6,  6,  3,  7,  0,
   2,  2,  5, -5,  6,  6,
@@ -6,7 +6,7 @@
 
 };
 
-static char argsst[] = {
+static signed char argsst[] = {
   0,  7,
   3,  2,  5, -6,  6,  3,  7,  0,
   2,  2,  5, -5,  6,  5,
--- a/src/starpos.cpp
+++ b/src/starpos.cpp
@@ -2155,7 +2155,7 @@
 	  char *p;
 	#else
 	#ifdef __STDC__
-	   char *p;
+	   signed char *p;
 	#else
 	  char *p;
 	#endif
@@ -2324,7 +2324,7 @@
   char *p;
 #else
 #ifdef __STDC__
-   char *p;
+   signed char *p;
 #else
   char *p;
 #endif
@@ -2476,7 +2476,7 @@
   char *p;
 #else
 #ifdef __STDC__
-   char *p;
+   signed char *p;
 #else
   char *p;
 #endif
@@ -2593,7 +2593,7 @@
   char *p;
 #else
 #ifdef __STDC__
-   char *p;
+   signed char *p;
 #else
   char *p;
 #endif

Bug#721928: [freesci] please transition from lesstif2 to motif

[Graham Inggs]

Source: freesci
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 0.6.4-7
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is
destined to be removed from the archive before the release of Jessie.
More information can be found in the Debian wiki [1].

Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before uploading.

Your package appears to have no dependent packages and to not depend on
any other lesstif2-dependent packages.

Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5228987e.3080...@nerve.org.za

Bug#717639: [cernlib] please transition from lesstif2 to motif

[Graham Inggs]

Source: cernlib
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 20061220+dfsg3-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is
destined to be removed from the archive before the release of Jessie.
More information can be found in the Debian wiki [1].

Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before uploading.

Your package appears to not depend on any other lesstif2-dependent
packages and its only dependent packages are geant321 and paw.

Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51ee4e97.2090...@nerve.org.za

Bug#717640: [paw] please transition from lesstif2 to motif

[Graham Inggs]

Source: paw
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1:2.14.04.dfsg.2-8
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is
destined to be removed from the archive before the release of Jessie.
More information can be found in the Debian wiki [1].

Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before uploading.

Your package depends on cernlib which also needs to be transitioned
as well as libxbae4 which has has already transitioned in experimental.
Packages geant321 and cernlib depend on paw.

Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51ee51aa.8070...@nerve.org.za

Bug#717643: [geant321] please transition from lesstif2 to motif

[Graham Inggs]

Source: geant321
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1:3.21.14.dfsg-10
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package indirectly depends or
build-depends is destined to be removed from the archive before the
release of Jessie.   More information can be found in the Debian wiki [1].

Your package depends on cernlib and paw which need to be transitioned
as well as libxbae4 which has already transitioned in experimental.

Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51ee5b3d.6070...@nerve.org.za

Bug#717644: [grace] please transition from lesstif2 to motif

[Graham Inggs]

Source: grace
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1:5.1.23-1
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is
destined to be removed from the archive before the release of Jessie.
More information can be found in the Debian wiki [1].

Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before uploading.

Your package depends on xmhtml1 which has already transitioned
as well as libxbae4 which has been transitioned in experimental.

Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51ee5c43.8050...@nerve.org.za

Bug#717647: [ia32-libs] please transition from lesstif2 to motif

[Graham Inggs]

Source: ia32-libs
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1:0.5
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is
destined to be removed from the archive before the release of Jessie.
More information can be found in the Debian wiki [1].

Please update your package to depend on the multiarch motif packages
instead, or simply remove lesstif2.

Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51ee6053.5040...@nerve.org.za

Bug#714833: [xmhtml] please transition from lesstif2 to motif

[Graham Inggs]

Source: xmhtml
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1.1.7-18
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to not depend on any other lesstif2-dependent 
packages and its only dependent package is grace.


We have checked for ABI changes using icheck which reported 
differences.  Please bump the library SONAME and package names as 
appropriate, or if in doubt.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d3e96c.5090...@nerve.org.za

Bug#714834: [dx] please transition from lesstif2 to motif

[Graham Inggs]

Source: dx
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1:4.4.4-4
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to not depend on any other lesstif2-dependent 
packages and its only dependent package is itself.


We have checked for ABI changes using icheck which reported no differences.

Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d3e9e4.9050...@nerve.org.za

Bug#714864: [inventor] please transition from lesstif2 to motif

[Graham Inggs]

Source: inventor
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 2.1.5-10-16
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages in the archive and to 
not depend on any other lesstif2-dependent packages.


ABI Compliance Checker [2] reports ABI changes in libInventorXt.so.0.0.0 
and no changes in libInventor.so.0.0.0, see attached.  Please bump the 
library SONAME and package names as appropriate.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition
[2] http://ispras.linuxbase.org/index.php/ABI_compliance_checker



libinventor_compat_report.html.gz
Description: GNU Zip compressed data


libinventorxt_compat_report.html.gz
Description: GNU Zip compressed data

Bug#714833: [xmhtml] please transition from lesstif2 to motif

[Graham Inggs]

ABI Compliance Checker [1] reports ABI changes in libXmHTML.so.1.1.7, 
see attached.
However, the only changes are globals _XmHTMLStrings and _XmHTMLMessages 
changing from char[] const to char, and XmSEE_DETAIL being added to enum 
XmHighlightMode.


[1] http://ispras.linuxbase.org/index.php/ABI_compliance_checker



libxmhtml_compat_report.html.gz
Description: GNU Zip compressed data

Bug#714737: [glw] please transition from lesstif2 to motif

[Graham Inggs]

Source: glw
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 8.0.0-1
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to not depend on any other lesstif2-dependent 
packages and its only dependent packages are arb, inventor and xmakemol.


We have checked for ABI changes using icheck which reported no 
differences.  We have also run xmakemol-gl compiled with lesstif2 
together with libglw compiled with motif, as well as xmakemol-gl 
compiled with motif together with libglw compiled with lesstif2 and did 
not encounter any problems.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d2b1e1.6080...@nerve.org.za

Bug#714740: [xmakemol] please transition from lesstif2 to motif

[Graham Inggs]

Source: xmakemol
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 5.16-6
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to only depend on 
glw which also needs to be transitioned.


We have checked for ABI changes in libglw using icheck which reported no 
differences.  We have also run xmakemol-gl compiled with lesstif2 
together with libglw compiled with motif, as well as xmakemol-gl 
compiled with motif together with libglw compiled with lesstif2 and did 
not encounter any problems.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d2bbee.60...@nerve.org.za

Bug#714742: [sciplot] please transition from lesstif2 to motif

[Graham Inggs]

Source: sciplot
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1.36-15
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages in the archive and to 
not depend on any other lesstif2-dependent packages.


We have checked for ABI changes in sciplot1 using icheck which reported 
no differences.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d2c2db.2020...@nerve.org.za

Bug#714755: [ferret-vis] please transition from lesstif2 to motif

[Graham Inggs]

Source: ferret-vis
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 6.6.2-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d2e00f.5070...@nerve.org.za

Bug#714756: [gromacs] please transition from lesstif2 to motif

[Graham Inggs]

Source: gromacs
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 4.5.5-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d2e1b6.90...@nerve.org.za

Bug#714758: [ctn] please transition from lesstif2 to motif

[Graham Inggs]

Source: ctn
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 3.0.6-13
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to not depend on any other lesstif2-dependent 
packages and its only dependent packages are ctsim and dicomnifti which 
do not need to be transitioned.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d2e2cb.2050...@nerve.org.za

Re: Bug#714737: [glw] please transition from lesstif2 to motif

[Graham Inggs]

On 2 July 2013 18:28, Julien Cristau jcris...@debian.org wrote:


 I think motif should provide a transitional lesstif2-dev package
 instead, if it's deemed safe to do so.

 I'm not sure this is going to be safe.  It looks like ABI breakages in
xbae and xmhtml, and very likely in inventor as well.
Transitioning glw on its own seems safe though; arb has been built with
libmotif and linking against libglw built with lesstif since late 2004.

Bug#714653: [alliance] please transition from lesstif2 to motif

[Graham Inggs]

Source: alliance
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 5.0-20120515-4
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1a49f.3020...@nerve.org.za

Bug#714655: [cmucl] please transition from lesstif2 to motif

[Graham Inggs]

Source: cmucl
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 20c-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1ab06.8010...@nerve.org.za

Bug#714657: [ddd] please transition from lesstif2 to motif

[Graham Inggs]

Source: ddd
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1:3.3.12-4
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1ae5b.1000...@nerve.org.za

Bug#714659: [geomview] please transition from lesstif2 to motif

[Graham Inggs]

Source: geomview
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1.9.4-3
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1aeff.2040...@nerve.org.za

Bug#714661: [gridengine] please transition from lesstif2 to motif

[Graham Inggs]

Source: gridengine
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 6.2u5-7.1
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1af5e.2050...@nerve.org.za

Bug#714665: [plan] please transition from lesstif2 to motif

[Graham Inggs]

Source: plan
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1.10.1-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b077.40...@nerve.org.za

Bug#714663: [mgdiff] please transition from lesstif2 to motif

[Graham Inggs]

Source: mgdiff
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1.0-29
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1afd6.8060...@nerve.org.za

Bug#714658: [elk] please transition from lesstif2 to motif

[Graham Inggs]

Source: elk
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 3.99.8-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1aea8.1070...@nerve.org.za

Bug#714669: [twclock] please transition from lesstif2 to motif

[Graham Inggs]

Source: twclock
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 3.1-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b18e.1080...@nerve.org.za

Bug#714668: [tcm] please transition from lesstif2 to motif

[Graham Inggs]

Source: tcm
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 2.20+TSQD-4.2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b143.4050...@nerve.org.za

Bug#714670: [twpsk] please transition from lesstif2 to motif

[Graham Inggs]

Source: twpsk
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 4.0-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b1dd.90...@nerve.org.za

Bug#714672: [xastir] please transition from lesstif2 to motif

[Graham Inggs]

Source: xastir
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 2.0.0-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b31a.3090...@nerve.org.za

Bug#714671: [viewmol] please transition from lesstif2 to motif

[Graham Inggs]

Source: viewmol
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 2.4.1-19
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b2d2.5070...@nerve.org.za

Bug#714675: [xmpi] please transition from lesstif2 to motif

[Graham Inggs]

Source: xmpi
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 2.2.3b8-13
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b3f0.4000...@nerve.org.za

Bug#714674: [xabacus] please transition from lesstif2 to motif

[Graham Inggs]

Source: xabacus
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 7.7.1-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b3ad.7030...@nerve.org.za

Bug#714673: [xball] please transition from lesstif2 to motif

[Graham Inggs]

Source: xball
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 3.0.1-1.1
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b35c.8070...@nerve.org.za

Bug#714677: [xtel] please transition from lesstif2 to motif

[Graham Inggs]

Source: xtel
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 3.3.0-16
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b494.30...@nerve.org.za

Bug#714676: [xpuzzles] please transition from lesstif2 to motif

[Graham Inggs]

Source: xpuzzles
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 7.6.3-1
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to have no dependent packages and to not depend on 
any other lesstif2-dependent packages.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b44d.60...@nerve.org.za

Bug#714678: [whitedune] please transition from lesstif2 to motif

[Graham Inggs]

Source: whitedune
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 0.30.10-1.1
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to not depend on any other lesstif2-dependent 
packages and its only dependent package is octave-vrml.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b5a1.1050...@nerve.org.za

Bug#714680: [hotswap] please transition from lesstif2 to motif

[Graham Inggs]

Source: hotswap
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 0.4.0-12
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to not depend on any other lesstif2-dependent 
packages and its only dependent package is itself.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b669.4030...@nerve.org.za

Bug#714681: [pcb] please transition from lesstif2 to motif

[Graham Inggs]

Source: pcb
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 20110918-8
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to not depend on any other lesstif2-dependent 
packages and its only dependent package is itself.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b6cb.9070...@nerve.org.za

Bug#714682: [xawtv] please transition from lesstif2 to motif

[Graham Inggs]

Source: xawtv
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 3.103-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to not depend on any other lesstif2-dependent 
packages and its only dependent packages are itself and webcamd.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b73b.50...@nerve.org.za

Bug#714679: [grass] please transition from lesstif2 to motif

[Graham Inggs]

Source: grass
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 6.4.2-2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

The lesstif2 package on which your package depends or build-depends is 
destined to be removed from the archive before the release of Jessie.  
More information can be found in the Debian wiki [1].


Please update your package to build against the motif package instead.  
In most cases this can be done by simply replacing the build-depends on 
lesstif2-dev with libmotif-dev, however please do verify proper 
behaviour before uploading.


Your package appears to not depend on any other lesstif2-dependent 
packages and its only dependent package is itself.


Regards
Paul and Graham

[1] http://wiki.debian.org/lesstif2motifTransition


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51d1b60f.8090...@nerve.org.za

Bug#713061: [arb] please rebuild and possibly move to main

[Graham Inggs]

Source: arb
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 5.5-1
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer

Your package build-depends on libmotif-dev.  Motif 2.3.4 was recently
released under LGPL and the openmotif package in non-free has been replaced
by the motif package in main.
The libmotif4 binary package has now been split into libxm4, libmrm4 and
libuil4 and your package should be rebuilt in order for shlibs to generate
the correct dependencies.

If your package's dependency on (open)motif is the only reason it is in
non-free, it should now be able to move into main.

Regards
Paul  Graham

Re: Motif FTBFS on non-linux due to YYSTYPE

[Graham Inggs]

Hi Paul

Thanks for uploading!

On 25 May 2013 17:47, Paul Gevers elb...@debian.org wrote:

 If we fixed the FTBFS, do you want to start filling wishlist bugs
 against the reverse dependencies of lesstif2-dev? (I am working on nedit
 already). Or do you want me to start them? If you do, please don't
 forget to tag them with the lesstif2motif usertag.


I will file the bugs against the reverse dependencies of lesstif2-dev in
Debian.
I will also file one in Ubuntu to remove openmotif and replace with motif.

Regards
Graham

Re: Motif

[Graham Inggs]

As per the motif 2.3.4 release notes [1], motif 2.3.4 is binary compatible
all the way back to motif 2.2.
I believe this means bug #587683 [2] should have been solved by symlinks
rather than bumping the name libmotif3 to libmotif4.
I cannot say why upstream bumped the soname when it was not necessary.
Anyway, motif 2.3.4 now provides these symlinks for compatibility with
applications that are not in Debian and libmotif3 has been out of the
archive for so long now that we do not need to worry about libmotif3 -
libmotif4 transitional packages.

We have removed Xprint from motif 2.3.4, so strictly speaking the ABI is
not 100% compatible with openmotif 2.3.3, but none of the packages in
Debian that depend on libmotif4 or lesstif2 make use of any of the Xprint
functions, so I see no reason not to proceed with the upload.

[1] http://motif.ics.com/motif-234-release-notes
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587683


On 23 May 2013 08:43, Luca Falavigna dktrkr...@debian.org wrote:

 2013/5/22 Paul Gevers elb...@debian.org:
  Ok. Then we just have to wait until the RT grants us a transition slot.
  Will keep you updated.

 I don't think we need it for openmotif - motif, as long as motif is
 ABI-compatible with openmotf.

Re: lesstif2 to motif transition

[Graham Inggs]

Another status update:

ferret-vis#707211 fix released in ferret-vis 6.6.2-2
gridengine#707937
hotswap#707621
mesa-glwUbuntu-only package, to be replaced by glw (LP: #1179164)
mgdiff   #707943
sqshLP: #1134233 fix released in sqsh 2.1.7-2
tcm#707923
xabacus#707926 fix released in xabacus 7.7.1-2
xawtv#707944 fix released in xawtc 3.102-1
xpdf#707927
xsol#707929
xtel#707623 fix released in xtel 3.3.0-15


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5194dd48.1090...@nerve.org.za

Re: lesstif2 to motif transition

[Graham Inggs]

Hi All

Below is a status update on the bugs filed against packages that 
required additional build dependencies:


ferret-vis#707211
gridengine#707937
hotswap#707621
mesa-glwUbuntu-only package, to be replaced by glw (LP: #1179164)
mgdiff   #707943
sqshLP: #1134233 fix released in sqsh 2.1.7-2
tcm#707923
xabacus#707926 fix released in xabacus 7.7.1-2
xawtv#707944
xpdf#707927
xsol#707929
xtel#707623

Below is a list of packages that only required changing lesstif2-dev to 
libmotif-dev.
New additions to the list are cernlib, paw, pcb and glw which have 
successfully built in my PPA [1].


alliance
cernlib
ctn
ddd
dx
elk
freesci
geomview
glw
grace
grass
gromacs
inventor
mtink
ncbi-tools6
nedit
njplot
paw
pcb
plan
sciplot
twclock
twpsk
via
viewmol
whitedune
xastir
xbae
xball
xmakemol
xmhtml
xmpi
xpuzzles
xshisen

[1] https://launchpad.net/~ginggs/+archive/motif

Regards
Graham


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5190af97.5060...@nerve.org.za

Re: lesstif2 to motif transition

[Graham Inggs]

Another status update:

ferret-vis#707211 fix released in ferret-vis 6.6.2-2
gridengine#707937
hotswap#707621
mesa-glwUbuntu-only package, to be replaced by glw (LP: #1179164)
mgdiff   #707943
sqshLP: #1134233 fix released in sqsh 2.1.7-2
tcm#707923
xabacus#707926 fix released in xabacus 7.7.1-2
xawtv#707944
xpdf#707927
xsol#707929
xtel#707623 maintainer responded


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5190b4ea.1000...@nerve.org.za

Bug#707923: [tcm] please build-depend on libxt-dev

[Graham Inggs]

Source: tcm
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 2.20+TSQD-4.2
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer,

Your package build depends on libxt-dev but does not declare this
relation in the debian/control file. This is currently not a problem as
this is pulled in by the lesstif2-dev package that you do depend on.

In the near future we like to replace lesstif2 in Debian with the
relicensed (open-)motif package. Lesstif2 was originally created as an
free alternative for motif, but in the meantime became unmaintained and
buggy. Motif itself is now free and got its latest maintenance release
last year.

To ease the transition that will happen sometime soon, we will follow
up on this, please explicitly build-depend on libxt-dev, as we don't
intend to include the depends on libxt-dev in libmotif-dev.

Kind regards,
Paul  Graham.

Bug#707926: [xabacus] please build-depend on libxt-dev

[Graham Inggs]

Source: xabacus
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 7.7.1-1
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer,

Your package build depends on libxt-dev but does not declare this
relation in the debian/control file. This is currently not a problem as
this is pulled in by the lesstif2-dev package that you do depend on.

In the near future we'd like to replace lesstif2 in Debian with the
relicensed (open-)motif package. Lesstif2 was originally created as a
free alternative for motif, but in the meantime became unmaintained and
buggy. Motif itself is now free and got its latest maintenance release
last year.

To ease the transition that will happen sometime soon, we will follow
up on this, please explicitly build-depend on libxt-dev, as we don't
intend to include the depends on libxt-dev in libmotif-dev.

Kind regards,
Paul  Graham.

Bug#707927: [xpdf] please build-depend on libxt-dev

[Graham Inggs]

Source: xpdf
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 3.03-10
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer,

Your package build depends on libxt-dev but does not declare this
relation in the debian/control file. This is currently not a problem as
this is pulled in by the lesstif2-dev package that you do depend on.

In the near future we'd like to replace lesstif2 in Debian with the
relicensed (open-)motif package. Lesstif2 was originally created as a
free alternative for motif, but in the meantime became unmaintained and
buggy. Motif itself is now free and got its latest maintenance release
last year.

To ease the transition that will happen sometime soon, we will follow
up on this, please explicitly build-depend on libxt-dev, as we don't
intend to include the depends on libxt-dev in libmotif-dev.

Kind regards,
Paul  Graham.

Bug#707929: [xsol] please build-depend on libxt-dev

[Graham Inggs]

Source: xsol
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 0.31-9
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer,

Your package build depends on libxt-dev but does not declare this
relation in the debian/control file. This is currently not a problem as
this is pulled in by the lesstif2-dev package that you do depend on.

In the near future we'd like to replace lesstif2 in Debian with the
relicensed (open-)motif package. Lesstif2 was originally created as a
free alternative for motif, but in the meantime became unmaintained and
buggy. Motif itself is now free and got its latest maintenance release
last year.

To ease the transition that will happen sometime soon, we will follow
up on this, please explicitly build-depend on libxt-dev, as we don't
intend to include the depends on libxt-dev in libmotif-dev.

Kind regards,
Paul  Graham.

Bug#707937: [gridengine] please build-depend on libxft-dev, libxp-dev

[Graham Inggs]

Source: gridengine
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 6.2u5-7.1
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer,

Your package build depends on libxft-dev and libxp-dev but
does not declare this relation in the debian/control file. This is
currently not a problem as this is pulled in by the lesstif2-dev package
that you do depend on.

In the near future we'd like to replace lesstif2 in Debian with the
relicensed (open-)motif package. Lesstif2 was originally created as a
free alternative for motif, but in the meantime became unmaintained and
buggy. Motif itself is now free and got its latest maintenance release
last year.

To ease the transition that will happen sometime soon, we will follow
up on this, please explicitly build-depend on libxft-dev and libxp-dev,
as we don't intend to include these depends in libmotif-dev.

Kind regards,
Paul  Graham.

Bug#707943: [mgdiff] please build-depend on libxt-dev, libxext-dev

[Graham Inggs]

Source: mgdiff
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1.0-29
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer,

Your package build depends on libxt-dev and libxext-dev but
does not declare this relation in the debian/control file. This is
currently not a problem as this is pulled in by the lesstif2-dev package
that you do depend on.

In the near future we'd like to replace lesstif2 in Debian with the
relicensed (open-)motif package. Lesstif2 was originally created as a
free alternative for motif, but in the meantime became unmaintained and
buggy. Motif itself is now free and got its latest maintenance release
last year.

To ease the transition that will happen sometime soon, we will follow
up on this, please explicitly build-depend on libxt-dev and libxext-dev,
as we don't intend to include these depends in libmotif-dev.

Kind regards,
Paul  Graham.

Bug#707944: [xawtv] please build-depend on libxp-dev

[Graham Inggs]

Source: xawtv
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 3.102-3
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org

Hi Maintainer,

Your package build depends on libxp-dev but does not declare this
relation in the debian/control file. This is currently not a problem as
this is pulled in by the lesstif2-dev package that you do depend on.

In the near future we'd like to replace lesstif2 in Debian with the
relicensed (open-)motif package. Lesstif2 was originally created as a
free alternative for motif, but in the meantime became unmaintained and
buggy. Motif itself is now free and got its latest maintenance release
last year.

To ease the transition that will happen sometime soon, we will follow
up on this, please explicitly build-depend on libxp-dev, as we don't
intend to include these depends in libmotif-dev.

Kind regards,
Paul  Graham.

P.S. Debian is trying to get rid of libxp, but as long as your package
needs it, please declare explicitly.

Re: lesstif2 to motif transition

[Graham Inggs]

Hi Paul

I think the testing went very well.  As we suspected, most packages only
required changing the build-depends on lesstif2-dev to libmotif-dev.  There
were a few that required the addition of libxt-dev and one or two that
required libxext-dev and libxp-dev (although we should try to remove that
dependency).

Cernlib depends on libpacklib-lesstif1-dev and libpawlib-lesstif3-dev from
paw and pcb depends on its own pcb-lesstif, these packages should probably
be renamed.

Do -dev packages normally get transitional packages?  I can't think of a
situation where that would be useful.
Ideally we need all of the packages that depend on lesstif2 to be rebuilt
against libmotif.  When a user upgrades they will then get libmotif which
conflicts with lesstif2 and it will be removed.
If a user was developing with lesstif2-dev it would be removed due to the
conflict above, but they would not have been able to continue building
against libmotif-dev without making changes anyway.

Regards
Graham




On 7 May 2013 07:14, Paul Gevers elb...@debian.org wrote:

 Hi Graham,

 On 06-05-13 23:01, Paul Gevers wrote:
  My proposal would be (with your approval) to just get motif into
  unstable/main and start converting the dependencies with the help of
  their maintainers (the libraries can coexist). Because the -dev package
  name has to change all build dependencies would have to get a
  source-full update. I would have liked to stage everything in
  experimental, but due to this (quoted from ftp-master) nasty dak bug,
  that would leave unstable (non-free) without (open-)motif.

 I was thinking, how well did it go with your building of all reverse
 dependencies, and how well would it work if lesstif2-dev would be a
 transitional package that depends on libmotif-dev? If that would work at
 all, I think that is a good alternative to my proposal above.

 Paul

Re: lesstif2 to motif transition

[Graham Inggs]

On 7 May 2013 08:19, Paul Gevers elb...@debian.org wrote:

 Can you please document that, I mean which ones? It would be great if
 you would reply to the e-mail I sent yesterday to the release team with
 full details, so that the team knows when they make a decision.


When I get home tonight I will compose an email to release team from my
testing notes.


 And I
 think (unsure now) that these missing dependencies are actual bugs in
 those packages, so they should get filed and fixed anyway.


Yes, I believe these are bugs in those packages that were hidden because
lesstif2-dev depends on just about every libX*-dev package.


 Did you actually try to
 RUN any of the compiled packages?


Yes, although not being familiar with the packages, many of them I just ran
and saw that a GUI appeared without any error messages.

 If a user was developing with lesstif2-dev it would be removed due to
  the conflict above, but they would not have been able to continue
  building against libmotif-dev without making changes anyway.

 Why not? Aren't the headers the same? If not, how can WE replace
 lesstif2 with libmotif?


They would at least need to change the build-depends in debian/control, so
it's still a manual change that needs to be made.


 Anyway, the users that build are not the only
 ones we need to care about.


Surely only users that build lesstif packages would have lesstif2-dev
installed?

I'm not totally against a lesstif2-dev transitional package, I just want to
be clear on why it is necessary.

Re: proposal for the reverse depending buggy packages [Was: Re: lesstif2 to motif transition]

[Graham Inggs]

I agree with the message.  I can suggest some minor grammatical changes
though.

On 7 May 2013 21:56, Paul Gevers elb...@debian.org wrote:


 This is currently no problem as
 this is pulled in by the lesstif2-dev package that you do depend on.


I would say This is current not a problem as


 Lesstif2 was originally created as an
 free alternative for motif, but in the mean time became unmaintained and


meantime - one word


 To ease the transition that will happen some time soon, we will follow


sometime - one word

...and then some of my own typos:

 hotswap - libxtdev, libxext-dev, libxp-dev


hotswap - libxt-dev, libxext-dev, libxp-dev


  xtel - libxpd-dev


xtel - libxp-dev

Re: First motif commits

[Graham Inggs]

On 25 March 2013 09:30, Paul Gevers elb...@debian.org wrote:

 Are you sure? I believe the NEW queue is ONLY accessible to the
 ftp-masters, as uploads might contain non-distributable material, and
 the task of the ftp-masters is exactly to prevent that entering Debian.


I'm not sure exactly how it was done, but see the changelog entry for new
package in raring, python-cffi [1].
That package is also waiting in Debian NEW, about one week behind motif.


 So if that is possible, you are talking to an ftp-master, right? Then we
 could just make an Ubuntu version of the package instead.


Yes, that is also an option, although 2.3.4-1 does not build in raring, but
I we could try pushing 2.3.4-2 straight to Ubuntu.

Furthermore, the feature freeze has already past for a long time, so
 usually Ubuntu does not allow such large changes. Who are you
 communicating with about this effort, please include me in the
 communication.


I chatted to Stefano Rivera about this some time ago.  I'll mail him and CC
you.
According to Motif 2.3.4's release notes [2], this is a bug fix release, so
as far as upstream is concerned there aren't any new features.
I did enable PNG, JPG and Xft support, but these features have been in
upstream for a while and have been tested, just not in Debian/Ubuntu.


[1]
http://changelogs.ubuntu.com/changelogs/pool/universe/p/python-cffi/python-cffi_0.5-0ubuntu1/changelog
[2] http://motif.ics.com/motif-234-release-notes

Re: First motif commits

[Graham Inggs]

Hi Paul

You wrote that you wouldn't upload 2.3.4-2 until 2.3.4-1 had been reviewed.
Is it possible to re-upload our current effort as 2.3.4-1 (with the
appropriate changes to the changelog and libxm4.symbols)?
It may then be possible to get Ubuntu to sync motif from Debian's NEW queue
and still make it into Raring (final beta freeze is March 28 [1]).

Is there anything that needs to be done in wnpp bug #695130 [2]?

Regards
Graham


[1] https://wiki.ubuntu.com/RaringRingtail/ReleaseSchedule
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695130

Re: [SCM] Motif widgetset library branch, master, updated. debian/2.3.4-1-31-g912bcbf

[Graham Inggs]

Hi Paul

On 17 March 2013 10:58, Paul Gevers elb...@debian.org wrote:

 If this is true, we do have an (small) issue. You can not just relicense
 this file without permission of the copyright owner. So, you have no
 choice other than state the license of this file as GPL-3 or ask
 Canonical to relicense.


I understood that this was OK since the new license was 2+.
Or is the problem more about changing from GPL to LGPL?


 By the way, you really should add Canonical to the copyright holders
 list as well.


Which list is that

Re: [SCM] Motif widgetset library branch, master, updated. debian/2.3.4-1-31-g912bcbf

[Graham Inggs]

On 17 March 2013 12:10, Paul Gevers elb...@debian.org wrote:

 The one in d/copyright. Please see below. (Don't forget to add the GPL3
 required text to the file.) (And are you sure it is not GPL3 or later?)


Yes, from d/copyright in unity-greeter:

Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Source: https://launchpad.net/unity-greeter

Files: *
Copyright: 2011-2012 Canonical Ltd
License: GPL-3

License: GPL-3
...

OK, I understand, will fix and commit now.

Re: First motif commits

[Graham Inggs]

On 13 March 2013 22:14, Paul Gevers elb...@debian.org wrote:

 On 03/12/13 22:19, Graham Inggs wrote:
  Shouldn't the xprint related symbols have been commented out so we don't
  get the #MISSING warnings?

 That is fine. I thought I had done that.


After asking that question I tried to do more reading up symbols, but I
found the information very vague, especially about (optional) symbols.
Out of interest, why are there so many other (optional) symbols?  How did
you determine they were optional?


On 13 March 2013 22:37, Paul Gevers elb...@debian.org wrote:

 On 03/13/13 09:46, Graham Inggs wrote:
  I've cleaned up some things, added copyright info for
  custom_mwm_badge.png and updated the changelog.

 Good. Are you sure you own the complete copyright of that file? I.e.
 didn't somebody else have the original copyright?


I guess Canonical might have the copyright on the white circle image, I'll
check in the sources of unity-greeter.  I'm not sure about the four
squares, I based that on the look of the icon for Xterm that is displayed
in MWM [1].


 I saw you dropped them in the mean time. Fine. However, from your story
 I understand that motif needs to link to libxft. If you want to be sure
 it is linked, please DON'T assume it is pulled in via your depends, but
 explicitely depend on it. In general, a depends of your package may
 cease to depend on the library (maybe it is optional, or a replacement
 is found) and you get strange FTBFS or worse in a case like this, your
 package builds different than you intend.


We still build-depends on libxft-dev and I am confident that we do not need
libfreetype6-dev and libxrender-dev, as Motif does not get linked to these
libraries, and although the freetype.h and Xrender.h headers are currently
checked by ac_find_xft.m4, their presence does not affect the build.
I do see your point for libfontconfig1-dev though, Motif does call some fc*
functions in lib/Xm/XmRenderT.c and we do need to link to -lfontconfig.

Sounds ok, but I thought originally you created your patch to save on
 build time. Do you now think it is worth it to distribute the demos? Oh,
 wait, you only mean the source code here. Than I think I like the
 examples better as name then demos, but I let it up to you.


Agreed, examples is more descriptive.  I'm not going to make this a
priority, and I don't mind if we end up releasing 2.3.4-2 without them.
As you mentioned previously, the examples are in the source package if
anyone wants them.

Shall I email upstream now and see if they are interested in support from
the community?

[1] http://xwinman.org/screenshots/mwm-matt.gif

Re: First motif commits

[Graham Inggs]

I've cleaned up some things, added copyright info for custom_mwm_badge.png
and updated the changelog.

As noted in 14-fix_ac_find_xft.patch, we can probably eventually drop the
build-depends on libfreetype6-dev and libxrender-dev as they only seem to
be used in the tests in ac_find_xft.m4. Although without Xrender.h, I think
LIBS won't get -lXft added and will leave libXm underlinked.
Maybe ac_find_xft.m4 should be totally reworked, and we should probably
consult upstream before doing that.
Is there any harm in leaving the build-depends on libfreetype6-dev and
libxrender-dev in place for now?

We could create a motif-demos package and copy the demos directory to
/usr/share/doc/motif-demos, similar to what is done in gtk2.0-examples and
gtk-3-examples.
What do you think?

Re: First motif commits

[Graham Inggs]

Paul, if you think my recent changes to:
05-multiarch-specialcase-libdir-X11.patch
13-fix_hardcoded_x11rgb_path.patch
and
14-fix_ac_find_xft.patch
are sane, then I'll send those patches upstream.

Re: First motif commits

[Graham Inggs]

I've been looking at the motif packaging for Fedora 19 [1].  I see they
also renamed their openmotif package to motif.
The only changes we don't have now are in the man pages relating to
relocated files.
There are still many references to X11R6.

Regarding my patch 14:
Including ft2build.h seems to be an intentional change in freetype from
some time ago (2004?).
On my system, $x_includes and $x_libraries are both empty, so the '-I' and
'-L' without paths breaks the test.
I don't know where $x_includes and $x_libraries are supposed to come from.
Not setting FONTCONFIG_LIBS=-lfontconfig looks like a bug to me.
I don't know how the package builds in Red Hat / Fedora without
modification, but running 'ldd uil' against the version included in
motif-devel-2.3.4-5.fc19.x86_64.rpm shows it is linked to libXft,
libXrender, libfontconfig and libfreetype.

I still want to work on patch 13 so that the path to rgb.txt can be
specified as a configure option.
The same for MWMRCDIR in patch 5.

I haven't forgotten about the SDK samples.

[1]
http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/source/SRPMS/m/

Re: [SCM] Motif widgetset library branch, master, updated. debian/2.3.4-1-12-g64986ea

[Graham Inggs]

On 8 March 2013 21:09, Paul Gevers elb...@debian.org wrote:

 I prefer to do this by adding that file to a file called debian/clean.
 That way you don't have to override dh_clean.


Thanks, I'll look into that.

Re: [SCM] Motif widgetset library branch, master, updated. debian/2.3.4-1-10-g5f4f0e2

[Graham Inggs]

On 8 March 2013 21:38, Paul Gevers elb...@debian.org wrote:


 Can you please elaborate why you find this nicer? You didn't need the
 clean up before, and now you do. So, why?


Previously, we had to create a directory and then copy to debian/tmp/etc...
which I always thought was a bit of a hack.
I believe this way is clearer; we make a copy of the file with a different
name, and all of the installations take place from mwm.install.

Re: [SCM] Motif widgetset library branch, master, updated. debian/2.3.4-1-10-g5f4f0e2

[Graham Inggs]

On 8 March 2013 21:50, Paul Gevers elb...@debian.org wrote:

 Where did you get this file? What is the copyright? Is this file created
 as png or is it actually created in a program and does that program
 store the file in a different format so that you can edit it? In the
 later case, we also need that source and preferable build the png from
 that source.


I created the file by hand in GIMP, starting with
/usr/share/unity-greeter/unknown_badge.png, as per:
https://lists.ubuntu.com/archives/ubuntu-devel/2012-February/034800.html

Re: First motif commits

[Graham Inggs]

I committed some changes and updated the changelog.
I am not done yet though, I still want to have a good look at the Red 
Hat package and see if there is anything that will be useful.

I can already see that we can probably get rid of the system.mwmrc symlink.
I also want to investigate building with fontconfig and xrender support, 
but I suspect that ac_find_xft.m4 needs some attention before this will 
work.


On 25/02/2013 18:33, Paul Gevers wrote:
I am not surprised. As I believe this is a company effort, I think 
somebody got time to work on release a 2.3.4 version with the new 
licensing. After that of course he got a new assignment. That is 
exactly why I think it might be interesting to have community support 
as well. 


Shall we wait until we release 2.3.4-2?  I was in contact with someone 
from ICS last year who seemed very helpful, I'll email him when we've 
got something to show.


Indeed. I think the examples in the source package are good for now as 
any user can install a source package (not just root). Maybe 
mentioning something along those lines in a README file somewhere in 
one of our packages does not hurt though. I.e. that example code is 
available.


I'm still wondering if there is a better way.  I'd like to do something 
similar for nvidia-cuda-toolkit.  I'll keep looking.



--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/512dc537.3010...@nerve.org.za

Re: First motif commits

[Graham Inggs]

On 24/02/2013 21:51, Paul Gevers wrote:

1. FTBFS on Ubuntu Raring:

I think the following page holds the answer:
http://wiki.debian.org/ToolChain/DSOLinking

I already had a look at that page when I was creating the symbols.
Indeed a lot of good info there.


I think the change in Raring happened fairly recently.  I've found a 
package already in Raring, njplot [1], that fails to build from source 
now with similar linking problems.  I've let Stefano know about this, he 
being an Ubuntu Developer as well, there might be other packages 
affected and I don't know how serious this is.


It seems other distributions, e.g. Fedora are also switching to DSO 
linking [2].
It's probably worth combining my patch along with Ubuntu's 
0003_fix_ftbfs_binutils-gold.patch [3] and pushing it upstream.


Do you know what this additional support means? In principle I don't 
object, but I like to understand.


I know it allows JPG and PNG files to be used as resources.  If the test 
case I attached to comment #4 of LP: #1026640 [4] is modified (line 72) 
to open a JPG image instead of the supplied XPM, then the resultant 
executable will display a small empty square when run against libXm 
without JPG support, but will display the image correctly if run against 
libXM with JPG support, without needing to be recompiled.  Further than 
that, I do not know.


How did you see with what code they released 2.3.4? I could not 
(easily) deduce this from upstream GIT repository.


I just went by the dates of the commits and the contents of their changelog.

Additionally, I was wondering if you/we find it worth while to ask the 
current maintainer of upstream what he things of co-maintainers? I 
expect there are still quite some upstream bugs which are worth 
fixing, although they are not reported against Debian.


No harm in asking.  I am a bit concerned that there hasn't been any 
upstream activity for a couple of months now.


What do you think of providing a motif-sdk-examples package?
I was thinking we could provide a compressed archive of the source code 
in /usr/share/doc/ or somewhere that users could extract to their home 
directories and then build the examples there.  I did have a brief look 
for similar packages in Debian, but didn't find any.  Maybe this is just 
redundant, as the examples are already available in the source package.



[1]: https://launchpad.net/ubuntu/raring/+source/njplot/2.4-1
[2]: https://fedoraproject.org/wiki/UnderstandingDSOLinkChange
[3]: 
http://changelogs.ubuntu.com/changelogs/pool/multiverse/o/openmotif/openmotif_2.3.3-5ubuntu1/changelog

[4]: https://bugs.launchpad.net/ubuntu/+source/openmotif/+bug/1026640


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/512b230f.8050...@nerve.org.za

Re: First motif commits

[Graham Inggs]

Recent changes (19 February)

Hi, I just wanted to clear up a few things regarding the recent changes I
committed.

1. FTBFS on Ubuntu Raring:
I had recently upgraded a test machine to Raring for another project and
decided to try building motif on it.  I encountered numerous error similar
to the following:
/usr/bin/ld: wmldbcreate.o: undefined reference to symbol 'XtStrings'
/usr/bin/ld: note: 'XtStrings' is defined in DSO
/usr/lib/x86_64-linux-gnu/libXt.so.6 so try adding it to the linker command
line
/usr/lib/x86_64-linux-gnu/libXt.so.6: could not read symbols: Invalid
operation
I was able to fix these by explicitly linking -lXt, -lXext and lX11 where
necessary.
'Fix FTBS on Ubunutu Raring' is a terrible description for the patch as it
describes the symptom rather than the underlying cause.
I'd like to rename (sorry) the patch and come up with a better description
once I fully understand what changed in Raring.
I think the following page holds the answer:
http://wiki.debian.org/ToolChain/DSOLinking

2. Build Motif with JPG and PNG support:
After being able to build motif on Raring, I noticed there were additional
symbols.  I found that my test machine had libjpeg8-dev and libpng12-dev
installed and this caused motif to build with additional support for these
image types.  I believe we should build motif with JPG and PNG support, and
found that motif is built this way in Red Hat [2].
I have not made any changes yet to the symbols files.

3. Fix buffer overrun in lib/Xm/FontS.c:
I was looking at the upstream git [1] and found the only change since the
2.3.4 release was this buffer overrun fix committed on 31 October 2012.  I
figured we should include it.

If you agree on the above changes, I will write up a changelog describing
them.

[1]: git://git.code.sf.net/p/motif/code
[2]:
http://vault.centos.org/6.3/updates/Source/SPackages/openmotif-2.3.3-5.el6_3.src.rpm

Re: First motif commits

[Graham Inggs]

The last few commits were the result of some testing against builds in my
PPA:
installing libmotif-dev and libmotif-dev:i386
installing libmotif4-dbg and libmotif4-dbg:i386
upgrading from 2.3.3 with all motif packages installed, including libmotif4
and libmotif4:i386