Bug#1064491: gdb: symbol lookup error: gdb: undefined symbol: rl_eof_found

[Héctor Orón Martínez]

Hello Natalia,

On Fri, 23 Feb 2024 at 03:36, Natalia Lewandowska
 wrote:

> Dear Maintainer,
>
> When trying to launch gdb I receive the following error message:
>   symbol lookup error: gdb: undefined symbol: rl_eof_found
> and gdb never starts.

Could you share output from the following commands?

 type gdb
 ldd /usr/bin/gdb
 readelf -sW /usr/bin/gdb | grep eof
 readelf -sW /usr/lib/x86_64-linux-gnu/libreadline.so | grep eof

Regards



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1065011: libpam0t64 competes for libpam.so.0 symlink against libpam0g (breaks debootstrap)

[Héctor Orón Martínez]

Source: pam
Version: 1.5.3-4
Severity: serious
Usertags: time-t
Justification: breaks buildd chroot build

Hello,

  When running:

  debootstrap --keyring /usr/share/keyrings/debian-archive-keyring.gpg
--include=apt,fakeroot,ca-certificates --variant=buildd --arch=amd64
--merged-usr sid /srv/buildd/unpack/create-sid-uMJcDm
https://deb.debian.org/debian /usr/share/debootstrap/scripts/sid

  breaks with:

[...]
I: Retrieving libpam0g 1.5.2-9.1+b1
I: Validating libpam0g 1.5.2-9.1+b1
I: Retrieving libpam0t64 1.5.3-4
I: Validating libpam0t64 1.5.3-4
[...]
I: Extracting util-linux...
I: Extracting zlib1g...
E: cannot move /lib/x86_64-linux-gnu/libpam.so.0 as its destination
exists as a symlink

  This breaks buildd chroot creation as well.

  I am keeping this bug with pam, but feel free to re-assign if you
feel this needs to be addressed elsewhere.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1057780: gdb-minimal provides gdb, without providing all the features in gdb

[Héctor Orón Martínez]

Hello Matthias,

El vie, 8 dic 2023, 13:27, Matthias Klose  escribió:

> Package: src:gdb
> Version: 13.2-1
> Severity: serious
> Tags: sid trixie
>
> gdb-minimal provides gdb, without providing all the features in gdb.
> Seen this in the python testsuite, trying to call
>
>gdb '--eval-command=python3 import sys; print(sys.version_info)'
>
> please drop the provides, or maybe it's time to stop building the
> gdb-minimal package.
>

Looking at popcon there are similar installs for gdb as there are for gdb
minimal. This is useful for systems with limited storage. I do not think
dropping it is an option.

https://qa.debian.org/popcon.php?package=gdb

Having gdb-minimal replace gdb with minimal features I think it makes sense
to keep it. Why do you think this is a serious issue?

>

Bug#1055646: gdb: extremely slow response to basic commands

[Héctor Orón Martínez]

Hello tomazzi,

On Sun, 26 Nov 2023 at 19:45, tomazzi  wrote:

> I have found the root cause of this problem:

Thanks very much! This is a very valuable investigation.
I wanted to drop a link to addr2line bug[1], could that be related?

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=29785

> I thought that this BUG should be easy to eliminate - but it turns out
> that there are several serious BUGs in the gdb, and the only way to
> eliminate them is to debug the gdb first ;)

Which several serious bugs? I understand you mean in the upstream GNU
GDB, instead of the Debian GNU GDB package. Are those reported
upstream?

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1056763: gdb: Remove references to obsolete dpkg m32r arch

[Héctor Orón Martínez]

Hi,

> I pondered about this, and should have given more context, but just to
> note that, Linux dropped support for m32r in 4.16, and gcc dropped
> support for it in 12.1, I don't think the glibc support was ever
> upstreamed, so it seems pretty dead at this point, and that was the
> reason I deemed it safe to drop support for it from dpkg.

Applied the change to git tree and this is queued for the upcoming release.

Thanks for your explanation.

-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1056763: gdb: Remove references to obsolete dpkg m32r arch

[Héctor Orón Martínez]

Hello Guillem,

  Thanks for the patch, however, I think we can keep support for this
architecture in the multiarch package, therefore drop the snippet
below from your patch.

diff --git a/debian/rules b/debian/rules
index 27b3f9d0e1b..1c0a55fa447 100755
--- a/debian/rules
+++ b/debian/rules
@@ -190,7 +190,7 @@ MULTIARCH_TARGETS := \
 sparc64-linux-gnu \
 x86_64-linux-gnu \
 x86_64-linux-gnux32 \
-m32r-linux-gnu
+# EOL

 # broken, see https://launchpad.net/bugs/1233185
 #MULTIARCH_TARGETS := all

I have applied your patch to the git tree and this is queued for the
upcoming GDB release. I have added a changelog entry for it.

Thanks for your support.

On Sat, 25 Nov 2023 at 23:45, Guillem Jover  wrote:
>
> Source: gdb
> Source-Version: 13.2-1
> Severity: important
> Tags: patch
>
> Hi!
>
> Support for this arch got removed in dpkg 1.22.0, which means that
> once the host running dak gets its dpkg upgraded to that version it
> might start being unhappy about the unknown architecture.
>
> Attached an untested patch that removes references to this obsolete arch.
>
> Thanks,
> Guillem



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1055646: gdb: extremely slow response to basic commands

[Héctor Orón Martínez]

Hello,

On Wed, 15 Nov 2023 at 23:09, tomazzi  wrote:

> To do this, I need to have a complete build log with all the
> compiler/linker flags, compiler warnings, etc.

Find logs at https://buildd.debian.org/status/logs.php?pkg=gdb=amd64

> Unfortunately, the methods described on the official Debian Wiki page
> does not allow to build gdb from source package -> "debuild" fails to
> produce the binary shipped by Debian. (I would say that this deserves a
> separate BUG report).

I am unsure about that, usually you can build using dpkg-buildpackage.

> Now, the "hacked" gdb is also different - so the first step is to find
> differences in the build process, like the exact list of features
> enabled/disabled.
>
> So, can You please explain how did You build the gdb?

Build daemons build it, see logs posted previously. Build daemons use sbuild.


-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1055646: gdb: extremely slow response to basic commands

[Héctor Orón Martínez]

Hello Tomazzi,

On Mon, 13 Nov 2023 at 21:51, tomazzi  wrote:
>
> Hello,
>
> I've just built gdb "the Debian way", to check what are the differences
> in the build process:
> $> apt source gdb
> $> apt build-dep gdb
> $> debuild -b -uc -us
>
>  From debuild output:
>
> gdb-default: configured with:
> ...
>   --without-babeltrace
>   --with-babeltrace
> ...
> gdb-minimal: configured with:
> ...
>   --without-babeltrace
>   --with-babeltrace
>   --without-babeltrace
> ...
>
> This looks bad, but the results are even more "interresting":

Latest switch is the one that should be in-use

> The gdb binary installed in the system (**debsums OK**) reports the
> following configuration (the "show configuration" command, differences
> only):
>
> ...
>   --with-babeltrace
>   --with-mpfr
>   --with-xxhash
>   --with-python=/usr (relocatable)
>   --with-python-libdir=/usr/lib (relocatable)
>   --enable-source-highlight
> ...
>
> The newly "debuild" gdb reports something *different*:
> ...
>   --without-babeltrace  << this: conflicting build flags
>   --without-mpfr
>   --with-xxhash
>   --without-python
>   --without-python-libdir
>   --disable-source-highlight
> ...
>
>
> The gdb which I've compiled using ./configure script (so *without*
> Debian patches) reports:
> ...
>   --with-babeltrace
>   --with-mpfr
>   --without-xxhash  << this: libxxhash-dev is installed, but
> flag is disabled ?
>   --with-python=/usr
>   --with-python-libdir=/usr/lib
>   --disable-source-highlight << this
> ...
>

Could you share your conclusion or a patch? I quite do not understand
what you are trying to say with all those examples.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1043221: RFS: xutils-dev/1:7.7+7 [Team] -- X Window System utility programs for development

[Héctor Orón Martínez]

Hello,

  Based on your package and Manuel changes I pushed the following to Git...
  
https://salsa.debian.org/xorg-team/app/xutils-dev/-/commit/64b07596fbc43441cf555d9e4eeb8f2e35312967

  I want to check other bugs in the BTS before following up with an
upload to unstable.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1041377: [patch] freerdp2: FTBFS with ffmpeg 6.0

[Héctor Orón Martínez]

Dear maintainer,

  I have uploaded this package to delayed/2 queue.

Regards

On Fri, 4 Aug 2023 at 11:51, Héctor Orón Martínez  wrote:
>
> Hello,
>
>   I have prepared a new package with a backported upstream fix for this issue.
>
>   This is submitted in salsa as:
>   https://salsa.debian.org/debian-remote-team/freerdp2/-/merge_requests/11
>
>   Find this patch attached here for completion.
>
> Regards
> --
>  Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1041377: [patch] freerdp2: FTBFS with ffmpeg 6.0

[Héctor Orón Martínez]

Hello,

  I have prepared a new package with a backported upstream fix for this issue.

  This is submitted in salsa as:
  https://salsa.debian.org/debian-remote-team/freerdp2/-/merge_requests/11

  Find this patch attached here for completion.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.
From 52a4aa3edd5980d257cb3bc61a38ba951033d479 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?H=C3=A9ctor=20Or=C3=B3n=20Mart=C3=ADnez?= 
Date: Fri, 4 Aug 2023 04:08:27 -0400
Subject: [PATCH] include upstream fix for FTBFS with FFmpeg 6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Fixes DebianBug #1041377

Signed-off-by: Héctor Orón Martínez 
---
 debian/changelog|  9 ++
 debian/patches/0001_fix_ftbfs_1041377.patch | 32 +
 debian/patches/series   |  1 +
 3 files changed, 42 insertions(+)
 create mode 100644 debian/patches/0001_fix_ftbfs_1041377.patch
 create mode 100644 debian/patches/series

diff --git a/debian/changelog b/debian/changelog
index 02eb10a..81b6158 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+freerdp2 (2.10.0+dfsg1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/0001_fix_ftbfs_1041377.patch:
+- include upstream fix for FTBFS with FFmpeg 6.0
+  (Closes: #1041377)
+
+ -- Héctor Orón Martínez   Fri, 04 Aug 2023 04:08:40 -0400
+
 freerdp2 (2.10.0+dfsg1-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/patches/0001_fix_ftbfs_1041377.patch b/debian/patches/0001_fix_ftbfs_1041377.patch
new file mode 100644
index 000..14d6536
--- /dev/null
+++ b/debian/patches/0001_fix_ftbfs_1041377.patch
@@ -0,0 +1,32 @@
+diff --git a/channels/tsmf/client/ffmpeg/tsmf_ffmpeg.c b/channels/tsmf/client/ffmpeg/tsmf_ffmpeg.c
+index c14877b43ac1..215337464386 100644
+--- a/channels/tsmf/client/ffmpeg/tsmf_ffmpeg.c
 b/channels/tsmf/client/ffmpeg/tsmf_ffmpeg.c
+@@ -235,8 +235,10 @@ static BOOL tsmf_ffmpeg_init_stream(ITSMFDecoder* decoder, const TS_AM_MEDIA_TYP
+ 		}
+ 	}
+ 
++#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(59, 18, 100)
+ 	if (mdecoder->codec->capabilities & AV_CODEC_CAP_TRUNCATED)
+ 		mdecoder->codec_context->flags |= AV_CODEC_FLAG_TRUNCATED;
++#endif
+ 
+ 	return TRUE;
+ }
+diff --git a/libfreerdp/codec/h264_ffmpeg.c b/libfreerdp/codec/h264_ffmpeg.c
+index 4e3ba8f9282f..9c445b8253ae 100644
+--- a/libfreerdp/codec/h264_ffmpeg.c
 b/libfreerdp/codec/h264_ffmpeg.c
+@@ -529,10 +529,12 @@ static BOOL libavcodec_init(H264_CONTEXT* h264)
+ 			goto EXCEPTION;
+ 		}
+ 
++#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(59, 18, 100)
+ 		if (sys->codecDecoder->capabilities & AV_CODEC_CAP_TRUNCATED)
+ 		{
+ 			sys->codecDecoderContext->flags |= AV_CODEC_FLAG_TRUNCATED;
+ 		}
++#endif
+ 
+ #ifdef WITH_VAAPI
+ 
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..1337965
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+0001_fix_ftbfs_1041377.patch
-- 
2.40.1

Bug#1040205: libclang-16-dev: ships broken symlinks (/usr/lib/llvm-16/lib/libclang.so -> ../../x86_64-linux-gnu/libclang-16.so.16)

[Héctor Orón Martínez]

Package: libclang-16-dev
Version: 1:16.0.6-3
Severity: normal
X-Debbugs-Cc: zu...@debian.org


Hello,

  When calling:
  python3 -c 'from ctypes import *; import clang.cindex; config =
clang.cindex.Config(); verfunc = config.lib.clang_getClangVersi
on;
verfunc.restype = c_char_p ; print(verfunc())'

  is unable to load libclang-16.so...
  clang.cindex.LibclangError: libclang-16.so: cannot open shared
object file: No such file or directory. To provide a path to libclang
use Config.set_library_path() or Config.set_library_file().

  this turns out to be broken naming for shared object libraries:
  # ls -l /usr/lib/llvm-16/lib/libclang.so /usr/lib/llvm-16/lib/libclang-16.so
lrwxrwxrwx 1 root root 40 Jun 27 06:58
/usr/lib/llvm-16/lib/libclang-16.so ->
../../x86_64-linux-gnu/libclang-16.so.16
lrwxrwxrwx 1 root root 40 Jun 27 06:58
/usr/lib/llvm-16/lib/libclang.so ->
../../x86_64-linux-gnu/libclang-16.so.16

  However the provided libraries are versioned 16.so.1:
  # dpkg -L libclang1-16 | grep so
/usr/lib/x86_64-linux-gnu/libclang-16.so.16.0.6
/usr/lib/llvm-16/lib/libclang-16.so.1
/usr/lib/llvm-16/lib/libclang.so.1
/usr/lib/x86_64-linux-gnu/libclang-16.so.1

  Please fix symlinks on development package.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1037031: gdb: std::length_error with tab-completion on Meson-built Rust program

[Héctor Orón Martínez]

found -1 13.2-1

Hello,

  I have been working on creating the gdb-13.2 package, however, I was
able to reproduce this issue.

Regars

Bug#990016: Debian installer images missing ASpeed video driver

[Héctor Orón Martínez]

Hello Salvatore,

On Sat, 11 Mar 2023 at 08:19, Salvatore Bonaccorso  wrote:

> >   I have opened an MR in salsa:
> >   https://salsa.debian.org/kernel-team/linux/-/merge_requests/676

> I assume you were able to test it accordingly it works as expected?
>
> Looks fine IMHO, but wanted to double-check with you.

I have not been able to test it since I (yet) do not have Power
hardware available. However the reporter is willing to test it, I was
hoping after it gets released.
The change only affects Power, so I believe this should be easy to
revert if that causes any issues.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#990016: Debian installer images missing ASpeed video driver

[Héctor Orón Martínez]

Hello,

  I have opened an MR in salsa:
  https://salsa.debian.org/kernel-team/linux/-/merge_requests/676

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1031004: gdb should be able to run without python support when not available

[Héctor Orón Martínez]

Hello,

On Fri, 10 Feb 2023 at 11:51, Vincent Lefevre  wrote:
>
> Package: gdb
> Version: 13.0.91.20230210-0.1
> Severity: normal
>
> When python is not available, e.g. in firejail with some profiles
> (for security reasons), gdb refuses to run:

Could you use gdb-minimal instead?

Regards

Bug#1030893:

[Héctor Orón Martínez]

Hello,

On Fri, 10 Feb 2023 at 05:18, Matthias Klose  wrote:
>
>  > I am unsure why you are uploading gdb snapshots for Debian bookworm.

[...]

> It's not a snapshot, it's a release candidate, allowing to read zstd 
> compressed
> debug sections and ctf information.  Users may expect in a Debian release a 
> gdb
> which can understand what is shipped with the distro.

Thanks for this rationale and follow up.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1030893: gdb FTBFS

[Héctor Orón Martínez]

Hello Matthias,

  I am unsure why you are uploading gdb snapshots for Debian bookworm.
  In anycase, could you look at this failure, you may need to generate
a DFSG tarball without the GFDL documentation.

Regards

