Bug#1053963: RFS: termpaint/0.3.0-3 [RC] -- low level terminal access - headers

2023-10-17 Thread Martin Hostettler 
On Sun, Oct 15, 2023 at 06:51:51AM -0400, Thomas Dickey wrote:
> 
> Likewise, it uses xterm's documentation (and source code) extensively
> (such as in termquery.cpp) without mentioning the source of the information.

Yes, termquery.cpp is a testing helper shipped in the source that has the
need to name modes.

I mean where else would one get names for those than the only contemporary
documentation of those things. Which is the xterm documentation.

Yes, i should not have assumed that it's totally obvious to anyone in the
space that those things are either from some floating around DEC manuals or
from ctlseqs.

I'm happy to fix that with a link back to your site, as it really is one of
the best sources.

But that files is not even linked into the library so it's a bit of a
tanget wrt termpaint itself.

For the rest, i don't think there is a lot that is similar to xterm except
as technically needed (e.g. the details of the 256 color color map)

But in the end this whole project is based on careful study¹ (and
redocumentation) of a lot of terminal implementations including xterm,
so some things might have stuck in my mind. I'm happy to look into any
other places where you feel that attribution is missing.

But this is all quite of topic here, so let's take that to private mail or
to the upstream issue tracker.

Regards, 
 - Martin


¹ which even lead me to report some improvments to xterm some years ago.

Bug#1053963: RFS: termpaint/0.3.0-3 [RC] -- low level terminal access - headers

2023-10-17 Thread Martin Hostettler 
On Sun, Oct 15, 2023 at 04:51:47AM -0400, Thomas Dickey wrote:
> On Sun, Oct 15, 2023 at 02:23:28AM +0200, Salvo Tomaselli wrote:
> > Could you improve the description?
> > 
> > What does this do?
> > 
> > For me low level access is ioctl, write or similar…
> 
> no - in this case "low level" is a synonym for "hard-coded"
> 
> It's just another of the programs written with the assumption that the
> terminal is xterm (or one of its imitators).

Well the long description clearly states that it only focuses on
"terminals in the tradition of VT1xx (like xterm, etc)".

It does make vastly different choices in terminal support than termcap and
ncurses. That allows is to have a more direct mapping of the terminal
functions but of course, it does not support nearly the breadth of
terminals that ncurses can support.

But i think that is ok, as many users nowadays use terminals in the
supported set.

Another choice where it differs is the it is build with the reality in mind
that $TERM is much more likely to be blatently wrong that than it having to
work with a terminal that is not "xterm like". Thus is uses terminal
response fingerprinting and terminal self identification to decide what
terminal implementation it is likely talking to and then uses its internal
(hard coded) terminal information to select features and workarounds.

Yes. That is throwing the towel on expecting properly administrated
systems, but a varity of factors ends making properly administrated
systems to be on the decline.

> 
> Unlike the last one on this topic, it uses the terminology of ncurses
> without using the word "ncurses".

I'm not sure what you mean with the terminology of ncurses, mostly because
ncurses certainly defined a lot of the terminology of the field and thus
it's hard to say where something is ncurses (or curses) specific or just
the broader terminology with terminals.

And i think the debian package is not really the place for a detailed
discussion of the tradeoffs between say ncurses and termpaint. Or termpaint
and s-lang or ... They would need a lot of nouance, and i'm pretty sure i
would get it wrong. So i think it is better to be silent on that than to
offer something incomplete.

As you pointed out, it is not even a alternative to ncurses, because it has
a vastly smaller set of supported terminals.

 - Martin

Bug#1036896: unblock: vdr-plugin-xineliboutput/2.2.0+git20211212-2.2

2023-05-29 Thread Martin Hostettler 
> unblock vdr-plugin-xineliboutput/2.2.0+git20211212-2.2

Now also attaching the *source* debdiff. Sorry for the confusion.

