Bug#1069679: Debian Bugs information: logs for Bug#1069679

[Hector Oron]

Hello Mike,

On Fri, 24 May 2024 at 08:57, Mike Gabriel  wrote:

> If noone plans to fix Ofono in Debian within the next 1-2 weeks, I'd
> like to do a team upload. In that case, could any of you give me
> access to
> https://salsa.debian.org/telepathy-team (or just the ofono repo in there).

I tried but I do not have enough permissions to add you. You'll need
Emilio or Laurent for that.

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

Bug#1037186: debian-installer: bookworm d-i graphics are not shown on Raptor system

[Hector Oron]

Hello

El mié, 7 jun 2023, 13:03, Cyril Brulebois  escribió:

> Hector Oron  (2023-06-07):
> > and Timonthy was able to test that. I could expand the change to ppc64
> > (be) and cdrom targets and test that.
> >
> > Note, the ppc64el installer images are unusable with that change, at
> > least on the Raptor systems
>
> I don't think you answered my question about fbdev.
>

I defer to Timothy since I do not have a machine myself, but since Raptorcs
is Debian partner I had assumed we - Debian - would like to ship a working
product that works for them.

Thanks for your support

>

Bug#1037186: debian-installer: bookworm d-i graphics are not shown on Raptor system

[Hector Oron]

Hello,

  To be honest, I only updated ppc64el netboot image with the following patch:

--- a/build/pkg-lists/netboot/ppc64el.cfg
+++ b/build/pkg-lists/netboot/ppc64el.cfg
@@ -1,5 +1,6 @@
 input-modules-${kernel:Version}
 nic-modules-${kernel:Version}
+fb-modules-${kernel:Version} ?
 usb-modules-${kernel:Version}
 virtio-modules-${kernel:Version} ?

I built the installer posted at:
https://people.debian.org/~zumbi/netboot_ppc64el/

and Timonthy was able to test that. I could expand the change to ppc64
(be) and cdrom targets and test that.

Note, the ppc64el installer images are unusable with that change, at
least on the Raptor systems, and since the change only affects power
package lists, I'd consider it as low impact/risk. I know we are close
to a release, and it is very bad timing, however if it can be merged,
it'd be great, otherwise we'll have to wait until the first point
release.

Thanks for your support.

On Wed, 7 Jun 2023 at 12:29, Cyril Brulebois  wrote:
>
> Hi,
>
> Hector Oron Martinez  (2023-06-07):
> > We found latest installer for bookworm is missing ast DRM kernel
> > module, causing graphical failure on ppc64el Raptor machines. Could
> > you please consider the following change or similar for the
> > debian-installer bookworm release.
> >
> >   
> > https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/34
>
> Thanks for the patch, but this is too late. We can consider that for
> unstable, and later on via a point release.
>
> I know for a fact we have fbdev in ppc64el builds, as we've suffered a
> regression there (#1033058, for which someone still needs to find a real
> fix on the kernel side, hint hint wink wink); isn't that generic driver
> sufficient to get some basic output?
>
> Also, I don't understand what's going on with the build/Makefile part:
>  1. This is a temporary workaround for 3 architectures that run into
> issues under UEFI/SB, which isn't quite relevant for ppc64el. (The
> idea was to avoid having to re-upload linux and linux-signed-* for
> just a few additions to the fb-modules udeb.)
>  2. If you look at the following commit, I suppose you'll get the very
> same impression as I have: this merge request is very likely to
> trigger a direct FTBFS on ppc64el.
>   
> https://salsa.debian.org/installer-team/debian-installer/-/commit/32e4d58c263fc5454067a7217ee7103cfb12bc1b
>
>
> Cheers,
> --
> Cyril Brulebois (k...@debian.org)<https://debamax.com/>
> D-I release manager -- Release team member -- Freelance Consultant



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

Bug#1037186: debian-installer: bookworm d-i graphics are not shown on Raptor system

[Hector Oron Martinez]

Source: debian-installer
Version: 20230526
Severity: important
X-Debbugs-Cc: tpear...@raptorcs.com, zu...@debian.org

Hello,

We found latest installer for bookworm is missing ast DRM kernel module, 
causing graphical failure on ppc64el Raptor machines. Could you please consider 
the following change or similar for the debian-installer bookworm release.

  https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/34

Regards

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_ES:ca
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1036623: libclang-common-16-dev: missing LLVM_VERSION_FULL in include path

[Hector Oron Martinez]

Package: libclang-common-16-dev
Version: 1:16.0.4-1~exp1
Severity: normal
X-Debbugs-Cc: zu...@debian.org

Hello,

  On clang 16 the include files are broken links:

$ ls -l /usr/include/clang/16*/include
lrwxrwxrwx 1 root root 45 17 de maig  09:25 /usr/include/clang/16.0.4/include 
-> ../../../lib/llvm-16/lib/clang/16.0.4/include
lrwxrwxrwx 1 root root 45 17 de maig  09:25 /usr/include/clang/16/include -> 
../../../lib/llvm-16/lib/clang/16.0.4/include

  Since /usr/lib/llvm-16/lib/clang/16 exists but not the
  /usr/lib/llvm-16/lib/clang/16.0.4 path.

$ LANG=C ls -l /usr/lib/llvm-16/lib/clang/16.0.4/
ls: cannot access '/usr/lib/llvm-16/lib/clang/16.0.4/': No such file or 
directory

Regards

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_ES:ca
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libclang-common-16-dev depends on:
ii  libllvm16  1:16.0.4-1~exp1

Versions of packages libclang-common-16-dev recommends:
ii  libclang-rt-16-dev  1:16.0.4-1~exp1

libclang-common-16-dev suggests no packages.

-- no debconf information

Bug#1035515: [pre-approval] unblock: gdb/13.1-2.1

[Hector Oron]

Hello,

  While I agree we should get this fixed on bookworm, I believe to be
able to unblock a package, the package should exist in the archive.

  Since you have not uploaded the package yet, are you fine if I do a
regular upload with the patch, then use this unblock request to add
the package to bookworm.

Regards

On Thu, 4 May 2023 at 16:21, Emanuele Rocca  wrote:
>
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: g...@packages.debian.org, debian-...@lists.debian.org
> Control: affects -1 + src:gdb
>
> Hello release team,
>
> Please unblock package gdb.
>
> [ Reason ]
> The most basic functionality of GDB, namely debugging an hello world C
> program, is currently broken in Bookworm for arm64 systems with pointer
> authentication enabled. See https://bugs.debian.org/1034611.
>
> There is a patch merged upstream addressing the issue [0]. I've tested
> it on a arm64 system and can confirm that it works. See also:
> https://bugs.debian.org/1034611#15
>
> I've prepared an NMU, not yet uploaded. Please find the debdiff
> attached.
>
> [ Impact ]
> GDB entirely unusable for most arm64 users.
>
> [ Tests ]
> Upstream test suite passes. Manually verified that #1034611 can be
> reproduced with gdb 13.1-2 from Bookworm, and it cannot with the
> proposed changes.
>
> [ Risks ]
> Minimal, the patch is small and targeted. Additionally, it only touches
> arm64-specific code.
>
> [ Checklist ]
>   [x] all changes are documented in the d/changelog
>   [x] I reviewed all changes and I approve them
>   [x] attach debdiff against the package in testing
>
> unblock gdb/13.1-2.1
>
> Thanks,
>   Emanuele
>
> [0] 
> https://sourceware.org/git/?p=binutils-gdb.git;a=patch;h=b3eff3e15576229af9bae026c5c23ee694b90389



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

Bug#1029814: ixp4xx-microcode: no longer useful, ixp4xx support dropped in 2014

[Hector Oron]

Hello,

  This firmware was used by slugs or NSLU-2,
  https://www.cyrius.com/debian/nslu2/install/

  Those devices were great to bootstrap and play with armel port.

  Due to low ram and flash it is no longer capable to run Debian. Therefore
I agree this package can be marked for removal.

  Userland package was removed time ago:
  https://tracker.debian.org/pkg/nslu2-utils

Regards

Bug#1000250: Dependency on patatt

[Hector Oron]

Hello,