On Wed, 8 Feb 2023 at 21:18, Adrian Bunk  wrote:
>
> Source: gdb
> Version: 13.0.91-0.1
> Severity: serious
> Tags: ftbfs
>
> https://buildd.debian.org/status/logs.php?pkg=gdb=13.0.91-0.1
>
> ...
> make[5]: Entering directory '/<>/build/default/gdb/doc'
> (test "ln -s" = "ln -s" && \
>   ln -s /<>/gdb/doc/all-cfg.texi gdb-cfg.texi) || \
> ln /<>/gdb/doc/all-cfg.texi gdb-cfg.texi || \
> cp /<>/gdb/doc/all-cfg.texi gdb-cfg.texi
> makeinfo --split-size=500 --split-size=500  -DHAVE_MAKEINFO_CLICK  -I 
> /<>/gdb/doc/../mi -I /<>/gdb/doc \
> -o gdb.info /<>/gdb/doc/gdb.texinfo
> makeinfo --split-size=500 --split-size=500  -DHAVE_MAKEINFO_CLICK -I 
> /<>/gdb/doc -o stabs.info /<>/gdb/doc/stabs.texinfo
> makeinfo --split-size=500 --split-size=500  -DHAVE_MAKEINFO_CLICK -I 
> /<>/gdb/doc -o annotate.info 
> /<>/gdb/doc/annotate.texinfo
> gdb.texinfo:39177: @include: could not find rluser.texi
> gdb.texinfo:39178: @include: could not find hsuser.texi
> gdb.texinfo:26429: @xref reference to nonexistent node `Command Line Editing'
> gdb.texinfo:26461: @xref reference to nonexistent node `Using History 
> Interactively'
> gdb.texinfo:26557: @xref reference to nonexistent node `Event Designators'
> gdb.texinfo:29361: @pxref reference to nonexistent node `Command Line Editing'
> gdb.texinfo:172: @menu reference to nonexistent node `Command Line Editing'
> gdb.texinfo:173: @menu reference to nonexistent node `Using History 
> Interactively'
> make[5]: *** [Makefile:491: gdb.info] Error 1



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1030104: b4: Please add debian/watch file

[Héctor Orón Martínez]

Hello Nicolas,

   Thanks very! I'll add the file on the next upload, but so close to
freeze I am not sure if this will make it for bookworm, we'll see.

Regards

On Tue, 31 Jan 2023 at 07:42, Nicolas Schier  wrote:
>
> Package: b4
> Version: 0.9.0-1
> Severity: wishlist
>
> Dear Héctor,
>
> can you please add a debian/watch file to allow use of uscan and
> friends?
>
> I am attaching a patch that works for me and adds debian/watch and
> upstream author's gpg key.
>
> Thanks and kind regards,
> Nicolas
>
>
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
> 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
> 'oldstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.0.0-5-amd64 (SMP w/6 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
> to C.UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages b4 depends on:
> ii  python33.11.1-1
> ii  python3-dkim   1.0.5-2
> ii  python3-dnspython  2.2.1-2
> ii  python3-patatt 0.6.2-1
> ii  python3-requests   2.28.1+dfsg-1
>
> b4 recommends no packages.
>
> b4 suggests no packages.
>
> -- no debconf information



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#1029230: gdb: None of the gdb pretty printers are working

[Héctor Orón Martínez]

Hello BogDan,

  Could you please share a reproducible test with error output?

Regards