diff -Nru vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog 
vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog
--- vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog 2022-01-25 
19:06:50.0 +0100
+++ vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog 2023-05-18 
13:40:36.0 +0200
@@ -1,3 +1,11 @@
+vdr-plugin-xineliboutput (2.2.0+git20211212-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing Breaks/Replaces for correction of xineliboutput-fbfe desktop
+icon. Closes: #1034915
+
+ -- Andreas Metzler   Thu, 18 May 2023 13:40:36 +0200
+
 vdr-plugin-xineliboutput (2.2.0+git20211212-2.1) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control 
vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control
--- vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control   2022-01-25 
19:06:50.0 +0100
+++ vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control   2023-05-18 
13:39:22.0 +0200
@@ -54,6 +54,8 @@
 Package: xineliboutput-fbfe
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, libxine2-xvdr (= 
${binary:Version}), libxine2-console
+Breaks: xineliboutput-sxfe (<< 2.2.0+git20211212-2.1)
+Replaces: xineliboutput-sxfe (<< 2.2.0+git20211212-2.1)
 Description: Remote Framebuffer frontend for vdr-plugin-xineliboutput
  This frambuffer remote frontend plays back streams provided by
  vdr-plugin-xineliboutput.
diff -Nru vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog 
vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog
--- vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog 2022-01-25 
19:06:50.0 +0100
+++ vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog 2023-05-18 
13:40:36.0 +0200
@@ -1,3 +1,11 @@
+vdr-plugin-xineliboutput (2.2.0+git20211212-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing Breaks/Replaces for correction of xineliboutput-fbfe desktop
+icon. Closes: #1034915
+
+ -- Andreas Metzler   Thu, 18 May 2023 13:40:36 +0200
+
 vdr-plugin-xineliboutput (2.2.0+git20211212-2.1) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control 
vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control
--- vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control   2022-01-25 
19:06:50.0 +0100
+++ vdr-plugin-xineliboutput-2.2.0+git20211212/debian/control   2023-05-18 
13:39:22.0 +0200
@@ -54,6 +54,8 @@
 Package: xineliboutput-fbfe
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, libxine2-xvdr (= 
${binary:Version}), libxine2-console
+Breaks: xineliboutput-sxfe (<< 2.2.0+git20211212-2.1)
+Replaces: xineliboutput-sxfe (<< 2.2.0+git20211212-2.1)
 Description: Remote Framebuffer frontend for vdr-plugin-xineliboutput
  This frambuffer remote frontend plays back streams provided by
  vdr-plugin-xineliboutput.

Bug#1036883: unblock: inventor/2.1.5-10+dfsg-2

2023-05-29 Thread Martin Hostettler 
> unblock inventor/2.1.5-10+dfsg-2

Now also attaching the *source* debdiff. Sorry for the confusion.

diff -Nru inventor-2.1.5-10+dfsg/debian/changelog 
inventor-2.1.5-10+dfsg/debian/changelog
--- inventor-2.1.5-10+dfsg/debian/changelog 2023-02-06 00:50:57.0 
+0100
+++ inventor-2.1.5-10+dfsg/debian/changelog 2023-05-28 03:08:52.0 
+0200
@@ -1,3 +1,13 @@
+inventor (2.1.5-10+dfsg-2) unstable; urgency=medium
+
+  [ Steve Robbins ]
+  * [6c3239d] Fix broken symlinks to Century-Schoolbook fonts.
+Closes: #1036603.
+  * [d2a2a86] Remove dep from transitional dummy package gsfonts-x11
+  * [54dce68] Change dep from transitional libfreetype6-dev to libfreetype-dev.
+
+ -- Steve M. Robbins   Sat, 27 May 2023 20:08:52 -0500
+
 inventor (2.1.5-10+dfsg-1) unstable; urgency=high
 
   * Team upload
diff -Nru inventor-2.1.5-10+dfsg/debian/control 
inventor-2.1.5-10+dfsg/debian/control
--- inventor-2.1.5-10+dfsg/debian/control   2023-02-05 23:50:02.0 
+0100
+++ inventor-2.1.5-10+dfsg/debian/control   2023-05-28 03:08:52.0 
+0200
@@ -12,7 +12,7 @@
libmotif-dev,
libglw1-mesa-dev,
libglu1-mesa-dev,
-   libfreetype6-dev,
+   libfreetype-dev,
libjpeg-dev,
bison
 Standards-Version: 4.6.1
@@ -27,7 +27,7 @@
 Depends: ${misc:Depends},
  ${shlibs:Depends},
  xfonts-scalable,
- fonts-urw-base35 | gsfonts-x11
+ fonts-urw-base35
 Recommends: xdg-utils,
 xpdf | pdf-viewer
 Conflicts: libinventor0
diff -Nru inventor-2.1.5-10+dfsg/debian/link-fonts.sh 
inventor-2.1.5-10+dfsg/debian/link-fonts.sh
--- inventor-2.1.5-10+dfsg/debian/link-fonts.sh 2023-02-05 23:50:02.0 
+0100
+++ inventor-2.1.5-10+dfsg/debian/link-fonts.sh 2023-05-28 03:08:52.0 
+0200
@@ -2,6 +2,7 @@
 
 fontpath=/usr/share/inventor/fonts
 type1=/usr/share/fonts/X11/Type1
+urw=/usr/share/fonts/type1/urw-base35
 
 mkdir -p $fontpath
 cd $fontpath
@@ -10,10 +11,10 @@
 ln -s -f $type1/c0582bt_.pfb  Courier-Italic
 ln -s -f $type1/c0583bt_.pfb  Courier-Bold
 ln -s -f $type1/c0611bt_.pfb  Courier-BoldItalic
-ln -s -f $type1/c059013l.pfb  Century-Schoolbook-Roman
-ln -s -f $type1/c059016l.pfb  Century-Schoolbook-Bold
-ln -s -f $type1/c059033l.pfb  Century-Schoolbook-Italic
-ln -s -f $type1/c059036l.pfb  Century-Schoolbook-BoldItalic
+ln -s -f $urw/C059-Roman.t1  Century-Schoolbook-Roman
+ln -s -f $urw/C059-Bold.t1  Century-Schoolbook-Bold
+ln -s -f $urw/C059-Italic.t1  Century-Schoolbook-Italic
+ln -s -f $urw/C059-BdIta.t1  Century-Schoolbook-BoldItalic
 
 
 for i in $type1/*.pfa; do
diff -Nru inventor-2.1.5-10+dfsg/debian/changelog 
inventor-2.1.5-10+dfsg/debian/changelog
--- inventor-2.1.5-10+dfsg/debian/changelog 2023-02-06 00:50:57.0 
+0100
+++ inventor-2.1.5-10+dfsg/debian/changelog 2023-05-28 03:08:52.0 
+0200
@@ -1,3 +1,13 @@
+inventor (2.1.5-10+dfsg-2) unstable; urgency=medium
+
+  [ Steve Robbins ]
+  * [6c3239d] Fix broken symlinks to Century-Schoolbook fonts.
+Closes: #1036603.
+  * [d2a2a86] Remove dep from transitional dummy package gsfonts-x11
+  * [54dce68] Change dep from transitional libfreetype6-dev to libfreetype-dev.
+
+ -- Steve M. Robbins   Sat, 27 May 2023 20:08:52 -0500
+
 inventor (2.1.5-10+dfsg-1) unstable; urgency=high
 
   * Team upload
diff -Nru inventor-2.1.5-10+dfsg/debian/control 
inventor-2.1.5-10+dfsg/debian/control
--- inventor-2.1.5-10+dfsg/debian/control   2023-02-05 23:50:02.0 
+0100
+++ inventor-2.1.5-10+dfsg/debian/control   2023-05-28 03:08:52.0 
+0200
@@ -12,7 +12,7 @@
libmotif-dev,
libglw1-mesa-dev,
libglu1-mesa-dev,
-   libfreetype6-dev,
+   libfreetype-dev,
libjpeg-dev,
bison
 Standards-Version: 4.6.1
@@ -27,7 +27,7 @@
 Depends: ${misc:Depends},
  ${shlibs:Depends},
  xfonts-scalable,
- fonts-urw-base35 | gsfonts-x11
+ fonts-urw-base35
 Recommends: xdg-utils,
 xpdf | pdf-viewer
 Conflicts: libinventor0
diff -Nru inventor-2.1.5-10+dfsg/debian/link-fonts.sh 
inventor-2.1.5-10+dfsg/debian/link-fonts.sh
--- inventor-2.1.5-10+dfsg/debian/link-fonts.sh 2023-02-05 23:50:02.0 
+0100
+++ inventor-2.1.5-10+dfsg/debian/link-fonts.sh 2023-05-28 03:08:52.0 
+0200
@@ -2,6 +2,7 @@
 
 fontpath=/usr/share/inventor/fonts
 type1=/usr/share/fonts/X11/Type1
+urw=/usr/share/fonts/type1/urw-base35
 
 mkdir -p $fontpath
 cd $fontpath
@@ -10,10 +11,10 @@
 ln -s -f $type1/c0582bt_.pfb  Courier-Italic
 ln -s -f $type1/c0583bt_.pfb  Courier-Bold
 ln -s -f $type1/c0611bt_.pfb  Courier-BoldItalic
-ln -s -f $type1/c059013l.pfb  Century-Schoolbook-Roman
-ln -s -f $type1/c059016l.pfb  Century-Schoolbook-Bold
-ln -s -f $type1/c059033l.pfb  Century-Schoolbook-Italic
-ln -s -f $type1/c059036l.pfb  Century-Schoolbook-BoldItalic
+ln -s -f

Bug#1036889: unblock: ignition-physics/5.1.0+ds1-4.1

2023-05-29 Thread Martin Hostettler 
> unblock ignition-physics/5.1.0+ds1-4.1

Now also attaching the *source* debdiff. Sorry for the confusion.

diff -Nru ignition-physics-5.1.0+ds1/debian/changelog 
ignition-physics-5.1.0+ds1/debian/changelog
--- ignition-physics-5.1.0+ds1/debian/changelog 2022-02-14 23:29:14.0 
+0100
+++ ignition-physics-5.1.0+ds1/debian/changelog 2023-05-21 20:50:53.0 
+0200
@@ -1,3 +1,13 @@
+ignition-physics (5.1.0+ds1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "missing Depends: libignition-physics5-bullet-plugin5 (=
+${binary:Version})": add missing dependency to libignition-physics-dev
+package.
+(Closes: #1035865)
+
+ -- gregor herrmann   Sun, 21 May 2023 20:50:53 +0200
+
 ignition-physics (5.1.0+ds1-4) unstable; urgency=medium
 
   * Include more debug information in FAKE patch
diff -Nru ignition-physics-5.1.0+ds1/debian/control 
ignition-physics-5.1.0+ds1/debian/control
--- ignition-physics-5.1.0+ds1/debian/control   2022-02-14 14:41:23.0 
+0100
+++ ignition-physics-5.1.0+ds1/debian/control   2023-05-21 20:50:52.0 
+0200
@@ -177,6 +177,7 @@
  libignition-physics-mesh-dev,
  libignition-physics-sdf-dev,
  libignition-physics-tpe-dev,
+ libignition-physics5-bullet-plugin5 (= ${binary:Version}),
  libignition-physics5-dartsim-plugin5 (= ${binary:Version}),
 # Bullet component dependencies
  libbullet-dev,
diff -Nru ignition-physics-5.1.0+ds1/debian/changelog 
ignition-physics-5.1.0+ds1/debian/changelog
--- ignition-physics-5.1.0+ds1/debian/changelog 2022-02-14 23:29:14.0 
+0100
+++ ignition-physics-5.1.0+ds1/debian/changelog 2023-05-21 20:50:53.0 
+0200
@@ -1,3 +1,13 @@
+ignition-physics (5.1.0+ds1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "missing Depends: libignition-physics5-bullet-plugin5 (=
+${binary:Version})": add missing dependency to libignition-physics-dev
+package.
+(Closes: #1035865)
+
+ -- gregor herrmann   Sun, 21 May 2023 20:50:53 +0200
+
 ignition-physics (5.1.0+ds1-4) unstable; urgency=medium
 
   * Include more debug information in FAKE patch
diff -Nru ignition-physics-5.1.0+ds1/debian/control 
ignition-physics-5.1.0+ds1/debian/control
--- ignition-physics-5.1.0+ds1/debian/control   2022-02-14 14:41:23.0 
+0100
+++ ignition-physics-5.1.0+ds1/debian/control   2023-05-21 20:50:52.0 
+0200
@@ -177,6 +177,7 @@
  libignition-physics-mesh-dev,
  libignition-physics-sdf-dev,
  libignition-physics-tpe-dev,
+ libignition-physics5-bullet-plugin5 (= ${binary:Version}),
  libignition-physics5-dartsim-plugin5 (= ${binary:Version}),
 # Bullet component dependencies
  libbullet-dev,

Bug#1036896: unblock: vdr-plugin-xineliboutput/2.2.0+git20211212-2.2

2023-05-28 Thread Martin Hostettler 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: vdr-plugin-xinelibout...@packages.debian.org, Andreas Metzler 

Control: affects -1 + src:vdr-plugin-xineliboutput

[I'm not the uploader of the update, but filing to meet the deadline]

Please unblock package vdr-plugin-xineliboutput

[ Reason ]
QA work by Helmut Grohne uncovered that xineliboutput-fbfe is missing
Breaks+Replaces for upgrades without unpack errors.

[ Impact ]
Possible unpack errors when users upgrade to bookworm.

[ Tests ]
No package provided tests found this bug. I did not do upgrade tests, but i
am relying that the uploader of the nmu (Andreas Metzler) did.

[ Risks ]
The exact version for the breaks+replaces could be wrong, but the version
of the package in bullseye is covered so the risks should be minor.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

[ Other info ]
I've reviewed the complete diffoscope
--exclude-directory-metadata=recursive output and there are only the
expected changes and changes that are consistent with a rebuild of a
package after the debian archive evolved for a year or so since the last
build.

[ Full debdiff ]
$ debdiff *.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in first .deb but not in second
-
-rw-r--r--  root/root   
/usr/share/doc/xineliboutput-fbfe/changelog.Debian.amd64.gz

Control files: lines which differ (wdiff format)

{+Breaks: xineliboutput-sxfe (<< 2.2.0+git20211212-2.1)+}
Depends: libc6 (>= [-2.33),-] {+2.34),+} libcec6 (>= 6.0.2), libjpeg62-turbo 
(>= 1.3.1), libxine2 (>= 1.2.0), libxine2-xvdr (= 
[-2.2.0+git20211212-2.1+b1),-] {+2.2.0+git20211212-2.2),+} libxine2-console
Installed-Size: [-278-] {+270+}
{+Replaces: xineliboutput-sxfe (<< 2.2.0+git20211212-2.1)+}
Source: vdr-plugin-xineliboutput [-(2.2.0+git20211212-2.1)-]
Version: [-2.2.0+git20211212-2.1+b1-] {+2.2.0+git20211212-2.2+}


unblock vdr-plugin-xineliboutput/2.2.0+git20211212-2.2
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in first .deb but not in second
-
-rw-r--r--  root/root   
/usr/share/doc/xineliboutput-fbfe/changelog.Debian.amd64.gz

Control files: lines which differ (wdiff format)

{+Breaks: xineliboutput-sxfe (<< 2.2.0+git20211212-2.1)+}
Depends: libc6 (>= [-2.33),-] {+2.34),+} libcec6 (>= 6.0.2), libjpeg62-turbo 
(>= 1.3.1), libxine2 (>= 1.2.0), libxine2-xvdr (= 
[-2.2.0+git20211212-2.1+b1),-] {+2.2.0+git20211212-2.2),+} libxine2-console
Installed-Size: [-278-] {+270+}
{+Replaces: xineliboutput-sxfe (<< 2.2.0+git20211212-2.1)+}
Source: vdr-plugin-xineliboutput [-(2.2.0+git20211212-2.1)-]
Version: [-2.2.0+git20211212-2.1+b1-] {+2.2.0+git20211212-2.2+}

Bug#1036889: unblock: ignition-physics/5.1.0+ds1-4.1

2023-05-28 Thread Martin Hostettler 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: ignition-phys...@packages.debian.org, gregor herrmann 

Control: affects -1 + src:ignition-physics

[I'm not the uploader of the update, but filing to meet the deadline]

Please unblock package ignition-physics

[ Reason ]
QA work by Andreas Beckmann uncovered that libignition-physics-dev is
missing a Depends on libignition-physics5-bullet-plugin5.

[ Impact ]
If the current package is shipped with bookworm, users of
libignition-physics-dev will have to manually install
libignition-physics5-bullet-plugin5 to properly compile sources using that
plugin.

If the current package is removed, users of bookworm will not be able to
use ignition-physics from debian packages.

[ Tests ]
No package provided tests found this bug. I've manually tested that the
symlinks that are created are no longer pointing to non existing files.

[ Risks ]
Only a dependency was added, so the risk should be minimal.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

[ Other info ]
I've reviewed the complete diffoscope
--exclude-directory-metadata=recursive output and there are only the
expected changes and changes that would be expected for a rebuild of a
package that is not fully reproducable (build dir paths in the build
package changed).

[ Full debdiff ]
$ debdiff *.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in first .deb but not in second
-
-rw-r--r--  root/root   
/usr/share/doc/libignition-physics-dev/changelog.Debian.amd64.gz

Control files: lines which differ (wdiff format)

Depends: libignition-physics-core-dev, libignition-physics-mesh-dev, 
libignition-physics-sdf-dev, libignition-physics-tpe-dev, 
{+libignition-physics5-bullet-plugin5 (= 5.1.0+ds1-4.1),+} 
libignition-physics5-dartsim-plugin5 (= [-5.1.0+ds1-4+b1),-] 
{+5.1.0+ds1-4.1),+} libbullet-dev, libignition-common-dev (>= 4.0.0), 
libignition-math-dev (>= 6.0.0), libignition-plugin-dev (>= 1.1.0), libdart-dev 
(>= 6.12.1+dfsg4), libdart-external-convhull-3d-dev (>= 6.12.1+dfsg4), 
libdart-collision-ode-dev (>= 6.12.1+dfsg4), libdart-utils-urdf-dev (>= 
6.12.1+dfsg4), libdart-utils-dev (>= 6.12.1+dfsg4), 
libdart-external-odelcpsolver-dev (>= 6.12.1+dfsg4), 
libdart-external-ikfast-dev (>= 6.12.1+dfsg4), libdart-collision-bullet-dev (>= 
6.12.1+dfsg4), libsdformat-dev (>= 12.0.0)
Installed-Size: [-592-] {+591+}
Source: ignition-physics [-(5.1.0+ds1-4)-]
Version: [-5.1.0+ds1-4+b1-] {+5.1.0+ds1-4.1+}


unblock ignition-physics/5.1.0+ds1-4.1
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in first .deb but not in second
-
-rw-r--r--  root/root   
/usr/share/doc/libignition-physics-dev/changelog.Debian.amd64.gz

Control files: lines which differ (wdiff format)

Depends: libignition-physics-core-dev, libignition-physics-mesh-dev, 
libignition-physics-sdf-dev, libignition-physics-tpe-dev, 
{+libignition-physics5-bullet-plugin5 (= 5.1.0+ds1-4.1),+} 
libignition-physics5-dartsim-plugin5 (= [-5.1.0+ds1-4+b1),-] 
{+5.1.0+ds1-4.1),+} libbullet-dev, libignition-common-dev (>= 4.0.0), 
libignition-math-dev (>= 6.0.0), libignition-plugin-dev (>= 1.1.0), libdart-dev 
(>= 6.12.1+dfsg4), libdart-external-convhull-3d-dev (>= 6.12.1+dfsg4), 
libdart-collision-ode-dev (>= 6.12.1+dfsg4), libdart-utils-urdf-dev (>= 
6.12.1+dfsg4), libdart-utils-dev (>= 6.12.1+dfsg4), 
libdart-external-odelcpsolver-dev (>= 6.12.1+dfsg4), 
libdart-external-ikfast-dev (>= 6.12.1+dfsg4), libdart-collision-bullet-dev (>= 
6.12.1+dfsg4), libsdformat-dev (>= 12.0.0)
Installed-Size: [-592-] {+591+}
Source: ignition-physics [-(5.1.0+ds1-4)-]
Version: [-5.1.0+ds1-4+b1-] {+5.1.0+ds1-4.1+}

Bug#1036883: unblock: inventor/2.1.5-10+dfsg-2

2023-05-28 Thread Martin Hostettler 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: inven...@packages.debian.org, Steve M. Robbins 
Control: affects -1 + src:inventor

[I'm not the uploader of the update, but filing to meet the deadline]

Please unblock package inventor

[ Reason ]
QA work by Andreas Beckmann uncovered that libinventor1 created broken
symlinks to font files that have been renamed.

[ Impact ]
Some broken font symlinks will be created and the application might fail to
find some fonts.

[ Tests ]
No package provided tests found this bug. I've manually tested that the
symlinks that are created are no longer pointing to non existing files.

[ Risks ]

Steven Robbins described the problem the following way:
> I couldn't say "harmless", but "mostly harmless", I'd think.  

And uploaded a fix to unstable.

The risks should be minimal given that the change in the package are
minimal.


[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

[ Other info ]
I've reviewed the complete diffoscope
--exclude-directory-metadata=recursive output and there are only the
expected changes and changes that would be expected for a rebuild of a
package that is not fully reproducable (gnu debuglink and build id).

[ Full debdiff ]
$ debdiff *.deb
File lists identical (after any substitutions)

Control files: lines which differ (wdiff format)

Depends: libc6 (>= 2.34), libfreetype6 (>= 2.2.1), libgcc-s1 (>= 3.0), libgl1, 
libglu1-mesa | libglu1, libjpeg62-turbo (>= 1.3.1), libstdc++6 (>= 5), 
libx11-6, libxi6, libxm4 (>= 2.3.4), libxt6, xfonts-scalable, fonts-urw-base35 
[-| gsfonts-x11-]
Version: [-2.1.5-10+dfsg-1-] {+2.1.5-10+dfsg-2+}


unblock inventor/2.1.5-10+dfsg-2

Bug#1036880: unblock: pyocd/0.13.1+dfsg-3

2023-05-28 Thread Martin Hostettler 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: py...@packages.debian.org, Adrian Bunk 
Control: affects -1 + src:pyocd

[I'm not the uploader of the update, but filing to meet the deadline]

Please unblock package pyocd

This upload backports upstream changes to support the python version in
bookworm.

[ Reason ]
The current version in bookworm is not compatible with the python version
in bookworm.

[ Impact ]
Using pyocd-gdbserver currently crashes.

[ Tests ]
Manually tested that it no longer crashes on start. I did not test further.

[ Risks ]
If the fix did not work debian would be shipping a broken package, if this
package is not removed before release.

On the other hand if the upstream fix works as expected debian bookworm
users will still be able to debug their microcontroller projects and will
still have packages for yotta and firmware-microbit-micropython.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

[ Other info ]
I've reviewed the complete diffoscope
--exclude-directory-metadata=recursive output and there are only the
expected changes in the python code for importing, some minor changes from
building with a more up to date dh_python3/debhelper version and very minor
changes in man pages. 

[ Full debdiff ]
File lists identical (after any substitutions)

Control files: lines which differ (wdiff format)

Version: [-0.13.1+dfsg-2-] {+0.13.1+dfsg-3+}


unblock pyocd/0.13.1+dfsg-3

Bug#1036876: Consider documenting that booting from partial volume groups is no longer supported.

2023-05-28 Thread Martin Hostettler 
Package: release-notes
Severity: wishlist
X-Debbugs-Cc: Debian LVM Team , Guilhem Moulin 
, Bastian Blank 

In
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018730
we have learned that debian was previously able to boot from lvm volume
groups that were not complete while running in the initramfs and that
bookworm will no longer support this.

Please consider adding this change to the release notes, if appropriate.

 - Martin

Bug#1036263: guestfs-tools: FTBFS in testing: make[6]: *** [Makefile:1716: test-suite.log] Error 1

2023-05-27 Thread Martin Hostettler 
tags -1 + unreproducible
thanks

On Thu, 25 May 2023 21:00:18 +0200 Bastian Germann  wrote:
> I cannot reproduce this.
> 

I can't reproduce this either.

I tried 2 variants and both build fine (using an up to date sid VM to
run the build using bookworm docker container or pbuilder).

docker run -it debian:bookworm /bin/bash
apt install devscripts build-essential aptitude pbuilder
dget 
https://deb.debian.org/debian/pool/main/g/guestfs-tools/guestfs-tools_1.48.2-1.dsc
/usr/lib/pbuilder/pbuilder-satisfydepends
debuild -uc -us -j4

Variant B
docker run --privileged -it debian:bookworm /bin/bash
apt install devscripts pbuilder
pbuilder create --distribution bookworm
dget 
https://deb.debian.org/debian/pool/main/g/guestfs-tools/guestfs-tools_1.48.2-1.dsc
pbuilder build --distribution bookworm guestfs-tools_1.48.2-1.dsc

Bug#1036021: cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror

2023-05-26 Thread Martin Hostettler 
On Thu, May 25, 2023 at 09:52:55PM +0200, Gürkan Myczko wrote:
> On 25.05.2023 19:47, Martin Hostettler wrote:
> > On 19/05/2023 12.48, Martin Hostettler wrote:
> > > It seems what is needed is this:
> > > 
> > > mv 
> > > debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static/components
> > > debian/cadabra2/usr/share/javascript
> > > rmdir
> > > debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static
> > > rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook
> > > 
> > > (The wildcards are used to avoid hard coding the current debian
> > > default
> > > python version)
> > 
> > Any chance to get this changes into an upload? The deadline for last
> > unblock requests is quickly coming.
> 
> I'm sorry, I'm busy with other things, if you feel like it please go ahead
> add yourself to
> Uploaders and upload. Or NMU, as you like. I am also fine reviewing changes,
> and uploading
> via mentors.d.n.
> 

I don't have a gpg key, so i think mentors.d.n is not an option but i
uploaded to some temporary web location. So feel free to review from there.
Also feel free to do what makes the most sense to you with the changelog
entry and version.

https://uchuujin.de/tmp/cadabra/cadabra2_2.4.3.2-0.2.dsc

I'm also attaching the intended patch, in case that is easier to review.

 - Martin
diff -ru orig/cadabra2-2.4.3.2/debian/changelog patched/cadabra2-2.4.3.2/debian/changelog
--- orig/cadabra2-2.4.3.2/debian/changelog	2023-02-06 22:21:08.0 +
+++ patched/cadabra2-2.4.3.2/debian/changelog	2023-05-26 18:17:02.306980093 +
@@ -1,3 +1,13 @@
+cadabra2 (2.4.3.2-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Move codemirror integration to canonical path to
+avoid symlink/directory conflict on
+/usr/lib/python3/dist-packages/notebook/static/components/codemirror
+(Closes: 1036021)
+
+ -- Martin Hostettler   Fri, 26 May 2023 06:41:29 +
+
 cadabra2 (2.4.3.2-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -ru orig/cadabra2-2.4.3.2/debian/rules patched/cadabra2-2.4.3.2/debian/rules
--- orig/cadabra2-2.4.3.2/debian/rules	2022-10-13 07:06:04.0 +
+++ patched/cadabra2-2.4.3.2/debian/rules	2023-05-26 06:41:08.613257764 +
@@ -27,6 +27,9 @@
 	dh_auto_install
 	sed -i s,python3.10,python3,g debian/cadabra2/usr/bin/cadabra2
 	sed -i s,site-,dist-,g debian/cadabra2/usr/bin/cadabra2
+	mv debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static/components debian/cadabra2/usr/share/javascript
+	rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static
+	rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook
 
 override_dh_shlibdeps:
 	@echo test

Bug#1034824: tomcat9 should not be released with Bookworm

2023-05-25 Thread Martin Hostettler 
I was asked to send a update to this bug from my notes/open tabs.

>From what i can see this is still a problem and it is getting very late
to fix all the fallout.

There are still 2 packages that are not fixed for this.

src:trapperkeeper-webserver-jetty9-clojure (#1036250) which is as far as
I understand a dependency of puppet, which is used by a lot of admins
including Debian's own DSA.

Which even after trying to fix the build problem left the package in a
state where it the whole logging is non functional: 

Quoting from J�r�me Charaoui in (#1036250):
> I did further tests with puppetserver, which is a downstream dependency 
> of trapperkeeper-webserver-jetty9-clojure and unfortunately, the web 
> requests (access) logging remains broken. There are no warnings or error 
> messages anywhere: as you can imagine, the logging events are simply 
> lost in the ether.

I'm not sure if the latest patches from 2023-05-22 do fix those, but there
was no follow up on the bug with details.

Then there is src:tomcatjss (1031816) which seems to have zero progress
since the bug was filed.

This is a dependency of at least dogtag-pki, pki-ca, pki-kra, pki-ocsp,
pki-server, pki-tks and pki-tps

I'm not sure what the actual state of src:logback is. It seems the problems
in trapperkeeper-webserver-jetty9-clojure are partially related to the
state of logback.
Do we know that it properly works with the tomcat10 migration patchset?
Logback seems to have quite a few reverse dependencies as well.


Some bugs have according to the bts been fixed and migrated meanwile:

#1035995: bazel-bootstrap
#1011597: tiles
#1033366: resteasy3.0

What is the plan here to get this in shape for in time before last unblock
requests for bookworm on the 28th?

 - Martin

Bug#1036021: cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror

2023-05-25 Thread Martin Hostettler 
On 19/05/2023 12.48, Martin Hostettler wrote:
> It seems what is needed is this:
> 
> mv 
> debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static/components 
> debian/cadabra2/usr/share/javascript
> rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static
> rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook
> 
> (The wildcards are used to avoid hard coding the current debian default
> python version)

Any chance to get this changes into an upload? The deadline for last
unblock requests is quickly coming.

 - Martin

Bug#1036021: cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror

2023-05-22 Thread Martin Hostettler 
On Mon, May 22, 2023 at 11:59:37AM +0200, Andreas Beckmann wrote:
> On 19/05/2023 12.48, Martin Hostettler wrote:
> > It seems what is needed is this:
> > 
> > mv 
> > debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static/components 
> > debian/cadabra2/usr/share/javascript
> > rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static
> > rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook
> > 
> > (The wildcards are used to avoid hard coding the current debian default
> > python version)
> 
> Does this still work if there is more than one supported python version
> (during python transitions)? It's probably OK to to break support for
> multiple python versions now (as we currently only have one and stable
> releases only have one), but this may need to be revisited for bookworm+1.
> 

As this is in the temporary directory where the build code is installed i
would suspect this will work with more supported python versions as well.
I think this is just a case of the upstream build system including the
python version of the python version used to build the package.
(i think usually debhelper takes care of removing that, but this is before
any of that runs)

At least as long as the code there is compatible with all supported python
versions in debian.

But i don't know anything for certain, as i don't know cadabre but just
want to help solve RC bugs against packages i use (like python3-notebook)

 - Martin

Bug#1036272: youtube-dl - Should this be released with Bookworm?

2023-05-21 Thread Martin Hostettler 
> Do we really need to release this package in a not so usable state?

It seems that currently mkchromecast still depends on this package. So just
removing it would remove mkchromecast as well. But i'm not sure how much
of mkchromecast works without a binary called youtube-dl.

Also some users might benefit from automatically transitioning to
youtube-dlp, on the other hand yt-dlp does not seem to provide youtube-dl
as a binary, so maybe this is unexpected as well.

 - Martin

Bug#1036021: cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror

2023-05-19 Thread Martin Hostettler 
On Fri, May 19, 2023 at 11:09:41AM +0200, Helmut Grohne wrote:
> On Fri, May 19, 2023 at 10:27:46AM +0200, Martin Hostettler wrote:
> 
> Do I understand correctly that all we have to do here is ship the file
> in its "canonical" path after resolving the symbolic link from
> python3-notebook? In other words, a simple file move in the data.tar?

If dpkg can handle that even with the symlink, then i think, yes.

> 
> > I have no clue how the correct way to make this switch in the debian
> > packaging is, but i hope this messages helps to confirm what is happening
> > in this situation and someone with more solid clue about these kind of
> > problems in packaging can resolve this.
> 
> It is as simple as adding a mv invocation to an
> appropriate override_dh_something to debian/rules. That's something that
> easily passes an unblock request with the release team.
> 
> Probably, appending to override_dh_auto_install is sufficient:
> 
> mv 
> debian/cadabra2/usr/lib/python3/dist-packages/notebook/static/components 
> debian/cadabra2/usr/lib/share/javascript
> rmdir debian/cadabra2/usr/lib/python3/dist-packages/notebook/static
> rmdir debian/cadabra2/usr/lib/python3/dist-packages/notebook
> 

It seems what is needed is this:

   mv 
debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static/components 
debian/cadabra2/usr/share/javascript
   rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static
   rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook

(The wildcards are used to avoid hard coding the current debian default
python version)

That results in a debdiff like this:
 
Files in second .deb but not in first
-
-rw-r--r--  root/root   /usr/share/javascript/codemirror/mode/cadabra/cadabra.js

Files in first .deb but not in second
-
-rw-r--r--  root/root   
/usr/lib/python3/dist-packages/notebook/static/components/codemirror/mode/cadabra/cadabra.js


Which looks ok.

both before the patch and after the following file exists when
python3-notebook was installed before installing cadabra:

/usr/share/javascript/codemirror/mode/cadabra/cadabra.js


I just noticed that the override_dh_auto_install also contains a line not
yet updated to python 3.11

> sed -i s,python3.10,python3,g debian/cadabra2/usr/bin/cadabra2

Updateing that might be a good idea too. Switching that to 3.11 results in
the further debdiff:

Control files: lines which differ (wdiff format)

Depends: fonts-cmu, python3 (<< 3.12), python3 (>= 3.11~), [-python3.11:any,-] 
python3:any (>= 3.6~)

Which seems ok too.

@G�rkan Myczko

Could you see if that seems sane and if it is do an upload with the moved
file? (I'm not a DD, so i can't help out with that)

 - Martin

Bug#1036021: cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror

2023-05-19 Thread Martin Hostettler 
On Fri, 19 May 2023 08:48:46 +0200 Helmut Grohne  wrote:
> Hi,
> 
> On Thu, May 18, 2023 at 10:30:48PM +0400, Andrey Rakhmatullin wrote:
> > Looks like the file in cadabra2, let's say, provides integration between
> > it and python3-notebook. 
> 
> I'm not sure what you want to achieve here. If this is about two
> competing implementations where one is strictly superior to the other,
> then maybe dpkg-diverting the lesser one would be reasonable? The
> diversion mechanism works entirely without adding a relationship between
> the packages.
> 
> Another option is use of update-alternatives, which also allows
> specifying a preference on the packaging level while also providing a
> user choice.
> 
> I lack the context of the package at hand, so I'll leave that up to you,
> but I think there is sufficient options on the table for dealing with it
> in a good way. Please choose wisely.
> 

>From what i see the intended result is not a file replacement but adding a
file into codemirror.

If everything works well the sequence is that python3-notebook pulls in
libjs-codemirror which contains various files in
/usr/share/javascript/codemirror/

python3-notebook then ships
/usr/lib/python3/dist-packages/notebook/static/components/codemirror
as
symlink (../../../../../../share/javascript/codemirror aka
/usr/lib/share/javascript/codemirror )
pointing to the codemirror library.

Now cadabra2 wants to place an additional file (mode/cadabra/cadabra.js)
for integration into the codemirror library used by python3-notebook.

Currently it does that by using the path
/usr/lib/python3/dist-packages/notebook/static/components/codemirror/mode/cadabra/cadabra.js
in data.tar which "works" when python3-notebook was installed previously,
but is the subject of this bug because when installation order if different
this does the wrong thing.

So all the ideas of diverts and alternatives seems to be unneeded. What
seems to be needed is finding the correct way for cadabra2 to always place
the integration file directly into /usr/lib/share/javascript/codemirror
without depending on the symlink from python3-notebook that might or might
not be there.

I have no clue how the correct way to make this switch in the debian
packaging is, but i hope this messages helps to confirm what is happening
in this situation and someone with more solid clue about these kind of
problems in packaging can resolve this.

- Martin

Bug#1032553: magic-wormhole: FTBFS in testing: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13

2023-04-07 Thread Martin Hostettler 
tags 1032553 + patch

thanks

On Wed, Apr 05, 2023 at 09:22:45AM +0200, Sascha Steinbiss wrote:
> Hi all,
> 
> [...]
> > This is mentioned in
> > https://github.com/magic-wormhole/magic-wormhole/issues/458 as likely
> > a "timing issue". Not sure if it's fixed upstream. >
> 
> Could it make sense to also patch the tests to include the delay that is
> mentioned in the GitHub issue comments?

I've tried adding a 2 second delay in the failing test and that yields a
package that builds reliably for me. I just rebuild the package with the
patch 250 times successfully in a row.

This patch works without any other commits backported.

--- magic-wormhole-0.12.0/src/wormhole/test/test_wormhole.py2021-02-05 
02:16:21.0 +
+++ magic-wormhole-0.12.0.fix/src/wormhole/test/test_wormhole.py
2023-04-07 14:44:26.792819150 +
@@ -6,6 +6,7 @@
 from twisted.internet import reactor
 from twisted.internet.defer import gatherResults, inlineCallbacks, returnValue
 from twisted.internet.error import ConnectionRefusedError
+from twisted.internet.task import deferLater
 from twisted.trial import unittest
 
 import mock
@@ -505,6 +506,7 @@
 yield self.assertFailure(w1.get_welcome(), WrongPasswordError)  # late
 
 yield self.assertFailure(w1.close(), WrongPasswordError)
+yield deferLater(reactor, 2, lambda: None)
 yield self.assertFailure(w2.close(), WrongPasswordError)
 
 @inlineCallbacks


I'm not a DD, so i can't upload any fixes, but i would really appreciate
if we can get this fixed before the auto removal strikes.

Regards,

 - Martin
--- magic-wormhole-0.12.0/src/wormhole/test/test_wormhole.py	2021-02-05 02:16:21.0 +
+++ magic-wormhole-0.12.0.fix/src/wormhole/test/test_wormhole.py	2023-04-07 14:44:26.792819150 +
@@ -6,6 +6,7 @@
 from twisted.internet import reactor
 from twisted.internet.defer import gatherResults, inlineCallbacks, returnValue
 from twisted.internet.error import ConnectionRefusedError
+from twisted.internet.task import deferLater
 from twisted.trial import unittest
 
 import mock
@@ -505,6 +506,7 @@
 yield self.assertFailure(w1.get_welcome(), WrongPasswordError)  # late
 
 yield self.assertFailure(w1.close(), WrongPasswordError)
+yield deferLater(reactor, 2, lambda: None)
 yield self.assertFailure(w2.close(), WrongPasswordError)
 
 @inlineCallbacks

Bug#1030307: RFS: posixsignalmanager/0.3-2 -- posix signal handling for qt

2023-02-03 Thread Martin Hostettler 
[upstream here]

On Thu, 2 Feb 2023 16:13:41 +0100 Norwid Behrnd  wrote:
> > So long for a library, change the name.

I don't see why library may not have a descriptive name instead of a short
and cryptic one.

And the debian package name follows the name of the library it contains.
Which is by its pkg-config name: PosixSignalManager

Yes, some may find that ugly and long, but it's the libraries name, and
discussions on if that name is good should be held upstream.

I'm not aware of any debian policy the package name might violate.

Also this is a upload to package that recently entered testing but did not
build for various release architectures due to tests build on amd64 centric
assumptions, which should now be fixed. I think it's important to try to
help debian to offer packages on as many architectures as feasable.

> 
> It might be better to rename the package after bookworm became stable.
> 

Given how near we are in the release cycle to the freeze for new packages
to enter testing i agree that **if** the name needs changing it is more
feasable to do that targeting bookworm+1, but i still think that the
name is fine.