On Sat, 20 Nov 2021 at 07:33, Anuradha Weeraman  wrote:
> Patatt (https://git.kernel.org/pub/scm/utils/patatt/patatt.git) is now
> in Debian unstable and patch attestation functionality has been moved
> to it, so requesting that a dependency be included in b4 for patatt.

This is now done, however, the recommended patatt version is patatt>=0.5,<2.0.
I'll update the package to versioned dependency once this is updated
in unstable.

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

Bug#1010064: salsa: please push the pristine-tar branch

[Hector Oron]

Hello Dmitry,

On Sat, 23 Apr 2022 at 15:57, Dmitry Baryshkov  wrote:
>
> Source: device-tree-compiler
> Version: 1.6.1-1
> Severity: normal
>
> Recent push to dtc sources to the repo at salsa includes the
> debian/gbp.conf file. This file contains the "pristine-tar = True"
> config option, however the repo does not contain the pristine-tar
> branch. Thus rebuilding the package from the repo without passing
> additional options to gbp is impossible.
>
> Please push the prisine-tar branch to the salsa repo.

I do not have a pristine-tar branch on my system, but you can grab the
upstream tarball from the Debian mirror. I'll drop pristine-tar from
gbp.conf to allow gbp to create a tarball from the upstream tag.

I hope that works for you.

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

Bug#1008323: bpftrace: fix FTBFS

[Hector Oron]

Hello,

  According to https://github.com/iovisor/bpftrace/issues/2068

  I applied the following patch to make the package build:

--- bpftrace-0.14.1.orig/src/btf.cpp
+++ bpftrace-0.14.1/src/btf.cpp
@@ -225,7 +225,7 @@ std::string BTF::c_def(const std::unorde
   char err_buf[256];
   int err;

-  dump = btf_dump__new(btf, nullptr, , dump_printf);
+  dump = btf_dump__new_deprecated(btf, nullptr, , dump_printf);
   err = libbpf_get_error(dump);
   if (err)
   {
@@ -496,7 +496,7 @@ std::unique_ptr BTF::get_a
   char err_buf[256];
   int err;

-  dump = btf_dump__new(btf, nullptr, , dump_printf);
+  dump = btf_dump__new_deprecated(btf, nullptr, , dump_printf);
   err = libbpf_get_error(dump);
   if (err)
   {
@@ -554,7 +554,7 @@ std::map BTF::get_all_struc
   char err_buf[256];
   int err;

-  dump = btf_dump__new(btf, nullptr, , dump_printf);
+  dump = btf_dump__new_deprecated(btf, nullptr, , dump_printf);
   err = libbpf_get_error(dump);
   if (err)
   {


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

Bug#1009109: fzf: FTBFS missing build dependency on golang-golang-x-term-dev

[Hector Oron]

Source: fzf
Version: 0.29.0-1
Severity: important

Hello,

fzf package fails to build from source as it is missing a dependency
on golang-golang-x-term-dev

diff -Nru fzf-0.29.0/debian/control fzf-0.29.0/debian/control
--- fzf-0.29.0/debian/control2022-01-08 11:13:51.0 -0500
+++ fzf-0.29.0/debian/control2022-04-07 06:19:10.0 -0400
@@ -11,13 +11,14 @@
 Build-Depends: debhelper-compat (= 13),
dh-exec,
dh-golang,
-   golang-github-rivo-uniseg-dev,
+   golang-github-rivo-uniseg-dev,
golang-github-mattn-go-isatty-dev,
golang-github-mattn-go-runewidth-dev,
golang-github-mattn-go-shellwords-dev,
golang-github-saracen-walker-dev,
golang-go (>= 1.5),
-   golang-golang-x-crypto-dev
+   golang-golang-x-crypto-dev,
+   golang-golang-x-term-dev,
 Rules-Requires-Root: no
 XS-Go-Import-Path: github.com/junegunn/fzf

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

Bug#988647: crash: please update to new upstream release

[Hector Oron]

Hello,

  Since release has now happened, could you move 7.3 to bookworm/sid
and upload newer version 8.0.0 needed for linux kernel 5.15.

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

Bug#991631: nfs-utils: please update to newer upstream version

[Hector Oron]

Hello Anibal,

El ds., 4 de set. 2021, 9:33, Anibal Monsalve Salazar 
va escriure:

> On Thu, Jul 29, 2021, 21:42 Salvatore Bonaccorso 
> wrote:
>
>> Control: forcemerge 917706 991631
>>
>> Hi Hector,
>>
>> On Thu, Jul 29, 2021 at 12:21:47PM +0200, Hector Oron wrote:
>> > Package: src:nfs-utils
>> > Severity: wishlist
>> >
>> > Dear Maintainer,
>> >
>> > Hello,
>> >
>> >   nfs-utils package is quite old, even in SID, what are the plans for
>> > this package? Could it be updated to a more recent upstream version?
>>
>> It should absolutely, there was an attempt to try to do this before
>> the bullseye release, but it failed, WIP in
>> https://salsa.debian.org/kernel-team/nfs-utils/-/merge_requests/3 .
>> Some help welcome!
>>
>> Debian is lacking too much behind. For after the bullseye release this
>> shouldbe tackled ASAP, we should not land in the same situation again
>> for bookworm.
>>
>> Regards,
>> Salvatore
>>
>
> Hello Salvatore, Héctor,
>
> Just to let you know that I have been working with version 2.5.4 and the
> 2.5.5 RCs for the last few days, almost full time. Currently, I'm reviewing
> once again all the patches.
>

Excellent! I worked on it sometime, but my work is not ready, I should post
it once it is ready for review and testing.

Anibal, do you have some WIP you can publish (on salsa) for review and/or
testing?

I feel we are pretty close for a real update. :-)

Thanks all for the work


> Kind regards,
>
> Aníbal
>
>>

Bug#991631: nfs-utils: please update to newer upstream version

[Hector Oron]

Package: src:nfs-utils
Severity: wishlist

Dear Maintainer,

Hello,

  nfs-utils package is quite old, even in SID, what are the plans for
this package? Could it be updated to a more recent upstream version?

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

Bug#989691: valgrind: please release 3.17.0 for DWARF 5 support

[Hector Oron]

Package: valgrind
Version: 3.17.0
Severity: wishlist

Dear maintainer,

  Please consider packaging (even to experimental) latest upstream
release, currently being 3.17.0, which turns out to be a DWARF 5
dependency I would like to use.

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

Bug#988648: systemtap: please package new upstream release

[Hector Oron]

Package: systemtap
Version: 4.5
Severity: wishlist

Dear maintainer,

  Please consider packaging (even to experimental) latest upstream
release, currently being 4.5, which turns out to be a linux kernel
dependency I would like to use.

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

Bug#988647: crash: please update to new upstream release

[Hector Oron]

Package: crash
Version: 7.3.0
Severity: wishlist

Dear maintainer,

  It would be really nice if you could consider updating crash to
latest upstream release, currently being 7.3.0, which turns out to be
5.10 linux kernel dependency I would like to use.

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

Bug#984462: RFH: open-build-service

[Hector Oron]

Hello,

On Wed, 3 Mar 2021 at 21:18, Andrej Shadura  wrote:

> While I don’t work on the OBS package in Debian, I know about the state
> of the package in Debian right now: the team, and most notably the main
> maintainer, Andrew Lee, need help to maintain this package, as it
> requires a lot of work due to a combination of Ruby / Ruby on Rails,
> Perl and shell bits. Ruby parts specifically is a pain point, since
> there’s a lot of gems this package depends on and updating one or
> multiple of them can break OBS in ways the upstream didn’t think about.
>
> The package has already missed Buster and Bullseye, and if the situation
> doesn’t improve, it may result in a removal at some point.

For the Ruby gems issue, bundling those as in Kubernetes resolution[0]
might be a way forward.

[0] https://lwn.net/Articles/835599/

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

Bug#973355: use plain debhelper for the packaging

[Hector Oron]

Hello,

El dg., 6 de des. 2020, 16:28, Matthias Klose  va escriure:

> On 12/6/20 4:24 PM, Hector Oron wrote:
> > Hello
> >
> > El dg., 6 de des. 2020, 11:03, Matthias Klose  va
> escriure:
> >
> >> Now that 10.1 migrated to testing, I'm uploading that patch to
> DELAYED/5.
> >> I'll
> >> check for regressions, and if the package looks ok, I'll provide a
> second
> >> patch
> >> for the packaging cleanup.
> >>
> >
> > That's fine. Thanks.
>
> even without the delay?
>

Yes, if it needs to go into bullseye better earlier than later.

>

Bug#973355: use plain debhelper for the packaging

[Hector Oron]

Hello

El dg., 6 de des. 2020, 11:03, Matthias Klose  va escriure:

> Now that 10.1 migrated to testing, I'm uploading that patch to DELAYED/5.
> I'll
> check for regressions, and if the package looks ok, I'll provide a second
> patch
> for the packaging cleanup.
>

That's fine. Thanks.

>

Bug#976634: systemtap-4.4: backport from upstream PR27001

[Hector Oron]

Package: src:systemtap-4.4
Version: 4.4-1
Severity: wishlist

Hello,

  Please backport from upstream fix for PR27001:
  - 
https://sourceware.org/git/?p=systemtap.git;a=commit;h=0d80048e02ecf6876c9f9ebeea387af9fb2a8051

Regards

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

Bug#974577: boost1.74: remove usage of deprecated headers

[Hector Oron]

Package: src:boost1.74
Version:1.74.0-1
Severity: wishlist

Hello,

  Please include the following patches to remove usage of deprecated headers:
  - 
https://github.com/boostorg/graph/commit/e4e12158e78157397254505f6cbae688e3e3174f.patch
  - 
https://github.com/boostorg/range/commit/486c74fbeba9ee9975e6d68e974230ec8ec22fb0.patch

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

Bug#970134: libweston-9-dev: missing (unversioned) Breaks+Replaces: libweston-8-dev

[Hector Oron]

Hello,

On Sat, 12 Sep 2020 at 11:21, Andreas Beckmann  wrote:
>
> Package: libweston-9-dev
> Version: 9.0.0-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
>
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>
> >From the attached log (scroll to the bottom...):
>
>   Preparing to unpack .../libweston-9-dev_9.0.0-1_amd64.deb ...
>   Unpacking libweston-9-dev (9.0.0-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/libweston-9-dev_9.0.0-1_amd64.deb (--unpack):
>trying to overwrite '/usr/lib/x86_64-linux-gnu/weston/libexec_weston.so', 
> which is also in package libweston-8-dev 8.0.0-1
>   Errors were encountered while processing:
>/var/cache/apt/archives/libweston-9-dev_9.0.0-1_amd64.deb
>
> Since libweston-8-dev is gone, the Breaks+Replaces can be unversioned.

Thanks for the report, I have been investigating a bit this issue,
libexec_weston was introduced in weston_8, it was created for the
purpose of the reset of the test suite so it doesn't need to exec()
but just load libexec_weston.so. libexec_weston is not something
anyone else should develop against, it is only needed by weston
binary.

I'll look into dropping
/usr/lib/x86_64-linux-gnu/weston/libexec_weston.so since weston is
linked to /usr/lib/x86_64-linux-gnu/weston/libexec_weston.so.0 which
should be shipped in the weston package.

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

Bug#960788: ITP: alsa-sof-firmware -- Intel SOF audio firmware and topology

[Hector Oron]

Hello intrigeri,

Missatge de intrigeri  del dia ds., 5 de set.
2020 a les 8:21:

> So we could close this ITP (#960788, since in the end no new source
> package will be introduced) in favor of #949019 and #962134, which
> could themselves be merged, right? I'm happy to do the BTS paperwork
> if this makes sense to you folks :)

Sounds great to me with thanks!

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

Bug#960788: ITP: alsa-sof-firmware -- Intel SOF audio firmware and topology

[Hector Oron]

+m...@debian.org

Hello,

Missatge de Jordi Mallach  del dia dj., 3 de set.
2020 a les 16:48:

> After claiming it and looking at the source, I resolved this probably
> belongs as part of linux-firmware or whatever the source name is, as
> Ubuntu did. zumbi@ has been talking to the kernel people about this but
> right now I'm unsure what the status is.

That is correct, we have been discussing it at the #debian-kernel IRC
channel and Maximilian was planning to add this SOF-bin to the
firmware-nonfree package.
I believe Lenovo is supportive and is going to send a machine to
Maximilian to be able to test it out.

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

Bug#954239: RFP: python-b4 -- helper utility to work with patches made available via a public-inbox archive

[Hector Oron]

Hello Salvatore,

Missatge de Salvatore Bonaccorso  del dia dj., 19
de març 2020 a les 7:18:
>
> Package: wnpp
> Severity: wishlist
>
> * Package name: python-b4
>   Version : v0.3.3 (or later)
>   Upstream Author : Konstantin Ryabitsev 
> * URL : https://git.kernel.org/pub/scm/utils/b4/b4.git
> * License : GPL
>   Programming Lang: Python
>   Description : helper utility to work with patches made available via a 
> public-inbox archive
>
> This is a helper utility to work with patches made available via a
> public-inbox archive like lore.kernel.org. It is written to make it
> easier to participate in a patch-based workflows, like those used in
> the Linux kernel development.
>
> For the package name, not sure if python-b4 or b4 is more appropriate.

I have done initial packaging at
  https://salsa.debian.org/zumbi/python-b4

If you are fine with it, I'll upload it, so it can go through NEW
queue and move it into Debian Python Modules Team (eventually).

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

Bug#950176: source-highlight: FTBFS on all architectures other than amd64

[Hector Oron]

Dear maintainer,

  I have uploaded a fix that worked for me on zelenka (s390) porterbox
to delay queue (7 days). Feel free to take action as needed. I am
attaching the Debian diff for the NMU.

diff -Nru source-highlight-3.1.9/debian/changelog
source-highlight-3.1.9/debian/changelog
--- source-highlight-3.1.9/debian/changelog2020-01-17
17:58:28.0 +0100
+++ source-highlight-3.1.9/debian/changelog2020-03-02
11:16:32.0 +0100
@@ -1,3 +1,10 @@
+source-highlight (3.1.9-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix builds on non intel architectures. (Closes: #950176)
+
+ -- Héctor Orón Martínez   Mon, 02 Mar 2020 11:16:32 +0100
+
 source-highlight (3.1.9-1) unstable; urgency=medium

   * New maintainer (closes: #948230)
diff -Nru source-highlight-3.1.9/debian/rules
source-highlight-3.1.9/debian/rules
--- source-highlight-3.1.9/debian/rules2020-01-17 17:58:28.0 +0100
+++ source-highlight-3.1.9/debian/rules2020-03-02 11:14:31.0 +0100
@@ -17,4 +17,4 @@
 mv $(DESTDIR)/usr/bin/src-hilite-lesspipe.sh
$(DESTDIR)/usr/share/source-highlight/
 mv $(DESTDIR)/usr/bin/source-highlight-esc.sh
$(DESTDIR)/usr/share/source-highlight/
 dh_install
-rm $(DESTDIR)/usr/lib/x86_64-linux-gnu/libsource-highlight.la
+rm $(DESTDIR)/usr/lib/$(DEB_TARGET_MULTIARCH)/libsource-highlight.la

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

Bug#950898: ansible/buster: flatpak_remote: IndexError: list index out of range

[Hector Oron Martinez]

Package: ansible
Version: 2.7.7+dfsg-1
Severity: important
Tags: patch

Hello,

Note this issue only happens in stable, Buster 10.2 with ansible 2.7.7

When using ansible with flatpak_remote, it breaks. The following snippet:
```
- name: Add the flathub flatpak repository remote to the user 
installation
  flatpak_remote:
name: flathub
state: present
flatpakrepo_url: https://dl.flathub.org/repo/flathub.flatpakrepo
method: user
```

causes:

```
TASK [Add the flathub flatpak repository remote to the user installation] 
*
fatal: [127.0.0.1]: FAILED! => {"changed": false, "module_stderr": 
"/home/zumbi/.ansible/tmp/ansible-tmp-1581109559.271161-112064566806002/AnsiballZ_flatpak_remote.py:17:
 DeprecationWarning: the imp module is deprecated in favour of importlib; see 
the module's documentation for alternative uses\n  import imp\nTraceback (most 
recent call last):\n  File 
\"/home/zumbi/.ansible/tmp/ansible-tmp-1581109559.271161-112064566806002/AnsiballZ_flatpak_remote.py\",
 line 113, in \n_ansiballz_main()\n  File 
\"/home/zumbi/.ansible/tmp/ansible-tmp-1581109559.271161-112064566806002/AnsiballZ_flatpak_remote.py\",
 line 105, in _ansiballz_main\ninvoke_module(zipped_mod, temp_path, 
ANSIBALLZ_PARAMS)\n  File 
\"/home/zumbi/.ansible/tmp/ansible-tmp-1581109559.271161-112064566806002/AnsiballZ_flatpak_remote.py\",
 line 48, in invoke_module\nimp.load_module('__main__', mod, module, 
MOD_DESC)\n  File \"/usr/lib/python3.7/imp.py\", line 234, in load_module\n
return load_source(name, filename, file)\n  File \"/usr/lib/python3.7/imp.py\", 
line 169, in load_source\nmodule = _exec(spec, sys.modules[name])\n  File 
\"\", line 630, in _exec\n  File \"\", line 728, in exec_module\n  File \"\", line 219, in _call_with_frames_removed\n  File 
\"/tmp/ansible_flatpak_remote_payload_3i68y3ku/__main__.py\", line 241, in 
\n  File \"/tmp/ansible_flatpak_remote_payload_3i68y3ku/__main__.py\", 
line 230, in main\n  File 
\"/tmp/ansible_flatpak_remote_payload_3i68y3ku/__main__.py\", line 172, in 
remote_exists\nIndexError: list index out of range\n", "module_stdout": "", 
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
to retry, use: --limit 
@/home/zumbi/SCM/GITAuth/local/ansible/playbook.retry
```

The issue has been reported upstream at:
https://github.com/ansible/ansible/issues/51481

And a pull request has been merged:
https://github.com/ansible/ansible/pull/54103

I am attaching a debdiff I have tested and fixes the issue above.
Please, consider fixing this issue in Buster, via stable-updates. If you
need help, please let me know, I am willing to proceed with the upload
if you wish.

Regards

-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages ansible depends on:
ii  python33.7.3-1
ii  python3-crypto 2.6.1-9+b1
ii  python3-cryptography   2.6.1-3+deb10u2
ii  python3-httplib2   0.11.3-2
ii  python3-jinja2 2.10-2
ii  python3-netaddr0.7.19-1
ii  python3-paramiko   2.4.2-0.1
ii  python3-pkg-resources  40.8.0-1
ii  python3-yaml   3.13-2

Versions of packages ansible recommends:
ii  python3-jmespath   0.9.4-1
ii  python3-kerberos   1.1.14-2
ii  python3-libcloud   2.4.0-1
ii  python3-selinux2.8-1+b1
ii  python3-winrm  0.3.0-2
ii  python3-xmltodict  0.11.0-2

Versions of packages ansible suggests:
pn  cowsay   
pn  sshpass  

-- no debconf information
diff -Nru ansible-2.7.7+dfsg/debian/changelog 
ansible-2.7.7+dfsg/debian/changelog
--- ansible-2.7.7+dfsg/debian/changelog 2019-02-21 08:44:57.0 +0100
+++ ansible-2.7.7+dfsg/debian/changelog 2020-02-07 22:07:29.0 +0100
@@ -1,3 +1,12 @@
+ansible (2.7.7+dfsg-1local1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Local test of upstream patch to fix flatpak module:
+https://github.com/ansible/ansible/issues/51481
+https://github.com/ansible/ansible/pull/54103
+
+ -- Hector   Fri, 07 Feb 2020 22:07:29 +0100
+
 ansible (2.7.7+dfsg-1) unstable; urgency=high
 
   * New upstream release
diff -Nru 
ansible-2.7.7+dfsg/debian/patches/d78b3424dd9e72132df9b52ee4e5422cd3094bd6.patch
 
ansible-2.7.7+dfsg/debian/patches/d78b3424dd9e72132df9b52ee4e5422cd3094bd6.patch
--- 
ansible-2.7.7+dfsg/debian/patches/d78b3424dd9e72132df9b52ee4e5422cd3094bd6.patch
1970-01-01 01:00:00.0 +0100
+++ 
ansible-2.7.7+dfsg/debian/patches/d78b3424dd9e72132df9b52ee4e5422cd3094bd6.patch
2020-02-07 22:07:29.0 +0100
@@ -0,0 

Bug#950778: Debian GDB patch

[Hector Oron]

Package: gdb
Version: 8.3-1
Severity: normal
tags: patch


Hello Christian,

Missatge de Christian Biesinger  del dia dj., 6
de febr. 2020 a les 2:11:

> I noticed that in
> https://salsa.debian.org/gdb-team/gdb/blob/debian/unstable/debian/patches/load-versioned-libcc1.patch,
> you only changed gcc-c-interface.h. Doesn't gcc-cp-interface.h need a
> similar change?
>
> Also, I submitted a couple of pull requests at
> https://salsa.debian.org/gdb-team/gdb/merge_requests, it would be
> great if you could find some time to take a look at them.

Thanks for your comments and contribution! I do not have my Debian
credentials with me right now, I'll have a look as soon as time
allows, probably this evening.

PS./ Adding this as a bug in the Debian BTS to keep track

Regards

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

Bug#950606: gdb-source: generated tarball includes system metadata

[Hector Oron]

Hello,

Missatge de Vagrant Cascadian  del
dia dt., 4 de febr. 2020 a les 7:33:

> The attached patch passes arguments to tar to ensure reproducible builds
> of this package.

Thanks, applied in git, queued for next release.

[debian/unstable 4704dec43] debian/rules: allow reproducible source tarballs
 Author: Vagrant Cascadian 
 Date: Tue Feb 4 03:16:30 2020 +
 1 file changed, 5 insertions(+)

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

Bug#929206: lshw: wrong -json output

[Hector Oron]

On Sun, May 19, 2019 at 11:23:10AM +0200, Xavier Bustamante wrote:
> Package: lshw
> Version: 02.18.85-0.1
> Severity: normal
> 
> Dear Maintainer,
> 
> Executing lshw -json prints a json with wrong syntax, making it unusuable.
> 
> I tried compiling the software directly from the repository of lshw with the 
> same results.
> The only version that does not fail for me is the one that the original 
> author considers stable: B.02.18. Compiling and using this one in my Debian 
> 10 works.

This issue was also affecting me, reverting the following commit renders
good JSON output for me, checking with:

  /usr/bin/lshw -json 2>/dev/null | python -m json.tool

  Revert:
  
https://github.com/lyonel/lshw/pull/28/commits/95d0d50b6997194534eda02c4b6d6a61a19d48b1

Regards


signature.asc
Description: PGP signature

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

[Hector Oron]

Hello László,

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:
> >   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.
>  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.

> >   Note the package might need further clean-ups, so distribution is set to
> >   UNRELEASED.
>  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.

Regards and thanks for your packaging efforts



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

Bug#940730: [External] Re: Bug#940730: alsa-utils: Add ucm support for whiskeylake sof-skl_hda_card audio

[Hector Oron]

On Wed, Sep 25, 2019 at 03:07:21PM +, Mark Pearson wrote:
> > 
> > This is not a Debian specific bug. It should be handled by the ALSA project
> > itself to provide it for all linux distributions using ALSA.
> > 
> Hi Elimar,
> 
> The ALSA team have done an initial import of the new alsa-ucm-conf repository 
> (https://github.com/alsa-project/alsa-ucm-conf/tree/import) which has the 
> support for the sof-skl_hda_card which I was looking for with this bug.
> 
> How does it work for this making its way into Debian? I appreciate that it's 
> still all new and an exercise in progress on the ALSA side but was curious as 
> to how the process worked from there with regards to Debian.

I have backported patches from upstream project into current SID
package. Find attached patches that apply on top of alsa-lib in
salsa.debian.org.

@Mark, could you please verify those patches are fine and build
them?

Regards
From 945fa07aa6c078e72402ff8f76f0828220dcb05d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?H=C3=A9ctor=20Or=C3=B3n=20Mart=C3=ADnez?= 
Date: Wed, 9 Oct 2019 17:33:59 +0200
Subject: [PATCH 1/2] conf/ucm: sof-skl_hda_card: backport
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

  Fixes audio on Lenovo X1 Carbon Gen 7 using the whiskeylake processor.
  (Closes: #940730)

Signed-off-by: Héctor Orón Martínez 
---
 .../patches/backport-sof-skl_hda_card.patch   | 681 ++
 debian/patches/series |   1 +
 2 files changed, 682 insertions(+)
 create mode 100644 debian/patches/backport-sof-skl_hda_card.patch

diff --git a/debian/patches/backport-sof-skl_hda_card.patch b/debian/patches/backport-sof-skl_hda_card.patch
new file mode 100644
index ..e172b3b9
--- /dev/null
+++ b/debian/patches/backport-sof-skl_hda_card.patch
@@ -0,0 +1,681 @@
+Description: Add support for sof-skl_hda_card
+Fixes support for Lenovo X1 Carbon Gen 7 using the whiskeylake processor
+.
+Author: Héctor Orón Martínez 
+Bug-Debian: https://bugs.debian.org/940730
+Origin: upstream
+Forwarded: not-needed
+Reviewed-By: Mark Pearson 
+Last-Update: 2019-10-09
+
+--- alsa-lib-1.1.8.orig/src/conf/ucm/Makefile.am
 alsa-lib-1.1.8/src/conf/ucm/Makefile.am
+@@ -44,6 +44,7 @@ PAZ00 \
+ PIPO-W2S-Defaultstring-CherryTrailCR \
+ SDP4430 \
+ skylake-rt286 \
++sof-skl_hda_card \
+ TECLAST-X80Pro-Defaultstring-CherryTrailCR \
+ tegraalc5632 \
+ VEYRON-I2S
+--- /dev/null
 alsa-lib-1.1.8/src/conf/ucm/sof-skl_hda_card/HiFi.conf
+@@ -0,0 +1,166 @@
++# Use case Configuration for skl-hda-card
++
++SectionVerb {
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Master Playback Switch' on"
++		cset "name='Capture Switch' on"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++	]
++}
++
++SectionDevice."Headphone" {
++	Comment "Headphone"
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Headphone Playback Switch' on"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Headphone Playback Switch' off"
++	]
++
++	Value {
++		PlaybackPCM "hw:sofsklhdacard,0"
++		PlaybackChannels "2"
++		JackName "sof-skl_hda_card Headphone"
++		JackType "gpio"
++		JackSwitch "12"
++		JackControl "Headphone Jack"
++	}
++}
++
++SectionDevice."Speaker" {
++	Comment "Speaker"
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Speaker Playback Switch' on"
++	]
++
++	DisableSequence [
++		cset "name='Speaker Playback Switch' off"
++	]
++
++	Value {
++		PlaybackPCM "hw:sofsklhdacard,0"
++		JackHWMute "Headphone"
++		PlaybackChannels "2"
++	}
++}
++
++SectionDevice."Headset" {
++	Comment "Headset Mic"
++
++	ConflictingDevice [
++		"DMIC Stereo"
++	]
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++	]
++
++	Value {
++		CapturePCM "hw:0,0"
++		CaptureChannels "2"
++		JackControl "Mic Jack"
++	}
++}
++
++SectionDevice."Dmic" {
++	Comment "DMIC Stereo"
++
++	ConflictingDevice [
++		"Headset Mic"
++	]
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++	]
++
++	Value {
++		CapturePCM "hw:0,6"
++		CaptureChannels "2"
++	}
++}
++
++SectionDevice."HDMI1" {
++	Comment "HDMI1/DP1 Output"
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='hif5-0 Jack Switch' on"
++		cset "name='Pin5-Port0 Mux' 1"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Pin5-Port0 Mux' 0"
++		cset "name='hif5-0 Jack Switch' off"
++	]
++
++	Value {
++		PlaybackPCM "hw:0,3"
++		PlaybackChannels "2"
++		JackControl "HDMI/DP, pcm=11 Jack"
++	}
++}
++
++SectionDevice."HDMI2" {
++	Comment "HDMI2/DP2 Output"
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='hif6-0 Jack Switch' on"
++		cset "name='Pin6-Port0 Mux' 2"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Pin6-Port0 Mux' 0"
++		cset "name='hif6-0 Jack Switch' off"
++	]
++
++	Value {
++		PlaybackPCM "hw:0,4"
++		

Bug#926701: [tlbuild] Bug#926701: dvisvgm binary fails to link on GNU Hurd

[Hector Oron]

Hello,

  JFYI, a give back (package rebuild from failed state) has been triggered per 
IRC request:

Day changed to 16 Aug 2019
12:08 < gnu_srs1> (11:51:02 PM) srs: Can somebody gb texlive-bin 
2019.20190605.51237-2 on
  hurd-i386. It built fine locally.


signature.asc
Description: PGP signature

Bug#933151: mariadb-10.3: FTBFS on riscv64

[Hector Oron]

Hello,

Missatge de Otto Kekäläinen  del dia ds., 27 de jul.
2019 a les 3:21:
>
> Package: mariadb-10.3
> X-Debbugs-CC: debian-ri...@lists.debian.org
> User: debian-ri...@lists.debian.org
> Usertags: riscv64
>
> The version of the package currently FTBFS on the riscv64 port.
>
> >From 
> >https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.3=riscv64=1%3A10.3.16-1=1561225015=0
>
>
> /usr/bin/ld: librocksdblib.a(memtable.cc.o): in function `.L0 ':
> ./builddir/storage/rocksdb/./storage/rocksdb/rocksdb/util/dynamic_bloom.h:177:
> undefined reference to `__atomic_fetch_or_1'
> /usr/bin/ld: librocksdblib.a(memtable.cc.o): in function `.LVL1731':
> ./builddir/storage/rocksdb/./storage/rocksdb/rocksdb/util/dynamic_bloom.h:179:
> undefined reference to `__atomic_fetch_or_1'
> /usr/bin/ld: librocksdblib.a(memtable.cc.o): in function `SaveValue':
> ./builddir/storage/rocksdb/./storage/rocksdb/rocksdb/db/memtable.cc:596:
> undefined reference to `__atomic_compare_exchange_1'
> /usr/bin/ld: librocksdblib.a(memtable.cc.o): in function `.L0 ':
> /usr/include/c++/8/bits/atomic_base.h:434: undefined reference to
> `__atomic_compare_exchange_1'
> /usr/bin/ld: /usr/include/c++/8/bits/atomic_base.h:434: undefined
> reference to `__atomic_compare_exchange_1'
> /usr/bin/ld: /usr/include/c++/8/bits/atomic_base.h:434: undefined
> reference to `__atomic_compare_exchange_1'
> /usr/bin/ld: /usr/include/c++/8/bits/atomic_base.h:434: undefined
> reference to `__atomic_compare_exchange_1'
> /usr/bin/ld: 
> librocksdblib.a(memtable.cc.o):/usr/include/c++/8/bits/atomic_base.h:434:
> more undefined references to `__atomic_compare_exchange_1' follow
> collect2: error: ld returned 1 exit status
>
> If you are an RISC expert, feel free to fork
> https://salsa.debian.org/mariadb-team/mariadb-10.3, play around, and
> make a merge request.

According to:
https://github.com/riscv/riscv-gnu-toolchain/issues/183#issuecomment-253721765

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.

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

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

[Hector Oron]

Hey guys,

Missatge de Alex Muntada  del dia dc., 17 de jul.
2019 a les 23:08:
>
> Hi gregor,
>
> > I just wanted to propose "Check the README" but it seems like
> > the friendly README [...] doesn't get installed in the package
> > anymore … Oops.
>
> I examined the contents of the older versions I have in my
> computer and none of them installed the README. Maybe it's
> because package installation will fail unless its depends
> are met first and hence the link to the README in the full
> description.
>
> I guess we could rename README to README.Debian and install
> it anyway. What do you think?

Thanks for the explanation, I was just checking repository consistency
for buster and came up with this issue. I leave it up to you to
downgrade severity accordingly or close the bug. Fixing the README
installation one way or the other might be nice.

Best regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

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

[Hector Oron]

Hello Alex,

Missatge de Alex Muntada  del dia dc., 17 de jul.
2019 a les 2:13:

> > 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.

> There's a comment in d/copyright explaining why this package is
> in contrib:
>
> «The upstream Perl distribution is freely licensed by the
> copyright holders but depends on Oracle Instant Client software,
> that is not free. Therefore, it belongs to Debian contrib section
> according to DFSG.»
>
> Is there something that has recently changed that maybe I'm
> missing?

Where can I find those packages to close the dependency loop, checking
at non-free those do not seem to be available.

https://packages.debian.org/search?searchon=names=oracle-instantclient12.1-basic
https://packages.debian.org/search?searchon=names=oracle-instantclient12.1-basiclite

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

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

[Hector Oron]

Hello,

> Missatge de James Clarke  del dia dc., 17 de jul.
> 2019 a les 8:25:

> > vidcontrol, and the rest of src:freebsd-utils, is available in unreleased,
> > since the source package only builds for kfreebsd-amd64 and kfreebsd-i386.
> > Avoiding this would require either getting the source package to build on 
> > Linux
> > architectures, or building at least one arch:all package, neither of which 
> > seem
> > to have much point to them. As an architecture on Debian Ports, it is 
> > expected
> > that you also have the "unreleased" suite enabled, as is clearly documented 
> > on
> > the main site[1]. This is especially important on kFreeBSD, since
> > bin:freebsd-utils is Essential, containing many of the core utilities 
> > required
> > for a functioning system. All ports buildds should have unreleased 
> > available,
> > and debian-installer learnt over 2 years ago to include unreleased when
> > downloading udebs. Thus, I consider this not a bug; as much as we would 
> > like it
> > to not be, as far as Debian Ports goes, unreleased is a necessary addition 
> > to
> > unstable, with cases like these stemming from the fact that ftp-master does 
> > not
> > allow sources to exist that don't build packages for any of its 
> > architectures.
>
> Oh! I did not check unreleased, only `amd64` architecture and I saw
> that dependency loop was not closed. Thanks very much for the nice
> explanation and background.

Along the lines,
https://packages.debian.org/unstable/console-setup-freebsd site should
probably check on the unreleased suite.

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

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

[Hector Oron]

Hello,

Missatge de James Clarke  del dia dc., 17 de jul.
2019 a les 8:25:

> vidcontrol, and the rest of src:freebsd-utils, is available in unreleased,
> since the source package only builds for kfreebsd-amd64 and kfreebsd-i386.
> Avoiding this would require either getting the source package to build on 
> Linux
> architectures, or building at least one arch:all package, neither of which 
> seem
> to have much point to them. As an architecture on Debian Ports, it is expected
> that you also have the "unreleased" suite enabled, as is clearly documented on
> the main site[1]. This is especially important on kFreeBSD, since
> bin:freebsd-utils is Essential, containing many of the core utilities required
> for a functioning system. All ports buildds should have unreleased available,
> and debian-installer learnt over 2 years ago to include unreleased when
> downloading udebs. Thus, I consider this not a bug; as much as we would like 
> it
> to not be, as far as Debian Ports goes, unreleased is a necessary addition to
> unstable, with cases like these stemming from the fact that ftp-master does 
> not
> allow sources to exist that don't build packages for any of its architectures.

Oh! I did not check unreleased, only `amd64` architecture and I saw
that dependency loop was not closed. Thanks very much for the nice
explanation and background.

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

Bug#859063: weston: running 'weston --fullscreen' inside of weston causes bad RAM access

[Hector Oron]

On Thu, Mar 30, 2017 at 01:00:15AM +0200, mviereck wrote:
> Package: weston
> Version: 1.12.0-3
> Severity: normal
> 
> Dear Maintainer,
> 
> Steps to reproduce:
> Start weston from console:
>   weston
> Inside of weston, open terminal and run
>   weston --fullscreen

This works fine for me on weston 5.0.0.


signature.asc
Description: PGP signature

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

[Hector Oron]

Hello again,

  Besides what was mentioned in the previous email, I would like to clarify
that we commit to open-build-service active maintenance since it is used in
production by us.

  Regarding security we have already discussed with security team adding a
note in the package clarifying security implications and doing
recommendations to the potential users on whether running a public instance
is discouraged.

Regards

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

[Hector Oron]

Hello,

Missatge de Jonathan Wiltshire  del dia dc., 6 de març
2019 a les 22:59:
> On Thu, Feb 14, 2019 at 08:19:10PM +0100, Héctor Orón Martínez wrote:
> > 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`.
>
> I don't wish to detract from that effort, but it's not a valid reason on
> its own for the unblock of a package not even in testing.
>
> With open-build-service being out of testing for nearly a year,

Newer `open-build-service` had a dependency on ruby rails 5, which we
have been coordinating with gitlab maintainers, because gitlab did not
support rails 5 until very recently, so we started rails 5 transition
in experimental, and barely made it to transition freeze.

> dependencies also not in testing (and my feelings on them are similar), and

While `open-build-service` was ready, some of the dependencies prevent
it from migrating to testing, which was very unfortunated.

> a popcon of just 10 or so, I think a better pathway would be via

Right, not many popcon users, however it has it's users and ease the
Debian derivative distro maintenance, for instance, it is used by
Apertis, SteamOS, Endless Debian derivatives. Sylvestre has been using
it for LLVM work as well. And it is being used by Linaro as well for
distro work for the ARM architecture.

> buster-backports when that is open.

While we have thought about maintaining `open-build-service` newer
versions in `stretch-backports`, it has not been possible due to webUI
ruby dependencies and the way ruby is packaged in Debian, it makes it
very hard to align all dependencies to have a working set. While
buster-backports would be awesome to have, I do not think is going to
work, since ruby versions do not remain compatible with older ones. We
have also thought on changing the paradigm and package the backend
services (perl) separated from webui (ruby) and provide webui in a
container and install gems with ruby package manager instead as a work
around, since doing the Debian way with rubygems is quite painful, but
if you have any other good ideas we'd love to hear them.

> I'm open to be pursuaded.

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.

Thanks for considering, I know it is not an easy call to do, so I'll
understand either way you decide.

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

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

[Hector Oron]

Hello,

Missatge de Yann Ylavic  del dia dl., 11 de
febr. 2019 a les 14:03:
>
> Package: gdb
> Version: 8.2-1
>
> The below happens when hitting a breaking in a shared library compiled
> with Linker Time Optimizer (-flto):
>
> /build/gdb-Ji3G0U/gdb-8.2/gdb/dwarf2read.c:9715: internal-error: void
> dw2_add_symbol_to_list(symbol*, pending**): Assertion `(*listhead) ==
> NULL || (SYMBOL_LANGUAGE ((*listhead)->symbol[0]) == SYMBOL_LANGUAGE
> (symbol))' failed.
> A problem internal to GDB has been detected,
>
> 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.

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

Bug#888400: RFA: python-cassandra-driver

[Hector Oron]

Hello,

On Wed, Nov 28, 2018 at 10:48:11AM -0300, eamanu15 wrote:
> Control: retitle -1 ITA: python-cassandra-driver
> 
> Control: owner -1 emmanuelaria...@gmail.com
> 
> Hello,
> 
> I am interest on adopt this package.
> 
> I upload a new version(3.16.0-1) to mentors.d.o
> https://mentors.debian.net/package/python-cassandra-driver

Since this package has RC bugs is not part of Buster, and it is needed
for new `salt` packages. I plan to sponsor Emmanuel package into Debian,
in the hope to allow newer `salt` into Buster.

Regards


signature.asc
Description: PGP signature

Bug#912048: obs-build: FTBFS: Test failures

[Hector Oron]

Hello,

On Sat, Oct 27, 2018 at 08:45:29AM -0700, Daniel Schepler wrote:
> Source: obs-build
> Version: 20180831-1
> Severity: serious
> Tags: ftbfs

Sadly I am unable to reproduce it and the build runs fine here.
I'll downgrade severity of this bug to allow it re-enter Buster again.

If you think the package still FTBFS, please reply this message and I'll
re-try to reproduce it one more time.

> From my pbuilder build log:
> 
> ...
>dh_auto_test
>make -j1 test
> make[1]: Entering directory '/build/obs-build-20180831'
> PERL5LIB=. prove -v
> Can't locate Date/Parse.pm in @INC (you may need to install the
> Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.2
> /usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
> /perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
> /usr/share/perl/5.26 /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
> BEGIN failed--compilation aborted at ./changelog2spec line 31.
> 
> #   Failed test 'changelog2spec --selftest rpm python-rpm.changes rpm.changes'
> #   at t/changelog2spec.t line 10.
> #  got: ''
> # expected: 'rpm.changes'
> Can't locate Date/Parse.pm in @INC (you may need to install the
> Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.2
> /usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
> /perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
> /usr/share/perl/5.26 /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
> BEGIN failed--compilation aborted at ./changelog2spec line 31.
> 
> #   Failed test 'changelog2spec --selftest python-rpm
> python-rpm.changes rpm.changes'
> #   at t/changelog2spec.t line 10.
> #  got: ''
> # expected: 'python-rpm.changes'
> Can't locate Date/Parse.pm in @INC (you may need to install the
> Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.2
> /usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
> /perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
> /usr/share/perl/5.26 /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
> BEGIN failed--compilation aborted at ./changelog2spec line 31.
> 
> #   Failed test 'changelog2spec --selftest antlr antlr.changes
> antlr-bootstrap.changes'
> #   at t/changelog2spec.t line 10.
> #  got: ''
> # expected: 'antlr.changes'
> Can't locate Date/Parse.pm in @INC (you may need to install the
> Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.2
> /usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
> /perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
> /usr/share/perl/5.26 /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
> BEGIN failed--compilation aborted at ./changelog2spec line 31.
> 
> #   Failed test 'changelog2spec --selftest antlr anyunrelated.changes'
> #   at t/changelog2spec.t line 10.
> #  got: ''
> # expected: 'anyunrelated.changes'
> Can't locate Date/Parse.pm in @INC (you may need to install the
> Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.2
> /usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
> /perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
> /usr/share/perl/5.26 /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
> BEGIN failed--compilation aborted at ./changelog2spec line 31.
> 
> #   Failed test 'changelog2spec --selftest antlr-bootstrap
> antlr.changes antlr-bootstrap.changes'
> #   at t/changelog2spec.t line 10.
> #  got: ''
> # expected: 'antlr-bootstrap.changes'
> Can't locate Date/Parse.pm in @INC (you may need to install the
> Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.2
> /usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
> /perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
> /usr/share/perl/5.26 /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
> BEGIN failed--compilation aborted at ./changelog2spec line 31.
> 
> #   Failed test 'changelog2spec --selftest antlr-bootstrap antlr.changes'
> #   at t/changelog2spec.t line 10.
> #  got: ''
> # expected: 'antlr.changes'
> Can't locate Date/Parse.pm in @INC (you may need to install the
> Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.2
> /usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
> /perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
> /usr/share/perl/5.26 /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
> BEGIN 

Bug#910409: wayland-protocols: Can't use second monitor via HDMI

[Hector Oron]

Hello,

On Fri, Oct 05, 2018 at 10:48:33PM -0500, Pavlo Solntsev wrote:
> Package: wayland-protocols
> Version: 1.16-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I am not sure what package name I should use for this report. Today (Oct. 5,
> 22:40T+6) I updated my system debian testing and my external monitor stop
> working. In my xrandr output I see only one monitor
> Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
> XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis)
> 290mm x 170mm
>1920x1080 59.96*+

`wayland-protocols` is not the package you are looking for.
Do you see any relevant messages from kernel? i.e. `/var/log/messages`

> Combination Fn+F8 (switch video mode) doesn't produce anything. I am not sure
> what information I should ptovide. Please guide and I will send you info. You
> can contact me directly if it helps: p.sun.fun at gmail dot com.
> 
> The following packages were upgraded:
> 2018-10-05 22:02:49 install libcamel-1.2-62:amd64  3.30.1-1
> 2018-10-05 22:02:49 status half-installed libcamel-1.2-62:amd64 3.30.1-1

Why do you have half-installed packages? Can you fully upgrade your system?

> 2018-10-05 22:02:49 status half-installed evolution-plugin-bogofilter:amd64
> 3.28.5-1
> 2018-10-05 22:02:49 status half-installed evolution-plugin-bogofilter:amd64
> 3.28.5-1
> 2018-10-05 22:02:49 status half-installed evolution-plugin-pstimport:amd64
> 3.28.5-1
> 2018-10-05 22:02:49 status half-installed evolution-plugin-pstimport:amd64
> 3.28.5-1
> 2018-10-05 22:02:49 status half-installed evolution-plugins:amd64 3.28.5-1
> 2018-10-05 22:02:49 status half-installed evolution-plugins:amd64 3.28.5-1
> 2018-10-05 22:02:50 status half-installed evolution:amd64 3.28.5-1
> 2018-10-05 22:02:50 status half-installed evolution:amd64 3.28.5-1
> 2018-10-05 22:02:50 status half-installed libevolution:amd64 3.28.5-1
> 2018-10-05 22:02:50 status half-installed libevolution:amd64 3.28.5-1
> 2018-10-05 22:02:50 status half-installed evolution-data-server:amd64 3.28.5-3
> 2018-10-05 22:02:51 status half-installed evolution-data-server:amd64 3.28.5-3
> 2018-10-05 22:02:51 status installed libedata-cal-1.2-28:amd64 3.28.5-3
> 2018-10-05 22:02:51 status half-installed libedata-cal-1.2-28:amd64 3.28.5-3
> 2018-10-05 22:02:51 status not-installed libedata-cal-1.2-28:amd64 
> 2018-10-05 22:02:51 status half-installed libecal1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:51 status half-installed libecal1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libecal-1.2-19:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libecal-1.2-19:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libebook-1.2-19:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libebook-1.2-19:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libedata-book1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libedata-book1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libedata-book-1.2-25:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libedata-book-1.2-25:amd64 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebackend1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebackend1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebackend-1.2-10:amd64 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebackend-1.2-10:amd64 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libedataserverui1.2-dev:amd64
> 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libedataserverui1.2-dev:amd64
> 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebook-contacts1.2-dev:amd64
> 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebook-contacts1.2-dev:amd64
> 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libedataserver1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:54 status half-installed libedataserver1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:54 status half-installed libcamel1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:54 status half-installed libcamel1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:54 status half-installed libsecret-common:all 0.18.6-2
> 2018-10-05 22:02:54 status half-installed libsecret-common:all 0.18.6-2
> 2018-10-05 22:02:54 status half-installed libsecret-1-dev:amd64 0.18.6-2
> 2018-10-05 22:02:54 status half-installed libsecret-1-dev:amd64 0.18.6-2
> 2018-10-05 22:02:55 status half-installed libsecret-1-0:amd64 0.18.6-2
> 2018-10-05 22:02:55 status half-installed libsecret-1-0:amd64 0.18.6-2
> 2018-10-05 22:02:55 status half-installed gir1.2-secret-1:amd64 0.18.6-2
> 2018-10-05 22:02:55 status half-installed gir1.2-secret-1:amd64 0.18.6-2
> 2018-10-05 22:02:55 status half-installed gir1.2-ebookcontacts-1.2:amd64
> 3.28.5-3
> 2018-10-05 22:02:55 status half-installed gir1.2-ebookcontacts-1.2:amd64
> 3.28.5-3
> 2018-10-05 22:02:55 status half-installed gir1.2-edataserverui-1.2:amd64
> 3.28.5-3
> 2018-10-05 22:02:55 status half-installed 

Bug#915322: --args option not documented in gdb.1 man page

[Hector Oron]

Hello,

> Missatge de Kevin Locke  del dia dg., 2 de des.
> 2018 a les 20:24:
> >
> > Package: gdb-doc
> > Version: 8.1-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > The --args option does not appear in the gdb.1 manual page, although it
> > is documented in gdb/doc/gdb.texinfo[1] from which gdb.1 is generated.
> > It would be helpful if this option were included in the manual page.

Please also see
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831470#10

Regards

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

Bug#915322: --args option not documented in gdb.1 man page

[Hector Oron]

Hello,

Missatge de Kevin Locke  del dia dg., 2 de des.
2018 a les 20:24:
>
> Package: gdb-doc
> Version: 8.1-1
> Severity: normal
>
> Dear Maintainer,
>
> The --args option does not appear in the gdb.1 manual page, although it
> is documented in gdb/doc/gdb.texinfo[1] from which gdb.1 is generated.
> It would be helpful if this option were included in the manual page.

The manual page is generated from `gdb.pod` file which is generated
using the script in `etc/texi2pod.pl`.
In particular, the generated pod does not contain information about
--args feature, upstream has considered to place it in the info page
instead.
Therefore, I have no plans to contradict upstream decisions in this
case, however, could you please file this bug report in the GNU GDB
bugtracker instead and get it fixed upstream?

Thanks for your report

> Thanks for considering,
> Kevin
>
> 1.  
> https://salsa.debian.org/gdb-team/gdb-doc/blob/debian/8.1-1/gdb/doc/gdb.texinfo?expanded=true=simple#L1223
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.19.0 (SMP w/4 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
> LANGUAGE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> -- no debconf information



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



-- Would you like to make a donation towards the upcoming Debian conference?
   Brochure: 
https://media.debconf.org/dc18/fundraising/debconf18_sponsorship_brochure_en.pdf

   ** https://debconf18.debconf.org/sponsors/become-a-sponsor/ **

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

[Hector Oron]

Hello,

Missatge de Ian Jackson  del dia dv.,
5 d’oct. 2018 a les 14:50:
> Ian Jackson writes ("Re: Bug#906317: dgit: consider demoting git-buildpackage 
> to recommends"):
> > So I'm inclined to think that the subset of dgit's functionality which
> > is useable without gbp pq is too small for your use case (and too
> > small to make it sensible to demote this depends).  But I'm happy to
> > talk about it some more.
> ...
> > What is the concern with git-buildpackage ?  I understand that it's a
> > big piece of software but it contains many important tools for
> > managing many styles of Debian packaging git branch.  I wasn't aware
> > that it had significant functionality of a kind that would be
> > undesirable on a porterbox.

As I understood, DSA team had some concerns for security reasons since
porterboxes are meant to be used to debug package build failures and
not used for anything else, so it is much preferred a 'push' scenario
where developers push the code to porterboxes, rather than 'pull',
being `apt-get source` the unique exception to that unwritten policy.
So developers would like to use `dgit push` from porterboxes, however
getting that functionality also opens a can of worms, allowing for
pulls as well.

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

Bug#790093: No TOFU for git server host key

[Hector Oron]

Hello Ian,

Missatge de Ian Jackson  del dia dv.,
5 d’oct. 2018 a les 14:51:
>
> Ian Jackson writes ("No TOFU for git server host key"):
> > I think now would be a good time to look at #790093 again.  Would
> > anyone from the DSA team with the requisite TLS knowledge be available
> > to get together with me to sketch out a solution ?
>
> Ping ?
>
> I think we are nearing the end of our opportunity to improve this in
> buster.

Apologies for not replying earlier, but I have no idea, I think it'd
be best if you drop by #debian-admin IRC channel and ask there for
support or email dsa mailing list about it.

Regards

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

Bug#840829: docker.io: Won't start under cgroupsv2

[Hector Oron]

On Sat, Oct 15, 2016 at 12:37:37PM +0100, Sam Morris wrote:
> Package: docker.io
> Version: 1.11.2~ds1-6
> Severity: normal
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> When booting with the systemd.unified_cgroup_hierarchy kernel parameter,
> systemd mounts the cgroup2 filesystem at /sys/fs/cgroup. As a result,
> docker no longer starts:
> 
> time="2016-10-13T11:40:35.542974438+01:00" level=info msg="New containerd 
> process, pid: 5361\n"
> time="2016-10-13T11:40:36.560787581+01:00" level=info msg="[graphdriver] 
> using prior storage driver \"overlay\""
> time="2016-10-13T11:40:36.589298060+01:00" level=info msg="Graph migration to 
> content-addressability took 0.00 seconds"
> time="2016-10-13T11:40:36.641136232+01:00" level=info msg="Firewalld running: 
> false"
> time="2016-10-13T11:40:36.769321694+01:00" level=info msg="Default bridge 
> (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip 
> can be used to set a preferred IP address"
> time="2016-10-13T11:40:36.930907456+01:00" level=warning msg="Your kernel 
> does not support cgroup memory limit"
> time="2016-10-13T11:40:36.930946129+01:00" level=warning msg="Unable to find 
> cpu cgroup in mounts"
> time="2016-10-13T11:40:36.930958093+01:00" level=warning msg="Unable to find 
> blkio cgroup in mounts"
> time="2016-10-13T11:40:36.930967804+01:00" level=warning msg="Unable to find 
> cpuset cgroup in mounts"
> time="2016-10-13T11:40:36.933815046+01:00" level=warning msg="mountpoint for 
> pids not found"
> time="2016-10-13T11:40:36.934330952+01:00" level=fatal msg="Error starting 
> daemon: Devices cgroup isn't mounted"

Can you reproduce it with current package in `unstable`?

Regards

-- 


signature.asc
Description: PGP signature

Bug#902900: python3-celery: python3-celery fails to install with Python 3.7

[Hector Oron]

On Tue, Jul 03, 2018 at 10:09:56AM +0200, Antoine R. Dumont wrote:
> Package: python3-celery
> Version: 4.1.0-4
> Severity: serious
> Hello,
> 
> Setting up python3-celery (4.2.0-1) ...
>   File "/usr/lib/python3/dist-packages/celery/backends/redis.py", line 22
> from . import async, base
>   ^
> SyntaxError: invalid syntax
> 
>   File "/usr/lib/python3/dist-packages/celery/backends/rpc.py", line 20
> from .async import AsyncBackendMixin, BaseResultConsumer
>   ^
> SyntaxError: invalid syntax
> 
> dpkg: error processing package python3-celery (--configure):
>  installed python3-celery package post-installation script subprocess
>  returned error exit status 1

I have submitted a backported patch from upstream as MR#1 in salsa:
https://salsa.debian.org/python-team/modules/celery/merge_requests/1

I have been able to build the package and install it, I have not done any 
further testing.

Regards,
 Héctor Orón Martínez


signature.asc
Description: PGP signature

Bug#902437: xwayland: Firefox crashes Wayland on some web pages

[Hector Oron]

Hello,
Missatge de Lars Wirzenius  del dia dt., 26 de juny 2018 a
les 19:51:
>
> Package: xwayland
> Version: 2:1.20.0-2
> Severity: important

> After much headbanging and wailing, I've manged to find way to
> reproduce the crash. I use Firefox as my web browser, and certain web
> pages trigger the crash reproducibly. One such web page is here:
>
> http://johannesbrodwall.com/2018/06/24/forget-about-clean-code-lets-embrace-compassionate-code/

Using xwayland 2:1.20.0-3 I have been able to reproduce by opening
above pointer on X220 machine.

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

Bug#906822: gdb: gdb FTBFS on ia64

[Hector Oron]

Hello,

2018-08-21 17:33 GMT+02:00 Jason Duerstock :
> Package: gdb
> Version: 7.12-6+ia64.1
> Severity: normal
> Tags: patch
> User: debian-i...@lists.debian.org
> Usertags: ia64
>
> Dear Maintainer,
>
> gdb 8.1 FTBFS on ia64 because an internal API change was not fully
> propagated across all callers.  This is fixed in upstream git commit
> 5d691c8829d0e5c4c4b9cfb147c8a873ce18085b, which is included here for
> your convenience.

Thanks for the patch, apparently it does not apply on 8.1 (in
Unstable/Buster), but it applies on the version in experimental.

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

Bug#832594: libinput10: Thinkpad middle mouse not functioning properly, appears to be libinput10 issue

[Hector Oron]

On Wed, Jul 27, 2016 at 05:47:08AM -0500, Karsten M. Self wrote:
> Package: libinput10
> Version: 1.3.3-1
> Severity: normal
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***
> 
> See also Bug #823147
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823147
> 
> As of a couple of months ago (system's been infrequently used), middle
> mouse behavior on a Thinkpad T520i changed.  When using the TrackPoint
> mouse and buttons, the middle button behavior changed.  It's not
> possible to move the pointer while the middle button is depressed,
> several programs and tools don't respond (though Xorg clipboard paste
> appears to work).  I believe this affects *both* console and Xorg
> sessions.
> 
> xev _doesn't_ report either BottonPress or ButtonRelease events for the
> 2nd (middle) mouse button.  Contrast (button 2 was pressed and released
> several times in this capture):
> 
> 
> ButtonPress event, serial 36, synthetic NO, window 0x561,
> root 0xc4, subw 0x562, time 9625078, (36,51), root:(37,452),
> state 0x0, button 1, same_screen YES
> 
> EnterNotify event, serial 36, synthetic NO, window 0x561,
> root 0xc4, subw 0x0, time 9625078, (36,51), root:(37,452),
> mode NotifyGrab, detail NotifyInferior, same_screen YES,
> focus YES, state 256
> 
> KeymapNotify event, serial 36, synthetic NO, window 0x0,
> keys:  4294967236 0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   
>0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 
> ButtonRelease event, serial 36, synthetic NO, window 0x561,
> root 0xc4, subw 0x562, time 9625217, (36,51), root:(37,452),
> state 0x100, button 1, same_screen YES
> 
> LeaveNotify event, serial 36, synthetic NO, window 0x561,
> root 0xc4, subw 0x0, time 9625217, (36,51), root:(37,452),
> mode NotifyUngrab, detail NotifyInferior, same_screen YES,
> focus YES, state 0
> 
> ButtonPress event, serial 36, synthetic NO, window 0x561,
> root 0xc4, subw 0x562, time 9626514, (36,51), root:(37,452),
> state 0x0, button 2, same_screen YES
> 
> EnterNotify event, serial 36, synthetic NO, window 0x561,
> root 0xc4, subw 0x0, time 9626514, (36,51), root:(37,452),
> mode NotifyGrab, detail NotifyInferior, same_screen YES,
> focus YES, state 512
> 
> KeymapNotify event, serial 36, synthetic NO, window 0x0,
> keys:  4294967236 0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   
>0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 
> ButtonRelease event, serial 36, synthetic NO, window 0x561,
> root 0xc4, subw 0x562, time 9626514, (36,51), root:(37,452),
> state 0x200, button 2, same_screen YES
> 
> 
> 
> xinput shows:
> 
> $ xinput list
> ⎡ Virtual core pointerid=2[master pointer  (3)]
> ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
>  (2)]
> ⎜   ↳ TPPS/2 IBM TrackPoint   id=11   [slave  pointer 
>  (2)]
> ⎣ Virtual core keyboard   id=3[master keyboard (2)]
> ↳ Virtual core XTEST keyboard id=5[slave  
> keyboard (3)]
> ↳ Power Buttonid=6[slave  
> keyboard (3)]
> ↳ Video Bus   id=7[slave  
> keyboard (3)]
> ↳ Sleep Buttonid=8[slave  
> keyboard (3)]
> ↳ Integrated Camera   id=9[slave  
> keyboard (3)]
> ↳ AT Translated Set 2 keyboardid=10   [slave  
> keyboard (3)]
> ↳ ThinkPad Extra Buttons  id=12   [slave  
> keyboard (3)]
> 
> $ xinput get-button-map 11
> 1 2 3 4 5 6 7 
> 
> $ xinput list-props 11
> Device 'TPPS/2 IBM TrackPoint':
>   Device Enabled (139):   1
>   Coordinate Transformation Matrix (141): 1.00, 0.00, 0.00, 
> 0.00, 1.00, 0.00, 0.00, 0.00, 1.00
>   libinput Accel Speed (275): 0.00
>   libinput Accel Speed Default (276): 0.00
>   libinput Accel Profiles Available (277):1, 1
>   libinput Accel Profile Enabled (278):   1, 0
>   libinput Accel Profile Enabled Default (279):   1, 0
>   libinput Natural Scrolling Enabled (280):   0
>   libinput Natural Scrolling Enabled Default (281):   0
>   

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

[Hector Oron]

On Wed, Jul 26, 2017 at 02:18:45PM +0200, Alf wrote:
> Package: libinput10
> Version: 1.6.3-1
> Severity: normal
> 
>* What led up to the situation?
> Sweitching from Jessie to Stretch makes the Trackball hardly usable.
> 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.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> Tried to adjust the parameters with "xinput" and the XFCE-settings
> without success (settings are not respected).
> Tried to cheat the DPI-values as given in /lib/udev/hwdb.d/70-mouse.hwdb
> for MOUSE_DPI= without success.
> Btw: the polling frequeny ist not 167Hz as hwdb suggests, but 125Hz as
> reported by solaar:
> Wireless Trackball M570
>  Codename : M570
>  Kind : mouse
>  Wireless PID : 1028
>  Protocol : HID++ 1.0
>  Polling rate : 8 ms  (=125Hz)
>  Serial number: BD48472C
>   Firmware: 26.00.B0003
> Bootloader: 02.06
>  Other: 00.01
>* What was the outcome of this action?
> None of the known adjustments are respected by libinput - no changes.
> 
> For now I had to revert to xserver-xorg-input-evdev which allows
> detailled adjustments to operate the trackball a comfortable way.
> To obtain a "clean Xorg.log" I also had to set libinput to ignore all
> mice and keyboars. All works like a charm with evdev!
> 
> Remak: xserver-xorg-input-evdev sets a Velocity Scaling (267):
> 10.00, while libinput sets it fixed to 15.00.

Could you please test version 1.11.2-1 and report back?

Best regards

> 
> -- System Information:
> Debian Release: 9.1
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8),
> LANGUAGE=de_DE.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages libinput10 depends on:
> ii  libc6 2.24-11+deb9u1
> ii  libevdev2 1.5.6+dfsg-1
> ii  libinput-bin  1.6.3-1
> ii  libmtdev1 1.1.5-1+b1
> ii  libudev1  232-25+deb9u1
> ii  libwacom2 0.22-1+b1
> 
> libinput10 recommends no packages.
> 
> libinput10 suggests no packages.
> 
> -- no debconf information

-- 


signature.asc
Description: PGP signature

Bug#883036: disable-while-typing not working?

[Hector Oron]

Hello Marco,

On Tue, Nov 28, 2017 at 08:30:10PM -0500, Marco Villegas wrote:
> 
> Package: libinput10
> Version: 1.6.3-1
> Severity: normal
> 
> Dear Mantainer,
> 
> It seems like disable-while-typing[1] feature is not working correctly,
> even if it is enabled, it does not honor the timeouts in the code.

Could you please test version 1.11.2-1 in unstable and report back?

> This feature has been in there for a while, but I guess I notice it in
> Debian because libinput driver superseded synaptic Xorg driver in
> stretch. disable-while-typing was possible with synaptic with
> syndaemon/synclient, but libinput method seems to be more efficient[2].
> 
> At first, I thought the feature was simply not enabled.
> GNOME seems to not have an UI for it until 3.24[3][4], but after
> installing xinput I see it is enabled.
> 
> $ xinput | grep Touchpad
> ⎜   ↳ 1A586753:00 06CB:8323 Touchpad  id=15 [slave
> pointer  (2)]
> $ xinput list-props 15| grep Typing
>   libinput Disable While Typing Enabled (309):1
>   libinput Disable While Typing Enabled Default (310):1
> 
> To test this:
> a. I start typing some sentence in a text editor, 
> b. then use the touchpad,
> c. and the original application where I was typing is not in focus
> anymore.
> 
> What I expected would be to the text editor to keep focus even if the
> touchpad is pressed when the time between the last key pressed and the
> touchpad is less than the established timeout, which in current
> packaged version 1.6.3 is 500ms[5].
> 
> This setting sounds like a good candidate for a configuration option,
> e.g. then it can be set with xinput; but I see in upstream similar
> requests closed during issue triagging[6], but that is probably a new
> upstream request altogether.
> 
> I may be not understanding the feature or stack correctly, so I would
> really appreciate if you can point me in the right direction.

If the issue persists, could you please ask in the upstream bug tracker and let 
us know the bug reference to be able to track the issue?

Best regards

> 1:
> https://wayland.freedesktop.org/libinput/doc/latest/palm_detection.html#disable-while-typing
> 2:
> https://who-t.blogspot.pe/2016/08/libinput-and-disable-while-typing.html
> 3: https://bugzilla.gnome.org/show_bug.cgi?id=764852 4:
> https://git.gnome.org/browse/gsettings-desktop-schemas/commit/?id=4c5b1c1df399d6afaaccb237e299ccd1d5d29ddd
> 5:
> https://anonscm.debian.org/cgit/pkg-xorg/lib/libinput.git/tree/src/evdev-mt-touchpad.c?h=libinput-1.6.3-1#n35
> 6: https://bugs.freedesktop.org/show_bug.cgi?id=88353
> 
> -- System Information:
> Debian Release: 9.1
> Architecture: amd64 (x86_64)
> Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
> 
> $ dpkg-query --show -f='${binary:Package}\t${Version}\n' libinput*
> libc6 libudev1 libwacom2 libevdev2 libmtdev1 libc6:amd64
> 2.24-11+deb9u1 libevdev2:amd641.5.6+dfsg-1
> libinput-bin  1.6.3-1
> libinput10:amd64  1.6.3-1
> libmtdev1:amd64   1.1.5-1+b1
> libudev1:amd64232-25+deb9u1
> libwacom2:amd64   0.22-1+b1
> -- no debconf information
> 
> 
> Best,
> 
> -Marco

-- 


signature.asc
Description: PGP signature

Bug#885032: upgrading libinput10 from 1.8.3-1 to 1.9.3-1 breaks ps2 keyboard

[Hector Oron]

Hello,

On Fri, Dec 22, 2017 at 08:28:56PM -0600, Brent S Elmer wrote:
> Package: libinput10
> Version: 1.9.3-1
> Severity: normal
> 
> When I upgrade libinput10 from 1.8.3-1 to 1.9.3-1 my ps2 keyboard no longer
> works on my hp desktop.  It appears to be caused by libinput10 and not
> libinput-bin.  When I revert libinput10 to 1.8.3-1 my ps2 keyboard works again
> even if libinput-bin is still at 1.9.3-1.  I see a similar bug report for
> libinput-bin but it is for a laptop in a docking station.  The problem is
> definitely in libinput10 for me.  USB keyboards will still work with 
> libinput10
> 1.9.3-1.
 
  Could you please retry with 1.11.2-1 version in unstable and report back? TIA

Regards


> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.4.0-1-amd64 (SMP w/2 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)
> 
> Versions of packages libinput10 depends on:
> ii  libc6 2.24-17
> ii  libevdev2 1.5.7+dfsg-1
> ii  libinput-bin  1.9.3-1
> ii  libmtdev1 1.1.5-1+b1
> ii  libudev1  235-3
> ii  libwacom2 0.26-1
> 
> libinput10 recommends no packages.
> 
> libinput10 suggests no packages.
> 
> -- no debconf information

-- 


signature.asc
Description: PGP signature

Bug#891858: offset negative related ( i think )

[Hector Oron]

Hello,

On Sun, Mar 18, 2018 at 08:46:18PM +, Sergy Pylypchuk wrote:
> Mar 18 21:07:33 xps9550 org.gnome.Shell.desktop[1124]: libinput error: client 
> bug: timer event18 gestures: offset negative (-111ms)
> Mar 18 21:08:04 xps9550 org.gnome.Shell.desktop[1124]: libinput error: client 
> bug: timer event18 tap: offset negative (-455ms)
> 
> But in my case it's correlates to very annoying behavior:   
>  I move cursor with touchpad and after random period (20 - 120 sec) cursor 
> freezes for a moment, this error appears, then cursor jumps further.
> 
> Laptop: Dell XPS 9550
> libinput10 version: 1.10.2-1
> Debian version: Buster

Could you please test version 1.11.2-1 and report back?
Thanks

> Attached file if part of apt/history.log

I do not see libinput in the upgraded list of packages.

Regards



signature.asc
Description: PGP signature

Bug#895756: libinput bug: invalid tap event TAP_EVENT_PALM in state TAP_STATE_TAPPED related

[Hector Oron]

On Sun, Apr 15, 2018 at 10:30:27PM +0530, Jeffrin Thalakkottoor wrote:
> Package: libinput10
> Version: 1.10.4-1
> 
> 
> hello ,
> 
> I found the following in syslog
> 
> Apr 15 19:41:54 debian org.gnome.Shell.desktop[1356]: libinput error:
> event1  - SynPS/2 Synaptics TouchPad: libinput bug: invalid tap event
> TAP_EVENT_PALM in state TAP_STATE_TAPPED

Could you please try with 1.11.2-1 version in unstable and report back with 
more information?

Regards

> --
> software engineer
> rajagiri school of engineering and technology

-- 


signature.asc
Description: PGP signature

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

[Hector Oron]

Hello,

2018-07-16 9:10 GMT+02:00 Svante Signell :
> I found out too that gdb 8.1 still FTBFS on GNU/Hurd. Why did you close
> that bug without applying any of the patches supplied? The bug report
> was submitted in November last year for gdb version 8.0-1.

I closed the bug, as your patchset was for old 8.0-1 version, which I
_wrongly_ understood, it was backported from upstream 8.1, so 8.1
would have compiled fine on GNU/Hurd and bug would have been closed.

> I'm working on an updated patch-set hoping that you can apply when
> submitted (and forward upstream).

Probably, I am able to do releases more frequently now. Please
checkout `debian/experimental` branch which is based on 8.1.90
snapshot release and send MR in gitlab. Also, please let me know
references when you submit patches upstream.

Hopefully, we can get the build fixed sooner now, and apologies for
any inconvenience.

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



-- Would you like to make a donation towards the upcoming Debian conference?
   Brochure: 
https://media.debconf.org/dc18/fundraising/debconf18_sponsorship_brochure_en.pdf

   ** https://debconf18.debconf.org/sponsors/become-a-sponsor/ **

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

[Hector Oron]

Hello,

2018-07-16 2:13 GMT+02:00 Hector Oron :
> Hello Svante,
>
>   I have pushed GDB 8.1, but apparently it does not yet have support for Hurd:
>   
> https://buildd.debian.org/status/fetch.php?pkg=gdb=hurd-i386=8.1-1=1531671238=0

I tried applied patchset on exodar (hurd porterbox) but it was also
failing to build.

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



-- Would you like to make a donation towards the upcoming Debian conference?
   Brochure: 
https://media.debconf.org/dc18/fundraising/debconf18_sponsorship_brochure_en.pdf

   ** https://debconf18.debconf.org/sponsors/become-a-sponsor/ **

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

[Hector Oron]

Hello Svante,

  I have pushed GDB 8.1, but apparently it does not yet have support for Hurd:
  
https://buildd.debian.org/status/fetch.php?pkg=gdb=hurd-i386=8.1-1=1531671238=0

Regards

On Mon, Jan 08, 2018 at 12:10:58AM +0100, Svante Signell wrote:
> Ping
> 
> On Wed, 2017-12-27 at 23:36 +0100, Svante Signell wrote:
> > On Tue, 2017-12-26 at 09:40 +0100, Héctor Orón Martínez wrote:
> > > 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.
> > 
> > Hi again,
> > 
> > Unfortunately I'm not authorized to NMU that package. However, the
> > reason for submitting the patches upstream is that they should be
> > applied there. In the meanwhile we could create a Debian package of
> > 8.0.1 (or later). If you don't have time maybe Samuel could help out
> > here?
> > 
> > Thanks for your reply anyway!

-- 


signature.asc
Description: PGP signature

Bug#870646: gdb: Make source package bootstrappable

[Hector Oron]

On Thu, Aug 03, 2017 at 12:09:23PM -0700, Daniel Schepler wrote:
> Source: gdb
> Version: 7.12-6
> Severity: wishlist
> 
> The gdb source package's Build-Depends on texlive-base is creating
> some build dependency cycles - for example:
> 
> texlive-base Depends on texlive-binaries
> texlive-bin Build-Depends on libgs-dev
> ghostscript Build-Depends on libopenjp2-7-dev
> openjpeg2 Build-Depends on dh-apache2
> apache2 Build-Depends on libaprutil1-dev
> apr-util Build-Depends on default-libmysqlclient-dev
> default-libmysqlclient-dev Depends on libmariadbclient-dev-compat
> mariadb-10.1 Build-Depends on gdb
> 
> It would be nice if gdb could be bootstrapped without the
> documentation.  Probably the easiest way would be to split out the
> documentation into a gdb-doc package, and then move texlive-base to
> Build-Depends-Indep.

I would need to have a closer look why we have texlive-base listed, as we 
already split out gdb-doc in a separate non-free source package. If you could 
help testing that would be great, it might take me a bit longer to work on 
that, but it certainly is for a great goal (bootstrapping).

Regards


signature.asc
Description: PGP signature

Bug#895035: osc package maintenance

[Hector Oron]

Hello Michal,

  I have NMU the package with the fix, even `openssl` has also fixed
their side on the same day.
  Find NMU diff attached. And of course, I have just noticed 898963
(another NMU) after I have uploaded my changes. :-/

2018-05-18 16:53 GMT+02:00 Michal Čihař <mic...@cihar.com>:
> Hello
>
> Feel free to do the upload, I'm quite busy with other things right now.
>
> Michal
>
> 18. května 2018 14:38:42 SELČ, Hector Oron <zu...@debian.org> napsal:
>>Hello Michal,
>>
>>  Do you mind if I go ahead and upload a fix for
>>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895035 ?
>>
>>  Or do you prefer to take care of it?
>>
>>Regards



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



-- Would you like to make a donation towards the upcoming Debian conference?
   Brochure: 
https://media.debconf.org/dc18/fundraising/debconf18_sponsorship_brochure_en.pdf

   ** https://debconf18.debconf.org/sponsors/become-a-sponsor/ **


diff -Nru osc-0.162.1/debian/changelog osc-0.162.1/debian/changelog
--- osc-0.162.1/debian/changelog	2018-01-23 09:47:02.0 +0100
+++ osc-0.162.1/debian/changelog	2018-05-23 16:58:00.0 +0200
@@ -1,3 +1,11 @@
+osc (0.162.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+- Contains fix (from upstream) for crash with memory corruption.
+(Closes: #895035)
+
+ -- Héctor Orón Martínez <zu...@debian.org>  Wed, 23 May 2018 16:58:00 +0200
+
 osc (0.162.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru osc-0.162.1/debian/patches/Disable-ssl-session-resumption.patch osc-0.162.1/debian/patches/Disable-ssl-session-resumption.patch
--- osc-0.162.1/debian/patches/Disable-ssl-session-resumption.patch	1970-01-01 01:00:00.0 +0100
+++ osc-0.162.1/debian/patches/Disable-ssl-session-resumption.patch	2018-05-23 16:55:21.0 +0200
@@ -0,0 +1,105 @@
+From: Marcus Huewe <suse-...@gmx.de>
+Date: Tue, 8 May 2018 14:23:08 +0200
+Subject: Disable ssl session resumption
+
+The old code could potentially yield to a use-after-free situation,
+which results in UB. For this, consider the following scenario, where
+osc performs several HTTPS requests (assumption: the server supports
+ssl session resumption):
+
+- HTTPS Request 1:
+  * a new SSL *s connection is established, which also creates a new
+SSL_SESSION *ss => ss->references == 1
+  * once the handshake is done, the ss is put into the session cache
+(see ssl_update_cache) => ss->references == 2
+  - osc saves the session ss in a class variable
+  - s is SSL_free()d, which calls SSL_SESSION_free => ss->references == 1
+
+- HTTPS Request 2:
+  * setup a new SSL *s connection that reuses the saved session ss
+=> ss->references == 2
+  * once the handshake is done, ssl_update_cache is called, which is a
+NOP, because s->hit == 1 (that is, the session was resumed)
+  * osc saves the session ss in a class variable
+  * s is SSL_free()d, which calls SSL_SESSION_free => ss->references == 1
+
+...
+
+> 2 hours later (see tls1_default_timeout)
+
+...
+
+- HTTPS Request 256:
+  * setup a new SSL *s connection that reuses the saved session ss
+=> ss->references == 2
+  * once the handshake is done, ssl_update_cache is called, but is
+_no_ NOP anymore
+  * ssl_update_cache flushes the session cache (this is done every
+255/256 (depending on the way we count) connections) => ss is
+SSL_SESSION_free()d => ss->references == 1
+  * osc saves the session ss in a class variable
+  * s is SSL_free()d, which calls SSL_SESSION_free:
+since ss->references == 1, ss is eventually free()d
+
+- HTTPS Request 257:
+  * setup a new SSL *s connection that reuses the saved session ss
+
+Since ss does not exist anymore, the remaining program execution is UB.
+
+(Note: SSL_free(...) is _NOT_ called, if M2Crypto 0.29 is used.
+M2Crypto 0.30 calls SSL_free(...) again.)
+
+Due to a bug in OpenSSL_1_1_0h (see openssl commit 8e405776858) the
+scenario from above can be triggered with exactly 2 HTTPS requests (the
+SSL_SESSION is not cached, because we configured SSL_VERIFY_PEER, but
+no sid_ctx was set). This is fixed in openssl commit c4fa1f7fc01.
+
+In order to reliably reuse a session, we probably need to listen to the
+session cache changes. Such callbacks could be registered via
+SSL_CTX_sess_set_new_cb and/or SSL_CTX_sess_set_remove_cb, but both
+functions are not provided by M2Crypto. Another idea is to directly utilize
+the session cache, but this also has to be implemented in M2Crypto first.
+Yet another approach is to retrieve the session via SSL_get1_session, which
+increases the session's refcnt, but this also needs to be implemented in
+M2Crypto first (if we choose to use this approach, we also have to make
+sure that we eventually free the session manually...).
+
+Fixes: #398 ("SIGSEGV on \&qu

Bug#899312: [pkg-go] Bug#899312: RM: debos [arm64 i386 mips mips64el mipsel] -- NBS; was built but didn't work

[Hector Oron]

Hello,

2018-05-22 16:56 GMT+02:00 Simon McVittie :
> Package: ftp.debian.org
> Severity: normal
>
> debos/1.0.0+git20180112.6e577d4-1 was built on all architectures, but
> is not currently usable on !amd64 due to architecture assumptions in
> fakemachine (see #898649, #898650). In debos/1.0.0+git20180328.8f2bc2a-1
> it was corrected to only build on amd64 until #898649 can be fixed.
> Please remove the obsolete arm64, i386 and mips* binaries.

As `debos` package maintainer, I second Simon's request.

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



-- Would you like to make a donation towards the upcoming Debian conference?
   Brochure: 
https://media.debconf.org/dc18/fundraising/debconf18_sponsorship_brochure_en.pdf

   ** https://debconf18.debconf.org/sponsors/become-a-sponsor/ **

Bug#893366: libwayland-dev: Uninstallable due to conflicting wayland-egl.pc

[Hector Oron]

Hello,

On Sun, Mar 18, 2018 at 11:35:52AM +0100, Guillem Jover wrote:
> Package: libwayland-dev
> Version: 1.14.91-1
> Severity: serious
> 
> Hi!
> 
> This package ships the file /usr/lib//pkgconfig/wayland-egl.pc
> which conflicts with the one installed by libegl1-mesa-dev, w/o any
> Replaces field or similar.
> 
> The problem also is that the file providing the shared library is also
> not pulled in by libwayland-dev, so packages that would find the
> pkg-config file would then fail to build, and they should really not
> be depending on the shared library directly.

Thanks for the report, I have pushed
  [debian-experimental 33a3903] libwayland-dev: fix installability issues
to address this issue. I would appreciate if you could review it.

Regards,
-- 


signature.asc
Description: PGP signature

Bug#888189: [DRE-maint] Bug#888189: ruby-innertube: FTBFS on ruby2.5: undefined method mock

[Hector Oron]

Hello,

2018-03-16 23:05 GMT+01:00 Georg Faerber :
> On 18-01-23 20:31:56, Chris West (Faux) wrote:
>> This package fails to build against ruby2.5. Soon, there will be a
>> transition to ruby2.5, and this package will FTBFS in sid.
>
> Upstream seems rather dead, popcon lists 11 installations.

Indeed, upstream seems dead.

> @Héctor: You've tagged this help: Are you using it personally, or DSA?

Open Build Service (obs-api) needs it for the webUI ruby on rails
application, that's why I am interested on getting it fixed.

It has nothing to do with DSA, for those see
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-ad...@lists.debian.org

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



-- Would you like to make a donation towards the upcoming Debian conference?
   Brochure: 
https://media.debconf.org/dc18/fundraising/debconf18_sponsorship_brochure_en.pdf

   ** https://debconf18.debconf.org/sponsors/become-a-sponsor/ **

Bug#888193: ruby-rmagick: FTBFS on ruby2.5: <FrozenError(<can't modify frozen Magick::Image>)>

[Hector Oron]

On Tue, Jan 23, 2018 at 08:38:43PM +, Chris West (Faux) wrote:
> Source: ruby-rmagick
> Version: 2.16.0-2
> Severity: important
> User: debian-r...@lists.debian.org
> Usertags: ruby2.5
> 
> Dear Maintainer,
> 
> This package fails to build against ruby2.5. Soon, there will
> be a transition to ruby2.5, and this package will FTBFS in sid.
> 
> There may be some details on the wiki about common problems:
> https://wiki.debian.org/Teams/Ruby/Ruby25Transition
> 
> Super confusing build log excerpt:
> 
> 
> Pending: (Failures listed here are expected and do not affect your suite's 
> status)
> 
>   1) Magick::Draw#marshal_dump #marshal_load marshals without an error
>  # this spec fails on some versions of ImageMagick
>  # ./spec/rmagick/draw_spec.rb:82
> 
> Finished in 0.27725 seconds (files took 0.12424 seconds to load)
> 36 examples, 0 failures, 1 pending
> 
> /usr/bin/ruby2.5 -w  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
> "test/test_all_basic.rb" -v
> /build/ruby-rmagick-2.16.0/test/Image2.rb:80: warning: assigned but unused 
> variable - img
> /build/ruby-rmagick-2.16.0/test/Image2.rb:305: warning: assigned but unused 
> variable - format
> /build/ruby-rmagick-2.16.0/test/Image2.rb:306: warning: assigned but unused 
> variable - size
> /build/ruby-rmagick-2.16.0/test/Image2.rb:307: warning: assigned but unused 
> variable - geometry
> /build/ruby-rmagick-2.16.0/test/Image2.rb:308: warning: assigned but unused 
> variable - image_class
> /build/ruby-rmagick-2.16.0/test/Image2.rb:401: warning: `-' after local 
> variable or literal is interpreted as binary operator
> /build/ruby-rmagick-2.16.0/test/Image2.rb:401: warning: even though it seems 
> like unary operator
> /build/ruby-rmagick-2.16.0/test/Image2.rb:536: warning: assigned but unused 
> variable - res
> /build/ruby-rmagick-2.16.0/test/Image2.rb:537: warning: assigned but unused 
> variable - res
> /build/ruby-rmagick-2.16.0/test/Image2.rb:538: warning: assigned but unused 
> variable - res
> /build/ruby-rmagick-2.16.0/test/Image2.rb:539: warning: assigned but unused 
> variable - res
> /build/ruby-rmagick-2.16.0/test/Image3.rb:683: warning: assigned but unused 
> variable - img
> /build/ruby-rmagick-2.16.0/test/ImageList1.rb:295: warning: assigned but 
> unused variable - cur
> /build/ruby-rmagick-2.16.0/test/ImageList1.rb:332: warning: assigned but 
> unused variable - res
> /build/ruby-rmagick-2.16.0/test/ImageList1.rb:333: warning: assigned but 
> unused variable - res
> /build/ruby-rmagick-2.16.0/test/Import_Export.rb:12: warning: assigned but 
> unused variable - res
> /build/ruby-rmagick-2.16.0/test/Magick.rb:312: warning: assigned but unused 
> variable - img
> 2.5.0
> String
> Loaded suite /usr/lib/ruby/vendor_ruby/rake/rake_test_loader
> Started
> Image1_UT: 
>   test_adaptive_blur: .: (0.002072)
>   test_adaptive_blur_channel: .: (0.002713)
>   test_adaptive_resize:   .: (0.000529)
>   test_adaptive_sharpen:  .: (0.000895)
>   test_adaptive_sharpen_channel:  .: (0.001748)
>   test_adaptive_threshold:.: (0.000333)
>   test_add_compose_mask:  .: (0.000255)
>   test_add_noise: .: (0.008137)
>   test_add_noise_channel: .: (0.007935)
>   test_affine_matrix: .: (0.001704)
>   test_alpha: F
> ===
> Failure: test_alpha(Image1_UT)
> /build/ruby-rmagick-2.16.0/test/Image1.rb:172:in `test_alpha'
>  169: assert_nothing_raised { @img.alpha Magick::ResetAlphaChannel }
>  170: assert_nothing_raised { @img.alpha Magick::SetAlphaChannel }
>  171: @img.freeze
>   => 172: assert_raise(FreezeError) { @img.alpha Magick::SetAlphaChannel }
>  173:   end
>  174: 
>  175:   def test_auto_gamma
> 
>  expected but was
> )>
> 
> diff:
> ? Ru   ntimeError 
> ? Froze  ()
> ===
> : (0.052752)
>   test_alpha_compat:  .: (0.000186)
>   test_auto_gamma:.: (0.012168)
>   test_auto_level:.: (0.000255)
>   test_auto_orient:   .: (0.000143)
>   test_bilevel_channel:   .: (0.000527)
>   test_black_threshold:   .: (0.000445)
> 
> 
> 
> ...
> 
> 
> 
> Finished in 42.696937665 seconds.
> --
> 385 tests, 232948 assertions, 15 failures, 0 errors, 0 pendings, 0 omissions, 
> 0 notifications
> 96.1039% passed
> 

Bug#888196: ruby-sexp-processor: FTBFS on ruby2.5: BOOM GOES THE STACK

[Hector Oron]

On Tue, Jan 23, 2018 at 08:43:02PM +, Chris West (Faux) wrote:
> Source: ruby-sexp-processor
> Version: 4.7.0-1
> Severity: important
> User: debian-r...@lists.debian.org
> Usertags: ruby2.5
> 
> Dear Maintainer,
> 
> This package fails to build against ruby2.5. Soon, there will
> be a transition to ruby2.5, and this package will FTBFS in sid.

Find patch attached that fixes the build.

Regards
diff -Nru ruby-sexp-processor-4.7.0/debian/changelog ruby-sexp-processor-4.7.0/debian/changelog
--- ruby-sexp-processor-4.7.0/debian/changelog	2016-07-21 06:11:59.0 +0200
+++ ruby-sexp-processor-4.7.0/debian/changelog	2018-03-10 11:59:35.0 +0100
@@ -1,3 +1,10 @@
+ruby-sexp-processor (4.7.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with Ruby2.5 (Closes: #888196)
+
+ -- Héctor Orón Martínez   Sat, 10 Mar 2018 11:59:35 +0100
+
 ruby-sexp-processor (4.7.0-1) unstable; urgency=medium
 
   * Imported Upstream version 4.7.0
diff -Nru ruby-sexp-processor-4.7.0/debian/patches/series ruby-sexp-processor-4.7.0/debian/patches/series
--- ruby-sexp-processor-4.7.0/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ ruby-sexp-processor-4.7.0/debian/patches/series	2018-03-10 11:59:21.0 +0100
@@ -0,0 +1 @@
+update-tests-to-use-sexps-not-raw-arrays.patch
diff -Nru ruby-sexp-processor-4.7.0/debian/patches/update-tests-to-use-sexps-not-raw-arrays.patch ruby-sexp-processor-4.7.0/debian/patches/update-tests-to-use-sexps-not-raw-arrays.patch
--- ruby-sexp-processor-4.7.0/debian/patches/update-tests-to-use-sexps-not-raw-arrays.patch	1970-01-01 01:00:00.0 +0100
+++ ruby-sexp-processor-4.7.0/debian/patches/update-tests-to-use-sexps-not-raw-arrays.patch	2018-03-10 11:59:35.0 +0100
@@ -0,0 +1,96 @@
+commit 05838e8658872f71a7c01cc66333ca76bea2a1bd
+Author: Ryan Davis 
+Date:   Sat May 20 02:35:03 2017 -0800
+
+Updated tests to use sexps, not raw arrays
+[git-p4: depot-paths = "//src/sexp_processor/dev/": change = 11326]
+
+Index: ruby-sexp-processor-4.7.0/test/test_sexp_processor.rb
+===
+--- ruby-sexp-processor-4.7.0.orig/test/test_sexp_processor.rb	2016-03-31 01:14:48.0 +0200
 ruby-sexp-processor-4.7.0/test/test_sexp_processor.rb	2018-03-10 12:03:31.687705413 +0100
+@@ -72,7 +72,7 @@
+   end
+ 
+   def rewrite_major_rewrite(exp)
+-exp[0] = :rewritable
++exp.sexp_type = :rewritable
+ exp
+   end
+ end
+@@ -98,13 +98,13 @@
+   end
+ 
+   def test_process_specific
+-a = [:specific, [:x, 1], [:y, 2], [:z, 3]]
+-expected = [:blah, [:x, 1], [:y, 2], [:z, 3]]
++a = s(:specific, s(:x, 1), s(:y, 2), s(:z, 3))
++expected = s(:blah, s(:x, 1), s(:y, 2), s(:z, 3))
+ assert_equal(expected, @processor.process(a))
+   end
+ 
+   def test_process_generic
+-a = [:blah, 1, 2, 3]
++a = s(:blah, 1, 2, 3)
+ expected = a.deep_clone
+ assert_equal(expected, @processor.process(a))
+   end
+@@ -131,7 +131,7 @@
+ @processor.unsupported << :strip
+ 
+ assert_raises UnsupportedNodeError do
+-  @processor.process([:whatever])
++  @processor.process(s(:whatever))
+ end
+   end
+ 
+@@ -139,14 +139,14 @@
+ @processor.strict = true
+ @processor.unsupported = [ :unsupported ]
+ assert_raises UnsupportedNodeError do
+-  @processor.process([:unsupported, 42])
++  @processor.process(s(:unsupported, 42))
+ end
+   end
+ 
+   def test_strict
+ @processor.strict = true
+ assert_raises UnknownNodeError do
+-  @processor.process([:blah, 1, 2, 3])
++  @processor.process(s(:blah, 1, 2, 3))
+ end
+   end
+   def test_strict=; skip; end #Handled
+@@ -154,12 +154,12 @@
+   def test_require_empty_false
+ @processor.require_empty = false
+ 
+-assert_equal s(:nonempty, 1, 2, 3), @processor.process([:nonempty, 1, 2, 3])
++assert_equal s(:nonempty, 1, 2, 3), @processor.process(s(:nonempty, 1, 2, 3))
+   end
+ 
+   def test_require_empty_true
+ assert_raises NotEmptyError do
+-  @processor.process([:nonempty, 1, 2, 3])
++  @processor.process(s(:nonempty, 1, 2, 3))
+ end
+   end
+   def test_require_empty=; skip; end # handled
+@@ -175,7 +175,7 @@
+   end
+ 
+   def test_rewrite_different_type
+-assert_equal(s(:rewritable, :b, :a),
++assert_equal(s(:major_rewrite, :a, :b),
+  @processor.rewrite(s(:major_rewrite, :a, :b)))
+   end
+ 
+@@ -282,7 +282,7 @@
+   @processor.process(s(:string, "string")) # should raise
+ end
+ 
+-@processor.process([:expected])# shouldn't raise
++@processor.process(s(:expected))# shouldn't raise
+   end
+   def test_expected=; skip; end # handled
+ 


signature.asc
Description: PGP signature

Bug#888121: ruby-delayed-job-active-record: FTBFS on ruby2.5: `method_missing': undefined method `yaml_as'

[Hector Oron]

Hello,

  The issue below is caused by `ruby-delayed-job`. Find patch attached which 
fixes the problem.

Regards

On Tue, Jan 23, 2018 at 03:09:02PM +, Chris West (Faux) wrote:
> Source: ruby-delayed-job-active-record
> Version: 4.0.3-2
> Severity: important
> User: debian-r...@lists.debian.org
> Usertags: ruby2.5
> 
> Dear Maintainer,
> 
> This package fails to build against ruby2.5. Soon, there will
> be a transition to ruby2.5, and this package will FTBFS in sid.
> 
> There may be some details on the wiki about common problems:
> https://wiki.debian.org/Teams/Ruby/Ruby25Transition
> 
> Build log excerpt:
> 
> ...
> 
> Finished in 1.56 seconds (files took 2.53 seconds to load)
> 88 examples, 0 failures
> 
> /usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.5  
>  │
> └──┘
> 
> GEM_PATH=debian/ruby-delayed-job-active-record/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
>  ruby2.5 -e gem\ \"delayed_job_active_record\"
> 
> ┌──┐
> │ Run tests for ruby2.5 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/build/ruby-delayed-job-active-record-4.0.3/debian/ruby-delayed-job-active-record/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=debian/ruby-delayed-job-active-record/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
>  ruby2.5 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation
> /usr/lib/ruby/vendor_ruby/thread_safe/cache.rb:155: warning: constant 
> ::Fixnum is deprecated
> /usr/lib/ruby/vendor_ruby/thread_safe/cache.rb:155: warning: constant 
> ::Fixnum is deprecated
> /usr/lib/ruby/vendor_ruby/active_record/dynamic_matchers.rb:26:in 
> `method_missing': undefined method `yaml_as' for ActiveRecord::Base:Class 
> (NoMethodError)
> Did you mean?  yaml_tag
>   from 
> /usr/lib/ruby/vendor_ruby/delayed/serialization/active_record.rb:4:in 
> `'
>   from 
> /usr/lib/ruby/vendor_ruby/delayed/serialization/active_record.rb:3:in 
> `'
>   from 
> /usr/lib/ruby/vendor_ruby/delayed/serialization/active_record.rb:2:in ` (required)>'
>   from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
> `require'
>   from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
> `require'
>   from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:274:in 
> `block in require'
>   from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:240:in 
> `load_dependency'
>   from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:274:in 
> `require'
>   from /usr/lib/ruby/vendor_ruby/delayed/worker.rb:64:in `backend='
>   from 
> /build/ruby-delayed-job-active-record-4.0.3/lib/delayed_job_active_record.rb:5:in
>  `'
>   from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
> `require'
>   from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
> `require'
>   from /build/ruby-delayed-job-active-record-4.0.3/spec/helper.rb:8:in 
> `'
>   from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
> `require'
>   from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
> `require'
>   from 
> /build/ruby-delayed-job-active-record-4.0.3/spec/delayed/backend/active_record_spec.rb:1:in
>  `'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
> `load'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
> `block in load_spec_files'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
> `each'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
> `load_spec_files'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:100:in `setup'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:86:in `run'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
>   from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
>   from /usr/bin/rspec:4:in `'
> /usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.5" failed. Exiting.
> dh_auto_install: dh_ruby --install 
> /build/ruby-delayed-job-active-record-4.0.3/debian/ruby-delayed-job-active-record
>  returned exit code 1
> debian/rules:10: recipe for target 'binary' 

Bug#891714: [pkg-go] Bug#891714: missing /bin/busybox

[Hector Oron]

Hello,

FYI, patch queued for next release:
  
https://anonscm.debian.org/cgit/pkg-go/packages/debos.git/commit/?id=6c6f32e3729c6966f6bc23c02a6612c2af1c3615

On Wed, Feb 28, 2018 at 10:21:04AM +0100, Geert Stappers wrote:
> Control: tag -1 patch
> 
> On Wed, Feb 28, 2018 at 09:33:31AM +0100, Michael Stapelberg wrote:
> > On Wed, Feb 28, 2018 at 9:24 AM, Geert Stappers wrote:
> > } While testdriving debos was encountered that /bin/busybox is missing
> > >
> > > | $ apt-file search /bin/busybox
> > > | busybox: /bin/busybox
> > > | busybox-static: /bin/busybox
> > >
> > > Which one to use?
> >
> > Either version of busybox should be fine. Prefer ???busybox??? unless you 
> > have
> > a reason to use the static variant.
> 
> --- a/debian/control
> +++ b/debian/control
> @@ -24,7 +24,9 @@ Testsuite: autopkgtest-pkg-go
>  Package: debos
>  Architecture: any
>  Built-Using: ${misc:Built-Using}
> -Recommends: bmap-tools, ovmf
> +Recommends: bmap-tools
> +  , busybox | busybox-static
> +  , ovmf
>  Depends: ${shlibs:Depends},
>   ${misc:Depends},
>   systemd-container
> 
> Groeten
> Geert Stappers
> -- 
> Leven en laten leven

-- 


signature.asc
Description: PGP signature

Bug#854627: root application will not run under wayland

[Hector Oron]

Hello,

  Andrius Štikona and Markus Ongyerth are totally right, AFAIK.
  If it's an X11 app that simply cannot be run without root, then you need the 
xhost command to allow only local connections from the root user.
  If it's a native Wayland app that cannot run without root, then you probably 
bind-mount the wayland socket from the user's $XDG_RUNTIME_DIR to the root's. 
(I've never done it myself)
  Whether such access should be granted by default to the root user is a policy 
decision, up for the DE or distribution or admin.
  Personally I'd like to see the access not granted, so there would be more 
pressure to fix the apps to not run GUI as root.
  Therefore I am resolving this issue as 'wontfix'.

Regards


signature.asc
Description: PGP signature

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

[Hector Oron]

Hello,

  I just realized I have attached debdiff for wrong version, attached
debdiff for version against stable.

Regards

2018-03-04 23:13 GMT+01:00 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



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



-- Would you like to make a donation towards the upcoming Debian conference?
   Brochure: 
https://media.debconf.org/dc18/fundraising/debconf18_sponsorship_brochure_en.pdf

   ** https://debconf18.debconf.org/sponsors/become-a-sponsor/ **


diff -Nru obs-build-20160921/debian/changelog obs-build-20160921/debian/changelog
--- obs-build-20160921/debian/changelog	2016-09-23 15:49:42.0 +0200
+++ obs-build-20160921/debian/changelog	2018-03-04 23:18:00.0 +0100
@@ -1,3 +1,11 @@
+obs-build (20160921-1+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   Sun, 04 Mar 2018 23:18:00 +0100
+
 obs-build (20160921-1) unstable; urgency=medium
 
   [ Andrew Lee (李健秋) ]
diff -Nru obs-build-20160921/debian/patches/Improve-sanity-checks-in-extractbuild.patch obs-build-20160921/debian/patches/Improve-sanity-checks-in-extractbuild.patch
--- obs-build-20160921/debian/patches/Improve-sanity-checks-in-extractbuild.patch	1970-01-01 01:00:00.0 +0100
+++ obs-build-20160921/debian/patches/Improve-sanity-checks-in-extractbuild.patch	2018-03-04 23:16:40.0 +0100
@@ -0,0 +1,34 @@
+From fc36b1c95afbe11e65fd1ed6f75c1824cdb26230 Mon Sep 17 00:00:00 2001
+Message-Id: 
+From: Marcus Huewe 
+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-20160921/debian/patches/series obs-build-20160921/debian/patches/series
--- obs-build-20160921/debian/patches/series	2016-09-23 07:04:44.0 +0200
+++ obs-build-20160921/debian/patches/series	2018-03-04 23:17:33.0 +0100
@@ -1,2 +1,4 @@
 0001-Use-obs-build-in-locations-and-executable-names-inst.patch
 0010_find-perm_slash.diff
+
+Improve-sanity-checks-in-extractbuild.patch

Bug#886772: ITP: debos -- Debian OS builder

[Hector Oron]

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

* Package name: debos
  Version : 1.0.0+git20171222.87b0d5e-1
  Upstream Author :
* URL : https://github.com/go-debos/debos
* License : Apache-2.0
  Programming Lang: Go
  Description : Debian OS builder

 debos Debian OS builder. debos is a tool to make creation of various
 debian based os "images" simpler. While most other tools focus on
 specific use-case, debos is more meant as a toolchain to make comon
 actions trivial while providing enough rope to do whatever tweaking that
 might be required behind the scene.
 debos Debian OS builder. debos is a tool to make creation of various
 debian based os "images" simpler. While most other tools focus on
 specific use-case, debos is more meant as a toolchain to make comon
 actions trivial while providing enough rope to do whatever tweaking that
 might be required behind the scene.
 .
 debos expects a yaml file as input, syntax description can be found at:
   https://godoc.org/github.com/go-debos/debos/actions
 .
 and examples are to be found at:
   https://github.com/go-debos/debos-recipes

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


-- Would you like to make a donation for Debian Conference?
   ** http://debconf18.debconf.org **

Bug#886769: ITP: fakemachine -- create and spawn virtual machines

[Hector Oron]

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

* Package name: fakemachine
  Version : 0.0~git20171207.6af110d-1
  Upstream Author : Sjoerd Simons 
* URL : https://github.com/go-debos/fakemachine
* License : Apache-2.0
  Programming Lang: Go
  Description : create and spawn virtual machines

  Create and spawn virtual machines for building images with debos tool.

  This is a build dependency for `debos'.

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


-- Would you like to make a donation for Debian Conference?
   ** http://debconf18.debconf.org/ **

Bug#886767: ITP: go-flags -- go command line option parser

[Hector Oron]

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

* Package name: go-flags
  Version : 1.3.0+git20170926.f88afde-1
  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 library provides similar functionality to the builtin flag library
 of Go, but provides much more functionality and nicer formatting. From
 the documentation:
 .
 Package flags provides an extensive command line option parser.  The flags
 package is similar in functionality to the go builtin flag package but
 provides more options and uses reflection to provide a convenient and
 succinct way of specifying command line options.
 .
 More information can be found in the godocs:
 http://godoc.org/github.com/jessevdk/go-flags

 This is build dependency for `debos' Go application.

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


-- Would you like to make a donation for Debian Conference?
   ** http://debconf18.debconf.org/ **

Bug#886766: ITP: golang-github-ostreedev-ostree-go -- Golang bindings for OSTree

[Hector Oron]

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

* Package name: golang-github-ostreedev-ostree-go
  Version : 0.0~git20171027.cb6250d-1
  Upstream Author : OSTree Project
* URL : https://github.com/ostreedev/ostree-go
* License : ISC
  Programming Lang: Go
  Description : Golang bindings for OSTree

 OSTree-Go Go bindings for OSTree. Find out more about OSTree here
 (https://github.com/ostreedev/ostree)

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


-- Would you like to make a donation for Debian Conference?
   ** http://debconf18.debconf.org/ **

Bug#886764: ITP: golang-github-14rcole-gopopulate -- A small library to populate a directory with random data

[Hector Oron]

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

* Package name: golang-github-14rcole-gopopulate
  Version : 0.0~git20171207.91c73a7-1
  Upstream Author : Ryan Cole
* URL : https://github.com/14rcole/gopopulate
* License : MIT License
  Programming Lang: Go
  Description : A small library to populate a directory with random data

 populate a directory with random data. This package is used for ostree Go
 bindings testing.

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

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


-- Would you like to make a donation for Debian Conference?
   ** http://debconf18.debconf.org/ **

Bug#878217:

[Hector Oron]

Package: ttf-adf
Version: 0.20090423-2
Severity: important

Hello,

  I believe ttf-adf is replaced by fonts-adf, therefore it should
eventually be removed from the unstable Debian archive. Could you
please confirm and report to ftp-masters if that's the case.

  I set severity important as I believe this package should not be
part of next release, but if you think I am mistaken, please downgrade
it or set to appropriate one.

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

Bug#842140: ITP: obs-signd -- open build service signer client and daemon

[Hector Oron]

Hi,

2017-03-01 14:47 GMT+01:00 Riku Voipio :
> What's the status with this? Is there some preliminary packaging already?

There is one old version packaged at:
  https://repositories.collabora.co.uk/obs/debian/pool/tools/o/obs-signd/

We should look at fixing gnupg2 related issues before doing Debian upload.

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

Bug#842140: ITP: obs-signd -- open build service signer client and daemon

[Hector Oron]

On Wed, Oct 26, 2016 at 02:23:36PM +0100, Dimitri John Ledkov wrote: 
> Does this still require a patched/custom gnupg?

Currently, yes, that's probably why it has not been uploaded as it won't work
with Debian gnupg2.

The main issue is described at:
  https://bugs.gnupg.org/gnupg/issue1646

An elegant solution is proposed at:
  https://bugs.gnupg.org/gnupg/msg5172

However upstream is not willing to move to gnupg2 at the moment, therefore we
either need to do that work, or wait until upstream moves on.

Regards,
-- 
  Hector Oron


signature.asc
Description: PGP signature

Bug#846597: linux: please enable `perf data' support

[Hector Oron]

Hello,

On Fri, Dec 02, 2016 at 02:37:21PM +0100, Sebastian Andrzej Siewior wrote:
> diff --git a/debian/templates/control.source.in 
> b/debian/templates/control.source.in
> index 08969a3da9d9..2a1fdf048823 100644
> --- a/debian/templates/control.source.in
> +++ b/debian/templates/control.source.in
> @@ -41,6 +41,8 @@ Standards-Version: 3.9.8
>   libperl-dev ,
>   libunwind8-dev [amd64 armel armhf arm64 i386]  !nopython>,
>   python-dev ,
> + libbabeltrace-dev ,
> + libbabeltrace-ctf-dev ,

Out of curiosity,

The final patch that got merged has versioned depends on babeltrace >=1.5.0, but
Jessie has 1.2.3. While trying to do a linux kernel backport, I have come up
with a question if we really need babeltrace >=1.5.0 or if 1.2.3 has the needed
features. Do you happen to know?

Note: In anycase, I am preparing a backport of babeltrace.

Regards

>  # used by upstream to build usbip
>   autoconf ,
>   automake ,
> -- 
> 2.10.2
> 


-- 
  Hector Oron


signature.asc
Description: PGP signature

Bug#848362: gdb: incorrectly marked as Multi-Arch: same

[Hector Oron]

Hello,

2016-12-16 18:10 GMT+01:00 Sven Joachim :
> Package: gdb
> Version: 7.12-3

> Since version 7.12-2, gdb is marked as "Multi-Arch: same" which is not
> correct.  Because /usr/bin/gdb (among other files) is different across
> architectures, multiple versions of gdb are not actually coinstallable.

This was added due to the addition of jit-reader.h header (trying to
avoid creating gdb-dev package), but you are right that might not work
as I initially expected and I should probably drop that stanza for the
release. I'll revert that change on the upcoming upload.

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

Bug#848307: gdb-doc has no binaries on any arch

[Hector Oron]

Hello Sven,

2016-12-16 8:18 GMT+01:00 Sven Joachim :
> Source: gdb-doc
> Version: 7.12-1
> Severity: serious
>
> The latest upload of gdb-doc included only the source, but the
> autobuilders are not allowed to build the binary package because there
> is no XS-Autobuild field in debian/control.
>
> And because of #825398 the binary package has already been removed from
> unstable, so you will have to build and upload it. :-(

You were amazingly quick :-)

Yes, I did source only upload, which I think I did in past, but this
time did not build, one reason as you mentioned, we do not set
autobuild flag in package metadata and we have not package
whitelisted. I was checking if it would be possible to build it in the
builders, but probably it'll be easier to do newer source+binary
upload.

I should fix this in few minutes. :-)

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

Bug#831470: gdb manual: missing documentation of the -tui option

[Hector Oron]

Hey Pablo,

On Sat, Jul 16, 2016 at 10:03:53PM +0800, Paul Wise wrote:
> Package: gdb-doc
> Version: 7.11.1-1
> Severity: normal
> File: /usr/share/man/man1/gdb.1.gz
> 
> The manual page is missing documentation of the -tui option:
> 
> https://sourceware.org/gdb/onlinedocs/gdb/TUI.html

  Some time ago, there was a patch for such purpose (man-page-args.patch)
  This was coming from similar request to this one:
https://bugs.debian.org/362795

  However manpage was rewriten as texinfo document and licensed under GFDL 1.3
  I was pondering if we should be able to modify the text and document the
  feature in the manpage, however I understand from license requirements:

"
  Copyright @copyright{} 1988-2016 Free Software Foundation, Inc.

  Permission is granted to copy, distribute and/or modify this document
  under the terms of the GNU Free Documentation License, Version 1.3 or
  any later version published by the Free Software Foundation; with the
  Invariant Sections being ``Free Software'' and ``Free Software Needs
  Free Documentation'', with the Front-Cover Texts being ``A GNU Manual,''
  and with the Back-Cover Texts as in (a) below.

  (a) The FSF's Back-Cover Text is: ``You are free to copy and modify
  this GNU Manual.  Buying copies from GNU Press supports the FSF in
  developing GNU and promoting software freedom.''
"

  Does the manual page have covers to modify? 
  
  GFDL 4A:
"
  A. Use in the Title Page (and on the covers, if any) a title distinct
 from that of the Document, and from those of previous versions
 (which should, if there were any, be listed in the History section
 of the Document).  You may use the same title as a previous version
 if the original publisher of that version gives permission.
"
  To accomplish that I understand that we need to modify the manpage title
  page, which is the program name.
  
  Also in Debian package changelog you might find the following comment:
"
- Drop man-page-args.patch and man-page-order.patch:
  Manpages are dead to us now (not DFSG free), and the source is in
  texinfo now anyway.
"

  Given all the above I tend to think that we should propose upstream to
  document such option in the manpage instead of us modifying it.

  In anycase, you should be able to access TUI pages and know about it by
  checking:
info gdb
  or
file:///usr/share/doc/gdb-doc/html/gdb/TUI.html

Regards,
-- 
Hector Oron


signature.asc
Description: PGP signature

Bug#835439: gdb --write segfaults on quit in _bfd_elf_strtab_finalize

[Hector Oron]

Hello,

2016-12-13 23:38 GMT+01:00 Ben Harris :
> It looks like it's already been reported upstream:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=20948

Excellent! Thanks very much!

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

Bug#834575: gdb: FTBFS on hurd-i386

[Hector Oron]

On Wed, Aug 17, 2016 at 09:52:14AM +0200, Svante Signell wrote:
> Source: gdb
> Version: 7.11.1-2
> Severity: important
> Tags: patch
> User: debian-h...@lists.debian.org
> Usertags: hurd

Hello,

  I have applied your patches on top of 7.12-1 and attempt to build on
  hurd-i386 porterbox, but the build end up failing for me.

  Could you please attempt to build GDB under hurd and submit a patch, so we
  can apply that before release.

Thanks,
-- 
  Hector Oron


signature.asc
Description: PGP signature

Bug#836802: gdb: Process record does not support instruction 0xc5

[Hector Oron]

On Mon, Sep 05, 2016 at 06:33:29PM -0400, mudongliang wrote:
> Package: gdb
> Version: 7.11.1-2
> Severity: normal
> Tags: newcomer
> 
> Dear Maintainer,
> 
> $ cat simple.c
> 
> #include 
> void foo (char *bar)
> {
> char  c[12];
> 
> strcpy(c, bar);  // no bounds checking
> }
> int main (int argc, char **argv)
> {
> foo(argv[1]);
> }
> 
> $ gdb simple
> ..
> (gdb) b main
> Breakpoint 1 at 0x40050c
> (gdb) r
> Starting program: /home/mudongliang/Work/simple
> 
> Breakpoint 1, 0x0040050c in main ()
> (gdb) record full
> (gdb) c
> Continuing.
> Process record does not support instruction 0xc5 at address 0x77dee807.
> Process record: failed to record execution log.

Thanks for the report, the issues persists with the upcoming 7.12 package.
Could you please bring this topic with upstream GDB and keep this bug updated?

Regards,
-- 
  Hector Oron


signature.asc
Description: PGP signature

Bug#835439: gdb --write segfaults on quit in _bfd_elf_strtab_finalize

[Hector Oron]

On Thu, Aug 25, 2016 at 06:40:47PM +0100, Ben Harris wrote:
> Package: gdb
> Version: 7.11.1-2
> Severity: normal
> 
> Dear Maintainer,
> 
> When I use "gdb --write" on a trivial executable and immediately type
> "quit", GDB segfaults:
> 
> wraith:/tmp/hello$ cat > hello.c
> #include 
> 
> int main(int argc, char **argv)
> {
> 
> printf("hello, world\n");
> return 0;
> }
> wraith:/tmp/hello$ gcc -o hello hello.c
> wraith:/tmp/hello$ gdb --quiet --write hello
> Reading symbols from hello...(no debugging symbols found)...done.
> (gdb) quit
> Segmentation fault

Thanks for the report, I am able to reproduce it with the upcoming 7.12 package.
Could you please forward this one upstream to the GNU GDB community and keep 
this one up to date.

Regards,
-- 
  Hector Oron


signature.asc
Description: PGP signature

Bug#840375: NMU for dejagnu

[Hector Oron]

Hello,

2016-11-23 17:59 GMT+01:00 Dr. Tobias Quathamer :
> please find attached the patch for the NMU I've just uploaded to remove
> the Build-Depends on jade.

Thanks! It looks fine.

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

Bug#842919: failed armhf build of xen 4.8.0~rc3-1 [and 1 more messages]

[Hector Oron]

Hello,

2016-11-08 16:01 GMT+01:00 Ian Jackson :

> FYI it looks[1] like the libvirt rebuilds for the xen transition have
> been afflicted with the same problem, on at least some architectures.

Given back

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

Bug#842919: failed armhf build of xen 4.8.0~rc3-1 [and 1 more messages]

[Hector Oron]

Hello,

2016-11-08 11:41 GMT+01:00 Ian Jackson :
> Kurt Roeckx writes ("Re: failed armhf build of xen 4.8.0~rc3-1 [and 1 more 
> messages]"):


>> The chroots get updated on sunday and wednesday. It seems to be
>> easier to just wait for wednesday and give back those few that are
>> affected. It looks like all buildds actually need the new chroot.

In case you have not noticed, the packages have already been built.

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

Bug#842551: gdb fails to build from source in binary NMU

[Hector Oron]

On Sun, Oct 30, 2016 at 01:16:50PM +0100, Santiago Vila wrote:
> reassign 842551 cdbs
> affects 842551 src:gdb
> forcemerge 837006 842551
> thanks
> 
> On Sun, Oct 30, 2016 at 11:47:16AM +0100, Matthias Klose wrote:
> > Package: src:gdb
> > Version: 7.11.1-2
> > Severity: serious
> > Tags: sid stretch
> > 
> > According to
> > https://buildd.debian.org/status/fetch.php?pkg=gdb=amd64=7.11.1-2%2Bb1=1476144043
> > 
> > gdb fails to build from source on all architectures:
> > [...]
> > /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
> > resolved
> 
> This is a bug in cdbs and it was already visible in the BTS web page for gdb:
> 
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gdb

FWIW, this regression was introduced with CDBS 0.4.144, possibly with the 
changes to python-autotools.mk CDBS class.
 
Regards,
-- 
  Hector Oron


signature.asc
Description: PGP signature

Bug#837420: #837420 - dietlibc: FTBFS with bindnow and PIE enabled

[Hector Oron]

Hello guys,

2016-10-28 8:01 GMT+02:00 Christian Seiler :
> Am 25. Oktober 2016 22:54:47 MESZ, schrieb Thorsten Glaser :

>>Since I’m back now,
> Oh, nice, didn't realize that. Welcome back.

Indeed, I also did not realize Thorsten was back. Welcome back!

>>if you wish I can still help out.)
> In principle, yes (assuming zumbi agrees), but I have some additional changes 
> queued locally that I'd like to merge in this update first. Unfortunately I 
> had a family emergency recently which kind of ruined my plans a bit, so I 
> didn't get to it last weekend. I'll have time this weekend, but in case 
> something else happens and I still haven't gotten to it until Monday morning, 
> feel free to NMU the package then (directly, no DELAYED), targeting just this 
> bug.

Christian Seiler was done excellent job keeping up the package, I hope
Thorsten agrees on that, he did as well took good care of dietlibc in
the past. I have no objection for Thorsten to get back to dietlibc
maintenance work, you guys are excellent on it. However I would like
you to fix some workflow which avoids stepping on others toes and
avoid potential future issues. In near future, possibly I should step
down on this package maintenance as I do not use it anymore, and you
are being good takers/maintainers for it.

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

Bug#838349: ITP: osc-plugins-dput -- dput plugin for OpenSUSE (buildsystem) commander

[Hector Oron]

Hello,

2016-09-20 11:35 GMT+02:00 Michal Čihař :
> Hi Héctor
>
> Héctor Orón Martínez píše v Út 20. 09. 2016 v 10:14 +0200:
>> Package: wnpp
>> Severity: wishlist
>> Owner: "Héctor Orón Martínez" 
>>
>> * Package name: osc-plugins-dput
>>   Version : 20160627.0
>>   Upstream Author : Collabora Ltd
>> * URL :
>> http://cgit.collabora.com/git/singularity/tools/osc-plugins-dput.git/
>
> The URL doesn't seem to work...

Sorry, I had out of date URL... current is...
  https://git.collabora.com/cgit/osc-plugins-dput.git/

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

Bug#834505: arm64 boot failure with large physical memory range

[Hector Oron]

On Tue, Aug 16, 2016 at 04:39:15PM +0200, Hector Oron wrote:
> On Tue, Aug 16, 2016 at 01:13:28PM +0100, Leif Lindholm wrote:
> > Package: linux
> > Version: 4.6.4-1
> > X-Debbugs-CC: st...@einval.com, woo...@wookware.org, zheng...@linaro.org
> > 
> > Upstream commit 211102d85 ("arm64: defconfig: enable 48-bit virtual
> > addresses") changed the default configuration for arm64 to be 48-bit
> > VA (CONFIG_ARM64_VA_BITS_48). This is required in order to be able to
> > access the full amount of RAM available on some current arm64 systems
> > (currently with large memory holes, but could apply to any system with
> > >512GB of RAM). Without this, on these systems, the kernel will fail
> > to access the initrd, which will have been located near top of RAM by
> > GRUB. Error message given is:
> > ---
> > initrd not fully accessible via the linear mapping -- please check
> > your bootloader ...
> > ---
> > 
> > So please enable CONFIG_ARM64_VA_BITS_48 for arm64 kernels.
> > 
> > Note: this change _will_ cause breakage in certain userland software
> > making non-portable assumptions about available of top address bits
> > for pointer tagging - including luajit and mozilla-js (and hence
> > everything using mozilla-js).
> 
> FTR, this is an issue DSA is having booting arm64 machine donated by
> Gigabyte MR30-AR1. I am currently building a kernel, to get a d-i image
> and test this proposed fix.
> 
> I'll follow up with the results.

Ok, that worked fine, in addition to:
CONFIG_ARM64_VA_BITS_48=y
we also need to set on arm64
CONFIG_ACPI=y

As we are using ACPI for booting MR30-AR1 device.

Regards,
-- 
  Hector Oron


signature.asc
Description: PGP signature

Bug#834505: arm64 boot failure with large physical memory range

[Hector Oron]

On Tue, Aug 16, 2016 at 01:13:28PM +0100, Leif Lindholm wrote:
> Package: linux
> Version: 4.6.4-1
> X-Debbugs-CC: st...@einval.com, woo...@wookware.org, zheng...@linaro.org
> 
> Upstream commit 211102d85 ("arm64: defconfig: enable 48-bit virtual
> addresses") changed the default configuration for arm64 to be 48-bit
> VA (CONFIG_ARM64_VA_BITS_48). This is required in order to be able to
> access the full amount of RAM available on some current arm64 systems
> (currently with large memory holes, but could apply to any system with
> >512GB of RAM). Without this, on these systems, the kernel will fail
> to access the initrd, which will have been located near top of RAM by
> GRUB. Error message given is:
> ---
> initrd not fully accessible via the linear mapping -- please check
> your bootloader ...
> ---
> 
> So please enable CONFIG_ARM64_VA_BITS_48 for arm64 kernels.
> 
> Note: this change _will_ cause breakage in certain userland software
> making non-portable assumptions about available of top address bits
> for pointer tagging - including luajit and mozilla-js (and hence
> everything using mozilla-js).

FTR, this is an issue DSA is having booting arm64 machine donated by
Gigabyte MR30-AR1. I am currently building a kernel, to get a d-i image
and test this proposed fix.

I'll follow up with the results.

Regards,
-- 
  Hector Oron


signature.asc
Description: PGP signature

Bug#757536: eclipse: FTBFS with Java 8: Duplicate methods named spliterator with the parameters () and ()

[Hector Oron]

Hello,

  In a recent build in a porterbox this packages still fails to build from 
sources.

  Find attached build log.

Regards
-- 
  Hector Oron
dpkg-buildpackage: info: source package eclipse
dpkg-buildpackage: info: source version 3.8.1-8
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Jakub Adam <jakub.a...@ktknet.cz>
 dpkg-source --before-build eclipse-3.8.1
dpkg-buildpackage: info: host architecture amd64
 debian/rules build
make: 'build' is up to date.
 fakeroot debian/rules binary
dh binary
   debian/rules override_dh_auto_install
make[1]: Entering directory '/home/zumbi/eclipse-3.8.1'
ant installSDKinDropins -Dprefix=/usr 
-DdestDir=/home/zumbi/eclipse-3.8.1/debian/tmp
Buildfile: /home/zumbi/eclipse-3.8.1/build.xml
 [echo] Build log is available in build_20150228181320.log
 [echo] uname -m: x86_64. Build eclipse on x86_64 for x86_64.

fetch:

setLib64Dir:

setLibDir:

symlinkBuildFeature:

symlinkBuildConfig:

unpack:

insertBuildId:

applyPatches:

buildHelperTask:

defineTasks:

symlinkDeps:

prebootstrap:
[mkdir] Created dir: /home/zumbi/eclipse-3.8.1/temp
 [copy] Copying 8 files to /home/zumbi/eclipse-3.8.1/temp
 [copy] Copying 1 file to /home/zumbi/eclipse-3.8.1/temp
[javac] /home/zumbi/eclipse-3.8.1/build.xml:458: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 9 source files to /home/zumbi/eclipse-3.8.1/temp
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.3
[javac] warning: [options] source value 1.3 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.1 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 4 warnings
 [copy] Copying 1 file to 
/home/zumbi/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.core.runtime.compatibility.registry/classes
   [delete] Deleting directory /home/zumbi/eclipse-3.8.1/temp

bootstrap:

compilelibs:

build:

p2prep:

provision.cvs:

provisionSDKinDropins:
 [echo] Build log is available in build_20150228181320.log
 [echo] uname -m: x86_64. Build eclipse on x86_64 for x86_64.

fetch:

setLib64Dir:

setLibDir:

symlinkBuildFeature:

symlinkBuildConfig:

unpack:

insertBuildId:

applyPatches:

buildHelperTask:

defineTasks:

symlinkDeps:

prebootstrap:
[mkdir] Created dir: /home/zumbi/eclipse-3.8.1/temp
 [copy] Copying 8 files to /home/zumbi/eclipse-3.8.1/temp
 [copy] Copying 1 file to /home/zumbi/eclipse-3.8.1/temp
[javac] /home/zumbi/eclipse-3.8.1/build.xml:458: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 9 source files to /home/zumbi/eclipse-3.8.1/temp
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.3
[javac] warning: [options] source value 1.3 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.1 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 4 warnings
 [copy] Copying 1 file to 
/home/zumbi/eclipse-3.8.1/build/eclipse-3.8.1-src/plugins/org.eclipse.core.runtime.compatibility.registry/classes
   [delete] Deleting directory /home/zumbi/eclipse-3.8.1/temp

bootstrap:

compilelibs:

build:

p2prep:

provision.installed:
 [echo] Installing into:  
/home/zumbi/eclipse-3.8.1/build/eclipse-3.8.1-src/installation
 [echo] Build log is available in build_20150228181320.log
 [echo] uname -m: x86_64. Build eclipse on x86_64 for x86_64.

run.installed.director:
 [exec] OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
support was removed in 8.0
 [exec] org.eclipse.osgi error loading hook: 
org.eclipse.core.runtime.internal.adaptor.EclipseLogHook
 [exec] java.lang.Error: Unresolved compilation problem: 
 [exec] Duplicate methods named spliterator with the parameters () and 
() are inherited from the types Collection and Iterable
 [exec] 
 [exec] at 
org.eclipse.osgi.internal.baseadaptor.ArrayMap.(ArrayMap.java:23)
 [exec] at 
org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.(ExtendedLogReaderServiceFactory.java:53)
 [exec] at 
org.eclipse.equinox.log.internal.LogServiceManager.(LogServiceManager.java:27)
 [exec] at 
org.eclipse.core.runtime.internal.adaptor.EclipseLogHook.(EclipseLogHook.java:71)
 [exec] at 
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 [exec] at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

Bug#826355: apitrace: wrong Built-Using, causing dak rejection

[Hector Oron]

On Sat, Jun 04, 2016 at 11:09:37PM +0200, Aurelien Jarno wrote:
> Source: apitrace
> Version: 7.1+git20160531.2d78bef0+repack-1
> Severity: serious
> 
> The binary package apitrace-tracers uses the Built-Using filed with a
> binary package in instead of the source one. This causes dak to not find
> the corresponding source package and to reject the package:
> 
>   apitrace-tracers_7.1+git20160531.2d78bef0+repack-1_mipsel.deb: Built-Using 
> refers to non-existing source package libsnappy-dev (= 1.1.3-3)

Find attached patch (untested) which should fix the issue.

-- 
  Hector Oron
diff -Nru apitrace-7.1+git20160531.2d78bef0+repack/debian/changelog apitrace-7.1+git20160531.2d78bef0+repack/debian/changelog
--- apitrace-7.1+git20160531.2d78bef0+repack/debian/changelog	2016-06-03 08:58:07.0 +0200
+++ apitrace-7.1+git20160531.2d78bef0+repack/debian/changelog	2016-06-09 17:20:36.0 +0200
@@ -1,3 +1,11 @@
+apitrace (7.1+git20160531.2d78bef0+repack-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * d/rules: fix Built-Using using source package instead binary name.
+(Closes: #826355)
+
+ -- Héctor Orón Martínez <zu...@debian.org>  Thu, 09 Jun 2016 16:23:43 +0200
+
 apitrace (7.1+git20160531.2d78bef0+repack-1) unstable; urgency=medium
 
   [ Christopher James Halse Rogers ]
diff -Nru apitrace-7.1+git20160531.2d78bef0+repack/debian/rules apitrace-7.1+git20160531.2d78bef0+repack/debian/rules
--- apitrace-7.1+git20160531.2d78bef0+repack/debian/rules	2016-06-03 08:36:39.0 +0200
+++ apitrace-7.1+git20160531.2d78bef0+repack/debian/rules	2016-06-09 17:19:00.0 +0200
@@ -25,11 +25,11 @@
 	dh_install --fail-missing
 
 override_dh_gencontrol:
-	echo "built-using:Depends=zlib1g-dev (= $(shell dpkg-query -s zlib1g-dev \
+	echo "built-using:Depends=zlib (= $(shell dpkg-query -s zlib1g-dev \
| grep Version: \
| cut -d' ' -f2))" \
 >> debian/apitrace-tracers.substvars
-	echo "built-using:Depends=libsnappy-dev (= $(shell dpkg-query -s libsnappy-dev \
+	echo "built-using:Depends=snappy (= $(shell dpkg-query -s libsnappy-dev \
| grep Version: \
| cut -d' ' -f2))" \
 >> debian/apitrace-tracers.substvars


signature.asc
Description: PGP signature