On Fri, 20 Jan 2023 at 07:39, BogDan Vatra  wrote:
>
> Package: gdb
> Version: 13.0.90.20230114-0.1
> Severity: important
> X-Debbugs-Cc: bog...@kde.org
>
> Dear Maintainer,
>
> Since python3 upgrade, none of the gdb pretty printers are working (e.g.
> std::*).
>
>
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 6.1.0-1-amd64 (SMP w/32 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages gdb depends on:
> ii  libbabeltrace1  1.5.11-1+b1
> ii  libc6   2.36-8
> ii  libdebuginfod1  0.188-2.1
> ii  libexpat1   2.5.0-1
> ii  libgcc-s1   12.2.0-14
> ii  libgmp102:6.2.1+dfsg1-1.1
> ii  libipt2 2.0.5-1
> ii  liblzma55.4.1-0.0
> ii  libmpfr64.2.0-1
> ii  libncursesw66.4-1
> ii  libpython3.11   3.11.1-2
> ii  libreadline88.2-1.3
> ii  libsource-highlight4v5  3.1.9-4.2+b2
> ii  libstdc++6  12.2.0-14
> ii  libtinfo6   6.4-1
> ii  libxxhash0  0.8.1-1
> ii  libzstd11.5.2+dfsg2-3
> ii  zlib1g  1:1.2.13.dfsg-1
>
> Versions of packages gdb recommends:
> ii  libc6-dbg [libc-dbg]  2.36-8
>
> Versions of packages gdb suggests:
> pn  gdb-doc
> ii  gdbserver  13.0.90.20230114-0.1
>
> -- no debconf information



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#913655: grub-pc: id caching in postinst does not work

[Héctor Orón Martínez]

Hello,

  Please find below an update from previous patch suggested

--- postinst2021-10-06 17:16:32.966812000 -0400
+++ postinst.913655.patched   2021-10-27 09:03:25.32434 -0400
@@ -73,7 +73,6 @@
 # This only works on a Linux system with udev running.  This is probably the
 # vast majority of systems where we need any of this, though, and we fall
 # back reasonably gracefully if we don't have it.
-cached_available_ids=
 available_ids()
 {
   local id path
@@ -84,19 +83,25 @@
   fi   [ -d /dev/disk/by-id ] || return
-  cached_available_ids="$(
-for path in /dev/disk/by-id/*; do
-  [ -e "$path" ] || continue
-  printf '%s %s\n' "$path" "$(readlink -f "$path")"
-done | sort -k2 -s -u | cut -d' ' -f1
-  )"
-  echo "$cached_available_ids"
+  for path in /dev/disk/by-id/*; do
+[ -e "$path" ] || continue
+printf '%s %s\n' "$path" "$(readlink -f "$path")"
+  done | sort -k2 -s -u | cut -d' ' -f1
 }
+cached_available_ids=$(available_ids) # Returns non-zero and no
output if no mapping can be found.
 device_to_id()
 {
   local id
+  # If it's already in /dev/disk/by-id, skip the expensive loop
+  # Using case to support glob matching with /bin/sh compatibility
+  case "$1" in
+/dev/disk/by-id/*)
+  echo "$1"
+  return 0
+  ;;
+  esac
   for id in $(available_ids); do
 if [ "$(readlink -f "$id")" = "$(readlink -f "$1")" ]; then
   echo "$id"

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#981033: segfault in dtc -I fs

[Héctor Orón Martínez]

Hello Cyril,

On Wed, 27 Jan 2021 at 09:31, Cyril Brulebois  wrote:

> I'm happy to look into preparing a fix for this bug in stable, and to
> talk to the release team about it.

Please, do not block on me, if you want to do that please go ahead.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#981033: segfault in dtc -I fs

[Héctor Orón Martínez]

Hello,

El dl., 25 de gen. 2021, 18:15, Uwe Kleine-König  va
escriure:

> Package: device-tree-compiler
> Version: 1.4.7-3
> Severity: important
> Tags: upstream, fixed-upstream
> Control: fixed -1 1.5.0-1
>
> Hello,
>

Since 1.6.0 is available via backports and this issue only happens in
stable, is this a common operation that must be fixed in stable?


[...]
> Segmentation fault (core dumped)
>
> The problem was introduced by upstream commit
> 32b9c61307629ac76c6ac0bead6f926d579b3d2c. So v1.4.7 is first release that
> is affected by this bug.
>
> It was fixed upstream by commit
> 9619c8619c37b9aea98100bcc15c51a5642e877e and so v1.5.0 is the first
> fixed commit.
>

Thanks

>

Bug#968219: ITP: openpbs -- An HPC workload manager and job scheduler for desktops, clusters, and clouds.

[Héctor Orón Martínez]

Hello,

El dt., 11 d’ag. 2020, 5:33, Mo Zhou  va escriure:

> Package: wnpp
> Severity: wishlist
> Owner: Mo Zhou 
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: openpbs
>   Version : 20.0.1
>   Upstream Author : Name 
> * URL : http://www.example.org/


It looks like URL needs to be fixed.


> * License : AGPL-3
>   Programming Lang: C, python, shell
>   Description : An HPC workload manager and job scheduler for
> desktops, clusters, and clouds.
>
>
> I'm wondering why it is absent in debian.
>
>

Bug#953165: gdb-doc: Please update the gnu.org URLs to https

[Héctor Orón Martínez]

Hello Vincent,

Missatge de Vincent Lefevre  del dia dj., 5 de
març 2020 a les 14:09:
>
> Package: gdb-doc
> Version: 9.1-1
> Severity: minor
>
> In the package information:
>
>   Homepage: http://www.gnu.org/s/gdb/
>
> The URL should be updated to https: https://www.gnu.org/software/gdb/
>
> /usr/share/doc/gdb-doc/copyright also uses old http URLs:
>   http://www.gnu.org/licenses/
>   http://www.gnu.org/copyleft/

Thanks for the report, I have added the suggested changes to git, so
they'll ship in the upcoming release.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#936055: t/unthreaded.t test failing

[Héctor Orón Martínez]

Source: libapp-stacktrace-perl
Version: 0.09-3
Followup-For: Bug #936055

Dear Maintainer,

  This issue is now affecting GDB 9.1 autopkgtests and preventing it from 
migrating to testing.
  
https://ci.debian.net/data/autopkgtest/testing/amd64/liba/libapp-stacktrace-perl/4328197/log.gz
  
https://ci.debian.net/data/autopkgtest/testing/arm64/liba/libapp-stacktrace-perl/4314744/log.gz

Regards

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

Kernel: Linux 5.3.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#945255: gdb: package is lacking a man page

[Héctor Orón Martínez]

tags -1 wontfix
thank

Hello Andrew,

Missatge de Andrew Apted  del dia dv., 22 de nov.
2019 a les 3:21:
>
> Package: gdb
> Version: 8.2.1-2+b3
> Severity: normal
>
> Dear Maintainer,
>
> Section 12.1 of Debian Policy states: Each program, utility, and function
> should have an associated manual page included in the same package.
>
> The package "gdb" is in violation of that policy since the man page is
> not in the same package, but in the gdb-doc package.  I expect man pages
> for programs to be available without needing to install additional
> packages.

GNU GDB manpage lives in "src:gdb-doc" package, which is in
"non-free", since GFDL is considered a non-free license by the DFSG.

Regards

Bug#923377: zfsutils-linux: fails to upgrade

[Héctor Orón Martínez]

Package: zfsutils-linux
Version: 0.8.2-2
Followup-For: Bug #923377

Dear Maintainer,

  When upgrading zfsutils-linux, systemd tries to restart
  zfs-mount.service, that fails because there's nothing to mount and
  makes the install fail. Do you think ignoring the return code for
  zfs-mount.service could be sane approach to fix this issue?


   || Setting up zfsutils-linux (0.8.2-2) ...
   || Job for zfs-import-cache.service failed because the control process 
exited with error code.
   || See "systemctl status zfs-import-cache.service" and "journalctl -xe" for 
details.
   || zfs-import-cache.service couldn't restart.
   || zfs-import-scan.service is a disabled or a static unit not running, not 
starting it.
   || Job for zfs-mount.service failed because the control process exited with 
error code.
   || See "systemctl status zfs-mount.service" and "journalctl -xe" for details.
   || invoke-rc.d: initscript zfs-mount, action "restart" failed.
   || * zfs-mount.service - Mount ZFS filesystems
   ||Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor 
preset: enabled)
   ||Active: failed (Result: exit-code) since Wed 2019-11-06 00:55:20 EST; 
4ms ago
   ||  Docs: man:zfs(8)
   ||   Process: 19846 ExecStart=/sbin/zfs mount -a (code=exited, 
status=1/FAILURE)
   ||  Main PID: 19846 (code=exited, status=1/FAILURE)
   || 
   || Nov 06 00:55:20 zfs-host2 systemd[1]: Starting Mount ZFS filesystems...
   || Nov 06 00:55:20 zfs-host2 zfs[19846]: The ZFS modules are not loaded.
   || Nov 06 00:55:20 zfs-host2 zfs[19846]: Try running '/sbin/modprobe zfs' as 
root t…hem.
   || Nov 06 00:55:20 zfs-host2 systemd[1]: zfs-mount.service: Main process 
exited, co…LURE
   || Nov 06 00:55:20 zfs-host2 systemd[1]: zfs-mount.service: Failed with 
result 'exi…de'.
   || Nov 06 00:55:20 zfs-host2 systemd[1]: Failed to start Mount ZFS 
filesystems.
   || Hint: Some lines were ellipsized, use -l to show in full.
   || dpkg: error processing package zfsutils-linux (--configure):
   ||  subprocess installed post-installation script returned error exit status 
1
   || dpkg: dependency problems prevent configuration of zfs-initramfs:
   ||  zfs-initramfs depends on zfsutils-linux (>= 0.8.2-2); however:
   ||   Package zfsutils-linux is not configured yet.
   || 
   || dpkg: error processing package zfs-initramfs (--configure):
   ||  dependency problems - leaving unconfigured
   || Processing triggers for man-db (2.7.6.1-2) ...
   || Setting up python3-ply (3.9-1) ...
   || dpkg: dependency problems prevent configuration of python3-pyzfs:
   ||  python3-pyzfs depends on zfsutils-linux (= 0.8.2-2); however:
   ||   Package zfsutils-linux is not configured yet.
   || 
   || dpkg: error processing package python3-pyzfs (--configure):
   ||  dependency problems - leaving unconfigured
   || Setting up python3-pycparser (2.17-2) ...
   || Setting up python3-cffi (1.9.1-2) ...
   || Errors were encountered while processing:
   ||  zfsutils-linux
   ||  zfs-initramfs
   ||  python3-pyzfs
   || E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#942437: grpc: Consider new upstream release (1.24.2)

[Héctor Orón Martínez]

Hello,

Missatge de Héctor Orón Martínez  del dia dv.,
18 d’oct. 2019 a les 17:23:

> > > >  Did you try to build it with the current protobuf version available
> > > > in experimental?
> > >
> > > Not really, I need the package for stretch, which involves a bit of
> > > backporting stuff, I'll try that tomorrow.
> >  Tested and unfortunately it doesn't compile. There's no sense to
> > merge your work, sorry.
> > But it seems to be good for your backporting efforts (compiles with
> > older protobuf version).
>
> Actually, not entirely sure why, the package does not have third-party
> upb, so the build (on stretch) fails with:
>
> [  243s] mkdir -p `dirname
> /usr/src/packages/BUILD/objs/opt/src/core/lib/security/credentials/alts/alts_credentials.o`
> [  243s] c++ -Ithird_party/googletest/googletest/include
> -Ithird_party/googletest/googlemock/include
> -Ithird_party/address_sorting/include -Wdate-time -D_FORTIFY_SOURCE=2
> -g -Wall -Wextra -DOSATOMIC_USE_INLINED=1 -Ithird_party/upb
> -Isrc/core/ext/upb-generated -O2 -Wframe-larger-than=16384 -fPIC -I.
> -Iinclude -I/usr/src/packages/BUILD/gens -DNDEBUG
> -DINSTALL_PREFIX=\"/usr\" -DGRPC_HAVE_PERFTOOLS   -g -O2
> -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong
> -Wformat -Werror=format-security -std=c++11   -fno-rtti
> -fno-exceptions -MMD -MF
> /usr/src/packages/BUILD/objs/opt/src/core/lib/security/credentials/alts/alts_credentials.dep
> -c -o 
> /usr/src/packages/BUILD/objs/opt/src/core/lib/security/credentials/alts/alts_credentials.o
> src/core/lib/security/credentials/alts/alts_credentials.cc
> [  243s] In file included from
> ./src/core/tsi/alts/handshaker/transport_security_common_api.h:29:0,
> [  243s]  from
> ./src/core/lib/security/credentials/alts/grpc_alts_credentials_options.h:26,
> [  243s]  from
> ./src/core/lib/security/credentials/alts/alts_credentials.h:26,
> [  243s]  from
> src/core/lib/security/credentials/alts/alts_credentials.cc:21:
> [  243s] 
> src/core/ext/upb-generated/src/proto/grpc/gcp/transport_security_common.upb.h:12:32:
> fatal error: upb/generated_util.h: No such file or directory
> [  243s]  #include "upb/generated_util.h"
> [  243s] ^
> [  243s] compilation terminated.

I have added upb third party libs into my source package and using
protobuf on stretch (3.6 series) failed to build, since some struct
was missing a field that got introduced in 3.7 series, finally I got
it built backporting 3.9 protobuf

> > > >  I've already packaged it myself. Why I didn't and can't push it to
> > > > Salsa is that it needs two source tarballs now. Do you know how to
> > > > handle this with gbp?
> > > > gbp import-orig works with only one source as I've seen.
> > >
> > > Have a look to 
> > > https://git.sigxcpu.org/cgit/git-buildpackage/commit/?id=f9ded2f342e8b22171cbadb3d7e55830eff21823
> > > hopefully that gives you a better clue.
> >  A quick test showed that --component works fine. Going to update the
> > packaging on next Tuesday when I get back home.

Once you get a source package ready for 1.24.2, let me know and I'll
run a build.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#942437: grpc: Consider new upstream release (1.24.2)

[Héctor Orón Martínez]

Hello,

Missatge de László Böszörményi (GCS)  del dia dj., 17
d’oct. 2019 a les 8:32:
> On Wed, Oct 16, 2019 at 6:23 PM Hector Oron  wrote:
> > Missatge de László Böszörményi (GCS)  del dia dc., 16
> > d’oct. 2019 a les 17:34:
> > > On Wed, Oct 16, 2019 at 12:24 PM Héctor Orón Martínez  
> > > wrote:
> > > >   Please, could you please review the changes and either accept them or
> > > >   comment on further changes.
> > >  Did you try to build it with the current protobuf version available
> > > in experimental?
> >
> > Not really, I need the package for stretch, which involves a bit of
> > backporting stuff, I'll try that tomorrow.
>  Tested and unfortunately it doesn't compile. There's no sense to
> merge your work, sorry.
> But it seems to be good for your backporting efforts (compiles with
> older protobuf version).

Actually, not entirely sure why, the package does not have third-party
upb, so the build (on stretch) fails with:

[  243s] mkdir -p `dirname
/usr/src/packages/BUILD/objs/opt/src/core/lib/security/credentials/alts/alts_credentials.o`
[  243s] c++ -Ithird_party/googletest/googletest/include
-Ithird_party/googletest/googlemock/include
-Ithird_party/address_sorting/include -Wdate-time -D_FORTIFY_SOURCE=2
-g -Wall -Wextra -DOSATOMIC_USE_INLINED=1 -Ithird_party/upb
-Isrc/core/ext/upb-generated -O2 -Wframe-larger-than=16384 -fPIC -I.
-Iinclude -I/usr/src/packages/BUILD/gens -DNDEBUG
-DINSTALL_PREFIX=\"/usr\" -DGRPC_HAVE_PERFTOOLS   -g -O2
-fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong
-Wformat -Werror=format-security -std=c++11   -fno-rtti
-fno-exceptions -MMD -MF
/usr/src/packages/BUILD/objs/opt/src/core/lib/security/credentials/alts/alts_credentials.dep
-c -o 
/usr/src/packages/BUILD/objs/opt/src/core/lib/security/credentials/alts/alts_credentials.o
src/core/lib/security/credentials/alts/alts_credentials.cc
[  243s] In file included from
./src/core/tsi/alts/handshaker/transport_security_common_api.h:29:0,
[  243s]  from
./src/core/lib/security/credentials/alts/grpc_alts_credentials_options.h:26,
[  243s]  from
./src/core/lib/security/credentials/alts/alts_credentials.h:26,
[  243s]  from
src/core/lib/security/credentials/alts/alts_credentials.cc:21:
[  243s] 
src/core/ext/upb-generated/src/proto/grpc/gcp/transport_security_common.upb.h:12:32:
fatal error: upb/generated_util.h: No such file or directory
[  243s]  #include "upb/generated_util.h"
[  243s] ^
[  243s] compilation terminated.


> > >  I've already packaged it myself. Why I didn't and can't push it to
> > > Salsa is that it needs two source tarballs now. Do you know how to
> > > handle this with gbp?
> > > gbp import-orig works with only one source as I've seen.
> >
> > Have a look to 
> > https://git.sigxcpu.org/cgit/git-buildpackage/commit/?id=f9ded2f342e8b22171cbadb3d7e55830eff21823
> > hopefully that gives you a better clue.
>  A quick test showed that --component works fine. Going to update the
> packaging on next Tuesday when I get back home.

Sounds excellent! I'll test it.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#942437: grpc: Consider new upstream release (1.24.2)

[Héctor Orón Martínez]

Source: grpc
Version: 1.23.0
Severity: wishlist

Dear Maintainer,

  I have prepared a new release for 1.24.2-1, I have submitted changes
  via MR into salsa, as:
https://salsa.debian.org/debian/grpc/merge_requests/1
https://salsa.debian.org/debian/grpc/merge_requests/2

  Please, could you please review the changes and either accept them or
  comment on further changes.

  Note the package might need further clean-ups, so distribution is set to
  UNRELEASED.

Regards

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#940141: RM: ofono-phonesim -- RoQA; Depends on qt4, dead upstream

[Héctor Orón Martínez]

Hello,

  Yes, please, remove the package.

Missatge de Moritz Muehlenhoff  del dia dj., 12 de
set. 2019 a les 23:57:
>
> Package: ftp.debian.org
> Severity: normal
>
> Please remove ofono-phonesim. It depends on Qt4 and is dead upstream
> zumbi acked the removal in #875066
>
> Cheers,
> Moritz



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#875066: [ofono-phonesim] Future Qt4 removal from Buster

[Héctor Orón Martínez]

Hello,

Missatge de Moritz Mühlenhoff  del dia dj., 12 de set.
2019 a les 22:30:

> Are you planning to port it to Qt5 yourself or shall we remove it from
> the archive?

Let's remove it from the archive.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#939737: emacs: please package newer release 26.3

[Héctor Orón Martínez]

Hello Rob,

Missatge de Rob Browning  del dia dl., 9 de set.
2019 a les 0:52:
> "Héctor Orón Martínez"  writes:

> > Package: emacs
> > Version: 1:26.1+1-3.3
> > Severity: wishlist
> >
> > Dear Maintainer,
> >
> >   Please consider packaging newer emacs 26.3 release:
> > https://lists.gnu.org/archive/html/emacs-devel/2019-08/msg00577.html

> It's in progress, but right now I'm working on the EPLA cert epiration
> problem for buster and sid, then I'll resume 26.3.

Thanks very much for packaging emacs! However I tried to look at the
Git repository at:
  https://salsa.debian.org/rlb/deb-emacs

I wanted to submit a MR for new upstream release, could you please
explain which is debian packaging branch for new releases and how to
handle upstream source?

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#939737: emacs: please package newer release 26.3

[Héctor Orón Martínez]

Package: emacs
Version: 1:26.1+1-3.3
Severity: wishlist

Dear Maintainer,

  Please consider packaging newer emacs 26.3 release:
https://lists.gnu.org/archive/html/emacs-devel/2019-08/msg00577.html

Regards

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emacs depends on:
ii  emacs-gtk  1:26.1+1-3.3

emacs recommends no packages.

emacs suggests no packages.

-- no debconf information

Bug#935337: RM: pillow -- NVIU; duplicated source packages in unstable

[Héctor Orón Martínez]

Package: ftp.debian.org
Severity: normal

Hello,

I noticed src:pillow 4.3.0-2 and 6.1.0-1 in unstable.

At #debian-python:

< zumbi> there is src:pillow 4.3.0-2 and 6.1.0-1 in unstable, does some know if
   that's intentional? (to keep python-imaging?)
< zumbi> (/cc doko ^)
< doko> zumbi: no, probably should be removed


Please remove src:pillow 4.3.0-2 along it's binaries, including python-imaging.

@doko, could you please confirm?

Regards

Bug#932892: libwayland-server0: wayland crashes when I (un)plug a monitor

[Héctor Orón Martínez]

Hello,

Missatge de Rémi Letot  del dia dc., 24 de jul.
2019 a les 12:48:
>
> Package: libwayland-server0
> Version: 1.17.0-1
> Severity: normal
>
> Dear Maintainer,
>
> when I plug or unplug a monitor, my desktop session crashes
> and I'm back at the gdm login screen. If I do the same when
> at the gdm login screen, it disappears and doesn't come back.
> Then I have to restart the pc.
>
> I have errors in syslog:
>
> gnome-shell[4078]: segfault at ?? ip  sp  error 4 in 
> libwayland-server.so.0.1.0[?+7000]
>
> I have several errors since I tried multiple combinations,
> so I replaced the non constant parts of the error with ??.
>
> There are probably things that I can do to have better error
> messages, but you'll have to guide me :-)
>
> I'm now using gnome on Xorg, which doesn't crash, so the
> problem is with wayland.

Thanks for the report! We need more information to really know what's
going on. Which monitor are you using? which kind of hardware port are
you using for the connection? which graphics card are you using and
which driver? Can you report which gnome-shell version are you using?

I am currently on a laptop, but next time I get closer to a desktop
I'll try to reproduce it.

Do I understand correctly that the reproducer is unplug monitor cable
from PC and plug it again?

> Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
> LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages libwayland-server0 depends on:
> ii  libc62.28-10
> ii  libffi6  3.2.1-9
>
> libwayland-server0 recommends no packages.
>
> libwayland-server0 suggests no packages.
>
> -- no debconf information



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#807383: gcc-doc: Manpage documentation of -l is incorrect

[Héctor Orón Martínez]

Hello,

Missatge de Kai-Uwe Eckhardt  del dia dj., 25 de
jul. 2019 a les 10:48:
>
> Hello,
>
> the manual text has been fixed upstream for gcc-9.1.0.
> https://gcc.gnu.org/onlinedocs/gcc-9.1.0/gcc/Link-Options.html#Link-Options
>
>
> The linker searches a standard list of directories for the library. The
> directories searched include several standard system directories plus
> any that you specify with -L.
>
> Static libraries are archives of object files, and have file names like
> liblibrary.a. Some targets also support shared libraries, which
> typically have names like liblibrary.so. If both static and shared
> libraries are found, the linker gives preference to linking with the
> shared library unless the -static option is used.
>

Thanks for the report, however I feel reluctant to patch gdb-doc
documentation since GFDL is considered non-free by Debian.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#933174: wayland: Brightness bar not displayed when adjusting screen brightness

[Héctor Orón Martínez]

Hello,

Missatge de Conrad J.C. Hughes (for Debian package stuff)
 del dia ds., 27 de jul. 2019 a les 11:09:
>
> Source: wayland
> Severity: normal
>
> Dear Maintainer,
>
> When I operate my laptop's screen brightness buttons, an overlay appears,
> usually with a bar showing the current level.  Since upgrading to
> buster+wayland, the overlay appears, but the bar doesn't: it's always blank.

Which laptop is that? On a Dell XPS13 I get the bar displayed.
This issue might be unrelated to wayland itself.

> Just noticed that this is *not* the case prior to login; I assume that the gdm
> greeter doesn't use wayland?

gdm greeter uses wayland

Regards

Bug#933756: ITS: conman

[Héctor Orón Martínez]

Package: conman
Version: 0.2.7-1
Severity: important

Dear Maintainer,

  I intend to salvage package conman, which has note been updated since 2015, 
first upload, despite BTS requests to release updated version.
  My plan is to add myself as comaintainer and release newer upstream version.

Regards

Bug#933151: mariadb-10.3: FTBFS on riscv64

[Héctor Orón Martínez]

Hello,

Missatge de Hector Oron  del dia dg., 28 de jul.
2019 a les 1:45:
> The code including atomic must link using `-latomic`, that is
> apparently GCC bug, which it is not often seen in other architectures.
> I have been unable to test the assumption.

>From irc://OFTC/debian-riscv channel someone suggests to link -pthread.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#932514: gdb: Don't build against flex-old

[Héctor Orón Martínez]

Hello,

  I have pushed a slightly updated version of your patch to Git
(salsa) now, so it should be part of next release.

  
https://salsa.debian.org/gdb-team/gdb/commit/c9f210a8e1fcd89d2f24630a0283d68fa3b6275f

Regards

Missatge de Tommi Vainikainen  del dia ds., 20 de
jul. 2019 a les 11:42:
>
> Source: gdb
> Severity: normal
> Tags: patch
>
> Hi, as a maintainer of flex-old package I'm considering requesting
> removing it as obsolete and unmaintained version of flex.  The
> gdb Build-Depends on flex-old optionally. Please build the
> package only against current flex by removing references to flex-old
> package such as changed in the following patch.
>
> --- a/debian/control
> +++ b/debian/control
> @@ -17,7 +17,7 @@ Build-Depends:
> gettext,
> bison,
> dejagnu,
> -   flex | flex-old,
> +   flex,
> procps,
>  # Do we really care that much about running the Java tests?
>  #   gcj-jdk | gcj,



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#932258: console-setup-freebsd: missing dependency

[Héctor Orón Martínez]

Hello,

Missatge de Anton Zinoviev  del dia dc., 17 de jul.
2019 a les 17:06:

> On Wed, Jul 17, 2019 at 04:15:51PM +0200, Guillem Jover wrote:
> >
> > this seems like a problem with console-setup-freebsd being arch:all
> > and depending on kFreeBSD-specific packages which will not be
> > available elsewhere, in the same way console-setup-linux is an
> > arch:all depending on Linux-specific packages.
>
> Why is it a problem to have an arch:all package which is installable
> only on some architectures (due to missing dependencies)?

I noticed the issue while doing a repository consistency check with
main, contrib and non-free components for amd64 architecture on the
buster suite. Tools like wanna-build also do similar checks for
building packages, however this has not been an issue for the
wanna-build checks in the past.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#932258: console-setup-freebsd: missing dependency

[Héctor Orón Martínez]

Package: console-setup-freebsd
Version: 1.191
Severity: grave


Dear Maintainer,

  console-setup-freebsd has a dependency on vidcontrol, which is not part of 
buster|bullseye|unstable,
and causes the package to be uninstallable.

Regards

Bug#932257: libdbd-oracle-perl: unsatisfiable dependencies

[Héctor Orón Martínez]

Package: libdbd-oracle-perl
Version: 1.76-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

  libdbd-oracle-perl depends on oracle-instantclient12.1-basic | 
oracle-instantclient12.1-basiclite,
which are not found in buster|bullseye|unstable, causes the package to be 
unusable.

Regards

Bug#928229: gdb: fails to load libpython3.6m.so.1.0, but pkg depends on libpython3.7

[Héctor Orón Martínez]

Hello Maik,

Missatge de Maik Fischer  del dia dt., 30 d’abr.
2019 a les 12:42:
> $ gdb
> gdb: error while loading shared libraries: libpython3.6m.so.1.0: cannot open 
> shared object file: No such file or directory

Can you please show the output of `apt-cache policy gdb`?

Note in my system I see, expected, output:

zumbi@duoxiangshi:~$ ldd /usr/bin/gdb | grep python
libpython3.7m.so.1.0 =>
/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0 (0x7f4373f0e000)
zumbi@duoxiangshi:~$ LANG=C apt-cache policy gdb
gdb:
  Installed: 8.2.50.20190222-1
  Candidate: 8.2.50.20190222-1
  Version table:
 *** 8.2.50.20190222-1 100
  1 http://deb.debian.org/debian experimental/main amd64 Packages
100 /var/lib/dpkg/status
 8.2.1-2 500
500 http://deb.debian.org/debian sid/main amd64 Packages


-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#926931: unblock: golang-github-go-debos-fakemachine/0.0~git20181105.9316584-2

[Héctor Orón Martínez]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package golang-github-go-debos-fakemachine

Fixes release critical bug which causes package to be unusable


diff -Nru 
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/changelog 
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/changelog
--- golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/changelog 
2018-11-09 10:15:18.0 +0100
+++ golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/changelog 
2019-04-12 11:53:04.0 +0200
@@ -1,3 +1,10 @@
+golang-github-go-debos-fakemachine (0.0~git20181105.9316584-2) unstable; 
urgency=medium
+
+  * fakemachine: execution fails due to missing shared lib
+(Closes: #924392)
+
+ -- Héctor Orón Martínez   Fri, 12 Apr 2019 11:53:04 +0200
+
 golang-github-go-debos-fakemachine (0.0~git20181105.9316584-1) unstable; 
urgency=medium
 
   * New upstream version 0.0~git20181105.9316584
diff -Nru 
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/0001-Add-libresolve.so.2-in-the-initramfs.patch
 
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/0001-Add-libresolve.so.2-in-the-initramfs.patch
--- 
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/0001-Add-libresolve.so.2-in-the-initramfs.patch
   1970-01-01 01:00:00.0 +0100
+++ 
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/0001-Add-libresolve.so.2-in-the-initramfs.patch
   2019-04-12 11:47:40.0 +0200
@@ -0,0 +1,25 @@
+From: Sjoerd Simons 
+Date: Tue, 5 Mar 2019 10:17:57 +0100
+Subject: Add libresolve.so.2 in the initramfs
+
+busybox in buster depends on libresolve.so.2 so copy it to the
+initramfs; Potentially in future fakemachine should move to
+busybox-static
+
+Signed-off-by: Sjoerd Simons 
+---
+ machine.go | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/machine.go b/machine.go
+index 4a9bd83..021ee67 100644
+--- a/machine.go
 b/machine.go
+@@ -457,6 +457,7 @@ func (m *Machine) startup(command string, extracontent 
[][2]string) (int, error)
+   if mergedUsrSystem() {
+   prefix = "/usr"
+   }
++  w.CopyFile(prefix + "/lib/x86_64-linux-gnu/libresolv.so.2")
+   w.CopyFile(prefix + "/lib/x86_64-linux-gnu/libc.so.6")
+   w.CopyFile(prefix + "/bin/busybox")
+ 
diff -Nru 
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/series
 
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/series
--- 
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/series
1970-01-01 01:00:00.0 +0100
+++ 
golang-github-go-debos-fakemachine-0.0~git20181105.9316584/debian/patches/series
2019-04-12 11:47:40.0 +0200
@@ -0,0 +1 @@
+0001-Add-libresolve.so.2-in-the-initramfs.patch



unblock golang-github-go-debos-fakemachine/0.0~git20181105.9316584-2

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#926124: unblock: weston/5.0.0-3

[Héctor Orón Martínez]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package weston

Fixed a couple bugs related to:
  - make build reproducible
  - fix startup with systemd-login

Find debdiff attached:

diff --git a/debian/changelog b/debian/changelog
index d6a391bc..ba9cb592 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+weston (5.0.0-3) unstable; urgency=medium
+
+  * debian/control: add libdbus-1-dev to Build-Depends
+- Fixes "won't start despite having an active logind session"
+(Closes: #799325)
+Thanks Paul Menzel for analysis.
+  * debian/patches/reproducible-build-899358.patch: new patch
+- Make the build reproducible
+(Closes: #899358)
+
+ -- Héctor Orón Martínez   Thu, 28 Mar 2019 14:11:26 +0100
+
 weston (5.0.0-2) unstable; urgency=medium
 
   [ Emilio Pozuelo Monfort ]
diff --git a/debian/control b/debian/control
index c2c11c28..4eea61de 100644
--- a/debian/control
+++ b/debian/control
@@ -10,6 +10,7 @@ Build-Depends:
  debhelper (>= 10),
  quilt,
  pkg-config,
+ libdbus-1-dev,
  libpixman-1-dev (>= 0.25.2),
  libpng-dev,
  libjpeg-dev,
diff --git a/debian/patches/reproducible-build-899358.patch 
b/debian/patches/reproducible-build-899358.patch
new file mode 100644
index ..642c9dfb
--- /dev/null
+++ b/debian/patches/reproducible-build-899358.patch
@@ -0,0 +1,14 @@
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899358
+Index: weston/weston.ini.in
+===
+--- weston.orig/weston.ini.in  2019-03-28 12:55:11.730324981 +0100
 weston/weston.ini.in   2019-03-28 12:58:53.029372855 +0100
+@@ -38,7 +38,7 @@
+ 
+ [launcher]
+ icon=/usr/share/icons/gnome/24x24/apps/arts.png
+-path=@abs_top_builddir@/weston-flower
++path=@libexecdir@/weston-flower
+ 
+ [input-method]
+ path=@libexecdir@/weston-keyboard
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index ..4a8185bf
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+reproducible-build-899358.patch

unblock weston/5.0.0-3

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#922340: unblock: open-build-service/2.9.4-1

[Héctor Orón Martínez]

Hello,

Missatge de Jonathan Wiltshire  del dia dg., 17 de
març 2019 a les 19:04:
>
> Control: tag -1 moreinfo
>
> Hi,
>
> On Wed, Mar 06, 2019 at 11:51:45PM +0100, Hector Oron wrote:
> > OK, I tried, and to be honest, stable isn't perfect either, since
> > distro lifecycle is longer than application support, so not allowing
> > newer upstream versions in stable is problematic security wise in the
> > long term. open-build-service is not the only one in this category,
> > there are many packages in the same situation and it'd be nice to find
> > a common solution for all those.
>
> What is upstream's approach to stable security updates like? How long is a
> stable series maintained? Is it realistic to cherry-pick fixes from new
> upstream releases for buster's lifetime?
>
> New upstreams in stable aren't a problem in themselves, but when not all
> new upstream releases are suitable (e.g. mixing bug fixes and features) the
> effect can be to block further releases, and make fixing high severity bugs
> harder.

I have been discussing with my colleagues about current state of the
package and it needs a bit more polishing, hence we are fine with
closing this unblock as Paul did. We'll look into alternative ways to
distribute the package for the next stable distribution.

Thanks,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#922339: unblock: python-cassandra-driver/3.16.0-1

[Héctor Orón Martínez]

Hello,

Missatge de Paul Gevers  del dia ds., 30 de març
2019 a les 19:12:
>
> tags 922339 wontfix
> thanks
>
> On Sun, 17 Mar 2019 17:38:21 + Jonathan Wiltshire 
> wrote:
> > On Thu, Feb 14, 2019 at 08:11:55PM +0100, Héctor Orón Martínez wrote:
> > > Please unblock package python-cassandra-driver
> > >
> > > I have been working with Emmanuel Arias on getting his package sponsored
> > > into Debian, however it did not make it into Buster on time. It is a
> > > `salt` build dependency (however `salt` package maintainer has disabled
> > > it until it makes it in Buster).
> >
> > Is the intention that salt will enable support once this package migrates?
> > Will that require an unblock too?
> >
> > #921658 seems to suggest that salt is only a test-time build dependency.
> > Does this mean that not all of salt's tests are being run at the moment?
> > What is the impact of this?
> >
> > 2018-12-05 when the upload was prepared to 2019-02-08 when it was uploaded
> > is quite a long delay. Is long-term maintenance assured? Are sufficient
> > sponsors available for the next 5-6 years?
>
> I am closing this bug as wontfix as it is getting too late in the cycle
> for new packages and the above questions were not answered.

I am fine with that if it is not bloking saltstack from being in
buster. We can get it back in for Bullseye.

Thanks,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#917806: gdb: FTBFS on kfreebsd-any

[Héctor Orón Martínez]

Hello,

  Pushed patch to git.
  
https://salsa.debian.org/gdb-team/gdb/commit/4aff8eff239a85188e66617e719c51d93c1857e7

Missatge de Svante Signell  del dia dg., 30
de des. 2018 a les 16:21:
>
> Source: gdb
> Version: 8.2.1-1
> Severity: important
> Tags: ftbfs, patch
> User: debian-k...@lists.debian.org
> Usertags: kfreebsd
>
> Hello,
>
> Currently libdrm FTBFS on GNU/kFreeBSD due to a change of "struct
> nlist" in the header file /usr/include/bsd/nlist.h.
>
> Attached is a patch to make gdb build properly on kfreebsd-any.
>
> Thanks!



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#922796: gdb: Missing support for RISC-V

[Héctor Orón Martínez]

Hello,

  Patch pushed to git.
  
https://salsa.debian.org/gdb-team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175

Saludos

Missatge de Jonathan Behrens  del dia dc., 20 de
febr. 2019 a les 21:30:
>
> Package: gdb
> Version: 7.10-1
> Severity: normal
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu disco ubuntu-patch
>
> Dear Maintainer,
>
> In Ubuntu, the attached patch was applied to achieve the following:
>
> Enable support for the RISC-V architecture. This functionality was added
> upstream in GDB version 8.2.1, but did not take effect in the gdb-multiarch
> package because it maintains a whitelist of architectures to include (to keep
> binary size small by eliminating rarely used ones). My undestanding is that 
> the
> list of supported architectures is meant to mirror binutils-multiarch, which
> already includes RISC-V, meaning there shouldn't be any policy issues to 
> adding
> it here.
>
>
>   * Enable RISC-V architecture support.
>
>
> Thanks for considering the patch.
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers disco
>   APT policy: (500, 'disco')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.19.0-13-generic (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#922030: gdb internal error running -flto linked binaries

[Héctor Orón Martínez]

Hello,

Missatge de Hector Oron  del dia dl., 11 de febr.
2019 a les 15:17:

> > The fix seems to exist upstream ([1]) and was pushed to Fedora 29
> > already ([2]), looks like a good candidate for "buster" too...
>
> Indeed, thanks, I'll that uploaded in a -2 revision once 8.2.1 enters testing.

Pushed patches into git.
https://salsa.debian.org/gdb-team/gdb/commit/dc9459a2f7452cff27b26dded50a1f9c9d652e40

-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#922745: gdb needs a backport for PR binutils/23919

[Héctor Orón Martínez]

Missatge de Matthias Klose  del dia dc., 20 de febr.
2019 a les 10:15:
>
> Package: src:gdb
> Version: 8.2.1-1
> Severity: serious
> Tags: sid buster
>
> gdb needs a backport for PR binutils/23919. The PR fixes an issue with
> compressed debug sections, and is needed so that gdb can handle the fixed 
> debug
> sections.  elfutils already has the fix.
>
> The patch can be taken from the binutils 2.31 branch.

Patch applied in git.
https://salsa.debian.org/gdb-team/gdb/commit/b2e31f9b1cff137fc33f379b8e98bc134d648033

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#922342: unblock: ruby-jquery-ui-rails/6.0.1+dfsg-3

[Héctor Orón Martínez]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package ruby-jquery-ui-rails

`ruby-jquery-ui-rails` did not make it on time for the soft-free however I'd 
like release team to consider and grant an exception for it so we can get 
`open-build-service` package in for Buster release.

I am not attaching a debdiff since it is a major update. Gitlab is available at:
https://salsa.debian.org/ruby-team/ruby-jquery-ui-rails

Thanks for considering

unblock ruby-jquery-ui-rails/6.0.1+dfsg-3

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#922341: unblock: ruby-clockwork/2.0.3-4

[Héctor Orón Martínez]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package ruby-clockwork

`ruby-clockwork` did not make it on time for the soft-free however I'd like 
release team to consider and grant an exception for it so we can get 
`open-build-service` package in for Buster release.

I am not attaching a debdiff since it is a major update. Gitlab is available at:
https://salsa.debian.org/ruby-team/ruby-clockwork

Thanks for considering

unblock ruby-clockwork/2.0.3-4

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#922340: unblock: open-build-service/2.9.4-1

[Héctor Orón Martínez]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package open-build-service

A lot of effort has been put into `open-build-service`, since ruby rails 5 
transition needed to happen and it did. Even uploading the package on-time it 
was delayed due to a couple dependencies: `ruby-clockwork` and 
`ruby-jquery-ui-rails`.

Please consider an exception and allow `open-build-service` into Buster release.

I am not attaching a debdiff since it is a major upstream version update.

You might check gitlab instead at:
  https://salsa.debian.org/ruby-team/open-build-service

And its dependencies at:
  https://salsa.debian.org/ruby-team/ruby-clockwork
  https://salsa.debian.org/ruby-team/ruby-jquery-ui-rails

unblock open-build-service/2.9.4-1

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#922339: unblock: python-cassandra-driver/3.16.0-1

[Héctor Orón Martínez]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-cassandra-driver

I have been working with Emmanuel Arias on getting his package sponsored into 
Debian, however it did not make it into Buster on time. It is a `salt` build 
dependency (however `salt` package maintainer has disabled it until it makes it 
in Buster).

I am not attaching a debdiff because it is a new upstream version and I am 
requesting an exception here. You may check gitlab instead, which I know it is 
not preferred.

https://salsa.debian.org/python-team/modules/python-cassandra-driver

unblock python-cassandra-driver/3.16.0-1

Thanks for considering an exception to allow this package into Buster release.

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#898689: ITP: golang-github-ostreedev-ostree-go -- Golang bindings for httt://github.com/ostreedev/ostree

[Héctor Orón Martínez]

[Adding Sjoerd in CC]

Hello,

Missatge de Reinhard Tartler  del dia dc., 13 de febr.
2019 a les 13:22:
>
>
>
> On Wed, Jan 9, 2019 at 9:58 AM Alexandre Viau  wrote:
>>
>> On 2019-01-09 6:54 a.m., Reinhard Tartler wrote:
>> > Hi Juan,
>> >
>> > are you still working on this ITP? I was looking at skopeo as well,
>> > and stumpled upon this ITP. I noticed that you created a repository on
>> > salsa:
>> >
>> >
https://salsa.debian.org/go-team/packages/golang-github-ostreedev-ostree-go
>> >
>> > This package never got uploaded.
>> >
>> > However, I also noticed that there is another packaging repo in salsa,
>> > which contains a similar package that did get uploaded:
>> >
>> >
https://salsa.debian.org/go-team/packages/golang-github-sjoerdsimons-ostree-go
>> > https://tracker.debian.org/pkg/golang-github-sjoerdsimons-ostree-go
>> >
>> > I wonder what the relationship between these two are. It seems that the
>> > sjoerdsimons
>> > version does declare it satisfies the import of the
>> > github:ostreedev/ostree-go repo,
>> > which makes me believe it is a fork.
>>
>> Looking at the upstream website will show you that yes it is a fork.
>> (forked from ostreedev/ostree).
>>
>
>
> I'm slowly making progress towards to goal of packaging skopeo, and have
arrived at packaging the containers/image package. It also requires
compiling against the ostree-dev library (like containers/storage), but
this time it fails to build:
>
> # github.com/sjoerdsimons/ostree-go/pkg/otbuiltin
> In file included from /usr/include/glib-2.0/glib/glist.h:32,
>  from /usr/include/glib-2.0/glib/ghash.h:33,
>  from /usr/include/glib-2.0/glib.h:50,
>  from src/
github.com/sjoerdsimons/ostree-go/pkg/otbuiltin/builtin.go:16:
> src/github.com/sjoerdsimons/ostree-go/pkg/otbuiltin/builtin.go.h: In
function '_g_clear_object':
> /usr/include/glib-2.0/glib/gmem.h:121:18: warning: passing argument 1 of
'g_object_unref' discards 'volatile' qualifier from pointer target type
[-Wdiscarded-qualifiers]
>(destroy) (_ptr);
   \
>   ^~~~
> /usr/include/glib-2.0/gobject/gobject.h:672:36: note: in expansion of
macro 'g_clear_pointer'
>  #define g_clear_object(object_ptr) g_clear_pointer ((object_ptr),
g_object_unref)
> ^~~
> src/github.com/sjoerdsimons/ostree-go/pkg/otbuiltin/builtin.go.h:51:3:
note: in expansion of macro 'g_clear_object'
>g_clear_object(object_ptr);
>
>^~
>
>
> I noticed that a very similar error is mentioned in a commit message of
the upstream fork (ostreedev/ostree-go):
>
>
https://github.com/ostreedev/ostree-go/commit/7af23efc78cbcbf462ae58e30fc4b94e99f09436#diff-898ad6510d1fe82a218a36340e3b56ec
>
>
> I strongly suspect that compiling against ostreedev/ostree-go would fix
this issue.
>
> Given that https://github.com/sjoerdsimons/ostree-go/blob/master/README.md
clearly states:
>
>> Temporary repository for patches not yet merged in upstream ostree-go.
Please don't use this one but use https://github.com/ostreedev/ostree-go
instead
>
>
> I wonder why we are are using this fork in the first place.
>
> Hector, Andrej, Alex, can you please chime in? Can we avoid having two
copies of this library in the archive or is that the best way to proceed
for now?

https://github.com/sjoerdsimons/ostree-go is used by `debos`, an OS image
building tool. As you noticed Sjoerd attempted to work with upstream
https://github.com/ostreedev/ostree-go, but upstream has not been
responsive so far.
Sjoerd has only been taking care of the bits he needed for `debos` and not
committing to its upstream maintenance out of `debos` needs, therefore not
recommending general use of github.com/sjoerdsimons/ostree-go.

IMO, you should try to work with upstream and package that one for
`skopeo`. If upstream ever takes Sjoerd patches we'll remove his version
from Debian archive and switch to upstream copy for `debos` which to be
honest I do not see happening any time soon.

If upstream also fails for you, I am open to take patches to support your
application into `golang-github-sjoerdsimons-ostree-go` Debian package
and/or Sjoerd might be willing to queue those patches in his fork.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#917046: mesa: ease cross build dependency installability

[Héctor Orón Martínez]

Source: mesa
Version: 18.3.0-1
Severity: wishlist
Tags: patch

Dear Maintainer,

  Please consider easing cross dependency installability.
  Find propose patch:
  https://salsa.debian.org/xorg-team/lib/mesa/merge_requests/6

Regards

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

Kernel: Linux 4.17.0-3-amd64 (SMP w/16 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#917045: mako: support nocheck build profiles

[Héctor Orón Martínez]

Source: mako
Version: 1.0.7+ds1-1
Severity: wishlist
Tags: patch

Dear Maintainer,

  Please consider adding build profile for nocheck.
  Find proposed patch at:
  https://salsa.debian.org/python-team/modules/mako/merge_requests/3

Regards

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

Kernel: Linux 4.17.0-3-amd64 (SMP w/16 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#917044: mako: add support for nodoc

[Héctor Orón Martínez]

Source: mako
Version: 1.0.7+ds1-1
Severity: wishlist

Dear Maintainer,

  Please consider adding support for nodoc.
  Find proposed patch at:
  https://salsa.debian.org/python-team/modules/mako/merge_requests/2  

Regards

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

Kernel: Linux 4.17.0-3-amd64 (SMP w/16 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#917043: mako: fix clean target

[Héctor Orón Martínez]

Source: mako
Version: 1.0.7+ds1-1
Severity: important

Dear Maintainer,

  When building `mako` twice the package fails to clean.

  Please consider
  https://salsa.debian.org/python-team/modules/mako/merge_requests/1

Regards

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

Kernel: Linux 4.17.0-3-amd64 (SMP w/16 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#912853: transition: icu

[Héctor Orón Martínez]

Hey Steve,

Missatge de Steve McIntyre  del dia dc., 14 de nov.
2018 a les 17:11:

> Digging further and installing some debug symbols, I get to a problem
> in libfreetype6:
>
> (sid-armhf)steve@mjolnir:~/debian/harfbuzz/harfbuzz-2.1.1/build-main$ gdb 
> util/.libs/hb-shape core
> ...
> Core was generated by 
> `/home/steve/debian/harfbuzz/harfbuzz-2.1.1/build-main/util/.libs/hb-shape 
> ../te'.
> Program terminated with signal SIGBUS, Bus error.
> #0  TT_Get_MM_Var (face=0x1c66d78, master=master@entry=0x0) at 
> ./freetype-2.8.1/src/truetype/ttgxvar.c:2122
> 2122if ( a->minimum > a->def ||

Thanks!
Did you check if version in experimental (freetype-2.9.1) fixes it?

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#912853: transition: icu

[Héctor Orón Martínez]

Hello,

Missatge de Emilio Pozuelo Monfort  del dia dt., 13
de nov. 2018 a les 18:44:
>
> On 13/11/2018 17:45, László Böszörményi (GCS) wrote:
> >  Please note that src:harfbuzz currently has a problem on armhf, it
> > failed to build three times in line. The reason is known: the
> > arm-arm-01 named buildd always failed to build it[1]. Can you schedule
> > its build on an other armhf machine or a buildd admin (in Cc) can do
> > it? There's no sense trying to build it on the mentioned box again and
> > again or even later. If possible, please set that src:harfbuzz
> > shouldn't be tried to build on the arm-arm-01 machine in the future.
>
> That will be investigated. The problem is that arm-arm-01 is an arm64 machine,
> building armhf packages. harfbuzz doesn't like that.

Indeed, Steve is working on that topic, re-building armhf/armel on
arm64 and already found some issues. I pinged him about it in IRC,
however I CC him on this one as it might be valuable for his work.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#912853: transition: icu

[Héctor Orón Martínez]

Hello László,

Missatge de László Böszörményi (GCS)  del dia dt., 13
de nov. 2018 a les 17:46:
>
> On Mon, Nov 12, 2018 at 4:05 PM Emilio Pozuelo Monfort  
> wrote:
> > On 11/11/2018 11:24, László Böszörményi (GCS) wrote:
> > > On Sun, Nov 4, 2018 at 4:45 PM Laszlo Boszormenyi (GCS)  
> > > wrote:
> > >> I'd like to upload ICU 63.1 which was recently released for Buster.
> > >  I still miss the last three packages rebuilt, but I don't expect any
> > > problems with those.
> > > First, my methodology was to build the related packages both on i386
> > > and amd64 (32 and 64 bit) to detect all possible problems in advance.
> > > If a package failed due to ICU, I've patched it. If the reason was not
> > > clear, rebuilt the package for Sid to check that result as well.
> > > The order of rebuilds was harfbuzz -> boost1.67 -> make boost-defaults
> > > point to it, then all other packages.
> > Please go ahead with this. I will ack the boost transition once this is 
> > built.
>  Please note that src:harfbuzz currently has a problem on armhf, it
> failed to build three times in line. The reason is known: the
> arm-arm-01 named buildd always failed to build it[1]. Can you schedule
> its build on an other armhf machine or a buildd admin (in Cc) can do
> it? There's no sense trying to build it on the mentioned box again and
> again or even later. If possible, please set that src:harfbuzz
> shouldn't be tried to build on the arm-arm-01 machine in the future.

I have blacklisted it in arm-arm-01, however someone had give it back
and it is building (update built!) in arnold now.
Regards

> Thanks,
> Laszlo/GCS
> [1] https://buildd.debian.org/status/logs.php?pkg=harfbuzz=armhf



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#892031: stretch-pu: package wayland/1.12.0-1

[Héctor Orón Martínez]

Hello,

Missatge de Salvatore Bonaccorso  del dia dv., 9 de
nov. 2018 a les 6:57:

> Friendly ping, can you upload the fixed package? Unfortunately this
> will not make it for 9.6 but can then for 9.7.

I have uploaded the package.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#913130: ITP: golang-gopkg-freddierice-go-losetup.v1 -- A losetup implementation for go-lang

[Héctor Orón Martínez]

Package: wnpp
Severity: wishlist
Owner: Héctor Orón Martínez 

* Package name: golang-gopkg-freddierice-go-losetup.v1
  Version : 0.0~git20170407.fc9adea-1
  Upstream Author : Freddie Rice
* URL : https://github.com/freddierice/go-losetup
* License : MIT
  Programming Lang: Go
  Description : A losetup implementation for go-lang

This is a new dependency for `debos`, the Debian OS image builder tool.
I would like to maintain this package inside golang packaging team.

Bug#913026: libwww-curl-perl: Uninstallable on armhf due to being built against Perl 5.26 instead of 5.28

[Héctor Orón Martínez]

Hello Axel,

Thanks for the report.

Missatge de Axel Beckert  del dia dt., 6 de nov. 2018
a les 6:27:
>
> Package: libwww-curl-perl
> Version: 4.17-5
> Severity: serious
>
> Hi,
>
> it seems as if libwww-curl-perl 4.17-5 has been built for armhf in a
> outdated chroot:
>
> # apt-cache show libwww-curl-perl | egrep 'Version|Depends|Architecture|^$'
> Version: 4.17-5
> Architecture: armhf
> Depends: perl (>= 5.26.2-7+b1), perlapi-5.26.2, libc6 (>= 2.15), 
> libcurl3-gnutls (>= 7.16.2)
> ^^
> Version: 4.17-4+b3
> Architecture: armhf
> Depends: perl (>= 5.28.0-3), perlapi-5.28.0, libc6 (>= 2.15), libcurl3-gnutls 
> (>= 7.16.2)
> #
>
> (Underlining has been done manual.)
>
> Could please the armhf buildd admins chase down which buildds are
> affected (at least arm-arm-01 where this package was built) and trigger
> BinNMUs for all affected packages? (And then probably close this bug
> report.)

I have triggered nmu build for libwww-curl-perl and libre-engine-re2-perl.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#908603: docker.io: consider backporting to stable

[Héctor Orón Martínez]

Hello,

Missatge de Dmitry Smirnov  del dia dc., 12 de
set. 2018 a les 2:29:
>
> On Wednesday, 12 September 2018 4:01:24 AM AEST Héctor Orón Martínez wrote:
> >   Since `docker.io` reached testing, could you please consider backporting
> > it to stable?

> No, please... Maintaining Docker is an enormous time sink. I doubt backports
> will ever happen and certainly I don't want to be involved.

The whole point to bring back `docker.io` package to Debian was to
provide something usable in stable.

> I'm contemplating orphaning Docker and the only reason I'm still looking
> after it is because I think it is strategically important for Debian success.

I think so too, please keep up the good work, I am willing to help
(note I collaborated with Arnaud Rebillout) for docker.io to be back
again in Debian.

> I don't like Docker. It is very sloppy, bloated, over engineered with
> selfish, uncooperative fork-obsessed upstream who refuses to adopt good
> versioning practices making our work very difficult.

I agree, but it is key package for Debian and it's users.

> Recently I've switched all my containers to _rkt_ and I'm very happy about
> that.

I have never used rkt

> Whoever needs Docker can install it straight from "testing" since Docker is
> statically linked. I can't justify the effort required to maintain the
> official backport.

Hopefully we (Arnaud and I, and maybe other people can join a
docker-team) can help on that.

> >   What kind of work would be needed to ease the path to provide such
> > backport?
>
> Man time required to backport hundreds of dependency libraries and even more
> time to maintain all those, resolve complicated transitions, build/test
> failures and tight versioning. Team of several people working full time for
> months - that's what it will take.

If we embedded in the package most of the vendoring, would that help
on its future maintenance?
I know that might be a bit controversial however I think it might be
the only way to keep docker.io in the distribution going further
ahead.

> We are nowhere near the point where it would be safe to backport a monster
> package like Docker. First, I'd like to suggest having a real team
> maintaining Docker, not just myself. I've already invested too much time into
> Docker at the great personal cost and expense of other worthy projects/
> packages. I'm not going to stick much longer...

Your involvement has been key to give latest push and unblock latest
issues, it was great to find you managed to actually get docker.io
uploaded back to Debian. Thanks for that and all the hard work. I am
also pretty short time, however I'll try to be helpful going forward.

> Besides just keeping Docker in testing is a challenge due to build/test
> failures routinely exposed by CI. Docker dependency tree is very big and
> surface for problems is enormous.

Are you using Gitlab provided CI/CD features to track that? I'd need
to get up to speed with those.

> I wholeheartedly recommend using _rkt_ instead and it looks like rkt would be
> actually possible to backport.

I would need to look at that, however, that's a different package.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#908603: docker.io: consider backporting to stable

[Héctor Orón Martínez]

Package: docker.io
Version: 18.03.1+dfsg1-6
Severity: wishlist

Dear Maintainer,

  Since `docker.io` reached testing, could you please consider backporting it 
to stable?

  What kind of work would be needed to ease the path to provide such backport?

Regards

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

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#901180: release notes fails to build in a clean checkout

[Héctor Orón Martínez]

Hello
Missatge de Baptiste Jammet  del dia dj., 6 de
set. 2018 a les 19:57:
>
> Hello,
>
> Dixit Miroslav Kure, le 04/09/2018 :
>
> >I believe cs translation was excluded from builds quite some years ago,
> >so if it got reactivated again, please disable it / mark as obsolete
> >as needed. AFAIK there is noone working on the translation and I do
> >not see this changing in the near future.
>
> Thanks for your feedback.
> Indeed, ca & cs translations are disabled in the Makefile.
> So we just need to have a working transcount script for 1) have a
> successfull build and 2) taking care of future (or reactivated) xml
> translations.
>
> As nobody disagree, I plan to push the attached change during the
> week-end.

Sure, please go ahead! I am trying to find someone interested on doing
'ca' translation, so we might be able to reactivate it in future.

Regards
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#906696: flash-kernel: Please add an entry for the Rock64

[Héctor Orón Martínez]

Hello,

Missatge de Josua Mayer  del dia dg., 19
d’ag. 2018 a les 22:00:
> There is a vendor u-boot available based on 2017.09. It fully supports distro 
> boot and
> loading EFI applications.

Do you happen to know what's missing in the Debian u-boot package to
be usable in that board?

> Therefore the rock64 can be booted with grub-arm-efi.

Great!

> Only one important thing has to be dealt with: Getting the DTB loaded by 
> U-Boot!
> U-Boot searches for rockchip/rk3328-rock64.dtb in /, /dtb/, /dtb/current on 
> the EFI partition.
>
> The attached db entry takes care ot this particular path by storing it at 
> /boot/efi/dtb/rockchip/rk3328-rock64.dtb.

This is with vendor u-boot instead Debian u-boot, right?

> Other rockchip boards supported by mainline u-boot omit the rockchip 
> subdirectory and just search for the dtb name.
> However there is no support for the rock64 in mainline u-boot so I think 
> carrying this weird prefix is acceptable.

Not sure I agree on that. Is someone working on mainline u-boot to
support rock64?

> Currently most used and best documented source for rock64 U-Boot:
> https://github.com/ayufan-rock64/linux-u-boot/releases
>
> u-boot-erase-spi-rock64.img.xz can be used to flash u-boot to SPI flash once;
> from then on everything is standard:
> - debootstrap
> - linux-image-arm64
> - grub-arm-efi
> - grub-install --target=arm-efi --removable
>
> Yours sincerely
> Josua Mayer
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: arm64 (aarch64)
>
> Kernel: Linux 4.17.0-1-arm64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages flash-kernel depends on:
> ii  debconf [debconf-2.0]  1.5.69
> ii  devio  1.2-1.2+b1
> ii  initramfs-tools0.132
> ii  linux-base 4.5
> ii  mtd-utils  1:2.0.1-1
> ii  ucf3.0038
>
> Versions of packages flash-kernel recommends:
> ii  u-boot-tools  2018.05+dfsg-1
>
> flash-kernel suggests no packages.
>
> -- Configuration Files:
> /etc/flash-kernel/db changed:
> Machine: Pine64 Rock64
> Boot-DTB-Path: /boot/efi/rockchip/rk3328-rock64.dtb
> DTB-Id: rockchip/rk3328-rock64.dtb
>
>
> -- debconf information excluded



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#906317: dgit: consider demoting git-buildpackage to recommends

[Héctor Orón Martínez]

Package: dgit
Version: 6.6
Severity: wishlist
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team

Dear Maintainer,

  Please, consider demoting `git-buildpackage` to a recommends, since `dgit` 
does not "seem" to depend on it.

  For some background, I would like to enable Debian porterbox users to be able 
to run `dgit push`, however some of my colleagues on the Debian sysadmin team, 
consider installing `dgit` a concern, since they prefer users to push sources 
into porterboxes rather than pull them (being `apt source` the only exception). 
At the moment `dgit` is installed in porterboxes, however it drags in 
`git-buildpackage` which is very much a concern to have it installed there. 
Could you please consider demoting such dependency to a recommends? Or 
alternatively provide a separated binary package providing `dgit push` 
functionality? (Since porterboxes run on stable and you agree with the report, 
consider making available such feature via stable-backports)

  For reference, APT install log on stretch porterbox:
  Commandline: /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold 
install dgit
  Install: libjson-perl:amd64 (2.90-1, automatic), dgit:amd64 (3.11~deb9u1), 
git-buildpackage:amd64 (0.8.12.2, automatic), libtext-glob-perl:amd64 (0.10-1, 
automatic), python-dateutil:amd64 (2.5.3-2, automatic)

  Regards

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dgit depends on:
ii  apt1.6.3
ii  ca-certificates20180409
ii  coreutils  8.28-1
ii  curl   7.60.0-2
ii  devscripts 2.18.3
ii  dpkg-dev   1.19.0.5
ii  dput   1.0.2
ii  git [git-core] 1:2.18.0-1
ii  git-buildpackage   0.9.9
ii  libdpkg-perl   1.19.0.5
ii  libjson-perl   2.97001-1
ii  liblist-moreutils-perl 0.416-1+b3
ii  libtext-glob-perl  0.10-1
ii  libtext-iconv-perl 1.7-5+b6
ii  libwww-perl6.35-2
ii  perl [libdigest-sha-perl]  5.26.2-6

Versions of packages dgit recommends:
ii  openssh-client [ssh-client]  1:7.7p1-3

Versions of packages dgit suggests:
ii  cowbuilder  0.87+b1
ii  pbuilder0.229.3

-- no debconf information

Bug#905923: [pkg-go] Bug#905923: debos: autopkgtest regression: m.SetShowBoot undefined

[Héctor Orón Martínez]

Hello,

2018-08-11 22:09 GMT+02:00 Simon McVittie :
> Control: retitle -1 debos: autopkgtest regression: missing versioned B-D for 
> m.SetShowBoot
>
> On Sat, 11 Aug 2018 at 20:45:55 +0200, Paul Gevers wrote:
>> src/github.com/go-debos/debos/cmd/debos/debos.go:159:4: m.SetShowBoot
>> undefined (type *fakemachine.Machine has no field or method SetShowBoot)
>
> I contributed this feature to debos upstream. It is going to need a
> versioned build-dependency on the fakemachine version that added this
> method.

That is correct, already noticed when trying to build with old
fakemachine version, as it failed. All pieces are now in the archive,
however, for next upcoming debos release I'll add that as versioned
build dependency.

Thanks for your attention to detail!

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#869785: libinput10: Can't set base velocity and acceleration to match Logitech Trackball M570

[Héctor Orón Martínez]

Hello,

2018-07-16 19:33 GMT+02:00 Alf :
> Am 16.07.2018 um 16:26 schrieb Hector Oron:
>
>>
>> Could you please test version 1.11.2-1 and report back?
>>
>> Best regards
>>
> No change so far, tested with libinput10 1.11.2-1 in Buster.
>
> Please tell me a way how I can set base speed and accelleration profile for
> a Trackball. Mice work fine with default settings - but a TRACKBALL needs
> different settings as explained above for Velocity and Acceleration:
>> Base Speed ist too high, acceleration is too high. It does not consider
>> that with just a thumb you cannot position as exactly as with a mouse.
>> Movements over greater distance just needs a small kick to let the ball
>> spin, which does not apply to mice.

Can you please have a look to
  https://bugzilla.redhat.com/show_bug.cgi?id=1217881#c8

If that does not work, please open an issue upstream and let me know
bug reference for tracking.
  
https://bugs.freedesktop.org/enter_bug.cgi?component=Input%2Flibinput=xorg

Regards

> I had to revert to evdev again and current settings are:
>
> $ xinput --list-props 10
>
> Device 'Logitech M570':
> Device Enabled (136):   1
> Coordinate Transformation Matrix (138): 1.00, 0.00,
> 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00
> Device Accel Profile (264): 0
> Device Accel Constant Deceleration (265):   1.00
> Device Accel Adaptive Deceleration (266):   1.00
> Device Accel Velocity Scaling (267):10.00
> Device Product ID (259):1133, 4136
> Device Node (260):  "/dev/input/event2"
> Evdev Axis Inversion (268): 0, 0
> Evdev Axes Swap (270):  0
> Axis Labels (271):  "Rel X" (146), "Rel Y" (147), "Rel Horiz
> Wheel" (292), "Rel Vert Wheel" (263)
> Button Labels (272):"Button Left" (139), "Button Middle" (140),
> "Button Right" (141), "Button Wheel Up" (142), "Button Wheel Down" (143),
> "Button Horiz Wheel Left" (144), "Button Horiz Wheel Right" (145), "Button
> Side" (287), "Button Extra" (288), "Button Forward" (289), "Button Back"
> (290), "Button Task" (291), "Button Unknown" (262), "Button Unknown" (262),
> "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262),
> "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262),
> "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262),
> "Button Unknown" (262)
> Evdev Scrolling Distance (273): 1, 1, 1
> Evdev Middle Button Emulation (274):0
> Evdev Middle Button Timeout (275):  50
> Evdev Middle Button Button (276):   2
> Evdev Third Button Emulation (277): 0
> Evdev Third Button Emulation Timeout (278): 1000
> Evdev Third Button Emulation Button (279):  3
> Evdev Third Button Emulation Threshold (280):   20
> Evdev Wheel Emulation (281):0
> Evdev Wheel Emulation Axes (282):   0, 0, 4, 5
> Evdev Wheel Emulation Inertia (283):10
> Evdev Wheel Emulation Timeout (284):200
> Evdev Wheel Emulation Button (285): 4
> Evdev Drag Lock Buttons (286):  0



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#903830: RM: intel-processor-trace/stable [s390x] -- ANAIS; package only meanful on Intel architecture

[Héctor Orón Martínez]

Package: ftp.debian.org
Severity: normal

The `intel-processor-trace` package is only meanful on Intel arches, therefore 
other binaries should be removed from the archive.
Please, remove  s390x binaries (libipt1, libipt-dev) for stable/testing and 
unstable distributions.

Regards

Bug#892070: stretch-pu: package obs-build/20160921-1

[Héctor Orón Martínez]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hello,

  I would like to push security fix into stable for `obs-build`.
  The patch fixes CVE-2017-14804 as described in #887306.
  Please consider the following patch attached.

Regards

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_AD.utf8, LC_CTYPE=ca_AD.utf8 (charmap=UTF-8), LANGUAGE=ca_AD:ca 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru obs-build-20170201/debian/changelog 
obs-build-20170201/debian/changelog
--- obs-build-20170201/debian/changelog 2017-08-04 23:24:36.0 +0200
+++ obs-build-20170201/debian/changelog 2018-03-04 23:05:06.0 +0100
@@ -1,3 +1,11 @@
+obs-build (20170201-3+deb9u1) stretch; urgency=medium
+
+  * CVE-2017-14804 (Closes: #887306)
+- Improve extractbuild to avoid write to files in the host system.
+- debian/patches/Improve-sanity-checks-in-extractbuild.patch: add new
+
+ -- Héctor Orón Martínez <zu...@debian.org>  Sun, 04 Mar 2018 23:05:06 +0100
+
 obs-build (20170201-3) unstable; urgency=medium
 
   [ Sjoerd Simons ]
diff -Nru 
obs-build-20170201/debian/patches/Improve-sanity-checks-in-extractbuild.patch 
obs-build-20170201/debian/patches/Improve-sanity-checks-in-extractbuild.patch
--- 
obs-build-20170201/debian/patches/Improve-sanity-checks-in-extractbuild.patch   
1970-01-01 01:00:00.0 +0100
+++ 
obs-build-20170201/debian/patches/Improve-sanity-checks-in-extractbuild.patch   
2018-03-04 23:01:56.0 +0100
@@ -0,0 +1,34 @@
+From fc36b1c95afbe11e65fd1ed6f75c1824cdb26230 Mon Sep 17 00:00:00 2001
+Message-Id: 
<fc36b1c95afbe11e65fd1ed6f75c1824cdb26230.1511739165.git.suse-...@gmx.de>
+From: Marcus Huewe <suse-...@gmx.de>
+Date: Sun, 26 Nov 2017 20:25:48 +0100
+Subject: [PATCH] Improve sanity checks in extractbuild
+
+A \0 in a symlink target can be used to write to a file in the host
+system. For the same reason, we do not allow to process a file more
+than once. A \0 in a filename makes no sense, hence forbid it.
+---
+ extractbuild | 3 +++
+ 1 file changed, 3 insertions(+)
+
+Index: obs-build-20160921/extractbuild
+===
+--- obs-build-20160921.orig/extractbuild
 obs-build-20160921/extractbuild
+@@ -74,6 +74,8 @@ while () {
+   my ($filetype, $file, $filesize, $blksize, @blocks) = split(/ /);
+   die("invalid input '$_'\n") unless defined($file);
+   $file =~ s/%([a-fA-F0-9]{2})/chr(hex($1))/ge;
++  die("bad file '$file' (contains \\0)\n") if $file =~ /\0/;
++  die("already processed: $file\n") if $done{$file};
+   die("bad file '$file'\n") if "/$file/" =~ /\/\.{0,2}\//s;
+   if ($file =~ /^(.*)\//s) {
+ die("file without directory: $file\n") unless $done{$1} && $done{$1} eq 
'd';
+@@ -88,6 +90,7 @@ while () {
+ my $target = $filesize;
+ die("symlink without target\n") unless defined $target;
+ $target =~ s/%([a-fA-F0-9]{2})/chr(hex($1))/ge;
++die("bad symlink: $target (contains \\0)\n") if $target =~ /\0/;
+ die("bad symlink: $target\n") if "/$target/" =~ /\/\.?\//s;
+ if ("/$target/" =~ /^(\/\.\.)+\/(.*?)$/s) {
+   my ($head, $tail) = ($1, $2);
diff -Nru obs-build-20170201/debian/patches/series 
obs-build-20170201/debian/patches/series
--- obs-build-20170201/debian/patches/series2017-08-04 23:24:36.0 
+0200
+++ obs-build-20170201/debian/patches/series2018-03-04 23:03:58.0 
+0100
@@ -15,3 +15,4 @@
 HACK-Make-glibc-build.patch
 debootstrap-generate-apt-caches.patch
 
+Improve-sanity-checks-in-extractbuild.patch

Bug#892032: jessie-pu: package wayland/1.6.0-2

[Héctor Orón Martínez]

Hello,

2018-03-04 15:44 GMT+01:00 Emilio Pozuelo Monfort <po...@debian.org>:
> On 04/03/18 12:46, Héctor Orón Martínez wrote:
>>
>> diff --git a/debian/changelog b/debian/changelog
>> index 645a4bc..b6409a8 100644
>> --- a/debian/changelog
>> +++ b/debian/changelog
>> @@ -1,3 +1,14 @@
>> +wayland (1.6.0-2+deb8u1) stretch; urgency=medium
>
> Distribution should be jessie.

Ouch! Right. Find new version attached


-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.
From c9f4eb1998a3b390c8b03df7c84f83608a3418fb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?H=C3=A9ctor=20Or=C3=B3n=20Mart=C3=ADnez?= <zu...@debian.org>
Date: Sun, 4 Mar 2018 12:29:17 +0100
Subject: [PATCH] debian/patches/CVE-2017-16612.patch: fix cursor integer
 overflow
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Héctor Orón Martínez <zu...@debian.org>
---
 debian/changelog| 11 +
 debian/patches/CVE-2017-16612.patch | 47 +
 debian/patches/series   |  1 +
 3 files changed, 59 insertions(+)
 create mode 100644 debian/patches/CVE-2017-16612.patch
 create mode 100644 debian/patches/series

diff --git a/debian/changelog b/debian/changelog
index 645a4bc..0379671 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+wayland (1.6.0-2+deb8u1) jessie; urgency=medium
+
+  * debian/patches/CVE-2017-16612.patch: (Closes: #889681)
+- libXcursor before 1.1.15 has various integer overflows that could lead
+  to heap buffer overflows when processing malicious cursors, e.g., with
+  programs like GIMP. It is also possible that an attack vector exists
+  against the related code in cursor/xcursor.c in Wayland through
+  1.14.0.
+
+ -- Héctor Orón Martínez <zu...@debian.org>  Sun, 04 Mar 2018 12:27:36 +0100
+
 wayland (1.6.0-2) unstable; urgency=medium
 
   * Switch back to use upstream tarball.
diff --git a/debian/patches/CVE-2017-16612.patch b/debian/patches/CVE-2017-16612.patch
new file mode 100644
index 000..9d91f70
--- /dev/null
+++ b/debian/patches/CVE-2017-16612.patch
@@ -0,0 +1,47 @@
+commit 5d201df72f3d4f4cb8b8f75f980169b03507da38
+Author: Tobias Stoeckmann <tob...@stoeckmann.org>
+Date:   Tue Nov 28 21:38:07 2017 +0100
+
+cursor: Fix heap overflows when parsing malicious files.
+
+It is possible to trigger heap overflows due to an integer overflow
+while parsing images.
+
+The integer overflow occurs because the chosen limit 0x1 for
+dimensions is too large for 32 bit systems, because each pixel takes
+4 bytes. Properly chosen values allow an overflow which in turn will
+lead to less allocated memory than needed for subsequent reads.
+
+See also: https://cgit.freedesktop.org/xorg/lib/libXcursor/commit/?id=4794b5dd34688158fb51a2943032569d3780c4b8
+Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=103961
+
+Signed-off-by: Tobias Stoeckmann <tob...@stoeckmann.org>
+[Pekka: add link to the corresponding libXcursor commit]
+Signed-off-by: Pekka Paalanen <pekka.paala...@collabora.co.uk>
+
+diff --git a/cursor/xcursor.c b/cursor/xcursor.c
+index ca41c4a..689c702 100644
+--- a/cursor/xcursor.c
 b/cursor/xcursor.c
+@@ -202,6 +202,11 @@ XcursorImageCreate (int width, int height)
+ {
+ XcursorImage*image;
+ 
++if (width < 0 || height < 0)
++   return NULL;
++if (width > XCURSOR_IMAGE_MAX_SIZE || height > XCURSOR_IMAGE_MAX_SIZE)
++   return NULL;
++
+ image = malloc (sizeof (XcursorImage) +
+ 		width * height * sizeof (XcursorPixel));
+ if (!image)
+@@ -482,7 +487,8 @@ _XcursorReadImage (XcursorFile		*file,
+ if (!_XcursorReadUInt (file, ))
+ 	return NULL;
+ /* sanity check data */
+-if (head.width >= 0x1 || head.height > 0x1)
++if (head.width > XCURSOR_IMAGE_MAX_SIZE  ||
++	head.height > XCURSOR_IMAGE_MAX_SIZE)
+ 	return NULL;
+ if (head.width == 0 || head.height == 0)
+ 	return NULL;
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..4c42ec7
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+CVE-2017-16612.patch
-- 
2.16.2

Bug#892032: jessie-pu: package wayland/1.6.0-2

[Héctor Orón Martínez]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Hello,

  I would like to apply oldstable fix for #889681 in oldstable.
  I am attaching the patch I plan to upload to oldstable.
  Note, I have requested security team if they want to handle it via
  security queue or stable update instead.

Regards

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_AD.utf8, LC_CTYPE=ca_AD.utf8 (charmap=UTF-8), LANGUAGE=ca_AD:ca 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
From 5df34123d130816a1acf506d8e9f1a1c3e3efcc8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?H=C3=A9ctor=20Or=C3=B3n=20Mart=C3=ADnez?= <zu...@debian.org>
Date: Sun, 4 Mar 2018 12:29:17 +0100
Subject: [PATCH] debian/patches/CVE-2017-16612.patch: fix cursor integer
 overflow
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Héctor Orón Martínez <zu...@debian.org>
---
 debian/changelog| 11 +
 debian/patches/CVE-2017-16612.patch | 47 +
 debian/patches/series   |  1 +
 3 files changed, 59 insertions(+)
 create mode 100644 debian/patches/CVE-2017-16612.patch
 create mode 100644 debian/patches/series

diff --git a/debian/changelog b/debian/changelog
index 645a4bc..b6409a8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+wayland (1.6.0-2+deb8u1) stretch; urgency=medium
+
+  * debian/patches/CVE-2017-16612.patch: (Closes: #889681)
+- libXcursor before 1.1.15 has various integer overflows that could lead
+  to heap buffer overflows when processing malicious cursors, e.g., with
+  programs like GIMP. It is also possible that an attack vector exists
+  against the related code in cursor/xcursor.c in Wayland through
+  1.14.0.
+
+ -- Héctor Orón Martínez <zu...@debian.org>  Sun, 04 Mar 2018 12:27:36 +0100
+
 wayland (1.6.0-2) unstable; urgency=medium
 
   * Switch back to use upstream tarball.
diff --git a/debian/patches/CVE-2017-16612.patch 
b/debian/patches/CVE-2017-16612.patch
new file mode 100644
index 000..9d91f70
--- /dev/null
+++ b/debian/patches/CVE-2017-16612.patch
@@ -0,0 +1,47 @@
+commit 5d201df72f3d4f4cb8b8f75f980169b03507da38
+Author: Tobias Stoeckmann <tob...@stoeckmann.org>
+Date:   Tue Nov 28 21:38:07 2017 +0100
+
+cursor: Fix heap overflows when parsing malicious files.
+
+It is possible to trigger heap overflows due to an integer overflow
+while parsing images.
+
+The integer overflow occurs because the chosen limit 0x1 for
+dimensions is too large for 32 bit systems, because each pixel takes
+4 bytes. Properly chosen values allow an overflow which in turn will
+lead to less allocated memory than needed for subsequent reads.
+
+See also: 
https://cgit.freedesktop.org/xorg/lib/libXcursor/commit/?id=4794b5dd34688158fb51a2943032569d3780c4b8
+Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=103961
+
+Signed-off-by: Tobias Stoeckmann <tob...@stoeckmann.org>
+[Pekka: add link to the corresponding libXcursor commit]
+Signed-off-by: Pekka Paalanen <pekka.paala...@collabora.co.uk>
+
+diff --git a/cursor/xcursor.c b/cursor/xcursor.c
+index ca41c4a..689c702 100644
+--- a/cursor/xcursor.c
 b/cursor/xcursor.c
+@@ -202,6 +202,11 @@ XcursorImageCreate (int width, int height)
+ {
+ XcursorImage*image;
+ 
++if (width < 0 || height < 0)
++   return NULL;
++if (width > XCURSOR_IMAGE_MAX_SIZE || height > XCURSOR_IMAGE_MAX_SIZE)
++   return NULL;
++
+ image = malloc (sizeof (XcursorImage) +
+   width * height * sizeof (XcursorPixel));
+ if (!image)
+@@ -482,7 +487,8 @@ _XcursorReadImage (XcursorFile *file,
+ if (!_XcursorReadUInt (file, ))
+   return NULL;
+ /* sanity check data */
+-if (head.width >= 0x1 || head.height > 0x1)
++if (head.width > XCURSOR_IMAGE_MAX_SIZE  ||
++  head.height > XCURSOR_IMAGE_MAX_SIZE)
+   return NULL;
+ if (head.width == 0 || head.height == 0)
+   return NULL;
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..4c42ec7
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+CVE-2017-16612.patch
-- 
2.16.2

Bug#892031: stretch-pu: package wayland/1.12.0-1

[Héctor Orón Martínez]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hello,

  I would like to apply fix in stable for #889681.
  I have asked security team if they want the fix via security queue or stable
  update, however I have gotten no reply yet. I am attaching the patch I intend
  to upload to stable if you acknowledge it.

Regards

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_AD.utf8, LC_CTYPE=ca_AD.utf8 (charmap=UTF-8), LANGUAGE=ca_AD:ca 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
From 2471b0463e9395bd981f8b875e3280f1fc6b995f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?H=C3=A9ctor=20Or=C3=B3n=20Mart=C3=ADnez?= <zu...@debian.org>
Date: Sun, 4 Mar 2018 11:54:40 +0100
Subject: [PATCH] debian/patches/CVE-2017-16612.patch: fix cursor integer
 overflow
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Héctor Orón Martínez <zu...@debian.org>
---
 debian/changelog| 11 +
 debian/patches/CVE-2017-16612.patch | 47 +
 debian/patches/series   |  1 +
 3 files changed, 59 insertions(+)
 create mode 100644 debian/patches/CVE-2017-16612.patch
 create mode 100644 debian/patches/series

diff --git a/debian/changelog b/debian/changelog
index 2f84b50..7495ef3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+wayland (1.12.0-1+deb9u1) stretch; urgency=medium
+
+  * debian/patches/CVE-2017-16612.patch: (Closes: #889681)
+- libXcursor before 1.1.15 has various integer overflows that could lead
+  to heap buffer overflows when processing malicious cursors, e.g., with
+  programs like GIMP. It is also possible that an attack vector exists
+  against the related code in cursor/xcursor.c in Wayland through
+  1.14.0.
+
+ -- Héctor Orón Martínez <zu...@debian.org>  Sun, 04 Mar 2018 11:43:29 +0100
+
 wayland (1.12.0-1) unstable; urgency=medium
 
   * New upstream release. Closes: #840752.
diff --git a/debian/patches/CVE-2017-16612.patch 
b/debian/patches/CVE-2017-16612.patch
new file mode 100644
index 000..9d91f70
--- /dev/null
+++ b/debian/patches/CVE-2017-16612.patch
@@ -0,0 +1,47 @@
+commit 5d201df72f3d4f4cb8b8f75f980169b03507da38
+Author: Tobias Stoeckmann <tob...@stoeckmann.org>
+Date:   Tue Nov 28 21:38:07 2017 +0100
+
+cursor: Fix heap overflows when parsing malicious files.
+
+It is possible to trigger heap overflows due to an integer overflow
+while parsing images.
+
+The integer overflow occurs because the chosen limit 0x1 for
+dimensions is too large for 32 bit systems, because each pixel takes
+4 bytes. Properly chosen values allow an overflow which in turn will
+lead to less allocated memory than needed for subsequent reads.
+
+See also: 
https://cgit.freedesktop.org/xorg/lib/libXcursor/commit/?id=4794b5dd34688158fb51a2943032569d3780c4b8
+Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=103961
+
+Signed-off-by: Tobias Stoeckmann <tob...@stoeckmann.org>
+[Pekka: add link to the corresponding libXcursor commit]
+Signed-off-by: Pekka Paalanen <pekka.paala...@collabora.co.uk>
+
+diff --git a/cursor/xcursor.c b/cursor/xcursor.c
+index ca41c4a..689c702 100644
+--- a/cursor/xcursor.c
 b/cursor/xcursor.c
+@@ -202,6 +202,11 @@ XcursorImageCreate (int width, int height)
+ {
+ XcursorImage*image;
+ 
++if (width < 0 || height < 0)
++   return NULL;
++if (width > XCURSOR_IMAGE_MAX_SIZE || height > XCURSOR_IMAGE_MAX_SIZE)
++   return NULL;
++
+ image = malloc (sizeof (XcursorImage) +
+   width * height * sizeof (XcursorPixel));
+ if (!image)
+@@ -482,7 +487,8 @@ _XcursorReadImage (XcursorFile *file,
+ if (!_XcursorReadUInt (file, ))
+   return NULL;
+ /* sanity check data */
+-if (head.width >= 0x1 || head.height > 0x1)
++if (head.width > XCURSOR_IMAGE_MAX_SIZE  ||
++  head.height > XCURSOR_IMAGE_MAX_SIZE)
+   return NULL;
+ if (head.width == 0 || head.height == 0)
+   return NULL;
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..4c42ec7
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+CVE-2017-16612.patch
-- 
2.16.2

Bug#889681: wayland: CVE-2017-16612: fix via stable updates or security queue?

[Héctor Orón Martínez]

Hello,

  I plan to fix the CVE issue in stable and oldstable:
  -
https://salsa.debian.org/xorg-team/wayland/wayland/commit/2471b0463e9395bd981f8b875e3280f1fc6b995f
  -
https://salsa.debian.org/xorg-team/wayland/wayland/commit/5df34123d130816a1acf506d8e9f1a1c3e3efcc8

  While I am testing the package, should I upload to security queues or
stable updates?

Regards,
-- 
Héctor Orón Martínez
   
   Visit Collabora on the Web at https://www.collabora.com/
   Follow Collabora on Twitter https://twitter.com/collabora
   

Bug#887306: obs-build: CVE-2017-14804: Exploit extractbuild to write to files in the host system

[Héctor Orón Martínez]

Hello Salvatore,

  Since you are part of security team, should the fix go in stable via
security queue or stable pu?

Regards

On Sun, 14 Jan 2018 20:44:07 +0100 Salvatore Bonaccorso
<car...@debian.org> wrote:
> Source: obs-build
> Version: 20170201-1
> Severity: grave
> Tags: security upstream
> Forwarded: https://bugzilla.novell.com/show_bug.cgi?id=1069904
> 
> Hi,
> 
> the following vulnerability was published for obs-build.
> 
> I noticed the SUSE entry while checking for another issue for osc, and
> note I'm completely unfamiliar with obs-build, so if you think this
> needs an update as well for stable and oldstable, contact team@s.d.o
> for double checking. To be on the safe side, chosen severity grave.
> 
> CVE-2017-14804[0]:
> build: Exploit extractbuild to write to files in the host system
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2017-14804
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14804
> [1] https://bugzilla.novell.com/show_bug.cgi?id=1069904
> 
> Please adjust the affected versions in the BTS as needed.
> 
> Regards,
> Salvatore
> 
> 

-- 
Héctor Orón Martínez

Collabora Ltd
The Platinum Building
St John's Innovation Park, Cambridge
CB4 0DS, United Kingdom
Telephone: +44 (0)1223 362967
Fax: +44 (0) 1223 351966

   
   Visit Collabora on the Web at https://www.collabora.com/
   Follow Collabora on Twitter https://twitter.com/collabora
   

Bug#886767: two packages of https://github.com/jessevdk/go-flags

[Héctor Orón Martínez]

Hello,

On Wed, 10 Jan 2018 13:54:02 +0100 Geert Stappers <stapp...@stappers.nl>
wrote:
> Control: retitle -1  two packages of https://github.com/jessevdk/go-flags
> 
> On Wed, Jan 10, 2018 at 01:47:06PM +0100, Geert Stappers wrote:
> > On Wed, Jan 10, 2018 at 07:47:20AM +1300, Michael Hudson-Doyle wrote:
> > > On 10/01/2018 7:08 AM, "Hector Oron" <zu...@debian.org> wrote:
> > > > Package: wnpp
> > > > 
> > > > * Package name: go-flags
> > > >   Upstream Author : Jesse van den Kieboom
> > > > * URL : https://github.com/jessevdk/go-flags
> > > > * License : BSD-3-clause
> > > >   Programming Lang: Go
> > > >   Description : go command line option parser
> > > > 
> > > >  go-flags: Go library for parsing command line arguments
> > > >
> > > This is already packaged, as golang-go-flags-dev or something like that.
> > 
> > https://tracker.debian.org/pkg/golang-go-flags
> > 
> > and there is also
> > 
> > https://tracker.debian.org/pkg/golang-github-svent-go-flags
> > 
> > both originate from https://github.com/jessevdk/go-flags
> > 
> > both packages are maintaint by pkg-go-maintain...@lists.alioth.debian.org
> > 
> > 
> > Closing this ITP  could be an option.
> 
> Using this bugreport for discussion what to do with
> the "duplicate" is another option.

FWIW, for now I'll use a build dependency on `golang-go-flags-dev`.
However, according to Go packaging policy, I understand the proper
package should be named `golang-github-jessevdk-go-flags`.

What do you think? Should we rename them all to
`golang-github-jessevdk-go-flags` and keep only one copy in the archive?

Best regards,
-- 
Héctor Orón Martínez

Collabora Ltd
The Platinum Building
St John's Innovation Park, Cambridge
CB4 0DS, United Kingdom
Telephone: +44 (0)1223 362967
Fax: +44 (0) 1223 351966

   
   Visit Collabora on the Web at https://www.collabora.com/
   Follow Collabora on Twitter https://twitter.com/collabora
   



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#886763: ITP: golang-github-surma-gocpio -- A Go package for cpio archives

[Héctor Orón Martínez]

Package: wnpp
Severity: wishlist
Owner: Héctor Orón Martínez <zu...@debian.org>

* Package name: golang-github-surma-gocpio
  Version : 1.1.0+git20160926.fcb6877-1
  Upstream Author : Surma
* URL : https://github.com/surma/gocpio
* License : Apache-2.0
  Programming Lang: Go
  Description : A Go package for cpio archives

 gocpio is a  simple library similar to Go’s tar or zip
 package for accessing cpio archives. It’s not pretty and
 only implements the new ASCII format.

 This is a build dependency for `debos' Go application.

-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#881569: [Fwd: gdb: FTBFS on hurd-i386]

[Héctor Orón Martínez]

Hello Svante,

On Sat, Dec 23, 2017 at 7:41 PM, Svante Signell
 wrote:
> Hello,
>
> These patches was submitted to Debian November 13 2017. Nothing has
> happened so far, so maybe upstream would be interested to consider the
> patches for next release.

I would like to have them applied in Debian package for next release,
however it is taking more time than I thought, then I am going on
vacations. If you are able to upload to Debian, feel free to NMU the
package, otherwise, I'll try to have a look in a couple weeks.

> Thanks!
>
> -- Forwarded message --
> From: Svante Signell 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Mon, 13 Nov 2017 04:31:34 +0100
> Subject: gdb: FTBFS on hurd-i386
> Source: gdb
> Version: 8.0-1
> Severity: important
> Tags: patch
> User: debian-h...@lists.debian.org
> Usertags: hurd, experimental
>
> Hi,
>
> gdb FTBFS on GNU/Hurd due to three reasons:
>
> - Usage of PATH_MAX in gdb/remote.c
>
> - Recent changes in Hurd failing the build of gdb/gnu-nat.c
>
> - A name clash of struct thread_info and the kernel function thread_info()
> included in gdb/thread.c and gdb/python/py-record-btrace.c.
>
> Include paths:
> 1) defs.h: #include "gdbarch.h": struct thread_info
>
> 2) defs.h: #include "nm.h":#include :#include 
> where the function thread_info() is defined:
>
> extern kern_return_t thread_info
> (
>  mach_port_t target_thread,
>  int flavor,
>  thread_info_t thread_info_out,
>  mach_msg_type_number_t *thread_info_outCnt
> );
>
> The attached patches fixes these issues:
> gdb-PATH_MAX.patch
> gnu-nat.c.patch
> struct-thread_info.patch
>
> Thanks :)
>



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#881936: apparmor: support usrmerge

[Héctor Orón Martínez]

Hello,

FYI patch got merged upstream:
https://gitlab.com/apparmor/apparmor/commit/b24a1c4d546a6825f252d27243e09c80d04cf484

And thanks for reminding me.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#881936: apparmor: support usrmerge

[Héctor Orón Martínez]

Hello,

2017-12-07 19:12 GMT+01:00 intrigeri :
> Control: retitle -1 the upstream test suite does not support usrmerge
>
> intrigeri:
>> Can you please send this upstream as a merge request there:
>
>>   https://gitlab.com/apparmor/apparmor/
>
>> ?
>
>> If you prefer not to, I can forward. But IIRC it's not your first
>> contribution so on the long term, it would make sense if you would
>> send your proposed changes directly upstream :)
>
> Ping?

Sorry it felt through the cracks... here it is now...

https://gitlab.com/apparmor/apparmor/merge_requests/33

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#881983: nvidia-kernel-common: fails upon upgrade

[Héctor Orón Martínez]

Package: nvidia-kernel-common
Version: 20151021+4
Severity: important

Dear Maintainer,

   * What led up to the situation?
   Upgrading Debian Sid system.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 sudo apt upgrade

   * What was the outcome of this action?
 Preparing to unpack .../nvidia-kernel-common_20151021+5_amd64.deb ...
 dpkg-maintscript-helper: error: dpkg: warning: version 
'20051028\+1\+nmu2\~' has bad syntax: invalid character in version number
 dpkg: error processing archive 
/var/cache/apt/archives/nvidia-kernel-common_20151021+5_amd64.deb (--unpack):
  new nvidia-kernel-common package pre-installation script subprocess 
returned error exit status 1
 dpkg-maintscript-helper: error: dpkg: warning: version 
'20051028\+1\+nmu2\~' has bad syntax: invalid character in version number
 dpkg: error while cleaning up:
  new nvidia-kernel-common package post-removal script subprocess returned 
error exit status 1
 Errors were encountered while processing:
  /var/cache/apt/archives/nvidia-kernel-common_20151021+5_amd64.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)

   * What outcome did you expect instead?
 Sucessfully installed package

   dpkg 1.19.0.4 is installed in this system.

Regards

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/16 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#881936: apparmor: support usrmerge

[Héctor Orón Martínez]

Source: apparmor
Version: 2.11.1-3
Severity: wishlist

Dear Maintainer,

  Please consider the following patch to support usrmerge: (in debdiff form)


diff -Nru apparmor-2.11.1/debian/changelog apparmor-2.11.1/debian/changelog
--- apparmor-2.11.1/debian/changelog2017-11-05 20:26:47.0 +0100
+++ apparmor-2.11.1/debian/changelog2017-11-16 19:57:03.0 +0100
@@ -1,3 +1,11 @@
+apparmor (2.11.1-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/apparmor-support-usrmerge.patch:
+- add support for usrmerge in tests
+
+ -- Héctor Orón Martínez <zu...@debian.org>  Thu, 16 Nov 2017 19:57:03 +0100
+
 apparmor (2.11.1-3) unstable; urgency=medium
 
   * upstream-commit-92752f5-support-Google-Chrome-beta.patch:
diff -Nru apparmor-2.11.1/debian/patches/apparmor-support-usrmerge.patch 
apparmor-2.11.1/debian/patches/apparmor-support-usrmerge.patch
--- apparmor-2.11.1/debian/patches/apparmor-support-usrmerge.patch  
1970-01-01 01:00:00.0 +0100
+++ apparmor-2.11.1/debian/patches/apparmor-support-usrmerge.patch  
2017-11-16 19:56:45.0 +0100
@@ -0,0 +1,136 @@
+From: Héctor Orón Martínez
+ <hector.o...@collabora.co.uk>
+Date: Thu, 16 Nov 2017 18:11:43 +0100
+Subject: apparmor: support usrmerge
+MIME-Version: 1.0
+Content-Type: text/plain; charset="utf-8"
+Content-Transfer-Encoding: base64
+
+---
+ parser/tst/simple_tests/file/allow/ok_append_1.sd  | 10 +-
+ .../file/allow/ok_embedded_spaces_1.sd |  2 +-
+ .../file/allow/ok_embedded_spaces_2.sd |  2 +-
+ parser/tst/simple_tests/file/allow/ok_lock_1.sd| 22 +++---
+ parser/tst/simple_tests/file/allow/ok_mmap_1.sd| 10 +-
+ parser/tst/simple_tests/file/allow/ok_mmap_2.sd| 12 ++--
+ 6 files changed, 29 insertions(+), 29 deletions(-)
+
+diff --git a/parser/tst/simple_tests/file/allow/ok_append_1.sd 
b/parser/tst/simple_tests/file/allow/ok_append_1.sd
+index b1085d2..c924614 100644
+--- a/parser/tst/simple_tests/file/allow/ok_append_1.sd
 b/parser/tst/simple_tests/file/allow/ok_append_1.sd
+@@ -4,11 +4,11 @@
+ # vim:syntax=apparmor
+ #
+ /usr/bin/foo {
+-  allow /bin/cat a,
+-  allow /bin/true ra,
+-  allow /bin/false ma,
++  allow /{usr/,}bin/cat a,
++  allow /{usr/,}bin/true ra,
++  allow /{usr/,}bin/false ma,
+   allow /lib/libc.so la,
+-  allow /bin/less ixa,
+-  allow /bin/more pxa,
++  allow /{usr/,}bin/less ixa,
++  allow /{usr/,}bin/more pxa,
+   allow /a uxa,
+ }
+diff --git a/parser/tst/simple_tests/file/allow/ok_embedded_spaces_1.sd 
b/parser/tst/simple_tests/file/allow/ok_embedded_spaces_1.sd
+index 345e482..4269d5e 100644
+--- a/parser/tst/simple_tests/file/allow/ok_embedded_spaces_1.sd
 b/parser/tst/simple_tests/file/allow/ok_embedded_spaces_1.sd
+@@ -2,6 +2,6 @@
+ #=EXRESULT PASS
+ # vim:syntax=apparmor
+ 
+-/bin/foo {
++/{usr/,}bin/foo {
+   allow "/abc\ def" r,
+ }
+diff --git a/parser/tst/simple_tests/file/allow/ok_embedded_spaces_2.sd 
b/parser/tst/simple_tests/file/allow/ok_embedded_spaces_2.sd
+index 3334f8d..1aba4c9 100644
+--- a/parser/tst/simple_tests/file/allow/ok_embedded_spaces_2.sd
 b/parser/tst/simple_tests/file/allow/ok_embedded_spaces_2.sd
+@@ -2,6 +2,6 @@
+ #=EXRESULT PASS
+ # vim:syntax=apparmor
+ 
+-/bin/foo {
++/{usr/,}bin/foo {
+   allow "/abc def" r,
+ }
+diff --git a/parser/tst/simple_tests/file/allow/ok_lock_1.sd 
b/parser/tst/simple_tests/file/allow/ok_lock_1.sd
+index defed2f..b1d57c5 100644
+--- a/parser/tst/simple_tests/file/allow/ok_lock_1.sd
 b/parser/tst/simple_tests/file/allow/ok_lock_1.sd
+@@ -4,15 +4,15 @@
+ # vim:syntax=apparmor
+ #
+ /usr/bin/foo {
+-  allow /bin/a k,
+-  allow /bin/b rk,
+-  allow /bin/c wk,
+-  allow /bin/d ak,
+-  allow /bin/e lk,
+-  allow /bin/e mk,
+-  allow /bin/f pxk,
+-  allow /bin/g Pxk,
+-  allow /bin/h ixk,
+-  allow /bin/i uxk,
+-  allow /bin/j Uxk,
++  allow /{usr/,}bin/a k,
++  allow /{usr/,}bin/b rk,
++  allow /{usr/,}bin/c wk,
++  allow /{usr/,}bin/d ak,
++  allow /{usr/,}bin/e lk,
++  allow /{usr/,}bin/e mk,
++  allow /{usr/,}bin/f pxk,
++  allow /{usr/,}bin/g Pxk,
++  allow /{usr/,}bin/h ixk,
++  allow /{usr/,}bin/i uxk,
++  allow /{usr/,}bin/j Uxk,
+ }
+diff --git a/parser/tst/simple_tests/file/allow/ok_mmap_1.sd 
b/parser/tst/simple_tests/file/allow/ok_mmap_1.sd
+index c02d76b..ae1df0f 100644
+--- a/parser/tst/simple_tests/file/allow/ok_mmap_1.sd
 b/parser/tst/simple_tests/file/allow/ok_mmap_1.sd
+@@ -4,10 +4,10 @@
+ # vim:syntax=apparmor
+ #
+ /usr/bin/foo {
+-  allow /bin/cat mix,
+-  allow /bin/true mpx,
+-  allow /bin/false mux,
++  allow /{usr/,}bin/cat mix,
++  allow /{usr/,}bin/true mpx,
++  allow /{usr/,}bin/false mux,
+   allow /lib/libc.so rwlm,
+-  allow /bin/less mUx,
+-  allow /bin/more mPx,
++  allow /{usr/,}bin/less mUx,
++  allow /{usr/,}bin/more mPx,
+ }
+diff --git a/parser/tst/simple_tests/file/allow/ok_mmap_2.sd 
b/parser/tst/simple_tests/file/allow/o

Bug#881569: gdb: FTBFS on hurd-i386

[Héctor Orón Martínez]

Hello Svante,

Thanks very much for the patches! I'll apply them if I need as I plan
to work on releasing 8.0.1 RSN.

2017-11-13 4:31 GMT+01:00 Svante Signell :
> Source: gdb
> Version: 8.0-1
> Severity: important
> Tags: patch
> User: debian-h...@lists.debian.org
> Usertags: hurd, experimental
>
> Hi,
>
> gdb FTBFS on GNU/Hurd due to three reasons:
>
> - Usage of PATH_MAX in gdb/remote.c
>
> - Recent changes in Hurd failing the build of gdb/gnu-nat.c
>
> - A name clash of struct thread_info and the kernel function thread_info()
> included in gdb/thread.c and gdb/python/py-record-btrace.c.
>
> Include paths:
> 1) defs.h: #include "gdbarch.h": struct thread_info
>
> 2) defs.h: #include "nm.h":#include :#include 
> where the function thread_info() is defined:
>
> extern kern_return_t thread_info
> (
>  mach_port_t target_thread,
>  int flavor,
>  thread_info_t thread_info_out,
>  mach_msg_type_number_t *thread_info_outCnt
> );
>
> The attached patches fixes these issues:
> gdb-PATH_MAX.patch
> gnu-nat.c.patch
> struct-thread_info.patch
>
> Thanks :)



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#881527: qemu: FTCBFS due to broken cross build depend on glusterfs-common

[Héctor Orón Martínez]

Hello,

2017-11-12 21:21 GMT+01:00 Michael Tokarev <m...@tls.msk.ru>:
> Control: tag -1 + moreinfo
>
> 12.11.2017 22:14, Héctor Orón Martínez wrote:
>> Source: qemu
>> Version: 1:2.10.0+dfsg-2
>> Severity: normal
>>
>> Dear Maintainer,
>>
>>   Your package fails to satisfy cross build dependency installability due to 
>> glusterfs-common not being installable via multiarch:
>>   * https://bootstrap.debian.net/cross_all/qemu.html
>>   * DebianBug#881526
>>
>>   You might want to consider disabling glusterfs-common build dependency for 
>> the cross build case, otherwise your package seems to cross build fine.
>
> I'm not sure what's the problem here and why this bugreport exists in the 
> first place.
>
> First, what is "the cross build case", which case is that and why should we 
> care about it?

There are efforts to cross build Debian packages from sources, which
might be beneficial for bootstraping new/old architectures among other
use cases.
I think it woud be nice to be able to cross build QEmu (for new comers
better experience) as explained at:
  
http://suihkulokki.blogspot.com/2017/06/cross-compiling-with-debian-stretch.html

> And second, why should we disable some option(s) and build a broken package 
> in case some
> dependent package is buggy?  I think it is better to fix the buggy package 
> than to introduce
> bugs in other packages.

At your consideration, the option is only to be temporarily disabled
*in the cross case* until #881526 gets properly fixed. Due to
glusterfs-common being uninstallable, I was toying with cross build
case and found QEmu disables this option for Ubuntu distribution and
attempted a successful build without this option. In practical means,
that only needs to add a  tag after build dependency (I could
provide a tested patch if you need). However, we might leave the cross
build dependency in same way as native build and leave this bug open
to track cross buildability of the package.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#881527: qemu: FTCBFS due to broken cross build depend on glusterfs-common

[Héctor Orón Martínez]

Source: qemu
Version: 1:2.10.0+dfsg-2
Severity: normal

Dear Maintainer,

  Your package fails to satisfy cross build dependency installability due to 
glusterfs-common not being installable via multiarch:
  * https://bootstrap.debian.net/cross_all/qemu.html
  * DebianBug#881526

  You might want to consider disabling glusterfs-common build dependency for 
the cross build case, otherwise your package seems to cross build fine.

Regards

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_AD.utf8, LC_CTYPE=ca_AD.utf8 (charmap=UTF-8), LANGUAGE=ca_AD:ca 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#881526: glusterfs-common: split package into many (-dev,python-,-bin/-tools/-utils)

[Héctor Orón Martínez]

Package: glusterfs-common
Version: 3.12.2-2
Severity: normal

Dear Maintainer,

  Attempting to cross build QEmu, when installing cross build
dependencies, it results in uninstallability issues with
glusterfs-common. Main issue we have here is that package needs to be
splitted in different packages to be able to mark them accordingly
Multi-Arch: same or foreign. The package contains:
  * headers and .a need to go into -dev shared libraries named libfooN
(I believe those need to be marked multiarch same)
  * python modules need to be shipped into python-foo package
  * tools need to go into -bin/-tools/-utils (I believe that should be
marked multiarch foreign)

Regards

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_AD.utf8, LC_CTYPE=ca_AD.utf8 (charmap=UTF-8),
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#881348: libgcc-7-dev-armhf-cross: unmet dependencies

[Héctor Orón Martínez]

Hello,

2017-11-10 20:23 GMT+01:00 Matthias Klose <d...@debian.org>:
> On 10.11.2017 16:53, Héctor Orón Martínez wrote:
>> Source: gcc-7-cross
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> In armhf chroot, trying to install cross compiler from amd64, using
>> multiarch, I get:
>>
>> The following packages have unmet dependencies:
>> gcc-7-arm-linux-gnueabihf:amd64 : Depends:
>> libgcc-7-dev-armhf-cross:amd64 (>= 7.2.0-11cross1)
>>
>> I have been suggested at #debian-bootstrap channel that is a bug and
>> libgcc-7-dev-armhf-cross should be marked multiarch foreign.
>
> why would you want to install that package in an armhf chroot?

I was trying to experiment with cross environment setup and have
emulated chroot with cross compilers installed (via multiarch), and
yet to see if packages cross build sanely.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#881348: libgcc-7-dev-armhf-cross: unmet dependencies

[Héctor Orón Martínez]

Source: gcc-7-cross
Severity: normal

Dear Maintainer,

In armhf chroot, trying to install cross compiler from amd64, using
multiarch, I get:

The following packages have unmet dependencies:
gcc-7-arm-linux-gnueabihf:amd64 : Depends:
libgcc-7-dev-armhf-cross:amd64 (>= 7.2.0-11cross1)

I have been suggested at #debian-bootstrap channel that is a bug and
libgcc-7-dev-armhf-cross should be marked multiarch foreign.

Regards

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/16 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8),
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#881164: nvidia-graphics-drivers: please update to new upstream release (387.22)

[Héctor Orón Martínez]

Hello,

2017-11-08 14:37 GMT+01:00 Luca Boccassi <bl...@debian.org>:
> On Wed, 2017-11-08 at 13:11 +0100, Héctor Orón Martínez wrote:

> Thanks for the patch! But we already have a branch updated for 387.22
> on SVN:
>
> https://anonscm.debian.org/viewvc/pkg-nvidia/packages/nvidia-graphics-drivers/branches/387/

Ugh! I checked svn, but not in branches but trunk, doh!

> If you'd like to help us maintain these packages it would be very
> welcome - I'd suggest to keep an eye on the SVN repos to avoid
> duplicated effort.
>
> In terms of uploading, I think the plan is to move 384 to unstable, as
> it's the new LTS branch, and then that will clear the way for newer
> short term or beta releases to be uploaded to experimental.

Sounds reasonable! Thanks

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Bug#881164: nvidia-graphics-drivers: 387.22 update patch

[Héctor Orón Martínez]

Hello,

  Of course I forgot to attach the patch, here it is now.
  Please review it and do not apply it blindly.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.
diff -Nru nvidia-graphics-drivers-384.90/debian/changelog nvidia-graphics-drivers-387.22/debian/changelog
--- nvidia-graphics-drivers-384.90/debian/changelog	2017-10-30 02:16:27.0 +0100
+++ nvidia-graphics-drivers-387.22/debian/changelog	2017-11-08 14:11:38.0 +0100
@@ -1,3 +1,9 @@
+nvidia-graphics-drivers (387.22-0.1) UNRELEASED; urgency=medium
+
+  * New upstream release
+
+ -- Héctor Orón Martínez   Wed, 08 Nov 2017 14:11:38 +0100
+
 nvidia-graphics-drivers (384.90-2) experimental; urgency=medium
 
   * Merge changes from 375.82-7.  (Closes: #876766)
diff -Nru nvidia-graphics-drivers-384.90/debian/copyright nvidia-graphics-drivers-387.22/debian/copyright
--- nvidia-graphics-drivers-384.90/debian/copyright	2017-07-01 17:38:28.0 +0200
+++ nvidia-graphics-drivers-387.22/debian/copyright	2017-11-08 12:09:59.0 +0100
@@ -168,6 +168,11 @@
  OF THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF NVIDIA HAS
  BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
  .
+ 6.3  Specific Use.  SOFTWARE is licensed only for use with NVIDIA products.
+ Customer’s use of NVIDIA products with any other firmware is at its own
+ risk and may cause an NVIDIA product to become non-compliant with certain
+ of its certification markings.
+ .
  7.  MISCELLANEOUS
  .
  The United Nations Convention on Contracts for the International
diff -Nru nvidia-graphics-drivers-384.90/debian/libegl1-nvidia.symbols nvidia-graphics-drivers-387.22/debian/libegl1-nvidia.symbols
--- nvidia-graphics-drivers-384.90/debian/libegl1-nvidia.symbols	2017-07-01 17:38:29.0 +0200
+++ nvidia-graphics-drivers-387.22/debian/libegl1-nvidia.symbols	2017-11-08 12:50:48.0 +0100
@@ -12,14 +12,21 @@
  eglBindAPI@Base 331
  eglBindTexImage@Base 331
  eglChooseConfig@Base 331
+ eglClientWaitSync@Base 387.22
  eglCopyBuffers@Base 331
  eglCreateContext@Base 331
+ eglCreateImage@Base 387.22
  eglCreatePbufferFromClientBuffer@Base 331
  eglCreatePbufferSurface@Base 331
  eglCreatePixmapSurface@Base 331
+ eglCreatePlatformPixmapSurface@Base 387.22
+ eglCreatePlatformWindowSurface@Base 387.22
+ eglCreateSync@Base 387.22
  eglCreateWindowSurface@Base 331
  eglDestroyContext@Base 331
+ eglDestroyImage@Base 387.22
  eglDestroySurface@Base 331
+ eglDestroySync@Base 387.22
  eglGetConfigAttrib@Base 331
  eglGetConfigs@Base 331
  eglGetCurrentContext@Base 331
@@ -27,7 +34,9 @@
  eglGetCurrentSurface@Base 331
  eglGetDisplay@Base 331
  eglGetError@Base 331
+ eglGetPlatformDisplay@Base 387.22
  eglGetProcAddress@Base 331
+ eglGetSyncAttrib@Base 387.22
  eglInitialize@Base 331
  eglMakeCurrent@Base 331
  eglQueryAPI@Base 331
@@ -43,6 +52,7 @@
  eglWaitClient@Base 331
  eglWaitGL@Base 331
  eglWaitNative@Base 331
+ eglWaitSync@Base 387.22
 #MISSING: 384# (arch=i386)glvnd_asprintf@Base 375
 #MISSING: 384# (arch=i386)glvnd_byte_swap16@Base 375
 #MISSING: 384# (arch=i386)glvnd_vasprintf@Base 375
diff -Nru nvidia-graphics-drivers-384.90/debian/libegl-nvidia0.symbols nvidia-graphics-drivers-387.22/debian/libegl-nvidia0.symbols
--- nvidia-graphics-drivers-384.90/debian/libegl-nvidia0.symbols	2017-07-01 17:38:29.0 +0200
+++ nvidia-graphics-drivers-387.22/debian/libegl-nvidia0.symbols	2017-11-08 12:50:48.0 +0100
@@ -1,4 +1,5 @@
 libEGL_nvidia.so.0 #PACKAGE# #MINVER#
+ NvEglApiGetAccess@Base 387.22
  NvEglDevtoolsQuery@Base 384
  NvEglRegClientApi@Base 378
  __egl_Main@Base 355
diff -Nru nvidia-graphics-drivers-384.90/debian/libgl1-nvidia-glx.symbols nvidia-graphics-drivers-387.22/debian/libgl1-nvidia-glx.symbols
--- nvidia-graphics-drivers-384.90/debian/libgl1-nvidia-glx.symbols	2017-09-05 11:02:25.0 +0200
+++ nvidia-graphics-drivers-387.22/debian/libgl1-nvidia-glx.symbols	2017-11-08 14:00:40.0 +0100
@@ -3,9 +3,12 @@
  glAlphaToCoverageDitherControlNV@Base 370
  glBufferStorageMemEXT@Base 384.69
  glConservativeRasterParameteriNV@Base 367
+ glClearTexImageEXT@Base 387.22
+ glClearTexSubImageEXT@Base 387.22
  glCreateMemoryObjectsEXT@Base 384.69
  glDebugControlNVX@Base 177
  glDeleteMemoryObjectsEXT@Base 384.69
+ glDeleteQueryResourceTagNV@Base 387.22
  glDeleteSemaphoresEXT@Base 384.69
  glDepthRangeArrayfvOES@Base 378
  glDepthRangeIndexedfOES@Base 378
@@ -15,6 +18,7 @@
  glGenSemaphoresEXT@Base 384.69
  glGetFloati_vOES@Base 378
  glGetMemoryObjectParameterivEXT@Base 384.69
+ glGenQueryResourceTagNV@Base 387.22
  glGetSemaphoreParameterui64vEXT@Base 384.69
  glGetUnsignedBytei_vEXT@Base 384.69
  glGetUnsignedBytevEXT@Base 384.69
@@ -25,9 +29,14 @@
  glIsMemoryObjectEXT@Base 384.69
  glIsSemaphoreEXT@Base 384.69
  glLogTokenFlushNVX@Base 364
+ glMaxShaderCompilerThreadsKHR@Base 387.22
  glMemoryObjectParameterivEXT@Base 384.69
+ glMultiDrawArraysIndirectCount@Base 387.22
+ 

Bug#881164: nvidia-graphics-drivers: please update to new upstream release (387.22)

[Héctor Orón Martínez]

Source: nvidia-graphics-drivers
Severity: wishlist
Tags: patch

Dear Maintainer,

  Could you please consider updating your package to 387.22?
  Please find patch attached

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_AD.utf8, LC_CTYPE=ca_AD.utf8 (charmap=UTF-8), LANGUAGE=ca_AD:ca 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#877951: lists.debian.org: kill debian-ports mailing list

[Héctor Orón Martínez]

Package: lists.debian.org
Severity: wishlist

Dear Maintainer,

  debian-ports mailing list, actually not a mailing list but a can of worms
  as it spams all other debian-$architecture (ports) mailing lists, should be
  imho killed. Not only because we are getting several copies of the same
  email, but also because it can be confused with unofficial Debian ports
  maintenance mailing list (recently created request for debian-ports-devel).

  Do you think it is time for that to happen?

Best Regards,

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

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)